From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/xe: Drop pre-release GuC definitions for LNL and BMG
Date: Fri, 26 Jul 2024 08:11:21 -0700 [thread overview]
Message-ID: <f97bb25e-31f2-4cf7-928e-52451a4ce96c@intel.com> (raw)
In-Reply-To: <wzitchh3yzru3hbx4rewwmhdicp6n4uwxz6wrocj5tdnotxig3@l22weesvtnwf>
On 7/26/2024 6:57 AM, Lucas De Marchi wrote:
> On Thu, Jul 25, 2024 at 06:26:08PM GMT, Daniele Ceraolo Spurio wrote:
>> Now that we have the binaries ready to go to linux-firmware, we can
>> remove the pre-release definitions as a prep step to add the final
>> defines in drm-xe-next.
>>
>> Note that this patch is meant to be squashed with the patch in
>> xe-for-CI that adds the definitions
>> ("drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC"). We
>> can't just drop that patch because we want to keep the PVC FW def.
>>
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> while applying it, can you reword the commit message so the remaining
> commit is just about PVC?
Sure. I was already planning to do that, I should've probably made it
clearer in the commit message.
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Thanks!
Daniele
>
> thanks
> Lucas De Marchi
>
>> ---
>> drivers/gpu/drm/xe/xe_uc_fw.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c
>> b/drivers/gpu/drm/xe/xe_uc_fw.c
>> index 6b92255a769d..c0ff44e0b0ea 100644
>> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
>> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
>> @@ -105,8 +105,7 @@ struct fw_blobs_by_type {
>> };
>>
>> #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver) \
>> - fw_def(BATTLEMAGE, major_ver(intel-ci/xe, guc, bmg, 70,
>> 24, 0)) \
>> - fw_def(LUNARLAKE, major_ver(intel-ci/xe, guc, lnl, 70,
>> 24, 0)) \
>> + fw_def(LUNARLAKE, major_ver(xe, guc, lnl, 70, 19,
>> 2)) \
>> fw_def(METEORLAKE, major_ver(i915, guc, mtl, 70, 19,
>> 2)) \
>> fw_def(PVC, mmp_ver(intel-ci/xe, guc, pvc, 70, 24,
>> 0)) \
>> fw_def(DG2, major_ver(i915, guc, dg2, 70, 19,
>> 2)) \
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2024-07-26 15:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 1:26 [PATCH 0/3] Move GuC FW defs for LNL and BMG to drm-xe-next Daniele Ceraolo Spurio
2024-07-26 1:26 ` [PATCH 1/3] drm/xe: Drop pre-release GuC definitions for LNL and BMG Daniele Ceraolo Spurio
2024-07-26 13:57 ` Lucas De Marchi
2024-07-26 15:11 ` Daniele Ceraolo Spurio [this message]
2024-07-26 1:26 ` [PATCH 2/3] drm/xe/guc: Bump LNL GuC recommended version to 70.29.1 Daniele Ceraolo Spurio
2024-07-26 13:55 ` Lucas De Marchi
2024-07-26 1:26 ` [PATCH 3/3] drm/xe/guc: Add BMG GuC definition Daniele Ceraolo Spurio
2024-07-26 13:56 ` Lucas De Marchi
2024-07-26 1:31 ` ✓ CI.Patch_applied: success for Move GuC FW defs for LNL and BMG to drm-xe-next Patchwork
2024-07-26 1:32 ` ✓ CI.checkpatch: " Patchwork
2024-07-26 1:33 ` ✓ CI.KUnit: " Patchwork
2024-07-26 1:45 ` ✓ CI.Build: " Patchwork
2024-07-26 1:47 ` ✓ CI.Hooks: " Patchwork
2024-07-26 1:48 ` ✓ CI.checksparse: " Patchwork
2024-07-26 2:09 ` ✓ CI.BAT: " Patchwork
2024-07-26 11:59 ` ✗ CI.FULL: failure " Patchwork
2024-07-26 15:15 ` ✓ CI.Patch_applied: success for Move GuC FW defs for LNL and BMG to drm-xe-next (rev2) Patchwork
2024-07-26 15:15 ` ✓ CI.checkpatch: " Patchwork
2024-07-26 15:16 ` ✓ CI.KUnit: " Patchwork
2024-07-26 15:28 ` ✓ CI.Build: " Patchwork
2024-07-26 15:30 ` ✓ CI.Hooks: " Patchwork
2024-07-26 15:32 ` ✓ CI.checksparse: " Patchwork
2024-07-26 15:52 ` ✓ CI.BAT: " Patchwork
2024-07-27 3:26 ` ✗ CI.FULL: 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=f97bb25e-31f2-4cf7-928e-52451a4ce96c@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-xe@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