Hi Lukasz, > It can happen that controller will schedule ACL data > containing L2CAP connect request to host just before > encryption change event, even though link is encrypted on > LMP level before L2CAP connect request come. > With this fix, L2CAP layer will handle such scenario. I really don't like to have a work around for this. It is clearly a bug in the controller. 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
