From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-xe] [PATCH i-g-t v2] tools: Add tool to dump GuC/HuC CSS header
Date: Tue, 11 Apr 2023 09:19:06 -0700 [thread overview]
Message-ID: <168122983958.3152898.432397312184705707.b4-ty@intel.com> (raw)
In-Reply-To: <20230404170737.1856619-1-lucas.demarchi@intel.com>
On Tue, 04 Apr 2023 10:07:37 -0700, Lucas De Marchi wrote:
> Since we are now using unversioned GuC/HuC, it's useful to be able to
> dump the firmware blob and get that information from the CSS header.
> Add a tool that decodes that information and dumps the raw header.
>
> Example output:
>
> $ tools/intel-gfx-fw-info /lib/firmware/i915/tgl_guc_70.bin
> version: 70.5.1
> date: 2022-09-09
> raw dump:
> 00000000 06 00 00 00 a1 00 00 00 00 00 01 00 00 00 00 00 ................
> 00000010 86 80 00 00 09 09 22 20 71 17 01 00 40 00 00 00 ......" q...@...
> 00000020 40 00 00 00 01 00 00 00 09 21 45 00 73 79 73 5f @........!E.sys_
> 00000030 67 62 73 62 50 43 2d 31 2e 30 2e 33 31 35 30 00 gbsbPC-1.0.3150.
> 00000040 01 05 46 00 00 00 00 00 00 00 00 00 00 00 00 00 ..F.............
> 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00000070 00 00 00 00 00 00 00 00 00 10 80 00 00 01 40 00 ..............@.
>
> [...]
Applied, thanks for the reviews.
[1/1] tools: Add tool to dump GuC/HuC CSS header
commit: 2da179d399d83a6859a89176d83b7ec1d71fe27a
Best regards,
--
Lucas De Marchi <lucas.demarchi@intel.com>
prev parent reply other threads:[~2023-04-11 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 17:07 [igt-dev] [PATCH i-g-t v2] tools: Add tool to dump GuC/HuC CSS header Lucas De Marchi
2023-04-04 18:15 ` [igt-dev] ✗ Fi.CI.BAT: failure for tools: Add tool to dump GuC/HuC CSS header (rev2) Patchwork
2023-04-11 16:19 ` Lucas De Marchi [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=168122983958.3152898.432397312184705707.b4-ty@intel.com \
--to=lucas.demarchi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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