Stefan Schake stschake@gmail.com writes:
v2 drops the extra syncobj parameter and gets rid of the submit flags since 0 is never a valid syncobj handle.
This series allows userspace to submit syncobj handles for importing a fence to wait on or exporting the job fence as part of submission.
The primary use of this is to enable native fence fd support in Mesa. Userspace implementation is under review and available here:
This series was a joy to read. I've reviewed and pushed it to drm-misc-next, and we can land the Mesa side once it's made its way to drm-next.