Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 202515] Bluetooth LE Extended Connect returning Command Disallowed
Date: Wed, 06 Feb 2019 08:27:47 +0000
Message-ID: <bug-202515-62941-H44wtQtG9m@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202515-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202515

--- Comment #2 from Johan Hedberg (johan.hedberg@gmail.com) ---
According to the Bluetooth core spec, HCI_LE_Extended_Create_Connection is
octet 37, bit 7 in the supported commands mask. In the supported commands that
your controller returns octet 37 is 0xdf which does have bit 7 set, i.e. it's
claiming to support the extended version of the command. The way this kind of
issues are normally worked around is by introducing a so-called quirk flag that
gets set (usually by the HCI driver) when a problematic controller is
identified. It might be worth checking first however if there's a newer
firmware available for your controller - perhaps the issue has already been
fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  0:01 [Bug 202515] New: " bugzilla-daemon
2019-02-06  8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06  8:27 ` bugzilla-daemon [this message]
2019-02-06  9:07 ` bugzilla-daemon
2019-02-06  9:42 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:19 ` bugzilla-daemon
2019-02-06 11:58 ` bugzilla-daemon
2019-02-06 12:18 ` bugzilla-daemon
2019-02-06 19:36 ` bugzilla-daemon
2019-02-07 12:59 ` bugzilla-daemon
2019-02-07 22:55 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-07 23:48 ` bugzilla-daemon
2019-02-08 16:16 ` bugzilla-daemon
2019-02-08 17:35 ` bugzilla-daemon
2019-02-08 21:39 ` bugzilla-daemon

Reply instructions:

You may reply publically 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=bug-202515-62941-H44wtQtG9m@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox