From alsa-devel-owner@alsa.jcu.cz  Mon Feb 15 09:35:07 1999
Received: from mgate2.uni-hannover.de (root@mgate2.uni-hannover.de [130.75.2.5])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id JAA04539
	for <alsa-devel@alsa.jcu.cz>; Mon, 15 Feb 1999 09:33:56 +0100
Received: from helios.tnt.uni-hannover.de by mgate2.uni-hannover.de 
          with LocalSMTP (PP) with ESMTP; Mon, 15 Feb 1999 09:33:43 +0100
Received: from sokrates.tnt.uni-hannover.de (pahl@sokrates.tnt.uni-hannover.de [130.75.31.157]) 
          by helios.tnt.uni-hannover.de (8.8.8/8.8.8) with ESMTP id JAA12152;
          Mon, 15 Feb 1999 09:33:41 +0100 (MET)
Received: (from pahl@localhost) by sokrates.tnt.uni-hannover.de (8.8.8/8.8.8) 
          id JAA30296; Mon, 15 Feb 1999 09:33:40 +0100
Date: Mon, 15 Feb 1999 09:33:40 +0100
Message-Id: <199902150833.JAA30296@sokrates.tnt.uni-hannover.de>
From: Martin Pahl <pahl@tnt.uni-hannover.de>
To: alsa-devel@alsa.jcu.cz, Jaroslav Kysela <perex@jcu.cz>
Subject: Driver for ZA2 - output works
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

It took a long time, but I found the bug!!!

I just forgot to send the sync-samples to the card :-).

Ok, you can get the newest version of the driver from

ftp://ftp.tnt.uni-hannover.de/pub/misc/alsa-za2/

Only output is tested so far. But this should work with 16bit, stereo,
20kHz-60kHz. You shouldn't pause the driver as resyncing probably does
not work so far. Another problem is DMA. It seems that the DMA starts
running directly after enabling in snd_dma_programm although it should
start after setting the bits in the ZA2-command-register. I don't know
why. If you notice switched left and right channels comment out
enable_dma in snd_dma_programm in kernel/isadma.c. In my opinion it's
a better idea to always let the driver enable the dma at the right
point. Maybe this can be changed in ALSA (Jaroslav?). 

Martin Pahl

