From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Fri, 15 Oct 2004 19:39:31 +0100 [thread overview]
Message-ID: <1097865570.10133.187.camel@localhost.localdomain> (raw)
In-Reply-To: <416FB29A.11731.1C46848@localhost>
On Gwe, 2004-10-15 at 19:20, Kendall Bennett wrote:
> That works great on x86, but this solution was developed for PowerPC and
> MIPS embedded systems development not x86 desktop systems. For those
> platforms you either need a boot loader that can bring up the system into
> graphics mode (possible with U-Boot) or to init the video right when the
> framebuffer console driver is brought up.
Right there are certainly cases where you need to do stuff very early.
Even then you may benefit because you can keep the kernel side init
pretty basic and also marked "__init" so it is freed post boot.
> >From the sound of it that might be too early to spawn a user mode
> process?
Do the embedded folks want the kernel boot messages via the display or
are they happy with that via debug port/serial anyway. If so is it an
issue ? You can bring up the video at the point user space begins.
next prev parent reply other threads:[~2004-10-15 19:42 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 [this message]
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
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=1097865570.10133.187.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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