Date: Mon, 13 Jul 2020 09:13:53 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: "Bjoern A. Zeeb" <bz@freebsd.org>, driesm.michiels@gmail.com, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Current state of recent wireless cards Message-ID: <CAJ-Vmon7=-DSLPu0o7JGs1%2B4i3%2BEKMzG7VePhWES4rSUUahrDg@mail.gmail.com> In-Reply-To: <20200713172526.81bb91a04198792ce8695322@bidouilliste.com> References: <000501d655e3$90c40170$b24c0450$@gmail.com> <CAFC648B-1A32-4FF3-AC98-23A2B93732D5@FreeBSD.org> <20200710233308.b27284cd15dec5849fb5cc32@bidouilliste.com> <778A3FF0-905B-49ED-ABDE-913C3451AB16@FreeBSD.org> <20200713172526.81bb91a04198792ce8695322@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Jul 2020 at 08:25, Emmanuel Vadot <manu@bidouilliste.com> wrote: > > > Compile and working ? > Because that's easy to compile code if you add a lot of dummy stub > functions. I'm happy that this is going on; at the very least it'll point out a bunch of missing bits from our net80211 API that should get implemented (whether for linuxkpi style reasons or not!) that newer chipsets want. That's why I've started implementing per-VAP versions of things, initial uAPSD negotiation, etc - the ath10k driver port showed they were missing from net80211. I implemented them in ath10k then migrated them to net80211. I have a whole lot more to port from ath10k -> net80211 too. :-) There are a bunch of "is this 802.11 header X?" inlines / macros that mac80211 has that we don't, and it would be nice to have them in net80211. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon7=-DSLPu0o7JGs1%2B4i3%2BEKMzG7VePhWES4rSUUahrDg>