From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218495] New: NKRO does not work on Mistel MD770 (Holtek Semiconductor, Inc. USB-HID Keyboard)
Date: Wed, 14 Feb 2024 17:33:47 +0000 [thread overview]
Message-ID: <bug-218495-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218495
Bug ID: 218495
Summary: NKRO does not work on Mistel MD770 (Holtek
Semiconductor, Inc. USB-HID Keyboard)
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: ishitatsuyuki@gmail.com
Regression: No
Created attachment 305872
--> https://bugzilla.kernel.org/attachment.cgi?id=305872&action=edit
BPF program to fix the quirk
My Mistel MD770 (04d9:0339 Holtek Semiconductor, Inc. USB-HID Keyboard) seems
to have a descriptor quirk that prevents NKRO from working. A device
descriptor, a hid capture of NKRO sequence and proposed BPF program for fix is
attached.
It's the exact same error as the Topre quirk [1], but the descriptor and offset
is different.
NKRO works on Windows without extra vendor drivers. I'm not sure if Microsoft
just has a better quirk database, or they have some clever heuristics to detect
this. Before copy pasting the Topre code and calling it a patch, I would like
to ask about what's the best way to fix this.
[1]: https://gitlab.freedesktop.org/libinput/libinput/-/issues/804
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-02-14 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 17:33 bugzilla-daemon [this message]
2024-02-14 17:34 ` [Bug 218495] NKRO does not work on Mistel MD770 (Holtek Semiconductor, Inc. USB-HID Keyboard) bugzilla-daemon
2024-02-14 17:34 ` bugzilla-daemon
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=bug-218495-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).