From: Takashi Iwai <tiwai@suse.de>
To: Peter Heatwole <peter599@gotnet.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Cirrus Logic S/PDIF
Date: Tue, 21 May 2002 12:46:47 +0200 [thread overview]
Message-ID: <s5helg5hj6w.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020517152415.GA872@porky>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Hi Peter,
At Fri, 17 May 2002 08:24:15 -0700,
Peter Heatwole wrote:
>
> Hello,
>
> I have a CS4281 based card with a CS4297A AC'97 codec, and wanted
> to use the IEC958 jack. After reading some of the specs, I realized
> that the function "patch_cirrus_cs4205()" in ac97_codec.c applies to
> the CS4297A codec as well. I changed the line in the snd_ac97_codec_ids
> array that corresponds to the CS4297A, and made it use the CS4205 patch,
> and the codec successfully copies the data to the iec958 jack as well
> as analog out.
> What would be the drawbacks to setting this line in the CVS? I realize
> this will not work for all soundcards using the CS4297A (for instance, I
> used this patch with my Santa Cruz (CS4630 DSP), with no luck, as
> expected),
> but would using the patch cause harm?
no, i don't think it harms.
the attached patch is what you mentioned above?
if it's ok, then i'll commit it to cvs.
> I have not checked, but I assume this would also apply to other Cirrus
> Logic AC'97 codecs?
well, we need to check spec sheets to be sure.
could you tell us which chips did you check (to be supposed to work)?
Takashi
[-- Attachment #2: cs-spdif.dif --]
[-- Type: application/octet-stream, Size: 788 bytes --]
Index: alsa-kernel/pci/ac97/ac97_codec.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/ac97/ac97_codec.c,v
retrieving revision 1.15
diff -u -r1.15 ac97_codec.c
--- alsa-kernel/pci/ac97/ac97_codec.c 21 May 2002 09:34:54 -0000 1.15
+++ alsa-kernel/pci/ac97/ac97_codec.c 21 May 2002 10:46:02 -0000
@@ -113,7 +113,7 @@
{ 0x414c4740, 0xfffffff0, "ALC202", NULL },
{ 0x414c4750, 0xfffffff0, "ALC250", NULL },
{ 0x43525900, 0xfffffff8, "CS4297", NULL },
-{ 0x43525910, 0xfffffff8, "CS4297A", NULL },
+{ 0x43525910, 0xfffffff8, "CS4297A", patch_cirrus_cs4205 },
{ 0x42525920, 0xfffffff8, "CS4294/4298", NULL },
{ 0x42525928, 0xfffffff8, "CS4294", NULL },
{ 0x43525930, 0xfffffff8, "CS4299", patch_cirrus_cs4299 },
next prev parent reply other threads:[~2002-05-21 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 15:24 Cirrus Logic S/PDIF Peter Heatwole
2002-05-21 10:46 ` Takashi Iwai [this message]
2002-05-21 15:41 ` Peter Heatwole
2002-05-21 15:58 ` Takashi Iwai
2002-05-21 20:02 ` Peter Heatwole
2002-05-22 8:06 ` Jaroslav Kysela
2002-05-22 15:27 ` Peter Heatwole
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=s5helg5hj6w.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=peter599@gotnet.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 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.