From: "John W. Linville" <linville@tuxdriver.com>
To: Taku Izumi <izumi.taku@jp.fujitsu.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH resend] ethtool: add register dump support for fjes driver
Date: Wed, 23 Nov 2016 09:56:47 -0500 [thread overview]
Message-ID: <20161123145646.GA13179@tuxdriver.com> (raw)
In-Reply-To: <1479257733-19277-1-git-send-email-izumi.taku@jp.fujitsu.com>
On Wed, Nov 16, 2016 at 09:55:32AM +0900, Taku Izumi wrote:
> This patch adds the register dump format for FUJITSU Extended
> Network device like the following:
>
> # ethtool -d es0
>
> 0x0000: OWNER_EPID (Owner EPID) 0x00000001
> 0x0004: MAX_EP (Maximum EP) 0x00000008
> 0x0010: DCTL (Device Control) 0x00000000
> 0x0020: CR (Command request) 0x80000002
> 0x0024: CS (Command status) 0x80000002
> 0x0028: SHSTSAL (Share status address Low) 0xE8215304
> 0x002C: SHSTSAH (Share status address High) 0x00000007
> 0x0034: REQBL (Request Buffer length) 0x00008028
> 0x0038: REQBAL (Request Buffer Address Low) 0xEB0A0000
> 0x003C: REQBAH (Request Buffer Address High) 0x00000007
> 0x0044: RESPBL (Response Buffer Length) 0x00000018
> 0x0048: RESPBAL (Response Buffer Address Low) 0xE41E1220
> 0x004C: RESPBAH (Response Buffer Address High) 0x00000007
> 0x0080: IS (Interrupt status) 0x00000000
> 0x0084: IMS (Interrupt mask set) 0x7FE00000
> 0x0088: IMC (Interrupt mask clear) 0x001F0000
> 0x008C: IG (Interrupt generator) 0x00010000
> 0x0090: ICTL (Interrupt control) 0x00000000
>
> Signed-off-by: Taku Izumi <izumi.taku@jp.fujitsu.com>
Thank you, Taku Izumi. I have merged this patch and will be pushing
it shortly.
I apologize for the delay.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2016-11-23 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 0:55 [PATCH resend] ethtool: add register dump support for fjes driver Taku Izumi
2016-11-23 14:56 ` John W. Linville [this message]
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=20161123145646.GA13179@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=izumi.taku@jp.fujitsu.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).