From: Michal Januszewski <spock@gentoo.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Pavel Machek <pavel@ucw.cz>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: Bootsplash for 2.6.11-rc4
Date: Sun, 27 Feb 2005 20:52:06 +0100 [thread overview]
Message-ID: <20050227195206.GA2202@spock.one.pl> (raw)
In-Reply-To: <1109532700.15362.42.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Sun, Feb 27, 2005 at 08:31:39PM +0100, Arjan van de Ven wrote:
> well.. how much does it really need in kernel space? I mean, with all
> drivers as modules, and the "quiet" option, initramfs runs *really*
> fast. And that can just bang a bitmap to the framebuffer as first
> thing... (rhgb does it a bit later but that's a design choice in a
> feature vs early-boot tradeoff).
Most of the code in fbsplash handles the so-called 'verbose' mode,
ie. displaying a pretty picture in the background of the consoles.
The 'silent' mode (progress bar and stuff) can be brought down to
a single call to a userspace helper which can paint the initial bitmap
or do whatever else it wants to do. In fact, this is how it works now.
However, fbsplash currently not only calls the helper, but also tracks
whether we're running in the 'silent' mode or in the 'verbose' mode.
I plan to remove that functionality, so we'll be left with the
following:
- silent is handled 100% by userspace
- verbose is handled by fbsplash (ie. kernelspace)
- fbsplash takes care of the initial call to the userspace
helper when starting in the silent mode (splash=silent in
the kernel command line)
Live long and prosper.
--
Michal 'Spock' Januszewski Gentoo Linux Developer
cell: +48504917690 http://dev.gentoo.org/~spock/
JID: spock@im.gentoo.org freenode: #gentoo-dev, #gentoo-pl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-27 19:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 16:52 Bootsplash for 2.6.11-rc4 Pavel Machek
2005-02-19 1:14 ` Michal Januszewski
2005-02-19 23:03 ` Greg KH
2005-02-19 23:25 ` Pavel Machek
2005-02-20 9:50 ` Arjan van de Ven
2005-02-20 13:26 ` Michal Januszewski
2005-02-21 1:59 ` Marcos D. Marado Torres
2005-02-27 16:54 ` Pavel Machek
2005-02-27 19:31 ` Arjan van de Ven
2005-02-27 19:41 ` Pavel Machek
2005-03-01 13:09 ` Michal Januszewski
2005-02-27 19:52 ` Michal Januszewski [this message]
2005-02-27 21:03 ` Greg KH
2005-03-01 13:05 ` Michal Januszewski
2005-03-08 2:52 ` Michal Januszewski
2005-02-20 13:15 ` Michal Januszewski
2005-02-23 17:53 ` Greg KH
2005-02-28 17:40 ` Pavel Machek
2005-03-01 13:03 ` Michal Januszewski
2005-03-01 14:28 ` Michael Schroeder
2005-03-01 23:32 ` 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=20050227195206.GA2202@spock.one.pl \
--to=spock@gentoo.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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