Re: [PATCH weston 01/12] shared: Add timespec_is_zero helper

2017-11-24 Thread Emil Velikov
Hi Alexandros, On 16 November 2017 at 16:20, Alexandros Frantzis wrote: > +ZUC_TEST(timespec_test, timespec_is_zero) > +{ > + struct timespec zero = { 0 }; > + struct timespec non_zero_sec = { 1, 0 }; > + struct timespec non_zero_nsec = { 0, 1 }; > + The standard (be that POSIX

Re: Screen dimensions, top level surface positioning...

2017-11-24 Thread Jari Vuomajoki
Hi Everyone! Thank you all for clear answers. I can understand the problematic of providing parallel solutions for several graphics environments... ...so here is the use-case I am puzzled with: I am implementing a desktop application consisting of several windows. I can create proper implementat

[PATCH weston v2 05/12] libweston: Use struct timespec for motion events

2017-11-24 Thread Alexandros Frantzis
Change code related to motion events to use struct timespec to represent time. This commit is part of a larger effort to transition the Weston codebase to struct timespec. Signed-off-by: Alexandros Frantzis --- Changes in v2: - Fix handle_pointer_motion_absolute to use the event time in mic

Re: [PATCH weston 12/12] libweston: Use struct timespec for compositor time

2017-11-24 Thread Pekka Paalanen
On Thu, 16 Nov 2017 18:21:01 +0200 Alexandros Frantzis wrote: > Change weston_compositor_get_time to return the current compositor time > as a struct timespec. Also, use clock_gettime (with CLOCK_REALTIME) to > get the time, since it's equivalent to the currently used gettimeofday > call, but ret

Re: [PATCH weston 05/12] libweston: Use struct timespec for motion events

2017-11-24 Thread Alexandros Frantzis
On Fri, Nov 24, 2017 at 03:29:11PM +0200, Pekka Paalanen wrote: > On Thu, 16 Nov 2017 18:20:54 +0200 > Alexandros Frantzis wrote: > > > Change code related to motion events to use struct timespec to represent > > time. > > > > This commit is part of a larger effort to transition the Weston codeb

Re: [PATCH weston 05/12] libweston: Use struct timespec for motion events

2017-11-24 Thread Pekka Paalanen
On Thu, 16 Nov 2017 18:20:54 +0200 Alexandros Frantzis wrote: > Change code related to motion events to use struct timespec to represent > time. > > This commit is part of a larger effort to transition the Weston codebase > to struct timespec. > > Signed-off-by: Alexandros Frantzis > --- > co

Re: [PATCH weston 04/12] libweston: Use struct timespec for the output presentation timestamp

2017-11-24 Thread Pekka Paalanen
On Thu, 16 Nov 2017 18:20:53 +0200 Alexandros Frantzis wrote: > Store the output presentation timestamp as struct timespec. > > This commit is part of a larger effort to transition the Weston codebase > to struct timespec. > > Signed-off-by: Alexandros Frantzis > --- > libweston/compositor.c

Re: [PATCH weston] ivi-shell: Fix incorrect use of logical instead of bitwise operator

2017-11-24 Thread Pekka Paalanen
On Tue, 21 Nov 2017 12:04:55 + "Ucan, Emre (ADITG/ESB)" wrote: > Hi, > > Thank you for the patch. It looks good to me. > > Reviewed-by: Emre Ucan Pushed: 71c4f70e..0343c6ac master -> master Thanks, pq pgpqRh5RLlutk.pgp Description: OpenPGP digital signature

Re: [RFC wayland] protocol: Add high-resolution wl_touch timestamp event

2017-11-24 Thread Pekka Paalanen
On Tue, 21 Nov 2017 15:45:48 +0200 Alexandros Frantzis wrote: > wl_touch events currently use a 32-bit timestamp with millisecond > resolution. In some cases, notably latency measurements, this resolution > is too coarse-grained to be useful. > > This protocol update adds a wl_touch.timestamp ev

Re: [RFC wayland] protocol: Add high-resolution wl_touch timestamp event

2017-11-24 Thread Pekka Paalanen
On Tue, 21 Nov 2017 18:20:08 +0200 Alexandros Frantzis wrote: > On Tue, Nov 21, 2017 at 10:52:00PM +0800, Jonas Ã…dahl wrote: > > On Tue, Nov 21, 2017 at 03:45:48PM +0200, Alexandros Frantzis wrote: > > > wl_touch events currently use a 32-bit timestamp with millisecond > > > resolution. In some