Hi Kyle, here again, patches to linux-bluetooth only please. > * Userspace can now specify connection parameters to override the > defaults prior to connecting to the device. > * The intention is that setsockopt() will be called before connect() is > called in userspace apps and BlueZ libraries. > * It is critical to set these parameters prior to connect() to avoid > issues with hardware that must arbitrate the antenna access between > Bluetooth LE and things like WiFi. Aggressive connect (and scan) > window and interval values result in significant WiFi degradation. > * Reduces the need to call the hci LE Connection Update Command to > override the "defaults" when the desired values are known ahead of > time. > * Add BT_LE_CONN_PARAM socket option. I am not convinced that this is a good idea. My idea is that bluetoothd should just program connection parameters into the kernel via mgmt and not via the L2CAP socket. Especially since with LE auto-connect handling most likely starting to use listen() + accept() instead in the future, the L2CAP socket is not a good option here. Regards Marcel -- 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
