From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Fixes AC3 output on Audigy2 sound cards.
Date: Fri, 25 Mar 2005 00:47:19 +0100 [thread overview]
Message-ID: <m2is3ga9o7.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <42433C51.6080500@superbug.co.uk> (James Courtier-Dutton's message of "Thu, 24 Mar 2005 22:16:49 +0000")
James Courtier-Dutton <James@superbug.co.uk> writes:
> >>Did you also apply the patch to the Audigy2.conf file, that goes
> >>with this patch? The spdif out routing has changed.
> > when did this changed in the driver btw?
> >
>
> 1.0.9rc2 needs the changed Audigy2.conf file, otherwise AC3 passthru
> will not work. The DSP code in alsa-driver changed to fix a hardware
> bug in some Creative sound cards,
i guess that this's this commit:
2005-03-22 21:58 tiwai
* pci/emu10k1/emufx.c: Summary: Fixes AC3 output on Audigy2 sound
cards
This patch adds a DSP patch to fix an spdif_bug on some Audigy2
cards.
is'nt it?
-------------------------------------------------------
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-24 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 14:03 [PATCH] Fixes AC3 output on Audigy2 sound cards James Courtier-Dutton
2005-03-21 19:49 ` Takashi Iwai
2005-03-21 21:26 ` James Courtier-Dutton
2005-03-22 20:59 ` Takashi Iwai
2005-03-23 20:46 ` James Courtier-Dutton
2005-03-24 11:24 ` Takashi Iwai
2005-03-24 15:00 ` Takashi Iwai
2005-03-24 13:54 ` Thierry Vignaud
2005-03-24 22:16 ` James Courtier-Dutton
2005-03-24 23:47 ` Thierry Vignaud [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=m2is3ga9o7.fsf@vador.mandrakesoft.com \
--to=tvignaud@mandrakesoft.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--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.