From: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
To: Richard Olsson <flame@home.se>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: RC7 and CS46xx (GTXP) -> Terratec XFire
Date: Sun, 02 Feb 2003 17:22:43 +0100 [thread overview]
Message-ID: <3E3D45D3.8010303@gmx.de> (raw)
In-Reply-To: <20030201144858.0479188a.flame@home.se>
Richard Olsson wrote:
>Something between CVS 2002-12-18 and RC7 seriously broke the amplifier
>stuff for me on my GTXP - sound is very disorted and volume is very low.
>It's different from the troubles RC6 gave me though. I'd guess it's
>the recent amplifier patch that was applied to the CS46xx driver.
>
>Only oddity I see is in dmesg:
>ALSA ../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:415: cs46xx: failure waiting for FIFO command to complete
>
>I'll stick to the 2002-12-18 CVS for now:)
>
>
>
The same warning in dmesg with my Terrartec DMX XFire. But everything
seems to work (OK) like 2002-12-09-CVS + 2003-01-05-patch. What does
this warning mean. Should I ignore it?
TIA
fe
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-02-02 16:22 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
2003-02-02 16:22 ` Friedrich Ewaldt [this message]
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=3E3D45D3.8010303@gmx.de \
--to=friedrich.ewaldt@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=flame@home.se \
/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