From: Pavel Machek <pavel@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: Michal Januszewski <spock@gentoo.org>, linux-kernel@vger.kernel.org
Subject: Re: Bootsplash for 2.6.11-rc4
Date: Sun, 20 Feb 2005 00:25:19 +0100 [thread overview]
Message-ID: <20050219232519.GC1372@elf.ucw.cz> (raw)
In-Reply-To: <20050219230326.GB13135@kroah.com>
Hi!
> > > Just in case someone is interested, this is bootsplash for 2.6.11-rc4,
> > > taken from suse kernel. I'll probably try to modify it to work with
> > > radeonfb.
> > >
> > > Any ideas why bootsplash needs to hack into vesafb? It only uses
> > > vesafb_ops to test against them before some kind of free...
> >
> > It doesn't really need vesafb for anything. Back in the days of 2.6.7
> > I used to release a version of bootsplash that had the dep. on vesafb
> > removed. It worked fine with at least some other fb drivers.
> >
> > You might also want to save yourself some work and try out an
> > alternative solution called fbsplash [1], which I designed after I got
> > tired of fixing bootsplash and which I actively maintain. Fbsplash
> > provides virtually the same functionality, and it has as much code as
> > possible moved into userspace (no more JPEG decoders in the kernel).
> >
> > [1] http://dev.gentoo.org/~spock/projects/gensplash/current/
>
> Pavel, I agree with Michal, take a look at this version of the code
> instead of the version that you posted. It's a _whole_ lot more sane,
> and possibly even mergable.
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...
> Michal, any thoughts on submitting it for inclusion? It seems pretty
> stable now.
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?
If most distros do some kind of splash screen, anyway, it would make
sense to merge one "good" version...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-02-20 0:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 16:52 Pavel Machek
2005-02-19 1:14 ` Michal Januszewski
2005-02-19 23:03 ` Greg KH
2005-02-19 23:25 ` Pavel Machek [this message]
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
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=20050219232519.GC1372@elf.ucw.cz \
--to=pavel@suse.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
Powered by JetHome