Messages in this thread | | | Date | Fri, 9 Jul 2004 00:52:16 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH] swsusp bootsplash support |
| |
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! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |