********** REQUEST *********** Would it be possible for someone to add the controller info to the debug messages, in the proper way. I just stuck in what I needed, without any thought as to format. ******************************
The 2.5 driver should be better, though I've got some diagnostics patches pending there. I'll likely submit them before too long, more or less at the time I post a backport of that newer OHCI code to the latest 2.4 kernel.
Yes, now that most new PC hardware has multiple USB 1.1 controllers, that old "there's only one" assumption is troublesome.
Some of the error codes, -75 EOVERFLOW, I can' find in any of the source I'm running. I'm probably blind!
See the cc_to_error[] in usb-ohci.h, which is where all the hardware error codes get translated (from <linux/usb.h> USB_ST_* codes, finally gone in 2.5).
I've seen this failure on both hardware. <3>usb-ohci.c: OHCI Unrecoverable Error, controller usb-00:12.1 disabled <7>usb-ohci.c: OHCI controller usb-00:12.1 state
If you want to track this down further, the first thing I'd suggest is trying to reproduce it on the 2.5 "ohci-hcd" driver. Since you're only accessing it from user mode (with usbfs) that should be easy to do. (Make sure you have the latest "module-init-tools".) - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
