public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@web.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] usbhid: add ASUS LCM to the blacklist
Date: Fri, 27 Jul 2007 01:10:00 +0200	[thread overview]
Message-ID: <200707270110.01135.chunkeey@web.de> (raw)
In-Reply-To: <20070726152709.6daa1c96.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Some of ASUS' notebooks (e.g G Series) include a tiny oled display, which is 
attached to an internal USB bus. Unfortunatly the device reports a wrong
DeviceDescriptor and is therefore identified as a HID device...

Signed-off-by: Christian Lamparter <chunkeey@web.de>
CC: linux-input@atrey.karlin.mff.cuni.cz
CC: linux-usb-devel@lists.sourceforge.net

---
Right! the last _two_ patches/resends were made from 2.6.22-*,
this time however, it's diffed from 2.6.23-rc1-git3... 
(I hope it get's merged before someone else has already changed
the line numbers again. ;) )


[-- Attachment #2: asus-lcm-hid-quirk.diff --]
[-- Type: text/x-diff, Size: 840 bytes --]

diff -up drivers/hid/usbhid/hid-quirks.c.orig drivers/hid/usbhid/hid-quirks.c
--- a/drivers/hid/usbhid/hid-quirks.c.orig	2007-07-27 00:23:36.000000000 +0200
+++ b/drivers/hid/usbhid/hid-quirks.c	2007-07-27 00:25:26.000000000 +0200
@@ -63,6 +63,9 @@
 #define USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY	0x030b
 #define USB_DEVICE_ID_APPLE_IR		0x8240
 
+#define USB_VENDOR_ID_ASUS		0x0b05
+#define USB_DEVICE_ID_ASUS_LCM		0x1726
+
 #define USB_VENDOR_ID_ATEN		0x0557
 #define USB_DEVICE_ID_ATEN_UC100KM	0x2004
 #define USB_DEVICE_ID_ATEN_CS124U	0x2202
@@ -464,6 +467,8 @@ static const struct hid_blacklist {
 	{ USB_VENDOR_ID_DELL, USB_DEVICE_ID_DELL_W7658, HID_QUIRK_RESET_LEDS },
 	{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_KBD, HID_QUIRK_RESET_LEDS },
 
+	{ USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_LCM, HID_QUIRK_IGNORE},
+
 	{ 0, 0 }
 };
 

  reply	other threads:[~2007-07-26 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  0:28 [PATCH] usbhid: add ASUS LCM to the blacklist Christian Lamparter
2007-07-26 22:27 ` Andrew Morton
2007-07-26 23:10   ` Christian Lamparter [this message]
2007-07-30 12:45     ` Jiri Kosina
2007-07-30 14:11       ` Chr
2007-07-31  8:39         ` Jiri Kosina
2007-07-31 21:24           ` Cleaning up the USBHID's blacklist Chr
2007-08-01 12:11             ` Jiri Kosina
     [not found] ` <8a1758740710101811q22fc235aifb1edcccd6e98e56@mail.gmail.com>
2007-10-12  8:49   ` [PATCH] usbhid: add ASUS LCM to the blacklist Chr

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=200707270110.01135.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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