public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Januszewski <spock@gentoo.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Arjan van de Ven <arjan@infradead.org>,
	aj@suse.de, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Bootsplash for 2.6.11-rc4
Date: Tue, 1 Mar 2005 14:09:10 +0100	[thread overview]
Message-ID: <20050301130910.GD14278@spock.one.pl> (raw)
In-Reply-To: <20050227194123.GX1441@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Sun, Feb 27, 2005 at 08:41:23PM +0100, Pavel Machek wrote:

Hi,

> [aj added to the list].
> 
> Andreas, who is the person to talk about this? I like redhat's
> solution the best. Pass "quiet", perhaps replace penguin with some big
> picture including penguin and chameleon or something, and do the
> interesting work in userspace...
> 
> That's the best solution, technically... Perhaps it is even acceptable
> politically?

And that's exactly how it will be done in fbsplash, as soon as I move
the rest of the 'silent'-handling code to the userspace. Fbsplash will 
call a userspace helper as soon as fbcon is initialized. The helper can 
be used put the console into KD_GRAPHICS mode and paint a full-screen 
picture to cover any text messages. Progress bars and other fancy stuff 
will be handled after init, by 100% userspace code (it's done that way 
even with the current version of fbsplash).

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 --]

  reply	other threads:[~2005-03-01 13:24 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 [this message]
2005-02-27 19:52             ` Michal Januszewski
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=20050301130910.GD14278@spock.one.pl \
    --to=spock@gentoo.org \
    --cc=aj@suse.de \
    --cc=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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