From: Don Fry <brazilnut@us.ibm.com>
To: netdev@oss.sgi.com
Subject: RFC ethtool usage
Date: Thu, 5 May 2005 16:41:28 -0700 [thread overview]
Message-ID: <20050505234128.GA21736@us.ibm.com> (raw)
One of the pieces of information that is useful for me when debugging
problems with the pcnet32 driver, is which chip version the problem
occurs with (79C973, 79C976, etc).
Since the chip has no firmware, how badly would I be flamed, if I
modified the driver to return the string (which is currently printed
on boot), as the 'firmware-version'?
--- orig.pcnet32.c Mon May 2 15:12:02 2005
+++ pcnet32.c Mon May 2 15:13:38 2005
@@ -559,6 +559,7 @@ static void pcnet32_get_drvinfo(struct n
strcpy (info->driver, DRV_NAME);
strcpy (info->version, DRV_VERSION);
+ strncpy(info->fw_version, lp->name, sizeof(info->fw_version) - 1);
if (lp->pci_dev)
strcpy (info->bus_info, pci_name(lp->pci_dev));
else
So the output looked like:
$ ethtool -i eth0
driver: pcnet32
version: 1.30j
firmware-version: PCnet/PRO 79C976
bus-info: 0000:00:01.0
$
--
Don Fry
brazilnut@us.ibm.com
next reply other threads:[~2005-05-05 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 23:41 Don Fry [this message]
2005-05-06 2:32 ` RFC ethtool usage Jeff Garzik
2005-05-06 3:01 ` David S. Miller
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=20050505234128.GA21736@us.ibm.com \
--to=brazilnut@us.ibm.com \
--cc=netdev@oss.sgi.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).