From mboxrd@z Thu Jan  1 00:00:00 1970
From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Subject: Re: sw parameter boundary
Date: Thu, 26 Jun 2008 16:36:36 +0200
Message-ID: <4863A974.5030502@aimvalley.nl>
References: <48620563.3050207@aimvalley.nl>	<s5h3an18qmu.wl%tiwai@suse.de>	<4863569C.5040502@aimvalley.nl>
	<s5hiqvwqz14.wl%tiwai@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30])
	by alsa0.perex.cz (Postfix) with ESMTP id 5854C2465B
	for <alsa-devel@alsa-project.org>;
	Thu, 26 Jun 2008 16:36:39 +0200 (CEST)
Received: from mail3.aimsys.nl (a80-127-156-242.adsl.xs4all.nl
	[80.127.156.242])
	by smtp-vbr10.xs4all.nl (8.13.8/8.13.8) with ESMTP id m5QEacED041201
	for <alsa-devel@alsa-project.org>;
	Thu, 26 Jun 2008 16:36:38 +0200 (CEST)
	(envelope-from nvbolhuis@aimvalley.nl)
In-Reply-To: <s5hiqvwqz14.wl%tiwai@suse.de>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: alsa-devel@alsa-project.org
List-Id: alsa-devel@alsa-project.org

 >> OK, but what does an ALSA driver need to do with boundary, nothing ?
 >
 > The boundary is aligned to buffer_size so that the offset can be
 > calculated properly even after the overwrap.
 >

OK, so I assume that's a yes.
I don't see any driver maniplating boundary though.


-- 
This message has been scanned for viruses and is believed to be clean