From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"Filipchuk, Julia" <julia.filipchuk@intel.com>
Subject: Re: [PATCH v2 0/2] Enable GSC loading and PXP for NVL-P
Date: Tue, 22 Sep 2026 23:26:48 +0000 [thread overview]
Message-ID: <5bd962a7def2a460aec77c08756ab22f77f40314.camel@intel.com> (raw)
In-Reply-To: <20260922181232.1111750-4-alan.previn.teres.alexis@intel.com>
Please ignore this series. Apologies for the interrupt.
I need to follow up if we are able to enable both NVL-S and NVL-P with the same firmware or just NVL-S first.
...alan
On Tue, 2026-09-22 at 11:12 -0700, Alan Previn wrote:
> GSC firmware is required for content protection features (PXP, HDCP).
> This series adds this support.
>
> history:
> v2: Fix ordering of NVL-GSC-FW in XE_GSC_FIRMWARE_DEFS (Shasiko-bot)
>
> Alan Previn (2):
> drm/xe/gsc: Define GSC for NVL-P
> drm/xe/nvl-p: Enable PXP for NVL-P
>
> drivers/gpu/drm/xe/xe_pci.c | 1 +
> drivers/gpu/drm/xe/xe_uc_fw.c | 1 +
> 2 files changed, 2 insertions(+)
>
>
> base-commit: ff831af91674990f9f1814340860e96943d5df1a
next prev parent reply other threads:[~2026-09-22 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:12 [PATCH v2 0/2] Enable GSC loading and PXP for NVL-P Alan Previn
2026-09-22 18:12 ` [PATCH v2 1/2] drm/xe/gsc: Define GSC " Alan Previn
2026-09-22 18:12 ` [PATCH v2 2/2] drm/xe/nvl-p: Enable PXP " Alan Previn
2026-09-22 19:43 ` ✓ CI.KUnit: success for Enable GSC loading and PXP for NVL-P (rev2) Patchwork
2026-09-22 21:53 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-09-22 23:26 ` Teres Alexis, Alan Previn [this message]
2026-09-23 9:43 ` ✗ Xe.CI.FULL: " 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=5bd962a7def2a460aec77c08756ab22f77f40314.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@intel.com \
--cc=rodrigo.vivi@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