diff options
| author | Eric Anholt <[email protected]> | 2010-05-23 21:00:13 -0700 |
|---|---|---|
| committer | Eric Anholt <[email protected]> | 2010-05-26 12:13:54 -0700 |
| commit | 8f61114907669b2134fbdc1a794926035486e8df (patch) | |
| tree | 1874c6a80dfdd42327cb4ecc44f8f03a4b0ffb0e /src/mesa | |
| parent | 6e2330daa6d7872405485ffabfe613a7c053d890 (diff) | |
i965: Don't PIPE_CONTROL instruction cache flush.
This is a workaround for Ironlake errata. The emit_mi_flush is used
for a few purposes:
1) Flushing write caches for RTT (including blit to texture)
2) Pipe fencing for sync objects
3) Spamming cache flushes to track down cache flush bugs
Spamming cache flushes seems less important than following the docs,
and we should probably do that with a different mechanism than the one
for render cache flushes.
Diffstat (limited to 'src/mesa')
| -rw-r--r-- | src/mesa/drivers/dri/intel/intel_batchbuffer.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/mesa/drivers/dri/intel/intel_batchbuffer.c b/src/mesa/drivers/dri/intel/intel_batchbuffer.c index ca8e3448368..de5134008f2 100644 --- a/src/mesa/drivers/dri/intel/intel_batchbuffer.c +++ b/src/mesa/drivers/dri/intel/intel_batchbuffer.c @@ -278,7 +278,6 @@ intel_batchbuffer_emit_mi_flush(struct intel_batchbuffer *batch) if (intel->gen >= 4) { BEGIN_BATCH(4); OUT_BATCH(_3DSTATE_PIPE_CONTROL | - PIPE_CONTROL_INSTRUCTION_FLUSH | PIPE_CONTROL_WRITE_FLUSH | PIPE_CONTROL_NO_WRITE); OUT_BATCH(0); /* write address */ |