[ from the giant-pandas-are-everywhere dept. ]
Well the project code is a good few thousand lines now and can talk to the prom, framebuffer, etc. though the memory management code is starting to get really bothering – at the moment everything I try to do seems to be failing, and it is very difficult to determine where when you have no hardware debugger. I am writing a minimal pixel painting assembly routing for emergency display blanking to determine whether the code is still running at certain points or if it has gone for a nice little trip through the memory to execute whatever it finds there again…
The memory concept at the moment is to have a single global free list which is initialised to contain a double(y) linked list of structs describing pages of memory – effectively all memory is one giant array of page frames with mimimal cleaverness implemented at this stage.