On Fri, 10 Aug 2007, David Brownell wrote: > > The code in ohci-hcd isn't very sophisticated about > > checking for interference from the firmware. Maybe because there are > > so many different implementations of OHCI floating around, it's hard > > to know what approach will work on all of them. And maybe because > > there aren't many settings which can be checked. > > On the contrary ... it's relatively sophisticated, precisely since > there ARE so many different hardware variations.
Relatively sophisticated? All it does is check if the firmware owns the controller or the controller is in a reset state. There's nothing like a Configured flag to check. I'd say that makes it less sophisticated than ehci-hcd or uhci-hcd. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
