From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Alistair Francis <alistair23@gmail.com>,
Alistair Francis <alistair@alistair23.me>,
Linux Firmware <linux-firmware@kernel.org>,
Franky Lin <franky.lin@broadcom.com>,
phil@raspberrypi.org
Subject: Re: [PULL 1/1] brcm: Add the brcmfmac43456-sdio.* files
Date: Tue, 2 Feb 2021 12:07:37 +0100 [thread overview]
Message-ID: <b8a9d845-7289-190e-90ec-849d33721c7d@broadcom.com> (raw)
In-Reply-To: <CA+5PVA7OKP4mQeWVRGLFYSXVH-gzqBTow6D0QoFveN1as7z_Jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
+ Phil Elwell
On 2/1/2021 4:14 PM, Josh Boyer wrote:
> On Tue, Jan 19, 2021 at 5:07 PM Arend van Spriel
> <arend.vanspriel@broadcom.com> wrote:
>>
>> On 19-01-2021 17:47, Alistair Francis wrote:
>>> On Tue, Jan 19, 2021 at 3:55 AM Josh Boyer <jwboyer@kernel.org> wrote:
>>>>
>>>> On Sun, Jan 17, 2021 at 10:05 PM Alistair Francis
>>>> <alistair@alistair23.me> wrote:
>>>>>
>>>>> Add brcm/brcmfmac43456-sdio.bin, brcm/brcmfmac43456-sdio.clm_blob and
>>>>> brcm/brcmfmac43456-sdio.txt from the
>>>>> RaspberryPi debian package avaliable at:
>>>>> https://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/
>>>>
>>>> I'm confused. Which package in there, and why is Debian carrying
>>>> firmware that isn't in the upstream linux-firmware tree?
>>>
>>> It's in the `firmware-brcm80211_20190114-1+rpt10_all.deb`. I'm not
>>> sure why it's there but not in linux-firmware.
>>
>> It is not provided by Debian, but by RPi foundation which provides it in
>> debian package. The URL kinda gives away why it is not in
>> linux-firmware: /firmware-nonfree/
>>
>> Also if you dive into the .deb file it has a copyright notice (attached)
>> which differs from the license that we have in linux-firmware for
>> Broadcom/Cypress firmware files.
>
> Would it be possible for Broadcom to release the firmware themselves
> under a license permissible for linux-firmware?
Hi Josh,
Things get confusing for me, but it seems 43456 is a Synaptics chipset
(now).
Regards,
Arend
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4176 bytes --]
next prev parent reply other threads:[~2021-02-02 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 7:48 [PULL 0/1] brcmfmac434 queue Alistair Francis
2021-01-17 7:48 ` [PULL 1/1] brcm: Add the brcmfmac43456-sdio.* files Alistair Francis
2021-01-19 11:55 ` Josh Boyer
2021-01-19 16:47 ` Alistair Francis
2021-01-19 22:07 ` Arend van Spriel
2021-02-01 15:14 ` Josh Boyer
2021-02-02 11:07 ` Arend Van Spriel [this message]
2021-02-02 11:18 ` Phil Elwell
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=b8a9d845-7289-190e-90ec-849d33721c7d@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=franky.lin@broadcom.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=phil@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).