From: Benny Morgan <gorm@cucumelo.org>
To: Richard Olsson <flame@home.se>
Cc: alsa-devel@lists.sourceforge.net, tiwai@suse.de
Subject: Re: RC7 and CS46xx (GTXP)
Date: Thu, 06 Feb 2003 16:46:30 -0500 [thread overview]
Message-ID: <3E42D7B6.6030205@cucumelo.org> (raw)
In-Reply-To: 20030201170036.47cea5c3.flame@home.se
>
>
>Replying to my own mail, I know:)
>
>I reverted the changes the recent amplifier patch did to cs46xx_lib.c
>and RC7 works perfectly - no warning in dmesg either.
>
>
>
The cs46xx FIFO's are usually only accessed internally by the DSP.
There's is backdoor that make it possible to access the FIFO's from the
host.
My theory is that it's not possible to use this backdoor while the DSP
is accesing the FIFO's
To enable the rear speakers on the Santa Cruz card this backdoor is used
to access some GPIO's on the secondary codec.
A couple of month agoo I've changed the initialization order so: the
rear-speakers on the Santa Cruz board was enabled was enababled before
the DSP core was started, apparently it worked out. Now the problem
could be that the initialization order is changed again.
/Benny
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-06 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 13:48 RC7 and CS46xx (GTXP) Richard Olsson
2003-02-01 16:00 ` Richard Olsson
2003-02-02 15:59 ` Eloy A. Paris
2003-02-03 11:21 ` Takashi Iwai
2003-02-03 12:17 ` Richard Olsson
2003-02-04 12:22 ` Takashi Iwai
2003-02-05 18:31 ` Eloy A. Paris
2003-02-09 15:53 ` Christian Esken
2003-02-06 21:46 ` Benny Morgan [this message]
2003-02-02 16:22 ` RC7 and CS46xx (GTXP) -> Terratec XFire Friedrich Ewaldt
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=3E42D7B6.6030205@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=flame@home.se \
--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.