If we have a zeroed frequency on the calibration piers it means that we
shouldn't use that pier, not stop reading the EEPROM and break out from
the loop. By doing that we return the wrong offset and the whole dataset
gets corrupted.
Signed-off-by: Nick Kossifidis <mickfl...@gmail.com>
Tested-by: Thomas Huehn <tho...@net.t-labs.tu-berlin.de>
---
drivers/net/wireless/ath/ath5k/eeprom.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath5k/eeprom.c
b/drivers/net/wireless/ath/ath5k/eeprom.c
index 4026c90..10a4396 100644
--- a/drivers/net/wireless/ath/ath5k/eeprom.c
+++ b/drivers/net/wireless/ath/ath5k/eeprom.c
@@ -522,7 +522,7 @@ ath5k_eeprom_read_freq_list(struct ath5k_hw *ah, int
*offset, int max,
freq1 = val & 0xff;
if (!freq1)
- break;
+ continue;
pc[i++].freq = ath5k_eeprom_bin2freq(ee,
freq1, mode);
@@ -530,7 +530,7 @@ ath5k_eeprom_read_freq_list(struct ath5k_hw *ah, int
*offset, int max,
freq2 = (val >> 8) & 0xff;
if (!freq2)
- break;
+ continue;
pc[i++].freq = ath5k_eeprom_bin2freq(ee,
freq2, mode);
--
1.7.3.4
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
