Thread (15 messages) 15 messages, 3 authors, 2012-08-07

Re: [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2012-08-06 22:08:04
Also in: lkml

On Monday, August 06, 2012 02:43:40 PM Greg KH wrote:
On Mon, Aug 06, 2012 at 11:21:43PM +0200, Yann Cantin wrote:
quoted
Signed-off-by: Yann Cantin <redacted>
---

 drivers/hid/hid-core.c |    3 +++
 drivers/hid/hid-ids.h  |    3 +++
 2 files changed, 6 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 60ea284..b1ed8ee 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1908,6 +1908,9 @@ static const struct hid_device_id hid_ignore_list[]
= {> 
 	{ HID_USB_DEVICE(USB_VENDOR_ID_DELORME, USB_DEVICE_ID_DELORME_EM_LT20)
 	},
 	{ HID_USB_DEVICE(USB_VENDOR_ID_DREAM_CHEEKY, 0x0004) },
 	{ HID_USB_DEVICE(USB_VENDOR_ID_DREAM_CHEEKY, 0x000a) },

+#if defined(CONFIG_INPUT_EBEAM_USB)
+	{ HID_USB_DEVICE(USB_VENDOR_ID_EFI, USB_DEVICE_ID_EFI_CLASSIC) },
+#endif
Why is this #if in here?  Just always do it, how could it not be
defined?
User might disable the driver and CONFIG_INPUT_EBEAM_USB will not be
set. But I agree, since the device is unusable with generic HID driver
there is no point in doing this conditionally.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help