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. If you need any more information, let me know. On Tue, May 28, 2019 at 3:19 PM Jaroslav Kysela <perex@xxxxxxxx> 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@xxxxxxxx> > Linux Sound Maintainer; ALSA Project; Red Hat, Inc. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
