From: Aditya Garg <gargaditya08@live.com>
To: Hector Martin <marcan@marcan.st>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Orlando Chamberlain <redecorating@protonmail.com>,
"arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>,
"aspriel@gmail.com" <aspriel@gmail.com>,
"ranky.lin@broadcom.com" <ranky.lin@broadcom.com>,
"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"lina@asahilina.net" <lina@asahilina.net>
Subject: Re: [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel 6.1
Date: Mon, 2 Jan 2023 08:57:57 +0000 [thread overview]
Message-ID: <F9EFCCD1-4407-42CC-8316-2F58AAC1AE7F@live.com> (raw)
In-Reply-To: <f36dd8e3-9905-f04a-ed34-4be91ed1fec6@marcan.st>
> 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?
next prev parent reply other threads:[~2023-01-02 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 7:46 Aditya Garg
2023-01-02 8:21 ` Linux kernel regression tracking (#info)
2023-01-02 10:27 ` Thorsten Leemhuis
2023-01-02 8:47 ` Hector Martin
2023-01-02 8:57 ` Aditya Garg [this message]
2023-01-02 9:13 ` Hector Martin
2023-01-02 14:40 ` [PATCH 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Aditya Garg
2023-01-02 14:41 ` [PATCH 2/2] brcmfmac: Add PCIe ID of BCM4355 chip found on T2 Macs Aditya Garg
2023-01-02 14:46 ` Aditya Garg
2023-01-03 2:08 ` kernel test robot
2023-01-02 14:46 ` [PATCH v2 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Aditya Garg
2023-01-02 14:48 ` [PATCH v2 2/2] brcmfmac: Add PCIe ID of BCM4355 chip found on T2 Macs Aditya Garg
2023-01-02 15:15 ` [PATCH 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Hector Martin
2023-01-02 15:24 ` Aditya Garg
2023-01-02 18:27 ` Arend Van Spriel
2023-01-03 3:55 ` Hector Martin
2023-01-03 13:30 ` Arend van Spriel
2023-01-03 13:46 ` Hector Martin
2023-01-04 9:32 ` Arend van Spriel
2023-01-03 19:59 ` Zzy Wysm
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=F9EFCCD1-4407-42CC-8316-2F58AAC1AE7F@live.com \
--to=gargaditya08@live.com \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hante.meuleman@broadcom.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=pabeni@redhat.com \
--cc=ranky.lin@broadcom.com \
--cc=redecorating@protonmail.com \
/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
all inboxes | Powered by JetHome®