From: Richard Smith <rsmith@bitworks.com>
To: KendallB@scitechsoft.com
Cc: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
Date: Mon, 18 Oct 2004 20:39:23 -0500 [thread overview]
Message-ID: <4174704B.9050601@bitworks.com> (raw)
In-Reply-To: <41740384.5783.12A07B14@localhost>
Kendall Bennett wrote:
> Actually there is nothing wrong with the x86 BIOS from the perspective of
> functionality and useability (or bloat for that matter). It contains all
> the functionality we need and armed with something like the x86 emulator
> we can use it for what we need on any platform.
> IMHO that is the best solution to the problem because it will be using
> code that has been heavily tested by the vendor. The one thing x86 Video
> BIOS'es can do reliably is POST the graphics card ;-)
I'm just going to take your word on this since you have messed with far
more video bioses than I. I've just got a few too many scars over the
years from trying to make the whole BIOS sub-system robust enough for
embedded standards.
> That would be nice if you could trim it down ;-) Would certainly save a
Check out linux-tiny (http://www.selenic.com/tiny-about/)
> lot of code bloat. But if you do that, then you would need this code in
> the kernel since now it would be the boot loader as well ;-)
Exactly. Which is why I like your project and I think its a good thing.
The only reason I have to carry around the legacy BIOS baggage is
for video.
How big is your in-kernel implementation?
--
Richard A. Smith
next prev parent reply other threads:[~2004-10-19 1:39 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
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 [this message]
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=4174704B.9050601@bitworks.com \
--to=rsmith@bitworks.com \
--cc=KendallB@scitechsoft.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).