Daniel Vetter <daniel@xxxxxxxx> writes: > One more that came up on irc after discussion why this is needed: The > userspace side using this won't work on split gpus where the render node > has 0 displays, and hence where you really need to query the compositor > anyway. Agreed -- using the X connection to get the information should let this work on split systems. Within the Vulkan code, I already have to move objects from the render node to the display node. Hrm. That exposes a weakness in the kms_display extension I've proposed; that only allows you to pass a single fd. Passing separate display and render fds through that interface seems like a pretty useful change. -- -keith
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
