public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jamey Sharp <jamey@minilop.net>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, Theo Hill <Theo0x48@gmail.com>,
	Eric Anholt <eric@anholt.net>
Subject: Re: [PATCH v2] UXA: Wait until a pageflip actually completes to report it.
Date: Wed, 21 May 2014 09:30:15 -0700	[thread overview]
Message-ID: <20140521163015.GA20056@minilop.net> (raw)
In-Reply-To: <20140521162418.GB28410@nuc-i3427.alporthouse.com>


[-- Attachment #1.1: Type: text/plain, Size: 638 bytes --]

On Wed, May 21, 2014 at 05:24:18PM +0100, Chris Wilson wrote:
> On Wed, May 21, 2014 at 08:53:18AM -0700, Jamey Sharp wrote:
> > Please merge this patch, which fixes two spec violations that make
> > OML_sync_control unusable; and if you're concerned about uncomposited
> > triple-buffering in UXA, please find a less awful way to get it.
> 
> Why not just change the default to double buffering? Or fix it
> correctly?

This patch *is* fixing it correctly. I don't understand the buffer
management well enough to implement triple buffering in your driver
though, sorry; all I know is that what's there now isn't it.

Jamey

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 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

      reply	other threads:[~2014-05-21 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 15:53 [PATCH v2] UXA: Wait until a pageflip actually completes to report it Jamey Sharp
2014-05-21 16:24 ` Chris Wilson
2014-05-21 16:30   ` Jamey Sharp [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=20140521163015.GA20056@minilop.net \
    --to=jamey@minilop.net \
    --cc=Theo0x48@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=eric@anholt.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