On Saturday 11 August 2007, Alan Stern wrote:
> 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.
Being simple doesn't preclude being sophisticated. In fact it's
probably the ultimate mark of sophistication that only essential
components exist.
“Perfection is achieved, not when there is nothing left to add,
but when there is nothing left to remove.” — Antoine de Saint-Exupery
Though it seems to be true that there are multiple definitions
of sophtication, and ones that focus on complexity are at odds
with ones that focus on being highly refined. It's another of
those words which can self-mock. :)
> There's nothing like a Configured flag to check.
Irrelevant; it doesn't need to grab ports from other
controllers using such a mechanism.
> I'd say that makes it less
> sophisticated than ehci-hcd or uhci-hcd.
Less complicated, I'd agree.
-------------------------------------------------------------------------
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
