diff options
author | Daniel Golle <daniel@makrotopia.org> | 2016-05-25 19:32:01 +0200 |
---|---|---|
committer | Felix Fietkau <nbd@nbd.name> | 2016-06-05 13:37:55 +0200 |
commit | 3ec48039326f218b1edad9da74b1694f722da7f2 (patch) | |
tree | 9d4eefab49f9397db19a16d24df72e148b1d1215 /target/linux/ixp4xx/Makefile | |
parent | 56b377304e6ff71608034247ac537bff3014c582 (diff) | |
download | upstream-3ec48039326f218b1edad9da74b1694f722da7f2.tar.gz upstream-3ec48039326f218b1edad9da74b1694f722da7f2.tar.bz2 upstream-3ec48039326f218b1edad9da74b1694f722da7f2.zip |
mac80211: respect user-set regulatory domain by default
It turns out most device vendors don't set the correct country code
in their devices' on-flash-EEPROM sections as they apparently rather
provide a complete per-target-market firmware with patched drivers
instead of just setting the country code.
This results in the driver to incorrectly assume the value stored in
the on-flash-EERPOM (usually US or China) being the regulatory domain
inside which the device is being used.
To work around this issue, OpenWrt introduced the ATH_USER_REGD config
variable to decide during build whether or not to allow the user to
override the regulatory domain setting. This option, however, is not
enabled by default and thus ends up being disabled for snapshots builds
and released binaries.
As we know for a long time that most devices got borked regulatory
domain values set in their EEPROMs we should allow our users to respect
their local law (instead of just assume US or China laws).
Note that also the current default has great potential of users not
ever setting their regulatory domain and thus using inapproriate and
potentially illegal frequencies and/or tx-power settings
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'target/linux/ixp4xx/Makefile')
0 files changed, 0 insertions, 0 deletions