mirror of
https://git.openwrt.org/openwrt/openwrt.git
synced 2024-10-19 05:58:53 +02:00
3ec4803932
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> |
||
|---|---|---|
| .. | ||
| acx-mac80211 | ||
| ar7-atm | ||
| avila-wdt | ||
| brcm2708-gpu-fw | ||
| broadcom-wl | ||
| button-hotplug | ||
| ep80579-drivers | ||
| gpio-button-hotplug | ||
| hostap-driver | ||
| i2c-gpio-custom | ||
| lantiq | ||
| linux | ||
| mac80211 | ||
| mmc_over_gpio | ||
| mt76 | ||
| mwlwifi | ||
| om-watchdog | ||
| rotary-gpio-custom | ||
| rtc-rv5c386a | ||
| spi-gpio-custom | ||
| trelay | ||
| w1-gpio-custom | ||
| wrt55agv2-spidevs | ||