Hi, Here is a new status update of the BLE development. Changes since the first status report: 1. SM patches refactoring based on the comments of the maintainers in the ML 2. Use the LTK after receiving a LE Security Request: basically for re-connections 3. initial LE scanning before connections(re-connections) if the entry is not found in the cache (unstable) Proximity Link Loss and Find are now working. Tested using real hardware(key fobs). Proximity Path Loss needs improvement, is there someone in the BlueZ ML interested in helping us? At the moment we are using hard-coded values for RSSI thresholds: -60(low RSSI threshold) and -75(high RSSI threshold) We need to improve the logic to define the SignalLevel(good, regular, weak) properly based on the measured RSSI, Remote TX Power and other parameter that could influence the results. * Unstable kernel with Interleaved Discovery, RSSI Threshold monitor, LE scanning and remaining SM patches [1] http://git.infradead.org/users/vcgomes/linux-2.6.git (branch proximity-integration) * BlueZ Userspace [2] git://git.infradead.org/users/cktakahasi/bluez.git proximity-devel 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
