oh and heh, maybe add what the minimum should be in the dialog, so people don't have to guess?

I'd at least put a comment into here as to why we've chosen this. Eg, what I just asked about in IRC and you said "pkgbase OOM's on 256mb RAM".

Heh we've both hit a couple of fun paths into this (see https://reviews.freebsd.org/D50794 as well)

re-add missing multicast check, thanks bz!

fix the seqno update routines to wrap things appropriately.
This bit me when doing some work on if_rsu

Address bz's comment - yup, this works with seqno offload and
with it just not populated in the driver encap path. Neat!

I assume it just works fine? :-)

Note: my hope is to eventually delete the TX lock entirely; this sets the ground work to first experiment and test various drivers in this stack.

migrate prefix to net80211_

rename prefix to net80211_

use net80211_ prefix

update commit message (locally)

In D50642#1156201, @bz wrote:

So i was thinking if we can start using ieee80211 for standards things and use a net80211 prefix for our own stuff (at least for anything new or we change)?

In D50638#1156017, @bz wrote:

Need to check all the other places which may have changed implicit behaviour too and they all need the same comment,

update from bz; matches what's in CCMP

I think this looks fine. I'm personally not too worried about breaking things in ipfw to make them much cleaner/clearer/less error prone, as long as we document it in UPDATING.

tested on my MSI GE76 raider that was exhibiting this w/ firefox/pulseaudio; it no longer happens. Thanks!

It's better than the status quo in -HEAD, so let's get it in and then churn some more on making it recover better!

technically (cry) ucast will eventually be keyix 0 and keyix 1, but not the WEP/global slots. Aiee. :-)

This doesn't apply cleanly on -head, it requires D49827 first

I'm finally updating my GE76 w/ AX210 to test iwx and iwlwifi in -head out, so I'll have to apply this to actually get it to pass a suspend/resume pass. stay tuned!

I'm still not a big fan of putting the strings in the kernel syscall ABI (as i guarantee someone's gonna end up writing stuff that depends upon the content of the strings!), but I /am/ a fan of how the kernel source is being updated with errors. We can at least grep for the macro use to see what they're doing, and they're a no-op if it's not compiled in.