>
>Hi all,
>
>> what if the module had a list of function pointers at the
>begining of its
>> address space? then a snippit of org 0 asm code (well, actually just
>> data) could be used within each module to set up the
>pointers properly in
>> a 16 bit link, and the same asm stubs in the kernel would
>work for any
>> module of a given type. maybe with some cleverness, there
>could be only
>> one stub and a bunch of macros or wrappers for accessing it, to make
>> porting to other platforms easier.
>> andru
>
>Oops... looks like I was right, and nobody had tried to implement
>MSDOS/UMSDOS support in ELKS... I was thinking that using UMSDOS as the
>primary filesystem would make it more usable (FAT is more commonly used
>than Minix filesystem -- or am I right?). Maybe I should try
>again with a
>newer kernel source.
>
>Concerning the function pointer business... it might work for kernel
>_functions_, but I doubt that it can work with kernel _variables_... :)
>
presumably modules should only have limited access (if at all) to kernel
_variables_?
The big problem i thought was stuff like kmalloc cos where does it allocate
memory?
unless the kernel is a (compact?) memory model, where everything shares one
DS and SS and we have lots of little CS's
how we get this to compile and link i'm not quite sure, although the big
linux kernel loads modules by doing the linker bit at run-time IIRC
Cheers
Paul
