alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>,
	Daniel Drake <drake@endlessm.com>,
	"Lin, Mengdong" <mengdong.lin@intel.com>
Cc: Jian-Hong Pan <jian-hong@endlessm.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	sound-open-firmware@alsa-project.org
Subject: Re: [Sound-open-firmware] Signed firmware availability for kbl/cnl
Date: Wed, 31 Jul 2019 15:07:57 +0100	[thread overview]
Message-ID: <999df23199e5284459e66eaf351e2a2b66e25804.camel@linux.intel.com> (raw)
In-Reply-To: <3f6f48ac-6eac-ba98-91ac-62c19578b1fb@linux.intel.com>

On Wed, 2019-07-31 at 09:01 -0500, Pierre-Louis Bossart wrote:
> > Any objections to using this repo for topologies too ? I know we
> > haven't yet used it for UCMs but now is probably a good point to
> > move
> > (including moving the older UCMs over too).
> 
> We'll need to figure out the license for all this, the topologies 
> and 
> UCM files created for SOF are all BSD 3-clause but I am not clear on 
> older UCM files stored in alsa-lib, I don't think there was any 
> agreement that the LGPL license applied to them.

I remember this was discussed in the past, it is possible to make all
new UCMs and topologies BSD 3c in the new repo. We could also transfer
over and re-license any topoloies over from alsa-lib where we had
agreement from authors. 

This would eventually mean alsa-lib would contain "legacy" GPL
topologies whilst alsa-ucm-conf would contain any new and BSD licences
UCM/topologies.

Liam

  reply	other threads:[~2019-07-31 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAD8Lp45Bp1xVC7NjuNaANA7kAEN2Edshw+cViaTF3tRZEumgZA@mail.gmail.com>
     [not found] ` <cc9fa5b52138daffb09dc5b66ea9248379c9f60e.camel@linux.intel.com>
     [not found]   ` <CAD8Lp46GW8n8K7ttOeSje_au06BsyvCp4seVwj2wNbipei5ssA@mail.gmail.com>
     [not found]     ` <a4b17a75-d4e0-fc6b-a286-aa6b7b281b7d@linux.intel.com>
     [not found]       ` <CAD8Lp444soO1i8mWF73eucT16yAhy2js1byWJCTV5fn=TikHBg@mail.gmail.com>
     [not found]         ` <9e8b667f1aa2333dbcc34b5253372d1a8667551e.camel@linux.intel.com>
     [not found]           ` <ee34f820-0753-dfbe-09c0-7147cf229cc0@perex.cz>
     [not found]             ` <6493f195-eb5a-1a6d-2c31-e3a4123b2ad1@linux.intel.com>
     [not found]               ` <7c940d90-297e-19c0-2f74-1843439d5ccf@perex.cz>
     [not found]                 ` <d41b02286db2a827648d1c1ec793bbd0a55e99c1.camel@linux.intel.com>
2019-07-24 16:23                   ` [Sound-open-firmware] Signed firmware availability for kbl/cnl Jaroslav Kysela
2019-07-31 13:23                     ` Liam Girdwood
2019-07-31 14:01                       ` Pierre-Louis Bossart
2019-07-31 14:07                         ` Liam Girdwood [this message]
2019-07-31 17:52                           ` Jaroslav Kysela
2019-07-31 17:29                       ` Jaroslav Kysela
2019-07-31 18:14                         ` Pierre-Louis Bossart
2019-08-02  8:21                           ` Jaroslav Kysela
2019-08-02 14:40                             ` Liam Girdwood
2019-08-02 19:01                               ` Jaroslav Kysela
2019-08-02 19:24                                 ` Pierre-Louis Bossart
2019-08-05 14:39                                   ` Liam Girdwood
2019-08-05 14:36                                 ` Liam Girdwood

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=999df23199e5284459e66eaf351e2a2b66e25804.camel@linux.intel.com \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=drake@endlessm.com \
    --cc=jian-hong@endlessm.com \
    --cc=mengdong.lin@intel.com \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.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 NNTP newsgroup(s).