summaryrefslogtreecommitdiffstats
path: root/net/mac80211/util.c
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2012-09-05 13:41:37 +0200
committerJohannes Berg <johannes.berg@intel.com>2012-09-14 14:06:51 +0200
commit04b7b2ff50fc77380c1e711f1d7223734547e41b (patch)
tree0f048db9f4324e9db134bdbbddc139df9bceffab /net/mac80211/util.c
parent3a6a0d8ee88d23e7dda28808c2c890c4db50ccb2 (diff)
downloadtalos-obmc-linux-04b7b2ff50fc77380c1e711f1d7223734547e41b.tar.gz
talos-obmc-linux-04b7b2ff50fc77380c1e711f1d7223734547e41b.zip
mac80211: handle power constraint/country IE better
Currently, mac80211 uses the power constraint IE, and reduces the regulatory max TX power by it. This can cause issues if the AP is advertising a large power constraint value matching a high TX power in its country IE, for example in this case: ... Country: US Environment: Indoor/Outdoor ... Channels [157 - 157] @ 30 dBm ... Power constraint: 13 dB ... What happened here is that our local regulatory TX power is 15 dBm, and gets reduced by 13 dB so we end up with only 2 dBm effective TX power, which is way too low. Instead, handle the country IE/power constraint IE combined and restrict our TX power to the max of the regulatory power and the maximum power advertised by the AP, in this case 17 dBm (= 30 dBm - 13 dB). Also print a message when this happens to let the user know and help us debug issues with it. Reported-by: Carl A. Cook <CACook@quantum-equities.com> Tested-by: Carl A. Cook <CACook@quantum-equities.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/mac80211/util.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud