ath5k: clarify logic when to enable spur mitigation filter
authorBruno Randolf <br1@einfach.org>
Wed, 19 May 2010 01:31:21 +0000 (10:31 +0900)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 2 Jun 2010 20:13:25 +0000 (16:13 -0400)
commit30bd3a3092c17dbfa18f042ca0815758e8d34e65
treecacb13fb1c894ab67479f3138b5a5124629ea91d
parent230fc4f3b2fa72980787a5f86c850f02bb193187
ath5k: clarify logic when to enable spur mitigation filter

The old code logically did not make sense and seems to have been confused by
the fact that we could have newer EEPROMs on older hardware. In any case the
spur mitigation filter was set if the srev was >= AR5K_SREV_AR5424.

Spur info is available only from EEPROM versions bigger than 5.3 but but the
EEPOM routines will use static values for older versions, so that should be
o.k.

Signed-off-by: Bruno Randolf <br1@einfach.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath/ath5k/reset.c