From: Matthias Brugger <mbrugger@suse.com>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Linux Firmware <linux-firmware@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
serge@raspberrypi.org, Phil Elwell <phil@raspberrypi.org>,
Arend van Spriel <arend@broadcom.com>
Subject: Re: [GIT PULL] Add NVRAM files for bcm43455 and bcm43430
Date: Mon, 14 Jan 2019 18:54:29 +0100 [thread overview]
Message-ID: <71fb2876-53d8-1fad-a0cc-df2268c705c2@suse.com> (raw)
In-Reply-To: <CA+5PVA6T=YLF_5Dk-zm03_SaTwk+1DZVWURzgtJwjCdn0uSgHg@mail.gmail.com>
Hi Josh,
On 14/01/2019 18:32, Josh Boyer wrote:
> On Mon, Jan 14, 2019 at 10:33 AM Josh Boyer <jwboyer@kernel.org> wrote:
>>
>> On Fri, Jan 11, 2019 at 7:11 AM Matthias Brugger <mbrugger@suse.com> wrote:
>>>
>>> Hi Josh,
>>> Hi all,
>>>
>>> This pull request add firmware files neede by bcm43430 for Raspberry Pi 3 Model
>>> B and bcm43455 for Raspberry Pi 3 Model B+.
>>>
>>> Please have a look and, if convenient, pull :)
>>>
>>> Best regards,
>>> Matthias
>>>
>>> ---
>>> The following changes since commit 0f22c8527439eaaf5c3fcf87b31c89445b6fa84d:
>>>
>>> Revert "amdgpu: update vega10 fw for 18.50 release" (2018-12-18 15:38:53 -0500)
>>>
>>> are available in the Git repository at:
>>>
>>>
>>> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux-firmware.git/
>>> tags/add-rpi-fw
>>>
>>> for you to fetch changes up to 930f276f8f1f2d83e44da6a32f4e0b2513db21a2:
>>>
>>> brcm: Add BCM43430 NVRAM for the Raspberry Pi 3 Model B (2019-01-11 13:04:43
>>> +0100)
>>>
>>> ----------------------------------------------------------------
>>> - Add NVRAM for BCM43455 used by Raspberry Pi 3 Model B+
>>> - Add NVRAM for BCM43430 used by Raspberry Pi 3 Model B
>>>
>>> ----------------------------------------------------------------
>>> Matthias Brugger (2):
>>> brcm: Add BCM43455 NVRAM for Raspberry Pi 3 B+
>>> brcm: Add BCM43430 NVRAM for the Raspberry Pi 3 Model B
>>>
>>> WHENCE | 3 +
>>> brcm/brcmfmac43430-sdio.raspberrypi-rpi.txt | 47 ++++++++++++++++
>>> brcm/brcmfmac43455-sdio.clm_blob | Bin 0 -> 14036 bytes
>>> brcm/brcmfmac43455-sdio.raspberrypi-rpi.txt | 82 ++++++++++++++++++++++++++++
>>> 4 files changed, 132 insertions(+)
>>> create mode 100644 brcm/brcmfmac43430-sdio.raspberrypi-rpi.txt
>>> create mode 100644 brcm/brcmfmac43455-sdio.clm_blob
>>> create mode 100644 brcm/brcmfmac43455-sdio.raspberrypi-rpi.txt
>>
>> Pulled and pushed out.
>
> I reverted commit fca5958287a3e5e0bd1676af0ca4fc2fb9704b42 as there is
> some question around the clm_blob file an license applicability. If
> that gets resolved, please submit a new patch to add those files.
>
Thanks, actually I realized that there are some more problems with this pull
request, so thank you for reverting. I'll send a new one soon.
Regards,
Matthias
prev parent reply other threads:[~2019-01-14 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 12:11 [GIT PULL] Add NVRAM files for bcm43455 and bcm43430 Matthias Brugger
2019-01-14 15:33 ` Josh Boyer
2019-01-14 17:32 ` Josh Boyer
2019-01-14 17:54 ` Matthias Brugger [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=71fb2876-53d8-1fad-a0cc-df2268c705c2@suse.com \
--to=mbrugger@suse.com \
--cc=arend@broadcom.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phil@raspberrypi.org \
--cc=serge@raspberrypi.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).