[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BA494267-7B5A-4042-BD33-44F62837C8DB@live.com>
Date: Mon, 2 Jan 2023 14:34:17 +0000
From: Aditya Garg <gargaditya08@...e.com>
To: Hector Martin <marcan@...can.st>
CC: Arend van Spriel <arend.vanspriel@...adcom.com>,
Ian Lin <ian.lin@...ineon.com>,
"alep@...ress.com" <alep@...ress.com>,
"brcm80211-dev-list@...adcom.com" <brcm80211-dev-list@...adcom.com>,
"brcm80211-dev-list@...ress.com" <brcm80211-dev-list@...ress.com>,
"franky.lin@...adcom.com" <franky.lin@...adcom.com>,
"hante.meuleman@...adcom.com" <hante.meuleman@...adcom.com>,
"kvalo@...nel.org" <kvalo@...nel.org>,
"Double.Lo@...ineon.com" <Double.Lo@...ineon.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Asahi Linux <asahi@...ts.linux.dev>
Subject: Re: [PATCH v2 2/4] brcmfmac: Support 89459 pcie
> 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
Powered by blists - more mailing lists