From: Takashi Iwai <tiwai@suse.de>
To: "Vedran Miletić" <rivanvx@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Re: snd-ca0106
Date: Sun, 02 Nov 2008 12:26:53 +0100 [thread overview]
Message-ID: <s5htzaqid1e.wl%tiwai@suse.de> (raw)
In-Reply-To: <fd3eb9bf0811010422n7e03035ah62368287567be725@mail.gmail.com>
At Sat, 1 Nov 2008 12:22:01 +0100,
=?UTF-8?Q?Vedran_Mileti=C4=87?= wrote:
>
> I played with CA0106 driver a bit. I wonder if we could make it set
> name for card and chip, in similar way to snd-emu10k1 and others.
> So... in emu10k1.c we have:
> 180 strcpy(card->driver, emu->card_capabilities->driver);
> 181 strcpy(card->shortname, emu->card_capabilities->name);
> While in ca0106_main.c there is:
> 1369 strcpy(card->driver, "CA0106");
> 1370 strcpy(card->shortname, "CA0106");
> Can it be changed? I want it do display Card in alsamixer as a board
> name from ca0106_card_capabailities list and Chip name to be CA0106
> [chip->model].
Changing these fields are often dangerous and can easily break the
existing setup. The driver field determines which config file is
used, so it should stay as is unless you want to change the config
file explicitly (for incompatibility or so).
The shortname can influence on the creation of id string, so this
change should be done carefully, too.
> Also, it would be great if we could name the four PCMs, like
> hw0,0 - card_name Front
> hw0,1 - card_name Rear
> hw0,2 - card_name Center/LFE
> hw0,3 - card_name Side (it's not unknown)
> Instead of just CA0106. Any ideas?
The PCM name can be set independently from the card name, etc.
This should be safe in most cases.
Takashi
prev parent reply other threads:[~2008-11-02 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 11:22 snd-ca0106 Vedran Miletić
2008-11-02 11:26 ` 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=s5htzaqid1e.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=rivanvx@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