From: Kenneth Graunke <kenneth@whitecape.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: use BLT ring for flips on IVB
Date: Tue, 14 Jun 2011 00:29:08 -0700 [thread overview]
Message-ID: <4DF70DC4.1060801@whitecape.org> (raw)
In-Reply-To: <f80fcd$guqsv@fmsmga001.fm.intel.com>
On 06/13/2011 03:22 PM, Chris Wilson wrote:
> On Tue, 14 Jun 2011 00:14:11 -0700, Kenneth Graunke<kenneth@whitecape.org> wrote:
>> On 06/09/2011 12:14 PM, Jesse Barnes wrote:
>>> Found a couple more problems:
>>> 1) MI_DISPLAY_FLIP should take a '1' in the last byte to indicate
>>> length on IVB
>>> 2) apprently only the BLT ring version of the command actually causes
>>> interrupts to be generated
>>>
>>> With this patch, modetest -v works on my test platform. Clearly it's in
>>> need of more splitting though. The case statement should be split into
>>> per-chipset flip command generation.
>>>
>>> Signed-off-by: Jesse Barnes<jbarnes@virtuousgeek.org>
>>
>> Reviewed-and-tested-by: Kenneth Graunke<kenneth@whitecape.org>
>
> But it's not the neatest patch in the world ;-)
True :)
> Using struct intel_ring_buffer *ring for all generation and switching
> between blt/render on demand should be neater. Also we should be able
> to do pageflips from either the render or blt ring on gen7, right? That
> will be useful to avoid a synchronisation point.
> -Chris
I thought so, from reading the docs. But it doesn't seem to work from
the render ring...
--Kenneth
next prev parent reply other threads:[~2011-06-13 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 19:14 [PATCH] drm/i915: use BLT ring for flips on IVB Jesse Barnes
2011-06-14 7:14 ` Kenneth Graunke
2011-06-13 22:22 ` Chris Wilson
2011-06-14 7:29 ` Kenneth Graunke [this message]
2011-06-13 23:00 ` Jesse Barnes
2011-06-14 7:40 ` 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=4DF70DC4.1060801@whitecape.org \
--to=kenneth@whitecape.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox