50Hz Display is not support
Nobody has claimed this yet.
- 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. Try to work with LCD/Plasma display which support 50Hz only
2.
3.
What is the expected output? What do you see instead?
trying to work with Plasma display which support 50Hz only cause the following
error in boot time:
omapfb omapfb: failed to allocate framebuffer
omapfb omapfb: failed to allocate fbmem
omapfb omapfb: failed to setup omapfb
omapfb: probe of omapfb failed with error -12
omaplfb: OMAPLFB_Init: OMAPLFBInit failed
request_suspend_state: wakeup (3->0) at 25539184573 (1970-01-01
00:00:25.539184573 UTC)
init: untracked pid 785 exited
What version of the product are you using? On what operating system?
I'm using BeagleBoard-xM rev A with the pre-build version of FROYO
Please provide any additional information below.
```
Original issue reported on code.google.com by `Eli.Roze...@gmail.com` on 18 Dec 2010 at 10:11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the omapfb and omaplfb framebuffer initialization reported in the boot log, and reproduce the failure on a BeagleBoard-xM with a 50Hz-only LCD or plasma display. Done means the display initializes successfully without the framebuffer allocation and probe errors shown in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, linux
- Domain
- computer-graphics, 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