All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Zagorodnikov <xglooom@gmail.com>
To: "Benjamin Tissoires" <bentiss@kernel.org>,
	"Erik Håkansson" <erikhakan@gmail.com>
Cc: Rafael Passos <rafael@rcpassos.me>,
	lains@riseup.net, hadess@hadess.net, jikos@kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Brigham Campbell <me@brighamcampbell.com>,
	Jori Koolstra <jkoolstra@xs4all.nl>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master
Date: Fri, 4 Sep 2026 23:20:36 +0500	[thread overview]
Message-ID: <8b4a0709-823d-44cb-a6b0-14a12392ef0c@gmail.com> (raw)
In-Reply-To: <apr493wpBH50vXNi@beelink>

 >we just revert the inclusion of the receiver in the dj driver.

Please no, we finally able to achieve hi-res scrolling, like it was on 
unifying and bluetooth connections.

Maybe place it behind some quirk flags if causes more trouble on other 
setup.

On 9/4/26 22:03, Benjamin Tissoires wrote:
> On Sep 04 2026, Erik Håkansson wrote:
>> Hi!
>> Is this the same issue as in
>> https://lore.kernel.org/linux-input/20260901-bolt-scroll-fix-v1-1-58bca7ae487f@protonmail.com/
>> The symptoms seem similar at least, and if so the approach to fixing
>> it in that case is to simply treat Bolt devices like previous DJ
>> devices, rather than having special treatment for Bolt.
>> Can you who have Bolt mice maybe test that patch too to see if it
>> solves the same issue?
> FWIW, my initial decision a few years back when Bolt was introduced was
> to not include it in the kernel, because there are too many things it's
> missing, the most problematic one being that we don't know which device
> sends which event.
>
> So basically, there is a chance that the driver sets high-resolution
> scrolling on a bolt device, when 2 mice are connected, and one is
> capable of it and the other is not. This is unlikely to happen, but is
> hard to solve in the kernel.
>
> So I'm happy to wait for testing and patches, but I would also like a
> conclusion where bolt doesn't belong to the kernel, and we just revert
> the inclusion of the receiver in the dj driver.
>
> Cheers,
> Benjamin

  reply	other threads:[~2026-09-04 18:20 UTC|newest]

Thread overview: 9+ 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 [this message]
2026-09-04 18:17     ` Alexey Zagorodnikov
2026-09-04 20:21       ` Rafael Passos
2026-09-07 17:46         ` erikhakan

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=8b4a0709-823d-44cb-a6b0-14a12392ef0c@gmail.com \
    --to=xglooom@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=erikhakan@gmail.com \
    --cc=hadess@hadess.net \
    --cc=jikos@kernel.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=rafael@rcpassos.me \
    --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.