From: Mikel Astiz <mikel.astiz@xxxxxxxxxxxx> This patch series includes patches that have been useful to connect two HCI-based SCO links simultaneously. This can be used for example to connect to HSP headsets at the same time. The patch series is divided in three groups: kernel patches, BlueZ userspace patches and PulseAudio patches for module-bluetooth-device. The kernel patches include some code cleanup and more importantly a dynamically changing alternate setting in btusb driver. These ideas have been taken from the patches I found in [1]. The last patch, “Bluetooth: Remove outgoing MTU check” should be considered with care, since there probably are better approaches to solve this (WIP). The BlueZ userspace patches add some necessary infrastructure to support such use-cases. The PulseAudio patches provide some changes to be able to test the rest of the code. The first three patches have been reused from a previously submitted patch series, and only the last two patches are relevant for this purpose. They provide some simple workarounds and should not be considered a proper solution. As I said, the easiest may to test these patches is by using two Bluetooth headsets. You should use the Media API (Enable=Media in audio.conf), connect both headsets, and use pacmd to set their profile to hsp. [1] http://bluetooth-alsa.sourceforge.net/future.html Mikel Astiz (7): btio: Fix bind SCO socket only if server audio: Fix gateway state check audio: Add multiple device search to manager media: Support multiple transports per endpoint media: Create multiple transports if needed media: Enable parallel requests to endpoint media: Increase hardcoded incoming MTU audio/device.c | 2 +- audio/manager.c | 33 +++++++++- audio/manager.h | 7 ++ audio/media.c | 183 +++++++++++++++++++++++++++++++++++----------------- audio/transport.c | 4 +- btio/btio.c | 5 +- 6 files changed, 165 insertions(+), 69 deletions(-) -- 1.7.7.6 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
