summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorJohannes Berg2014-05-09 09:56:53 +0200
committerJohannes Berg2014-05-09 09:56:53 +0200
commit4a817aa78f573c6964f16d9aea3d0d10a226ade4 (patch)
treed1dbb605ccfad90290cf4ea19b17931e75a9f8b0 /net/bluetooth
parentmac80211: fix nested rtnl locking on ieee80211_reconfig (diff)
downloadkernel-qcow2-linux-4a817aa78f573c6964f16d9aea3d0d10a226ade4.tar.gz
kernel-qcow2-linux-4a817aa78f573c6964f16d9aea3d0d10a226ade4.tar.xz
kernel-qcow2-linux-4a817aa78f573c6964f16d9aea3d0d10a226ade4.zip
mac80211: allow VHT with peers not capable of 40MHz
There are two (related) issues with this. One case, reported by Michal, is related to hostap: it unsets the 20/40 capability bit for stations that associate when it's in 20 MHz mode. The other case, reported by Eyal, is that some APs like Netgear R6300v2 and probably others based on the BCM4360 chipset can be configured for doing VHT at 20Mhz. In this case the beacon has a VHT IE but the HT cap indicates transmitter only support 20Mhz. In both of these cases, we currently avoid VHT and use only HT this means we can't use the highest rates (MCS8), so fixing this leads to throughput improvements. Reported-by: Michal Kazior <michal.kazior@tieto.com> Reported-by: Eyal Shapira <eyal@wizery.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions