From: Alexey Fisher <bug-track@fisher-privat.net>
To: intel-gfx@lists.freedesktop.org
Subject: [regression] drm/i915: Flush pending writes on i830/i845 after updating GTT
Date: Thu, 30 Dec 2010 10:36:35 +0100 [thread overview]
Message-ID: <1293701795.5595.7.camel@zwerg> (raw)
Hi,
after this patch i get some rendering issues on my Intel DG45ID board,
(Vendor: 0x8086, Device: 0x2e22, Revision: 0x03 (A3))
removing this lines fix it:
diff --git a/drivers/gpu/drm/i915/i915_gem.c
b/drivers/gpu/drm/i915/i915_gem.c
index cecaa07..3a12cbf 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -2148,8 +2148,8 @@ i915_gem_flush_ring(struct drm_device *dev,
uint32_t invalidate_domains,
uint32_t flush_domains)
{
- if (list_empty(&ring->gpu_write_list))
- return;
+// if (list_empty(&ring->gpu_write_list))
+// return;
ring->flush(ring, invalidate_domains, flush_domains);
i915_gem_process_flushing_list(dev, flush_domains, ring);
commit 15056d2c06862627ead868e035fcacc59dce1b1a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Tue Dec 21 17:04:23 2010 +0000
drm/i915: Flush pending writes on i830/i845 after updating GTT
There is an erratum on these two chipsets that causes the wrong PTE
entries to be invalidate after updating the GTT and when used from the
BLT engine. The workaround is to flush any pending writes before those
PTEs are used by the BLT.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
--
Regards,
Alexey
next reply other threads:[~2010-12-30 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 9:36 Alexey Fisher [this message]
2010-12-30 9:51 ` [regression] drm/i915: Flush pending writes on i830/i845 after updating GTT Chris Wilson
2010-12-30 10:09 ` Alexey Fisher
2010-12-30 10:31 ` Chris Wilson
2010-12-30 11:23 ` Alexey Fisher
2010-12-30 18:06 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1293701795.5595.7.camel@zwerg \
--to=bug-track@fisher-privat.net \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox