From: John Harrison <john.c.harrison@intel.com>
To: <linux-firmware@kernel.org>
Cc: <jwboyer@kernel.org>, <kyle@kernel.org>, <ben@decadent.org.uk>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: PR for new GuC v70.19.2
Date: Wed, 14 Feb 2024 15:46:04 -0800 [thread overview]
Message-ID: <f7dda4d9-3953-4574-ba48-8d731e806d1e@intel.com> (raw)
In-Reply-To: <20240202011249.1965081-1-John.C.Harrison@Intel.com>
Hello,
Please disregard this pull request if hasn't already been processed.
We need to send out an update to bump to a newer version.
Thanks,
John.
On 2/1/2024 17:12, John.C.Harrison@Intel.com wrote:
> The following changes since commit 1a9518c73c4b54854c9cd8f416fd3b8f8e3456e7:
>
> Merge branch 'mlimonci/amd-2024-01-30.2' into 'main' (2024-01-30 15:55:30 +0000)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-firmware guc_70.19.2
>
> for you to fetch changes up to 92c06b3c1b4b93ccd9953825cfd4e6ab56e03f16:
>
> xe: First GuC release for LNL and Xe (2024-01-30 09:23:50 -0800)
>
> ----------------------------------------------------------------
> John Harrison (2):
> i915: Add GuC v70.19.2 for ADL-P, DG1, DG2, MTL and TGL
> xe: First GuC release for LNL and Xe
>
> LICENSE.xe | 39 +++++++++++++++++++++++++++++++++++++++
> WHENCE | 20 ++++++++++++++------
> i915/adlp_guc_70.bin | Bin 342848 -> 347264 bytes
> i915/dg1_guc_70.bin | Bin 272512 -> 321088 bytes
> i915/dg2_guc_70.bin | Bin 443200 -> 406336 bytes
> i915/mtl_guc_70.bin | Bin 365376 -> 332608 bytes
> i915/tgl_guc_70.bin | Bin 330304 -> 334784 bytes
> xe/lnl_guc_70.bin | Bin 0 -> 336704 bytes
> 8 files changed, 53 insertions(+), 6 deletions(-)
> create mode 100644 LICENSE.xe
> create mode 100644 xe/lnl_guc_70.bin
prev parent reply other threads:[~2024-02-14 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 1:12 PR for new GuC v70.19.2 John.C.Harrison
2024-02-14 23:46 ` John Harrison [this message]
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=f7dda4d9-3953-4574-ba48-8d731e806d1e@intel.com \
--to=john.c.harrison@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jwboyer@kernel.org \
--cc=kyle@kernel.org \
--cc=linux-firmware@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).