Hi all, Interleave BR/EDR/LE discovery is implemented, the next step in the user space is how to manage advertising and LE connections. Some aspects: 1. Only one LE connection is allowed(per peer), meaning only one GAttrib instance will be allowed otherwise it will not be possible to serialize commands/events 2. The remote/Peripheral can support more than one GATT primary service 3. We are planning to use "direct" connections only, meaning that we will not use whitelist and the application interested must inform the remote address/object to connect to. 4. Kernel manages the connection establishment, currently there isn't a way to change the connection parameters. BMI or ioctls will be required to change the default parameters and also to trigger SMP negotiation. Some ideas: 1. implement a characteristic driver: basically to provide an abstraction to GATT clients. ex: Proximity, Health, ... 2. We don't need to implement Proximity and other GATT clients as a plugin at the moment, it can be enabled automatically by --enable-attrib 3. GATT clients could register a watcher/filter for advertising events 4. GATT clients doesn't need to know ATT, in theory it can handle characteristics only 5. GATT clients needs to control/request LE connections based on the advertisement received An initial draft implementing part of this idea is here: git://git.infradead.org/users/cktakahasi/bluez.git devel Comments? Regards, Claudio -- 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
