From: Damien Lespiau <damien.lespiau@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tools Add a intel_fw_dump tool
Date: Tue, 30 Jun 2015 16:30:09 +0100 [thread overview]
Message-ID: <20150630153009.GC5180@strange.amr.corp.intel.com> (raw)
In-Reply-To: <87si992qvr.fsf@intel.com>
On Tue, Jun 30, 2015 at 05:49:12PM +0300, Jani Nikula wrote:
> On Tue, 30 Jun 2015, Damien Lespiau <damien.lespiau@intel.com> wrote:
> > So we can inspect fw headers. Sample output:
>
> Nitpick on the tool name, I'd like to make a distinction between tools
> that dump some blob from the driver/hardware/bios/whatever, and tools
> that decode those blobs. (See also the confusing naming with
> intel_bios_dumper vs. intel_bios_reader.) I'd call this
> "intel_firmware_decode".
Sure, I can't say I care much, so glad someone does.
> Another nitpick is that I'd plan on using getopt from the beginning, and
> having a -f or --file option for the input.
Well, for that one, the file is the actual thing we act on, so I
wouldn't use an option, we always need it. Options can always come later
if needed.
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-30 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:13 [PATCH i-g-t] tools Add a intel_fw_dump tool Damien Lespiau
2015-06-30 14:49 ` Jani Nikula
2015-06-30 15:30 ` Damien Lespiau [this message]
2015-06-30 15:42 ` Damien Lespiau
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=20150630153009.GC5180@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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