4 ms·

What's GBM?

• boudin 5y ago
  It's the buffer management part of wayland. Nvidia never implemented it and pushed for egl streams instead. This means that compositor have to implement two paths, gbm (wayland), egl stream (nvidia propriatory only).
  • kaba0 5y ago
    Nitpick, but it is actually part of the kernel. X server also uses it, but there was no problem because nvidia could release a binary patch for it to use their proprietary thingy. It is not possible with the many wayland compositor so it became an apparent problem with wayland.
    • boudin 5y ago
      It is explicitely part of the wayland protocol https://wayland-book.com/introduction/high-level-design.html https://wayland-book.com/introduction/high-level-design.html
      • kaba0 5y ago
        From your link: “There are many distinct software components in desktop ecosystem. There are tools like Mesa for rendering (and each of its drivers), the Linux KMS/DRM subsystem, buffer allocation with GBM, the userspace libdrm library, libinput and evdev, and much more still. [...] libinput Like libdrm abstracts the DRM subsystem, libinput provides the userspace end of evdev.”
  • deleted 5y ago
    [deleted]
• josefx 5y ago
  Apparently a Mesa driver API for buffer management.