From: Takashi Iwai <tiwai@suse.de>
To: danny@mailmij.org
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] buffersize and constraints on pmac
Date: Wed, 15 Dec 2004 22:50:02 +0100 [thread overview]
Message-ID: <s5h3by7qlit.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0412152236040.15285-100000@luna.ellen.dexterslabs.com>
At Wed, 15 Dec 2004 22:40:03 +0100 (CET),
<danny@mailmij.org> wrote:
>
> On Wed, 15 Dec 2004, Takashi Iwai wrote:
>
> > At Wed, 15 Dec 2004 21:31:30 +0100 (CET),
> > <danny@mailmij.org> wrote:
> > >
> > > + /* constraints to fix choppy sound */
> > > + snd_pcm_hw_constraint_minmax(runtime, SNDRV_PCM_HW_PARAM_PERIODS, 3, UINT_MAX);
> >
> > This should be specified in snd_pmac_playback.periods_min and
> > snd_pmac_capture.periods_min statically.
> duh...ofcourse, sorries :)
>
> >
> > Others look fine. Could you regenerate the patch?
> >
> here you are..I wondered btw, why PMAC_MAX_FRAGS is set to what it is (32)
> since for me higher values seem to work as well. But since it doesn't seem
> broken I didn't touch it:)
Yep, usually 32 periods are enough :)
I applied your patch now to CVS, but it was done manually because your
mailer broke the patch with tab/space conversion. Please check the
CVS tree later whether I did correctly.
thanks,
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-12-15 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 20:31 [PATCH] buffersize and constraints on pmac danny
2004-12-15 21:23 ` Takashi Iwai
2004-12-15 21:40 ` danny
2004-12-15 21:50 ` Takashi Iwai [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=s5h3by7qlit.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=danny@mailmij.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox