On Fri, 20 Oct 2006, Alan Stern wrote:
> Okay, I tried it. And I found a bug: When RD and RHSC are both set in the
> interrupt status register, the driver tries to do _two_ root-hub resumes!
> That accounts for the mysterious "resume root" lines in the log.
>
> The patch below fixes that problem. I didn't see the other, more
> important problem, though. All the port resumes all completed as expected
> and on time. Still, you never know -- perhaps the patch will fix both
> problems.
By the way, if you still run into your problem with that patch applied and
you're still worried about "bogus" root-hub states, try doing this:
Plug in some other USB device into one of the other OHCI ports first.
Something normal, like a flash drive or an HID device.
Then the state in question will be:
One port connected and enabled (the other device);
One port connected, enabled, and suspended (the ftdi device);
Root hub is OPERATIONAL.
This state is one that has been supported ever since you originally added
the suspend/resume code. The only difference from before is that the
other port is enabled. I predict this won't affect what happens when the
system tries to autoresume the ftdi device.
Alan Stern
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
