From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-Xe@Lists.FreeDesktop.Org>
Cc: Julia Filipchuk <julia.filipchuk@intel.com>
Subject: Re: [PATCH v4 4/4] drm/xe/guc: Pre-release GuC firmware v70.29.2 for PVC
Date: Fri, 2 Aug 2024 15:42:23 -0700 [thread overview]
Message-ID: <af410932-3c56-4a5c-b913-da3d90ac5548@intel.com> (raw)
In-Reply-To: <20240802222129.3976212-5-John.C.Harrison@Intel.com>
On 8/2/2024 3:21 PM, John.C.Harrison@Intel.com wrote:
> From: Julia Filipchuk <julia.filipchuk@intel.com>
>
> Add pre-release support for PVC.
>
> UAPI version 1.13.4.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com>
For the CI branch:
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/xe/xe_uc_fw.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 4bb2a4a80ddc..41c4ac6ba42a 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -109,6 +109,7 @@ struct fw_blobs_by_type {
> 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)) \
> + fw_def(PVC, mmp_ver(intel-ci/xe, guc, pvc, 70, 29, 2)) \
> fw_def(DG2, major_ver(i915, guc, dg2, 70, 29, 2)) \
> fw_def(DG1, major_ver(i915, guc, dg1, 70, 29, 2)) \
> fw_def(ALDERLAKE_N, major_ver(i915, guc, tgl, 70, 29, 2)) \
next prev parent reply other threads:[~2024-08-02 22:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 22:21 [PATCH v4 0/4] Update to GuC v70.29.2 as minimum for Xe (support LNL, BMG) John.C.Harrison
2024-08-02 22:21 ` [PATCH v4 1/4] Revert "drm/xe/guc: Pre-release GuC firmware v70.24.0 for LNL/BMG/PVC" John.C.Harrison
2024-08-02 22:43 ` Daniele Ceraolo Spurio
2024-08-02 22:21 ` [PATCH v4 2/4] drm/xe/guc: Bump minimum required GuC version to v70.29.2 John.C.Harrison
2024-08-02 22:41 ` Daniele Ceraolo Spurio
2024-08-02 22:21 ` [PATCH v4 3/4] drm/xe/guc: Define GuC version v70.29.2 for BMG John.C.Harrison
2024-08-02 22:21 ` [PATCH v4 4/4] drm/xe/guc: Pre-release GuC firmware v70.29.2 for PVC John.C.Harrison
2024-08-02 22:42 ` Daniele Ceraolo Spurio [this message]
2024-08-02 22:26 ` ✓ CI.Patch_applied: success for Update to GuC v70.29.2 as minimum for Xe (support LNL, BMG) Patchwork
2024-08-02 22:27 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-02 22:28 ` ✓ CI.KUnit: success " Patchwork
2024-08-02 22:39 ` ✓ CI.Build: " Patchwork
2024-08-02 22:42 ` ✓ CI.Hooks: " Patchwork
2024-08-02 22:43 ` ✓ CI.checksparse: " Patchwork
2024-08-02 23:05 ` ✗ CI.BAT: failure " Patchwork
2024-08-03 0:12 ` ✗ CI.FULL: " Patchwork
2024-08-05 17:49 ` ✓ CI.Patch_applied: success for Update to GuC v70.29.2 as minimum for Xe (support LNL, BMG) (rev2) Patchwork
2024-08-05 17:49 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-05 17:50 ` ✓ CI.KUnit: success " Patchwork
2024-08-05 18:02 ` ✓ CI.Build: " Patchwork
2024-08-05 18:04 ` ✓ CI.Hooks: " Patchwork
2024-08-05 18:06 ` ✓ CI.checksparse: " Patchwork
2024-08-05 18:26 ` ✓ CI.BAT: " Patchwork
2024-08-05 20:24 ` ✗ 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=af410932-3c56-4a5c-b913-da3d90ac5548@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@Intel.com \
--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