public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michal Januszewski <spock@gentoo.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Bootsplash for 2.6.11-rc4
Date: Sun, 27 Feb 2005 17:54:20 +0100	[thread overview]
Message-ID: <20050227165420.GD1441@elf.ucw.cz> (raw)
In-Reply-To: <20050220132600.GA19700@spock.one.pl>

Hi!

> > Yes, I agree, almost anything is more sane than code I posted :-(. My
> > only requirement is that it works with radeonfb and similar low-level
> > drivers (so that I can get suspend-to-ram to work) and that it gets
> > past our branding people...   
> 
> I don't know about the branding people, but suspend-to-ram and radeonfb
> shouldn't be a problem for fbsplash :)
>  
> > How many distros do use some variant of bootsplash? SuSE does, from
> > above url I guess gentoo does, too... Does RedHat do something
> > similar? [Or do they just set log-level to very high giving them clean
> > look?] What about Debian?
> 
> As far as I know: SuSE uses bootsplash, Gentoo and PLD use fbsplash,
> RedHat uses rhgb (100% userspace solution, based on xvesa, doesn't
> provide graphical backgrounds on vt's - for that a kernel patch like
> bootsplash or fbsplash is necessary). I don't know about Debian - they
> probably have some (possibly unofficial) support for both bootsplash
> and fbsplash.

Well, I like rhgb the best (because it is 100% userspace and I do not
have to deal with it :-), but it seems like bootsplash should be
deprecated in favor of fbsplash.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  parent reply	other threads:[~2005-02-27 16:54 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 [this message]
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
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=20050227165420.GD1441@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spock@gentoo.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