[PATCH v6] unstable/drm-lease: DRM lease protocol support

Drew DeVault sir at cmpwn.com
Mon Sep 16 16:00:01 UTC 2019

On Mon Sep 16, 2019 at 11:57 AM Pekka Paalanen wrote:
> > Or, simplifying things, we could send them that non-master fd and then
> > they can just query it themselves and match the resources by their IDs
> > with the resources offered for lease by the compositor. I'm not sure why
> > constraining the resources they can browse (read-only) is necessary. We
> > could drop the EDID if we went with this approach.
> My only reason is that it would be obvious which resources the
> compositor will not lease out. If the resource picking in the client is
> automatic, that's not a big deal. But if the client has some UI to let
> the user pick a connector, it might be useful. Or, we need accompanying
> Wayland events to carry the leasability, but they could be as simple as
> device/drm-resource-id and nothing more.

I think for this to work we'd want to keep the event which shares the
object IDs available for lease.

More information about the wayland-devel mailing list