public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Intel-GFX@lists.freedesktop.org, DRI-Devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/mtl: Update GuC firmware version for MTL to 70.6.6
Date: Thu, 4 May 2023 13:45:24 -0700	[thread overview]
Message-ID: <0ef47947-d52e-18aa-5642-874ee2ca14c8@intel.com> (raw)
In-Reply-To: <jo3pp2ew2qsckcrn4lvrkmhfilve6gjr6vb2iiof465dhj3uus@fppfx7jwt3q3>

On 5/4/2023 13:29, Lucas De Marchi wrote:
> On Thu, May 04, 2023 at 01:22:52PM -0700, John.C.Harrison@Intel.com 
> wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> Also switch to using reduced version file naming as it is no longer
>> such a work-in-progress and likely to change.
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>
>
> commit message here will be bogus as it will be the first time MTL will
> actually have the define.
Oh. Because the current line is coming from the for-CI branch and is not 
actually upstream already. Yeah, forgot that!

>
> Better to do it like this:
>
>     git revert 5c71b8b8ac87
>     then this patch, with a better commit message
>
> or I can change the commit message of this commit while applying to:
>
>     drm/i915/mtl: Define GuC firmware version for MTL
>
>     First release of GuC for Meteorlake.
>
>     Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>     Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> Lucas De Marchi
That works for me :).

>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> 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 55e50bd08d7ff..10e48cbcf494a 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
>> @@ -79,7 +79,7 @@ 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(METEORLAKE,   0, guc_mmp(mtl,  70, 6, 5)) \
>> +    fw_def(METEORLAKE,   0, guc_maj(mtl,  70, 6, 6)) \
>>     fw_def(DG2,          0, guc_maj(dg2,  70, 5, 1)) \
>>     fw_def(ALDERLAKE_P,  0, guc_maj(adlp, 70, 5, 1)) \
>>     fw_def(ALDERLAKE_P,  0, guc_mmp(adlp, 70, 1, 1)) \
>> -- 
>> 2.39.1
>>


  reply	other threads:[~2023-05-04 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 20:22 [Intel-gfx] [PATCH 0/2] Update MTL GuC firmware John.C.Harrison
2023-05-04 20:22 ` [Intel-gfx] [PATCH 1/2] drm/i915/uc: Track patch level versions on reduced version firmware files John.C.Harrison
2023-05-04 20:22 ` [Intel-gfx] [PATCH 2/2] drm/i915/mtl: Update GuC firmware version for MTL to 70.6.6 John.C.Harrison
2023-05-04 20:29   ` Lucas De Marchi
2023-05-04 20:45     ` John Harrison [this message]
2023-05-05 18:10       ` Lucas De Marchi
2023-05-04 23:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update MTL GuC firmware Patchwork
2023-05-04 23:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=0ef47947-d52e-18aa-5642-874ee2ca14c8@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=DRI-Devel@lists.freedesktop.org \
    --cc=Intel-GFX@lists.freedesktop.org \
    --cc=lucas.demarchi@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