From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: vsync + vaapi question
Date: Wed, 23 Dec 2015 13:13:46 +0100 [thread overview]
Message-ID: <20151223121346.GY31063@ics.muni.cz> (raw)
In-Reply-To: <20151223120144.GQ5896@nuc-i3427.alporthouse.com>
On Wed, Dec 23, 2015 at 12:01:44PM +0000, Chris Wilson wrote:
> The clipped extents of the va-api Window is used to determine which CRTC
> to use as the vblank source. Hmm, the Primary Output is used as the
> preference (i.e. if any part of that Window is on the Primary, it is
> used as the CRTC - the idea being that Primary is important and this
> should share the vblank source for more Windows and prevent arbitrary
> jumps between vblank sources as the Window moves).
just tested, with xv output, vsync seems to be quite ok. however, with va-api
it not ok on both LVDS and HDMI. HDMI seems to be far worse with va-api (i.e.
out of sync). Maybe a bug in va-api sync code?
--
Lukáš Hejtmánek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-23 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 18:08 vsync + vaapi question Lukas Hejtmanek
2015-12-22 20:54 ` Chris Wilson
2015-12-22 22:25 ` Lukas Hejtmanek
2015-12-23 12:01 ` Chris Wilson
2015-12-23 12:13 ` Lukas Hejtmanek [this message]
2015-12-23 13:38 ` Chris Wilson
2015-12-24 9:44 ` Lukas Hejtmanek
2015-12-24 15:50 ` Chris Wilson
2015-12-24 19:28 ` Lukas Hejtmanek
2015-12-24 19:37 ` Chris Wilson
2015-12-24 19:42 ` Lukas Hejtmanek
2015-12-24 19:55 ` Chris Wilson
2015-12-24 19:59 ` Lukas Hejtmanek
2015-12-24 20:05 ` Chris Wilson
2015-12-24 22:15 ` Lukas Hejtmanek
2015-12-24 22:22 ` Chris Wilson
2015-12-24 22:25 ` Lukas Hejtmanek
2015-12-24 23:54 ` Robert Hooker
2015-12-26 15:40 ` Lukas Hejtmanek
2016-01-13 13:12 ` Lukas Hejtmanek
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=20151223121346.GY31063@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--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