Kirsher, Jeffrey T wrote:
Sorry. The duplex control register is used for setting the driver and
is not necessary for debug purposes. The value of the duplex control
register is what the register's current value is and may not reflect the
correct status of the current connection. That is what
Jeff Kirsher wrote:
The duplex control register is used for setting the driver and is not
necessary for debug purposes. The value of the duplex control register is
what the register's current value is and may not reflect the correct status
of te current connection. That is what the duplex
applied, after replacing ethtool: with e1000: in the subject line.
Even if it's modifying the ethtool app? As long as it doesn't confuse
your scripts, I suppose.
-Jeb
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More
cramerj wrote:
applied, after replacing ethtool: with e1000: in the subject line.
Even if it's modifying the ethtool app? As long as it doesn't confuse
your scripts, I suppose.
ethtool is a separate project. Since the email contents are copied into
the ethtool project changelog, having
The duplex control register is used for setting the driver and is not
necessary for debug purposes. The value of the duplex control register is
what the register's current value is and may not reflect the correct status
of te current connection. That is what the duplex status register is used
Removes duplex information from the control register dump when ethtool
-d is called.
The duplex control register is used for setting the driver and is not
necessary for debug purposes. The value of the duplex control
register is what the register's current value is and may not reflect
the
