linux-dmabuf and eglBindWaylandDisplayWl

Matt Hoosier matt.hoosier at
Thu Apr 9 19:42:17 UTC 2020


Historically, many EGL implementations have registered a private wl_drm
buffer factory for use internally by the implementation's Wayland backend,
as part of the setup work done go eglBindWaylandDisplayWl().

Separately, compositors have started to implement explicit support for the
zwp_linux_dmabuf_v1 buffer factory, independent of the GPU backend.

If I remember correctly, I've read various messages on the list here saying
that eventually it would be preferred for EGL implementations would just
use linux-dmabuf as their buffer factory. That would mean that EGL backends
would now also want to register a zwp_linux_dmabuf_v1 global.

I'm wondering how the logistics on that would work. Normally, you can't
register two globals having the same name in the compositor. Does this lead
to a conflict between the EGL implementation's ability to enumerate a
linux-dmabuf API for its own use, and the linux-dmabuf API that the overall
compositor might offer?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the wayland-devel mailing list