Stef Hellemans wrote: > I am having a problem whit the uru 4000 sensor. I am getting a wrong > interrupt type back. Instead of the interrupt 56aa I am getting b194. I > only have this when I work on my cris processor. On my pc it works > normal so I don’t think something is wrong whit the sensor. The debug > info is listed below
I've never heard of that interrupt type. As the protocol is entirely reverse engineered we can't just look up it's meaning, unfortunately. Can you use usbmon on both your PC and your cris to capture the raw data from when using fprint? See Documentation/usb/usbmon.txt in the kernel source. You need to compile your kernel with CONFIG_DEBUG_FS and CONFIG_USB_MON. Thanks, Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
