Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-966-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <a1a3683b-9d47-41e8-a527-17bdca1607ba@gmail.com>
Date: Mon, 8 Jan 2024 20:03:09 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: License of old broadcom BT firmwares and WiFi calibration files
Content-Language: en-US
To: Svyatoslav Ryhel <clamor95@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>
References: <CAPVz0n2Ky350xhOv6WvE0YhFJ9QBe59LnWvKiafs2tjFnptP+g@mail.gmail.com>
 <22115037-3a81-4a52-8e64-bc85c2be4212@broadcom.com>
 <CAPVz0n2Dah1b45c0yUjMZNph5AVJjneLsc2LOQ-dkXNRTv6y+Q@mail.gmail.com>
 <18cce9a7818.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <18ccea1d6d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <BFE6B9E5-CAF5-4E30-A4A2-A2489423C961@gmail.com>
 <18cd08e83d0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <CAPVz0n347PVv28H2wswmO3N63dpfPZ0d3VrdxmQHXMoo9LS69g@mail.gmail.com>
 <18ce9be5470.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <CAPVz0n3BxJjaudDnC=QLHa-0NsE9JSs1ezFpwK2yb=9ySyr2cw@mail.gmail.com>
 <18cea3af2c8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <CAPVz0n3-nirqD9XW+-R_Uh8Ehkm2WKcxa3ZTp8TiOUf7gz+wKA@mail.gmail.com>
From: Arend Van Spriel <aspriel@gmail.com>
In-Reply-To: <CAPVz0n3-nirqD9XW+-R_Uh8Ehkm2WKcxa3ZTp8TiOUf7gz+wKA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

+ 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