public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Big patch to a2dpd
Date: Wed, 06 Sep 2006 11:33:02 +0200	[thread overview]
Message-ID: <44FE95CE.1090502@palmsource.com> (raw)
In-Reply-To: <44FE42C7.7030100@xmission.com>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Hi,

> Lea
>
>   
>> Yes. I prefer modifying alsa_transfer_raw(), which makes the framework logic consistent. How do you think about it? 
>>     
>
> I'm not familiar with this new stuff, but it seems that the return
> values were commented out for some reason and maybe forgotten. If
> Frederic has no problems with the change to alsa_transfer_raw, I'll do
> it that way.
>   

Hi Brad and Lea,
No it's not forgotten : what I wanted is to restart audio on errors. I
had some failures when trying to recover : when pausing a stream in
xmms, an underrun occurs as the alsa device is not closed.
However, I didn't investigate the xrun_recovery return value.
Lea's patch is interesting but it miss something : the xrun_recovery
will ALWAYS return 0 if fed with EPIPE or ESIGPIPE, whether the recovery
succeed or not.
The cleanest is to keep Lea's patch but remove the two "return 0;" calls
in order to "return err;" at the end of the func.

The modification to a2dpd.c should not be done.

See the following :

static int xrun_recovery(snd_pcm_t * handle, int err)
{
if (err == -EPIPE) { /* under-run */
err = snd_pcm_prepare(handle);
if (err < 0)
printf("Can't recovery from underrun, prepare failed: %s\n",
snd_strerror(err));
return 0; // ------------------------ Remove this line to return err at
the end of the func
} else if (err == -ESTRPIPE) {
while ((err = snd_pcm_resume(handle)) == -EAGAIN)
sleep(1); /* wait until the suspend flag is released */
if (err < 0) {
err = snd_pcm_prepare(handle);
if (err < 0)
printf("Can't recovery from suspend, prepare failed: %s\n",
snd_strerror(err));
}
return 0;// ------------------------ Remove this line to return err at
the end of the func
}
return err;
}





[-- Attachment #2: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-09-06  9:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  3:12 [Bluez-devel] Big patch to a2dpd Li, Lea
2006-09-06  3:38 ` Brad Midgley
2006-09-06  9:33   ` Frédéric DALLEAU [this message]
2006-09-07 16:48     ` Andrew Waldram
2006-09-07 19:47       ` Brad Midgley
2006-09-07 20:36         ` Michael Frey
2006-09-07 22:46           ` Brad Midgley
2006-09-07 21:06         ` Andrew Waldram
2006-09-07 22:52           ` Brad Midgley
  -- strict thread matches above, loose matches on Subject: below --
2006-09-02  6:21 Li, Lea
2006-09-06  3:06 ` Brad Midgley
2006-09-02  6:04 Li, Lea
2006-09-02 13:02 ` Michael Frey
2006-08-23 16:55 [Bluez-devel] Small " Frédéric DALLEAU
2006-08-30 14:45 ` Brad Midgley
2006-08-31 16:04   ` [Bluez-devel] Big " Frédéric DALLEAU
2006-09-01 12:57     ` andy
2006-09-01 18:25       ` Michael Frey
2006-09-02 16:05     ` Brad Midgley
2006-09-02 16:08     ` Brad Midgley
2006-09-02 17:01       ` Brad Midgley

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=44FE95CE.1090502@palmsource.com \
    --to=frederic.dalleau@palmsource.com \
    --cc=bluez-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox