On Sun, Jun 17, 2012 at 4:08 PM, Nils Kanning <nils@xxxxxxxxxx> wrote: > On Sat, 2012-06-16 at 19:43 -0500, Chris Bagwell wrote: >> > The exact patch used is at [2]. That produced: > >> Can you "rmmod wacom" and this run "lsusb -vvv" and email me directly >> or post to debian bug report the section for Wacom? I'd like to look > > With this kernel I could not remove the wacom module using "rmmod > wacom" (the options -f or -w do not help). Furthermore "lsusb -vvv" > hangs at the wacom device and does not produce more then: > Bus 002 Device 004: ID 056a:00e6 Wacom Co., Ltd > > The output of "lsusb -vvv" using the Debian kernel from linux-image > 3.2.17 and after doing "rmmod wacom" is in the attached file. > > Nils > The HID report didn't help me yet; other then now knowing the i++ is correct. Your dmesg log file from 3.5-rc2 gives best hint yet at problem. [ 2.159684] input: Wacom ISDv4 E6 Pen as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5 [ 2.164406] input: Wacom ISDv4 E6 Pen as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6 Instead of opps, it loads 2 input devices. That second device should say "Finger" instead of "Pen". Thats related to device_type that gets set while parsing the HID report. I'll need some more time to study your HID report to see if I can figure out why its getting confused. Chris -- 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
