Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: [PATCH 1/2] brcmfmac: Use separate struct to declare firmware
 names for Apple OTP chips
From:   Zzy Wysm <zzy@zzywysm.com>
In-Reply-To: <6b30559d-9bcc-f3b3-d9b2-2406e9a044b7@broadcom.com>
Date:   Tue, 3 Jan 2023 14:59:20 -0500
Cc:     Hector Martin <marcan@marcan.st>,
        Aditya Garg <gargaditya08@live.com>, aspriel@gmail.com,
        hante.meuleman@broadcom.com, kvalo@kernel.org, davem@davemloft.net,
        edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
        lina@asahilina.net, franky.lin@broadcom.com,
        Orlando Chamberlain <redecorating@protonmail.com>,
        brcm80211-dev-list@broadcom.com,
        brcm80211-dev-list.pdl@broadcom.com,
        linux-wireless@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>,
        Asahi Linux <asahi@lists.linux.dev>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CFE1145-8C00-4529-B4A5-E9FA85D95398@zzywysm.com>
References: <F8829A7C-909E-4A1F-A22C-668220C5C06D@live.com>
 <f36dd8e3-9905-f04a-ed34-4be91ed1fec6@marcan.st>
 <F9EFCCD1-4407-42CC-8316-2F58AAC1AE7F@live.com>
 <ACC0D1F6-7857-4FF0-A474-4EC699572E1B@live.com>
 <9c5bdb0a-0877-ed16-f09f-164a9dab16d4@marcan.st>
 <18573bd1a38.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <3785835b-164b-28d1-6905-85454cabb69d@marcan.st>
 <6b30559d-9bcc-f3b3-d9b2-2406e9a044b7@broadcom.com>
To:     Arend van Spriel <arend.vanspriel@broadcom.com>
Precedence: bulk


> On Jan 3, 2023, at 8:30 AM, Arend van Spriel =
<arend.vanspriel@broadcom.com> wrote:
>=20
> On 1/3/2023 4:55 AM, Hector Martin wrote:
>> More specifically:
>> - What BCM4355 variants exist in the wild, and what are their PCI =
device
>> IDs and revision IDs?
>=20
> Who knows. The PCI revision ID always equals the chip revision afaik. =
The PCI device IDs should be as below.

If the day ever came where the FCC inquired about a theoretical spurious =
radio emissions issue in such a chipset, and asked Broadcom for a list =
of all affected hardware releases, would the FCC also be told =E2=80=9Cwho=
 knows=E2=80=9D?

I guess the difference is that the FCC has the statutory authority to =
yank Broadcom=E2=80=99s certifications to sell their product, whereas =
Hector is merely improving your driver support for no monetary =
compensation from you.

Maybe the Broadcom drivers should be yanked from Linux if this is what =
passes for Broadcom release engineering.

zzy