Hello All,
It's my first and test message to oslib-devel. I enumerate the main
ideas which must be described in the new documentation. (It's mainly from
our conversation with Luca).
* GDT, IDT state after l1_init, ll_init and
security limitation for GDT_place, i.e. how to manage GDT/IDT in order not to
hurt kernel library and hardware library assumptions (address space
management, tss etc.), default handlers, making CS,DS,ES... to be
zero-based and 4GB limited...
* IRQ mapping (IDT entry "number X" handles IRQ "number Y")
* LDT management
* initialization (which one or both l1_init or ll_init?)
* l1_ and ll_ collisions (what I can't use in hw lib while using
kernel library)
* memory allocation, what are the limits, internals, lacks of free()
and alloc() provided by OSLib?
* v86 usage limitations and assumptions, a note about BIOS... etc.
Optional (not important by now):
* multi-boot modules command, handling modules
--
Best regards,
Juras mailto:yb...@tu...
|
