From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug in cfb_console driver
Date: Wed, 21 Mar 2012 13:18:39 +0100 [thread overview]
Message-ID: <20120321131839.344f3542@wker> (raw)
In-Reply-To: <2061837.hvmuTMjBKQ@pali>
On Wed, 21 Mar 2012 02:54:02 -0700 (PDT)
Pali Roh?r <pali.rohar@gmail.com> wrote:
> On Saturday 10 March 2012 14:06:23 Pali Roh?r wrote:
> > On Tuesday 06 March 2012 10:25:57 Anatolij Gustschin wrote:
> > > Hi,
> > >
> > > On Mon, 05 Mar 2012 11:42:13 +0100
> > > Pali Roh?r <pali.rohar@gmail.com> wrote:
> > > ...
> > >
> > > > Hi, thanks. If you need some more info write me.
> > >
> > > Can you please test with attached patch? Does it help to solve
> > > your problem on N900?
> > >
> > > Thanks,
> > > Anatolij
> >
> > Hi! This patch solving problem on my N900.
>
> Hi, I found a problem why code (without) this patch garbage display
> output. I played with code in function video_draw_cursor and every
> time when I tried to only read what is stored in *dest, on n900
> dispaly was show some random white or blue pixel. This code not
> working on n900:
>
> static u8 foo;
> ...
> for (y for (x u8 *dest foo *dest }
> }
>
> But if I commented assign foo
> So I think that reading memory of framebuffer on n900 does not working
> (it also write something somewhere...) What do you think, where can be
> problem?
I have a suspicion that your framebuffer area configured for the
display controller is not exclusively used. In another email [1]
to Marek I explained where the problem could be.
Thanks,
Anatolij
[1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/123527/focus=127720
prev parent reply other threads:[~2012-03-21 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 3:32 [U-Boot] Bug in cfb_console driver Pali Rohár
2012-03-04 21:12 ` Pali Rohár
2012-03-05 10:16 ` Anatolij Gustschin
2012-03-05 10:42 ` Pali Rohár
2012-03-06 9:25 ` Anatolij Gustschin
2012-03-10 13:06 ` Pali Rohár
2012-03-21 9:54 ` Pali Rohár
2012-03-21 12:18 ` Anatolij Gustschin [this message]
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=20120321131839.344f3542@wker \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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