From: Bastien Nocera <hadess@hadess.net>
To: Simon Wood <simon@mungewell.org>
Cc: linux-input@vger.kernel.org,
Frank Praznik <frank.praznik@oh.rr.com>,
linux-iio@vger.kernel.org
Subject: Re: [RFC] HID: hid-sony: Add basic iio-subsystem reading of SixAxis Accelerometers
Date: Thu, 11 Jun 2015 17:07:34 +0200 [thread overview]
Message-ID: <1434035254.5707.21.camel@hadess.net> (raw)
In-Reply-To: <1434034458-1968-1-git-send-email-simon@mungewell.org>
On Thu, 2015-06-11 at 08:54 -0600, Simon Wood wrote:
> [resent as I screwed up addressing... sorry]
>
> This patch is a RFC/POC for the idea of using the iio-subsystem as
> the
> 'proper' way to communicate the state of motion enabled controllers
> to
> the Linux internals.
>
> I have started with the hid-sony driver, with support for the
> SixAxis's
> 3 Accelerometers. Proper trigger/buffer support will follow shortly,
> along
> with support for the DS4 and PSMove controllers (which have a much
> more
> extensive set of motion hardware).
>
> Once the sensor data is available (over iio) I envision that it will
> be
> considerably easier to write motion tracking, flight control and AHRS
> software in a consistant manner.
Given that the software reading from the sensors will need to be root,
how will you send the data from those devices to the applications?
> Hopefully this will become the standard way of connecting
> controllers,
> motion controls and head mounted displays.
next prev parent reply other threads:[~2015-06-11 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <195dff9bd065db7e618280cb7c6eb5a9.squirrel@mungewell.org>
2015-06-11 14:48 ` [RFC] HID: hid-sony: Add basic iio-subsystem reading of SixAxis Accelerometers Simon Wood
2015-06-11 14:54 ` Simon Wood
2015-06-11 15:07 ` Bastien Nocera [this message]
2015-06-14 14:53 ` Jonathan Cameron
2015-06-14 17:25 ` simon
2015-06-14 17:57 ` Jonathan Cameron
2015-06-15 18:14 ` Srinivas Pandruvada
2015-06-21 13:16 ` Jonathan Cameron
2015-06-18 6:15 ` simon
2015-06-21 13:12 ` Jonathan Cameron
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=1434035254.5707.21.camel@hadess.net \
--to=hadess@hadess.net \
--cc=frank.praznik@oh.rr.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=simon@mungewell.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).