From: Josh Boyer <jwboyer@kernel.org>
To: John.C.Harrison@intel.com
Cc: linux-firmware@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.20.0 binaries
Date: Mon, 19 Feb 2024 07:45:09 -0500 [thread overview]
Message-ID: <CA+5PVA4HNHBpR_5LBi8KbE3artRf6WZUMFXTR_myiDhm58YXkA@mail.gmail.com> (raw)
In-Reply-To: <20240216211432.519411-1-John.C.Harrison@Intel.com>
On Fri, Feb 16, 2024 at 4:16 PM <John.C.Harrison@intel.com> wrote:
>
> The following changes since commit fbef4d381e3d0143427e1a8c924be8e738c0fc2d:
>
> Merge branch 'main' into 'main' (2024-02-08 12:24:01 +0000)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-firmware guc_70.20.0
Merged and pushed out.
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/156
josh
>
> for you to fetch changes up to 28c2472d37d089edb56c75e3af83511babaa756c:
>
> xe: First GuC release for LNL and Xe (2024-02-14 16:28:32 -0800)
>
> ----------------------------------------------------------------
> John Harrison (2):
> i915: Add GuC v70.20.0 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 -> 347584 bytes
> i915/dg1_guc_70.bin | Bin 272512 -> 321472 bytes
> i915/dg2_guc_70.bin | Bin 443200 -> 410368 bytes
> i915/mtl_guc_70.bin | Bin 365376 -> 332544 bytes
> i915/tgl_guc_70.bin | Bin 330304 -> 335168 bytes
> xe/lnl_guc_70.bin | Bin 0 -> 336640 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-19 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 21:14 PR for new GuC v70.20.0 binaries John.C.Harrison
2024-02-19 12:45 ` Josh Boyer [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=CA+5PVA4HNHBpR_5LBi8KbE3artRf6WZUMFXTR_myiDhm58YXkA@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=John.C.Harrison@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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).