That is what I was actualy reffering to. I see even the network adapter drivers being implemented as kernel modules. of course if the kernel load/unload module mechanism would take more than the actual driver the solution is to have different kernels compiled for the particular hardware. Probably the principial question is if ELKS will need runtime kernel modules or not.
cristi
At 09:11 PM 6/13/00 +0000, you wrote:
On Tue, 13 Jun 2000, Cristi wrote:
>
> I would rather wait for a solid kernel and then add networking. I think
> networking should be a module as you don't need networking everywhere.
> Biulding it modular you can deal with limited resources.
>
I think the origional plan was to have a user space stack, and in kernel
drivers. That makes sense, as the 64k limit won't stretch much further.
Lukeboo
