From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
Date: Wed, 21 Dec 2022 11:19:06 +0000 [thread overview]
Message-ID: <bug-216817-62941-tKmyVwD5cr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216817-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #8 from Andrew M (quantumphazor@gmail.com) ---
(In reply to Luiz Von Dentz from comment #7)
> (In reply to Andrew M from comment #6)
> > (In reply to Luiz Von Dentz from comment #5)
> > > Can you try with the following patch
> >
> > Thanks for the quick response. Tried the patch and it has solved the
> problem
> > for me on both 6.1.0 and git.
> > I hope it makes it into 6.1.1
>
> Please test with the latest version:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20221219234945.3733741-
> 1-luiz.dentz@gmail.com/
>
> It turns out the features are not ready if we don't change the command
> sequence so iso_capable would always evaluate to false.
Still works. Tested v6.1 and 6.1.r13872.gb6bb9676f216
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-12-21 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
2022-12-18 4:30 ` [Bug 216817] " bugzilla-daemon
2022-12-19 8:33 ` bugzilla-daemon
2022-12-19 10:55 ` bugzilla-daemon
2022-12-19 21:06 ` bugzilla-daemon
2022-12-19 21:10 ` bugzilla-daemon
2022-12-19 21:13 ` [Bug,216817] " bluez.test.bot
2022-12-20 3:25 ` [Bug 216817] " bugzilla-daemon
2022-12-20 20:25 ` bugzilla-daemon
2022-12-21 11:19 ` bugzilla-daemon [this message]
2023-01-11 19:44 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
2023-01-16 13:29 ` bugzilla-daemon
2023-01-17 19:22 ` bugzilla-daemon
2023-01-26 16:21 ` 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-216817-62941-tKmyVwD5cr@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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