All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langer <martin-langer@gmx.de>
To: alsa-devel@lists.sourceforge.net
Subject: rules for /proc/asound [was: VIA EPIA (VT1612A) and SPDIF]
Date: Wed, 19 Feb 2003 11:30:16 +0100	[thread overview]
Message-ID: <20030219103016.GF3246@tuba.home> (raw)
In-Reply-To: <3E52CD2B.7090505@lemur.sytes.net>

On Tue, Feb 18, 2003 at 07:17:47PM -0500, Mathias Kretschmer wrote:
> 
> [root@musicbox root]# cat /proc/asound/card0/ac97#0
> 0-0/0: VIA Technologies VIA1612A
> 
> Capabilities     : -headphone out-
> DAC resolution   : 18-bit
> ADC resolution   : 18-bit
> 3D enhancement   : Reserved 27
> 
> Current setup
> Mic gain         : +0dB [+0dB]
> POP path         : pre 3D
> Sim. stereo      : off
> 3D enhancement   : off
> Loudness         : off
> Mono output      : MIX
> Mic select       : Mic1
> ADC/DAC loopback : off
> Extended ID      : codec=0 rev=0 AMAP DSA=0 SPDIF VRA
> Extended status  : SPDIF=3/4 SPDIF VRA
> PCM front DAC    : 44100Hz
> PCM ADC          : 48000Hz
> SPDIF Control    : Consumer PCM Copyright Category=0x2 Generation=1 
> Rate=48kHz
> 


Are there any rules for /proc/asound/cardX/XXX status files? Has it to be
readable by an external script? I think using standard control names can be 
one point. Are there other things I have to think about? Or is it still an
area without rules?


martin



-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge

      parent reply	other threads:[~2003-02-19 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19  0:17 VIA EPIA (VT1612A) and SPDIF Mathias Kretschmer
2003-02-19  9:29 ` Takashi Iwai
2003-02-22  3:19   ` Mathias Kretschmer
2003-02-19 10:30 ` Martin Langer [this message]

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=20030219103016.GF3246@tuba.home \
    --to=martin-langer@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.