From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Erik Håkansson" <erikhakan@gmail.com>
Cc: "Filipe Laíns" <lains@riseup.net>,
"Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Bastien Nocera" <hadess@hadess.net>,
"Rafael Passos" <rafael@rcpassos.me>,
"Grégoire Stein" <greyxor@protonmail.com>,
"Alexey Zagorodnikov" <xglooom@gmail.com>,
"Roman Stingler" <roman.stingler@gmail.com>,
"Lovekesh Solanki" <lovekeshsolanki00@gmail.com>,
"Kateřina Medvědová" <k8ie@mcld.eu>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/4] HID: logitech: add Bolt support with HID++ input handling
Date: Fri, 13 Nov 2026 13:08:15 +0100 [thread overview]
Message-ID: <c1eFIG4pSqG6mUjzIm5Xvg@natalenko.name> (raw)
In-Reply-To: <20261002-bolt-input-rfc-v1-0-333e1f350586@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
Hello.
On pátek 2. října 2026 0:23:34, středoevropský standardní čas Erik Håkansson wrote:
> The following items need to be tested:
> 1. First and foremost, the 16-bit descriptor finding was based on looking
> at the native descriptor from the Bolt receiver and not something I
> could test myself without a Bolt mouse.
> Hence, just regular mouse movement needs to be verified with a few
> different devices.
I'm using MX Master 4 mouse. So far, the cursor moves as expected.
> 2. Further, scrolling with a 0x2121-supporting device (i.e. high-resolution
> scrolling) needs to be tested with Solaar set to all four combinations
> of HID++ diversion + resolution, and all four combinations of HID++
> diversion + scroll direction inversion.
As far as I can tell, things do not break if I play with these switches, the high-res scrolling is working for me.
> 3. MX Master 4 thumbwheel (0x2150, or any other mouse with this), diversion
> on and off in Solaar.
Yeah, diversion enables high-res horisontal scrolling, I suppose? If I enable it, the scrolling is smoother.
> 4. M650 Back/Forward clicks when connected over Bolt.
Can speak for MX Master 4, these clicks work.
> 5. Ratchet wheel (0x2130, I think Signature M650 and M750 support this,
> from issue reports online) with diversion on and off in Solaar.
Enabling/disabling magnetic mechanism for the ratchet wheel on MX Master 4 works.
> 6. For all devices, testing so everything works after turning off and on,
> after reconnecting, after reboot, after switching to Bluetooth and back.
So far so good, but I'm going to give it more time to see how it behaves in daily usage.
> 7. There was previously one report of scrambled keyboard input for a Logi
> POP Icon Keys when letting the keyboard interface be claimed by the DJ
> driver. This issue was never traced to a root cause and may have been
> unrelated. It has not been replicated on MX Keys. It should be retested.
On my MX Keys S so far no difference, things just work.
Please let me know if I should test something specific.
Thank you.
--
Oleksandr Natalenko, MSE
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-11-13 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 22:23 Erik Håkansson
2026-10-01 22:23 ` [PATCH RFC 1/4] HID: logitech: add Bolt receiver support Erik Håkansson
2026-10-01 22:23 ` [PATCH RFC 2/4] HID: logitech: handle HID++ thumbwheel reports Erik Håkansson
2026-10-01 22:23 ` [PATCH RFC 3/4] HID: logitech: divert M650 side buttons over Bolt Erik Håkansson
2026-10-01 22:23 ` [PATCH RFC 4/4] HID: logitech-hidpp: support ratchet wheel Erik Håkansson
2026-11-13 12:08 ` Oleksandr Natalenko [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=c1eFIG4pSqG6mUjzIm5Xvg@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=bentiss@kernel.org \
--cc=erikhakan@gmail.com \
--cc=greyxor@protonmail.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=k8ie@mcld.eu \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lovekeshsolanki00@gmail.com \
--cc=rafael@rcpassos.me \
--cc=roman.stingler@gmail.com \
--cc=xglooom@gmail.com \
/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
all inboxes | Powered by JetHome®