From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 190831] Intel Bluetooth 8260 breaks with latest firmware
Date: Wed, 21 Dec 2016 18:08:39 +0000 [thread overview]
Message-ID: <bug-190831-62941-3vSebHR6lb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-190831-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=190831
--- Comment #2 from Jan Steffens <jan.steffens@gmail.com> ---
New firmware with old DDC indeed works. The "Setting Intel event mask failed"
message seen with the old firmware didn't reappear, either.
Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Bluetooth: hci0: Device revision is 5
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1424291 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 15526 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-12-21 18:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 17:54 [Bug 190831] New: Intel Bluetooth 8260 breaks with latest firmware bugzilla-daemon
2016-12-21 17:55 ` [Bug 190831] " bugzilla-daemon
2016-12-21 18:08 ` bugzilla-daemon [this message]
2016-12-21 19:56 ` bugzilla-daemon
2016-12-21 20:23 ` bugzilla-daemon
2016-12-21 20:24 ` bugzilla-daemon
2016-12-22 6:49 ` bugzilla-daemon
2016-12-22 20:35 ` bugzilla-daemon
2016-12-23 9:16 ` bugzilla-daemon
2017-01-05 10:09 ` bugzilla-daemon
2017-01-05 13:14 ` bugzilla-daemon
2017-01-05 13:59 ` bugzilla-daemon
2017-01-05 14:44 ` bugzilla-daemon
2017-01-05 14:53 ` bugzilla-daemon
2017-01-06 6:19 ` bugzilla-daemon
2017-01-06 6:27 ` bugzilla-daemon
2017-01-06 6:28 ` bugzilla-daemon
2017-01-06 6:46 ` bugzilla-daemon
2017-01-06 6:59 ` bugzilla-daemon
2017-01-06 7:06 ` bugzilla-daemon
2017-01-06 7:27 ` bugzilla-daemon
2017-01-06 7:28 ` bugzilla-daemon
2017-01-06 8:00 ` bugzilla-daemon
2017-01-06 12:25 ` bugzilla-daemon
2017-01-08 10:46 ` bugzilla-daemon
2017-01-13 16:45 ` bugzilla-daemon
2017-01-15 16:43 ` bugzilla-daemon
2017-01-17 17:07 ` bugzilla-daemon
2017-01-17 17:08 ` bugzilla-daemon
2017-01-17 17:09 ` bugzilla-daemon
2017-01-18 13:49 ` bugzilla-daemon
2017-01-19 6:54 ` bugzilla-daemon
2017-01-19 6:54 ` bugzilla-daemon
2017-01-19 10:22 ` bugzilla-daemon
2017-01-19 10:31 ` bugzilla-daemon
2017-01-19 11:16 ` bugzilla-daemon
2017-01-20 13:21 ` bugzilla-daemon
2017-01-29 13:35 ` bugzilla-daemon
2017-01-31 0:34 ` bugzilla-daemon
2017-01-31 7:14 ` bugzilla-daemon
2017-01-31 18:31 ` bugzilla-daemon
2017-02-01 6:41 ` bugzilla-daemon
2017-02-01 13:24 ` bugzilla-daemon
2017-02-04 3:11 ` bugzilla-daemon
2017-02-09 6:48 ` bugzilla-daemon
2017-02-09 20:57 ` bugzilla-daemon
2017-02-11 15:24 ` bugzilla-daemon
2017-02-11 22:59 ` bugzilla-daemon
2017-02-18 20:43 ` bugzilla-daemon
2017-02-23 16:28 ` bugzilla-daemon
2017-02-23 16:39 ` bugzilla-daemon
2017-02-24 8:47 ` 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-190831-62941-3vSebHR6lb@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 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.