From: "Thomas S. Iversen" <zensonic@zensonic.dk>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: No tux in 24 and 32 bits?
Date: Thu, 4 Sep 2003 22:22:52 +0200 [thread overview]
Message-ID: <20030904202252.GA13496@zensonic.dk> (raw)
Hi There
During development of a new driver I found that tux is not drawn upon
boot of the kernel if I boot into a 24 or 32 bpp framebuffer
(truecolor, packed pixels) and use the software accelerated routines.
First I thought that I might have done something wrong, but then I
tried the aty128 driver on a ATI Rage 128 card and the same thing
happened.
I now know that my driver behaves like it should, but would anybody
care to explain why it is so? Skimming the logo setup code I see code
for handling truecolor modes and setting up pseudopalettes and stuff,
so I can not see any reasons for it not to be working.
Regards Thomas, Denmark
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
reply other threads:[~2003-09-04 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030904202252.GA13496@zensonic.dk \
--to=zensonic@zensonic.dk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).