Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/x11-drivers
Commit message (Collapse)AuthorAgeFilesLines
...
* x11-drivers/xf86-input-wacom: Stabilize 1.2.1 amd64, #928529Arthur Zamarin2024-04-031-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 sparc, #928444Sam James2024-04-031-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 ppc, #928444Arthur Zamarin2024-04-021-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.40.59:0/vulkan, drop 550.40.55Ionen Wolkens2024-04-022-9/+3
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 ppc64, #928444Arthur Zamarin2024-04-021-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 amd64, #928444Arthur Zamarin2024-04-021-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 arm, #928444Arthur Zamarin2024-04-021-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/xf86-input-elographics: Stabilize 1.4.4 x86, #928444Arthur Zamarin2024-04-021-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 550.67 for amd64Ionen Wolkens2024-03-261-1/+1
| | | | | | | | | | | | This is the 3rd iteration of the new 0/550 production branch and it is about time to stabilize it. Note however that some Lenovo laptop users may or may not experience random crashes and need to stick to 0/535 for now (which is still supported and not going anywhere for a while). That aside, happy bday immolo :) Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 535.171.04 for amd64Ionen Wolkens2024-03-261-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop 535.154.05, 550.54.14Ionen Wolkens2024-03-263-1040/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.171.04Ionen Wolkens2024-03-212-0/+529
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop 470.223.02Ionen Wolkens2024-03-202-472/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.67Ionen Wolkens2024-03-192-0/+508
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-video-openchrome: mark LTO-unsafe, strict-aliasing unsafeEli Schwartz2024-03-111-2/+12
| | | | | | | | | | | | | Freedesktop moved to gitlab and dropped support for previous project hosting methods to read-only. It appears openchrome never made the migration. May be dead -- it hasn't been developed in some time, the cgit HEAD is 4 years old and a non-default branch is "only" a year old. Not really sure where to report a bug to. ;) Closes: https://bugs.gentoo.org/864406 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 535.161.07 for amd64Ionen Wolkens2024-03-101-1/+1
| | | | | | | | | | | This driver was formerly marked "beta" which was expected to be a mistake, and indeed NVIDIA has since corrected that. Just a bugfix release, and it works fine (for me). So let's stable it. Stable for new production branch (550) is not far off, but will wait a bit more. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 470.239.06 for amd64Ionen Wolkens2024-03-101-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: bump KERNEL_MAX to 6.8 where possibleIonen Wolkens2024-03-105-5/+5
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.40.55:0/vulkan, drop 550.40.53Ionen Wolkens2024-03-082-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-input-wacom: Version bump to 1.2.1Matt Turner2024-03-042-0/+82
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/nvidia-drivers: drop 545.29.06-r1, 550.40.07Ionen Wolkens2024-03-023-1030/+0
| | | | | | | | Old NFB and a beta, should be little need to keep these around for an extended period. Use production branch 550.54.14 instead or the old 535.* one if issues. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.40.53:0/vulkan, drop 535.43.28Ionen Wolkens2024-03-022-34/+10
| | | | | | | | | | | | | No real testing like usual for 0/vulkan (beside a basic build test) despite major bump, please report if issues. Seems to have received the pfn_valid fix from 550.54.14. Reminder that this branch is only intended for vulkan developers that also need the latest vulkan extensions, most users should use 535.154.05 or 550.54.14. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/xf86-input-elographics: Version bump to 1.4.4Matt Turner2024-02-292-0/+11
| | | | Signed-off-by: Matt Turner <mattst88@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.54.14Ionen Wolkens2024-02-262-0/+509
| | | | | Closes: https://bugs.gentoo.org/925461 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.161.07Ionen Wolkens2024-02-262-0/+530
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 470.239.06Ionen Wolkens2024-02-263-1/+445
| | | | | | | | | | | | | | | | | | | Also drop USE=wayland, last time I tried to use this with 470 not only was it very limited due to the lack of GBM support, but it was starting to break in horrible ways (e.g. flickering). This been incompatible with newer egl-wayland, and 1.1.7 is filed with problems. Users often find it annoying that portage warns that it skipped the egl-wayland update too (USE=wayland is default on desktop profiles even if they don't use it, so it was still annoying). 470 users should really just stick to Xorg (sorry). Note nvidia-drm.modeset=1 was enabled with USE=wayland, disabling may possibly have unexpected effects for some users even on Xorg. Re-enable in nvidia.conf manually if you need this. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: drop 535.146.02Ionen Wolkens2024-02-222-536/+0
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.43.28:0/vulkan, drop 535.43.25Ionen Wolkens2024-02-172-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: check for CPU_FREQ with USE=powerdIonen Wolkens2024-02-076-0/+6
| | | | | Bug: https://bugs.gentoo.org/923117 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: move nvidia-powerd behind IUSE=powerdIonen Wolkens2024-02-067-21/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | Mostly due to the openrc service's "need dbus" which is an annoyance when dbus is missing (preventing from being a runtime-only optfeature), but even with systemd this now also allows to properly check for multilib on dbus (used by 32bit glcore/eglcore libraries to communicate with powerd). *Technically* needs a revbump given --changed-use does not know it needs to rebuild here, but given this only cause problems for rare users without dbus (e.g. headless cuda servers with USE=-tools) and will propagate with kernel updates+rebuilds let's not bother every users over this. Hopefully users of powerd (incl. for systemd which may have more existing ones) will notice the new USE and enable it. Also re-arrange arm64 handling, it makes more sense to mask the USE on arm64 than keep it as a no-op by checking if use !amd64. Exception to this is 0/550 branch which started to include a arm64 nvidia-powerd build (albeit do not think hardware that need this even exists yet). Hope did not break installation there given did not test on arm64, please report if so. Bug: https://bugs.gentoo.org/923117 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.43.25:0/vulkan, drop 535.43.24Ionen Wolkens2024-02-022-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.43.24:0/vulkan, drop 535.43.23Ionen Wolkens2024-02-022-3/+3
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: fix build w/ kernel 6.1.76+6.6.15+6.7.3Ionen Wolkens2024-02-018-0/+69
| | | | | | | | | | | NVIDIA already confirmed to be planning a release without pfn_valid, so this is temporary until then. May need revisiting for older kernels if change is further backported. bug #923456 could be closed but leaving open for visibility for now. Bug: https://bugs.gentoo.org/923456 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: remove IBT warning in 545+Ionen Wolkens2024-01-312-12/+0
| | | | | | | | | | | Hopefully for good this time, albeit will be left forever in 390 (definitely broken) and 470 too given status is incertain. 525+535 will eventually be dropped either way (far sooner than 390+470 anyway), so let's just leave them alone to be safe. Closes: https://bugs.gentoo.org/911142 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: use gcc14 patch in unkeyworded 0/550 tooIonen Wolkens2024-01-291-0/+1
| | | | | | | | Turns out was misled into thinking it was fixed, the issue doesn't trigger with my own kernel but does with a "defconfig" one. And then changes from NVIDIA made me think it worked around it. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add nvidia-powerd openrc scriptIonen Wolkens2024-01-287-0/+17
| | | | | | | | | | | | | | | | Untested given requires specific hardware to even start the daemon which I do not have. Please report if any issues. Not worth revbumps, can let it propagate with rebuilds during kernel upgrades. Use /var/run rather than /run given nvidia hardcodes path to the pid file and /run may be incorrect if /var/run is not a symlink. Albeit with command_background=true openrc is technically the one handling it (may avoid duplicates, again can't test). Closes: https://bugs.gentoo.org/923117 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: relicense nvidia-persistenced.initdIonen Wolkens2024-01-281-2/+1
| | | | | | | | | Tiny script that was entirely written by me, and came to prefer installed+redistributed simple scripts to not carry extra baggage. (MIT is already in the ebuild's LICENSE) Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.43.23:0/vulkan, drop 535.43.22Ionen Wolkens2024-01-262-2/+2
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: sync tc-is-lto w/ other ebuilds in 0/550Ionen Wolkens2024-01-241-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: migrate checking for enabled lto, to tc-is-ltoEli Schwartz2024-01-246-6/+6
| | | | | | | | | | This toolchain func was recently added, and is a lot more reliable than get-flagq, for example if the active flags contain `-flto -fno-lto` then tc-is-lto gets it correct. We would rather use this wherever possible. Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/34996 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: tc-export PKG_CONFIGIonen Wolkens2024-01-248-10/+10
| | | | | | | | | | Noticed variable is used due to a change to utils.mk in 0/550 but turns out there was already some use of it in nvidia-settings for older versions too. Just export it everywhere. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 550.40.07 (unkeyworded beta)Ionen Wolkens2024-01-242-0/+508
| | | | | | | | | | | | | | | No known issues, only unkeyworded due to its beta status, feel free to try it. In theory should be fairly sane given most of its changes were in 545 and this is likely due to become a production branch (and a stable candidate here) next release. Removes the need for a few things: - kernel-6.7 patch (fixed) - gcc14 patch (not *really* fixed, but conftests.sh uses -Wno-error) - 6.6 kernel limitation for arm64, nvidia does a GPL test (untested) - powerd amd64 limitation, files exist on arm64 too now (untested) Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: stabilize 535.154.05 for amd64Ionen Wolkens2024-01-231-1/+1
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: downgrade KERNEL_MAX to 6.6 for arm64Ionen Wolkens2024-01-174-4/+24
| | | | | | | | | | | screen_info is marked GPL on non-x86 and cannot be used. It's possible to tell nvidia-drivers to not use that symbol albeit unknown what downsides this has (esp. when I cannot test this). For now, let's just not advertise 6.7 compatibility for arm64. 6.6 is the next LTS either way, so waiting should not be so bad. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: add 535.154.05Ionen Wolkens2024-01-162-0/+525
| | | | Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: fix build with upcoming gcc14Ionen Wolkens2024-01-157-0/+60
| | | | | | | | | | | | | | | | | | | Trivial and proper fix for 5xx branches, NVIDIA seems to be (now) keeping track of implicits and incompatibles beside missing this one hidden behind 2>/dev/null and kernel >=5.18. Can't say the same for the legacy branches (390 and 470), and rather than worry about these going for the lame life support treatment with -Wno-error= there. 470 has hope to be fixed properly by NVIDIA still but this is likely there forever in the not supported + masked 390. No need for revbumps, with gcc13 the test simply functions properly and does what's right, while with 14 it's just a build-time issue (and legacy branches are unchanged). Closes: https://bugs.gentoo.org/921370 Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* Move {dev-util → dev-debug}/valgrindMichał Górny2024-01-132-4/+4
| | | | | | Signed-off-by: Michał Górny <mgorny@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/34786 Signed-off-by: Michał Górny <mgorny@gentoo.org>
* x11-drivers/nvidia-drivers: depend on xorg-proto for static-libsIonen Wolkens2024-01-126-1/+7
| | | | | | | | static-libs is a subset of USE=tools which depends on xorg-proto, but static-libs itself was missing it and is entirely an X library that needs these. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: fix with linux-6.7 and some configsIonen Wolkens2024-01-084-0/+33
| | | | | | | | | | | | | | | | Looked fine for me but turns out the issue is conditional to kernel configs and it was not enabling USE_LKCA with mines. Also needed USE=kernel-open to run into this. An NVIDIA representative has offered a fix, so may as well use it this time around. 525 and older branches did not use this function. Should be harmless for older kernels, but have not really tested so only applying if >6.7 as a precaution, esp. for stable 535. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
* x11-drivers/nvidia-drivers: bump KERNEL_MAX to 6.7 where possibleIonen Wolkens2024-01-075-9/+9
| | | | | | Nothing special, all those compatible with 6.6 still seem fine. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>