Messages in this thread | | | Date | Tue, 07 Dec 2010 20:57:14 +0100 | From | Henrik Rydberg <> | Subject | Re: [RFC][PATCH] input: Introduce device information ioctl |
| |
On 12/07/2010 10:16 AM, Dmitry Torokhov wrote:
> Hi Henrik, > > On Tue, Dec 07, 2010 at 08:25:26AM +0100, Henrik Rydberg wrote: >> Today, userspace sets up an input device based on the data it emits. >> This is not always enough; a tablet and a touchscreen may emit exactly >> the same data, for instance, but the former should be set up with a >> pointer whereas the latter does not need to. Recently, a new type of >> touchpad has emerged where the buttons are under the pad, which changes >> handling logic without changing the emitted data. This patch introduces >> a new ioctl, EVIOCGDEVINFO, which allows userspace to extract information >> about the device resulting in proper setup. > > If we agree that the new ioctl is suitable we'llalso need to wireit up > through sysfs. Also, can we keep all definitions to INPUT_ namespace? > > Thanks. >
Thanks all for the comments, this is what I extract from them:
* Split struct into separate calls, although this still seems debated.
* Use INPUT_ namespace
* Add sysfs version
* Keep bitmask for types. Is the list of types complete?
* Still only one data point for capabilities. Anything else?
Sounds about right?
Thanks, Henrik
| |