From: Matthias Brugger <matthias.bgg@gmail.com>
To: Linux Firmware <linux-firmware@kernel.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
serge@raspberrypi.org, Phil Elwell <phil@raspberrypi.org>,
Arend van Spriel <arend@broadcom.com>,
Hans de Goede <hdegoede@redhat.com>, Takashi Iwai <tiwai@suse.de>,
Guillaume Gardet <Guillaume.Gardet@arm.com>
Subject: Re: [GIT PULL] Add NVRAM files for bcm43455 found on RPi4
Date: Wed, 4 Dec 2019 08:50:00 +0100 [thread overview]
Message-ID: <7e2fd4b5-0ea0-8509-0c7c-14e0a250ce7e@gmail.com> (raw)
In-Reply-To: <b34e62bb-d217-d583-67c9-72ae7fe7b589@gmail.com>
On 27/11/2019 17:23, Matthias Brugger wrote:
> Hi Josh,
> Hi all,
>
Friendly reminder, do you have any objections to include this file to the
repository?
Regards,
Matthias
> This pull request adds the NVRAM config file for BCM43455 as needed by Raspberry
> Pi 4. The only difference to the file for RPi3 is the value of boardflags3.
>
> Please have a look and drop me a line, if you have any issues.
>
> Regards,
> Matthias
>
> ---
> The following changes since commit e8a0f4c9314754d8b2cbe9840357d88a861c438a:
>
> rtl_nic: add firmware rtl8168fp-3 (2019-11-18 16:16:01 -0500)
>
> are available in the Git repository at:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux-firmware.git
> rpi4-fw
>
> for you to fetch changes up to f93c7a18dbb3705aa1899318c3bf5d3819cd7781:
>
> brcm: Add BCM43455 NVRAM for Raspberry Pi 4 B (2019-11-27 17:12:39 +0100)
>
> ----------------------------------------------------------------
> Matthias Brugger (1):
> brcm: Add BCM43455 NVRAM for Raspberry Pi 4 B
>
> brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt | 82 +++++++++++++++++++++++
> 1 file changed, 82 insertions(+)
> create mode 100644 brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
>
next prev parent reply other threads:[~2019-12-04 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 16:23 [GIT PULL] Add NVRAM files for bcm43455 found on RPi4 Matthias Brugger
2019-12-04 7:50 ` Matthias Brugger [this message]
2019-12-15 12:26 ` 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=7e2fd4b5-0ea0-8509-0c7c-14e0a250ce7e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Guillaume.Gardet@arm.com \
--cc=arend@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phil@raspberrypi.org \
--cc=serge@raspberrypi.org \
--cc=tiwai@suse.de \
/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).