From: Auke Kok <auke-jan.h.kok@intel.com>
To: dean gaudet <dean@arctic.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Stephen Hemminger <shemminger@osdl.org>,
dhinds@pcmcia.sourceforge.org, netdev@vger.kernel.org
Subject: Re: mii-tool gigabit support.
Date: Wed, 27 Sep 2006 12:32:38 -0700 [thread overview]
Message-ID: <451AD1D6.4030708@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609271215150.2299@twinlark.arctic.org>
dean gaudet wrote:
> On Tue, 26 Sep 2006, Jeff Garzik 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.
>
> is there some ethtool (version 5) option i'm missing that will give a nice
> concise link negotation state report like mii-tool does?
how about `ethtool ethX` ? It doesn't report what happened during negotiotion
but it shows status and advertised/autonegotiated/supported modes
> on e1000 it seems i can find this info only via the -d option, which dumps
> a lot of other info.
>
> on skge -d doesn't seem to dump the negotiation state.
>
> on tg3 -d doesn't even interpret the registers...
>
> maybe it's just that i haven't had caffeine but i think i've tried every
> reporting option i can find on the man page and can't find link
> negotiation state.
dumping registers in readable format is an extension that needs to be
implemented per driver. Not all nics have done this - we just did it ourselves
for ixgb, and I saw skge/sky2 just fly by this week.
Cheers,
Auke
>
> -dean
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-09-27 19:34 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
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 [this message]
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=451AD1D6.4030708@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=dean@arctic.org \
--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 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.