Created attachment 261053 [details] patch to modify regdomain.xml For regdomain JAPAN, freqband 5040_5080 is no longer available since 2017-12-01. W56 band was extended from 5470-5725MHz to 5470-5730MHz since 2019-07-11. i.e. ch.144 became available. 802.11ac netband definition needed. Though I'm not sure this modification is correct, it seems to be working on my laptop.
Japan is .. complicated. Every time the rules change, there may be a /new/ japan regulatory domain that needs to be created based upon when a device was certified. Let me go take a look at how far behind with all the japan regulatory domain updates (I think we're /way/ behind) and see how many new "countries" / regulatory domains I need to add to represent it all. Thanks!
Adrian: you are going to lose the "how much do I need to add" if you try to do it manually. I really want to fix the "regdomain" thinking given not even all EU countries in ETSI land seem to be the same at all times, so having up to 27 ETSI entries is just silly even if in the end it's likely just 5 or 6. We really need to get hard coded "FCC" and other bits out if ifconfig etc. and do this per-country with "regdomain" being a meta-data hint, e.g. for DFS rules? I started doing this based on Linux wireless-regdb: https://lists.freebsd.org/archives/freebsd-wireless/2025-April/003299.html It'll likely be easier to simply grab the JP bits from there or see if they are correct?
(In reply to Bjoern A. Zeeb from comment #2) No, it's worse than that. :-) Japan in particular doesn't back date its regulatory rules. So, NICs made /before/ the rules changed aren't grandfathered into the new rules, you also need to apply the old restrictions. That's why when you eg look at linux:drivers/net/wireless/ath/[regd stuff], you'll see JAPAN1 .. JAPAN40 or so, because even though CRDA knows about the current rules, it doesn't have the fine grained SKU info anywhere. Sam migrated some of it from the ath_hal regulatory code into net80211, which is why we have both country codes and regdomain SKU codes. Linux doesn't expose knobs to tweak the SKU regdomain (without extra diffs, like what openwrt does.) So yeah, I don't mind correcting the Japan bands. But we just need to keep in mind that whole SKU mess right now. (yes, regulatory domain support in net80211 needs a proper and large overhaul, and all of the drivers need updating to implement the SKU stuff properly. Alas.)
Created attachment 261146 [details] regdomain-xml-14-3R.diff ^Triage: rebase patch.