From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
"Song, Barry" <Barry.Song@analog.com>
Subject: Re: Using uinput
Date: Tue, 31 Aug 2010 19:24:20 +0100 [thread overview]
Message-ID: <4C7D48D4.8070106@cam.ac.uk> (raw)
In-Reply-To: <4C7BEF39.2030507@cam.ac.uk>
On 08/30/10 18:49, Jonathan Cameron wrote:
> Hi All,
>
> In a thread to do with the cma3000 accelerometer on lkml Dmitry (input maintainer)
> in passing mentioned that an iio to input bridge might exist in userspace
> using uinput.
>
> Looks to me like this might kill two birds with one stone for us.
>
> * Would finally provide a route for all those who want their sensor
> drivers in input because they want to use them for games.
> * Would provide a fairly good test of the generality of the user space interfaces.
>
> What do people think of this rather than an in kernel bridge?
>
> Given it would trivially have access to all of the info on what the sensor is producing
> it actually looks much easier to do than the kernel bridge (which was going to need
> a userspace configuration element or a lot of changes to our internal structure).
>
If anyone is curious, I just cc'd the list in on the mega lkml thread because
my post includes a quick and dirty hacked together bridge. It works.
Annoying my test platform is currently rather unstable (stargate2).
Git bisect fun tomorrow.
Jonathan
prev parent reply other threads:[~2010-08-31 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 17:49 Using uinput Jonathan Cameron
2010-08-31 18:24 ` Jonathan Cameron [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=4C7D48D4.8070106@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Barry.Song@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.