Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
To: Benny Sjostrand <gorm@cucumelo.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: cs46xx patch for XFire 4channel output not in cvs?
Date: Sat, 10 May 2003 20:16:05 +0200	[thread overview]
Message-ID: <3EBD41E5.6040102@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

Hi,

as I looked into the current cvs, I noticed that the patch enabling 
4channel output for the Terratec DMX XFire didn't make it into the 
source tree.
I attached once again Benny's patch from 5th or 6th of april, with one 
minor change:
I changed the value 0x5d2d to 0x592d as Benny asked me to when I tested 
the patch.

The attached patch applies without problems to cvs snapshot from 6th of may.

thanks,
  fe



[-- Attachment #2: cs46xx_lib.patch --]
[-- Type: text/plain, Size: 832 bytes --]

--- alsa-kernel/pci/cs46xx/cs46xx_lib.c	Sat Apr  5 21:09:20 2003
+++ ../cvs/alsa-kernel/pci/cs46xx/cs46xx_lib.c	Sat Apr  5 21:22:58 2003
@@ -2543,13 +2543,21 @@
 	chip->eapd_switch = snd_ctl_find_id(chip->card, &id);
     
 #ifdef CONFIG_SND_CS46XX_NEW_DSP
+	if (chip->nr_ac97_codecs == 1 && 
+	   snd_cs46xx_codec_read(chip,AC97_VENDOR_ID2,
+				 CS46XX_PRIMARY_CODEC_INDEX) == 0x592d) {
+		/* set primary cs4294 codec into Extended Audio Mode */
+		snd_printdd("setting EAM bit on cs4294 CODEC\n");
+		snd_cs46xx_codec_write(chip,AC97_CSR_ACMODE,0x200,
+				       CS46XX_PRIMARY_CODEC_INDEX);
+	}
 	/* do soundcard specific mixer setup */
 	if (chip->mixer_init) {
 		snd_printdd ("calling chip->mixer_init(chip);\n");
 		chip->mixer_init(chip);
 	}
 #endif
-
+	
  	/* turn on amplifier */
 	chip->amplifier_ctrl(chip, 1);
     

                 reply	other threads:[~2003-05-10 18:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EBD41E5.6040102@gmx.de \
    --to=friedrich.ewaldt@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=gorm@cucumelo.org \
    /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