On Wednesday 12 January 2005 8:02 am, Petko Manolov wrote: > On Wed, 12 Jan 2005, David Brownell wrote: > > > Mike Nix confirmed it resolved the bridging issue for him too, but > > reported some problems detecting carrier loss. Does that ring any > > bells for you? I found the link status bit you were testing would > > always say "connected" (on a D-Link adapter), while the TX status > > bit behaved once the host transmitted something. > > Well, reading the PHY's media status register should always indicate the > correct value. According to the specs part of the information passed > through interrupt pipe (incl link status) is read from the MII, which > probably doesn't happen. I could experiment and see if can prove this > theory.
Sounds like the theory I was ending up with ... :) 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 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!) > D-Link and Linksys have always had slightly different GPIO setup (part > of which connect the MII to adm851x), hence the problem. It is possible > that the TX/RX and link status LED doesn't work either. 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. - 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
