From: Svyatoslav <clamor95@gmail.com>
To: Arend Van Spriel <aspriel@gmail.com>,
Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org, linux-firmware@kernel.org,
linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: License of old broadcom BT firmwares and WiFi calibration files
Date: Mon, 08 Jan 2024 21:16:10 +0200 [thread overview]
Message-ID: <397291D1-1657-4560-9E7C-57C890BD84FB@gmail.com> (raw)
In-Reply-To: <a1a3683b-9d47-41e8-a527-17bdca1607ba@gmail.com>
8 січня 2024 р. 21:03:09 GMT+02:00, Arend Van Spriel <aspriel@gmail.com> написав(-ла):
>+ linux-bluetooth
>+ Marcel
>
>On 1/8/2024 7:21 PM, Svyatoslav Ryhel wrote:
>> пн, 8 січ. 2024 р. о 19:59 Arend Van Spriel <arend.vanspriel@broadcom.com> пише:
>>>
>>> On January 8, 2024 5:48:37 PM Svyatoslav Ryhel <clamor95@gmail.com> wrote:
>>>
>>>> пн, 8 січ. 2024 р. о 17:43 Arend Van Spriel <arend.vanspriel@broadcom.com>
>>>> пише:
>>>>>
>>>>> On January 4, 2024 10:08:04 AM Svyatoslav Ryhel <clamor95@gmail.com> wrote:
>>>>>
>>>>>> ср, 3 січ. 2024 р. о 20:20 Arend Van Spriel <arend.vanspriel@broadcom.com>
>>>>>> пише:
>>>>>>>
>>>>>>> On January 3, 2024 6:28:33 PM Svyatoslav Ryhel <clamor95@gmail.com> wrote:
>>>>>>>
>>>>>>>> 3 січня 2024 р. 11:22:42 GMT+02:00, Arend Van Spriel
>>>>>>>> <arend.vanspriel@broadcom.com> написав(-ла):
>>>>>>>>> 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.
>>>>>>>>
>>>>>>>> Can Broadcom re-grant license to these files?
>>>>>>>>
>>>>>>>> This license is for bcm4329 in crespo
>>>>>>>> <https://android.googlesource.com/device/samsung/crespo/+/refs/heads/main/self-extractors/broadcom/LICENSE>
>>>>>>>
>>>>>>> Actually checked this link:
>>>>>>>
>>>>>>> https://android.googlesource.com/device/samsung/crespo/+/refs/heads/main/proprietary-blobs.txt
>>>>>>>
>>>>>>> It lists the bcm4329.hcd file as falling under Apache-2.0 license. Same for
>>>>>>> asus/grouper.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Arend
>>>>>>
>>>>>> So this actually resolves ambiguity. Thanks
>>>>>
>>>>> Yes, but ... you should add them to linux-firmware under the same license.
>>>>> That means you need to mark them as such in the WHENCE file. Feel free to
>>>>> cc: me for the patch so I can have a look at it.
>>>>>
>>>>> Regards,
>>>>> Arend
>>>>
>>>> Thank you for your assistance, it is really appreciated and valued but
>>>> it was rejected
>>>>
>>>> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/114
>>>>
>>>> I have referred to our conversation.
>>>
>>> I see and it seems they were correct. My bad. Clearly should not try a
>>> career as lawyer.
>>>
>>> I can try to publish them to linux-firmware, but I have to ask internally.
>>>
>>> Regards,
>>> Arend
>>>
>>
>> Thank you, looking forward to your answer. But keep in mind that
>> generic firmware for bluetooth might not be an option. I have tried to
>> shuffle them and bluetooth failed.
>
>Okay. I guess there is a naming scheme that btbcm.ko uses. Will look in the source file how it loads firmware/patch. Actually your merge request would also tell me. That involves a whole lot more firmware files than what we discussed earlier.
>
>Regards,
>Arend
Uh, yes, I am terribly sorry about that. I was looking for analogies with existing publishes of firmwares since bt firmware occurred to be not interchangeable. I have no hopes that any of them will be accepted, so if any passes then good.
prev parent reply other threads:[~2024-01-08 19:16 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 ` License of old broadcom BT firmwares and WiFi calibration files Arend Van Spriel
[not found] ` <BFE6B9E5-CAF5-4E30-A4A2-A2489423C961@gmail.com>
[not found] ` <18cd08e83d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
2024-01-04 9:07 ` 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 [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=397291D1-1657-4560-9E7C-57C890BD84FB@gmail.com \
--to=clamor95@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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).