From alsa-devel-owner@alsa.jcu.cz  Tue Oct 13 11:03:46 1998
Received: from ife.ee.ethz.ch (ife-delek-fast.ee.ethz.ch [129.132.2.204])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id LAA07245
	for <alsa-devel@jcu.cz>; Tue, 13 Oct 1998 11:02:55 +0200
Received: from ife.ee.ethz.ch (eldrich.ee.ethz.ch [129.132.24.203])
	by ife.ee.ethz.ch (8.8.5/8.8.5) with ESMTP id KAA01742
	for <alsa-devel@jcu.cz>; Tue, 13 Oct 1998 10:59:51 +0200 (MET DST)
Message-ID: <36231727.6E35C6BF@ife.ee.ethz.ch>
Date: Tue, 13 Oct 1998 11:02:31 +0200
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
MIME-Version: 1.0
To: alsa-devel@jcu.cz
Subject: Re: S3 SonicVibes
References: <Pine.LNX.3.96.981012230713.25987C-100000@entry.jcu.cz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Jaroslav Kysela wrote:

> Looks that this problem is serious. My colleague have same problem with
> ALSA, but I didn't find any bug in code (yet). Seems that S3 SonicVibes
> chip is going to some dead mode in some cases. This dead mode shouldn't

I can confirm something like this also with my driver. I too haven't
found out so far what the culprit is.

I also haven't heard anything back from S3 about my inquiry why
32bit DDMA addresses don't work, although I'm by now a "registered
developer". They only sent me NDA's to sign :-(

Tom

