From: Swyter <swyterzone@gmail.com>
To: Mika Laitio <lamikr@pilppa.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Jack <ostroffjh@users.sourceforge.net>,
linux-bluetooth@vger.kernel.org,
Paul Menzel <pmenzel@molgen.mpg.de>,
Marcel Holtmann <marcel@holtmann.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle
Date: Tue, 15 Nov 2022 07:41:41 +0100 [thread overview]
Message-ID: <c8987bdd-8a8d-1491-c4c7-66e95f990148@gmail.com> (raw)
In-Reply-To: <e382d911-90bc-de3f-9f3-6143ed8a9b75@pilppa.org>
>> Thanks to this last-effort parameter we can cover that last mile
>> without people having to recompile custom versions of btusb.
>>
>> My dongle doesn't work? Easy, add this here. Most people won't
>> have to bother with this, but that final ~3% would be screwed.
>
> So what is the parameter needed for now? Might help users coming to this
> bug and finding this thread.
Hans explained it better than me.
The Linux people haven't merged this patch yet, but the idea is that in
case our generic workaround is a bit too much for a small bunch of dissident
devices and we are actually making it not work (we're making it worse!) when
it would work otherwise, adding «btusb.disable_fake_csr_forcesuspend_hack=1»
should neutralize any side effects, as that workaround wasn't needed
for your dongle in the first place. But we can't be sure of that.
I think we have received two or three reports of this actually helping.
It should be a thing you'd try and see what happens, this isn't an exact
science. Most people won't need it, we're just being thorough and nice.
Letting you skip our little shakeup. Easily.
next prev parent reply other threads:[~2022-11-15 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 21:11 [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0 Jack
2022-10-25 7:02 ` Paul Menzel
2022-10-25 18:00 ` Jack
2022-10-25 19:38 ` Luiz Augusto von Dentz
2022-10-26 3:41 ` quic_zijuhu
2022-10-27 9:48 ` quic_zijuhu
2022-11-09 19:12 ` [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle Swyter
2022-11-09 19:40 ` Jack
2022-11-09 20:43 ` Luiz Augusto von Dentz
2022-11-09 21:14 ` Swyter
2022-11-15 6:20 ` Mika Laitio
2022-11-15 6:41 ` Swyter [this message]
2022-10-26 9:17 ` [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0 #forregzbot Thorsten Leemhuis
2022-12-01 14:41 ` Thorsten Leemhuis
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=c8987bdd-8a8d-1491-c4c7-66e95f990148@gmail.com \
--to=swyterzone@gmail.com \
--cc=hdegoede@redhat.com \
--cc=lamikr@pilppa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=ostroffjh@users.sourceforge.net \
--cc=pmenzel@molgen.mpg.de \
/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).