On Sunday 28 October 2007 16:39, Jiri Kosina wrote: > On Sun, 28 Oct 2007, Torsten Kaiser wrote: > > > But it looks like that uses another driver: > > hiddev0hidraw1: USB HID v1.10 Device [Western Digital External HDD] on > > usb-0000:00:02.1-5.2 > > Otherwise I would be willing to try to test this, if someone would tell > > me how to check that the second commit did fix the suspend problem. > > If you need to unbind usbhid driver from the device and bind another one, > you can use the 'unbind' and 'bind' files in sysfs. > > As soon as the driver you are willing to test is bound to the device, you > can go ahead with testing any functionality you wish (probably > suspend/resume cycle is needed here?). > > If the device is claimed by usbhid driver (because its descriptor probably > states that it's HID-compliant device) and should be claimed by another > driver, it's necessary to add it to usbhid blacklist -- just let me know. >
Maybe onetouch driver is not needed after all. I wonder what key/button does HID deriver reports when it binds to it... Torsten, could you please post your /proc/bus/input/devices? -- Dmitry
