From: Takashi Iwai <tiwai@suse.de>
To: cltien@cmedia.com.tw
Cc: alsa-devel@alsa-project.org
Subject: Re: Q:codec based config file?
Date: Mon, 07 Mar 2005 14:41:02 +0100 [thread overview]
Message-ID: <s5hoedvwp3l.wl@alsa2.suse.de> (raw)
In-Reply-To: <92C0412E07F63549B2A2F2345D3DB515F7D66B@cm-msg-02.cmedia.com.tw>
At Thu, 3 Mar 2005 06:40:22 +0800,
Tien, C.L. wrote:
>
> Hi,
>
> There are chip-based config file in /usr/share/alsa/cards, but they are based on driver name.
> For example all USB audio will need to search USB-Audio.conf, while AC97 codec with ICH4
> will need to search ICH4.conf.
>
> Since more and more codecs (USB, AC97 and HDA) can appear on the same bus, can this be changed
> to support config file based on the codec id? There are many codecs with different
> capabilities that may needs separate config files.
Yes, that's a problem right now.
The usb, ac97 and hda-codec drivers already add an ID string to
card_info.components list so that user-space lib/app can look at it.
So, we'll need just a few hook up in alsa-lib to look up the ID and
checks the preferred device/codec-specific config in prior to the card
(driver name) config.
I thought I'll work on this issue after 1.0.9 release, but of course,
pathes are always welcome ;)
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-07 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 22:40 Q:codec based config file? "Tien, C.L. - 田承禮"
2005-03-07 13:41 ` Takashi Iwai [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=s5hoedvwp3l.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cltien@cmedia.com.tw \
/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.