From: Lorenzo Bianconi <lorenzo@kernel.org>
To: David Bauer <mail@david-bauer.net>
Cc: nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, kvalo@codeaurora.org,
linux-wireless@vger.kernel.org, dev@andreas-ziegler.de,
Ron Asimi <ron.asimi@gmail.com>
Subject: Re: [PATCH] mt76: mt7603: add additional EEPROM chip ID
Date: Tue, 13 Oct 2020 16:32:19 +0200 [thread overview]
Message-ID: <20201013143219.GA2854@lore-desk> (raw)
In-Reply-To: <20201013142326.8361-1-mail@david-bauer.net>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
> Some newer MT7628 based routers (notably the TP-Link Archer C50 v4) are
> shipped with a chip-id of 0x7600 in the on-flash EEPROM. Add this as a
> possible valid ID.
>
> Ref: https://bugs.openwrt.org/index.php?do=details&task_id=2781
>
> Suggested-by: Ron Asimi <ron.asimi@gmail.com>
> Signed-off-by: David Bauer <mail@david-bauer.net>
> ---
> drivers/net/wireless/mediatek/mt76/mt7603/eeprom.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/mediatek/mt76/mt7603/eeprom.c b/drivers/net/wireless/mediatek/mt76/mt7603/eeprom.c
> index 3ee06e2577b8..422b9d9e8962 100644
> --- a/drivers/net/wireless/mediatek/mt76/mt7603/eeprom.c
> +++ b/drivers/net/wireless/mediatek/mt76/mt7603/eeprom.c
> @@ -141,6 +141,7 @@ static int mt7603_check_eeprom(struct mt76_dev *dev)
> switch (val) {
> case 0x7628:
> case 0x7603:
> + case 0x7600:
is it a hw bug or does this part-number really exist?
> return 0;
> default:
> return -EINVAL;
> --
> 2.28.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-10-13 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 14:23 [PATCH] mt76: mt7603: add additional EEPROM chip ID David Bauer
2020-10-13 14:32 ` Lorenzo Bianconi [this message]
2020-10-13 14:42 ` David Bauer
2020-10-13 16:00 ` Andreas Ziegler
2020-10-13 23:55 ` David Bauer
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=20201013143219.GA2854@lore-desk \
--to=lorenzo@kernel.org \
--cc=dev@andreas-ziegler.de \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=mail@david-bauer.net \
--cc=nbd@nbd.name \
--cc=ron.asimi@gmail.com \
--cc=ryder.lee@mediatek.com \
/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.