From: Clemens Ladisch <clemens@ladisch.de>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [RFC] Remove non-exist device and control from snd-ymfpci
Date: Mon, 19 Sep 2011 11:56:13 +0200 [thread overview]
Message-ID: <4E7711BD.9010208@ladisch.de> (raw)
In-Reply-To: <CAN8ccibjZSqiMRg6bO+tSsdTZUNJ3Q6FFEF-sYsLf8np9SSY2A@mail.gmail.com>
Raymond Yau wrote:
> Is it feasible to remove playback device 2 (rear) and control (e.g. 4
> ch Duplication) by checking sdac bit of ac97 registers to know that it
> does not support 4 channels ?
Yes.
> How about device 1 spdif since this card does not have spdif connector ?
How could this be detected?
> what is the difference of capture device 0 and device 3 ?
The default device can mix lots of sources together; the AC'97 device is
a direct input from the AC'97 codec.
Regards,
Clemens
next prev parent reply other threads:[~2011-09-19 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 5:13 [RFC] Remove non-exist device and control from snd-ymfpci Raymond Yau
2011-09-19 9:56 ` Clemens Ladisch [this message]
2011-09-21 2:03 ` Raymond Yau
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=4E7711BD.9010208@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).