linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Smith <rsmith@bitworks.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
Date: Mon, 18 Oct 2004 17:34:45 -0500	[thread overview]
Message-ID: <41744505.4080507@bitworks.com> (raw)
In-Reply-To: <9e47339104101814166bf4cfe5@mail.gmail.com>

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



  reply	other threads:[~2004-10-18 22:34 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 19:02 Generic VESA framebuffer driver and Video card BOOT? Kendall Bennett
2004-10-15  0:27 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-15 18:36   ` Kendall Bennett
2004-10-15 21:51     ` Antonino A. Daplas
2004-10-15 23:20       ` Jon Smirl
2004-10-15 23:51         ` Kendall Bennett
2004-10-15 23:58           ` Jon Smirl
2004-10-19 21:15           ` Pavel Machek
2004-10-16  1:50         ` Antonino A. Daplas
2004-10-16  2:03           ` Jon Smirl
2004-10-18 19:34             ` Kendall Bennett
2004-10-18 20:34               ` Richard Smith
2004-10-18 20:47                 ` Kendall Bennett
2004-10-18 21:04                   ` Richard Smith
2004-10-18 21:16                 ` Jon Smirl
2004-10-18 22:34                   ` Richard Smith [this message]
2004-10-18 23:28                     ` Jon Smirl
2004-10-19  0:18                       ` Richard Smith
2004-10-19  0:55                     ` Kendall Bennett
2004-10-19  1:39                       ` Richard Smith
2004-10-19 17:54                         ` Kendall Bennett
2004-10-19 21:48                       ` Pavel Machek
2004-10-20 17:01                         ` Kendall Bennett
2004-10-20 19:08                           ` Pavel Machek
2004-10-21 19:36                             ` Kendall Bennett
2004-10-19 21:42                   ` Pavel Machek
2004-10-15 12:05 ` Gerd Knorr
2004-10-15 12:38   ` Geert Uytterhoeven
2004-10-15 12:45     ` Alan Cox
2004-10-19 21:54       ` Pavel Machek
2004-10-15 13:13     ` Gerd Knorr
2004-10-17 12:07       ` Martin Waitz
2004-10-18  8:36         ` Gerd Knorr
2004-10-18 11:39           ` Martin Waitz
2004-10-18 12:10             ` Gerd Knorr
2004-10-18 20:21               ` Helge Hafting
2004-10-18 20:42                 ` Oliver Neukum
2004-10-19 16:57                   ` Martin Waitz
2004-10-15 18:29     ` Venkatesh Pallipadi
2004-10-16  9:01       ` Nigel Cunningham
2004-10-15 18:36   ` Kendall Bennett
2004-10-15 13:48 ` Helge Hafting
2004-10-15 18:36   ` Kendall Bennett
2004-10-15 21:44     ` Helge Hafting
2004-10-15 22:12       ` Kendall Bennett
2004-10-16  0:41         ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-26 11:14           ` Paulo Marques
2004-10-27  1:58             ` Kendall Bennett
2004-10-27 11:11               ` Paulo Marques
2004-10-27 19:52                 ` Kendall Bennett
2004-10-15 21:51     ` Antonino A. Daplas
2004-10-16 17:44 ` Jon Smirl
2004-10-18 19:34   ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:00 ` Pavel Machek
2004-10-19 21:11 ` Pavel Machek
2004-10-20 17:01   ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 17:31     ` Pavel Machek
2004-10-20 18:44       ` Kendall Bennett
2004-10-20 19:10         ` Pavel Machek
2004-10-21 19:36           ` Kendall Bennett
2004-10-21 20:47             ` Richard Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41744505.4080507@bitworks.com \
    --to=rsmith@bitworks.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).