On 05/10/2025 22:32, Bjoern A. Zeeb wrote:
My limited understanding is that the SKUs were straight out of Atheros land
and in general would only be usable for one product a time.
There is very little help of them in regdomain.xml as the only place the
information makes sense is somewhere in the driver which needs to know which
SKU at which time was mapped to which regulatory setting.
It seems that ifconfig also uses sku in some internal data structure (instead of
a more natural key like 'name' or 'id'). So, if there are two entries with zero
sku (or no sku, which is the same), then that can confuse ifconfig.
In other words, it was okay to create an entry without sku but only once.
So, we probably shouldn't do it until we retire those sku-s from regdomain
altogether.
We may have to provide lots more of regulartory settings, especially for
JAPAN (50+ in theory now), in order to allow a proper mapping but we
are far away from this currently. If you look through sys/contrib/dev/athk/reg*
you can get a gimplse of what is involved.
Thank you for the pointer!
I now see that those magic sku-s match definitions in
sys/dev/ath/ath_hal/ah_regdomain/ah_rd_regenum.h.
That is, it's some Atheros private / proprietary stuff with no meaning outside
of Atheros universe that somehow made its way into regdomain.xml. Probably
there was a reason for it when FreeBSD WiFi support was in its infancy.
Well, this would be another item in the list of strange, confusing, sub-optimal,
incomplete and even wrong things about regdomain.xml.
Maybe this is another area where we could admit that "Linux won" and try to
switch to its regdb (which is much more complete and more readable at the same
time).
Thank you again.
--
Andriy Gapon
