From: Lee Revell <rlrevell@joe-job.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Adrian McMenamin <adrian@mcmen.demon.co.uk>, alsa-devel@alsa-project.org
Subject: Re: amixer issues
Date: Tue, 04 Apr 2006 12:30:39 -0400 [thread overview]
Message-ID: <1144168240.26668.6.camel@mindpipe> (raw)
In-Reply-To: <20060404161719.GB18884@turing.informatik.uni-halle.de>
On Tue, 2006-04-04 at 18:17 +0200, Clemens Ladisch wrote:
> Does /dev/snd/controlC0 exist, and does it point to the control device
> listed in /proc/asound/devices?
>
Can you please clarify? How does a device node "point to" something?
$ ls -al /dev/snd/controlC0
crw-rw---- 1 root audio 116, 0 Apr 1 10:06 /dev/snd/controlC0
$ cat /proc/asound/devices
0: [ 0] : control
1: : sequencer
4: [ 0- 0]: hardware dependent
6: [ 0- 2]: hardware dependent
8: [ 0- 0]: raw midi
9: [ 0- 1]: raw midi
10: [ 0- 2]: raw midi
11: [ 0- 3]: raw midi
16: [ 0- 0]: digital audio playback
18: [ 0- 2]: digital audio playback
19: [ 0- 3]: digital audio playback
20: [ 0- 4]: digital audio playback
24: [ 0- 0]: digital audio capture
25: [ 0- 1]: digital audio capture
26: [ 0- 2]: digital audio capture
28: [ 0- 4]: digital audio capture
33: : timer
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
next prev parent reply other threads:[~2006-04-04 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 16:07 amixer issues Adrian McMenamin
2006-04-04 16:17 ` Clemens Ladisch
2006-04-04 16:30 ` Lee Revell [this message]
2006-04-04 16:56 ` Clemens Ladisch
[not found] ` <4432C745.3090306@pianodisc.com>
2006-04-05 8:34 ` Clemens Ladisch
2006-04-04 18:07 ` Adrian McMenamin
2006-04-05 8:36 ` Clemens Ladisch
2006-04-05 21:36 ` Adrian McMenamin
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=1144168240.26668.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/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.