Kendall Bennett wrote:

Richard Smith [off-list ref] wrote:

Good, so my assumption was incorrect which I am happy about. Since it 
makes the work we did more useful ;-)

Anyway in your case do you need diagnostic messages just from the kernel 
or from the firmware as well?

Firmware messages are the most critical since none of the app code is 
running yet and can't self-heal or cry for help.

Some units boot off of a compact flash.  Try as we might to make these 
babies robust they do fail.  So in that case the boot message from the 
firmware needs to be displayed.  In other cases the system net boots 
which increases the firmware error message level by about a factor of 10.

 > To get it in the firmware the video boot
 > code would need to be ported there (U-Boot has a version of it already,
 > but it is the only firmware I am aware of that supports this).

LinuxBIOS has some suport for this.  Not by emulation though.  It uses 
the bios from the BOCHS project as a payload.  Some glue drops the 
system back into real mode and runs the BOCHS bios which scans the 
legacy regions for ROM expansion modules.  So as long as I copy my video 
bios up int 0x0C0000 prior to this I get video.  Otherwise I have to 
wait until X comes up and soft-boots the display device.

-- 
Richard A. Smith