On Wed, 29 Jul 2009, vijay manchala wrote: > Hi > > I saw earlier mailing lists which says about the releasing the hid driver using "unbind", > > so what I did here now is, " echo -n /sys/bus/usb/driver/usbhid/bind" from the command line > > Then I compiled the usbmouse.c as it is whithout changing anything of that file. Now I got usbmouse.ko module. > Next I inserted that module using insmod usbmouse.ko. > > Then I went back to /sys/bus/usb/devices/ and given the command > " echo -n 4-1.1.1 > /sys/bus/usb/drivers/usbmouse/bind > > So now the mouse device is regsistered with usbmouse > > cat /proc/bus/usb/devices/ gives the below out put > > C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA > I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbmouse > > But when I see the dmesg and cat /proc/kmsg mesagges continuosly usb_mouse_irq is getting called without even any mouse clicks > > when I saw the status of urb->status it is -84 (EILSEQ) > > and usbmon capture is showed below one > <URB Tag> <Timestamp> <Event Type> <Address> > f02e5c80 150582594 S Ii:4:010:1 -115:8 4 < > f02e5c80 150606583 C Ii:4:010:1 -84:8 0 > f02e5c80 150606601 S Ii:4:010:1 -115:8 4 < > f02e5c80 150630578 C Ii:4:010:1 -84:8 0 > f02e5c80 150630594 S Ii:4:010:1 -115:8 4 < > f02e5c80 150654576 C Ii:4:010:1 -84:8 0 ... > ... > above message is continuously recieving after binding the device > > But am able to reicieve the device details properly like vendor id , product id and all remaining things > > > Is any thing wrong am doing or my approach itself not correct. > Please suggest me in this regard what am missing in usbmouse.c to get it work properly. In general nothing is wrong (although you should not use usbmouse because usbhid is much better). -84 indicates a hardware or firmware problem, not a software problem. Perhaps if you provided a complete usbmon log (starting from before you detach usbhid) the answer would be clear. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
