From: Florian Zeitz <florob@babelmonkeys.de>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de
Subject: [PATCH] [ALSA] emu10k1: Add details for E-mu 0404 PCIe version
Date: Sun, 12 Jun 2011 01:48:44 +0200 [thread overview]
Message-ID: <4DF3FEDC.1060608@babelmonkeys.de> (raw)
This patch adds the necessary details to support the PCIe version of
E-MU's 0404 card. I have tested this for some time now and it appears to
be working fine.
>From comparing the PCBs it seems the PCIe version just added a PCIe
chipset and left all other components pretty much in place.
For anyone intrigued to take a look at the PCB there are pictures I took
at <http://babelmonkeys.de/~florob/E-MU%200404/>.
This modification was made on top of Takashi Iwai's fix/misc branch.
Regards,
Florian Zeitz
---
sound/pci/emu10k1/emu10k1_main.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/sound/pci/emu10k1/emu10k1_main.c
b/sound/pci/emu10k1/emu10k1_main.c
index 5e619a8..15f0161 100644
--- a/sound/pci/emu10k1/emu10k1_main.c
+++ b/sound/pci/emu10k1/emu10k1_main.c
@@ -1440,6 +1440,14 @@ static struct snd_emu_chip_details
emu_chip_details[] = {
.ca0102_chip = 1,
.spk71 = 1,
.emu_model = EMU_MODEL_EMU0404}, /* EMU 0404 */
+ /* EMU0404 PCIe */
+ {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40051102,
+ .driver = "Audigy2", .name = "E-mu 0404 PCIe [MAEM8984]",
+ .id = "EMU0404",
+ .emu10k2_chip = 1,
+ .ca0108_chip = 1,
+ .spk71 = 1,
+ .emu_model = EMU_MODEL_EMU0404}, /* EMU 0404 PCIe ver_03 */
/* Note that all E-mu cards require kernel 2.6 or newer. */
{.vendor = 0x1102, .device = 0x0008,
.driver = "Audigy2", .name = "SB Audigy 2 Value [Unknown]",
--
1.7.5.4
next reply other threads:[~2011-06-11 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 23:48 Florian Zeitz [this message]
2011-06-12 16:47 ` [PATCH] [ALSA] emu10k1: Add details for E-mu 0404 PCIe version Takashi Iwai
2011-06-12 17:23 ` Florian Zeitz
2011-06-12 19:24 ` 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=4DF3FEDC.1060608@babelmonkeys.de \
--to=florob@babelmonkeys.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.