From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v2 0/7] Support different GuCs per GT
Date: Mon, 3 Mar 2025 11:52:08 -0800 [thread overview]
Message-ID: <20250303195215.1046192-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Add support for loading a different GuC firmware image on each GT.
v2: Split and add reverts/re-applies to cope with some patches being
in the for-ci topic branch.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Clint Taylor (1):
drm/xe/ptl: Add GuC firmware definition
Daniele Ceraolo Spurio (1):
drm/xe/ptl: Define HuC FW version for PTL
John Harrison (4):
Revert "drm/xe/ptl: Define HuC FW version for PTL"
Revert "drm/xe/ptl: Add GuC firmware definition"
Revert "drm/xe/pvc: Add GuC firmware definition"
drm/xe/uc: Add support for different firmware files on each GT
Julia Filipchuk (1):
drm/xe/pvc: Add GuC firmware definition
drivers/gpu/drm/xe/xe_uc_fw.c | 73 +++++++++++++++++++++--------------
1 file changed, 43 insertions(+), 30 deletions(-)
--
2.47.0
next reply other threads:[~2025-03-03 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 19:52 John.C.Harrison [this message]
2025-03-03 19:52 ` [PATCH v2 1/7] Revert "drm/xe/ptl: Define HuC FW version for PTL" John.C.Harrison
2025-03-03 19:52 ` [PATCH v2 2/7] Revert "drm/xe/ptl: Add GuC firmware definition" John.C.Harrison
2025-03-03 19:52 ` [PATCH v2 3/7] Revert "drm/xe/pvc: " John.C.Harrison
2025-03-03 19:52 ` [PATCH v2 4/7] drm/xe/uc: Add support for different firmware files on each GT John.C.Harrison
2025-03-06 2:09 ` Lucas De Marchi
2025-03-03 19:52 ` [PATCH v2 5/7] drm/xe/pvc: Add GuC firmware definition John.C.Harrison
2025-03-03 19:52 ` [PATCH v2 6/7] drm/xe/ptl: " John.C.Harrison
2025-03-03 19:52 ` [PATCH v2 7/7] drm/xe/ptl: Define HuC FW version for PTL John.C.Harrison
2025-03-03 20:19 ` ✓ CI.Patch_applied: success for Support different GuCs per GT Patchwork
2025-03-03 20:19 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-03 20:20 ` ✓ CI.KUnit: success " Patchwork
2025-03-03 20:37 ` ✓ CI.Build: " Patchwork
2025-03-03 20:39 ` ✓ CI.Hooks: " Patchwork
2025-03-03 20:41 ` ✓ CI.checksparse: " Patchwork
2025-03-03 20:51 ` [PATCH v2 0/7] " Cavitt, Jonathan
2025-03-03 21:00 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-03 23:46 ` ✗ Xe.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=20250303195215.1046192-1-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