All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: User land drivers.
Date: Fri, 03 Sep 2004 14:29:54 +0200	[thread overview]
Message-ID: <s5hbrgny1q5.wl@alsa2.suse.de> (raw)
In-Reply-To: <413456AE.7000007@superbug.demon.co.uk>

At Tue, 31 Aug 2004 11:45:02 +0100,
James Courtier-Dutton wrote:
> 
> I have found that there are a number of different possible sound 
> devices, where creating a user land driver would be beneficial to using 
> a kernel module.
> E.g. Bluetooth, Firewire etc.
> 
> Currently, we have:
> user app(user)
>      |
>      V
> alsa-lib(user)
>      |
>      V
> alsa-driver(kernel)
>      |
>      V
> hardware(kernel).
> 
> Bluetooth would prefer:
> user app(user)
>      |
>      V
> alsa-lib(user)
>      |
>      V
> alsa-bluetooth-headset-profile(user)
>      |
>      V
> bluetooth-driver(kernel)
>      |
>      V
> hardware(kernel).
> 
> 
> Would it be possible to have userland processes creating /dev/ files ?

Why do you need to *create* /dev?
When you access through alsa-lib, you don't need a device file.

> Alternatively, could we provide a new plugin method, so we can add 
> userland PCMs, Mixer, etc.

Exactly.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

  reply	other threads:[~2004-09-03 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 10:45 User land drivers James Courtier-Dutton
2004-09-03 12:29 ` Takashi Iwai [this message]
2004-09-03 13:11 ` Florian Schmidt
2004-09-03 14:08 ` Jaroslav Kysela
2004-09-03 14:27   ` Takashi Iwai
2004-09-03 14:31     ` Jaroslav Kysela
2004-09-03 15:58       ` James Courtier-Dutton
2004-09-03 15:57         ` Jaroslav Kysela
2004-09-03 18:05   ` David Lloyd

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=s5hbrgny1q5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.demon.co.uk \
    --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.