Eric Seppanen <[EMAIL PROTECTED]> writes:
> On Mon, Dec 11, 2000 at 03:53:26PM -0700, Ronald G Minnich wrote:
> >
> > it's easy to fix as soon as I can figure out the interface between linux
> > and linuxbios.
>
> After thinking about this for a couple of days (we were talking about
> software reset) I still don't understand what you meant when you wrote
> this.
>
> But it got me to thinking (and maybe this is what you were thinking)...
> there seems to be a lot of things that maybe people want to do in
> linuxbios, and maybe people want to do in the kernel, and sometimes may
> want accessible from both places, and it occurs to me that if you could do
> this, you could have the best of both worlds:
It isn't a seperat universe.
There are a few things that we need to do in the linuxBIOS code.
Turn on RAM, Enable cache, Turn on RAM, Turn on RAM, IRQ routing tables, Turn on RAM.
But very little else.
For interesting functionality that all should be built into linux.
You really can't run any programs until you load a linux kernel anyway.
The functionality doesn't necessarily have to go into the stock kernel,
it can go into a custom patched kernel that resides in ROM, until
the patches are accepted.
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).
With respect to modules the code needed for module loading is a waste
for an embedded kernel.
Eric
