diff options
author | Dan Halperin <dhalperi@cs.washington.edu> | 2010-02-18 22:01:39 -0800 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2010-02-19 15:35:29 -0500 |
commit | 5e2f75b8993a0d83d469388b50716dd5551f2eb4 (patch) | |
tree | f1e3de04fb2fd6394af553a95700f1a552e6df92 /Makefile | |
parent | 5affcd6ba2036b59a4dee3f0576ae3584e92e4f1 (diff) | |
download | kernel_samsung_aries-5e2f75b8993a0d83d469388b50716dd5551f2eb4.zip kernel_samsung_aries-5e2f75b8993a0d83d469388b50716dd5551f2eb4.tar.gz kernel_samsung_aries-5e2f75b8993a0d83d469388b50716dd5551f2eb4.tar.bz2 |
iwlwifi: set HT flags after channel in rxon
The HT extension channel settings require priv->staging_rxon.channel to be
accurate. However, iwl_set_rxon_ht was being called before iwl_set_rxon_channel
and thus HT40 could be broken unless another call to iwl_mac_config came in.
This problem was recently introduced by "iwlwifi: Fix to set correct ht
configuration"
The particular setting in which I noticed this was monitor mode:
iwconfig wlan0 mode monitor
ifconfig wlan0 up
./iw wlan0 set channel 64 HT40-
#./iw wlan0 set channel 64 HT40-
tcpdump -i wlan0 -y IEEE802_11_RADIO
would only catch HT40 packets if I issued the IW command twice.
From visual inspection, iwl_set_rxon_channel does not depend on
iwl_set_rxon_ht, so simply swapping them should be safe and fixes this problem.
Signed-off-by: Daniel Halperin <dhalperi@cs.washington.edu>
Acked-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
CC: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions