All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: paul@linuxaudiosystems.com
Cc: Carlos Munoz <carlos@kenati.com>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: What is /dev/snd/hwC0D0 used for ?
Date: Thu, 30 Mar 2006 21:47:10 -0500	[thread overview]
Message-ID: <1143773231.22771.15.camel@mindpipe> (raw)
In-Reply-To: <1143769524.7539.54.camel@localhost.localdomain>

On Thu, 2006-03-30 at 20:45 -0500, Paul Davis wrote:
> On Thu, 2006-03-30 at 16:37 -0500, Lee Revell wrote:
> > > Is there a document explaining what all the devices are used for ? I 
> > > searched but didn't find anything.
> > > 
> > 
> > No because these interfaces are intended to be private to alsa-lib.  The
> > source code is authoritative.
> 
> is this confirmed policy?
> 

Nope, just my understanding of the situation.  Corrections are welcome.

> what happens about support for devices that have classes of control
> that do not fit into the existing ALSA schema and have traditionally
> been handled via device-specific ioctl's on /dev/snd/hwFOO ?
> 

Good question.  I know the upstream kernel policy is "no new ioctls,
period"...

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-03-31  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 19:09 What is /dev/snd/hwC0D0 used for ? Carlos Munoz
2006-03-30 21:37 ` Lee Revell
2006-03-31  1:45   ` Paul Davis
2006-03-31  2:47     ` Lee Revell [this message]
2006-03-31  9:53       ` Takashi Iwai

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=1143773231.22771.15.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=carlos@kenati.com \
    --cc=paul@linuxaudiosystems.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.