3 ms·
With the proprietary driver, the GPU is controlled by their closed-source kernel module, so Mesa's GBM code wouldn't know how to talk to it. However, as of the
by yissp 5y ago
With the proprietary driver, the GPU is controlled by their closed-source kernel module, so Mesa's GBM code wouldn't know how to talk to it. However, as of the latest version, NVIDIA is shipping a GBM back-end library that Mesa can load which is able to talk to their module.
- nextaccountic 5y agoBut what does this mean for applications that use Vulkan?
- dathinab 5y agoProbably nothing, similar for most applications using EGL it doesn't mean much. But it does matter for developers of Wayland compositors. A lot.
- lucb1e 5y agoSo Firefox, not using GBM but EGL, would not be able to make use of the proprietary driver and has to talk to DRM? Can two kernel modules even use the same card at the same time?
- pxc 5y ago> Can two kernel modules even use the same card at the same time? yes, I'm not sure how everything is divvied up. NVIDIA ships multiple kernel modules in their driver, and one of them is called ‘nvidia_drm’. So idk, maybe you have to use their DRM implementation or something
- matheusmoreira 5y agoI wonder if nvidia will ever integrate into the kernel properly. Using their drivers is such a poor user experience.