linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@kernel.org>
To: matthias.bgg@kernel.org
Cc: Linux Firmware <linux-firmware@kernel.org>,
	ruud@veniogames.com,  Peter Robinson <pbrobinson@gmail.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	 Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH] brcm: Fix Raspberry Pi 4B NVRAM file
Date: Wed, 3 Mar 2021 13:24:25 -0500	[thread overview]
Message-ID: <CA+5PVA59eD=R0W1UZFBSo5AVPCE9X35BGCjY0nDNYNs63A336A@mail.gmail.com> (raw)
In-Reply-To: <20210216193523.32321-1-matthias.bgg@kernel.org>

Applied and pushed out.

josh

On Tue, Feb 16, 2021 at 2:35 PM <matthias.bgg@kernel.org> wrote:
>
> From: Matthias Brugger <mbrugger@suse.com>
>
> NVRAM file set's boarflags3 to 0x48200100 which indicates the firmware
> that an external LPO is present. But on the RPi4 no external LPO exists.
>
> Fixes: 870b805 ("brcm: Update Raspberry Pi 3B+/4B NVRAM for downstream changes")
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
> ---
>  brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt b/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
> index d5bd530..8dda168 100644
> --- a/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
> +++ b/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
> @@ -7,7 +7,7 @@ aa5g=1
>  AvVmid_c0=1,165,2,100,2,100,2,100,2,100
>  boardflags=0x00480201
>  boardflags2=0x40800000
> -boardflags3=0x48200100
> +boardflags3=0x44200100
>  boardrev=0x1304
>  boardtype=0x6e4
>  btc_mode=1
> --
> 2.30.0
>

      reply	other threads:[~2021-03-03 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 19:35 matthias.bgg
2021-03-03 18:24 ` Josh Boyer [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='CA+5PVA59eD=R0W1UZFBSo5AVPCE9X35BGCjY0nDNYNs63A336A@mail.gmail.com' \
    --to=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=matthias.bgg@kernel.org \
    --cc=mbrugger@suse.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=pbrobinson@gmail.com \
    --cc=ruud@veniogames.com \
    --subject='Re: [PATCH] brcm: Fix Raspberry Pi 4B NVRAM file' \
    /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

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).