| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 31 Aug 2010 10:53:37 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: Felipe Balbi <me@...ipebalbi.com>, Hemanth V <hemanthv@...com>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, igor.stoppa@...ia.com, kai.svahn@...ia.com, mathias.nyman@...ia.com Subject: Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver) > > My hope is that we can make use of a well known and uniform > > API for all input devices in a device, be it a keypad, > > touchscreen, accelerometer, magnetometer, gyro, or whatever. > > > > If only we could agree what input devices are... Is that the right test for some of these devices. Surely the question is "what devices can be meaningfully represented by the input API". The device range is always going to be quite large and people want to use the API because it means things just work. They can wire their home made surfboard unit and tilt sensors up to the PC and tuxracer just goes. They can wire pedals and a current meter to it and use it as the speed input in bzflag to simulate bicycle tanks etc.. 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