Usplash question: a program is ready, but can we call it usplash?

[Matthew Garrett]

On Mon, 2005-04-11 at 18:28 -0400, Goshawk wrote:
> 1) vesa-tng is to be fixed for several bugs, i've already spoke with the
> author about that, and we think that it's a good solution (if fixed) if
> it will be added to the vanilla kernel.

Sure. At the moment it doesn't play nicely with X - that may improve in
the future, but right now it's not really an option.

> 2)the program that i've build (not only me but all the debsplash group)
> have changed name.. now it's called splashy, yes, it's even thought for
> ubuntu system but it's not usplash...

Yup, I noticed that. Not really a problem.

> 3)about framebuffers, there are many drivers, usually in 2 years old
> laptops vesa is well supported, we wil do all in our possibilities to
> make splashy compatible with all the linux systems.

If we want suspend/resume support (which we do), then we either need
some vicious changes to the Linux framebuffer infrastructure or we need
to use vga16fb. In the Breezy timescale, the latter of these is rather
more practical...

vga16fb is used in the installer, so it works in the vast majority of
cases. If it's disabled in the installer, we should probably carry that
across to the installed system.

Of course, it makes sense to allow the bootsplash solution to take
advantage of better framebuffers when they're available. However, the
reality of the situation is that we're pretty much stuck with vga16fb as
the lowest common denominator if we want suspend/resume support.
-- 
Matthew Garrett | mjg59 at srcf.ucam.org