From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Re: User space drivers
Date: Fri, 03 Aug 2007 14:55:23 +1200 [thread overview]
Message-ID: <46B2991B.6080402@audioscience.com> (raw)
In-Reply-To: <46B27108.1000409@superbug.co.uk>
James Courtier-Dutton wrote:
> Wallace, Brooke wrote:
>> Hi,
>>
>> 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. Doesn't this mean that they are running in Kernel space and
>> infact are not User Space drivers? 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...
What you may be looking for is the plugins API.
Take a look at the alsa-plugins source, there are some examples of
things that talk to other userspace things (E.g. jack or pulseaudio
plugin) or other non alsa drivers (E.g. oss or freebob)
http://hg-mirror.alsa-project.org/alsa-plugins/
But remember not to put any GPL code in your non-gpl driver ;)
As others have mentioned you may not be able to get much help for this
kind of endeavour if you are not prepared to "show us the source".
--
Eliot
next prev parent reply other threads:[~2007-08-03 2:55 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
2007-08-03 0:04 ` James Courtier-Dutton
2007-08-03 2:55 ` Eliot Blennerhassett [this message]
-- 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=46B2991B.6080402@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@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 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.