Hi, I'm currently developing a python application to communicate with an USB device, with pyusb (that use libusb). Communications are through control request. The program works very well on a computer running Fedora i686 but not on a computer running Fedora x86-64. By analyzing the communication with usbmon, I noticed that the wIndex field of the USB request remain at 0 (instead of 0x00f0), which is the default value in the function controlMsg() in pyusb librarie. And only with this field and control-out requests. usbmon trace on 2.6.32.11-99.fc12.i686 kernel : f6797800 3012799010 S Co:2:004:0 s 40 0c 5003 00f0 0001 1 = 30 f6797800 3012800594 C Co:2:004:0 0 1 > f6797800 3012801981 S Co:2:004:0 s 40 0c 5003 ffff 0001 1 = a0 f6797800 3012803587 C Co:2:004:0 0 1 > usbmon trace on 2.6.32.11-99.fc12.x86_64 kernel : ffff88001ae08c00 667700895 S Co:4:003:0 s 40 0c 5003 0000 0001 1 = 30 ffff88001ae08c00 667702510 C Co:4:003:0 0 1 > ffff88006acf2d80 667705695 S Co:4:003:0 s 40 0c 5003 0000 0001 1 = a0 ffff88006acf2d80 667708500 C Co:4:003:0 0 1 > By comparing the result of the "lshal" command on both computers, I noticed that on x86-64 computer (the one where it doesn't work), I have an extra line: « info.linux.driver = 'usb' (string) » But I don't know what it corresponds and I don't understand why my program don't work on both computer. Are there other tools to analyze what happens or to see where it crashes ? I don't know where to ask for help so I hope you can help me or redirect me somewhere. Thank you, Loïc GRENON -- 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
