Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 04 Mar 2025 22:42:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 285139] x11/nvidia-driver, x11/linux-nvidia-libs, graphics/nvidia-drm*-kmod: Upgrade to latest Production Branch of driver 570.124.04
Message-ID:  <bug-285139-7788-GeRDSp00ru@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-285139-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-285139-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=3D285139

--- Comment #9 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> ---
(In reply to Austin Shafer from comment #8)
FreeBSD is used on embedded appliances, too. Not sure autonomous vehicles
and/or medical appliances are included or not, though.

For those use cases, IIUC, possibly VulkanSC is wanted unlike other use-cas=
es.
But OTOH, for those use-cases, footprint of OS (not only kernel but also ba=
se
system) running usually matters.

This is another reason I considered VulkanSC supports in x11/linux-nvidia-l=
ibs
are not strongly needed (Linuxulator surely increases memory and disk
footprints compared with native drivers/libraries/apps).

Anyway, if anyone want it and possible to test popps in, I'll work on it af=
ter
completing category 1 and 2.

And what I can test for x11/linux-nvidia-libs is checking whether it builds=
 and
installs fine, as I currently don't have anything requiring the functionali=
ties
of x11/linux-nvidia-libs. Just trying to keep it in sync with x11/nvidia-dr=
iver
(which would be mandatory like with nvidia-drm-*-kmod ports, my guess).

--=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-285139-7788-GeRDSp00ru>