From: Richard Purdie <rpurdie@rpsys.net>
To: "Antonino A. Daplas" <adaplas@gmail.com>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Problems with rotated Logos
Date: Wed, 14 Jun 2006 11:13:17 +0100 [thread overview]
Message-ID: <1150279997.27375.15.camel@localhost.localdomain> (raw)
Hi,
I've been experimenting with logos on the Sharp Zaurus C3000 which has a
480x640 framebuffer which is rotated clockwise to give 640x480. I'm
using a 2.6.16 based kernel.
If I use the standard Linux logo (clut224), all is well. I added a
640x185 logo and this locked the machine up when booting. Space was
cleared at the top of the console for the logo and some boot messages
appeared beneath it. Also, 639x185 gave the same result.
To assist debugging, I changed to a 480x185 logo and tested this without
console rotation where it displays fine. If I rotate the console
clockwise, the logo doesn't appear but there is space left for it and
the system boots.
I've tried to get further with this but I couldn't quite understand how
fb_rotate_logo_cw was working. Could this be broken in the case where
you have a logo with width > height? (height > width in the case of that
function). I made a test program to look at the numbers outputted by
that function and they didn't seem right for my logo size. I've not
checked with the tux logo sizes as I ran out of time but will do in due
course.
I'll continue to look into this but I wondered if anyone had any
thoughts where the problem might be offhand? The lockup worries me but
could be some separate issue and I'll work on getting the 480x185 logo
working initially.
Regards,
Richard
next reply other threads:[~2006-06-14 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 10:13 Richard Purdie [this message]
2006-06-14 13:03 ` Problems with rotated Logos Antonino A. Daplas
2006-06-14 18:56 ` Richard Purdie
2006-06-14 21:24 ` Antonino A. Daplas
2006-06-14 21:27 ` Antonino A. Daplas
2006-06-14 23:35 ` Richard Purdie
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=1150279997.27375.15.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=adaplas@gmail.com \
--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).