From: Kalle Valo <kvalo@kernel.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Aditya Garg <gargaditya08@live.com>,
Arend van Spriel <aspriel@gmail.com>,
Hector Martin <marcan@marcan.st>, Janne Grunau <j@jannau.net>,
Orlando Chamberlain <orlandoch.dev@gmail.com>,
<stable@vger.kernel.org>, <linux-wireless@vger.kernel.org>,
<brcm80211@lists.linux.dev>,
<brcm80211-dev-list.pdl@broadcom.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wifi: brcmfmac: use random seed flag for BCM4355 and BCM4364 firmware
Date: Mon, 20 Jan 2025 20:01:41 +0200 [thread overview]
Message-ID: <87tt9tjrei.fsf@kernel.org> (raw)
In-Reply-To: <19484c927b8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (Arend Van Spriel's message of "Mon, 20 Jan 2025 18:36:03 +0100")
Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
> On January 20, 2025 5:50:56 PM Aditya Garg <gargaditya08@live.com> wrote:
>
>> From: Aditya Garg <gargaditya08@live.com>
>>
>> Before 6.13, random seed to the firmware was given based on the logic
>> whether the device had valid OTP or not, and such devices were found
>> mainly on the T2 and Apple Silicon Macs. In 6.13, the logic was changed,
>> and the device table was used for this purpose, so as to cover the special
>> case of BCM43752 chip.
>>
>> During the transition, the device table for BCM4364 and BCM4355 Wi-Fi chips
>> which had valid OTP was not modified, thus breaking Wi-Fi on these devices.
>> This patch adds does the necessary changes, similar to the ones done for
>> other chips.
>>
>> Fixes: ea11a89c3ac6 ("wifi: brcmfmac: add flag for random seed
>> during firmware download")
>> Cc: stable@vger.kernel.org
>
> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
I'll queue this to wireless tree for v6.14.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2025-01-20 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 16:50 [PATCH] wifi: brcmfmac: use random seed flag for BCM4355 and BCM4364 firmware Aditya Garg
2025-01-20 17:36 ` Arend Van Spriel
2025-01-20 18:01 ` Kalle Valo [this message]
2025-01-28 18:18 ` Kalle Valo
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=87tt9tjrei.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=gargaditya08@live.com \
--cc=j@jannau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=orlandoch.dev@gmail.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).