From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/6] Improvements to uc firmare management
Date: Thu, 20 Apr 2023 18:15:19 -0700 [thread overview]
Message-ID: <20230421011525.3282664-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Enhance the firmware table verification code to catch more potential
errors and to generally improve the code itself.
Track patch level version even on reduced version files to allow user
notification of missing bug fixes.
Detect another immediate failure case when loading GuC firmware.
Treat more problems as fatal errors, at least for DEBUG builds.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (6):
drm/i915/guc: Decode another GuC load failure case
drm/i915/guc: Print status register when waiting for GuC to load
drm/i915/uc: Track patch level versions on reduced version firmware
files
drm/i915/uc: Enhancements to firmware table validation
drm/i915/uc: Reject duplicate entries in firmware table
drm/i915/uc: Make unexpected firmware versions an error in debug
builds
.../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 1 +
drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 12 +-
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 224 +++++++++++-------
3 files changed, 154 insertions(+), 83 deletions(-)
--
2.39.1
next reply other threads:[~2023-04-21 1:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 1:15 John.C.Harrison [this message]
2023-04-21 1:15 ` [Intel-gfx] [PATCH 1/6] drm/i915/guc: Decode another GuC load failure case John.C.Harrison
2023-04-21 1:15 ` [Intel-gfx] [PATCH 2/6] drm/i915/guc: Print status register when waiting for GuC to load John.C.Harrison
2023-04-21 1:15 ` [Intel-gfx] [PATCH 3/6] drm/i915/uc: Track patch level versions on reduced version firmware files John.C.Harrison
2023-04-28 23:53 ` Ceraolo Spurio, Daniele
2023-04-21 1:15 ` [Intel-gfx] [PATCH 4/6] drm/i915/uc: Enhancements to firmware table validation John.C.Harrison
2023-04-29 0:04 ` Ceraolo Spurio, Daniele
2023-04-29 0:16 ` John Harrison
2023-04-29 0:26 ` Ceraolo Spurio, Daniele
2023-04-29 0:30 ` John Harrison
2023-04-29 0:32 ` John Harrison
2023-04-29 1:21 ` Ceraolo Spurio, Daniele
2023-04-21 1:15 ` [Intel-gfx] [PATCH 5/6] drm/i915/uc: Reject duplicate entries in firmware table John.C.Harrison
2023-04-29 0:08 ` Ceraolo Spurio, Daniele
2023-04-21 1:15 ` [Intel-gfx] [PATCH 6/6] drm/i915/uc: Make unexpected firmware versions an error in debug builds John.C.Harrison
2023-04-29 0:19 ` Ceraolo Spurio, Daniele
2023-04-29 0:21 ` John Harrison
2023-04-21 2:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to uc firmare management (rev2) Patchwork
2023-04-21 2:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-21 2:43 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-21 20:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to uc firmare management (rev3) Patchwork
2023-04-21 20:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-21 21:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-25 1:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to uc firmare management (rev4) Patchwork
2023-04-25 1:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-25 1:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-25 8:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230421011525.3282664-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@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