summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2008-10-09 14:29:04 -0700
committerJesse Barnes <jbarnes@virtuousgeek.org>2008-11-11 12:22:38 -0800
commit6f3bfebaaf8017d6bee244e945a1c7d2b1400e71 (patch)
tree7c6d4601001e6e55ec23776dba05efcb76992ef2
parentfc66fbbb37da86f02bc3beff30bf0630a03a9e10 (diff)
Disable frame buffer compression by default for GM965.
We haven't found a way to make FBC work reliably with GM965 yet, (it often fails to notice CPU writes). This appears to be a specific problem with this device, (as we haven't gotten similar bug reports for subsequent devices such as GM45). So FBC is now disabled by default for GM965 but can still be enabled with the FrameBufferCompression option for experimenting/debugging. This resolves bug #16257: [GM965 EXA] Frame-buffer compression broken for CPU writes (XPutImage) https://bugs.freedesktop.org/show_bug.cgi?id=16257
-rw-r--r--src/i830.h7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/i830.h b/src/i830.h
index 6a5de6bc..b2e339a0 100644
--- a/src/i830.h
+++ b/src/i830.h
@@ -887,6 +887,13 @@ static inline int i830_fb_compression_supported(I830Ptr pI830)
*/
if (!pI830->tiling || (IS_I965G(pI830) && !pI830->useEXA))
return FALSE;
+ /* We have not gotten FBC to work consistently on 965GM. Our best
+ * working theory right now is that FBC simply isn't reliable on
+ * that device. See this bug report for more details:
+ * https://bugs.freedesktop.org/show_bug.cgi?id=16257
+ */
+ if (IS_I965GM(pI830))
+ return FALSE;
return TRUE;
}