Graphics driver on i.MX53 Android issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android |
Fix Released
|
Undecided
|
Bernhard Rosenkraenzer |
Bug Description
Booting Android on i.MX53 QSB using your bsp/freescale/
[...]
<7>[ 120.044524] DMFC high resolution has set, will not change
<7>[ 120.144532] DMFC high resolution has set, will not change
<7>[ 120.224553] DMFC high resolution has set, will not change
[...]
This error message comes from drivers/
_ipu_dmfc_init is called from _ipu_dmfc_
_ipu_dmfc_
through the IPU_INIT_
There doesn't seem to be a reasonable code path that could hit those
10+ times a second, but I haven't put a lot of time into debugging this
yet.
In my current builds, I've speeded it up by hiding the warning and avoiding the logging activity. We can now see the right picture, but any screen update (e.g. moving the mouse cursor, or automatic updates when e.g. running 0xbench) causes the screen to blank for a while (and then come back up showing what it should be showing, behaves pretty much like an e-ink display). My current guess is that any screen update causes the driver to re-initialize, causing both the message and the blanking.
visibility: | private → public |
Changed in linaro-landing-team-freescale: | |
assignee: | nobody → Haitao Zhang (minipanda) |
Changed in linaro-android: | |
assignee: | nobody → Bernhard Rosenkraenzer (berolinux) |
status: | New → Confirmed |
Changed in linaro-android: | |
status: | Fix Committed → Fix Released |
This is a critical bug. What's going on with it?