From: Lee Revell <rlrevell@joe-job.com>
To: Juan Carlos Castro y Castro <jcastro@instant.com.br>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: question about closed source alsa driver
Date: Tue, 16 May 2006 11:26:00 -0400 [thread overview]
Message-ID: <1147793161.13948.117.camel@mindpipe> (raw)
In-Reply-To: <4469EE3B.7010600@instant.com.br>
On Tue, 2006-05-16 at 12:22 -0300, Juan Carlos Castro y Castro wrote:
> Lee Revell wrote:
>
> >On Tue, 2006-05-16 at 17:37 +0400, Sergey Kolosov wrote:
> >
> >
> >>Whether me interests if I shall write closed source alsa driver there
> >>will be it violations gpl?
> >>
> >>
> >No you cannot. The ALSA driver core is GPL so all drivers must be GPL.
> >
> >Why do you need to hide the hardware details? It's just a sound card.
> >
> >
> It may be that his bosses are not as enlightened as him... you and I
> understand that publishing the hardware interface to a sound card hardly
> gives away crucial secrets, but PHBs might not. Maybe some evangelism is
> in order.
>
They just need to survey the market - I would think it would be enough
to see that Intel, Via, M-Audio, RME, Creative, and countless other
vendors all have provided open source ALSA drivers.
Lee
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-05-16 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 10:18 question about closed source alsa driver Sergey Kolosov
2006-05-16 13:05 ` Petter Sundlöf
2006-05-16 13:37 ` Sergey Kolosov
2006-05-16 14:55 ` Lee Revell
2006-05-16 15:22 ` Juan Carlos Castro y Castro
2006-05-16 15:26 ` Lee Revell [this message]
2006-05-16 15:56 ` Juan Carlos Castro y Castro
2006-05-16 19:26 ` Sergey Kolosov
2006-05-17 18:09 ` Thierry Vignaud
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=1147793161.13948.117.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jcastro@instant.com.br \
/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.