From: Pekka Savola <pekkas@netcore.fi>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<netdev@oss.sgi.com>, "David S. Miller" <davem@redhat.com>
Subject: Re: PATCH: ethtool MII helpers
Date: Mon, 11 Jun 2001 08:59:10 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0106110852570.23217-100000@netcore.fi> (raw)
In-Reply-To: <3B23AFC3.71CE2FD2@mandrakesoft.com>
On Sun, 10 Jun 2001, Jeff Garzik wrote:
> Initial draft of a helper which uses generic elements present in several
> net drivers to implement ethtool ioctl support in a minimum amount of
> code.
In the patch there is:
@@ -135,6 +139,11 @@
MODULE_PARM(rx_copybreak, "i");
MODULE_PARM(options, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM(full_duplex, "1-" __MODULE_STRING(MAX_UNITS) "i");
+MODULE_PARM_DESC(debug, "EPIC/100 debug level (0-5)");
+MODULE_PARM_DESC(max_interrupt_work, "EPIC/100 maximum events handled per interrupt");
+MODULE_PARM_DESC(options, "EPIC/100: Bits 0-3: media type, bit 4: full duplex");
+MODULE_PARM_DESC(rx_copybreak, "EPIC/100 copy breakpoint for copy-only-tiny-frames");
+MODULE_PARM_DESC(full_duplex, "EPIC/100 full duplex setting(s) (1)");
I recall some discussion on a list (can't find it now) that driver
specific comment like "EPIC/100" here notification on all _DESC's would be
removed to a separate MODULE_ to make the comments more generic?
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
next prev parent reply other threads:[~2001-06-11 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 17:34 PATCH: ethtool MII helpers Jeff Garzik
2001-06-11 5:59 ` Pekka Savola [this message]
2001-06-11 6:10 ` Keith Owens
2001-06-12 17:09 ` Bogdan Costescu
2001-06-12 17:40 ` Jeff Garzik
2001-06-12 18:40 ` PATCH: ethtool MII helpers (vers 2) Jeff Garzik
2001-06-13 15:29 ` PATCH: ethtool MII helpers Bogdan Costescu
2001-06-13 16:56 ` Donald Becker
2001-06-13 20:24 ` Jeff Garzik
2001-06-15 17:22 ` Bogdan Costescu
2001-06-22 5:10 ` Chris Wedgwood
2001-06-22 5:24 ` Jeff Garzik
2001-06-22 5:34 ` Chris Wedgwood
2001-06-22 5:58 ` Jeff Garzik
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=Pine.LNX.4.33.0106110852570.23217-100000@netcore.fi \
--to=pekkas@netcore.fi \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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).