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: Tue, 22 Dec 2015 23:25:53 +0100 [thread overview]
Message-ID: <20151222222553.GX31063@ics.muni.cz> (raw)
In-Reply-To: <20151222205408.GL5896@nuc-i3427.alporthouse.com>
On Tue, Dec 22, 2015 at 08:54:08PM +0000, Chris Wilson wrote:
> Not really. The Primary output will be used as the vsync so long as a
> single pixel of the Window is upon it. Fundamentally, we need to use the
> output that the Window is on in order to driver the vblank update.
Which window? Any window or the va-api window? In the latter case, it would be
quite ok to setup left-of instead of clone and move mplayer window solely to
the external monitor. Do I understand it correctly?
> Ville once upon a time mentioned plans to try and synchronise the
> vblanks on matched outputs, i.e. start two 60Hz monitors at precisely
> the same time so they remain reasonably in sync.
hmm, well, right now, LVDS is running on 60Hz while HDMI2 runs at 30Hz.
--
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-22 22:27 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 [this message]
2015-12-23 12:01 ` Chris Wilson
2015-12-23 12:13 ` Lukas Hejtmanek
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=20151222222553.GX31063@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 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.