Re: Split render/display SoCs, Mesa's renderonly, and Wayland dmabuf hints

On Tue, Apr 20, 2021 at 3:18 AM Daniel Stone wrote: > > Hi, > > On Mon, 19 Apr 2021 at 13:06, Simon Ser wrote: >> >> I'm working on a Wayland extension [1] that, among other things, allows >> compositors to advertise the preferred device to be used by Wayland >> clients. >> >> In general, composi

Re: Drag & Drop - multiple wl_data_device/wl_seat interfaces

Hi, On Tuesday, April 20th, 2021 at 2:51 PM, Martin Stransky wrote: > with Drag & Drop sometimes only one device gets the D&D events This sounds like a compositor bug. The events should be broadcast to all objects of the client that has focus for the wl_seat I think. Simon ___

Re: Split render/display SoCs, Mesa's renderonly, and Wayland dmabuf hints

Just 2 comments on the kernel aspects here. On Tue, Apr 20, 2021 at 12:18 PM Daniel Stone wrote: > > Hi, > > On Mon, 19 Apr 2021 at 13:06, Simon Ser wrote: >> >> I'm working on a Wayland extension [1] that, among other things, allows >> compositors to advertise the preferred device to be used by

Re: Split render/display SoCs, Mesa's renderonly, and Wayland dmabuf hints

Hi, On Mon, 19 Apr 2021 at 13:06, Simon Ser wrote: > I'm working on a Wayland extension [1] that, among other things, allows > compositors to advertise the preferred device to be used by Wayland > clients. > > In general, compositors will send a render node. However, in the case > of split rende