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 18:40:04 -0400 [thread overview]
Message-ID: <4660A044.5090007@garzik.org> (raw)
In-Reply-To: <46F9780F64AE9945815725F4C0C72CB803026226@hq-exch-1.corp.brocade.com>
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
> Sun http://www.sun.com/blueprints/0704/817-7526.pdf says that IEEE
> 802.3ab says you can't force 1000Base-T over copper media (see page 4),
> whereas some other physical media allow GigE to run without
> autonegotiation (there's apparently this "serdes" interface that allows
> it, for instance).
>
> Seems like there should be another field named something like
> supported_forced to indicate what can be forced on the interface. Either
> that or some more SUPPORTED_* bits to indicate supported forced modes.
The 'supported' field has nothing at all to do with auto-negotiation.
The driver should list all possibilities in that field, even if some are
ONLY supported via 'forced' selection.
Jeff
P.S. netdev@linux.kernel.org is a far more active list, and is where
the network stack/driver developers appear.
next parent reply other threads:[~2007-06-01 22:40 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 ` Jeff Garzik [this message]
2007-06-01 22:51 ` ETHTOOL_GSET IOCTL on GigE links Jeff Haran
2007-06-01 22:59 ` David Miller
2007-06-01 23:04 ` Jeff Garzik
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=4660A044.5090007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).