mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
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: Fri, 22 Jun 2001 17:10:37 +1200	[thread overview]
Message-ID: <20010622171037.D2576@metastasis.f00f.org> (raw)
In-Reply-To: <3B23AFC3.71CE2FD2@mandrakesoft.com>
In-Reply-To: <3B23AFC3.71CE2FD2@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, Jun 10, 2001 at 01:34:59PM -0400

On Sun, Jun 10, 2001 at 01:34:59PM -0400, 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.
    
    I have included a sample implementation in the epic100 driver, to
    illustrate how these helpers may be used.  This should make it easier to
    implement support across 10/100 hardware which uses primarily an MII
    phy.
    
    Comments appreciated.

Can someone explain to me why we have ethtool and mii-tool? Can we
not extend ethtool for the mii-tool stuff, even if only at userland?



  --cw

  parent reply	other threads:[~2001-06-22  5:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 17:34 Jeff Garzik
2001-06-11  5:59 ` Pekka Savola
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 [this message]
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=20010622171037.D2576@metastasis.f00f.org \
    --to=cw@f00f.org \
    --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
all inboxes | Powered by JetHome®