All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Michael Schmitt <tcwardrobe@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something
Date: Fri, 18 Nov 2011 18:21:11 +0200	[thread overview]
Message-ID: <20111118162111.GA4680@fusion.localdomain> (raw)
In-Reply-To: <4EC67E88.6060202@gmail.com>

Hi Michael,

On Fri, Nov 18, 2011, Michael Schmitt wrote:
> < HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> > HCI Event: Command Complete (0x0e) plen 12
>     Read Local Version Information (0x04|0x0001) ncmd 1
>     status 0x00
>     HCI Version: 1.2 (0x2) HCI Revision: 0x2006
>     LMP Version: 1.2 (0x2) LMP Subversion: 0x1806
>     Manufacturer: AVM Berlin (31)

Ok, so this is a 1.2 adapter.

> < HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
> > HCI Event: Command Status (0x0f) plen 4
>     Read Local Supported Commands (0x04|0x0002) status 0x01 ncmd 1
>     Error: Unknown HCI Command

This is the reason why you're getting a timeout. Since the adapter
claims to support Bluetooth version 1.2 it should also support this HCI
command, so from that perspective it's not conforming to the
specification. Right now the kernel (lib/bluetooth/hci_event.c) is
completely missing a command status handler for this command. If such a
handler was in place instead of a timeout you would be getting an
immediate error (the kernel maps this HCI status code to EBADRQC).

However, since this is also not acceptable behavior (as the adapter
still wouldn't work for you) I suspect the need for some
adapter-specific quirk is in place or then the kernel should just ignore
any errors for HCI_Read_Local_Supported_Commands.

Johan

  reply	other threads:[~2011-11-18 16:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 15:28 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something Michael Schmitt
2011-11-18 15:36 ` Johan Hedberg
2011-11-18 15:49   ` Michael Schmitt
2011-11-18 16:21     ` Johan Hedberg [this message]
2011-11-18 16:34       ` Michael Schmitt
2011-11-18 20:30         ` Johan Hedberg
2011-11-20 15:27           ` Michael Schmitt
2011-11-27 10:04             ` Michael Schmitt
2011-11-28  8:42               ` Andrei Emeltchenko
2011-11-21  8:57       ` Andrei Emeltchenko
2011-11-21  9:12         ` Andrei Emeltchenko
2011-11-21  9:13         ` Marcel Holtmann
2011-11-21 10:22           ` Andrei Emeltchenko
2011-11-21 13:03             ` Marcel Holtmann
2011-11-21 10:35           ` Johan Hedberg
2011-11-21 13:04             ` Marcel Holtmann
2011-11-21 15:21               ` Johan Hedberg
2011-11-18 16:17   ` Michael Schmitt
2013-07-18 13:26 Jörg Esser
2013-07-18 14:13 ` Marcel Holtmann
2013-07-19  6:26   ` Jörg Esser
2013-07-19 13:49     ` Marcel Holtmann
2013-07-19 16:20       ` Johan Hedberg
2013-07-22  7:10         ` Jörg Esser
2013-07-22 14:22           ` Marcel Holtmann
2013-07-23 23:39             ` Johan Hedberg
2013-07-25  9:10               ` Jörg Esser
2013-07-25 10:55                 ` Gustavo Padovan
2013-07-25 14:51                   ` Marcel Holtmann
2013-07-25 14:40                 ` Marcel Holtmann

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=20111118162111.GA4680@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tcwardrobe@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.