linux-dmabuf and eglBindWaylandDisplayWl

Matt Hoosier matt.hoosier at
Thu Apr 9 22:34:38 UTC 2020

On Thu, Apr 9, 2020 at 2:51 PM Simon Ser <contact at> wrote:

> On Thursday, April 9, 2020 9:41 PM, Matt Hoosier <matt.hoosier at>
> wrote:
> > 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.
> Mesa already binds to zwp_linux_dmabuf_v1 and uses it if possible.
> > 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?
> Just to be clear: we're talking about the client side right?
> It's fine to bind twice to the same global. This creates two
> independent objects.

No, I mean from the standpoint of a compositor implementer.

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

More information about the wayland-devel mailing list