aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/ath/ath5k/base.h
diff options
context:
space:
mode:
authorBruno Randolf <br1@einfach.org>2010-04-12 03:38:52 -0400
committerJohn W. Linville <linville@tuxdriver.com>2010-04-14 14:52:42 -0400
commit87d77c4ef132599eb3a6c49520719d39f7341efd (patch)
tree9b353e63a5fa50b6fc58b5cbf20a395166da4f5d /drivers/net/wireless/ath/ath5k/base.h
parent0edc9a6709d8e7d4f26c7f2a4b5ebdb641f8dfa0 (diff)
ath5k: treat RXORN as non-fatal
We get RXORN interrupts when all receive buffers are full. This is not necessarily a fatal situation. It can also happen when the bus is busy or the CPU is not fast enough to process all frames. Older chipsets apparently need a reset to come out of this situration, but on newer chips we can treat RXORN like RX, as going thru a full reset does more harm than good, there. The exact chip revisions which need a reset are unknown - this guess AR5K_SREV_AR5212 ("venice") is copied from the HAL. Inspired by openwrt 413-rxorn.patch: "treat rxorn like rx, reset after rxorn seems to do more harm than good" Signed-off-by: Bruno Randolf <br1@einfach.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/ath/ath5k/base.h')
-rw-r--r--drivers/net/wireless/ath/ath5k/base.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath5k/base.h b/drivers/net/wireless/ath/ath5k/base.h
index 53a5651c57a2..56221bc7c8cd 100644
--- a/drivers/net/wireless/ath/ath5k/base.h
+++ b/drivers/net/wireless/ath/ath5k/base.h
@@ -135,6 +135,7 @@ struct ath5k_statistics {
135 unsigned int beacons; 135 unsigned int beacons;
136 136
137 unsigned int mib_intr; 137 unsigned int mib_intr;
138 unsigned int rxorn_intr;
138}; 139};
139 140
140#if CHAN_DEBUG 141#if CHAN_DEBUG