All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "mengdong.lin" <mengdong.lin@linux.intel.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Takashi Iwai <tiwai@suse.de>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: License for UCM config files - re plumbers audio conf discussion.
Date: Thu, 12 Jan 2017 11:01:29 +0000	[thread overview]
Message-ID: <1484218889.2604.85.camel@loki> (raw)

During the plumbers audio conference we discussed changing the release
cadence and packaging of the UCM config files. This was to separate them
from the alsa-lib package and alsa-lib release cadence for easier and
more timely distribution for Ubuntu, Fedora etc.

One thing that we did not cover was the UCM config file licence, if
indeed there is a license for the UCM config files ? It's clear to me
that the alsa-lib source and headers are LGPL, but does the LGPL also
apply to the runtime UCM config files ? LGPL is specifically designed
for libraries so my understanding is that it's probably not applicable
to the UCM runtime configuration files.  

Here the LGPL definition of source code from alsa-lib COPYING :-

  ""Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library."

Having a licence free or BSD/MIT type license for the UCM config repo
would mean the configurations (or derivatives of) could also be used
with Android.

IANAL

Liam

             reply	other threads:[~2017-01-12 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 11:01 Liam Girdwood [this message]
2017-01-12 11:59 ` License for UCM config files - re plumbers audio conf discussion Takashi Iwai
2017-01-31 19:30 ` Mark Brown

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=1484218889.2604.85.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=mengdong.lin@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.