Bugzilla

If this is indeed an NV only problem with the GLX vsync source, we could extend bug 1640779 to only use `GLX_SGI_video_sync` on Mesa and use Xrandr in all other cases.

If this is indeed an NV only problem with the GLX vsync source, we could extend bug 1640779 to only use `GLX_SGI_video_sync` on Mesa and use Xrandr in all other cases. Might make problems with switch interval 1 though.

Alternatively: I think all hardware supported by the 460 driver series (our NV baseline for WR) is also supported by the 470 series. So if we ship EGL for the 470 series (on EGL we always use the Xrandr vsync), we can also consider just bumping the NV baseline to 470.82, making sure that the whole prop. NV population is either on EGL+HW-WR or SW-WR, making the first big step to deprecate GLX.

If this is indeed an NV only problem with the GLX vsync source, we could extend bug 1640779 to only use `GLX_SGI_video_sync` on Mesa and use Xrandr in all other cases. Might make problems with switch interval 1 though.

Edit: Alternatively: I think all hardware supported by the 460 driver series (our NV baseline for WR) is also supported by the 470 series. So if we ship EGL for the 470 series (on EGL we always use the Xrandr vsync), we can also consider just bumping the NV baseline to 470.82, making sure that the whole prop. NV population is either on EGL+HW-WR or SW-WR, making the first big step to deprecate GLX.

Edit2: Given that the 470 driver series marks the line for officially supported hardware (the oldest being almost 10 years old), it's probably fair to only officially support WR on officially supported hardware. So going all EGL on NV sounds like a decent option to me (users of older hardware should use nouveau/mesa).