Tyson D Sawyer <[EMAIL PROTECTED]> writes:
> "Eric W. Biederman" wrote:
> > But linking linuxBIOS with linux just sounds wrong.
> >
> > linuxBIOS has only one job boot a linux kernel. Anything
> > that can be moved to kernel space should do so. If you can do
> > something safely from linux it should be removed from the linuxBIOS (core).
>
> I'll agree with these statements. I think that "normal" kernel modules
> for features we want in the kernel is better.
>
> > With respect to modules the code needed for module loading is a waste
> > for an embedded kernel.
>
> I disagree with this. The only way I have been able to get a full
> featured kernel with lots of device drivers into a 512K flash image is
> by using modules. I must make EVERYTHING possible a module and remove
> all support for a standard VGA type console or it doesn't fit. I agree
> that for many embedded systems it is possible to have a more efficient
> statically linked kernel in the flash image but this isn't always the
> case.
O.k. I'll agree here, that modules are can be useful. A better
statement is that requiring everyting the kernel to support modules
just for linuxBIOS when you don't need them is a waste.
I simiply use my initial kernel to boot another linux kernel, and
since I don't need a lot of drivers to do that modules seem like
a waste.
For what it's worth booting a second linux kernel adds maybe
a second to the total boot time.
> Though they are not needed for all applications kernel modules are a
> "very good thing(tm)". Linuxbios must continue to work with
> modules.
I definentily have no problem with that.
Eric
