Date: Mon, 28 Nov 2022 09:19:24 -0800 From: Adrian Chadd <adrian@freebsd.org> To: "Bjoern A. Zeeb" <bz@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: IEEE80211_DEBUG_REFCNT breaks drivers Message-ID: <CAJ-Vmo=mU%2BjczzdW954Avf4G_r0LELC4dQV-USBn=NCwbOXwMQ@mail.gmail.com> In-Reply-To: <CAJ-VmokecVa2xNgqSbvfPfy2ezMvS1JC4Hm65Ej2n5OpwXkO4Q@mail.gmail.com> References: <rqo55p4p-964s-pqps-r482-oqo1on5q5spr@mnoonqbm.arg> <CAJ-VmokecVa2xNgqSbvfPfy2ezMvS1JC4Hm65Ej2n5OpwXkO4Q@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Oh I hit send too quickly. The tl;dr there was that the /theory/ being you should be able to build a driver that'll load into a kernel without needing all of the non-global opt_xxx options lying around. The ABI for a given release is supposed to be the ABI. Anyway, I'm a fan of (2) for cleanliness. I'd rather we found a way to structure things to NOT change ABI based on what's in opt_xxx config options. -adrian [-- Attachment #2 --] <div dir="ltr">Oh I hit send too quickly.<div><br>The tl;dr there was that the /theory/ being you should be able to build a driver that'll load into a kernel without needing all of the non-global opt_xxx options lying around. The ABI for a given release is supposed to be the ABI.</div><div><br></div><div>Anyway, I'm a fan of (2) for cleanliness. I'd rather we found a way to structure things to NOT change ABI based on what's in opt_xxx config options.</div><div><br></div><div><br></div><div><br></div><div>-adrian</div><div><br></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=mU%2BjczzdW954Avf4G_r0LELC4dQV-USBn=NCwbOXwMQ>