https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241787
--- Comment #5 from Niclas Zeising <zeis...@freebsd.org> --- (In reply to vermaden from comment #3) That won't help the situation. The problem is that ports are built on the lowest common platform, which means, for 12 it is built on 12.0 until 12.0 is EOL (same for 11.2 and 11.3). The issue here is that while the kernel modules are indeed compatible with their respective branch (drm-fbsd11.2-kmod works on 11.3 and 11-stable, and 12.0-kmod on 12.1 and 12-stable), they have to be built together with kernel sources of the same version of the kernel actually running the module. Creating drm-fbsd12.1-kmod, or 11.3-kmod would not help, they would either be built on 12.0 and 11.2 respectively (well, 11.2 is EOL now, so the 11.2 module should work on 11.3 out of the box these days), or not built at all, depending on how the version check in the ports' Makefile is set up. I can agree that the naming of the modules are unfortunate and somewhat confusing, but renaming 11.2-kmod to 11.3-kmod was ruled out when Rene removed 11.2 support from the ports tree. See https://reviews.freebsd.org/D21974 for that discussion. In the end, the ambition is to have the user simply install drm-kmod and let that port pick the proper kernel module port for your specific system. Regards Niclas Zeising FreeBSD Graphics Team. PS. Please keep the discussion in the open PR (or the github issue, it gets more visibility that way). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
