On 2/25/06, Michael Alladin <[EMAIL PROTECTED]> wrote: > There is a little side effect though. According to dmesg, four input classes > are registered (wrong, should be 2), but only two jsX nodes are created > (which is good).
> usb-storage: device scan complete > usb 3-2: new low speed USB device using uhci_hcd and address 2 > usb 3-2: string descriptor 0 read error: -32 > usb 3-2: string descriptor 0 read error: -32 > usbcore: registered new driver hiddev > input: HID 0925:8866 as /class/input/input1 > input: HID 0925:8866 as /class/input/input2 > input: HID 0925:8866 as /class/input/input3 > input: HID 0925:8866 as /class/input/input4 > input: USB HID v1.00 Joystick [HID 0925:8866] on usb-0000:00:10.2-2 > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver I don't know what those input classes are (I don't see them in my dmesg), but I would hazard a guess that they match 1-to-1 with nodes that are created in /dev/input/ in which case I'd say it's correct, seeing as for each joystick input it actually creates a js# and an event#. 'Course if someone else here tells you otherwise then I stand corrected :) -Andrew ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
