From: Yann Cantin <yann.cantin@laposte.net>
To: linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Cc: gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
linux-kernel@vger.kernel.org
Subject: [RFC ebeam PATCH v3 0/2]
Date: Mon, 6 Aug 2012 23:21:42 +0200 [thread overview]
Message-ID: <1344288104-20731-1-git-send-email-yann.cantin@laposte.net> (raw)
Hi,
New USB input driver for eBeam devices.
Currently, only the Luidia eBeam classic projection model is supported.
Edge model and a NEC interactive video-projector support planned for the
end of the mounth.
Patch 1 to blacklist the device for hid generic-usb.
Patch 2 is the actual driver.
Changes from previous :
- switch to div64_s64 for portable 64/64-bits divisions
- some cosmetics in device name
- unused include and def removed
- variables name changes for readability
Pending issues :
- sysfs custom files : need to pass 13 parameters for calibration :
choice is between lots of simply-handled, or few with a big sscanf.
- is div64_s64 safe and available on all plateform ? this is the only
use of this function i've found in all the kernel tree.
The module run fine with a 3.3.6 and a 3.5.0 kernel, both x86_32 and 64.
Thanks for your help.
next reply other threads:[~2012-08-06 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 21:21 Yann Cantin [this message]
2012-08-06 21:21 ` [RFC ebeam PATCH v3 1/2] hid: Blacklist new eBeam classic device Yann Cantin
2012-08-06 21:43 ` Greg KH
2012-08-06 22:07 ` Dmitry Torokhov
2012-08-07 1:21 ` Yann Cantin
2012-08-07 1:45 ` Dmitry Torokhov
2012-08-07 8:10 ` Yann Cantin
2012-08-06 21:21 ` [RFC ebeam PATCH v3 2/2] input: misc: New USB eBeam input driver Yann Cantin
2012-08-06 21:43 ` Greg KH
2012-08-07 0:56 ` Yann Cantin
2012-08-07 1:43 ` Dmitry Torokhov
2012-08-07 7:59 ` Yann Cantin
2012-08-06 21:44 ` [RFC ebeam PATCH v3 0/2] Greg KH
2012-08-06 22:09 ` Dmitry Torokhov
2012-08-07 1:45 ` 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=1344288104-20731-1-git-send-email-yann.cantin@laposte.net \
--to=yann.cantin@laposte.net \
--cc=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 \
/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;
as well as URLs for NNTP newsgroup(s).