All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Jeff Mitchell <jmitchell@ll.mit.edu>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Color ghosting on BeagleBoard xM rev C
Date: Tue, 26 Jul 2011 11:15:07 -0600	[thread overview]
Message-ID: <4E2EF61B.3050002@mlbassoc.com> (raw)
In-Reply-To: <4E2EF2C1.7060708@ll.mit.edu>

On 2011-07-26 11:00, Jeff Mitchell wrote:
> On 07/26/2011 12:47 PM, Gary Thomas wrote:
>> On 2011-07-15 09:30, Jeff Mitchell wrote:
>>> Darren Hart suggested I send this to the list...
>>>
>>> Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom
>>> doesn't display these problems, so the setup should be fine.
>>>
>>> I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the
>>> newer DSS2 omapfb.mode variant).
>>
>> Did you ever find out what is causing this?
>
> No, but I'll be testing out a new build soon -- haven't been able to for a bit.
>
>> When you say that it works on one system (Poky?) vs another (Angstrom?)
>> are they both running the same version of U-Boot? I'm seeing this same
>> behaviour on one of my boards, but only when I run U-Boot from 2011.06
>
> Yes -- Yocto/Poky/Sato vs. Angstrom. I doubt they're running the same version of U-Boot, but I don't know the version numbers offhand.

Check the display setup.  In my case, my old U-Boot (which works great)
was using dvimode=1024x768-24@60 and the new U-Boot is using dvimode=1024x768MR-16@60
When I switch back to the old setting, even with the new U-Boot, my display
runs great again.  n.b. this may be kernel revision sensitive as well.

>
>> BTW - why did you send your original query to the Poky list?
>
> Because Darren suggested that I do so, to get various eyes on it :-)

Sounds reasonable - I only asked because your original email didn't
really spell out why it went to the Poky list.

Thanks & good luck

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2011-07-26 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 15:30 Color ghosting on BeagleBoard xM rev C Jeff Mitchell
2011-07-15 18:33 ` Darren Hart
2011-07-15 19:12   ` Koen Kooi
2011-07-15 19:32     ` Jeff Mitchell
2011-07-26 16:47 ` Gary Thomas
2011-07-26 17:00   ` Jeff Mitchell
2011-07-26 17:15     ` Gary Thomas [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=4E2EF61B.3050002@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=jmitchell@ll.mit.edu \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.