[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b472677f-c556-99a4-eef7-f3cbdc8f64c1@marcan.st>
Date: Mon, 2 Jan 2023 18:13:41 +0900
From: Hector Martin <marcan@...can.st>
To: Aditya Garg <gargaditya08@...e.com>
Cc: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"brcm80211-dev-list.pdl@...adcom.com"
<brcm80211-dev-list.pdl@...adcom.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Orlando Chamberlain <redecorating@...tonmail.com>,
"arend.vanspriel@...adcom.com" <arend.vanspriel@...adcom.com>,
"aspriel@...il.com" <aspriel@...il.com>,
"hante.meuleman@...adcom.com" <hante.meuleman@...adcom.com>,
"kvalo@...nel.org" <kvalo@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"lina@...hilina.net" <lina@...hilina.net>
Subject: Re: [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel
6.1
On 2023/01/02 17:57, Aditya Garg wrote:
>
>> You are using a downstream patched tree, specifically one with further
>> Broadcom patches not yet upstream from my Asahi Linux tree and probably
>> others.
>>
>> Please do not spam upstream developers with issues from downstream
>> trees. If you have an issue with my tree, you can report it on GitHub.
>> If you are using another tree, report it to its maintainer. If you can
>> reproduce this with *vanilla* 6.1 then you can report it upstream.
>>
>> - Hector
>
> I am sorry for the same Hector, but I sent that cause bcm4364 wifi chip is already supported upstream. If I ain't wrong, don't the Asahi Linux patches provide OTP support only for these chips?
There are a pile of Broadcom patches in our tree and there is no way to
eliminate them as the cause a priori. If you think this regressed
upstream, then test it with upstream Linux 6.1 and find out.
As I mentioned to you on Discord previously, please bisect this to a
specific commit so we can do something about it. I don't have the
hardware and there's nothing I can do with a "the firmware is crashing
now" report until you at least tell me what commit caused the problem so
I can take a stab at identifying the root cause.
- Hector
Powered by blists - more mailing lists