From: Peter Robinson <pbrobinson@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Justin Forbes <jforbes@fedoraproject.org>,
regressions@lists.linux.dev, linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
Hante Meuleman <hante.meuleman@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Arend van Spriel <aspriel@gmail.com>,
"Ivan T. Ivanov" <iivanov@suse.de>
Subject: Re: Regression in brcmfmac for 6.1/6.2-rc1 for SDIO devices
Date: Sat, 7 Jan 2023 03:25:56 +0000 [thread overview]
Message-ID: <CALeDE9Mzhogxm-05k9gk7htTSkOmfyk+N0-AAwVKs2yPOmyYoQ@mail.gmail.com> (raw)
In-Reply-To: <a223d9ba-2b80-6b6d-dcad-2ca2b170b393@i2se.com>
Hi Stefan,
> > could you please provide a "bad case" file list of all firmware files
> > for the Raspberry Pi 3 B+ which worked before Linux 6.1, so i can
> > reproduce it?
> >
> > Also OpenSuSE seems to be affected [1].
>
> Ivan send out a fix, which should also work for Fedora [2].
Yes, he cc:ed me, thanks for heads up, I tested and confirmed it fixed
the issue.
Peter
next prev parent reply other threads:[~2023-01-07 3:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 1:00 Regression in brcmfmac for 6.1/6.2-rc1 for SDIO devices Peter Robinson
2022-12-31 11:11 ` Stefan Wahren
2022-12-31 14:33 ` Peter Robinson
2022-12-31 15:29 ` Stefan Wahren
2022-12-31 15:58 ` Peter Robinson
2022-12-31 16:56 ` Stefan Wahren
2023-01-06 12:09 ` Stefan Wahren
2023-01-07 3:25 ` Peter Robinson [this message]
2022-12-31 14:20 ` Linux kernel regression tracking (#info)
2023-01-09 14:34 ` Kalle Valo
2023-01-09 18:10 ` Linux kernel regression tracking (#update)
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=CALeDE9Mzhogxm-05k9gk7htTSkOmfyk+N0-AAwVKs2yPOmyYoQ@mail.gmail.com \
--to=pbrobinson@gmail.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=iivanov@suse.de \
--cc=jforbes@fedoraproject.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).