DSS error messages during boot
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1. Boot the board
2. See output
What is the expected output? What do you see instead?
...
<3>omap-dss DISPC error: Requested pixel clock not possible with the
current OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.
<3>omap-dss DISPC error: Requested pixel clock not possible with the
current OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.
omap-dss DISPC error: Requested pixel clock not possible with the current
OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.
<4>omap-dss: Could not find exact pixel clock. Requested 25190 kHz, got
25189 kHz
<4>omap-dss: Could not find exact pixel clock. Requested 25190 kHz, got
25189 kHz
omap-dss: Could not find exact pixel clock. Requested 25190 kHz, got 25189 kHz
...
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `konstant...@gmail.com` on 29 Oct 2009 at 12:56
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the boot output in this issue and investigate the OMAP-DSS DISPC pixel-clock errors, including the OMAP2_DSS_MIN_FCK_PER_PCK constraint. Done means identifying the cause of the repeated messages and documenting or correcting the boot-time behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100