From: Mirko Lindner <demon@pro-linux.de>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
krishnakumar@naturesoft.net, mlindner@syskonnect.de,
netdev@oss.sgi.com, felix@allot.com
Subject: Re: [PATCH]sk98lin ethtool support
Date: Fri, 02 Jan 2004 14:23:10 +0000 [thread overview]
Message-ID: <3FF57ECE.5020107@pro-linux.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0401012352180.11808-100000@localhost.localdomain>
Feldman, Scott wrote:
> On Tue, 30 Dec 2003, Mirko Lindner wrote:
>
>
>>>Make sure you don't duplicate any ethtool functions. We don't need a
>>>NIC-specific diag tool either ;-) ethtool is the preferred method
>>>moving forward, as it's already shipping in most Linux distros.
>>
>>Yes, we need it ;) No kidding! This is not a tool for SW checks like
>>media, link or driver version checks, but a tool for HW checks like
>>register, PROM, MAC, PHY and some other chip and card checks. The
>>ethtool is a great tool, but the intention of this tool is not the same.
>
>
> If the tool reports the results of running the h/w checks, then you can
> use ETHTOOL_TEST. The summary results of all the tests is reported as
> PASS/FAIL. Not sure if your tool needs to do more...
>
> -scott
>
>
>
>
> <!DSPAM:3ff51cdf53311090219406>
>
Scott,
thanks for this info, but the tool reports not only the status, but also
the results of a test (Example: "Register 0xxxx=xxx", PROM info...).
"Problem" 2: All tests are included in the DIAG tool and not in the
driver. We have approx. 100 separate tests (over 1000 individual tests)
and the driver is huge enough (Support for Genesis, Yukon, Yukon-Lite,
Yukon-Plus and Yukon2 chipsets).
Mirko
next prev parent reply other threads:[~2004-01-02 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E0103424AA4@orsmsx402.jf.intel.com>
2004-01-02 8:00 ` [PATCH]sk98lin ethtool support Feldman, Scott
2004-01-02 14:23 ` Mirko Lindner [this message]
2003-12-30 10:24 Krishnakumar. R
2003-12-30 12:27 ` Mirko Lindner
2003-12-30 12:29 ` Felix Radensky
2003-12-30 15:14 ` Jeff Garzik
2003-12-31 1:15 ` Mirko Lindner
2003-12-31 0:23 ` Jeff Garzik
2003-12-31 1:37 ` Mirko Lindner
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=3FF57ECE.5020107@pro-linux.de \
--to=demon@pro-linux.de \
--cc=felix@allot.com \
--cc=jgarzik@pobox.com \
--cc=krishnakumar@naturesoft.net \
--cc=mlindner@syskonnect.de \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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).