netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Valdis.Kletnieks@vt.edu
Cc: mitake@clustcom.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ktaka@clustcom.com
Subject: Re: [RFC] New functions to manipulate registers for ethtool
Date: Mon, 08 Dec 2008 01:06:34 -0800 (PST)	[thread overview]
Message-ID: <20081208.010634.247305010.davem@davemloft.net> (raw)
In-Reply-To: <58622.1228726903@turing-police.cc.vt.edu>

From: Valdis.Kletnieks@vt.edu
Date: Mon, 08 Dec 2008 04:01:43 -0500

> On Mon, 08 Dec 2008 00:54:31 PST, David Miller said:
> > From: Hitoshi Mitake <mitake@clustcom.com>
> > Date: Mon, 8 Dec 2008 17:12:30 +0900
> > 
> > > I want to add two new functions to ethtool.
> > > 
> > > One is for setting driver's registers on MMIO area like
> > > --change-eeprom option.
> > 
> > You can map the registers into userspace using the bus
> > level mmap facilities exported to userspace.
> > 
> > No ethtool support is necessary for this.
> 
> Yes, but if Hitoshi wants to tell a user "run this command and send me
> the output", what's the incantation the user needs to use?

That's an awful reason to have to two ways of doing the exact same
thing from userspace.

Write the tool.  Someone will if it's important enough (in fact
such code probably exists already).


  reply	other threads:[~2008-12-08  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  8:12 [RFC] New functions to manipulate registers for ethtool Hitoshi Mitake
2008-12-08  8:54 ` David Miller
2008-12-08  9:01   ` Valdis.Kletnieks
2008-12-08  9:06     ` David Miller [this message]
2008-12-08  9:26       ` Valdis.Kletnieks
2008-12-08  9:57         ` David Miller
2008-12-08 17:36       ` Brandeburg, Jesse
2008-12-10 11:26         ` Hitoshi Mitake
2008-12-08  9:01   ` Hitoshi Mitake

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=20081208.010634.247305010.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=ktaka@clustcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitake@clustcom.com \
    --cc=netdev@vger.kernel.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 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).