From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: linux5.15: add patch to fix bluetooth dongle
Date: Thu, 09 Dec 2021 13:39:15 +0100 [thread overview]
Message-ID: <20211209123915.u-GBwqGhnRg0sFGoj8BiRc27V7346vKsPzKVmAmHlV0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34359@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
There's a merged pull request on the void-packages repository
linux5.15: add patch to fix bluetooth dongle
https://github.com/void-linux/void-packages/pull/34359
Description:
The patch is taken verbatim from this particular comment:
https://gist.github.com/nevack/6b36b82d715dc025163d9e9124840a07#gistcomment-3818325
Note that there are several fake variants of this CSR dongle
(usb id 0a12:0001) that need different workarounds. The gist itself
mentions a workaround (force-suspend) that is already included in 5.15
and fixes some dongles but not mine.
The issue is also mentioned in kernel bugzilla at
https://bugzilla.kernel.org/show_bug.cgi?id=60824#c187
Starting at comment 187 there are several reports of dongles fixed by
that patch (or a variation / rediscovery of the workaround).
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES** (I'm running 5.15.6 built with this PR on my main desktop)
NOTE: I didn't revbump since I don't think it's worth pushing an update for everybody and I already have my own package. It's enough if it gets picked up by the next minor version update.
Edit: make links clickable
prev parent reply other threads:[~2021-12-09 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 3:01 [PR PATCH] " tornaria
2021-12-09 12:39 ` leahneukirchen [this message]
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=20211209123915.u-GBwqGhnRg0sFGoj8BiRc27V7346vKsPzKVmAmHlV0@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).