From: Roderick Colenbrander <thunderbird2k@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: Handling of non-positional data through evdev
Date: Wed, 16 Mar 2016 11:39:35 -0700 [thread overview]
Message-ID: <CAEc3jaAUmhzVwCMWWwWADCwz22Q8sFQP5qN5H8+Gb2Exf3GRcQ@mail.gmail.com> (raw)
In-Reply-To: <1458141032.29084.0.camel@hadess.net>
On Wed, Mar 16, 2016 at 8:10 AM, Bastien Nocera <hadess@hadess.net> wrote:
> On Tue, 2016-03-15 at 17:17 -0700, Roderick Colenbrander wrote:
>> Hi Bastien,
>>
>> Thanks for providing this suggestion. I can see this approach work
>> for
>> situations like screen rotation on tablets. The device I'm involved
>> with is an input device, which needs a high poll rate for
>> acceleration
>> / velocity and needs to be paired with the button / axes data. Evdev
>> would be most appropriate.
>
> So more like a Wiimote than a builtin sensor. What will consume events
> in user-space? A specialised application?
Correct see it more like a wiimote-like device. I expect many
userspace applications (desktop or embedded) to ultimately support
this device and many existing applications could already use the
device except they can't utilize the motion sensors.
prev parent reply other threads:[~2016-03-16 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 19:26 Handling of non-positional data through evdev Roderick Colenbrander
2016-03-15 20:07 ` Benjamin Tissoires
2016-03-15 21:09 ` Roderick Colenbrander
2016-03-15 22:59 ` Bastien Nocera
2016-03-16 0:17 ` Roderick Colenbrander
2016-03-16 15:10 ` Bastien Nocera
2016-03-16 15:26 ` David Herrmann
2016-03-16 19:00 ` Roderick Colenbrander
2016-03-17 9:27 ` David Herrmann
2016-03-16 19:09 ` Clément VUCHENER
2016-03-16 20:32 ` Roderick Colenbrander
2016-03-16 22:51 ` Clément VUCHENER
2016-03-16 18:39 ` Roderick Colenbrander [this message]
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=CAEc3jaAUmhzVwCMWWwWADCwz22Q8sFQP5qN5H8+Gb2Exf3GRcQ@mail.gmail.com \
--to=thunderbird2k@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@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).