On Wed, Nov 06, 2002 at 06:04:25PM +1100, Brad Hards wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wed, 6 Nov 2002 17:51, Pete Zaitcev wrote:
> > This is wonderful, however I am concerned that hiddev cannot be
> > used while input is using hid. This seems a little too limiting.
> > How am I supposed to implement the applet to indicate the battery
> > charge, for example? Adding Logitech-specific control messages
> > to mousedev does not look appealing.
> 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:
>         for (i = 0; i < hid->maxcollection; i++)
>                 if (hid->collection[i].type ==
>                     HID_COLLECTION_APPLICATION &&
>                     !IS_INPUT_APPLICATION(hid->collection[i].usage))
>                         break;
> 
> in hiddev::hiddev_connect(). If you remove this test, then it should claim 
> every device (except those blacklisted). The need for explicit locking should 
> be explored further.
> 
> There is a cost to this: more minor numbers required for hiddev. 
> 
> Greg, Vojtech - any comments?

I'm fine with all devices being available as hiddev. Not too much
additional locking should be needed, because the interfaces to hardware
are doing the serializing already.

> - -- 
> http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE9yL76W6pHgIdAuOMRAqIjAJ9+I0ipW+PvKuo6GaFEQ4U8ENHFFQCffPBM
> lE5DRUGYgUpYskPLcKoirjo=
> =71Bb
> -----END PGP SIGNATURE-----

-- 
Vojtech Pavlik
SuSE Labs


-------------------------------------------------------
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

Reply via email to