From: firstname.lastname@example.org To: email@example.com Subject: [Bug 202515] Bluetooth LE Extended Connect returning Command Disallowed Date: Fri, 08 Feb 2019 21:39:29 +0000 Message-ID: <bug-202515-62941-MBcct6Zop8@https.bugzilla.kernel.org/> (raw) In-Reply-To: <firstname.lastname@example.org/> https://bugzilla.kernel.org/show_bug.cgi?id=202515 Mathias Tillman (email@example.com) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #17 from Mathias Tillman (firstname.lastname@example.org) --- To make a long story short, I've managed to figure it out: the latest firmware actually fixes it, but for some reason it's not actually loaded on to the controller until I shut down the computer and leave it off for around 10 seconds or so. A simple reboot isn't enough for it to load the new firmware. I verified this by doing a cold boot with the distro firmware, copying over the new firmware then rebooting several times. None of these times was the LE Set Extended Scan Parameters reported as being supported. I then shut down the computer and turned it on again after roughly 10 seconds, and after that the command was reported. I then copied over the distro firmware, rebooted several times and it was still working. Turned off the computer and on again, and it no longer worked. So aside from that odd firmware loading requiring a cold boot, it seems to be working as expected without a patched kernel. Thanks for the replies everyone, and sorry for all of the long-winded messages. I will be marking this as resolved now. -- You are receiving this mail because: You are the assignee for the bug.
prev 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 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 [this message]
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-MBcct6Zop8@https.bugzilla.kernel.org/ \ --email@example.com \ --firstname.lastname@example.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 \ email@example.com firstname.lastname@example.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