From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/uc: Update drawing for firmware layout
Date: Wed, 24 Jul 2019 13:11:23 -0700 [thread overview]
Message-ID: <bb6e105d-5bb9-01b8-bbd7-dd6d406fbca7@intel.com> (raw)
In-Reply-To: <op.z5f7l3szxaggs7@mwajdecz-mobl1.ger.corp.intel.com>
On 7/24/19 1:09 PM, Michal Wajdeczko wrote:
> On Wed, 24 Jul 2019 19:44:46 +0200, Daniele Ceraolo Spurio
> <daniele.ceraolospurio@intel.com> wrote:
>
>>
>>
>> On 7/24/19 10:34 AM, Michal Wajdeczko wrote:
>>> Sphinx was rendering firmware layout as html table, but since
>>> we want to add sizes relations switch to plain text graphics.
>>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h | 25 +++++++++-----------
>>> 1 file changed, 11 insertions(+), 14 deletions(-)
>>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h
>>> b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h
>>> index 3ca535534151..e25271aac765 100644
>>> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h
>>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h
>>> @@ -11,21 +11,18 @@
>>> /**
>>> * DOC: GuC Firmware Layout
>>> *
>>> - * The GuC firmware layout looks like this:
>>> + * The GuC firmware layout looks like this::
>>> *
>>> - * +-------------------------------+
>>> - * | uc_css_header |
>>> - * | |
>>> - * | contains major/minor version |
>>> - * +-------------------------------+
>>> - * | uCode |
>>> - * +-------------------------------+
>>> - * | RSA signature |
>>> - * +-------------------------------+
>>> - * | modulus key |
>>> - * +-------------------------------+
>>> - * | exponent val |
>>> - * +-------------------------------+
>>> + *
>>> +======================================================================+
>>> + * | Firmware
>>> blob |
>>> + *
>>> +===============+===============+============+============+============+
>>> + * | CSS header | uCode | key | modulus |
>>> exponent |
>>> + *
>>> +===============+===============+============+============+============+
>>
>> What about the RSA?
>
> key == RSA key == RSA signature
>
> I followed notation from our header definition which uses "key_size"
> but maybe it was too brave. What about "RSA key" to have a match ?
>
Works for me.
Daniele
>>
>> Daniele
>>
>>> + * <-header size-> <---header size continued
>>> ----------->
>>> + * <--- size
>>> ----------------------------------------------------------->
>>> + * <-key size->
>>> + * <-mod size->
>>> + *
>>> <-exp size->
>>> *
>>> * The firmware may or may not have modulus key and exponent data.
>>> The header,
>>> * uCode and RSA signature are must-have components that will be
>>> used by driver.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-24 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 17:34 [PATCH 1/3] drm/i915: Fix GuC documentation links Michal Wajdeczko
2019-07-24 17:34 ` [PATCH 2/3] drm/i915/uc: Move uc firmware layout definitions to dedicated file Michal Wajdeczko
2019-07-24 17:50 ` Daniele Ceraolo Spurio
2019-07-24 20:01 ` Michal Wajdeczko
2019-07-24 20:05 ` Daniele Ceraolo Spurio
2019-07-24 17:34 ` [PATCH 3/3] drm/i915/uc: Update drawing for firmware layout Michal Wajdeczko
2019-07-24 17:44 ` Daniele Ceraolo Spurio
2019-07-24 20:09 ` Michal Wajdeczko
2019-07-24 20:11 ` Daniele Ceraolo Spurio [this message]
2019-07-24 17:43 ` [PATCH 1/3] drm/i915: Fix GuC documentation links Daniele Ceraolo Spurio
2019-07-24 17:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] " Patchwork
2019-07-24 19:49 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-24 21:56 ` ✓ Fi.CI.IGT: " Patchwork
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=bb6e105d-5bb9-01b8-bbd7-dd6d406fbca7@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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