From: erikhakan@gmail.com
To: Oleksandr Natalenko <oleksandr@natalenko.name>,
linux-input@vger.kernel.org, lains@riseup.net, hadess@hadess.net,
jikos@kernel.org, bentiss@kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Brigham Campbell <me@brighamcampbell.com>,
Jori Koolstra <jkoolstra@xs4all.nl>,
Rafael Passos <rafael@rcpassos.me>,
greyxor@protonmail.com, roman.stingler@gmail.com,
lovekeshsolanki00@gmail.com, k8ie@mcld.eu
Subject: Re: [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master
Date: Tue, 22 Sep 2026 17:28:47 +0200 [thread overview]
Message-ID: <1db23bb2-f94a-4bd7-b9b6-5175aca68ff1@gmail.com> (raw)
In-Reply-To: <LYMlyJcyQt29e1KlLnEoLw@natalenko.name>
Hi all!
I believe I have an explanation (and a solution) for why everyone's results differ.
As noted in https://lore.kernel.org/linux-input/20260920094508.39682-1-roman.stingler@gmail.com/
there is a conflict between the driver and Solaar in that user settings are not
respected by the driver.
So while investigating that, I found some further issues with regards to how Rafael's
proposed fix would deal with the case where Solaar disables high resolution scroll.
Locally, I have a fix that expands on Rafael's patch and but also handles low-
resolution scroll events. And it also respects on-device user settings so that
settings set in Solaar will remain.
I believe that the reason for inconsistent behaviour for some testers is simply
that there are unhandled states in combinations of settings in the current code,
which my fix aims to solve.
So, Rafael, is it alright if I post a new series with your fix as Patch 1 and then
my addition as Patch 2?
I'd love to have it properly tested since I don't have a Bolt mouse.
Regards,
Erik
next prev parent reply other threads:[~2026-09-22 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 3:48 [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master Rafael Passos
2026-09-04 4:02 ` sashiko-bot
2026-09-04 7:44 ` Alexey Zagorodnikov
2026-09-04 16:34 ` Erik Håkansson
2026-09-04 17:03 ` Benjamin Tissoires
2026-09-04 18:20 ` Alexey Zagorodnikov
2026-09-04 18:17 ` Alexey Zagorodnikov
2026-09-04 20:21 ` Rafael Passos
2026-09-07 17:46 ` erikhakan
2026-09-14 10:31 ` Oleksandr Natalenko
2026-09-14 10:51 ` Oleksandr Natalenko
2026-09-22 15:28 ` erikhakan [this message]
2026-09-22 16:28 ` Rafael Passos
2026-09-22 16:32 ` Rafael Passos
2026-09-22 20:33 ` Oleksandr Natalenko
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=1db23bb2-f94a-4bd7-b9b6-5175aca68ff1@gmail.com \
--to=erikhakan@gmail.com \
--cc=bentiss@kernel.org \
--cc=greyxor@protonmail.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=k8ie@mcld.eu \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=lovekeshsolanki00@gmail.com \
--cc=me@brighamcampbell.com \
--cc=oleksandr@natalenko.name \
--cc=rafael@rcpassos.me \
--cc=roman.stingler@gmail.com \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.