Hi Justin, * Justin P. Mattock <justinmattock@xxxxxxxxx> [2011-03-16 12:11:10 -0700]: > On 03/16/2011 12:01 PM, Gustavo F. Padovan wrote: > > Hi Anderson, > > > > * Anderson Lizardo<anderson.lizardo@xxxxxxxxxxxxx> [2011-03-16 14:48:31 -0400]: > > > >> Hi Gustavo, > >> > >> On Wed, Mar 16, 2011 at 2:46 PM, Gustavo F. Padovan > >> <padovan@xxxxxxxxxxxxxx> wrote: > >>> > >>> * Gustavo F. Padovan<padovan@xxxxxxxxxxxxxx> [2011-03-16 15:44:46 -0300]: > >>> > >>>> We can't send new commands before a cmd_complete for the HCI_RESET commnnd > >>>> shows up. > >>>> > >>>> Reported-by: Mikko Vinni<mmvinni@xxxxxxxxx> > >>>> Reported-by: Justin P. Mattock<justinmattock@xxxxxxxxx> > >>>> Reported-by: Ed Tomlinson<edt@xxxxxx> > >>>> Signed-off-by: Gustavo F. Padovan<padovan@xxxxxxxxxxxxxx> > >>>> --- > >>>> include/net/bluetooth/hci.h | 2 ++ > >>>> net/bluetooth/hci_core.c | 3 +++ > >>>> net/bluetooth/hci_event.c | 4 +++- > >>>> 3 files changed, 8 insertions(+), 1 deletions(-) > >>> > >>> It works for me, but can someone test this and then add a Tested-by line. > >>> Thanks. > >> > >> Which hardware is needed to test this? > > > > I don't know, I have a dongle that can cause this issue. It's CSR 1.1. > > I don't know which other dongles have a similar issue. > > > > I started to test this out, but crapped out at hci_cmd_timer with the > current Mainline do you have this for the current? No, it's based on bluetooth-next (2.6.39). But you can drop the hci_cmd_timer part while testing it. It's not needed unless you have and hci_reset cmd timeout. -- Gustavo F. Padovan http://profusion.mobi -- 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
