From alsa-devel-owner@alsa.jcu.cz  Tue Oct 13 22:54:28 1998
Received: from obelix.fvdpol.inter.nl.net (frank@bd99-27.Breda.NL.net [193.79.246.252])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id WAA28596
	for <alsa-devel@jcu.cz>; Tue, 13 Oct 1998 22:52:09 +0200
Received: (from frank@localhost) by obelix.fvdpol.inter.nl.net (8.8.7/8.7.3) id VAA06682; Tue, 13 Oct 1998 21:51:54 +0100
From: Frank van de Pol <F.K.W.van.de.Pol@Inter.NL.net>
Message-Id: <199810132051.VAA06682@obelix.fvdpol.inter.nl.net>
Subject: Re: [linux-audio-dev] What to do ??? (fwd)
To: alsa-devel@jcu.cz
Date: Tue, 13 Oct 1998 21:51:53 +0100 (MET)
Cc: P.J.Leonard@bath.ac.uk (Paul Leonard)
In-Reply-To: <3621C2B9.6231@bath.ac.uk> from "P.J.Leonard" at Oct 12, 98 09:50:02 am
Content-Type: text
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

P.J.Leonard wrote:
> 
> [snip]
> 
> >    MIDI oriented applications (could also be MOD players): What is needed
> >    in the ALSA Sequencer API to let your application work with the new
> >    sequencer architecture? 
> 
>  An AWE32 driver ? (If I had the time I would do it myself) 
> 

This AWE32 driver is a piece of software (sequencer client) that makes use
of the API. To rephrase my question: What needs to be added/changed to the
sequencer API to allow someone to implement this AWE32[1] driver.

[1] replace with any other soundcard we need drivers for.

Regards,
Frank.

+---- --- -- -  -   -    - 
|Frank van de Pol                  -o)
|F.K.W.van.de.Pol@inter.NL.net     /\\
|                                 _\_v
|Linux - Why use Windows, since there is a door?
|
|ALSA Sequencer: http://www.inter.nl.net/users/F.K.W.van.de.Pol/alsa/

