summaryrefslogtreecommitdiff
path: root/dev-lang/python/python-3.13.11.ebuild
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2026-02-01 22:51:02 -0500
committerIonen Wolkens <ionen@gentoo.org>2026-02-01 23:55:00 -0500
commitb5c5ca63614554c0655ff34ed5dcf80b8a1f368d (patch)
tree98db30ebd71890795eb420bc07de8b27fef0edc0 /dev-lang/python/python-3.13.11.ebuild
parent819ed21ac98f4bd2beeac800369877eb5b8adbb8 (diff)
downloadgentoo-b5c5ca63614554c0655ff34ed5dcf80b8a1f368d.tar.gz
gentoo-b5c5ca63614554c0655ff34ed5dcf80b8a1f368d.tar.bz2
gentoo-b5c5ca63614554c0655ff34ed5dcf80b8a1f368d.zip
x11-drivers/nvidia-drivers: sync 580 modeset/fbdev defaults with 590
fbdev=1 will be needed if we ever want to support DRM_SIMPLEDRM in the future for dist kernels like Fedora does but that we explicitly disable in the kernel config we use from there. Albeit older or unsupported drivers will continue to either lack support or keep it off-by-default due to having more issues. 390.x + 470.x that lack fbdev=1 support will remain in the tree likely until December 2027 after the last kernel to support these versions will reach EOL given there is no plans to patch old drivers for newer kernels in Gentoo at the moment. 535.x + 570.x will likely be removed before then whenever NVIDIA stops updating them given they do not support more cards than 580.x does. wrt bug #840439, potentially switching in dist-kernel will likely require at least a warning somewhere or better yet a news item. Both for old drivers (if still in-tree when this is done) or for users that explicitly disabled fbdev=1 in their configs for one reason or another (sometime it picks a bad resolution or cause other issues). Users that cannot use or do not want fbdev=1 could probably use instructions to revert with /etc/kernel/config.d and won't be able to use -bin anymore. As for modeset=1, NVIDIA hasn't enabled that one by default "yet" but realistically about every distros does. It is also needed for fbdev=1 to work and locking =1 behind USE=wayland makes that inconvenient. -- Intentionally did this in a revbump *after* -r0 is stabilized so that issues do not get mixed up with unrelated regressions in the driver version itself. If users have -r1 issues not in -r0, they should know to adjust their nvidia.conf as needed (a postinst warning is included). Will stabilize this one a bit later if nothing major comes up. Formerly meant to use a separate nvidia-580.conf but, given restored USE=kernel-open in 590.x, nvidia-590.conf is fine for 580.x too. Bug: https://bugs.gentoo.org/840439 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-lang/python/python-3.13.11.ebuild')
0 files changed, 0 insertions, 0 deletions