Daniel Vetter <daniel@xxxxxxxx> writes: > Also if this confuses VR, then another reason why we want to make leases > invariant and only allow pure revoke, not changing the list. I'm not sure why you want this to be asymmetrical, nor why you would expect lessees to be any more competent at dealing with hotplug than the lessor. One use case already proposed for this API was to allow for multi-seat, where the lessee would be an existing window system, which we already accept as being incompetent at dealing with resource hotplug. I imagine that in this case, a newly plugged monitor would be detected by the multi-seat manager (logind?) and added to one of the existing leases, along with a suitable CRTC resource. For this to work, the lessee will need to already know about those resources and only have their connectivity status hidden. -- -keith
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
