[alsa-devel] Merging the new firmware files for CA0132 into alsa-firmware

[Jaroslav Kysela]

Dne 28. 05. 19 v 21:37 Takashi Iwai napsal(a):
> On Tue, 28 May 2019 21:24:39 +0200,
> Connor McAdams wrote:
>>
>> Yes, I did end up getting permission from Creative themselves to
>> redistribute the files. That was back in November of 2018.
>>
>> I also asked them to email Takashi Iwai to confirm, which I think they
>> ended up doing.
>>
>> My contact within Creative has not responded since December of 2018,
>> when I asked for a name to go with the email he told me to use for the
>> sign-off, and I think that was why the Linux firmware people weren't
>> willing to accept it.
> 
> Right, basically these two files align with the already existing other
> ca0132 firmware files in the repo.  But the problem was just that the
> submitter was the third person, which is quite unusual.

Ok, thanks. It might make sense to indicate this in the commit message
(clarify the licence - use forced push, if you like).

					Jaroslav

> 
> 
> Takashi
> 
>>
>> If you need any more information, let me know.
>>
>> On Tue, May 28, 2019 at 3:19 PM Jaroslav Kysela <perex at perex.cz> wrote:
>>>
>>> Dne 28. 05. 19 v 19:47 Takashi Iwai napsal(a):
>>>> On Tue, 28 May 2019 18:38:48 +0200,
>>>> Jaroslav Kysela wrote:
>>>>>
>>>>> Dne 28. 05. 19 v 16:54 Takashi Iwai napsal(a):
>>>>>> Hi,
>>>>>>
>>>>>> it seems that Connor's previous attempt to put a couple of ca0132
>>>>>> firmware files into linux-firmware tree didn't go through,
>>>>>> unfortunately.  And now I'm thinking of taking them into alsa-firmware
>>>>>> package as a stop-gap.  We already distribute other ca0132 firmware
>>>>>> files, so the addition shouldn't be a big problem.
>>>>>>
>>>>>> Jaroslav, what do you think?
>>>>>
>>>>> No problem. The same situation is for the SoC SOF firmware files (drivers are
>>>>> in kernel, firmware files are missing). Perhaps, we can release those files
>>>>> quickly in alsa-firmware and then migrate them slowly to linux-firmware.
>>>>
>>>> OK, now pushed to alsa-firmware git repo.
>>>>
>>>> BTW, the situation is slightly different from SOF.  At this time, the
>>>> problem was that it's been submitted by a third person.
>>>
>>> Ok, so we don't have a licence for those files? Connor, have you tried to
>>> contact Creative for a permission to use/distribute those files?
>>>
>>>                                                 Jaroslav
>>>
>>> --
>>> Jaroslav Kysela <perex at perex.cz>
>>> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
>>


-- 
Jaroslav Kysela <perex at perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.