Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: ILK also needs that last fix
Date: Tue, 16 Oct 2012 09:16:23 +0200	[thread overview]
Message-ID: <20121016071623.GD5753@phenom.ffwll.local> (raw)
In-Reply-To: <20121015202141.00007429@unknown>

On Mon, Oct 15, 2012 at 08:21:41PM -0700, Ben Widawsky wrote:
> On Mon, 15 Oct 2012 20:59:22 +0200
> Daniel Vetter <daniel@ffwll.ch> wrote:
> 
> > On Wed, Oct 03, 2012 at 07:34:23PM -0700, Ben Widawsky wrote:
> > > That fix was the disable render deptch cache pipeline flush
> > > 
> > > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > 
> > I've stumbled over the same one, but my docs here suggest i965g/gm45
> > need it, too:
> > 
> > http://cgit.freedesktop.org/~danvet/drm/commit/?h=ilk-wa-pile&id=37c4c82b8cdbcf5adccad97f0b45747ba37ed659
> > 
> > Have you checked whether we don't need this on ivb/vlv/hsw, too?
> 
> I did check whether the windows driver does it for those platforms, and
> the answer is no. So the answer to your question is maybe because who
> knows what exists in some other doc somewhere in the metaverse. I think
> this is a good enough start though since it seems SNB was definitely a
> bit buggier than IVB.

Yeah, I've noticed while checking w/as that they're not consistently named
on older platforms. E.g. the above definitely exists on eaglelake, too,
but named slightly different. So the w/a db doesn't pick up all uses.
Hoooray!

> > Also, for w/a patches based on the vpg w/a database, please include
> > the vpg w/a name tag both in the commit message and in a code comment
> > somewhere.
> 
> Good idea. If you're okay with longer commit message subjects, I'd even
> suggest putting it there to make it even a bit easier to search for.

Yeah, I'm fine with putting it into the commit head, I've put it there
myself. If the w/a only affects one platform we could try to squeeze the
platform name into the headline, too. But having to read the commit
message for that doesn't really hurt, either.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2012-10-16  7:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04  2:34 [PATCH 1/4] drm/i915: Remove duplicate cache workaround Ben Widawsky
2012-10-04  2:34 ` [PATCH 2/4] drm/i915: Disable render depth cache pipeline flush Ben Widawsky
2012-10-04  2:34 ` [PATCH 3/4] drm/i915: ILK also needs that last fix Ben Widawsky
2012-10-15 18:59   ` Daniel Vetter
2012-10-16  3:21     ` Ben Widawsky
2012-10-16  7:16       ` Daniel Vetter [this message]
2012-10-04  2:34 ` [PATCH 4/4] drm/i915: Fix GT_MODE default value Ben Widawsky
2012-10-04 11:25   ` Daniel Vetter
2012-10-04  7:01 ` [PATCH 1/4] drm/i915: Remove duplicate cache workaround Daniel Vetter
2012-10-04 14:55   ` Ben Widawsky
2012-10-05  0:14   ` Ben Widawsky

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=20121016071623.GD5753@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.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