<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>1260</bug_id>
          
          <creation_ts>2011-07-19 17:09:03 +0000</creation_ts>
          <short_desc>color ghosting on BeagleBoard xM rev C</short_desc>
          <delta_ts>2013-02-19 09:10:02 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>BSPs</product>
          <component>bsps-configuration</component>
          <version>1.0</version>
          <rep_platform>Beagleboard</rep_platform>
          <op_sys>arm</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>waiting for hardware (Mar 9, 2012)</status_whiteboard>
          <keywords></keywords>
          <priority>Low</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>1.4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Darren Hart">dvhart</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>corneliux.stoicescu</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>jingdong.lu</cc>
    
    <cc>sgw</cc>
    
    <cc>yi.zhao</cc>
    
    <cc>yp.bsp.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>14806</commentid>
    <comment_count>0</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-07-19 17:09:03 +0000</bug_when>
    <thetext>Quote from Jeff Mitchell&apos;s problem report to the yocto list:

&quot;
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&apos;t display these 
problems, so the setup should be fine.

I&apos;m not quite sure what is causing this. The resolution is also fairly 
low, and I haven&apos;t had any success using boot parameters (either the 
older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
&quot;

The terminal shows some red pixel noise along with cyan and white text overlapping eachother.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>15268</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2011-08-05 11:54:38 +0000</bug_when>
    <thetext>moving to accepted, but this is still pending triage by Darren.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>15565</commentid>
    <comment_count>2</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-08-18 14:42:32 +0000</bug_when>
    <thetext>Gary Thomas proposed a solution (kernel parameters) on a list. Jeff Mitchell was going to test, I haven&apos;t heard back in a few weeks though - we need to follow up with Jeff.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>15648</commentid>
    <comment_count>3</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2011-08-22 20:12:09 +0000</bug_when>
    <thetext>Darren: has anyone followed up on this ? We&apos;ve never seen this here.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>15709</commentid>
    <comment_count>4</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-08-24 13:46:46 +0000</bug_when>
    <thetext>Need someone with an xM rev C to test. I need to dig up Gary T&apos;s suggested kernel parameters.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16038</commentid>
    <comment_count>5</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-09-06 07:31:42 +0000</bug_when>
    <thetext>Gary T&apos;s suggested display parameters:

&quot;
I&apos;m not sure where it came from, but I was using this mode
    dvimode=1024x768MR-16@60
The MR part seems to be causing the most trouble.  What I use now
quite successfully is
    dvimode=1024x768-24@60

Note: this is parsed as
   WWxHH-DD@RR
     WW - display width in pixels
     HH - display height in pixels
     DD - pixel depth
     RR - video refresh rate
&quot;

Jeff is going to build and test, waiting on results.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>17789</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2011-12-21 11:25:45 +0000</bug_when>
    <thetext>Changing important, and release milestone. We still haven&apos;t reproduced this here, so we are largely waiting on this one to see if it has been addressed. 

We also have beagleboard 3.0 support that will be available soon, which would warrant a re-test.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>17944</commentid>
    <comment_count>7</comment_count>
    <who name="Jingdong Lu">jingdong.lu</who>
    <bug_when>2012-01-04 01:45:08 +0000</bug_when>
    <thetext>1.2_M1 RC2 20111213 build 
Tree/Branch: poky/1.2_M1
Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b
Board: Beagleboard C4
No such problem and display well.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>17952</commentid>
    <comment_count>8</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-01-04 06:41:59 +0000</bug_when>
    <thetext>The 3.0 kernel looks to address this, so I&apos;m marking this as resolved.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>18189</commentid>
    <comment_count>9</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-01-17 16:28:39 +0000</bug_when>
    <thetext>(In reply to comment #8)
&gt; The 3.0 kernel looks to address this, so I&apos;m marking this as resolved.

Are you basing that on comment #7?

(In reply to comment #7)
&gt; 1.2_M1 RC2 20111213 build 
&gt; Tree/Branch: poky/1.2_M1
&gt; Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b
&gt; Board: Beagleboard C4
&gt; No such problem and display well.

This suggests it was tested on Beagleboard C4. This is known to work. The bug was opened against the Beagleboard xM rev C (not the C4).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>18190</commentid>
    <comment_count>10</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-01-17 16:29:18 +0000</bug_when>
    <thetext>Please confirm this was tested on the Beagleboard xM rev C (not the Beagleboard C4).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>18191</commentid>
    <comment_count>11</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-01-17 16:29:31 +0000</bug_when>
    <thetext>.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>18946</commentid>
    <comment_count>12</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-03-09 15:48:04 +0000</bug_when>
    <thetext>C4 Boards ordered, but haven&apos;t arrived. Leaving as NEEDINFO as there is not a NEEDHW state.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>24100</commentid>
    <comment_count>13</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-08-16 12:02:51 +0000</bug_when>
    <thetext>(In reply to comment #12)
&gt; C4 Boards ordered, but haven&apos;t arrived. Leaving as NEEDINFO as there is not
&gt; a NEEDHW state.

Hi 
Are there any updates regarding this?

Thanks,
Alex.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>24104</commentid>
    <comment_count>14</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-08-16 14:28:12 +0000</bug_when>
    <thetext>No updates, as I still don&apos;t have a xM rev C. Checking directly with the
Wind River yocto QA team is the best way to see if h/w arrived there.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29765</commentid>
    <comment_count>15</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-02-13 15:02:14 +0000</bug_when>
    <thetext>Yi, can you please give us an update on this?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29941</commentid>
    <comment_count>16</comment_count>
    <who name="Yi Zhao">yi.zhao</who>
    <bug_when>2013-02-19 06:05:05 +0000</bug_when>
    <thetext>No such issue with recent builds.

Test env:
beagleboard xM rev C
HDMI to DVI-D cable (I don&apos;t have a HDMI to DVI adapter)
Dell P2311H LCD monitor


I think we could close this bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29950</commentid>
    <comment_count>17</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-02-19 09:09:36 +0000</bug_when>
    <thetext>Marking as RESOLVED as per previous comment.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>29951</commentid>
    <comment_count>18</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-02-19 09:10:02 +0000</bug_when>
    <thetext>Marking as VERIFIED as per previous comments.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>