public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Yann Cantin <yann.cantin@laposte.net>, Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [ebeam PATCH v2 1/2] hid: Blacklist eBeam devices
Date: Wed, 10 Oct 2012 09:37:47 -0700	[thread overview]
Message-ID: <20121010163747.GD19335@core.coreip.homeip.net> (raw)
In-Reply-To: <1349529287-23193-2-git-send-email-yann.cantin@laposte.net>

Jiri,

Are you OK with this change?

Yann,

Is the device usable at all with generic HID driver? If it isn't then
maybe we should blacklist it unconditionally?

Thanks.

On Sat, Oct 06, 2012 at 03:14:46PM +0200, Yann Cantin wrote:
> 
> Signed-off-by: Yann Cantin <yann.cantin@laposte.net>
> ---
>  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 bd3971b..59ffaa2 100644
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -1937,6 +1937,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_EBEAM) },
> +#endif
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ESSENTIAL_REALITY, USB_DEVICE_ID_ESSENTIAL_REALITY_P5) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ETT, USB_DEVICE_ID_TC5UH) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ETT, USB_DEVICE_ID_TC4UM) },
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 269b509..df826b8 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -274,6 +274,9 @@
>  #define USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH_72D0      0x72d0
>  #define USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH_72C4      0x72c4
>  
> +#define USB_VENDOR_ID_EFI		0x2650
> +#define USB_DEVICE_ID_EFI_EBEAM		0x1311
> +
>  #define USB_VENDOR_ID_ELECOM		0x056e
>  #define USB_DEVICE_ID_ELECOM_BM084	0x0061
>  
> -- 
> 1.7.10
> 

-- 
Dmitry

  reply	other threads:[~2012-10-10 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 13:14 [ebeam PATCH v2 0/2] new eBeam input driver Yann Cantin
2012-10-06 13:14 ` [ebeam PATCH v2 1/2] hid: Blacklist eBeam devices Yann Cantin
2012-10-10 16:37   ` Dmitry Torokhov [this message]
2012-10-10 22:01     ` Yann Cantin
2012-10-16 13:59     ` Jiri Kosina
2012-10-06 13:14 ` [ebeam PATCH v2 2/2] input: misc: New USB eBeam input driver Yann Cantin
2012-12-13  7:07 ` ebeam PATCH (new eBeam input driver) Yann Cantin
  -- strict thread matches above, loose matches on Subject: below --
2015-08-22 22:06 [ebeam PATCH v2 0/2] Add a new USB eBeam input driver Yann Cantin
2015-08-22 22:06 ` [ebeam PATCH v2 1/2] hid: Blacklist eBeam devices Yann Cantin

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=20121010163747.GD19335@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=yann.cantin@laposte.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