summaryrefslogtreecommitdiff
path: root/src/glamo-cmdq.c
diff options
context:
space:
mode:
authorLars-Peter Clausen <lars@metafoo.de>2009-05-05 01:07:10 +0200
committerLars-Peter Clausen <lars@metafoo.de>2009-05-05 01:07:10 +0200
commit9491d818583114e429db1330dc5e07b4668dfa35 (patch)
tree703d16fa66f5d4a36ae92dae852fbcd5b8a4ee49 /src/glamo-cmdq.c
parent20bb485f4a27c16b6faaf8a2ebc6067480889c50 (diff)
Only waiting for the cmdq engine to be finished when dispatching the queue
causes visual artifactes sometimes. Waiting for all engines to be finished seems to fix the issue.
Diffstat (limited to 'src/glamo-cmdq.c')
-rw-r--r--src/glamo-cmdq.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/glamo-cmdq.c b/src/glamo-cmdq.c
index f423aae..38950d7 100644
--- a/src/glamo-cmdq.c
+++ b/src/glamo-cmdq.c
@@ -120,7 +120,9 @@ GLAMODispatchCMDQ(GlamoPtr pGlamo)
} else {
memcpy(pGlamo->ring_addr + ring_write, addr, count);
}
- GLAMOEngineWait(pGlamo, GLAMO_ENGINE_CMDQ);
+ /* In Theory waiting for the CMDQ to be ready should be enough, but
+ * unfortunally this causes visual artifacts sometimes */
+ GLAMOEngineWait(pGlamo, GLAMO_ENGINE_ALL);
MMIOSetBitMask(mmio, GLAMO_REG_CLOCK_2D,
GLAMO_CLOCK_2D_EN_M6CLK,
0);