From alsa-user-owner@alsa.jcu.cz  Thu Jan  7 18:33:41 1999
Received: from sunny.bahnhof.se (sunny.bahnhof.se [193.44.91.1])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id SAA06220
	for <alsa-user@alsa.jcu.cz>; Thu, 7 Jan 1999 18:32:20 +0100
Received: from scode.noreva.se (pm1-02.bahnhof.se [195.178.166.15])
	by sunny.bahnhof.se (8.8.8+Sun/8.8.8) with ESMTP id SAA19620
	for <alsa-user@alsa.jcu.cz>; Thu, 7 Jan 1999 18:30:58 +0100 (MET)
Message-ID: <XFMail.990107193029.scode_ufp@usa.net>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990107131344.B1317@gotss.ml.org>
Date: Thu, 07 Jan 1999 19:30:29 +0100 (CET)
From: Peter Schuller <scode_ufp@usa.net>
To: alsa-user@alsa.jcu.cz
Subject: Re: ALSA and GUS MAX, on kernel 2.0.34 / Debian 2.0
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

> An application dumps a buffer of digital audio to be played. The driver says,
> "Start a DMA transferr and tell me when the transferr is finished or to a
> certain point".
> Guess how that happens? The soundcard triggers an interrupt that is picked
> up by the pc. Basically the soundcard says,
> "I've finished... eyes this way... attention to me" <smile>

Sounds reasonable. Guess I should've thought of that...
 
> Check your /proc/pci and make sure nothing is using IRQ5. If a PCI device
> grabs it, the ISA cards will appear never to generate interrupts. Symptoms
> of this are looping sound fragments, and messages to kernel log.

No luck. According to that file, the only IRQs occupied by PCI devices are the
video card and the SCSI controller, using 10 and 12 respektively. So that's not
it.

And if by kernel log, you mean the kernel ring buffer, then that's clean (well,
no, but clean from anything relating to sound or IRQs anyway).

Thanks!

/ Peter Schuller
----------------
E-Mail: scode_ufp@usa.net
Web: http://hem.passagen.se/petersch


