From: Eric Anholt <eric@anholt.net>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake.
Date: Mon, 08 Nov 2010 00:19:11 -0800 [thread overview]
Message-ID: <87d3qgdy80.fsf@pollan.anholt.net> (raw)
In-Reply-To: <5b55a1$ij95do@fmsmga002.fm.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 555 bytes --]
On Sat, 06 Nov 2010 22:07:40 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sat, 6 Nov 2010 14:53:32 -0700, Eric Anholt <eric@anholt.net> wrote:
> > This is not known to fix any particular bugs we have, but the spec
> > says to do it, and the BIOS hadn't already set it up on my system.
>
> Whilst you haven't directly identified any bug caused by these two,
> adhering to the spec sounds like a stability fix. Worth applying to -fixes
> and CC'ing stable?
> -Chris
I'd rather not unless we find that it does really fix someone.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-11-08 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 21:53 [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake Eric Anholt
2010-11-06 21:53 ` [PATCH 2/2] drm/i915: Apply display workaround required according to the B-Spec Eric Anholt
2010-11-07 11:55 ` Chris Wilson
2010-11-06 22:07 ` [PATCH 1/2] drm/i915: Apply B-spec mandated workaround for read flushes on Ironlake Chris Wilson
2010-11-08 8:19 ` Eric Anholt [this message]
2010-11-08 9:19 ` 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=87d3qgdy80.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.