Date: Sun, 9 Nov 2025 19:46:44 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Steve Kargl <kargls@comcast.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10] Message-ID: <osqqnro2-n1pn-6n91-o991-2nnosnnos28@SerrOFQ.bet> In-Reply-To: <8cfec553-ac9b-4357-80c6-74b7442289e0@comcast.net> References: <288036F0-180F-4DF4-94FD-66365B7504EA@yahoo.com> <255c624f-765c-4091-b3a5-22d439d292a1@comcast.net> <162qrp4-qr99-5qr6-413s-6r7rpr39nno9@SerrOFQ.bet> <8cfec553-ac9b-4357-80c6-74b7442289e0@comcast.net>
index | next in thread | previous in thread | raw e-mail
On Sun, 9 Nov 2025, Steve Kargl wrote: > On 11/9/25 08:56, Bjoern A. Zeeb wrote: >> >> So if you want things to work, it's the ports which needs to be fixed. >> > > First, commit the patch from the PR. That fixes the problem. The -D is not for a drm-kmod/ports fix please; there's another semi-native driver in src which uses LinuxKPI headers and needed this and there's still a need to fix that. Then I'll see if I can get away with it within LinuxKPI itself. I added a suggested patch to your PR for the port for some grpahics/ports person to start work with and get it in. > Second, it is an interesting stance to to take. It's okay to > break/diminish the FreeBSD experience for others in the name > of progress. If that would be the case, then I probably wouldn't have bothered following up and helping identifying a better fix the moment I became aware of the problem. I am sorry x11 hasn't dealt with this since (must be) end of September. /bz -- Bjoern A. Zeeb r15:7help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?osqqnro2-n1pn-6n91-o991-2nnosnnos28>