From: VDR User <user.vdr@gmail.com>
To: John Lindgren <john.lindgren@tds.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsa-lib: snd_pcm_delay and friends do not account for a write being currently in progress
Date: Thu, 3 Jun 2010 10:40:02 -0700 [thread overview]
Message-ID: <AANLkTil3VZiQe5wSezaDRXtekheR6d_hs7wKK6Ku7puX@mail.gmail.com> (raw)
In-Reply-To: <1275514176.8032.42.camel@satellite>
On Wed, Jun 2, 2010 at 2:29 PM, John Lindgren <john.lindgren@tds.net> wrote:
> In a multi-threaded application it is possible for snd_pcm_delay or an
> equivalent function to be called by one thread while another is sitting
> in snd_pcm_writei. In this case, snd_pcm_delay does not take into
> account that there may not be enough space for all the data passed to
> snd_pcm_writei to be written to the ring buffer at once, and will return
> incorrect values.
Hi. I've been getting "pcm_hw.c: snd_pcm_hw_delay()
SNDRV_PCM_IOCTL_DELAY failed." in my xine log and after some talks
with one of the devs, he suggested that alsa was not getting data fast
enough in some cases (iirc). Could you please email me a copy of your
patch (so I don't have to hand-patch) to try? Hopefully it will fix
this damn problem once and for all.
Thanks,
Derek
next prev parent reply other threads:[~2010-06-03 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:29 [PATCH] alsa-lib: snd_pcm_delay and friends do not account for a write being currently in progress John Lindgren
2010-06-03 6:40 ` Clemens Ladisch
2010-06-03 14:00 ` John Lindgren
2010-06-03 14:48 ` Clemens Ladisch
2010-06-03 16:16 ` John Lindgren
2010-06-03 17:03 ` Clemens Ladisch
2010-06-03 17:51 ` John Lindgren
2010-06-03 14:40 ` [PATCH] " James Courtier-Dutton
2010-06-03 16:10 ` John Lindgren
2010-06-03 16:34 ` James Courtier-Dutton
2010-06-03 18:06 ` John Lindgren
2010-06-03 17:40 ` VDR User [this message]
2010-06-03 18:08 ` John Lindgren
2010-06-04 6:50 ` 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=AANLkTil3VZiQe5wSezaDRXtekheR6d_hs7wKK6Ku7puX@mail.gmail.com \
--to=user.vdr@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=john.lindgren@tds.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).