From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: fix up semaphore_waits_for
Date: Tue, 25 Mar 2014 16:24:08 +0100 [thread overview]
Message-ID: <CAKMK7uHW-Y5Te-HLX2aRYwB+zFpu=TtRNrV4VXH+gFrswR-Vuw@mail.gmail.com> (raw)
In-Reply-To: <20140325145408.GA777@bwidawsk.net>
On Tue, Mar 25, 2014 at 3:54 PM, Ben Widawsky <ben@bwidawsk.net> wrote:
> I don't think it's quite that easy, but I took it as a, "yes." Which one
> is patch 3?
"drm/i915: make semaphore signaller detection more robust" - it was a
follow-up patch in this thread, hence no 3/3. If the relevant bits on
bdw have moved out of the the cmd dword I guess we need to keep a
cache of the relevant dword and supply it to the function. Was too
lazy to check that though.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-03-25 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 23:08 [PATCH 1/2] drm/i915: fix up semaphore_waits_for Daniel Vetter
2014-03-14 23:08 ` [PATCH 2/2] drm/i915: Add FIXME for bdw semaphore detection in hancheck Daniel Vetter
2014-03-15 0:38 ` Ben Widawsky
2014-03-15 11:44 ` Daniel Vetter
2014-03-18 9:26 ` [PATCH] drm/i915: make semaphore signaller detection more robust Daniel Vetter
2014-03-19 15:05 ` Chris Wilson
2014-03-19 15:35 ` Daniel Vetter
2014-03-15 15:46 ` [PATCH 1/2] drm/i915: fix up semaphore_waits_for Chris Wilson
2014-03-15 16:31 ` Daniel Vetter
2014-03-15 23:13 ` Chris Wilson
2014-03-21 17:33 ` Mika Kuoppala
2014-03-22 17:52 ` Daniel Vetter
2014-03-24 22:37 ` Ben Widawsky
2014-03-25 9:42 ` Daniel Vetter
2014-03-25 14:54 ` Ben Widawsky
2014-03-25 15:24 ` Daniel Vetter [this message]
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='CAKMK7uHW-Y5Te-HLX2aRYwB+zFpu=TtRNrV4VXH+gFrswR-Vuw@mail.gmail.com' \
--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 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.