> > The hard part is not linux booting linux but the passing of the
> > firmware/BIOS tables from one kernel to the next. Especially those
> > that can only be obtained by a 16bit query. It is my assumption that
> > after the OS runs you cannot return to the firmware, it's state is
> > hopelessly mangled. That may not be totally true but it is fairly
> > close to the truth.
>
> It is unless you control the firmware. Our (Cobalt) firmware reserves a
> region of memory which the primary (in-flash) kernel is not made aware of.
> The in-flash kernel can do all the fun things a kernel can do, and then
> return to firmware.
Hmm. I might have to check it out. Comparing notes with what you do on
the Cobalt with what I'm doing in linuxBIOS. Do you happen to have
a url?
But as I want a general solution I don't intend to pick a solution
that depends on the firmware.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/