On Wed, 20 May 2009, Jiri Slaby wrote: > >>> Full output from 2.6.28-11-generic at device connect: > >>> [ 1673.776066] usb 2-2: new low speed USB device using uhci_hcd and address 5 > >>> [ 1673.961620] usb 2-2: configuration #1 chosen from 1 choice > >>> [ 1673.982901] generic-usb 0003:0B57:8019.0005: hiddev96,hidraw1: USB > >>> HID v1.00 Device [HanWang co. HW Micro Drawing Tablet] on > >>> usb-0000:00:1d.0-2/input0 > >> Hmm, It looks like it is a standard HID device and got registered in the > >> input layer. Could you attach lsusb -v of that device and > >> /proc/bus/input/devices? > Actually I missed there is no "input" at 1673.982901, so the input is > not claimed. You still can read the events through hidraw (or via > deprecated hiddev). > Jiri, any ideas? Looks like there are no useful applications. A report > dump will tell us whether we can handle it through standard path (with > forced connect) or it has to be handled by hidraw, am I correct? Exactly. The device probably doesn't provide any applications that would pass through IS_INPUT_APPLICATION() macro (see include/linux/hid.h). We might well be extending this definition, as it is quite outdated (and doesn't for example deal with new digitizers very well). Report descriptor dump would absolutely be necessary (i.e. compiling the kernel with CONFIG_HID_DEBUG and modprobing the 'hid' module with 'debug=2' parameter). -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
