From: Pavel Machek <pavel@ucw.cz>
To: Christoph Hellwig <hch@infradead.org>,
Erik Rigtorp <erik@rigtorp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swsusp bootsplash support
Date: Fri, 9 Jul 2004 00:52:16 +0200 [thread overview]
Message-ID: <20040708225216.GA27815@elf.ucw.cz> (raw)
In-Reply-To: <20040708210403.GA18049@infradead.org>
Hi!
> > Perhaps CONFIG_BOOTSPLASH should be in mainline after all?
> > I really don't want to see 2 different incompatible sets
> > of hooks into swsusp....
>
> No. This stuff has no business in the kernel, paint your fancy graphics
> ontop of fbdev. And the SuSE bootsplash patch is utter crap, I mean what
> do you have to smoke to put a jpeg decoder into the kernel?
No idea; smoking is prohibited in SuSE offices, so someone external
had to do that ;-).
I have not seen SuSE version of bootsplash... I do not want to
see. But this way, SuSE has its own crappy bootsplash, RedHat probably
too, Mandrake probably too, etc.
And now, SUSE will want splash over swsusp, RedHat probably too,
Madrake probably too, etc. I do not want to deal with 3 different sets
of hooks into swsusp.
Now.. Perhaps cleaned-up bootsplash could find its way into
kernel. That would at least turn down ammount of crap in
distributions. At least there would be unified way to turn that thing
off...
Or at least standartized hooks for various splashes, so that I do not
have to deal with 3 different sets?
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:[~2004-07-08 22:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 11:05 [PATCH] swsusp bootsplash support Erik Rigtorp
2004-07-08 13:39 ` Christoph Hellwig
2004-07-08 20:48 ` Pavel Machek
2004-07-08 21:04 ` Christoph Hellwig
2004-07-08 22:52 ` Pavel Machek [this message]
2004-07-08 22:55 ` Christoph Hellwig
2004-07-08 23:23 ` Dave Jones
2004-07-09 5:15 ` Pavel Machek
2004-07-09 11:55 ` Dave Jones
2004-07-09 12:19 ` Nigel Cunningham
2004-07-09 14:27 ` Bartlomiej Zolnierkiewicz
2004-07-09 22:00 ` Nigel Cunningham
2004-07-09 15:56 ` Erik Rigtorp
2004-07-12 13:43 ` Jan Rychter
2004-07-12 3:21 ` Eric Altendorf
2004-07-10 12:34 ` Pavel Machek
2004-07-14 11:27 ` Jan Rychter
2004-07-09 8:36 ` Erik Rigtorp
2004-07-09 14:48 ` Stefan Reinauer
2004-07-09 15:01 ` Dave Jones
2004-07-09 20:44 ` Diego Calleja García
2004-07-09 21:49 ` Erik Rigtorp
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=20040708225216.GA27815@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=erik@rigtorp.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.