From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: snd_pcm_wait() More details required.
Date: Sun, 21 Mar 2004 14:49:00 +0000 [thread overview]
Message-ID: <405DAB5C.5010106@superbug.demon.co.uk> (raw)
I need more details on exactly what snd_pcm_wait() is supposed to do.
The documentation on the www.alsa-project.org gives: -
Wait for a PCM to become ready.
Parameters:
pcm PCM handle
timeout maximum time in milliseconds to wait
Returns:
a positive value on success otherwise a negative error code (-EPIPE
for the xrun and -ESTRPIPE for the suspended status, others for general
errors)
Return values:
0 timeout occurred
1 PCM stream is ready for I/O
So, when is a PCM ready?
If a PCM is already in SND_PCM_STATE_RUNNING, when is snd_pcm_wait()
supposed to return ?
I have discovered a problem with xine when using it. I have done a work
around in xine so that dmix now works in xine. I think that my
assumptions regarding snd_pcm_wait() might have been wrong, so I want to
get accurate details from yourselves.
It also might be a good idea to update the documentation for
snd_pcm_wait() with more details.
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-03-21 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 14:49 James Courtier-Dutton [this message]
2004-03-22 9:56 ` snd_pcm_wait() More details required Jaroslav Kysela
2004-03-22 17:31 ` James Courtier-Dutton
2004-03-22 17:51 ` Jaroslav Kysela
2004-03-23 12:33 ` Clemens Ladisch
2004-03-23 13:40 ` Jaroslav Kysela
2004-03-24 7:58 ` Clemens Ladisch
2004-03-24 8:59 ` Jaroslav Kysela
2004-03-22 10:10 ` Clemens Ladisch
2004-03-22 10:09 ` Jaroslav Kysela
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=405DAB5C.5010106@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.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 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.