From: Yann Cantin <yann.cantin@laposte.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
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: Thu, 11 Oct 2012 00:01:13 +0200 [thread overview]
Message-ID: <5075F029.90807@laposte.net> (raw)
In-Reply-To: <20121010163747.GD19335@core.coreip.homeip.net>
Hi,
Le 10/10/2012 18:37, Dmitry Torokhov a écrit :
> Is the device usable at all with generic HID driver? If it isn't then
> maybe we should blacklist it unconditionally?
Without the libusb based proprietary stack, the device is unusable under linux.
If i correctly understand, libusb need a driver to be present in the first place,
(even a useless generic-usb) to be able to grab the device. If we unconditionally
blacklist the device and the ebeam driver isn't loaded (not compiled for example), no way
for libusb (and the stack) to handle the device.
As stated before, i'm not comfortable with the risk of breaking other hypothetical support,
even proprietary.
--
Yann Cantin
A4FEB47F
--
next prev parent reply other threads:[~2012-10-10 21:56 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
2012-10-10 22:01 ` Yann Cantin [this message]
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=5075F029.90807@laposte.net \
--to=yann.cantin@laposte.net \
--cc=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 \
/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