From: Hitoshi Mitake <mitake@clustcom.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ktaka@clustcom.com
Subject: [RFC] New functions to manipulate registers for ethtool
Date: Mon, 8 Dec 2008 17:12:30 +0900 [thread overview]
Message-ID: <20081208171230.288c5ccf.mitake@clustcom.com> (raw)
Hi
I want to add two new functions to ethtool.
One is for setting driver's registers on MMIO area like --change-eeprom option.
I think form of command line is like this,
ethtool -X|--set-register ethX [offset N(in bytes)] [value N(single byte value)]
Another function is for reading driver's register on MMIO.
Currently, there is --register-dump option for dumping registers.
But I want finer granularity one which unit of manipulation is byte.
Like this,
ethtool -B|--dump-register-byte ethX [offset N(in bytes)]
(then print one byte to stdout)
Of course, names of options is temporary.
Because e1000e driver conflicts with some IPMI cards some time,
and the reasons of conflict are setting of registers not supported by
other general options of ethtool.
If this function is added, examing cause of confliction will be much easier.
How do you think about this plan?
If this plan is not bad, and nobody is working on patch like this plan,
I want to do that.
Thanks
Hitoshi
next reply other threads:[~2008-12-08 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 8:12 Hitoshi Mitake [this message]
2008-12-08 8:54 ` [RFC] New functions to manipulate registers for ethtool 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
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=20081208171230.288c5ccf.mitake@clustcom.com \
--to=mitake@clustcom.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).