From: Diederik de Haas <didi.debian@cknow.org>
To: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org
Cc: Diederik de Haas <didi.debian@cknow.org>,
1032367@bugs.debian.org, Marc <dkm+reportbug@kataplop.net>
Subject: Re: brcm/brcmfmac4356-pcie.bin failed with error -2
Date: Fri, 10 Mar 2023 17:31:39 +0100 [thread overview]
Message-ID: <5417930.k8YVOmb3Wj@prancing-pony> (raw)
In-Reply-To: <2716728.5R3jveeIG6@prancing-pony>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Thursday, 9 March 2023 19:17:10 CET Diederik de Haas wrote:
> In https://bugs.debian.org/1032367 we have a user who reported that the
> brcm/brcmfmac4356-pcie.bin firmware file failed to load with a new firmware-
> brcm80211 package, while it succeeded with an old one.
>
> In
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> / I found 2 commits that seem relevant:
> - 04f71fe564552c22dc7ece0d2b8afc11b33de392 where various cypress firmware
> and clm_blob files (including 4356) were added to the *cypress* directory.
> - 0f0aefd733f70beae4c0246edbd2c158d5ce974c which removed old brcm firmware
> files that have a newer cypress variant ... from the *brcm* directory.
>
> So in essence a bunch of firmware files were moved from 'brcm' dir to
> 'cypress'.
>
> I don't know how the firmware file loading mechanism works, but could it be
> that it (also) needs to look in the new (cypress) location for those files?
I am now reasonably certain that that is indeed the issue.
I asked the reporter of the issue to create symlinks and that 'fixed' it:
On Friday, 10 March 2023 13:07:22 CET dkm@kataplop.net wrote:
> March 10, 2023 10:57 AM, "Diederik de Haas" <didi.debian@cknow.org> wrote:
> > I'm 99% sure this would be a *workaround*, but let's verify anyway:
> > In the /lib/firmware directory, create a symlink from
> > brcm/brcmfmac4356-pcie.bin to cypress/cyfmac4356-pcie.bin
>
> As expected, it works with the symlink :)
AFAICT in drivers/net/wireless/broadcom/brcm80211/brcmfmac/ there is pcie.c
and firmware.[c|h] and it uses BRCMF_FW_DEFAULT_PATH (="brcm/") to construct
the location of the firmware files.
Now that several firmware files are stored in a different directory ('cypress')
and also have a different file 'prefix' ('cyfmac') the firmware files that are
stored in/moved to the cypress directory are no longer found.
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-03-10 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 18:17 brcm/brcmfmac4356-pcie.bin failed with error -2 Diederik de Haas
2023-03-10 16:31 ` Diederik de Haas [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=5417930.k8YVOmb3Wj@prancing-pony \
--to=didi.debian@cknow.org \
--cc=1032367@bugs.debian.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dkm+reportbug@kataplop.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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