From alsa-devel-owner@alsa.jcu.cz  Thu Jan 14 18:33:39 1999
Received: from ife.ee.ethz.ch (ife-fast.ee.ethz.ch [129.132.24.193])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id SAA27363
	for <alsa-devel@alsa.jcu.cz>; Thu, 14 Jan 1999 18:33:35 +0100
Received: from ife.ee.ethz.ch (eldrich.ee.ethz.ch [129.132.24.203])
	by ife.ee.ethz.ch (8.8.5/8.8.5) with ESMTP id SAA05030
	for <alsa-devel@alsa.jcu.cz>; Thu, 14 Jan 1999 18:33:34 +0100 (MET)
Message-ID: <369E2A6E.FD29AA32@ife.ee.ethz.ch>
Date: Thu, 14 Jan 1999 18:33:34 +0100
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
MIME-Version: 1.0
To: alsa-devel@alsa.jcu.cz
Subject: Re: ISA DMA problems
References: <Pine.LNX.3.96.990114151016.19753H-100000@entry.jcu.cz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Jaroslav Kysela wrote:

> We can do some workarounds, of course. For example write one module which
> should be loaded immediately after system boot and allocate some space for
> requested number of DMA channels. Any other ideas?

No, but if you implement it that way, please do it directly in the
kernel's kmalloc-implementation (possibly conditionally if there's
more than 16M RAM in the box).

Tom

