From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Erik Håkansson" <erikhakan@gmail.com>
Cc: "Benjamin Tissoires" <bentiss@kernel.org>,
"Jiri Kosina" <jikos@kernel.org>,
"Filipe Laíns" <lains@riseup.net>,
"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 0/2] HID: logitech-hidpp: fix Bolt hi-res wheel handling
Date: Thu, 24 Sep 2026 23:57:05 +0200 [thread overview]
Message-ID: <6UWkRWWaSvGIWNWwY_bPDw@natalenko.name> (raw)
In-Reply-To: <r8QjhQUkS86zOaJsxE4nUw@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
Hello.
On čtvrtek 24. září 2026 23:41:41, středoevropský letní čas Erik Håkansson wrote:
> > Somewhat unrelated note: if I enable "Thumb Wheel Diversion", the thumb
> > wheel stops working altogether. It's probably not supported by the driver
> > at all in HID++ mode?
> >
>
> Correct, the driver does not implement 0x2150 (Thumbwheel) in HID++ at all.
> However, since we're interested in diverting through HID++ for device
> separation purposes, I'm looking into implementing 0x2150 too to enable that
> diversion for that too.
> And while reading the protocol there, I noticed that it also supports touch
> events on the thumbwheel. There's three different statuses, single_tap, proxy,
> and touch. Touch is continuous touch, single_tap is tap, and proxy is whether
> a finger is in close proximity but not quite touching.
> Does your mouse by any chance support that? If so, can you tell if it sends a
> button event on tap or touch when in non-diverted mode? Or possibly if it does
> so in Windows. I don't know what I should map those events to really :)
No idea TBH. The mouse is this one:
https://www.logitech.com/en-us/shop/p/mx-master-4
I haven't seen proximity mentioned anywhere is specs. But I can try to sniff for these events, just let me know how.
Thanks.
--
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-09-24 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:40 Erik Håkansson
2026-09-22 17:40 ` [PATCH 1/2] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master Erik Håkansson
2026-09-22 17:40 ` [PATCH 2/2] HID: logitech-hidpp: fix Bolt wheel mode handling Erik Håkansson
2026-09-23 6:39 ` [PATCH 0/2] HID: logitech-hidpp: fix Bolt hi-res wheel handling Oleksandr Natalenko
2026-09-23 7:54 ` Benjamin Tissoires
2026-09-23 16:09 ` erikhakan
2026-09-24 6:51 ` Oleksandr Natalenko
2026-09-24 21:41 ` Erik Håkansson
2026-09-24 21:48 ` erikhakan
2026-09-24 21:57 ` 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=6UWkRWWaSvGIWNWwY_bPDw@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®