On Wed, 27 Sep 2006, Auke Kok wrote: > > Older equipment, which may still be in use here and there, allowed > > full-duplex operation, but no auto-negotiation. The duplex setting was > > either fixed or selectable in a system-specific manner. In such a case you > > certainly want your modern other end to be forced to full-duplex, but still > > let it detect the link speed, so that you do not have to do reconfiguration > > whenever you move a link between a 10base-T and a 100base-Tx port. > > in this case the new addition to ethtool will not help as it only changes the > modes that the NIC will advertise. In this specific case you will need to turn > of advertising/autonegotiation and force a speed/duplex pair anyway.
My whole point is to keep the speed negotiation enabled. If you force a given speed and the partner only supports a different one, you will get no link. > Advertising all half-duplex modes to a partner that does not do > autonegotiation is (by spec I think) an unsupported configuration (i.e. > undetermined behaviour). Yes, but more reasonable PHYs will autosense the link speed if allowed to, even if the partner is not capable of negotiating. It is useful, so why should we limit people so that they cannot do it? And as I wrote, it is not half-duplex operation that is problematic as it is the default if the partner does not negotiate anyway. Maciej - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
