From alsa-devel-owner@alsa.jcu.cz  Wed Oct 28 18:53:32 1998
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id SAA28108;
	Wed, 28 Oct 1998 18:51:11 +0100
Date: Wed, 28 Oct 1998 18:51:11 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: "P.J.Leonard" <P.J.Leonard@bath.ac.uk>
cc: iwai@ww.uni-erlangen.de, alsa-devel@jcu.cz
Subject: Re: ALSA + AWE32
In-Reply-To: <3636F539.237C@bath.ac.uk>
Message-ID: <Pine.LNX.3.96.981028184816.28810C-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Wed, 28 Oct 1998, P.J.Leonard wrote:

> Takashi Iwai <iwai@ww.uni-erlangen.de> wrote on the linux-awe mailing
> list
> 
> > I have a plan to rewrite the awedrv largely, especially about patch
> > loading and handling routines.  The samples can be cached on DRAM even
> > after released.  I noticed this necessity when I used chaos 12M fonts
> > on 8MB DRAM:  it takes a few seconds at each time for loaindg fonts
> > before playing a midi file.
> 
> Hello,
> 
>  There growing interest in the ALSA project http://alsa.jcu.cz/
> 
> If you are rewriting the awe stuff it would be nice if you could
> consider
> how best to allow integration of your drivers into this project.

It would be also nice separate abstract instrument handling from hardware.
For example - GUS soundcards (and maybe soundcards with Dream chip) have
same problems, too.. I think that instrument handling library should be in
separate module which will call lowlevel code..

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


