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] An explanation of a2dpd weird behaviour	on	high	resolution timers enabled kernels
Date: Mon, 13 Aug 2007 12:05:38 +0200	[thread overview]
Message-ID: <1186999538.6698.141.camel@violet> (raw)
In-Reply-To: <1186999158.6262.10.camel@ubuntu.mpl.access-company.com>

Hi Frederic,

> > you might wanna focus on the Bluetooth audio service in bluez-utils (the
> > code got committed today) which now has A2DP support.
> 
> That's great news !!! I was thinking of this coming out soon, but didn't expect something so early.

the CSR based headphones seem to work pretty good so far. We have some
minor issues on the AVDTP protocol level, but they are fixable. The
current big issue are the Broadcom based headphones. While CSR seems to
be quite forgiving if you send data too fast (actually I think they use
flow control in the baseband to slow us down), the Broadcom ones are
not. We have to send the next SBC frame at the exact time slot.
Otherwise the audio sounds too fast or frames are skipped. If you have
any ideas on how we can improve pcm_bluetooth.c (yes, that handling is
inside the ALSA plugin), I would like to know.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-08-13 10:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11  9:48 [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels Fabien Chevalier
2007-08-11 18:01 ` Marcel Holtmann
2007-08-12 10:22   ` Fabien Chevalier
2007-08-13  9:59   ` Frederic Dalleau
2007-08-13 10:05     ` Marcel Holtmann [this message]
2007-08-13 15:54       ` Fabien Chevalier
2007-08-13 17:04         ` Marcel Holtmann
2007-08-13 17:49           ` Frederic Dalleau
2007-08-14  2:39             ` Luiz Augusto von Dentz
2007-08-14 12:51             ` Fabien Chevalier
2007-08-14 14:47               ` Frederic Dalleau
2007-08-14 16:40                 ` Marcel Holtmann
2007-08-17 10:42                 ` Fabien Chevalier
2007-08-17 11:06                   ` Marcel Holtmann
2007-08-18 14:13                     ` Fabien Chevalier
2007-08-17 13:41                   ` Frederic Dalleau
2007-08-14 12:51           ` Fabien Chevalier
2007-08-14 16:44             ` Marcel Holtmann
2007-08-14 19:31               ` [Bluez-devel] Gnome Protocol Analyzer tjoconno
2007-08-17 11:17               ` [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels Fabien Chevalier
2007-08-17 11:32                 ` Marcel Holtmann

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=1186999538.6698.141.camel@violet \
    --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