3 ms·

FWIW I don't think this is an issue anymore, nVidia began implementing the necessary APIs - it was more a situation of nVidia not supporting Wayland, not the ot

• charcircuit 3y ago
  >it was more a situation of nVidia not supporting Wayland, not the other way around - a couple of years ago. Do not forget the era where compositors were choosing not to support an open standard of the EGL_KHR_stream extension. Instead they preferred a proprietary solution using Mesa's GBM API.
  • Bu9818 3y ago
    For good, functionality-related reasons at the time[0], and everyone in the Wayland space had been using the mesa library except nvidia with their own proprietary libgl. [0]: https://github.com/swaywm/sway/issues/490#issuecomment-471745501 https://github.com/swaywm/sway/issues/490#issuecomment-47174...
    • charcircuit 3y ago
      >For good, functionality-related reasons at the time Having it work surely is better than those drawbacks. Things can be improved and iterated on over time. Wayland adoption was damaged by this. >and everyone in the Wayland space had been using the mesa library They chose to make themselves compatible with a single graphics driver. GBM ended up having to be rearchitected so that Nvidia could create a backend for end.