netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hitoshi Mitake <mitake@clustcom.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: David Miller <davem@davemloft.net>,
	"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ktaka@clustcom.com" <ktaka@clustcom.com>
Subject: Re: [RFC] New functions to manipulate registers for ethtool
Date: Wed, 10 Dec 2008 20:26:18 +0900	[thread overview]
Message-ID: <20081210202618.0f2a2218.mitake@clustcom.com> (raw)
In-Reply-To: <F169D4F5E1F1974DBFAFABF47F60C10A1753409B@orsmsx507.amr.corp.intel.com>

On Mon, 8 Dec 2008 09:36:53 -0800
"Brandeburg, Jesse" <jesse.brandeburg@intel.com> wrote:

> David Miller wrote:
> > 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.
> 
> one hiccup, Arjan recently added functionality to the kernel that could
> disallow this unless a user overrides at boot. [1]
> 
> also, there is a .config option that disallows this but I'm just
> mentioning it for posterity.
> 
> >>> 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?
> > 
> 
> ethregs -s <bus>:<dev>.<fn>
> 
> > 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).

Thanks for your replying, David, Valdis and Jesse.

> 
> Hi Hitoshi,
> you probably want to download and install our ethregs utility.
> http://prdownloads.sf.net/e1000/ethregs-1.1.tar.gz
> (this is not a direct link as it seems but gets redirected to a mirror
> page, usually)
> 

This is a nice software for me, Thanks.

> Please let me know if it doesn't support your device ID.

I used this on my environment.
My NICs are 82573L and 82573E. ethregs could detected them well.

It seems that this program doesn't support for writing value to registers.
I think making ethregs to support writing is not bad idea.
If you are not planning, I want to do that.

I'm not a professional of Intel's NICs.
How do you think?

  reply	other threads:[~2008-12-10 11:26 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
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 [this message]
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=20081210202618.0f2a2218.mitake@clustcom.com \
    --to=mitake@clustcom.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davem@davemloft.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=ktaka@clustcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).