public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] a2dp_write patch
Date: Fri, 08 Aug 2008 00:06:40 +0200	[thread overview]
Message-ID: <1218146801.7819.40.camel@californication> (raw)
In-Reply-To: <3837d8b10807250948l20d30a1ld9f2867b382f54f7@mail.gmail.com>

Hi Keith,

> > Well done, now Im wondering if it isn't possible to use alsa buffer
> > all the time instead of copying to a temporary buffer?
> 
> You definitely can't depend on the buffer still being there.   There
> are two options, you can just refuse to process any part of the buffer
> that is not a certain size, or you can do what we are trying to do and
> store it off temporarily.   I think the last is the best solution,
> because it makes it easier on the our clients,  we have to deal with
> the extra instead of an application needed to deal with half processed
> buffers.

I applied your patch to the BlueZ 4.x repository. Thanks.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-08-07 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 19:38 [Bluez-devel] [PATCH] a2dp_write patch keith preston
2008-07-24 20:45 ` Luiz Augusto von Dentz
2008-07-25 16:48   ` keith preston
2008-08-07 22:06     ` Marcel Holtmann [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=1218146801.7819.40.camel@californication \
    --to=marcel@holtmann.org \
    --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