From alsa-devel-owner@alsa.jcu.cz  Fri Jan 15 09:35:29 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 JAA23578
	for <alsa-devel@alsa.jcu.cz>; Fri, 15 Jan 1999 09:32:36 +0100
Received: from helios.tnt.uni-hannover.de by mgate2.uni-hannover.de 
          with LocalSMTP (PP) with ESMTP; Fri, 15 Jan 1999 09:30:36 +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 JAA27143;
          Fri, 15 Jan 1999 09:30:35 +0100 (MET)
Received: (from pahl@localhost) by sokrates.tnt.uni-hannover.de (8.8.8/8.8.8) 
          id JAA18130; Fri, 15 Jan 1999 09:30:35 +0100
Date: Fri, 15 Jan 1999 09:30:35 +0100
Message-Id: <199901150830.JAA18130@sokrates.tnt.uni-hannover.de>
From: Martin Pahl <pahl@tnt.uni-hannover.de>
To: alsa-devel@alsa.jcu.cz
CC: Andreas Eggenschwiler <res@inorg.chem.ethz.ch>,
        Bill Gribble <grib@cs.utexas.edu>
Subject: Non working driver for ZA2
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

If there is somebody not knowing what to do at the weekend and owning
a ZA2 here is a non-working device-driver for that device.

I described the problems in the mailing-list and couldn't solve it so
far. Maybe it's a problem with my hardware. I don't know and I do not
have the time to test it right now.

You can get the device-driver from 

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

Martin Pahl

-- 
Martin Pahl                                email: pahl@tnt.uni-hannover.de  

Institut fuer Theoretische Nachrichtentechnik und Informationsverarbeitung
Universitaet Hannover                 http://www.tnt.uni-hannover.de/~pahl

