Re: Make the init-process look like the StarWars Credits

Rob Couto
2004-01-10T04:24:27Z

On Friday 09 January 2004 13:39, Måns Rullgård wrote:
> I suppose it would be possible to use 3D features of the graphics
> chip. It would require a rather massive hacking in the fb driver, of
> course.

massive hacking? hehe, yea. geniuses, please stop me when I stop making
sense...

AFAICT, that would be both excellent and terrible at the same time. using hw
accel makes the process lighter on CPU and looks great but ridiculously
intense on the coder... i mean, who could you recruit to take X11 vid drivers
and mutate them into kernel code? you'd need 3D code that belongs to Mesa,
DRI code that belongs to whatever X module and the matching kernel module,
possibly agpgart, and so on. by the time it's 3D, you aren't using the
framebuffer code, you've taken the GUI and moved it into the kernel --- hello
Win32. That's if you did it smart and made it modular enough to have other
purposes, i.e. X11 overdrive... then X needs to know about it, or at least
the DRI module involved, and then it's either they trip over one another or X
gets cut down to just the libs and network activity. then maybe the kernel
begins with X which starts your xterms fullscreen on vt1-6. all the time it's
faster and loads sooner. and along with it, you get the legendary stability
of a MS slop'erating system. to have that much for one brief piece of
eyecandy is a little silly. and when the booting's done, is vt1 still zooming
out into space? will I be able to see the top few lines of 'top'?

the nice thing about fbmngplay is that it can easily be told to stop ;)
why not simply make the console a file or fifo, then "tail -f <file> |
text_render_app -d /dev/fb0" as soon as init can fire it off?

there seems to be a mailing list at bootsplash.org, maybe we should be there
instead.