From: Benny Sjostrand <gorm@cucumelo.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: More CS4630, secondary CODEC output.
Date: Thu, 01 Aug 2002 14:57:43 +0200 [thread overview]
Message-ID: <3D493047.6060009@cucumelo.org> (raw)
In-Reply-To: s5hptx2agxp.wl@alsa2.suse.de
>
>
>
>
>about the secondary codec on terratec xfire: it's still not detected.
>could you test the latest cvs driver? i'm afraid that i did something
>wrong in merging...
>
My quick look on the cvsweb everything looks just fine, just one small
critical
fix that I missed in my 0731 release, I believe that's easy commited to
CVS (see my notice about this
earlier today) in _dsp_unlink_scb() function:
---
/home/pub/src/alsa-driver-0.9.0rc2-bs20020731/alsa-kernel/pci/cs46xx/dsp_spos_scb_lib.c
Wed Jul 31 23:19:19 2002
+++ dsp_spos_scb_lib.c Thu Aug 1 07:25:14 2002
@@ -148,6 +148,12 @@
spin_lock_irqsave(&chip->reg_lock, flags);
/* update entry in DSP RAM */
snd_cs46xx_poke(chip,
+ (scb->address + SCBsubListPtr) << 2,
+ (scb->sub_list_ptr->address << 0x10) |
+ (scb->next_scb_ptr->address));
+
+ /* update parent entry in DSP RAM */
+ snd_cs46xx_poke(chip,
(scb->parent_scb_ptr->address + SCBsubListPtr) << 2,
(scb->parent_scb_ptr->sub_list_ptr->address << 0x10) |
(scb->parent_scb_ptr->next_scb_ptr->address));
As soon I can I will test the CVS release, I'll comeback with feedback.
Any change from now
will be based on the CVS.
About the secondary CODEC, 1.03 codecs are not supported with the
current code, read, and write fucntions
needs to be slightly different for 1.03 codecs. I believe there are very
few cards shipped with 1.03 codecs, dont know the case
with terratec.
All differents boards always are shipped with some dam GPIO controls
which you never knows where they are wired, which never are documented,
if the terratec board is shipped with 2.0 codecs and it's not detected I
believe it's some magic GPIO pin that we need
to turn on.
/Benny
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-01 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 23:01 More CS4630, secondary CODEC output Benny Sjostrand
2002-07-27 0:36 ` Peter Heatwole
2002-07-27 7:02 ` Benny Sjostrand
2002-07-27 15:13 ` Frank van de Pol
2002-07-27 16:13 ` Peter Heatwole
2002-08-01 1:14 ` Peter Heatwole
2002-08-01 9:40 ` Takashi Iwai
2002-08-01 9:39 ` Benny Sjostrand
2002-08-01 10:57 ` Takashi Iwai
2002-08-01 12:42 ` Takashi Iwai
2002-08-01 12:57 ` Benny Sjostrand [this message]
2002-08-02 5:51 ` Benny Sjostrand
2002-08-02 10:14 ` Takashi Iwai
2002-08-02 15:47 ` Peter Heatwole
2002-08-02 18:16 ` Benny Sjostrand
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=3D493047.6060009@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@alsa-project.org \
--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.