From: Jaroslav Kysela <perex@perex.cz>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Mark Pearson <mpearson@lenovo.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Elimar Riesebieter <riesebie@lxtec.de>
Subject: Re: [alsa-devel] [External] Re: alsa-lib: Add ucm support for whiskeylake sof-skl_hda_card audio
Date: Tue, 24 Sep 2019 13:53:35 +0200 [thread overview]
Message-ID: <38abcb71-3041-7015-e56a-43f628b2faf1@perex.cz> (raw)
In-Reply-To: <98b99cea-9be1-f232-f62c-1f0b7a10e295@linux.intel.com>
Dne 19. 09. 19 v 17:15 Pierre-Louis Bossart napsal(a):
> On 9/19/19 9:54 AM, Mark Pearson wrote:
>>>
>>> Indeed UCM is required for all cases where SOF and PulseAudio are used.
>>>
>>> Our thinking was however to add this UCM file to the new repository outside
>>> of alsa-lib [1]. There is an on-going thread started by Jaroslav to move those
>>> files and relicense them as BSD-3-Clause [2]
>>>
>>> [1]
>>> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-
>>> July/153257.html
>>> [2]
>>> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-
>>> September/155246.html
>>
>> Thanks Pierre.
>>
>> Do we have any approximate timelines on when and how this will happen? (I'm new to this)
>>
>> One of my main aims is that we have a customer using Debian and one of our platforms that require this change - I need to make sure I understand how this would roll out and what actions they need to take in the meantime if it's not going to be available in Debian.
>
> I think the first order would be to have the file cleaned-up, with its
> Intel origin clearly stated with a signed-off-by tag.
>
> Then once this is done, the Debian package creation needs to be handled
> (using either the ALSA repo or the cloned version on SOF GitHub). I
> don't have any experience with Debian packages so can't really comment
> on the effort it would take.
I did some cleanups here:
https://github.com/alsa-project/alsa-ucm-conf/commit/f796f0852a097e238fa9f5efb174e95b5ee6c8b7
Pierre, could you confirm the original source and are you ok with that?
Thank you,
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-09-24 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 14:23 [alsa-devel] alsa-lib: Add ucm support for whiskeylake sof-skl_hda_card audio Elimar Riesebieter
2019-09-19 14:44 ` Pierre-Louis Bossart
[not found] ` <f11c5347d8504148a47fdbc48d920f59@lenovo.com>
2019-09-19 15:15 ` [alsa-devel] [External] " Pierre-Louis Bossart
2019-09-24 11:53 ` Jaroslav Kysela [this message]
2019-09-24 12:06 ` Mark Pearson
2019-09-27 8:21 ` Hui Wang
2019-09-27 9:01 ` Jaroslav Kysela
2019-09-28 3:33 ` Hui Wang
2019-10-03 2:07 ` Hui Wang
2019-09-27 10:07 ` Jaska Uimonen
2019-09-27 10:57 ` Jaroslav Kysela
2019-09-27 14:00 ` Jaska Uimonen
2019-09-27 14:49 ` Jaroslav Kysela
2019-09-28 16:33 ` Jaska Uimonen
2019-09-19 14:49 ` [alsa-devel] " Jaroslav Kysela
2019-09-19 15:14 ` [alsa-devel] [External] " Mark Pearson
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=38abcb71-3041-7015-e56a-43f628b2faf1@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=mpearson@lenovo.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=riesebie@lxtec.de \
/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