From: Joshua Kwan <joshk@triplehelix.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.5] Oversized FB logos
Date: Fri, 16 Apr 2004 20:07:24 -0700 [thread overview]
Message-ID: <pan.2004.04.17.03.07.22.362894@triplehelix.org> (raw)
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
next reply other threads:[~2004-04-17 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 3:07 Joshua Kwan [this message]
2004-04-17 9:26 ` Jorge Bernal (Koke)
2004-04-17 10:44 ` Russell King
2004-04-21 21:05 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2004.04.17.03.07.22.362894@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®