[arch-dev-public] Mesa, Nvidia and libglvnd (the good, the bad and the ugly) :)

Laurent Carlier lordheavym at gmail.com
Sun Feb 12 18:22:30 UTC 2017

Nvidia provides for several releases libglvnd support which mean the hability 
to have serveral libgl installed without hacks (nvidia-libgl, mesa-libgl 
currently). With Fedora providing default Mesa with libglvnd support (with 
some fedora patches, some upstream pending patches), i plan to provide Mesa 
with libglvnd support with mesa-17.0

What does this means ?
Mesa and Nvidia will be able to live together in a perfect harmony :) Mesa and 
Nvidia will not provide anymore mesa-libgl and nvidia-libgl packages; they are 
useless. libglvnd will provide libgl support and will depend on an opengl-
driver, what Mesa and Nvidia will provide. Bumblebee will not work anymore 
with Nvidia and Mesa, but only with prime (1).
Nvidia-340xx driver will still work with bumblebee but will need a specific 
(non libglvnd?) Mesa version.
Nvidia-304xx driver will be (finally) moved to unsupported.

So, When ?
The first step is a new xorg-server version with upstream patches to improve 
outputclass support and the glx.so symlink hack (2), now using ModulePath xorg 
option (3) and adapt Nvidia and Mesa drivers. Let's hope i will not break 
everything :)

The next step (after Mesa 17.0 release) is the libglvnd move.......

(1) https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime-synchronization/
(2) https://bugs.archlinux.org/task/26284
(3) man xorg.conf

Laurent Carlier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20170212/c6ae4af0/attachment.asc>

More information about the arch-dev-public mailing list