Unfortunately, it's not relevant here. nvidia-drm.ko itself is not built yet.
… 550.40.07 … BETA …
% rg linux-nvidia-libs /usr/doc/documentation/content/en
%
Yes, I know. What I wondered is that it is now incorporated into official (beta) driver package or not. I'm puzzled with this.(/boot/modules/nvidia-drm.ko is listed at <https://www.freshports.org/graphics/nvidia-drm-510-kmod/#pkg-plist> and <https://www.freshports.org/graphics/nvidia-drm-515-kmod/#pkg-plist>.)
It's for Linux apps working on top of linuxulator.What is the purpose of this port? I have one of its slaves installed, but I don't know why, I probably took a lucky dip approach in relation to some bugs.
Thanks for the clarification! So same distfile is used for both x11/nvidia-driver and graphics/nvidia-drm-*-kmod once 550 or later becomes production, but kept separately not to confuse existing users who don't need drm features.Yes the nvidia-drm patches are now incorporated into the official driver. No they are not built by default, you'll have to cd into src/nvidia-drm and make + make install there. It's not built by default because it requires having a copy of drm-kmod to reference during the build, and this way we don't have to suddenly update every testing system to be set up for DRM usage/builds and break existing flows.
For the average user this won't matter as I'll update the nvidia-drm-*-kmod ports to build nvidia-drm from the release tarball and get rid of my github patch distribution thing (finally!). Nobody should really be building the driver outside of ports anyway. I've been waiting for the 550 driver to get picked up by the nvidia-driver port, I see you created bug 277028 so I guess I should go ahead and start doing this.
Maybe unlikely.Will this patch make it into packages? At present, with nvidia-drm-515-kmod-535.146.02 (from packages) I am unable to get Wayland working on my machine with an NVidia card.
Even though for me, Wayland is more a curiosity than anything else, thank all of you for your work on this.