mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: cr7@os.inf.tu-dresden.de
To: linux-kernel@vger.kernel.org
Cc: vojtech@suse.cz
Subject: [PATCH] USB-HID: IOWarrior added to blacklist
Date: Tue, 11 May 2004 17:53:23 +0200	[thread overview]
Message-ID: <200405111753.23786.cr7@os.inf.tu-dresden.de> (raw)

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

Hi all,

this is a simple patch of USB's hid-core.c to add Codemercs' IOWarrior 24 and  
IOWarrior 40 to the blacklist as it's not a "real" HID device.
It should be used via Codemercs' driver or via libusb.

The datasheet for IOwarrior can be found here:
http://www.codemercs.com/Downloads/IOWarriorDatasheet.pdf

Regards,
Carsten



[-- Attachment #2: hid-iowarrior.patch --]
[-- Type: text/x-diff, Size: 816 bytes --]

--- /drivers/usb/input/hid-core.c-orig	2004-04-04 05:37:23.000000000 +0200
+++ /drivers/usb/input/hid-core.c	2004-05-11 13:50:11.877974264 +0200
@@ -1412,6 +1412,11 @@
 #define USB_VENDOR_ID_CHIC		0x05fe
 #define USB_DEVICE_ID_CHIC_GAMEPAD	0x0014
 
+#define USB_VENDOR_ID_CODEMERCS         0x07c0
+#define USB_DEVICE_ID_CODEMERCS_IOW40   0x1500
+#define USB_DEVICE_ID_CODEMERCS_IOW24   0x1501
+
+
 struct hid_blacklist {
 	__u16 idVendor;
 	__u16 idProduct;
@@ -1479,6 +1484,9 @@
 	{ USB_VENDOR_ID_SAITEK, USB_DEVICE_ID_SAITEK_RUMBLEPAD, HID_QUIRK_BADPAD },
 	{ USB_VENDOR_ID_TOPMAX, USB_DEVICE_ID_TOPMAX_COBRAPAD, HID_QUIRK_BADPAD },
 
+	{ USB_VENDOR_ID_CODEMERCS, USB_DEVICE_ID_CODEMERCS_IOW40, HID_QUIRK_IGNORE },
+	{ USB_VENDOR_ID_CODEMERCS, USB_DEVICE_ID_CODEMERCS_IOW24, HID_QUIRK_IGNORE },
+
 	{ 0, 0 }
 };
 

             reply	other threads:[~2004-05-11 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 15:53 cr7 [this message]
2004-06-24 13:45 ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2004-05-11 12:04 cr7

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=200405111753.23786.cr7@os.inf.tu-dresden.de \
    --to=cr7@os.inf.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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

all inboxes | Powered by JetHome®