On Thu, 18 Jan 2018 15:13:53 +
Daniel Stone wrote:
> Hi,
>
> On 18 January 2018 at 14:37, Pekka Paalanen wrote:
> > On Wed, 20 Dec 2017 16:21:32 +0200
> > Alexandros Frantzis wrote:
> >> a heads-up that I have
Hi,
On 18 January 2018 at 14:37, Pekka Paalanen wrote:
> On Wed, 20 Dec 2017 16:21:32 +0200
> Alexandros Frantzis wrote:
>> a heads-up that I have posted the libweston input-timestamps patchset
>> for review at:
>>
>>
On Wed, 20 Dec 2017 16:21:32 +0200
Alexandros Frantzis wrote:
> On Tue, Dec 19, 2017 at 01:06:11PM +0200, Alexandros Frantzis wrote:
> > On Tue, Dec 19, 2017 at 10:15:06AM +0200, Pekka Paalanen wrote:
> > > On Mon, 18 Dec 2017 14:55:00 +0200
> > > Alexandros
On Tue, Dec 19, 2017 at 01:06:11PM +0200, Alexandros Frantzis wrote:
> On Tue, Dec 19, 2017 at 10:15:06AM +0200, Pekka Paalanen wrote:
> > On Mon, 18 Dec 2017 14:55:00 +0200
> > Alexandros Frantzis wrote:
> >
> > > wl_pointer, wl_keyboard and wl_touch events
On Tue, Dec 19, 2017 at 10:15:06AM +0200, Pekka Paalanen wrote:
> On Mon, 18 Dec 2017 14:55:00 +0200
> Alexandros Frantzis wrote:
>
> > wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit
> > timestamp with millisecond resolution. In some cases,
On Mon, 18 Dec 2017 14:55:00 +0200
Alexandros Frantzis wrote:
> wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit
> timestamp with millisecond resolution. In some cases, notably latency
> measurements, this resolution is too coarse to be
wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit
timestamp with millisecond resolution. In some cases, notably latency
measurements, this resolution is too coarse to be useful.
This protocol provides additional high-resolution timestamps events,
which are emitted before the