From: Aditya Garg <gargaditya08@live.com>
To: Hector Martin <marcan@marcan.st>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Ian Lin <ian.lin@infineon.com>,
"alep@cypress.com" <alep@cypress.com>,
"brcm80211-dev-list@broadcom.com"
<brcm80211-dev-list@broadcom.com>,
"brcm80211-dev-list@cypress.com" <brcm80211-dev-list@cypress.com>,
"franky.lin@broadcom.com" <franky.lin@broadcom.com>,
"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"Double.Lo@infineon.com" <Double.Lo@infineon.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Asahi Linux <asahi@lists.linux.dev>
Subject: Re: [PATCH v2 2/4] brcmfmac: Support 89459 pcie
Date: Mon, 2 Jan 2023 14:34:17 +0000 [thread overview]
Message-ID: <BA494267-7B5A-4042-BD33-44F62837C8DB@live.com> (raw)
In-Reply-To: <6e204026-d102-6d81-f58b-f4340e7d07ac@marcan.st>
> I think he's proposing we special-case Apple chips into their own
> firmware table just to avoid colliding with non-Apple firmware usage,
> which is honestly kind of tempting as the safe option if nobody from the
> Broadcom/Cypress side is willing to clarify what, exactly, is the
> relationship between these chips and what their respective revision
> numbers are so we can *correctly* represent them and avoid further
> confusion and problems down the line.
Exactly
>
> You might be able to help with that ;)
I am sending the patch.
>
> - Hector
prev parent reply other threads:[~2023-01-02 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220922104140.11889-1-ian.lin@infineon.com>
[not found] ` <20220922104140.11889-3-ian.lin@infineon.com>
2022-10-17 12:38 ` Hector Martin
2023-01-02 9:45 ` Aditya Garg
2023-01-02 13:58 ` Arend van Spriel
2023-01-02 14:01 ` Hector Martin
2023-01-02 14:34 ` Aditya Garg [this message]
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=BA494267-7B5A-4042-BD33-44F62837C8DB@live.com \
--to=gargaditya08@live.com \
--cc=Double.Lo@infineon.com \
--cc=alep@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian.lin@infineon.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®