Message-ID: <4D516A85.5070604@t-online.de>
Date: Tue, 08 Feb 2011 17:08:37 +0100
From: Knut Petersen <Knut_Petersen@t-online.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.16) Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11
MIME-Version: 1.0
To: Jaroslav Kysela <perex@perex.cz>
CC: tiwai@suse.de, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: ALSA: Reasonable buffer size / where should it be implemented?
References: <4D511552.7030409@t-online.de> <alpine.LNX.2.00.1102081109170.6272@eeebox2.perex-int.cz>
In-Reply-To: <alpine.LNX.2.00.1102081109170.6272@eeebox2.perex-int.cz>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 775
Lines: 21


> It's probably the right way to go. I would only copy data in a tasklet
> not directly in the interrupt routine. New hardware (like HDA) have
> scatter-gather DMA buffers with almost unlimited size, so users can
> just tune the system up.
>
Well, obviously recording to /dev/null has a better chance not to
hit xrun problems ;-)

So I'll clean up my q&d rme96.c code and submit it.

I have not had a look at the sources ... is arecord "right behaving"
or which command line recording tool could be used if it is not?

cu,
 Knut
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/