From: RH <r@hirner.at>
To: linux-input@vger.kernel.org
Subject: Re: [PATCH] Handle spurious backslash key repeats on some keyboards
Date: Fri, 19 Dec 2014 16:28:50 +0000 (UTC) [thread overview]
Message-ID: <m71jo1$i0n$1@ger.gmane.org> (raw)
In-Reply-To: CAMsZVf-2_eFKoqgO1+bEB4ziA1e9-z4rYviy_r9ksjmAUAe5Sg@mail.gmail.com
Hello,
I experience the same issue with my new keyboard:
*Corsair Raptor K30 (German version)*
The issue can be fixed/worked around with this rule in hwdb:
---------------
#keyboard:name:*Corsair*:dmi:bvn*:bvr*:bd*:svn*:pn*:pvr*
keyboard:usb:v1B1Cp1B0A*
KEYBOARD_KEY_70031=reserved
---------------
So you think the US version won't work with this anymore? I guess they
will send both scancodes, too.
This is the output of lsusb:
---------------
Bus 004 Device 008: ID 1b1c:1b0a Corsair
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1b1c Corsair
idProduct 0x1b0a
bcdDevice 1.03
iManufacturer 1 Corsair
iProduct 2 Corsair K30A Gaming Keyboard
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 25
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 37
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000f 1x 15 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)
---------------
Did you already find someone with a US keyboard? Shall I write in the
corsair forums or to the support to find out whether US keyboards have
the same product IDs? If this is not the case, we could safely use vendor/
product IDs for the workaround.
I'd really like to submit working hwdb lines to the udev database to save
other users from having these troubles.
Also, do you know why
Greetings,
RH
next prev parent reply other threads:[~2014-12-19 16:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 9:56 [PATCH] Handle spurious backslash key repeats on some keyboards Fredrik Hallenberg
2014-09-09 9:40 ` Fredrik Hallenberg
2014-09-09 9:42 ` Jiri Kosina
2014-09-09 10:37 ` Fredrik Hallenberg
2014-09-10 8:26 ` Jiri Kosina
2014-09-10 10:09 ` David Herrmann
2014-09-10 11:13 ` Fredrik Hallenberg
2014-09-10 14:22 ` David Herrmann
2014-09-10 22:51 ` Dmitry Torokhov
2014-09-11 8:50 ` Fredrik Hallenberg
2014-09-11 12:41 ` David Herrmann
2014-09-11 20:35 ` Fredrik Hallenberg
2014-09-12 10:29 ` David Herrmann
2014-09-12 11:34 ` Fredrik Hallenberg
2014-09-12 11:47 ` David Herrmann
2014-09-12 17:36 ` Fredrik Hallenberg
2014-12-19 16:28 ` RH [this message]
2014-12-20 19:56 ` Fredrik Hallenberg
2014-09-14 16:45 ` David Herrmann
2014-09-14 17:03 ` David Herrmann
2014-09-14 22:53 ` Fredrik Hallenberg
2014-09-15 8:29 ` Fredrik Hallenberg
2014-09-15 14:39 ` Benjamin Tissoires
2014-09-15 14:47 ` Benjamin Tissoires
2014-09-15 14:52 ` David Herrmann
2014-09-15 15:14 ` Benjamin Tissoires
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='m71jo1$i0n$1@ger.gmane.org' \
--to=r@hirner.at \
--cc=linux-input@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).