Maybe just use time-zone or user hints in this case since NICs cannot
be fully trusted.
WTF no, the regulatory hint stuff should all be automated and user input
should really only come from trusted sources, see the cell base station
hint as a good example use case. The NICs are trusted as that's what
regulatory bodies like folks to do. Hell even the country IEs are only
trusted for the alpha2, the actual contents are disregarded. Regular
user input should only help compliance further, that's it.
NICs just aren't that reliable, seems you can buy NICs with any number
of regulatory domains on the interweb, and then you can hop on a plane
and go other interesting places.
If you ever have a system with NICs with two different regulatory domains,
I assume it is very likely that it was not certified in that configuration.
Maybe the user's input (and AP's beacons and such) are more reliable in this
case.
But, not worth arguing about at this point. As long as the basic regulatory
bugs are fixed (as per the other thread), then my problems should be solveable.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
