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).
mls suggested that there were some problems with matroxfb in the
past. Have you seen something like that?
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
