| Summary: | color ghosting on BeagleBoard xM rev C | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Darren Hart <dvhart> |
| Component: | bsps-configuration | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | alexandru.c.georgescu, corneliux.stoicescu, jessica.zhang, jingdong.lu, sgw, yi.zhao, yp.bsp.watcher, yp.watcher |
| Version: | 1.0 | ||
| Target Milestone: | 1.4 | ||
| Hardware: | Beagleboard | ||
| OS: | arm | ||
| Whiteboard: | waiting for hardware (Mar 9, 2012) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2011-07-19 17:09:03 UTC
moving to accepted, but this is still pending triage by Darren. Gary Thomas proposed a solution (kernel parameters) on a list. Jeff Mitchell was going to test, I haven't heard back in a few weeks though - we need to follow up with Jeff. Darren: has anyone followed up on this ? We've never seen this here. Need someone with an xM rev C to test. I need to dig up Gary T's suggested kernel parameters. Gary T's suggested display parameters:
"
I'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
"
Jeff is going to build and test, waiting on results.
Changing important, and release milestone. We still haven'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. 1.2_M1 RC2 20111213 build Tree/Branch: poky/1.2_M1 Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b Board: Beagleboard C4 No such problem and display well. The 3.0 kernel looks to address this, so I'm marking this as resolved. (In reply to comment #8) > The 3.0 kernel looks to address this, so I'm marking this as resolved. Are you basing that on comment #7? (In reply to comment #7) > 1.2_M1 RC2 20111213 build > Tree/Branch: poky/1.2_M1 > Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b > Board: Beagleboard C4 > 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). Please confirm this was tested on the Beagleboard xM rev C (not the Beagleboard C4). . C4 Boards ordered, but haven't arrived. Leaving as NEEDINFO as there is not a NEEDHW state. (In reply to comment #12) > C4 Boards ordered, but haven't arrived. Leaving as NEEDINFO as there is not > a NEEDHW state. Hi Are there any updates regarding this? Thanks, Alex. No updates, as I still don'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. Yi, can you please give us an update on this? No such issue with recent builds. Test env: beagleboard xM rev C HDMI to DVI-D cable (I don't have a HDMI to DVI adapter) Dell P2311H LCD monitor I think we could close this bug. Marking as RESOLVED as per previous comment. Marking as VERIFIED as per previous comments. |