Hi, Current Device1 interface doesn't handle dualmode devices very well and doesn't provide information if remote supports LE, BR/EDR or both. There is a problem with bond information, connected transport, supported technologies etc. Instead of duplicating properties which would require LE, BR/EDR and (as currently) mixed variants I propose having two separates interfaces DeviceSmart1 and DeviceClassic1 which would represent supported transports. Thanks to this applications can easily track if remote device is LE or not which is important eg with discovery where different apps can do different type of discovery or when it want to use profile only over specific transport. Eventually those new interfaces would deprecate Device1 interface. Comments are welcome. Szymon Janc (1): doc: Add DeviceClassic1 and DeviceSmart1 interfaces doc/device-classic-api.txt | 203 +++++++++++++++++++++++++++++++++++++++++++++ doc/device-smart-api.txt | 164 ++++++++++++++++++++++++++++++++++++ 2 files changed, 367 insertions(+) create mode 100644 doc/device-classic-api.txt create mode 100644 doc/device-smart-api.txt -- 2.6.2 -- 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
