From: Julien Boibessot <julien.boibessot@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
liu.y.victor@gmail.com, Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, B02280@freescale.com
Subject: Re: [PATCH v2] i.MX51 Framebuffer support
Date: Fri, 14 Jan 2011 10:17:09 +0100 [thread overview]
Message-ID: <4D301495.3050906@free.fr> (raw)
In-Reply-To: <20110106094237.GB31708@n2100.arm.linux.org.uk>
Russell King - ARM Linux a écrit :
> On Wed, Jan 05, 2011 at 02:04:20PM +0100, Julien Boibessot wrote:
>
>> The only strange thing I noticed was a kind of uggly sprite/artefact
>> (32x32, I would say) appearing at the same time as the Linux console. I
>> think it may be related to a hardware cursor badly (?) initialised, but
>> I didn't find a fix yet.
>> It disappears when I launch a graphical application (Qt or SDL).
>>
>
> In the top left corner? That'll be the linux penguin logo, and if it's
> not coming out correctly, your framebuffer driver is badly broken.
> Maybe your RGB bitfield information or visual is wrong?
>
Sorry for my late answer...
Penguin logo is OK, the artefact is just under the penguin and is
looking like a blinking cursor until login message is displayed. At that
time it becomes a kind of uggly rectangular black and white lines mix,
overlapping logging message.
I will follow Sascha's advise and try to play with i.MX51 hardware cursor.
Regards,
Julien
next prev parent reply other threads:[~2011-01-14 9:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 10:48 [PATCH v2] i.MX51 Framebuffer support Sascha Hauer
2010-12-20 10:48 ` [PATCH 1/9] ARM i.MX51: Add ipu clock support Sascha Hauer
2010-12-20 10:48 ` [PATCH 2/9] ARM i.MX51: rename IPU irqs Sascha Hauer
2010-12-20 10:48 ` [PATCH 3/9] Add a mfd IPUv3 driver Sascha Hauer
2011-01-03 15:42 ` Sascha Hauer
2011-01-07 12:08 ` Samuel Ortiz
2011-01-31 8:20 ` Sascha Hauer
2011-02-01 10:51 ` Samuel Ortiz
2011-02-01 10:59 ` Sascha Hauer
2011-02-01 11:44 ` Samuel Ortiz
2011-02-01 11:51 ` Russell King - ARM Linux
2011-02-01 12:07 ` Arnaud Patard
2011-02-01 12:51 ` Sascha Hauer
2011-02-01 16:47 ` Uwe Kleine-König
2011-02-01 14:03 ` Samuel Ortiz
2010-12-20 10:48 ` [PATCH 4/9] fb: export fb mode db table Sascha Hauer
2010-12-20 10:48 ` [PATCH 5/9] Add i.MX5 framebuffer driver Sascha Hauer
2010-12-20 10:48 ` [PATCH 6/9] ARM i.MX51: Add IPU device support Sascha Hauer
2010-12-20 10:48 ` [PATCH 7/9] ARM i.MX5: Allow to increase max zone order Sascha Hauer
2010-12-20 10:48 ` [PATCH 8/9] ARM i.MX5: increase dma consistent size for IPU support Sascha Hauer
2010-12-20 10:48 ` [PATCH 9/9] ARM i.MX51 babbage: Add framebuffer support Sascha Hauer
2010-12-20 12:35 ` arden jay
2010-12-22 7:56 ` [PATCH v2] i.MX51 Framebuffer support Arnaud Patard
2010-12-22 10:17 ` Peter Korsgaard
2010-12-23 20:45 ` Arnaud Patard
2011-01-05 13:04 ` Julien Boibessot
2011-01-06 9:42 ` Russell King - ARM Linux
2011-01-14 9:17 ` Julien Boibessot [this message]
2011-01-06 10:23 ` Sascha Hauer
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=4D301495.3050906@free.fr \
--to=julien.boibessot@free.fr \
--cc=B02280@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liu.y.victor@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sameo@linux.intel.com \
/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