Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [topic/xe-for-ci] drm/xe/ptl: Update GuC version for PTL
Date: Tue, 21 Jan 2025 14:08:00 -0800	[thread overview]
Message-ID: <e5c9b15f-b465-4c1a-b99c-39f98136fd4f@intel.com> (raw)
In-Reply-To: <349ff52f-94d2-4e14-b0cc-2847312877cb@intel.com>




On 1/17/2025 1:21 PM, Daniele Ceraolo Spurio wrote:
>
>
>
> On 1/16/2025 10:31 AM, Vinay Belgaumkar wrote:
>> Move to GuC 70.38.1.
>>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> Daniele

Pushed to the xe-for-CI branch (squashed into the original FW definition 
patch).

Daniele

>
>> ---
>>   drivers/gpu/drm/xe/xe_uc_fw.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c 
>> b/drivers/gpu/drm/xe/xe_uc_fw.c
>> index 9c14b0adad0c..18e06ee9e23f 100644
>> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
>> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
>> @@ -107,7 +107,7 @@ struct fw_blobs_by_type {
>>   };
>>     #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, 
>> major_ver)            \
>> -    fw_def(PANTHERLAKE,    mmp_ver(xe,    guc,    ptl,    70, 36, 
>> 0))    \
>> +    fw_def(PANTHERLAKE,    mmp_ver(xe,    guc,    ptl,    70, 38, 
>> 1))    \
>>       fw_def(BATTLEMAGE,    major_ver(xe,    guc,    bmg,    70, 29, 
>> 2))    \
>>       fw_def(LUNARLAKE,    major_ver(xe,    guc,    lnl,    70, 29, 
>> 2))    \
>>       fw_def(METEORLAKE,    major_ver(i915,    guc,    mtl, 70, 29, 
>> 2))    \
>


      reply	other threads:[~2025-01-21 22:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 18:31 [topic/xe-for-ci] drm/xe/ptl: Update GuC version for PTL Vinay Belgaumkar
2025-01-16 23:50 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-16 23:51 ` ✓ CI.checkpatch: " Patchwork
2025-01-16 23:52 ` ✓ CI.KUnit: " Patchwork
2025-01-17  0:10 ` ✓ CI.Build: " Patchwork
2025-01-17  0:12 ` ✓ CI.Hooks: " Patchwork
2025-01-17  0:14 ` ✓ CI.checksparse: " Patchwork
2025-01-17  0:39 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-17  5:00 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-17 21:21 ` [topic/xe-for-ci] " Daniele Ceraolo Spurio
2025-01-21 22:08   ` Daniele Ceraolo Spurio [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=e5c9b15f-b465-4c1a-b99c-39f98136fd4f@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=vinay.belgaumkar@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