From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Julia Filipchuk <julia.filipchuk@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v2 0/7] drm/xe/guc: Recommend GuC v70.60.0 for LNL, BMG, PTL
Date: Fri, 17 Apr 2026 14:39:01 -0400 [thread overview]
Message-ID: <aeJ-RTBuAU_yUkVk@intel.com> (raw)
In-Reply-To: <20260406211759.817577-9-julia.filipchuk@intel.com>
On Mon, Apr 06, 2026 at 02:17:24PM -0700, Julia Filipchuk wrote:
> Recommend newer GuC firmware for LNL, BMG, PTL. UAPI version: 1.31.0
>
> Update NVL-S, CRI to used matching GuC version v70.60.0 (Only applies
> to xe-for-ci topic branch).
>
> Platforms NVL-S, CRI, NVL-P are not merged to upstream at present. The
> GuC definitions for those only exist in the for-ci topic branches
> drm-xe:topic/xe-for-ci and drm-intel:topic/core-for-ci. This patch set
> reverts those patches, updates the recommended GuC versions for fully
> upstream platforms, then re-adds the CI only platforms definitions.
>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> v2: Added RB for main patch. (Daniele)
> Update xe-for-ci platforms NVL-S, CRI to use v60 as well.
>
> Julia INTEL (7):
> Revert "drm/xe/nvlp: Define GuC firmware for NVL-P"
> Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI"
> Revert "drm/xe/nvls: Define GuC firmware for NVL-S"
Let's not revert what is already upstream. For this we need a branch new patch.
> drm/xe/guc: Recommend GuC v70.60.0 for BMG, LNL, PTL
> Reapply "drm/xe/nvls: Define GuC firmware for NVL-S"
> Reapply "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI"
> Reapply "drm/xe/nvlp: Define GuC firmware for NVL-P"
And for the other 2 that gets replaced in the topic branch, let's avoid
adding yet another prefix on those.
>
> drivers/gpu/drm/xe/xe_uc_fw.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> --
> 2.51.0
>
prev parent reply other threads:[~2026-04-17 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 21:17 [PATCH v2 0/7] drm/xe/guc: Recommend GuC v70.60.0 for LNL, BMG, PTL Julia Filipchuk
2026-04-06 21:17 ` [PATCH v2 1/7] Revert "drm/xe/nvlp: Define GuC firmware for NVL-P" Julia Filipchuk
2026-04-06 21:17 ` [PATCH v2 2/7] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-04-06 21:17 ` [PATCH v2 3/7] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-04-06 21:17 ` [PATCH v2 4/7] drm/xe/guc: Recommend GuC v70.60.0 for BMG, LNL, PTL Julia Filipchuk
2026-04-06 21:17 ` [PATCH v2 5/7] Reapply "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-04-10 20:24 ` Daniele Ceraolo Spurio
2026-04-06 21:17 ` [PATCH v2 6/7] Reapply "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-04-10 20:24 ` Daniele Ceraolo Spurio
2026-04-06 21:17 ` [PATCH v2 7/7] Reapply "drm/xe/nvlp: Define GuC firmware for NVL-P" Julia Filipchuk
2026-04-06 21:24 ` ✗ CI.checkpatch: warning for drm/xe/guc: Recommend GuC v70.60.0 for LNL, BMG, PTL (rev2) Patchwork
2026-04-06 21:25 ` ✓ CI.KUnit: success " Patchwork
2026-04-06 22:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-07 1:55 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-17 18:39 ` Rodrigo Vivi [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=aeJ-RTBuAU_yUkVk@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@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