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 09:07:21 +0000 [thread overview]
Message-ID: <bug-202515-62941-xtWcK5SV5C@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 #3 from Mathias Tillman (master.homer@gmail.com) ---
I believe it is using the latest firmware, I haven't been able to find a later
one than the one mentioned in the kernel log anyway:
[ 6.478466] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
[ 8.361085] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-18-16-1.ddc
And yeah, the controller clearly reports that the Extended Create Connection
command is available, so it is a bit odd that it's not working correctly. I
suppose the only way to find out why would be to debug the controller, but I
have no idea how one would go about doing that.
I haven't found this issue being reported at all, so I don't know if it's just
my card, or if all of them have this issue. I know the 9260 is commonly used in
laptops, but I couldn't say to what extent. Perhaps there is someone who has
this card that could test, and if it is in fact broken, add a quirk as you
suggested that would force legacy mode?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-02-06 9:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 0:01 [Bug 202515] New: Bluetooth LE Extended Connect returning Command Disallowed bugzilla-daemon
2019-02-06 8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06 8:27 ` bugzilla-daemon
2019-02-06 9:07 ` bugzilla-daemon [this message]
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 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=bug-202515-62941-xtWcK5SV5C@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
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).