From: "Erik Håkansson" <erikhakan@gmail.com>
To: k8ie@mcld.eu
Cc: jikos@kernel.org, bentiss@kernel.org, lains@riseup.net,
hadess@hadess.net, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] HID: logitech: add Bolt receiver support for Logitech HID++ devices
Date: Mon, 13 Jul 2026 22:10:26 +0200 [thread overview]
Message-ID: <20260713201026.391186-1-erikhakan@gmail.com> (raw)
In-Reply-To: <345f7347-30a8-4568-a7a6-c70f54a52a8d@mcld.eu>
Hi,
Thank you for testing this.
I could not reproduce issue 1 locally with my MX Keys for Business, but
I applied your fix since it also works on my hardware. Either the
different keyboard models behave differently, or something differs
between our setups. I folded it into the existing interface handling to
keep the code smaller.
I also noticed that my older Lightspeed receiver exposes interfaces 0
and 1 as boot keyboard and mouse interfaces too, while only interfaces
>= 3 are treated as generic HID. So Bolt appears to need different
interface handling from the existing Lightspeed receiver path.
Issue 2 was easy to reproduce, and I applied your fix more or less
verbatim.
I will send a v2 patch shortly. I would be very grateful if you could
test it again.
Regards,
Erik
next prev parent reply other threads:[~2026-07-13 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 0:30 [PATCH 0/1] HID: logitech: add Bolt receiver support for Logitech HID++ devices Erik Håkansson
2026-07-12 0:30 ` [PATCH 1/1] " Erik Håkansson
2026-07-12 18:03 ` Kateřina Medvědová
2026-07-13 20:10 ` Erik Håkansson [this message]
2026-07-13 20:12 ` [PATCH v2 0/1] " Erik Håkansson
2026-07-13 20:12 ` [PATCH v2 1/1] " Erik Håkansson
2026-07-13 20:24 ` sashiko-bot
2026-07-13 21:09 ` Kateřina Medvědová
2026-07-14 0:54 ` Erik Håkansson
2026-07-14 10:32 ` Kateřina Medvědová
2026-07-14 15:33 ` Erik Håkansson
2026-07-14 0:50 ` Erik Håkansson
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=20260713201026.391186-1-erikhakan@gmail.com \
--to=erikhakan@gmail.com \
--cc=bentiss@kernel.org \
--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 \
/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.