From: Linus Walleij <linus.walleij@linaro.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Alvin Šipraga" <ALSI@bang-olufsen.dk>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Hector Martin" <marcan@marcan.st>,
"~postmarketos/upstreaming@lists.sr.ht"
<~postmarketos/upstreaming@lists.sr.ht>,
"martin.botka@somainline.org" <martin.botka@somainline.org>,
"angelogioacchino.delregno@somainline.org"
<angelogioacchino.delregno@somainline.org>,
"marijn.suijten@somainline.org" <marijn.suijten@somainline.org>,
"jamipkettunen@somainline.org" <jamipkettunen@somainline.org>,
"Arend van Spriel" <aspriel@gmail.com>,
"Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Marek Vasut" <marex@denx.de>,
"Zhao, Jiaqing" <jiaqing.zhao@intel.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
"Soon Tak Lee" <soontak.lee@cypress.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"SHA-cyfmac-dev-list@infineon.com"
<SHA-cyfmac-dev-list@infineon.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Stockholm syndrome with Linux wireless?
Date: Thu, 20 Oct 2022 16:09:36 +0200 [thread overview]
Message-ID: <CACRpkdYmXDCADH6-5KvdTZFFgTLRsw5U7zO2EtK-cN4E2BgOYw@mail.gmail.com> (raw)
In-Reply-To: <87wn9q35tp.fsf_-_@kernel.org>
On Mon, Sep 26, 2022 at 10:20 AM Kalle Valo <kvalo@kernel.org> wrote:
> Linus Walleij <linus.walleij@linaro.org> writes:
> > On Thu, Sep 22, 2022 at 3:31 PM Alvin Šipraga <ALSI@bang-olufsen.dk> wrote:
> >
> >> I would also point out that the BCM4359 is equivalent to the
> >> CYW88359/CYW89359 chipset, which we are using in some of our
> >> products. Note that this is a Cypress chipset (identifiable by the
> >> Version: ... (... CY) tag in the version string). But the FW Konrad is
> >> linking appears to be for a Broadcom chipset.
> >
> > This just makes me think about Peter Robinsons seminar at
> > LPC last week...
> > "All types of wireless in Linux are terrible and why the vendors
> > should feel bad"
> > https://lpc.events/event/16/contributions/1278/attachments/1120/2153/wireless-issues.pdf
>
> Thanks, this was a good read! I'm always interested about user and
> downstream feedback, both good and bad :) But I didn't get the Stockholm
> syndrome comment in the end, what does he mean with that?
>
> BTW we have a wireless workshop in netdevconf 0x16, it would be great to
> have there a this kind of session discussing user pain points:
I can't go to Lisbon, but my personal pain points are all this:
https://openwrt.org/meta/infobox/broadcom_wifi
and I think I'm not alone, but I can't speak for OpenWrt.
The lack of support in b43 for modern phys such as AC, i.e. the gap
between b43 and brcmfmac, is extremely annoying and turning perfectly
fine aftermarket devices into paperweights because there isn't even
a way to make Broadcoms old proprietary blob work with contemporary
kernels.
If Broadcom could be convinced to either add support for the late b43
variants or at least release documentation for the aftermarket that
would be great.
I suppose they might be coming to the conference so give them my best
regards with a "please fix" tag attached.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-10-20 14:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 0:16 [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Konrad Dybcio
2022-09-21 4:37 ` Hector Martin
2022-09-21 21:26 ` Konrad Dybcio
2022-09-22 6:40 ` Hector Martin
2022-09-22 10:21 ` Konrad Dybcio
2022-09-22 13:02 ` Linus Walleij
2022-09-22 13:08 ` Hector Martin
2022-09-22 13:30 ` Alvin Šipraga
2022-09-22 20:18 ` Linus Walleij
2022-09-26 8:20 ` Stockholm syndrome with Linux wireless? Kalle Valo
2022-09-26 8:59 ` Russell King (Oracle)
2022-10-03 19:40 ` Linus Walleij
2022-10-20 14:09 ` Linus Walleij [this message]
2022-10-20 14:44 ` Dave Taht
2022-09-26 9:27 ` [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Kalle Valo
2022-11-18 16:47 ` Konrad Dybcio
2022-11-21 13:56 ` Linus Walleij
2022-11-25 11:42 ` Konrad Dybcio
2022-11-25 11:53 ` Kalle Valo
2022-11-25 12:10 ` Konrad Dybcio
2022-11-25 12:25 ` Kalle Valo
2022-11-26 21:45 ` Linus Walleij
2022-11-28 11:17 ` Kalle Valo
2022-11-28 14:40 ` Konrad Dybcio
2022-11-29 9:19 ` Krzysztof Kozlowski
2022-12-01 11:31 ` Arend van Spriel
2022-12-02 10:33 ` Konrad Dybcio
2022-12-02 15:26 ` Arend van Spriel
2022-12-02 19:28 ` Arend Van Spriel
2022-12-06 9:58 ` Konrad Dybcio
2022-12-06 11:22 ` Arend van Spriel
2022-12-07 10:12 ` Konrad Dybcio
2022-12-06 23:37 ` Linus Walleij
2022-12-07 7:41 ` Arend Van Spriel
2022-12-07 13:42 ` Linus Walleij
2022-12-07 22:26 ` Arend van Spriel
2022-12-07 8:57 ` Konrad Dybcio
2022-12-07 11:10 ` Arend van Spriel
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=CACRpkdYmXDCADH6-5KvdTZFFgTLRsw5U7zO2EtK-cN4E2BgOYw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ALSI@bang-olufsen.dk \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=jamipkettunen@somainline.org \
--cc=jiaqing.zhao@intel.com \
--cc=konrad.dybcio@somainline.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=marex@denx.de \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=soontak.lee@cypress.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).