Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 Jun 2025 17:01:04 +0000
From:      Brooks Davis <brooks@freebsd.org>
To:        Warner Losh <imp@bsdimp.com>
Cc:        David Chisnall <theraven@freebsd.org>, "Bjoern A. Zeeb" <bz@freebsd.org>, wireless@freebsd.org, FreeBSD Current <current@freebsd.org>, FreeBSD Stable ML <stable@freebsd.org>, desktop@freebsd.org
Subject:   Re: HEADS UP: wireless KPI and KBI and FreeBSD 15
Message-ID:  <aEHNUKnuTE2PxpOy@spindle.one-eyed-alien.net>
In-Reply-To: <CANCZdfo4DyhkF=d=rJuByZjNk1Vq2FNatzMmJR3nttBqu9gr4A@mail.gmail.com>
References:  <114q5890-nrs9-55r5-44n9-86506985490s@SerrOFQ.bet> <6803DF9A-5660-4F05-82CC-B4085584EF30@freebsd.org> <CANCZdfrd1Z_Y35-C=L61iW01FX=iXR-noJWA-GheDPGv%2Bs6nGA@mail.gmail.com> <81E0167A-7330-4C67-BEAA-074A7CA26E63@FreeBSD.org> <CANCZdfo4DyhkF=d=rJuByZjNk1Vq2FNatzMmJR3nttBqu9gr4A@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

On Thu, Jun 05, 2025 at 09:40:27AM -0700, Warner Losh wrote:
> Bringing it back to wifi: we're so far behind the curve on WiFi today
> that we shouldn't saddle it with stability prematurely. We should do
> things like kv pairs to make it better. We should try not to shoot
> ourselves in the foot. But mistakes will be made almost certainly
> despite due care, and I'd rather give the wifi folks a
> get-out-jail-free card on a temporary basis to allow them to catch up
> because doing backwards compat stuff isn't super hard, but can be
> super time-consuming especially when there's no tests to assure
> accidents don't happen and tracking down why something crashed for
> binary compat reasons can take a huge amount of time. At least when I
> did this stuff for a release or two for drm-kmod when we did try hard
> to stay compatible for several minor releases. It was a ton of work. I
> don't think we currently have the resources to commit to that work
> because it will come at the expense of new features.

I think this is the best compromise.

I do think we might want to consider batching of wifi MFCs so most
breaks occur infrequently (perhaps around release time) rather than
scattered through out the inter-release period.  My thinking here is
that we shouldn't be breaking things for stable users more often than
necessarily and for the brave it wouldn't be that big a deal to pull
from a rebased MFC candidate branch.  This wouldn't be free, but maybe
it's got a reasonable cost/benefit ratio.

-- Brooks


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aEHNUKnuTE2PxpOy>