On Wed, 12 Jan 2005, David Brownell wrote:
No -- CONFIG_BRIDGE. The "brctl" tool just administers the kernel infrastructure for 802.1d bridging. There's not even a kernel task associated with it, much less a userspace one.
Well, any reading of the PHY should go through the pegasus driver. Since there was no such code (and is still not) present in the driver it's a bit of a mystery for me. Either problems in the generic MII code or i'm getting something dead wrong. :-)
I didn't see any changes that should obviously have any effect on link detection, but there were other ethtool updates and code cleanups. (Talking of cleanups: the !MII #ifdefs can be deleted, now that Kconfig forcibly enables MII.)
Good i haven't sent the cset to Greg yet. Checking for CONFIG_MII was a must after i separated the MII code in the kernel (about 2 years ago), but it seems this is now fixed in a better way. Will send reworked cset in a few minutes.
Petko
------------------------------------------------------- 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
