From: Bill Fink <billfink@mindspring.com>
To: "Michael Chan" <mchan@broadcom.com>
Cc: tarbal@gmail.com, jgarzik@pobox.com, Jeff@lime.pobox.com,
netdev@vger.kernel.org, davem@davemloft.net,
john.ronciak@intel.com, jesse.brandeburg@intel.com
Subject: Re: [PATCH] ethtool v4: add autoneg advertise feature
Date: Fri, 25 Aug 2006 19:42:54 -0400 [thread overview]
Message-ID: <20060825194254.7657318f.billfink@mindspring.com> (raw)
In-Reply-To: <1551EAE59135BE47B544934E30FC4FC093FAA2@NT-IRVA-0751.brcm.ad.broadcom.com>
On Thu, 24 Aug 2006, Michael Chan wrote:
> Jeff Kirsher wrote:
>
> > The old way of setting autonegotiation was using the
> > following command:
> > ethtool -s ethx speed 100 duplex full auto on
> > now the command would be
> > ethtool -s ethx auto on advertise 0x08
> > both commands would result in only advertising 100 FULL.
> >
> > There still needs to be a change made to the man file to reflect the
> > change in the behavior of ethtool, which I have not done. But this
> > patch will allow for greater flexibility in setting autonegotiation
> > speeds.
>
> It is more flexible, but less intuitive. The user now has to
> remember hex values instead of the more intuitive speed and
> duplex. Perhaps we can keep the old method of using speed and
> duplex, while adding the new method of specifying hex values?
I agree. Something like:
ethtool -s ethx auto on advertise mode1+mode2+...+moden
For example:
ethtool -s ethx auto on advertise 100-half+100-full
to set speed 100 either half or full duplex.
Maybe have some abbreviations such as 100-all (same as above) or
all-half (for all supported half duplex) or just all (for all supported
modes), which I suppose is the default.
Just an idea.
-Bill
next prev parent reply other threads:[~2006-08-25 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060805054256.14081.74770.stgit@lunar.tarbal.com>
2006-08-24 6:26 ` [PATCH] ethtool v4: add autoneg advertise feature Jeff Garzik
2006-08-24 15:22 ` Jeff Kirsher
2006-08-24 15:41 ` Michael Chan
2006-08-24 15:54 ` Jeff Kirsher
2006-08-24 15:59 ` Auke Kok
2006-08-24 16:05 ` Auke Kok
2006-08-24 16:12 ` Jeff Kirsher
2006-08-25 23:42 ` Bill Fink [this message]
2006-08-26 0:28 ` Jeff Kirsher
2006-08-26 0:58 ` Bill Fink
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=20060825194254.7657318f.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=Jeff@lime.pobox.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=tarbal@gmail.com \
/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).