Alan Stern wrote: > What did you do to the USB layer?
I meant the USB layer in ndiswrapper. The driver for SIS163 required implementation of more USB functions (than what existed earlier in ndiswrapper). > These messages mean that the device did not respond to a 4-byte > control-OUT URB. For an explanation of the error codes, read > Documentation/usb/error-codes.txt. I will probably have to compare URBs with that captured with usbsnoop in Windows. I started doing this, but was overwhelmed by size of output; looks like I need to process this with a script to see where things are going wrong. > These means that the device did not respond to a control-IN URB. In fact, > from your description it sounds like the device has stopped responding > almost entirely. Yes, that is what my understanding is too. Thanks for the information. Giri. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
