"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.
It also happens that my embedded project has numorous expansion ports
that may require a large variety of device drivers. I don't want to be
compiling kernels for every combination and there is no way I could
compile them all in without a huge bloated kernel. This would be bad
even if the static kernel could fit in my flash.
Though they are not needed for all applications kernel modules are a
"very good thing(tm)". Linuxbios must continue to work with modules.
> Eric
Ty
--
Tyson D Sawyer iRobot Corporation
Senior Systems Engineer Real World Interface Div.
[EMAIL PROTECTED] Robots for the Real World
603-532-6900 ext 206 http://www.irobot.com
