From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209499] NKRO does not work on vortex race 3 keyboard
Date: Sun, 04 Oct 2020 20:47:13 +0000 [thread overview]
Message-ID: <bug-209499-208809-01YvMg8MZL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209499-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209499
R0b0t1 (sid@aeam.us) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sid@aeam.us
--- Comment #1 from R0b0t1 (sid@aeam.us) ---
I understand your confusion but this is expected. The standard report format
for a USB keyboard is 8 bytes. The first byte contains the modifier key state,
the second is padding, and the remaining 6 bytes contain key codes.
N-key rollover is more a statement of how the switch matrix has been
constructed than how many keys you can use in your OS. There are other ways of
constructing a switch matrix that are marginally cheaper but lead to the
inability to distinguish keys after a certain point; for a typical 84-120 key
keyboard the optimal constructions tend to cap out at 6 simultaneous key
presses, explaining the choices made in the USB standard.
Looking at the lsusb -v output the device shows up as a boot keyboard (slightly
more restricted) and a normal keyboard, but both report the expected number of
bytes. Your keyboard has more interface information than usual but I am not
sure how it is interpreted. It could be sending more bytes back to Windows and
Windows may accept them. You may wish to investigate the keyboard from Windows
using the USBView tool.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-04 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 18:09 [Bug 209499] New: NKRO does not work on vortex race 3 keyboard bugzilla-daemon
2020-10-04 20:47 ` bugzilla-daemon [this message]
2020-10-04 21:44 ` [Bug 209499] " 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-209499-208809-01YvMg8MZL@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).