From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: mjander@users.sourceforge.net
Cc: Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA lib application compatibility [was] Re: mixer device
Date: Tue, 18 May 2004 15:49:22 +0100 [thread overview]
Message-ID: <40AA2272.6060306@superbug.demon.co.uk> (raw)
In-Reply-To: <1084887054.1835.14.camel@localhost>
Manuel Jander wrote:
>
> As the main author of the Aureal Vortex driver, its very stupid having
> to handle arbitrary period sizes, introducing a lot of overhead and
> complexity in the driver, while the hardware just is not designed to
> handle period sizes that are not powers of two, due to page boundary
> overlapping trouble.
You don't have to handle arbitary period sizes in the alsa-driver.
Here is an example from the emu10k1 driver, that restricts what period
sizes the application can use for caputure.
static unsigned int capture_period_sizes[31] = {
384, 448, 512, 640,
384*2, 448*2, 512*2, 640*2,
384*4, 448*4, 512*4, 640*4,
384*8, 448*8, 512*8, 640*8,
384*16, 448*16, 512*16, 640*16,
384*32, 448*32, 512*32, 640*32,
384*64, 448*64, 512*64, 640*64,
384*128,448*128,512*128
};
static snd_pcm_hw_constraint_list_t hw_constraints_capture_period_sizes = {
.count = 31,
.list = capture_period_sizes,
.mask = 0
};
static int snd_emu10k1_capture_open(snd_pcm_substream_t * substream)
{
<snip>
snd_pcm_hw_constraint_list(runtime, 0, SNDRV_PCM_HW_PARAM_PERIOD_SIZE,
&hw_constraints_capture_period_sizes);
<snip>
Has a driver writer, you have full control over these sorts of things.
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-18 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 19:51 mixer device Ronald S. Bultje
2004-05-12 15:40 ` Clemens Ladisch
2004-05-13 15:34 ` Adam Tla/lka
2004-05-13 15:51 ` Paul Davis
2004-05-13 16:28 ` Giuliano Pochini
2004-05-13 17:10 ` Adam Tla/lka
2004-05-18 13:46 ` barat
2004-05-18 13:30 ` ALSA lib application compatibility [was] " Manuel Jander
2004-05-18 14:49 ` James Courtier-Dutton [this message]
2004-05-18 15:00 ` Takashi Iwai
2004-05-18 14:23 ` ALSA lib application compatibility [was] Re: [Alsa-devel] " Manuel Jander
2004-05-19 10:27 ` Jaroslav Kysela
2004-05-18 15:55 ` ALSA lib application compatibility [was] Re: mi Giuliano Pochini
2004-05-14 8:22 ` mixer device Ronald S. Bultje
2004-05-18 10:31 ` Clemens Ladisch
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=40AA2272.6060306@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mjander@users.sourceforge.net \
/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.