aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware/ipq-wifi/Makefile
diff options
context:
space:
mode:
authorRobert Marko <robimarko@gmail.com>2023-04-11 20:20:18 +0200
committerRobert Marko <robimarko@gmail.com>2023-04-11 20:20:18 +0200
commit7475321f46b83cc04296638d6cf31542d11e3e78 (patch)
tree7c52ec8173a17553ecdf11bc4a67ee6ab6b2037b /package/firmware/ipq-wifi/Makefile
parentcd8c698f78980356d8fd2408e54f0c1c1d04c349 (diff)
downloadupstream-7475321f46b83cc04296638d6cf31542d11e3e78.tar.gz
upstream-7475321f46b83cc04296638d6cf31542d11e3e78.tar.bz2
upstream-7475321f46b83cc04296638d6cf31542d11e3e78.zip
mac80211: ath11k: Remove regulatory intersection
Currently, during initialization ath11k will receive a regulatory event from the firmware in which it will receive the default regulatory domain code and accompanying rules list and report those to the kernel. Then if you try to change the regulatory domain to a different country code it will do a weird thing in which it will send that to the FW and after receiving the appropriate regulatory event it will parse the rules. However, while its parsing there is a weird thing being done, and that is that new raw rules from FW get intersected with the rules from the default domain. This is creating a big issue as the default domain is almost always set to "US" or just "00" aka world so ath11k will unfairly limit you to the most restrictive combination of rules based on the default domain and your desired domain. For example, in ETSI countries this is causing channels 12 and 13 on 2.4GHz to not be usable since "US" limits 2.4GHz to 2472MHz instead of 2482MHz like ETSI countries do. So, lets do what TIP and even QCA do in their ath11k downstream tree and completely get rid of the interesection code in ath11k. Signed-off-by: Robert Marko <robimarko@gmail.com>
Diffstat (limited to 'package/firmware/ipq-wifi/Makefile')
0 files changed, 0 insertions, 0 deletions