From: Andrew Morton <akpm@linux-foundation.org>
To: Christian Lamparter <chunkeey@web.de>
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: Thu, 26 Jul 2007 15:27:09 -0700 [thread overview]
Message-ID: <20070726152709.6daa1c96.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707240228.39421.chunkeey@web.de>
On Tue, 24 Jul 2007 02:28:39 +0200 Christian Lamparter <chunkeey@web.de> wrote:
> 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
>
> ---
> (keep the cc!)
> for those who are interested in the userspace display driver:
> https://launchpad.net/asusoled
>
>
>
> [asus-lcm-hid-blacklist.diff text/x-diff (865B)]
> 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-24 02:23:36.000000000 +0200
> +++ b/drivers/hid/usbhid/hid-quirks.c 2007-07-24 02: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
> @@ -452,6 +455,8 @@ static const struct hid_blacklist {
> { USB_VENDOR_ID_CYPRESS, USB_DEVICE_ID_CYPRESS_BARCODE_1, HID_QUIRK_SWAPPED_MIN_MAX },
> { USB_VENDOR_ID_CYPRESS, USB_DEVICE_ID_CYPRESS_BARCODE_2, HID_QUIRK_SWAPPED_MIN_MAX },
>
> + { USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_LCM, HID_QUIRK_IGNORE},
> +
> { 0, 0 }
> };
diff -p said that the second hnk goes into the hid_blacklist[] array, but
your patch actually places it in the hid_rdesc_blacklist[] array.
I suspect what we have here is a diff against 2.6.22? Things changed
a lot since then - please prepare patches against the latest kernel you can get
your hands on, thanks.
next prev parent reply other threads:[~2007-07-26 22:27 UTC|newest]
Thread overview: 11+ 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 [this message]
2007-07-26 23:10 ` Christian Lamparter
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
2007-10-11 1:11 ` [PATCH] usbhid: add ASUS LCM to the blacklist Javier Bolaños Molina
2007-10-12 8:49 ` Chr
2007-10-12 15:59 ` Javier Bolaños Molina
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=20070726152709.6daa1c96.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chunkeey@web.de \
--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;
as well as URLs for NNTP newsgroup(s).