Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Videocard BOOT?
From: Richard Smith
Date: Mon Oct 18 2004 - 17:36:53 EST
Jon Smirl wrote:
Every system has to be able to somehow indicate that it can find/load the
kernel image or that the image is corrupt or that hardware diagnostics failed.
Displaying this info is the responsibility of the BIOS.
Jon, I agree with you 100%. I was merely responding to a statement I
saw as false.
If we could get the video chip manufacturers to provide me with all the
necessary documentation we embedded folk would be happy to do exactly as
you say. We could code up a nice robust boot time init procedure to
serve our purposes. OF would be great if all the mfgs would support it.
Its a sad fact though that we are (x86 anyway) dependant on some
amazingly fragile, stupid, usually binary only, legacy bloated, and
quite often buggy, 16-bit realmode video init code that should have been
put to pasture many years ago.
LinuxBIOS has been trying to come up with a solution to the video BOOT
problems for good while now. Emulation seems to be the only thing that
really has a chance of working.
I don't currently (see next paragraph) need the kernel to try and do all
that stuff for me since I need it prior to when the kernel loads. But
what I would like is to be able to use/build on kernel framework without
having to completely re-invent the wheel.
A long term goal of LinuxBIOS however is to use Linux _AS_ the bios
which kind of nullifies your BIOS responsibility statement. Some of the
LANL clusters are doing this right now. The only reason we aren't doing
it 100% of the time is that a lot of motherboards don't have a big
enough flash. Yet. But with projects like linux-tiny and larger flashes
headed our way those days are numbered.
Linux far exceeds the hardware support level and flexablity of any bios
and already does 90% of the job a bios does anyway. In most cases better
than the bios ever could. Linux booting Linux is the ultimate
bios/bootloader.
--
Richard A. Smith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/