From: Takashi Iwai <tiwai@suse.de>
To: Santiago Otero <santiago@atlas.uvigo.es>
Cc: ALSA-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Request for tests: scatter-gather dma support on via686 and emu10k1
Date: Tue, 30 Jul 2002 17:06:43 +0200 [thread overview]
Message-ID: <s5hu1mh8dbw.wl@alsa2.suse.de> (raw)
In-Reply-To: <1027444734.657.8.camel@atenea>
At 23 Jul 2002 19:18:53 +0200,
Santiago Otero wrote:
>
> El mar, 23-07-2002 a las 11:21, Takashi Iwai escribi�:
>
> >
> > ok, could you show me the values listed in the proc file above during
> > playback/record?
> > i guess the buffer size is not aligned to the period size, and the
> > number of period is relatively small.
> >
>
> playing sound:
>
> $cat /proc/asound/card0/pcm0p/sub0/hw_params
> access: RW_INTERLEAVED
> format: S16_LE
> subformat: STD
> channels: 2
> rate: 44100 (44100/1)
> period_size: 16
> buffer_size: 16384
> tick_time: 10000
i guess you didn't set up the period size in your application
explicitly, right?
that's why it gives so small value.
on the previous driver, there was a constraint about the period and
the buffer sizes, and perhaps this increased the minimum period size
eventually.
this constraint was disabled for the time being, because this likely
conflicts with the new constraint, period size = power of two.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
prev parent reply other threads:[~2002-07-30 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 17:19 Request for tests: scatter-gather dma support on via686 and emu10k1 Takashi Iwai
[not found] ` <1027166734.759.8.camel@atenea>
[not found] ` <s5hptxgovji.wl@alsa2.suse.de>
2002-07-22 16:21 ` Santiago Otero
2002-07-23 9:21 ` Takashi Iwai
2002-07-23 17:18 ` Santiago Otero
2002-07-30 15:06 ` 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=s5hu1mh8dbw.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=santiago@atlas.uvigo.es \
/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.