From: Florian Fainelli <f.fainelli@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Hector Martin <marcan@marcan.st>, Kalle Valo <kvalo@kernel.org>,
Neal Gompa <neal@gompa.dev>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
SHA-cyfmac-dev-list@infineon.com,
brcm80211-dev-list.pdl@broadcom.com,
Asahi Linux <asahi@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Julian Calaby <julian.calaby@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: On brcm80211 maintenance and support
Date: Thu, 12 Oct 2023 09:25:45 -0700 [thread overview]
Message-ID: <9b5e8c02-31fc-43c8-bac6-d84f540f2407@gmail.com> (raw)
In-Reply-To: <14ce82c5-f807-59bd-30ec-7eff5066e4f0@broadcom.com>
On 10/12/23 01:41, Arend van Spriel wrote:
[snip]
>> I have a patch to enable WPA3 in Broadcom chipsets (yes, the driver is
>> in such a sorry state it doesn't even support that yet). The current
>> support attempt was added by a Cypress engineer and uses a completely
>> different firmware mechanism. Is that supposed to actually work? Does it
>> work currently? Is that the case for all Cypress firmwares? Or only
>> some? Does the alternate mechanism we have for Broadcom chips work too?
>> Only Cypress can answer those questions ahead of time, and they aren't
>> (they ignored me last time I brought this up). So my current patch just
>> replaces the mechanism with the known-working one for Broadcom chips.
>
> This is mainly why I introduced the vendor-split concept so we can keep
> the Cypress mechanism and allow a different mechanism for Broadcom
> chips. The Cypress mechanism did not work for the Broadcom chips I have
> so I wanted to test it on the Cypress chips I got shipped long ago and
> they simply do not come up. Have not tried with RPi as it is not running
> vanilla kernel. Could try with a backports driver.
You can run mainline on all of the Raspberry Pi devices, as far as Wi-Fi
is concerned I cannot think of any major roadblocks, if not, email me
privately and we can figure this one out.
--
Florian
prev parent reply other threads:[~2023-10-12 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f78e624-62ee-3ae5-1db4-a0411566def8@yandex.ru>
[not found] ` <CAGRGNgU7aySyUny9aG_+wXiKJ7j1weosa-rZDY4_WAXbq-3ABg@mail.gmail.com>
[not found] ` <87ttr454bh.fsf@kernel.org>
2023-10-06 15:34 ` On brcm80211 maintenance and support Hector Martin
2023-10-06 15:48 ` Dmitry Antipov
2023-10-07 12:50 ` Hector Martin
2023-10-10 14:52 ` Neal Gompa
2023-10-10 15:35 ` Phil Elwell
2023-10-11 10:32 ` Kalle Valo
2023-10-11 10:45 ` Phil Elwell
2023-10-11 10:23 ` Kalle Valo
2023-10-11 11:28 ` Hector Martin
2023-10-11 11:47 ` Phil Elwell
2023-10-12 8:41 ` Arend van Spriel
2023-10-12 16:25 ` Florian Fainelli [this message]
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=9b5e8c02-31fc-43c8-bac6-d84f540f2407@gmail.com \
--to=f.fainelli@gmail.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dmantipov@yandex.ru \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=julian.calaby@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=phil@raspberrypi.org \
--cc=torvalds@linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).