netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: David Acker <dacker@roinet.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	dhinds@pcmcia.sourceforge.org, netdev@vger.kernel.org
Subject: Re: mii-tool gigabit support.
Date: Wed, 27 Sep 2006 08:00:17 -0700	[thread overview]
Message-ID: <451A9201.6000600@intel.com> (raw)
In-Reply-To: <451A7603.1030204@roinet.com>

David Acker wrote:
> Stephen Hemminger wrote:
>> On Tue, 26 Sep 2006 17:55:34 -0400
>> Jeff Garzik <jgarzik@pobox.com> wrote:
>>
>>> Stephen Hemminger wrote:
>>>> The mii-tool utility seems to be abandoned and unmaintained?
>>>>
>>>> Here is a version that does standard 1000baseT support.
>>>>     http://developer.osdl.org/shemminger/prototypes/mii-tool.tar.bz2
>>> Not really.  I would rather leave it as-is, and deprecate it in favor 
>>> of ethtool.
>>>
>>
>> It does make a handy debug tool when driver isn't doing MII correctly.
>>
> 
> mii-tool supports some things that ethtool does not.  mii-tool -A lets 
> you set the advertised speeds and can include a list of speeds.  The 
> closest ethtool seems to have is ethtool -s but that seems to just set 
> the advertised speed to a single value only.

We sent a patch for this to Jeff recently that allows setting of 'arbitrary' 
speeds. Unfortunately the interface is rather crude but it works (for e1000, 
and possibly all other nics) to set any combination of advertised speeds.

e.g. `ethtool -s eth0 advertise 0x0f` advertises all non-gigabit speeds

I haven't seen the patch merged yet upstream though.

Cheers,

Auke

> 
> We have instances where we want to limit the link of the ethernet port 
> to no higher then 10 Mbps full duplex but also advertise support for 
> half duplex.
> 
> With mii-tool we can do the command below and work with a half duplex 
> hub and a full duplex switch.
> mii-tool -A 10baseT-FD,10baseT-HD eth0
> 
> Meanwhile if I use ethtool like the command below I will not work with a 
> half duplex only hub.
> ethtool -s eth0 speed 10 duplex full autoneg on
> 
> Perhaps the "speed" part of ethtool -s should take a list of speeds like 
> mii-tool does.
> 
> -Ack

  reply	other threads:[~2006-09-27 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 21:51 mii-tool gigabit support Stephen Hemminger
2006-09-26 21:55 ` Jeff Garzik
2006-09-26 22:09   ` Stephen Hemminger
2006-09-27 13:00     ` David Acker
2006-09-27 15:00       ` Auke Kok [this message]
2006-09-27 16:20         ` Jeff Kirsher
2006-09-27 17:08       ` Rick Jones
2006-09-27 17:50         ` Auke Kok
2006-09-27 17:57           ` Rick Jones
2006-09-27 18:05             ` Maciej W. Rozycki
2006-09-27 18:42               ` Auke Kok
2006-09-28 12:10                 ` Maciej W. Rozycki
2006-09-27 20:26         ` David Acker
2006-09-27 19:24   ` dean gaudet
2006-09-27 19:31     ` Stephen Hemminger
2006-09-27 19:32     ` Auke Kok
2006-09-27 19:37       ` dean gaudet
2006-09-29 16:12       ` David Hollis
2006-09-29 17:12         ` Stephen Hemminger
2006-09-29 17:54           ` Rick Jones
2006-10-01 14:31             ` Michael Tokarev
2006-09-27 19:15 ` dean gaudet

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=451A9201.6000600@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=dacker@roinet.com \
    --cc=dhinds@pcmcia.sourceforge.org \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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).