From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH 3/3] drm/xe/guc: Add support for LNL firmware
Date: Thu, 1 Feb 2024 23:30:50 -0800 [thread overview]
Message-ID: <20240202073050.1986142-4-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20240202073050.1986142-1-John.C.Harrison@Intel.com>
From: John Harrison <John.C.Harrison@Intel.com>
First release of GuC firmware for LNL is now available, so start
using it.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
---
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 d896c98dd0bb..9814c5d8538d 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -103,6 +103,7 @@ struct fw_blobs_by_type {
};
#define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver) \
+ fw_def(LUNARLAKE, major_ver(i915, guc, lnl, 70, 19, 2)) \
fw_def(METEORLAKE, major_ver(i915, guc, mtl, 70, 19, 2)) \
fw_def(DG2, major_ver(i915, guc, dg2, 70, 19, 2)) \
fw_def(DG1, major_ver(i915, guc, dg1, 70, 19, 2)) \
--
2.43.0
next prev parent reply other threads:[~2024-02-02 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 7:30 [PATCH 0/3] Update to GuC 70.19.2 and add LNL John.C.Harrison
2024-02-02 7:30 ` [PATCH 1/3] drm/xe/uc: Include patch version in expectations John.C.Harrison
2024-02-02 16:48 ` Lucas De Marchi
2024-02-02 7:30 ` [PATCH 2/3] drm/xe/guc: Update to GuC firmware 70.19.2 John.C.Harrison
2024-02-02 16:56 ` Lucas De Marchi
2024-02-02 20:00 ` John Harrison
2024-02-02 7:30 ` John.C.Harrison [this message]
2024-02-02 17:00 ` [PATCH 3/3] drm/xe/guc: Add support for LNL firmware Lucas De Marchi
2024-02-02 7:36 ` ✗ CI.Patch_applied: failure for Update to GuC 70.19.2 and add LNL Patchwork
2024-02-02 16:53 ` [PATCH 0/3] " Lucas De Marchi
2024-02-02 18:51 ` John Harrison
2024-02-02 19:35 ` Lucas De Marchi
2024-02-02 19:53 ` John Harrison
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=20240202073050.1986142-4-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
/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