From: Richard Smith <rsmith@bitworks.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Generic VESA framebuffer driver and Video card BOOT?
Date: Mon, 18 Oct 2004 15:34:58 -0500 [thread overview]
Message-ID: <417428F2.2050402@bitworks.com> (raw)
In-Reply-To: <4173B865.26539.117B09BD@localhost>
Kendall Bennett wrote:
>
> I would assume however a serial port console would be fine for embedded
> machines until the framebuffer driver could come up anyway.
>
This would be an incorrect assumption. Speaking as a developer of one
said embedded system I must have video at boot and be able to dump
critical kernel messages to the screen.
In the field, hooking up a serial cable to see why the unit doesn't boot
requires the dispatch of a tech who would have open up the unit to get
to the serial port. This costs the end client lots of $$. They don't
like that.
By having video on boot the support person can tell the end user to look
at the screen and read back any messages and then make the determination
if a tech dispatch is needed.
And its common practice to only have as many serial ports as the system
needs during runtime. During development you can dual purpose them but
in the final system their may not be a serial port free (or even
installed) to get that console info from.
--
Richard A. Smith
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-18 20:35 UTC|newest]
Thread overview: 73+ 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-14 19:59 ` Zachary Smith
2004-10-15 23:36 ` Ian Romanick
2004-10-14 20:48 ` Zachary Smith
2004-10-15 18:05 ` Kendall Bennett
2004-10-15 18:55 ` Zachary Smith
2004-10-15 19:18 ` Geert Uytterhoeven
2004-10-15 22:22 ` 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 [this message]
2004-10-18 20:47 ` [Linux-fbdev-devel] " 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 ` [Linux-fbdev-devel] " Jon Smirl
2004-10-19 0:18 ` Richard Smith
2004-10-19 0:55 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 1:39 ` Richard Smith
2004-10-19 17:54 ` Kendall Bennett
2004-10-19 21:48 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 19:08 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-19 21:42 ` [Linux-fbdev-devel] " 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 ` [Linux-fbdev-devel] " Martin Waitz
2004-10-18 12:10 ` Gerd Knorr
2004-10-18 20:21 ` [Linux-fbdev-devel] " 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 ` [Linux-fbdev-devel] " 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 ` Kendall Bennett
2004-10-19 21:00 ` Pavel Machek
2004-10-19 21:11 ` Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:31 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-20 18:44 ` Kendall Bennett
2004-10-20 19:10 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 20:47 ` [Linux-fbdev-devel] " Richard Smith
[not found] <416E8322.25700.29ACC2F1@localhost>
[not found] ` <1097843969.9863.8.camel@localhost.localdomain>
[not found] ` <416FB275.6425.1C3D985@localhost>
2004-10-15 20:19 ` Jon Smirl
2004-10-15 22:22 ` Kendall Bennett
2004-10-15 23:02 ` Jon Smirl
2004-10-19 21:09 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 4:03 Yu, Luming
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=417428F2.2050402@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).