[2.6.5] Oversized FB logos

[2.6.5] Oversized FB logos

[Joshua Kwan]

Hi everyone,

I'm coming up with a grandma-proof laptop so I made a 800x580 PPM boot
logo and added it into my 2.6 kernel source. The machine does boot using
the image, HOWEVER, the first 11 lines of kernel messages after switching
to FB mode appear on top of the logo.

Console: switching to colour frame buffer device 100x37
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Hangcheck: starting hangcheck timer 0.5.0 (tick is 180 seconds, margin is 60 seconds).
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M

As expected, though, the first line of kernel messages prints;
the console won't function without at least one line anyway.

This renders the concept of the friendly logo to prevent grandma from
bugging out from all the kernel messages pretty useless.

Note that I'd be using bootsplash for this but vesafb only works up to
8bit color and bootsplash requires 16bit color.

Are boot logos in any way supported in this fashion? I'm tempted to just
nuke the emit_log_char call in printk.c, which I think might serve my
purpose temporarily...

Any hints/help provided would be highly appreciated. Thanks

-- 
Joshua Kwan

Re: [2.6.5] Oversized FB logos

[Jorge Bernal (Koke)]

On Sábado, 17 de Abril de 2004 05:07, Joshua Kwan wrote:
> Hi everyone,
>
> Note that I'd be using bootsplash for this but vesafb only works up to
> 8bit color and bootsplash requires 16bit color.

Maybe I haven't understood your question but I'm using vesafb at 1280x1024 and 
16 bits w/o any problem.

> Are boot logos in any way supported in this fashion? I'm tempted to just
> nuke the emit_log_char call in printk.c, which I think might serve my
> purpose temporarily...
>

what about passing CONSOLE=/dev/tty2 or CONSOLE=/dev/null at boot loader 
command line?? I saw that once in something like bootsplash or lpp but I'm 
not sure if this will work well.

> Any hints/help provided would be highly appreciated. Thanks

Re: [2.6.5] Oversized FB logos

[Russell King]

On Sat, Apr 17, 2004 at 11:26:09AM +0200, Jorge Bernal (Koke) wrote:
> what about passing CONSOLE=/dev/tty2 or CONSOLE=/dev/null at boot loader 
> command line?? I saw that once in something like bootsplash or lpp but I'm 
> not sure if this will work well.

Even better - use quiet on the kernel command line.  This sets the
console level to 4, which means only error, critical, alert and
emergency messages will appear on the console.

This means that, should something go wrong, grandma can "bug out"
and phone you, and read the error message to you.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

Re: [2.6.5] Oversized FB logos

[James Simmons]

> On Sábado, 17 de Abril de 2004 05:07, Joshua Kwan wrote:
> > Hi everyone,
> >
> > Note that I'd be using bootsplash for this but vesafb only works up to
> > 8bit color and bootsplash requires 16bit color.
> 
> Maybe I haven't understood your question but I'm using vesafb at 1280x1024 and 
> 16 bits w/o any problem.

I understand what he is talking about. There is a bug in cfb_imageblit 
in such that it doesn't allow images of color depths greaters than 8 bpp.
That is image depth. Not framebuffer depth. I just fixed that bug and I 
will be pushing that fix to Andrew Morton for people to test. I haven't 
tested it on big endian yet tho.