Re: [PATCH] Expose input device usages to userspace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 14 March 2006 09:22, Arjan van de Ven wrote:
> > > No, I don't think this is needed at all - users should be interested in
> > > what capabilities a particular device has, not what type it was
> > > assigned by soneone.
> >
> > I see your point that an application should not rely too much on device
> > usages. However, the main reason I want device usages is to help
> > applications and users identify and (visually) represent devices. For
> > example, games could show an appropriate icon graphic representing each
> > active device. The event interface already has a few other ioctls for
> > this kind of information:
>
> ok then you should consider to do it the other way around: make a way of
> asking
> "are you matching THIS profile".
> rather than
> "what profile are you"
>
> that way devices can present multiple faces etc; which is going to be
> needed as more and more weird devices come into existence.

If by profile you mean a device usage like Mouse, Keyboard, Joystick etc. is 
your proposal covered by the bit field ioctl exposed by my patch? For 
example, a device can already expose itself as both a joystick and a mouse 
(see the hid-input.c changes from the patch).

 - elias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux