Page MenuHomeFreeBSD

[NEW PORT] x11/nvidia-driver-devel, x11/linux-nvidia-libs-devel, graphics/nvidia-drm[,510,515,61,66]-kmod-devel: Add new port
ClosedPublic

Authored by junchoon_dec.sakura.ne.jp on Thu, Jun 5, 9:20 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jun 28, 6:38 AM
Unknown Object (File)
Wed, Jun 25, 7:52 PM
Unknown Object (File)
Sun, Jun 22, 9:56 AM
Unknown Object (File)
Sun, Jun 22, 7:08 AM
Unknown Object (File)
Sun, Jun 22, 6:47 AM
Unknown Object (File)
Tue, Jun 17, 10:50 PM
Unknown Object (File)
Mon, Jun 16, 8:02 PM
Unknown Object (File)
Mon, Jun 16, 8:02 PM
Subscribers

Details

Summary

Add *-devel versions of nvidia drivers

These ports provides supports for New Feature Branch (NFB) of upstream
nvidia drivers like existing legacy branches of ports.

In some cases, supports for cutting edge GPUs are provided via
NFB of driver packages or Beta branch of drivers.

As Beta Branch of drivers cannot be recommended widely, we decided to
add support for NFB as *-devel version.

This new *-devel versions tracks the latest non-Beta versions
regardless it's NFB or Production Branch of drivers.
This is because, in some cases, major version of Production Branch
of drivers are bumped to larger than the one for corresponding
NFB.

So depending on the timing, *-devel 100% matches non-devel
master ports except for its package name.

Our upgrading policies are:

  1. Start investigating whether some additional works are needed to build/install/run or not when new Beta is found to be released upstream.
  2. If any additional works were needed and done, upgrade master ports below without updating version nor PORTREVISION of master ports below.

    x11/nvidia-driver x11/linux-nvidia-libs graphics/nvidia-drm-*-kmod

    and as needed, graphics/nvidia-drm-kmod/Makefile.common would be updated, too.
  3. Once findng new NFB is released upstream, bump versions of *-devel. Step 2 would "usually" ease this work unless Beta is skipped or last-minutes breaking changes are introduced.
  4. Once finding new Production Branch is released upstream, bump versions of master ports.
  5. Once finding any of Legacy Branch of driver is released upstream, upgrade corresponding legacy ports. This could need some additional work, because updated version could incorporate patches from our ports.

Note that graphics/nvidia-drm-*-kmod does NOT support any of
exisiting legacy versions, as they don't yet have codes to
support these ports.

PR: 287268

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Thanks for implementing this. I'm hopeful it will help detect issues earlier, let users more easily consume the latest drivers, and avoid having to do large (550 -> 570) upgrades.

graphics/nvidia-drm-510-kmod/Makefile
7

Can we not make the second wildcard line cover both so we don't have two nearly identical lines? i.e. nvidia-drm-515-kmod* ...

graphics/nvidia-drm-510-kmod/Makefile
7

Well, this change simplly followed what commit bcaf25a8c8046b094f6b5ab5bc258333bc326ee1 did.

https://cgit.freebsd.org/ports/commit/?id=bcaf25a8c8046b094f6b5ab5bc258333bc326ee1

Maybe the intention would be to clarify master port and slave ports (my guess).
Should I fix this?

Simplify CONFLICTS_INSTALL lines.
While here, add missing CONFLICT_INSTALL for x11/linux-nvidia-libs.

Precisely, CONFLICTS_INSTALL for x11/nvidia-secondary-driver* can be removed, too, for main branch.

But intentionally keep this until next quarterly branches, as 2025Q2 still has x11/nvidia-secondary-driver[-390] and there could be anyone switching from 2025Q2 to main with some reason.

Thanks, I think this seems reasonable to me but we probably want to give time for others to sign off on the new approach as well.

This revision is now accepted and ready to land.Mon, Jun 9, 10:34 PM

Maybe we need to decide whether waiting until before the end of June or wait more.
This means in which quarterly this appears.

Someone would want the name other than "-devel", as it could confuse users that it can be Beta or not.
(Described in summary, though.)
And some braves would want this to include Beta.

Let's see whether someone pop in and comment here or Bug 287268. Currently both has the patch with same context.

Rebase after upgrading of graphics/drm-515-kmod to drm_v5.15.160_4 at commit d7a1f45acaef32b98399a28ab5be5307d1186026.

This revision now requires review to proceed.Tue, Jun 17, 9:37 AM

Found latest NFB 575.64 is released.
As I'm now running new Production Branch of driver 570.169 (filed PR 287641 and corresponding review D50915) to see whether any new problem occurs or not, update would be worked on (hopefully) after a couple of days.

Upgraded to new NFB 575.64.

While here, rebase after upgrading of master ports to 570.169 at commit ports ff354f2f8d35927a0c744770ef5a76f938522a77.