From: Jeff Garzik <jeff@garzik.org>
To: Jeff Haran <jharan@Brocade.COM>
Cc: linux-net@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: ETHTOOL_GSET IOCTL on GigE links
Date: Fri, 01 Jun 2007 19:04:36 -0400 [thread overview]
Message-ID: <4660A604.4080701@garzik.org> (raw)
In-Reply-To: <46F9780F64AE9945815725F4C0C72CB80302625D@hq-exch-1.corp.brocade.com>
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 can certainly attempt forcing a speed, and see what happens. The
driver will either (a) work, (b) refuse and give you an error message,
or (c) present you with a situation that requires filing a driver bug
report :)
Jeff
next prev parent reply other threads:[~2007-06-01 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46F9780F64AE9945815725F4C0C72CB803026226@hq-exch-1.corp.brocade.com>
2007-06-01 22:40 ` ETHTOOL_GSET IOCTL on GigE links Jeff Garzik
2007-06-01 22:51 ` Jeff Haran
2007-06-01 22:59 ` David Miller
2007-06-01 23:04 ` Jeff Garzik [this message]
2007-06-01 23:09 ` Jeff Haran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4660A604.4080701@garzik.org \
--to=jeff@garzik.org \
--cc=jharan@Brocade.COM \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.