Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Michal Kostrzewa <m.kostrzewa@pentacomp.com.pl>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Lynx AES16 driver
Date: Mon, 19 Jan 2004 18:46:01 +0100	[thread overview]
Message-ID: <s5hllo36dd2.wl@alsa2.suse.de> (raw)
In-Reply-To: <1074532503.3031.33.camel@gentoo>

At Mon, 19 Jan 2004 18:15:03 +0100,
Michal Kostrzewa wrote:
> 
> Hello,
> 
> Please help me in that license related case:
> I want to write a Lynx AES16 (http://www.lynxstudio.com/aes16.html) ALSA
> driver (I'm from Warsaw University of Technology and we want to use this
> card in our investigations). I wrote to Lynxstudio, and I received an
> answer that driver related specs are accessible under terms of
> Non-Disclosure Agreement which doesn't allow distribution of source code
> or any derived materials thus preventing development of ALSA driver as
> ALSA drivers are open source.
> 
> My question is: has an ALSA driver to be an open source? On
> www.alsa-project.org there is a sentence: "ALSA is released under the
> GPL (GNU General Public license) and the LGPL (GNU Lesser General Public
> License)." (please note the LGPL).

all the driver stuffs are distributed under GPL, while the ALSA libary
is under LGPL.  the user-space programs are all under GPL, so far.

> I understand, that there can be a
> driver distributed in binary form (e.g in fact firmware needed to run
> hdsp are distributed in binary form), GPL means that you cannot close
> the ALSA core framework. 

the modules which use the ALSA kernel API have to follow the GPL
rule.  if you load the firmware separately from the external program,
it's a different thing.  the firmware loader is nothing but an
application.

> Is this whole situation hopeless? Have I any arguments to use in the
> discussion with Lynxstudio?

don't think of releasing the binary-only modules on linux.
it's just a nightmare.

if the firmware matters, it's avoidable by putting it outside of the
kernel (which is anyway preferred), and creating a proper loader
program.  but the driver code itself must be open source.


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-01-19 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 17:15 Lynx AES16 driver Michal Kostrzewa
2004-01-19 17:46 ` Takashi Iwai [this message]
2004-01-19 20:55 ` Dan Hollis
2004-01-20 12:28   ` Michal Kostrzewa
2004-01-20 15:38     ` Ed Wildgoose
2004-01-20  8:40 ` Giuliano Pochini
2004-01-20  9:03   ` Glenn Maynard

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=s5hllo36dd2.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=m.kostrzewa@pentacomp.com.pl \
    /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