From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: <hdegoede@redhat.com>, <linux-wireless@vger.kernel.org>,
<linux-firmware@kernel.org>
Subject: Re: License of old broadcom BT firmwares and WiFi calibration files
Date: Wed, 03 Jan 2024 10:22:42 +0100 [thread overview]
Message-ID: <18ccea1d6d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (raw)
In-Reply-To: <18cce9a7818.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On January 3, 2024 10:14:42 AM Arend Van Spriel
<arend.vanspriel@broadcom.com> wrote:
> + linux-wireless
> + Hans de Goede
>
>
> On December 16, 2023 9:14:48 PM Svyatoslav Ryhel <clamor95@gmail.com> wrote:
>
>> сб, 16 груд. 2023 р. о 21:57 Arend van Spriel
>> <arend.vanspriel@broadcom.com> пише:
>>>
>>> On 12/16/2023 6:45 PM, Svyatoslav Ryhel wrote:
>>>> Greetings!
>>>>
>>>> I am trying to submit bluetooth firmwares (BCM4329B1.*,*.hcd and
>>>> BCM4330B1.*,*.hcd) and wifi calibration files
>>>> (brcmfmac4329-sdio.*,*.txt and brcmfmac4329-sdio.*,*.txt) from a few
>>>> Tegra 2 and Tegra 3 based devices into linux-fimware.
>>>>
>>>> I have faced ambiguous license issue since those files were part of
>>>> Android Images of different vendors. Those vendors did not provide a
>>>> license nor for android images, not for these files.
Does this mean you extracted them from the android image? That probably
never get accepted without any license information.
Regards,
Arend
>>>>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next parent reply other threads:[~2024-01-03 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPVz0n2Ky350xhOv6WvE0YhFJ9QBe59LnWvKiafs2tjFnptP+g@mail.gmail.com>
[not found] ` <22115037-3a81-4a52-8e64-bc85c2be4212@broadcom.com>
[not found] ` <CAPVz0n2Dah1b45c0yUjMZNph5AVJjneLsc2LOQ-dkXNRTv6y+Q@mail.gmail.com>
[not found] ` <18cce9a7818.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
2024-01-03 9:22 ` Arend Van Spriel [this message]
[not found] ` <BFE6B9E5-CAF5-4E30-A4A2-A2489423C961@gmail.com>
[not found] ` <18cd08e83d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
2024-01-04 9:07 ` License of old broadcom BT firmwares and WiFi calibration files Svyatoslav Ryhel
2024-01-08 15:43 ` Arend Van Spriel
2024-01-08 16:48 ` Svyatoslav Ryhel
2024-01-08 17:59 ` Arend Van Spriel
2024-01-08 18:21 ` Svyatoslav Ryhel
2024-01-08 19:03 ` Arend Van Spriel
2024-01-08 19:10 ` Svyatoslav Ryhel
2024-01-08 19:16 ` Svyatoslav
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=18ccea1d6d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=clamor95@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).