Hi,
quick reply to myself:
On 02 November 2007, Vehmanen Kai wrote:
>Hmm, but for instance gsta2dpsink works with the iMuff
>headset, while the system-timer paced pcm_bluetooth.c doesn't.
oops, I mixed the headset models, it was something else
than iMuff. Anyways, it seems that some headsets take advantage
of L2CAP flow control (-> blocking writes to L2CAP will work
more reliably as we don't need to guesstimate hw_ptr), while
some don't (-> we have to use a system timer). Now my patch tries
to work with both (it uses a system timer, but can adjust the hw_ptr
if needed as well), but as Fabien pointed out, some cases are still
not handled. Now I guess a good follow-up question is that should
the plugin try to verify whether L2CAP flow-control is used
or not, and then adjust its behaviour...?
--
[email protected] (Kai Vehmanen)
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel