linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Problems with rotated Logos
Date: Wed, 14 Jun 2006 19:56:41 +0100	[thread overview]
Message-ID: <1150311401.9240.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4490091B.4090900@gmail.com>

Hi,

On Wed, 2006-06-14 at 21:03 +0800, Antonino A. Daplas wrote:
> Richard Purdie wrote:
> > 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.
> 
> Yes, it's a bug. Also present in CCW. Try this patch.

The patch helps in that the 640x185 image no longer locks the system up
and it displays something, thanks! The image is corrupted however.
Rather than trying to describe it:

http://www.rpsys.net/openzaurus/temp/logo-corrupt.jpg

(I'm refraining from comment about the logo itself ;-)

As well as the wrapping, the blue colour to the left is also corruption,
and marks the edge of the screen.

I suspect the rotation function has a bug...

Cheers,

Richard

  reply	other threads:[~2006-06-14 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 10:13 Problems with rotated Logos Richard Purdie
2006-06-14 13:03 ` Antonino A. Daplas
2006-06-14 18:56   ` Richard Purdie [this message]
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=1150311401.9240.9.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).