From: Auke Kok <auke-jan.h.kok@intel.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Michael Chan <mchan@broadcom.com>,
Jeff Kirsher <tarbal@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
Jeff@lime.pobox.com, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>,
John Ronciak <john.ronciak@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [PATCH] ethtool v4: add autoneg advertise feature
Date: Thu, 24 Aug 2006 09:05:19 -0700 [thread overview]
Message-ID: <44EDCE3F.9010208@intel.com> (raw)
In-Reply-To: <44EDCCE2.3030408@intel.com>
Auke Kok wrote:
> 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?
>
> the patch doesn't remove the old method, it merely adds a second path to
> the speed/duplex setting. Using the "old" syntax will still work.
hmm, I'm not saying I was wrong there and that if the patch did remove the old
method there will certainly be a new patch that keeps the old functionality.
okay okay, I am ;)
Auke
next prev parent reply other threads:[~2006-08-24 16:11 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 [this message]
2006-08-24 16:12 ` Jeff Kirsher
2006-08-25 23:42 ` Bill Fink
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=44EDCE3F.9010208@intel.com \
--to=auke-jan.h.kok@intel.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).