aboutsummaryrefslogtreecommitdiffstats
path: root/package/madwifi/patches-testing/313-reset_channelchange.patch
diff options
context:
space:
mode:
Diffstat (limited to 'package/madwifi/patches-testing/313-reset_channelchange.patch')
-rw-r--r--package/madwifi/patches-testing/313-reset_channelchange.patch18
1 files changed, 18 insertions, 0 deletions
diff --git a/package/madwifi/patches-testing/313-reset_channelchange.patch b/package/madwifi/patches-testing/313-reset_channelchange.patch
new file mode 100644
index 0000000000..42d18ece07
--- /dev/null
+++ b/package/madwifi/patches-testing/313-reset_channelchange.patch
@@ -0,0 +1,18 @@
+--- a/ath/if_ath.c
++++ b/ath/if_ath.c
+@@ -8866,14 +8866,7 @@
+ hchan.channel,
+ jiffies);
+
+- /* ath_hal_reset with chanchange = AH_TRUE doesn't seem to
+- * completely reset the state of the card. According to
+- * reports from ticket #1106, kismet and aircrack people they
+- * needed to do the reset with chanchange = AH_FALSE in order
+- * to receive traffic when peforming high velocity channel
+- * changes. */
+- if (!ath_hw_reset(sc, sc->sc_opmode, &hchan, AH_TRUE, &status) ||
+- !ath_hw_reset(sc, sc->sc_opmode, &hchan, AH_FALSE, &status)) {
++ if (!ath_hw_reset(sc, sc->sc_opmode, &hchan, AH_TRUE, &status)) {
+ EPRINTF(sc, "Unable to reset channel %u (%u MHz) "
+ "flags 0x%x '%s' (HAL status %u)\n",
+ ieee80211_chan2ieee(ic, chan), chan->ic_freq,