On Wed, Apr 13, 2016 at 11:11:54AM +0300, Pekka Paalanen wrote: > From: Pekka Paalanen <pekka.paala...@collabora.co.uk> > > Associates better with the surrounding paragraphs by not jumping topics > back and forth. > > Suggested-by: Bill Spitzak <spit...@gmail.com> > Signed-off-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
For all four patches: Reviewed-by: Bryce Harrington <br...@osg.samsung.com> > --- > stable/presentation-time/presentation-time.xml | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/stable/presentation-time/presentation-time.xml > b/stable/presentation-time/presentation-time.xml > index dc4ae68..6c3fff8 100644 > --- a/stable/presentation-time/presentation-time.xml > +++ b/stable/presentation-time/presentation-time.xml > @@ -232,6 +232,10 @@ > targeting the next few vblanks. If such prediction cannot > usefully be done, the argument is zero. > > + If the output does not have a constant refresh rate, explicit > + video mode switches excluded, then the refresh argument must > + be zero. > + > The 64-bit value combined from seq_hi and seq_lo is the value > of the output's vertical retrace counter when the content > update was first scanned out to the display. This value must > @@ -240,10 +244,6 @@ > path has a non-zero latency, the time instant specified by > this counter may differ from the timestamp's. > > - If the output does not have a constant refresh rate, explicit > - video mode switches excluded, then the refresh argument must > - be zero. > - > If the output does not have a concept of vertical retrace or a > refresh cycle, or the output device is self-refreshing without > a way to query the refresh count, then the arguments seq_hi > -- > 2.7.3 _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
