> > Hello hackers,
> > I think that linux has somehow grown up and I would like to suggest we (
> > mostly you as my knowledge ... ) integrate the "new version" of
> > linux_logo.h which makes fullscreen tty1 graphical(maybe as non default
> > ).
> > What do you think about that ?
>
> IIRC, you can already do that using the framebuffer device. Please tell
> me if I am wrong.
Yes, atleast the are various patches out there for various 2.4.X kernels,
and as the include/linux/linux_logo.h format changed some of them work and
some require tweaking. The simplest ones allow larger pictures than 80x80
and more complicated ones also display a progress bar (google: linux
progress patch).
I have made a patch for 2.4.X that makes three new compile options -
custom boot logo, non blinking fbcon cursor and totally hidden fbcon
cursor. Custom boot logo stuff requires a picture in some well known
format and then uses convert, ppm* progs and one custom tool to
convert it to linux_logo.h alike "format". I've omitted the progress bar
stuff because that'd require placing code snippets allover the linux init
code. I'm glad to make that available somewhere, but it's all been done
over and over again by loads of people out there, sadly none of that code
has ever made it to the kernel.
My guess is that the people that have needed some tweaking to the graphical
booting (companies involved in making embedded linux boxes) have tweaked the
drivers/video/fbcon.c themselves, like myself, but have thought that
linux is fine without the bloat that bootlogo ehancements requires.
Besides there's been discussion about this here in lkml before.
You see, using a larger picture as a boot logo requires that it's compiled
into the kernel and it indeed increases it's size (some 100kb and then
some for a fullscreen picture). But indeed for embedded boxes it's
sometimes the only possible solution.
For the record, redirecting the kernel output to tty2 (kernel parameter
console=/dev/tty2 or perhaps even append="console/dev/tty2" for lilo),
and spalshing the picture from inittab or rc.sysinit (or similar)
('cat /dev/fb0 > /tmp/screenshot' and 'cat /tmp/screenshot > /dev/fb0')
may be sufficient, since the kernel boots fairly swiftly and
usually it's the userspace bootstuff that takes the time.
Redirecting the rc.sysinit to tty2 from inittab might also come in handy.
--
Tommi "Kynde" Kyntola
/* A man alone in the forest talking to himself and
no women around to hear him. Is he still wrong? */
-
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/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:28 EST