On Wed, 12 Jan 2005, David Brownell wrote:
Sounds like the theory I was ending up with ... :)
What a coincidence.. ;-)
The bridge code was able to detect the link coming back up, as if maybe it were talking directly to the MII and not needing to rely
You mean the user level code running on the same machine that has the pegasus thingie plugged in?
on the relevant bit in the status transfer. (I had a debug printk in there at one point, and there _was_ no status transfer that could have reported the carrier was back!)
Beats me, in case the answer of the above question is 'yes'. If it is 'not' then the job was done by the saner driver/device on the other side.
There have been versions of this driver where the LEDs didn't work right, but the current 2.6.10 doesn't seem to be one of them. Both LEDs work, and the link status LED is even the right color.
I am innocent! Haven't touched that part of the code for years.. :-)
Now this is interesting. Probably it's worth looking back in csets for the past few months and see where all that comes from.
Petko
- Dave
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
