From: Martin Waitz <tali@admingilde.org>
To: Kendall Bennett <KendallB@scitechsoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Generic VESA framebuffer driver and Video card BOOT?
Date: Tue, 19 Oct 2004 19:01:11 +0200 [thread overview]
Message-ID: <20041019170111.GG3618@admingilde.org> (raw)
In-Reply-To: <4173BA7D.32320.11833A1D@localhost>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
hoi :)
On Mon, Oct 18, 2004 at 12:43:41PM -0700, Kendall Bennett wrote:
> I am not sure what you mean by basic text output? If you mean to a
> display, then yes, embedded boxes using U-Boot and OpenBIOS usually do
> not have any text output. But if you mean serial output that is usually
> the method of choice for the embedded machines that don't have support
> for a physical display in the firmware.
I mean: text output on the preferred console.
Embedded devices have a serial console anyway and all other machines
have firmware support for drawing text.
That is: switching into graphics mode can be done by the firmware, bootloader,
or by userspace and doesn't have to be in the kernel.
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-19 17:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2Pkf0-42m-11@gated-at.bofh.it>
[not found] ` <2PncW-6j9-19@gated-at.bofh.it>
[not found] ` <2PncW-6j9-21@gated-at.bofh.it>
[not found] ` <20030401205016$5cc4@gated-at.bofh.it>
[not found] ` <20030401205016$63f7@gated-at.bofh.it>
[not found] ` <20030424075011$4028@gated-at.bofh.it>
[not found] ` <1ewKr-2Kh-41@gated-at.bofh.it>
[not found] ` <CebL.O9.13@gated-at.bofh.it>
[not found] ` <1bucs-57R-33@gated-at.bofh.it>
[not found] ` <2PncW-6j9-23@gated-at.bofh.it>
[not found] ` <20030423094012$4166@gated-at.bofh.it>
[not found] ` <2PncW-6j9-17@gated-at.bofh.it>
[not found] ` <2PAMY-7Ir-21@gated-at.bofh.it>
2004-10-15 14:22 ` Generic VESA framebuffer driver and Video card BOOT? Andi Kleen
2004-10-15 14:33 ` Alan Cox
2004-10-15 18:20 ` Kendall Bennett
2004-10-15 18:39 ` Alan Cox
2004-10-15 22:27 ` Kendall Bennett
2004-10-15 23:34 ` Alan Cox
2004-10-16 1:07 ` William Lee Irwin III
2004-10-21 11:59 ` Pavel Machek
2004-10-18 11:44 ` Martin Waitz
2004-10-18 19:43 ` Kendall Bennett
2004-10-19 17:01 ` Martin Waitz [this message]
2004-10-19 17:54 ` Kendall Bennett
2004-10-15 15:37 ` Gerd Knorr
2004-10-16 0:55 ` Andi Kleen
2004-10-16 12:21 ` Gerd Knorr
2004-10-21 4:03 Yu, Luming
[not found] <2PjiW-3hl-21@gated-at.bofh.it>
2004-10-14 20:03 ` Andi Kleen
2004-10-14 20:46 ` Kendall Bennett
2004-10-15 12:39 ` Alan Cox
2004-10-15 18:20 ` Kendall Bennett
2004-10-15 18:41 ` Alan Cox
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
2004-10-20 15:23 ` Paulo Marques
2004-10-20 17:27 ` Kendall Bennett
-- strict thread matches above, loose matches on Subject: below --
2004-10-14 19:02 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 17:44 ` Jon Smirl
2004-10-19 21:00 ` Pavel Machek
2004-10-19 21:11 ` Pavel Machek
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=20041019170111.GG3618@admingilde.org \
--to=tali@admingilde.org \
--cc=KendallB@scitechsoft.com \
--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).