Hi Rob, just checking on the status on the patch set. Do you plan to
send a revised series or commit them as-is? I ask because my i965
patches depend on your patches 1-4, and I'm trying to decide to when to
resend them.

On Fri 18 Nov 2016, Rob Clark wrote:
> This patchset implements support for EGL_ANDROID_native_fence_sync[1]
> for egl and gallium.  This extension provides support for native fence
> fd's (file descriptors) for the GPU.  In a similar way to dma-buf fd's,
> which provide a reference-counted userspace handle to buffers which
> can be shared across drivers and across processes, native fence fd's
> provide a reference-counted userspace handle to fences which can be
> shared across drivers and across processes.
> This extension is already in use on android, and should be useful in
> other environments.
> Patch 04/10 has some fixes from Chad squashed in, as well as a couple
> fixes for issues that Rafael found while writing piglit tests.
> The kernel patches for freedreno (drm/msm) are upstream (v4.9) and the
> libdrm patches are in v2.4.72.  Kernel patches for drm/virtio are in
> flight (so corresponding gallium patch is not ready to push).  Kernel
> plus libdrm plus mesa patches for i965 are in flight.
> This has been tested on piglit[2] (i965, freedreno), kmscube[3] (virgl,
> freedreno), and drm-hwc2[4] (virgl, freedreno).
> [1] 
> https://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_native_fence_sync.txt
> [2] https://patchwork.freedesktop.org/series/14498/
> [3] https://github.com/robclark/kmscube/commits/atomic-fence
> [4] 
> https://git.collabora.com/cgit/user/robertfoss/drm_hwcomposer.git/log/?h=hwc2_fence_v2
mesa-dev mailing list

Reply via email to