1) What I've done:
- documented some of my example code / vxrun with a debugger
interface code and commited it to the repo...so now there is from the
_technological_ point of view everything there i've so far done. there
is still uncommited example code for further memory management and my
9vx tree...but they are not commited because there's really nothing
worth looking at it...there will be ;)
- the memory managment issues goes a bit deeper than i thought...i
had to crawl through quite a bit of windows internals which are
neither covered in the msdn/knowledgebase (or is plain wrong in both
of them! duh!) or other sources of interest. i will document my
findings as soon as i have everything.
(also don't expect either ReactOS nor Wine to be able to run win9vx
anytime soon... there is soo much stuff lacking or plain wrong...)
2) What i am going to do:
- hopefully finally nail that memory management down. my plan is to
write a little memory managment interface that provides a superset of
the functionality for mm functionality needed both in 9vx/mmu.c and
vx32/chunk.c so that the code stays clean and i don't a hundred ifdefs/
extra files all over the place.
- when the mm stuff doesn't take soo long, i guess, i will try to
implement some vfs stuff and see if i can get 9vx to load a binary(but
really...don't count on this one ;)
Best regards,
André
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Plan
9 Google Summer of Code" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/plan9-gsoc?hl=en
-~----------~----~----~----~------~----~------~--~---
