diff options
| author | Bruno Randolf <br1@einfach.org> | 2010-04-12 16:38:52 +0900 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2010-04-14 14:52:42 -0400 |
| commit | 87d77c4ef132599eb3a6c49520719d39f7341efd (patch) | |
| tree | 9b353e63a5fa50b6fc58b5cbf20a395166da4f5d /Documentation | |
| parent | 0edc9a6709d8e7d4f26c7f2a4b5ebdb641f8dfa0 (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 'Documentation')
0 files changed, 0 insertions, 0 deletions