From: Josh Boyer <jwboyer@kernel.org>
To: Michel Piquemal <spam@ipik.org>
Cc: Linux Firmware <linux-firmware@kernel.org>
Subject: Re: brcm: add missing symlink for Pi Zero W NVRAM file
Date: Wed, 21 Apr 2021 07:23:04 -0400 [thread overview]
Message-ID: <CA+5PVA5Zs8iX77chTnZfw38OHbV+Y4G0ib3B-2_+O4oGv9ERzg@mail.gmail.com> (raw)
In-Reply-To: <0c5cfa45-1bc6-3f63-435b-5281529457d4@ipik.org>
On Mon, Apr 19, 2021 at 1:38 PM Michel Piquemal <spam@ipik.org> wrote:
>
> Raspberry Pi Zero W has no NVRAM files specified and dmesg reports the
> following error at boot:
> brcmfmac mmc1:0001:1: Direct firmware load for
> brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt failed with error -2
>
> Pi Zero W uses same wifi BCM43430 module than Pi 3 model B:
> symlinking to that Pi 3b NVRAM file fixes the issue, and wifi works as
> expected.
>
> Signed-off-by: Michel Piquemal <spam@ipik.org>
>
>
> --- a/WHENCE
> +++ b/WHENCE
> @@ -2771,6 +2771,7 @@ Link: brcm/brcmfmac43430-sdio.sinovoip,b
> File: "brcm/brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt"
> File: "brcm/brcmfmac43430-sdio.MUR1DX.txt"
> File: "brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt"
> +Link: brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt ->
> brcmfmac43430-sdio.raspberrypi,3-model-b.txt
> File: "brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt"
> Link: brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt ->
> brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
> File: "brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt"
Your patch is corrupted and doesn't apply. Please update your local
tree to the latest in git and resend.
josh
next prev parent reply other threads:[~2021-04-21 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 17:38 brcm: add missing symlink for Pi Zero W NVRAM file Michel Piquemal
2021-04-21 11:23 ` Josh Boyer [this message]
2021-04-22 17:47 ` Michel Piquemal
2021-04-23 11:05 ` Josh Boyer
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=CA+5PVA5Zs8iX77chTnZfw38OHbV+Y4G0ib3B-2_+O4oGv9ERzg@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=spam@ipik.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 NNTP newsgroup(s).