From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Yann Cantin <yann.cantin@laposte.net>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC ebeam PATCH 3/3] input: misc: New USB eBeam input driver.
Date: Sun, 29 Jul 2012 22:56:23 -0700 [thread overview]
Message-ID: <20120730055623.GD5830@core.coreip.homeip.net> (raw)
In-Reply-To: <5013AA95.7090006@laposte.net>
On Sat, Jul 28, 2012 at 11:02:13AM +0200, Yann Cantin wrote:
> Hi Dmitry,
>
> >> +config INPUT_EBEAM_USB_CLASSIC
> >> + bool "eBeam Classic Projection support"
> >> + depends on INPUT_EBEAM_USB
> >> + default y
> >
> > Will there be support for other eBean devices (are there any)? If there
> > will how soon? How different are they? If not the we probably do not
> > need this INPUT_EBEAM_USB_CLASSIC selector.
>
> I know at least one re-branded same hardware by 3M, i will be able to borrow
> one in a month or so. According to the wikipedia article, there's probably more.
>
> There's also newer models and embeded ones in some video projector setup, also
> re-branded, based on the same technology and that might use the same type of
> protocol, but i can't be sure until someone can inspect them.
> These pieces of hardware are quite expensive, and mostly used in educational
> or corporate, they are not easy to grab.
>
> The code structure (device selector + functions indirection) also seems overkill
> to me for now, but permit to anticipate device's variations. If it appears that they
> all works in the same way, it'll be easy (and more comfortable to me) to step down,
> the opposite seems more difficult.
Actually I am hesitant to add infrastructure if it is unclear if we need
it at all.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-07-30 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 0:02 [RFC ebeam PATCH 0/3] new USB eBeam input driver Yann Cantin
2012-07-28 0:02 ` [RFC ebeam PATCH 1/3] hid: hid-ids.h: Add vendor and device ID for eBeam classic device Yann Cantin
2012-07-28 0:02 ` [RFC ebeam PATCH 2/3] hid: hid-core.c: Blackist " Yann Cantin
2012-07-28 0:02 ` [RFC ebeam PATCH 3/3] input: misc: New USB eBeam input driver Yann Cantin
2012-07-28 1:42 ` Dmitry Torokhov
2012-07-28 9:02 ` Yann Cantin
2012-07-30 5:56 ` Dmitry Torokhov [this message]
2012-07-30 14:25 ` 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=20120730055623.GD5830@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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