From: Mikel Astiz <mikel.astiz@xxxxxxxxxxxx> Resending v3 with a small change in patch 3/16, where the "Name" property of org.bluez.Device1 is now considered as optional. This version is intended for the next branch since it depends on module-bluetooth-device not making use of device->name, which could now be potentially NULL. Note that the last 5 patches are somewhat controversial (see below) and it might therefore be desireable to keep them on hold. >From previous cover-letter: The discussion raised by Jo?o Paulo is whether the HSP/HFP endpoint should be registered or not, and the few associated features implemented. Luiz suggested it'd be good in any case to have the patches for reference, so I'm sending the full patchset (including the HSP/HFP part) reworked in a way that such code is grouped in the end (starting with v3 12/16). Mikel Astiz (15): bluetooth: Detect BlueZ 5 bluetooth: Parse the tree returned by ObjectManager bluetooth: Support ObjectManager interface add/remove bluetooth: Support Properties.PropertiesChanged signal bluetooth: BlueZ 5 interface rename to org.bluez.MediaEndpoint1 bluetooth: BlueZ 5 interface rename to org.bluez.Media1 bluetooth: BlueZ 5 interface rename to org.bluez.MediaTransport1 bluetooth: Parse media transport's properties bluetooth: Support media transport's State property bluetooth: Update to new BlueZ 5 transport acquire/release API bluetooth: Support transport auto-release bluetooth: Register HSP/HFP endpoints in BlueZ 5 Media API bluetooth: Handle transports configured before UUID received bluetooth: Update to new property setter API in BlueZ 5 bluetooth: Update to volume control in BlueZ 5 Vinicius Costa Gomes (1): bluetooth: Add HFP 1.6 codec ID src/modules/bluetooth/bluetooth-util.c | 568 ++++++++++++++++++++++-- src/modules/bluetooth/module-bluetooth-device.c | 8 +- 2 files changed, 521 insertions(+), 55 deletions(-) -- 1.8.1.4
