From: Denis Kalashnikov <denis281089@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: kvalo@codeaurora.org
Subject: [RESEND] ath9k: fix firmware bug in some of Mikrotik R11e-2HPnD cards
Date: Fri, 27 Dec 2019 13:01:15 +0300 [thread overview]
Message-ID: <20191227100115.6870-1-denis281089@gmail.com> (raw)
Sorry, first I sent the patch through a Gmail web interface, and spaces
were broken.
---
Some of the Mikrotik R11e-2HPnD cards have EEPROM where is
flashed that a card has 3 chains, but actually all this cards
have only 2. This leads ath9k to write periodically into the logs:
'ath: phy0: Unable to reset channel, reset status -5' and
stations don't see that AP.
Mikrotik R11e-2HPnD is based on AR9582 chip.
Signed-off-by: Denis Kalashnikov <denis281089@gmail.com>
---
drivers/net/wireless/ath/ath9k/ar9003_eeprom.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c b/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c
index b4885a700296..554a81400648 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c
@@ -3373,6 +3373,15 @@ static int ar9300_eeprom_restore_internal(struct ath_hw *ah,
cptr -= (COMP_HDR_LEN + osize + COMP_CKSUM_LEN);
}
+ /**
+ * Fix firmware bug of some Mikrotik R11e-2HPnD cards (based on AR9582)
+ * that claim that they have 3 chains, but actually have only 2.
+ */
+ if (AR_SREV_9580(ah)) {
+ eep = (struct ar9300_eeprom *)mptr;
+ eep->baseEepHeader.txrxMask &= 0x33;
+ }
+
kfree(word);
return cptr;
--
2.23.0
next reply other threads:[~2019-12-27 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 10:01 Denis Kalashnikov [this message]
2020-01-10 8:30 ` [RESEND] ath9k: fix firmware bug in some of Mikrotik R11e-2HPnD cards Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191227100115.6870-1-denis281089@gmail.com \
--to=denis281089@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.