From: Christoph Fritz <chf.fritz@googlemail.com>
To: "Adi J. Sieker" <adi@sieker.io>
Cc: Jiri Kosina <jkosina@suse.cz>,
Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oliver@neukum.org>,
USB list <linux-usb@vger.kernel.org>,
linux-input@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: USB keyboard recognized as HID keyboard but doesn't work
Date: Sun, 08 May 2011 00:24:53 +0200 [thread overview]
Message-ID: <1304807093.5891.45.camel@mars> (raw)
In-Reply-To: <4DC3FEC7.6050503@sieker.io>
On Fri, 2011-05-06 at 15:59 +0200, Adi J. Sieker wrote:
> On 06/05/11 14:58, Jiri Kosina wrote:
> > On Tue, 3 May 2011, Alan Stern wrote:
> >
> >>> Do you know of a way for me to tell the kernel/usbhid to use interface 1
> >>> and ignore interface 0?
> >>
> >> Well, you can always unbind interface 0 from usbhid -- it corresponds
> >> to the 2-1.1:1.0 file in /sys/bus/usb/drivers/usbhid/. If you do that,
> >> you'll probably find the few keys which _do_ currently work suddenly
> >> stop working.
> >>
> >> But there's nothing to be done immediately about interface 1; usbhid is
> >> _already_ using it. It just isn't using it correctly.
> >
> > Adi,
> >
> > could you please provide output of
> >
> > cat /syse/kernel/debug/hid/<keyboard>/rdesc
> >
> > anytime after the keyboard has been plugged, and
>
> in /sys/kernel/debug/hid I have two devices for the keyboard. One is
> 0003:060B:0230.0002 and the other 0003:060B:0230.0003
>
> attached are the rdesc files for both devices.
>
> >
> > cat /syse/kernel/debug/hid/<keyboard>/events
> > from the time you press any of the working and non-working keys? (both
> > cases will be interesting).
>
> I only get events for the working keys on the *:0002 device.
> All other files were empty after I pressed some keys.
>
> The events for the working keys are attached in the *.events file.
> I first pressed backspace and then the menu key.
Hi Adi,
I'm not sure about my patch below because of interface one, maybe you
can give it a try.
Thanks,
-- chf
---
Subject: [PATCH] HID: add quirk for Solid Year keyboard ACK231
This patch adds HID_QUIRK_MULTI_INPUT to Solid Year keyboard ACK231
which reports keystrokes from inside a firmware-configuration
interface instead of using its own interface.
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 00a94b5..abbace9 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -528,6 +528,9 @@
#define USB_VENDOR_ID_SKYCABLE 0x1223
#define USB_DEVICE_ID_SKYCABLE_WIRELESS_PRESENTER 0x3F07
+#define USB_VENDOR_ID_SOLIDYEAR 0x060b
+#define USB_DEVICE_ID_SOLIDYEAR_KEYBOARD_ACK231 0x0230
+
#define USB_VENDOR_ID_SONY 0x054c
#define USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE 0x024b
#define USB_DEVICE_ID_SONY_PS3_CONTROLLER 0x0268
diff --git a/drivers/hid/usbhid/hid-quirks.c b/drivers/hid/usbhid/hid-quirks.c
index a8426f1..b099380 100644
--- a/drivers/hid/usbhid/hid-quirks.c
+++ b/drivers/hid/usbhid/hid-quirks.c
@@ -49,6 +49,7 @@
{ USB_VENDOR_ID_ETURBOTOUCH, USB_DEVICE_ID_ETURBOTOUCH, HID_QUIRK_MULTI_INPUT },
{ USB_VENDOR_ID_PANTHERLORD, USB_DEVICE_ID_PANTHERLORD_TWIN_USB_JOYSTICK, HID_QUIRK_MULTI_INPUT | HID_QUIRK_SKIP_OUTPUT_REPORTS },
{ USB_VENDOR_ID_PLAYDOTCOM, USB_DEVICE_ID_PLAYDOTCOM_EMS_USBII, HID_QUIRK_MULTI_INPUT },
+ { USB_VENDOR_ID_SOLIDYEAR, USB_DEVICE_ID_SOLIDYEAR_KEYBOARD_ACK231, HID_QUIRK_MULTI_INPUT },
{ USB_VENDOR_ID_TOUCHPACK, USB_DEVICE_ID_TOUCHPACK_RTS, HID_QUIRK_MULTI_INPUT },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_UC100KM, HID_QUIRK_NOGET },
next prev parent reply other threads:[~2011-05-07 22:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DBF16D8.8040209@sieker.io>
2011-05-02 21:06 ` USB keyboard recognized as HID keyboard but doesn't work Alan Stern
2011-05-02 21:19 ` Adi J. Sieker
2011-05-02 22:29 ` Alan Stern
2011-05-03 9:40 ` Adi J. Sieker
2011-05-03 13:49 ` Alan Stern
2011-05-06 12:58 ` Jiri Kosina
2011-05-06 13:59 ` Adi J. Sieker
2011-05-07 22:24 ` Christoph Fritz [this message]
2011-05-08 19:51 ` Adi J. Sieker
[not found] ` <4DC6F44E.1000703-D1akFU9K7Sphl2p70BpVqQ@public.gmane.org>
2011-05-08 21:26 ` Christoph Fritz
2011-05-10 8:24 ` Adi J. Sieker
2011-04-30 20:23 Adi J. Sieker
[not found] ` <4DBC6FA9.3080008-D1akFU9K7Sphl2p70BpVqQ@public.gmane.org>
2011-05-01 7:53 ` Oliver Neukum
2011-05-01 17:49 ` Adi J. Sieker
[not found] ` <4DBD9D0D.1080503-D1akFU9K7Sphl2p70BpVqQ@public.gmane.org>
2011-05-02 14:04 ` Alan Stern
2011-05-02 19:35 ` Adi J. Sieker
2011-05-02 20:27 ` Alan Stern
2011-05-02 20:49 ` Adi J. Sieker
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=1304807093.5891.45.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=adi@sieker.io \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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).