> At one stage hiddev claimed every device. I am not sure when Vojtech
> changed this behaviour. I know that some protocols require a sequence of
> control commands, and it is bad karma if you get them mixed up (eg if you
> want to change the resolution on Logitech dual optical devices, you have to
> send a couple of commands. The device may not want you to try anything
> between them)>
>
> I'm seeing three options:
> 1. Change the HID driver to always associated interfaces with hiddev, even
> if also associated with hid-input. Probably needs some locking.
> 2. Don't used hiddev, just use usbfs control messages directly from
> userspace, and hope that you don't cock up something that hid-input is
> doing. 3. Add some additional code through the whole input subsystem.
>
> I'm thinking that option 1 is the best. It'll be trivial to associate every
> hid interface with hiddev - there is code that looks like:
If you do that you make hiddev much more sensitive in terms of security.
Know passwords could be read.
So you should do that only upon request.
If you need support for atomic sequences you need to add it to hiddev.
IMHO praying that people do it right isn't enough.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
