[ANNOUNCE] wayland-protocols 1.17

2018-11-12 Thread Jonas Ã…dahl
wayland-protocols 1.17 is now available. This versions include two new unstable protocols: linux-explicit-synchronization - A Linux specific mechanism for explicit per-surface buffer synchronization. primary-selection - A clipboard like mechanism mimicking primary selection on X11, commonly know

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Philipp Zabel
Hi Simon, On Fri, 2018-11-02 at 18:49 +, Simon Ser wrote: > On Friday, November 2, 2018 12:30 PM, Philipp Zabel > wrote: > > > > + > > > > + > > > > +This event advertizes the primary device that the server > > > > prefers. There > > > > +is exactly one primary dev

[PATCH wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_hints

2018-11-12 Thread Simon Ser
On multi-GPU setups, multiple devices can be used for rendering. Clients need hints about the device in use by the compositor. For instance, if they render on another GPU, then they need to make sure the memory is accessible between devices and that their buffers are not placed in hidden memory. T

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-12 Thread Pekka Paalanen
On Mon, 12 Nov 2018 11:15:25 + Daniel Stone wrote: > On Fri, 9 Nov 2018 at 10:48, Pekka Paalanen wrote: > > I can add that while pushing upstream, if there are no other changes > > coming. > > > > Reviewed-by: Pekka Paalanen > > > > You have ensured that the C files generated from this revi

Wayland intermediate sized data transfer

2018-11-12 Thread Pekka Paalanen
On Mon, 12 Nov 2018 14:48:19 +0200 Pekka Paalanen wrote: > Quite likely we need to revisit this in any case. Using shared memory > feels complicated, but OTOH it *is* relatively lot of data. Even the > kernel UABI does not use a flat list of format+modifier but a fairly > "interesting" bitfield e

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Pekka Paalanen
On Mon, 12 Nov 2018 12:16:04 + Simon Ser wrote: > On Monday, November 12, 2018 10:18 AM, Pekka Paalanen > wrote: > > On Sat, 10 Nov 2018 13:34:31 + > > Simon Ser wrote: > > > > > On Monday, November 5, 2018 9:57 AM, Pekka Paalanen > > > wrote: > > > > > > Yeah. Another option is

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-12 Thread Tomek Bury
HI Daniel, Where can I find the work-in-progress implementation? I'd like to try it out with Broadcom driver which doesn't have implicit cross-process sync. I can add the explicit sync protocol implementation on the driver side but I'd need a reference to test it against. Cheers, Tomek On Mon, N

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Simon Ser
On Monday, November 12, 2018 10:18 AM, Pekka Paalanen wrote: > On Sat, 10 Nov 2018 13:34:31 + > Simon Ser wrote: > > > On Monday, November 5, 2018 9:57 AM, Pekka Paalanen > > wrote: > > > > > Yeah. Another option is to send a wl_array of modifiers per format and > > > > > tranch. > > > > >

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Pekka Paalanen
On Mon, 12 Nov 2018 10:13:39 + Simon Ser wrote: > On Monday, November 12, 2018 10:14 AM, Pekka Paalanen > wrote: > > > * Create a wl_surface, get the hints, and destroy everything (without > > > mapping > > > the surface) > > > * Allow the get_surface_hints to take a NULL surface > > > *

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-12 Thread Alexandros Frantzis
On Fri, Nov 09, 2018 at 04:24:56PM +0200, Alexandros Frantzis wrote: > On Fri, Nov 09, 2018 at 12:48:09PM +0200, Pekka Paalanen wrote: > > On Fri, 9 Nov 2018 09:46:36 +0200 > > Alexandros Frantzis wrote: > > > > > Signed-off-by: Alexandros Frantzis > > > > Hi Alf, > > Hi Pekka, > > thanks fo

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-12 Thread Daniel Stone
On Fri, 9 Nov 2018 at 10:48, Pekka Paalanen wrote: > I can add that while pushing upstream, if there are no other changes > coming. > > Reviewed-by: Pekka Paalanen > > You have ensured that the C files generated from this revision build > fine in Weston, right? > > David, Daniel, since your name

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Simon Ser
On Monday, November 12, 2018 10:14 AM, Pekka Paalanen wrote: > > * Create a wl_surface, get the hints, and destroy everything (without > > mapping > > the surface) > > * Allow the get_surface_hints to take a NULL surface > > * Add a get_hints request without a wl_surface argument > > * Forget

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Pekka Paalanen
On Sat, 10 Nov 2018 13:34:31 + Simon Ser wrote: > On Monday, November 5, 2018 9:57 AM, Pekka Paalanen > wrote: > > > > Yeah. Another option is to send a wl_array of modifiers per format and > > > > tranch. > > > > > > True. Any reason why this hasn't been done in the global? > > > > For

Re: [PATCH RFC wayland-protocols] unstable/linux-dmabuf: add wp_linux_dmabuf_device_hint

2018-11-12 Thread Pekka Paalanen
On Sat, 10 Nov 2018 13:54:19 + Simon Ser wrote: > Just a general update about this: I tried to see how we could make Mesa use > this > new protocol. > > A bad news is that the DRM FD is per-EGLDisplay and I think it would require > quite some changes to make it per-EGLSurface. I'm still new