Daniel Vetter <daniel@xxxxxxxx> writes: > So given the huge possibilities of abuse, do we really, really need all > this, and is there not any way to create a bit of protocol to pass the > relevant data from X to clients? From your presentation is sounded like > current xrandr is (almost) there ... Yeah, it's the Vulkan EXT_acquire_xlib_display API which is using this access to discover the set of resources available via the render fd in preparation for accessing them over the lease fd once the lease has been created. I *think* I can get enough information to make a good guess as to what kernel resources there are from the RandR info. I'll go give that a try and see if I get stuck. Thanks for the feedback; the fewer kernel API changes the better. -- -keith
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
