Jeff Haran wrote:
With 10/100 Mbps links it wasn't such an issue since the devices tend to
support the same forced speeds and duplexities as they are capable of
negotiating, but with GigE links that's not always the case, at least
not according to what I've read. For instance, the following doc
From: Jeff Haran [EMAIL PROTECTED]
Date: Fri, 1 Jun 2007 15:51:18 -0700
OK, but my question remains. In the case where a device supports one set
of speeds via autonegotiation and another set via forcing, how does one
tell which speeds can be forced and which can be autonegotiated?
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Friday, June 01, 2007 3:40 PM
To: Jeff Haran
Cc: [EMAIL PROTECTED]; netdev
Subject: Re: ETHTOOL_GSET IOCTL on GigE links
Jeff Haran wrote:
With 10/100 Mbps links it wasn't such an issue since the
devices
Jeff Haran wrote:
OK, but my question remains. In the case where a device supports one set
of speeds via autonegotiation and another set via forcing, how does one
tell which speeds can be forced and which can be autonegotiated?
The interface does not currently support such enumeration.
You
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Friday, June 01, 2007 4:05 PM
To: Jeff Haran
Cc: [EMAIL PROTECTED]; netdev
Subject: Re: ETHTOOL_GSET IOCTL on GigE links
Jeff Haran wrote:
OK, but my question remains. In the case where a device
supports one
