From: Fabien Chevalier <fabchevalier@free.fr>
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: Fri, 17 Aug 2007 13:17:19 +0200 [thread overview]
Message-ID: <46C583BF.9080705@free.fr> (raw)
In-Reply-To: <1187109870.6698.287.camel@violet>
Hi Marcel,
>
> I might be simply never hear the difference,
Well, you will, however not always, this will be dependant upon the
bluetooth devices used, so that might work for you but fail for someone
else if those clock drifting issues are not handled properly.
but anyway, we can actually
> do this. However the implementation is tricky. The plugin should not
> send HCI commands at all. Actually no daemon (except hcid) should send
> any HCI commands at any time.
Woops, didn't know about that :-(
Are there any hard constraints behing this limitation or is it just a
good software architecturing rule that prevents us from doing it ?
> I can make the kernel to as for the clock
> offset in a certain interval.
Just for my own comprehension : could you expose here how do you intend
to implement this ?
> This costs too since it has to go over the
> same HCI link that the audio data goes.
Agreed :-)
> So at which rate do you need
> this information?
Let's say we are unlucky and we got the master clock and the main CPU
clock to drift each of 250 ppm in opposite directions. That leaves use
with a 30 ms per minute drift.
I'd say a clock resynch every 20-30 seconds should be enough, and would
limit the drift at any time below 15 mseconds, which should be
compensated byt the headset side buffering.
So let's say i need this information every ~20 seconds.
Note : of course this is for a2dp only, sco matters are completely
different.
Cheers,
Fabien
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-08-17 11:17 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
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 ` Fabien Chevalier [this message]
2007-08-17 11:32 ` [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels 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=46C583BF.9080705@free.fr \
--to=fabchevalier@free.fr \
--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