On Wed, 15 May 2002 08:46, Jens Kilian wrote: > > On Tue, 14 May 2002 17:55, Jens Kilian wrote: > > > As far as I can see, the only way to create an HID compliant report > > > descriptor for such a device is to use the "Ordinal" usage page to > > > specify 9 instances of a "Dial" control. Unfortunately, the Linux > > > USB/input drivers don't support the Ordinal page at the moment. I > > > therefore propose to add support for this page to the hid-input driver > > > and to somehow extend the /dev/input... driver to make use of this > > > information. > > > > I think that this is a key issue. Exactly what do you plan to do with > > this device in userspace? If you will always need a special userspace > > driver anyway, then the easiest way to handle this device might be to use > > hiddev. > > Well, it is potentially a plain vanilla input device; it could be used > by any application, but I plan to (eventually) write an XInput driver for > it. (I'd have to use the evdev driver, of course, because this is not a > mouse, keyboard, or joystick.) Err, more detail needed. Sure, any application could use it. But what do you want to get out of it? In particular, what would each dial do? How is that different to a mouse or a spaceball? When you know what the device is meant to do, you can make a good interface.
BTW: You would want to use the evdev interface anyway, because it has long term life. Brad -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
