Hi, On Tue, Sep 25, 2012, João Paulo Rechi Vita wrote: > Since controllers don't support more than one ongoing connection > procedure at the same time, new connection attempts needs to yield if > there is an ongoing connection procedure already. Simply based on this description the first question that comes to mind is wouldn't this be better handled on the kernel side? After all other processes besides bluetoothd (like obexd) are also capable of initiating connections and we can't control that within bluetoothd. Johan -- 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
