From: Andy Owen <andy-alsa@ultra-premium.com>
To: patch@alsa-project.org
Cc: alsa-devel@alsa-project.org, Andy Owen <andy-alsa@ultra-premium.com>
Subject: [PATCH - ca0106 1/6] ALSA: ca0106 - add Sound Blaster 5.1vx info.
Date: Thu, 21 Oct 2010 23:39:19 +1100 [thread overview]
Message-ID: <1287664764-4996-1-git-send-email-andy-alsa@ultra-premium.com> (raw)
Signed-off-by: Andy Owen <andy-alsa@ultra-premium.com>
diff --git a/sound/pci/ca0106/ca0106_main.c b/sound/pci/ca0106/ca0106_main.c
index 8e69620..6dc9a5d 100644
--- a/sound/pci/ca0106/ca0106_main.c
+++ b/sound/pci/ca0106/ca0106_main.c
@@ -239,6 +239,16 @@ static struct snd_ca0106_details ca0106_chip_details[] = {
.gpio_type = 1,
.i2c_adc = 1,
.spi_dac = 1 } ,
+ /* Sound Blaster 5.1vx
+ * Tested: Playback on front, rear, center/lfe speakers
+ * Not-Tested: Capture
+ */
+ { .serial = 0x10041102,
+ .name = "Sound Blaster 5.1vx [SB1070]",
+ .gpio_type = 1,
+ .i2c_adc = 0,
+ .spi_dac = 1
+ } ,
/* MSI K8N Diamond Motherboard with onboard SB Live 24bit without AC97 */
/* SB0438
* CTRL:CA0106-DAT
--
1.7.3.1.127.g1bb28
next reply other threads:[~2010-10-21 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:39 Andy Owen [this message]
2010-10-21 12:39 ` [PATCH - ca0106 2/6] ALSA: ca0106: Pull out dac powering routine into separate function Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 3/6] ALSA: ca0106: Move enabling of front dac out of hardcoded setup sequence Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 4/6] ALSA: ca0106: Create a nice spot for mapping channels to dacs Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 5/6] ALSA: ca0106: Allow different sound cards to use different SPI channel mappings Andy Owen
2010-10-21 12:39 ` [PATCH - ca0106 6/6] ALSA: ca0106: Use card specific dac id for mute controls Andy Owen
2010-10-21 21:16 ` [PATCH - ca0106 1/6] ALSA: ca0106 - add Sound Blaster 5.1vx info Takashi Iwai
2010-10-23 6:28 ` Andy Owen
[not found] ` <1287814690.1940.4.camel@marvin>
2010-10-23 9:22 ` Takashi Iwai
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=1287664764-4996-1-git-send-email-andy-alsa@ultra-premium.com \
--to=andy-alsa@ultra-premium.com \
--cc=alsa-devel@alsa-project.org \
--cc=patch@alsa-project.org \
/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