Openmoko Bug #1315: xglamo: Performance decreases after a while
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Aug 18 09:26:48 CEST 2008
#1315: xglamo: Performance decreases after a while
----------------------------------------+-----------------------------------
Reporter: zecke at selfish.org | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: Xfbdev (kdrive), Xglamo | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------------------+-----------------------------------
Comment(by andy):
One thing about Glamo command queue code in kernel anyway, despite what
may be there it is not sync'd to anything that matters, the only element
of it that allows entry and exit from command queue mode "apparently OK"
is the big mdleay(100). I spent some time a few weeks ago trying to
optimize it to "wait for LCD ready" and "wait for command mode ready" but
nothing worked without the big mdelay.
So I would check the bit that says you are actually in command mode --
maybe this pretty random not-understood delay thing failed and that's
where the insanity about queue empty started.
Also, kernel won't take down engines randomly, only in suspend.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the devel
mailing list