All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Heatwole <peter599@gotnet.net>
To: alsa-devel@lists.sourceforge.net
Subject: Cirrus Logic S/PDIF
Date: Fri, 17 May 2002 08:24:15 -0700	[thread overview]
Message-ID: <20020517152415.GA872@porky> (raw)

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?
    I have not checked, but I assume this would also apply to other Cirrus
Logic AC'97 codecs?

(Any additional info/corrections you may send me via personal mail would
also be much appreciated.)


-- Peter Heatwole
"Murphy was just a well known pessimist."

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

             reply	other threads:[~2002-05-17 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 15:24 Peter Heatwole [this message]
2002-05-21 10:46 ` Cirrus Logic S/PDIF Takashi Iwai
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=20020517152415.GA872@porky \
    --to=peter599@gotnet.net \
    --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 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.