From: Knut Petersen <Knut_Petersen@t-online.de>
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?
Date: Tue, 08 Feb 2011 17:08:37 +0100 [thread overview]
Message-ID: <4D516A85.5070604@t-online.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1102081109170.6272@eeebox2.perex-int.cz>
> 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
prev parent reply other threads:[~2011-02-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 10:05 ALSA: Reasonable buffer size / where should it be implemented? Knut Petersen
2011-02-08 10:21 ` Jaroslav Kysela
2011-02-08 10:21 ` Jaroslav Kysela
2011-02-08 16:08 ` Knut Petersen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D516A85.5070604@t-online.de \
--to=knut_petersen@t-online.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.