From alsa-devel-owner@alsa.jcu.cz  Fri Nov  6 07:05:20 1998
Received: from mail.alphalink.com.au (mail.alphalink.com.au [203.24.205.7])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id HAA04179
	for <alsa-devel@jcu.cz>; Fri, 6 Nov 1998 07:04:56 +0100
Received: from alphalink.com.au (andrew@ppp26-12-Melbourne.alphalink.com.au [203.62.182.121]) by mail.alphalink.com.au (8.8.8/8.6.9) with ESMTP id RAA30518 for <alsa-devel@jcu.cz>; Fri, 6 Nov 1998 17:04:50 +1100
Message-ID: <364291B3.BE7BD195@alphalink.com.au>
Date: Fri, 06 Nov 1998 17:05:39 +1100
From: Andrew Clausen <clausen@alphalink.com.au>
MIME-Version: 1.0
To: alsa list <alsa-devel@jcu.cz>
Subject: mmap
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

Hi,

What are the arguments for and against mmap()?  I would have thought
that
its a Good Thing, because it allows memory used for DMA buffers (for
example) to be accessed directly by the application.

Is mmap() supported by ALSA?
How do you know when each buffer is transferred?

Thanks,
Andrew Clausen




