From: Tyler Knott <tknott@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: The EMU 0404 soundcard and the Audigy driver...
Date: Thu, 24 Nov 2005 22:31:27 -0600 [thread overview]
Message-ID: <ea4102e90511242031w2fb02dbcqfa0da72db999ddcd@mail.gmail.com> (raw)
I'm not quiet sure whether to post this here or on the alsa-user
mailing list, but seeing as this information is more usefule to the
development of than use of ALSA I decided to put it here.
I have an EMU 0404 soundcard and I just tried the patch below (adapted
from the one suggested at
http://article.gmane.org/gmane.linux.alsa.devel/22204) to try and get
the EMU10k1/Audigy driver to work with this card. It does recognize
it, but I don't get any sound (not that I expected to anyways). Mixer
settings do not seem to have any affect (and curiously none of the
channels, except for the Tone channel, are muteable).
----PATCH---- (not a real diff-generated patch)
alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c (@ about line 750)
.emu10k2_chip = 1,
.ca0102_chip = 1,
.ac97_chip = 1} ,
+ {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
+ .driver = "Audigy", .name = "E-MU 0404 [4002]",
+ .id = "0404",
+ .emu10k2_chip = 1} ,
{.vendor = 0x1102, .device = 0x0004,
.driver = "Audigy", .name = "Audigy 1 [Unknown]",
.id = "Audigy",
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
next reply other threads:[~2005-11-25 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 4:31 Tyler Knott [this message]
2005-11-25 16:20 ` The EMU 0404 soundcard and the Audigy driver James Courtier-Dutton
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=ea4102e90511242031w2fb02dbcqfa0da72db999ddcd@mail.gmail.com \
--to=tknott@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
/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