linux-kernel - Re: [PATCH 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <2CFE1145-8C00-4529-B4A5-E9FA85D95398@zzywysm.com>
Date:   Tue, 3 Jan 2023 14:59:20 -0500
From:   Zzy Wysm <zzy@...wysm.com>
To:     Arend van Spriel <arend.vanspriel@...adcom.com>
Cc:     Hector Martin <marcan@...can.st>,
        Aditya Garg <gargaditya08@...e.com>, aspriel@...il.com,
        hante.meuleman@...adcom.com, kvalo@...nel.org, davem@...emloft.net,
        edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
        lina@...hilina.net, franky.lin@...adcom.com,
        Orlando Chamberlain <redecorating@...tonmail.com>,
        brcm80211-dev-list@...adcom.com,
        brcm80211-dev-list.pdl@...adcom.com,
        linux-wireless@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Asahi Linux <asahi@...ts.linux.dev>
Subject: Re: [PATCH 1/2] brcmfmac: Use separate struct to declare firmware
 names for Apple OTP chips

> On Jan 3, 2023, at 8:30 AM, Arend van Spriel <arend.vanspriel@...adcom.com> wrote:
> 
> 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?
> 
> 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 “who knows”?

I guess the difference is that the FCC has the statutory authority to yank Broadcom’s 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