Date: Sun, 27 Aug 2023 04:36:20 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273357] x11/nvidia-driver, x11/linux-nvidia-libs: update to 535.104.05 Message-ID: <bug-273357-7788-4QA7gBtmP4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273357-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-273357-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273357 --- Comment #2 from Austin Shafer <ashafer@badland.io> --- Populated a 535.104.05 branch in github, I can update the distinfos for the nvidia-drm ports tomorrow unless you want that to be part of this update. What exactly did you have in mind with "decouple"? Unfortunately there is a bit of an annoying process copying files from the Linux release and replaying patches onto the distributed tarball to get a working nvidia-drm, which is why it's coupled this way. I find this works b= est in git since it's easy to keep track of what's been applied and half automa= te it. That being said I am (slowly) working on getting this merged into the regular distribution to avoid this problem. I agree it isn't ideal, but it = lets me handle the significant churn in patches in an organized way. See: https://github.com/amshafer/nvidia-driver/blob/baseline/UPDATING.md and populate_driver.sh Note two related reviews: - https://reviews.freebsd.org/D41591 (the PRIME fix in this one is included= in the 535.104.05 branch, so this is really just a Makefile update now) - https://reviews.freebsd.org/D41574 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273357-7788-4QA7gBtmP4>