https://bugzilla.kernel.org/show_bug.cgi?id=51831 --- Comment #7 from Konstantin A. Lepikhov <lakostis@xxxxxxxxxxxx> 2013-03-01 19:17:36 --- (In reply to comment #5) > Alan's advice is best -- please do that. But if you don't want to do that, > then could you at least explain what your patch is supposed to be doing? I'm > not sure that I understand how it is supposed to work... I'm also have such dongle and made some code digging. Looks like this commit break the initialization: commit a5040efa2017f3e4f1b4d5f40fd989567f3994c1 Author: Johan Hedberg <johan.hedberg@xxxxxxxxx> Date: Mon Jan 10 13:28:59 2011 +0200 Bluetooth: Add special handling with __hci_request and HCI_INIT To support a more dynamic HCI initialization sequence the __hci_request behavior requires some more changes. Particularly, the init sequence should be able to have conditionals in it (sending some HCI commands depending on the outcome of a previous command) instead of being a fixed list as it is right now. The reasons for these additional requirements are the moving all previously user space driven initialization commands to the kernel side as well as the support the Low Energy controllers. To fulfull these requirements the init sequence is made the only special case for multi-command requests and req_last_cmd is renamed to init_last_cmd. The hci_send_cmd function is changed to update init_last_cmd as long as the HCI_INIT flag is set. Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> Signed-off-by: Gustavo F. Padovan <padovan@xxxxxxxxxxxxxx> If I revert this (at least first part with HCI_INIT check), everything working fine. Maybe we need some device-specific hack there? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- 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
