[Bug 290432] graphics/drm-515-kmod no longer builds on FreeBSD-current

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 09 Nov 2025 16:44:52 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290432

Bjoern A. Zeeb <bz@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open

--- Comment #4 from Bjoern A. Zeeb <bz@FreeBSD.org> ---
Sorry for the annoyance on current.

I am testing and making sure things compile for what the drm-kmod port
supports.

The snarly comment I have, and I hope you don't get me wrong, if you do not
find help or figure out what your issue is with newer drm-kmod you'll sooner or
later not have graphics anymore.

I have to admit it is a very painful process and after almost half a year I got
an amdgpu working without fully knowing what caused it not to bring my laptop
back to POST anymore.

I am ware that there are some projects under way which would help the debugging
immensely but I beleive sadly none of them is fully there yet (but I also have
been on holiday and still have more to catch up).

That all said, as a local workaround, you could probably fairly simply replay
the commit which went into drm-kmod master and 6.6-lts and 6.1-lts  to 5.15-lts
as it seems to apply cleanly:

% git cherry-pick 20829888caf411a4ac5a4349cbb013334e0b31de
Auto-merging drivers/gpu/drm/drm_pci.c
Auto-merging drivers/gpu/drm/drm_sysctl_freebsd.c
[5.15-lts bd997db9f2] drm: use LinuxKPI PCI functions rather than bsd native
 Date: Thu Jul 31 07:31:38 2025 +0000
 2 files changed, 15 insertions(+), 27 deletions(-)
% git status
On branch 5.15-lts
Your branch is ahead of 'origin/5.15-lts' by 1 commit.
  (use "git push" to publish your local commits)
...

But I believe we cannot do that unconditionally as the underlying LinuxKPI
change is not in the branches (and releases) which would still require 5.15-lts
(I'd have to go and check the full matrix).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.