From: Rene Herman <rene.herman@gmail.com>
To: "Wallace, Brooke" <brookew@qualcomm.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: User space drivers
Date: Fri, 03 Aug 2007 01:25:08 +0200 [thread overview]
Message-ID: <46B267D4.3040702@gmail.com> (raw)
In-Reply-To: <C7A98C6EB85FFF4FAE03BD695D68EC7601239680@NAEX05.na.qualcomm.com>
On 08/02/2007 11:39 PM, Wallace, Brooke wrote:
> I've been trying to sort thru the ALSA docs and am starting to get the
> impression that all of the existing drivers are written as Kernel
> Modules.
Yes. Some stuff like mixing happens in userspace but the lowlevel drivers
are in kernel space.
> Doesn't this mean that they are running in Kernel space and infact are
> not User Space drivers?
Yes.
> Shouldn't there be an ALSA Drivers API document that covers an API that
> User Space Drivers can use? I must be mssing something here...
I believe you are. Who told you that ALSA drivers ran in userspace?
> I'm looking into ALSA because my company wants to use this standard for
> writing User Space drivers for our product running on various linux
> kernels. The reasoning for this is strictly proprietary licensing - our
> leagl department is not comfortable with the GPL and the possiblitiy that
> something written for Kernel space could at some time be considered as
> required to be GPL - not my decision...
You have a sensible legal department. Many hold that distributing Linux
kernelspace code under a non GPL compatible license is illegal, period.
Your job, should you chose to accept it, is convince them that releasing the
code you will be writing under a GPL compatible license is not actually all
that scary. Pointing them to all the other companies that do so can help.
The other option you have is make do without _any_ help from _anyone_ on
this list at least. Good luck.
Rene.
next prev parent reply other threads:[~2007-08-02 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 21:39 User space drivers Wallace, Brooke
2007-08-02 23:25 ` Rene Herman [this message]
2007-08-03 0:04 ` James Courtier-Dutton
2007-08-03 2:55 ` Eliot Blennerhassett
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 18:27 bmentink
2013-10-04 18:42 ` Pow, Christopher (SWCOE)
2013-10-04 18:46 ` Denys Dmytriyenko
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=46B267D4.3040702@gmail.com \
--to=rene.herman@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=brookew@qualcomm.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.