From: Ben Hutchings <bhutchings@solarflare.com>
To: Ajit.Khaparde@Emulex.Com
Cc: anirban.chakraborty@qlogic.com, netdev@vger.kernel.org,
--no-chain-reply-to@mv.qlogic.com, davem@davemloft.net
Subject: RE: [ethtool PATCH] FW dump support
Date: Wed, 04 May 2011 19:25:22 +0100 [thread overview]
Message-ID: <1304533522.2926.58.camel@bwh-desktop> (raw)
In-Reply-To: <49395329523DD64492581B505F80C86D5A5BCD3990@EXMAIL.ad.emulex.com>
On Wed, 2011-05-04 at 11:15 -0700, Ajit.Khaparde@Emulex.Com wrote:
> ________________________________________
> From: netdev-owner@vger.kernel.org [netdev-owner@vger.kernel.org] On Behalf Of Ben Hutchings [bhutchings@solarflare.com]
> Sent: Wednesday, May 04, 2011 12:40 PM
> To: anirban.chakraborty@qlogic.com
> Cc: netdev@vger.kernel.org; --no-chain-reply-to@mv.qlogic.com; davem@davemloft.net
> Subject: Re: [ethtool PATCH] FW dump support
>
> > On Mon, 2011-05-02 at 16:29 -0700, anirban.chakraborty@qlogic.com wrote:
> >> From: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
> >>
> >> Added support to take FW dump via ethtool.
> > [...]
> >> --- a/ethtool.c
> >> +++ b/ethtool.c
> > [...]
> >> @@ -263,6 +270,12 @@ static struct option {
> >> "Get Rx ntuple filters and actions\n" },
> >> { "-P", "--show-permaddr", MODE_PERMADDR,
> >> "Show permanent hardware address" },
> >> + { "-W", "--get-dump", MODE_GET_DUMP,
> >> + "Get dump level\n" },
> >> + { "-Wd", "--get-dump-data", MODE_GET_DUMP_DATA,
> >> + "Get dump data", "FILENAME " "Name of the dump file\n" },
> >
> > The short options should only include one letter. Also the general
> > pattern is that 'get' options use lower-case letters and 'set' options
> > use upper-case letters. No, I'm not sure how best to handle a set of 3
> > options. Maybe you can combine --get-dump and --get-dump-data, making
> > the filename optional?
>
> ethtool already has "-f" option to flash/write the FW image.
> Can you use "-F" to get the FW dump data out?
> And then may be, these options can be extended to get the get/set dump levels?
Although '-F' would be nicely mnemonic, firmware update and dump are
different enough that I don't think they make sense as a pair. If a
driver implements both then there is the risk of a typo causing the
firmware image file to be overwritten with a firmware dump. I also
don't think it's possible to extend the '-f' option without breaking
compatibility with scripts that already use it.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-05-04 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 23:29 [ethtool PATCH] FW dump support anirban.chakraborty
2011-05-02 23:29 ` [net-next-2.6 PATCH] ethtool: Support to take FW dump anirban.chakraborty
2011-05-03 23:53 ` Ben Hutchings
2011-05-04 0:29 ` Anirban Chakraborty
2011-05-04 1:06 ` Ben Hutchings
2011-05-04 5:22 ` Anirban Chakraborty
2011-05-04 17:40 ` [ethtool PATCH] FW dump support Ben Hutchings
2011-05-04 18:02 ` Anirban Chakraborty
2011-05-04 18:07 ` Ben Hutchings
2011-05-04 18:15 ` Ajit.Khaparde
2011-05-04 18:25 ` Ben Hutchings [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=1304533522.2926.58.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=--no-chain-reply-to@mv.qlogic.com \
--cc=Ajit.Khaparde@Emulex.Com \
--cc=anirban.chakraborty@qlogic.com \
--cc=davem@davemloft.net \
--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).