[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100831104446.321fd4f4@lxorguk.ukuu.org.uk>
Date: Tue, 31 Aug 2010 10:44:46 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Felipe Balbi <me@...ipebalbi.com>, Hemanth V <hemanthv@...com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"igor.stoppa@...ia.com" <igor.stoppa@...ia.com>,
"kai.svahn@...ia.com" <kai.svahn@...ia.com>,
"matthias.nyman@...ia.com" <matthias.nyman@...ia.com>
Subject: Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2]
input: CMA3000 Accelerometer driver)
> 1. Input transport via evdev is very convenient
> 2. There is no other standard alternative
>
> Once there is standard interface for such sensors they will happily use
> it and will not look back.
I think the fact that most of the interest in IIO is "how do we make an
IIO/Input bridge" speaks volumes.
> Sure, for a particular cell phone there is no ambiguity, the sensor has
> certain functionality assigned that is well known. But does this mean
> that we should not expect parts being reused at all anymore?
If non-input uses later need non-input interfaces they can switch to that
with an input bridge when there is one and when it happens, which
probably won't.
> I am unsure how you would play a game with GPS as an input device.
In a non-game context take a look at things like the British Museum
application that allows you to view wherever you are and as it was long
ago by fishing out a relevant photograph as you walk around. In a game
context can I suggest the Zombies game is an example ?
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists