Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: John Harrison <john.c.harrison@intel.com>,
	Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/uc: Update to latest GuC and use new-format GuC/HuC names
Date: Fri, 16 Sep 2022 10:10:45 +0100	[thread overview]
Message-ID: <aeedcce3-ff03-b8d4-54b1-13ea7d482258@linux.intel.com> (raw)
In-Reply-To: <722b1da6-459b-dd35-8a3c-3056a75ee8a1@intel.com>


On 15/09/2022 21:03, John Harrison wrote:
> On 9/15/2022 01:59, Tvrtko Ursulin wrote:
>>
>> Hi,
>>
>> On 15/09/2022 00:46, John.C.Harrison@Intel.com wrote:
>>> From: John Harrison <John.C.Harrison@Intel.com>
>>>
>>> Going forwards, the intention is for GuC firmware files to be named
>>> for their major version only and HuC firmware files to have no version
>>> number in the name at all. This patch adds those entries for all
>>> platforms that are officially GuC/HuC enabled.
>>>
>>> Also, update the expected GuC version numbers to the latest firmware
>>> release for those platforms.
>>>
>>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 10 +++++++---
>>>   1 file changed, 7 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c 
>>> b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
>>> index 1169e2a09da24..b91ad4aede1f7 100644
>>> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
>>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
>>> @@ -72,12 +72,14 @@ void intel_uc_fw_change_status(struct intel_uc_fw 
>>> *uc_fw,
>>>    * security fixes, etc. to be enabled.
>>>    */
>>>   #define INTEL_GUC_FIRMWARE_DEFS(fw_def, guc_maj, guc_mmp) \
>>> -    fw_def(DG2,          0, guc_mmp(dg2,  70, 4, 1)) \
>>> +    fw_def(DG2,          0, guc_maj(dg2,  70, 5)) \
>>
>> Just glancing over out of curiosity. Part which confused me is that if 
>> only major is supposed to be used then what is the '5' in guc_maj(dg2, 
>> 70, 5) ?
> See the earlier patch that added support for version reduced filenames. 
> The minor number is still specified because want to be able to warn the 
> user if their firmware is out of date and causing them to miss features, 
> security fixes, etc. The driver will still load any old firmware with 
> the right name and work with it, but user's need to know that there are 
> updates available.

Got it. Release is deemed not important enough to warn about? no 
actually, it's different, I guess we never expect to bump only the 
release with a source level change - so in practice kernel could not 
warn that there is a newer release version since it would never know. In 
other words those ones would only be hitting linux-firmware, while minor 
changes would be kernel patches as well.

>> I also couldn't find guc_maj with grep so I guess it's some sort of a 
>> magic concatenation macro or what?
> 'guc_maj' is a macro parameter as per the definition of the macro three 
> lines above. According to where INTEL_GUC_FIRMWARE_DEFS is used, it 
> becomes either a mechanism for creating just a 'MODULE_FIRMWARE' 
> definition for the firmware file or a table entry giving all the version 
> information as well as the filename.

Doh thanks, macro magic was apparently impenetrable to me yesterday.

Regards,

Tvrtko

  reply	other threads:[~2022-09-16  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 23:46 [Intel-gfx] [PATCH 0/1] New GuC and new GuC/HuC names John.C.Harrison
2022-09-14 23:46 ` [Intel-gfx] [PATCH 1/1] drm/i915/uc: Update to latest GuC and use new-format " John.C.Harrison
2022-09-15  0:38   ` Ceraolo Spurio, Daniele
2022-09-15  8:59   ` Tvrtko Ursulin
2022-09-15 20:03     ` John Harrison
2022-09-16  9:10       ` Tvrtko Ursulin [this message]
2022-09-16 19:45         ` John Harrison
2022-09-15  3:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for New GuC and new " Patchwork
2022-09-15 19:54 ` [Intel-gfx] ✓ 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=aeedcce3-ff03-b8d4-54b1-13ea7d482258@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=DRI-Devel@Lists.FreeDesktop.Org \
    --cc=Intel-GFX@Lists.FreeDesktop.Org \
    --cc=john.c.harrison@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