From: Daniel Vetter <daniel@ffwll.ch>
To: Indan Zupancic <indan@nul.nu>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Date: Sun, 20 Feb 2011 11:55:15 +0100 [thread overview]
Message-ID: <20110220105514.GB3514@viiv.ffwll.ch> (raw)
In-Reply-To: <92f5b87a3559ed7f1b7c46b7497c1ad5.squirrel@webmail.greenhost.nl>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Hi,
On Sun, Feb 20, 2011 at 03:20:15AM +0100, Indan Zupancic wrote:
> > I've created two quick patches to check a few theories, please test them
> > (both patches independently and both together). Patches attached.
>
> Tried with both applied, doesn't change anything.
I've just noticed that one of the patches (the 2nd one) doesn't work as
advertised. Please retest with the attached one.
Yours, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
[-- Attachment #2: for-indan-2.patch --]
[-- Type: text/x-diff, Size: 453 bytes --]
diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
index 17bd766..d275c96 100644
--- a/drivers/gpu/drm/i915/i915_dma.c
+++ b/drivers/gpu/drm/i915/i915_dma.c
@@ -762,9 +762,6 @@ static int i915_getparam(struct drm_device *dev, void *data,
case I915_PARAM_HAS_BLT:
value = HAS_BLT(dev);
break;
- case I915_PARAM_HAS_RELAXED_FENCING:
- value = 1;
- break;
case I915_PARAM_HAS_COHERENT_RINGS:
value = 1;
break;
next prev parent reply other threads:[~2011-02-20 10:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 5:58 Indan Zupancic
2011-02-19 18:25 ` Daniel Vetter
2011-02-20 2:20 ` Indan Zupancic
2011-02-20 2:26 ` Indan Zupancic
2011-02-20 9:20 ` Daniel Vetter
2011-02-20 11:02 ` Indan Zupancic
2011-02-20 10:55 ` Daniel Vetter [this message]
2011-02-20 11:19 ` Indan Zupancic
2011-02-20 13:21 ` Daniel Vetter
2011-02-21 1:11 ` Indan Zupancic
[not found] ` <1298395549-4064-1-git-send-email-daniel.vetter@ffwll.ch>
[not found] ` <ed85db84d2d5ea460898d78e1179c6ca.squirrel@webmail.greenhost.nl>
2011-02-23 7:10 ` [PATCH] drm/i915: fix corruptions on i8xx due to relaxed fencing Daniel Vetter
2011-03-10 5:06 ` Indan Zupancic
2011-03-10 7:52 ` Daniel Vetter
2011-03-10 10:36 ` Indan Zupancic
2011-03-10 13:31 ` Daniel Vetter
2011-03-11 1:08 ` Indan Zupancic
2011-03-11 9:23 ` Daniel Vetter
2011-02-21 2:51 ` [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb Indan Zupancic
2011-02-20 3:51 ` Peter Stuge
2011-02-20 6:13 ` Indan Zupancic
2011-02-21 4:10 ` Peter Stuge
2011-02-21 5:26 ` Indan Zupancic
2011-02-22 3:25 Indan Zupancic
2011-02-22 3:39 ` Indan Zupancic
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=20110220105514.GB3514@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®