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_... :)
--
# -*- http://cryogen.com/ror4/ -*- http://wwp.mirabilis.com/8123598 -*-
# pgp -kvc: 1024/89d8686d 0f f4 b4 d9 2e 12 c7 b2 1a 85 bc 12 8f 54 77 f1
