linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>,
	linux-bluetooth@vger.kernel.org, mmvinni@yahoo.com, edt@aei.ca
Subject: Re: [PATCH] Bluetooth: Fix HCI_RESET command syncronization
Date: Wed, 16 Mar 2011 12:11:10 -0700	[thread overview]
Message-ID: <4D810B4E.7040702@gmail.com> (raw)
In-Reply-To: <20110316190154.GB2151@joana>

On 03/16/2011 12:01 PM, Gustavo F. Padovan wrote:
> Hi Anderson,
>
> * Anderson Lizardo<anderson.lizardo@openbossa.org>  [2011-03-16 14:48:31 -0400]:
>
>> Hi Gustavo,
>>
>> On Wed, Mar 16, 2011 at 2:46 PM, Gustavo F. Padovan
>> <padovan@profusion.mobi>  wrote:
>>>
>>> * Gustavo F. Padovan<padovan@profusion.mobi>  [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@yahoo.com>
>>>> Reported-by: Justin P. Mattock<justinmattock@gmail.com>
>>>> Reported-by: Ed Tomlinson<edt@aei.ca>
>>>> Signed-off-by: Gustavo F. Padovan<padovan@profusion.mobi>
>>>> ---
>>>>   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?

  reply	other threads:[~2011-03-16 19:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 22:29 re "bluetooth disabled" and "[BUG] usb problems in .38-rc3+" Mikko Vinni
2011-03-01  5:51 ` Justin Mattock
2011-03-02 14:00 ` Johan Hedberg
2011-03-03 10:54   ` Mikko Vinni
2011-03-03 14:31     ` Johan Hedberg
2011-03-04  4:47       ` Ville Tervo
2011-03-07 19:50       ` Mikko Vinni
2011-03-08 22:30         ` Justin P. Mattock
2011-03-09 21:23         ` Justin P. Mattock
2011-03-10  2:54           ` Ed Tomlinson
2011-03-10  7:32             ` Johan Hedberg
2011-03-10 18:02               ` Justin P. Mattock
2011-03-12  1:33               ` Gustavo F. Padovan
2011-03-12 17:44                 ` Justin P. Mattock
2011-03-16 18:44                   ` [PATCH] Bluetooth: Fix HCI_RESET command syncronization Gustavo F. Padovan
2011-03-16 18:46                     ` Gustavo F. Padovan
2011-03-16 18:48                       ` Anderson Lizardo
2011-03-16 19:01                         ` Gustavo F. Padovan
2011-03-16 19:11                           ` Justin P. Mattock [this message]
2011-03-16 19:15                             ` Gustavo F. Padovan
2011-03-16 20:02                               ` Justin Mattock
2011-03-16 21:13                                 ` Mikko Vinni
2011-03-16 22:33                                 ` Ed Tomlinson
2011-03-17 10:35                     ` Szymon Janc
2011-03-17 16:48                       ` Gustavo F. Padovan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D810B4E.7040702@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=anderson.lizardo@openbossa.org \
    --cc=edt@aei.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mmvinni@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).