>
>
>
>
>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
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
