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
Subject: Re: PR for new GuC v70.5.1 and GuC/HuC with new names
Date: Mon, 26 Sep 2022 10:30:27 -0400 [thread overview]
Message-ID: <CA+5PVA7inRVU=ux3cC9bvu3aOWydGLBQDbfCFoGUhAqfxPQG3g@mail.gmail.com> (raw)
In-Reply-To: <20220920204119.3514792-1-John.C.Harrison@Intel.com>
Pulled and pushed out.
josh
On Tue, Sep 20, 2022 at 4:40 PM <John.C.Harrison@intel.com> wrote:
>
> The following changes since commit f09bebf31b0590bdc875d7236aa705279510cfd0:
>
> amdgpu: update yellow carp DMCUB firmware (2022-09-13 08:02:23 -0400)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-firmware guc_70.5.1_huc_nover
>
> for you to fetch changes up to 51fff4e69b4554dd3fee21e3c55a0f94937293e3:
>
> i915: Add versionless HuC files for current platforms (2022-09-16 08:52:30 -0700)
>
> ----------------------------------------------------------------
> John Harrison (2):
> i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
> i915: Add versionless HuC files for current platforms
>
> WHENCE | 18 ++++++++++++++++++
> i915/adlp_guc_70.bin | Bin 0 -> 297984 bytes
> i915/dg1_guc_70.bin | Bin 0 -> 272512 bytes
> i915/dg1_huc.bin | Bin 0 -> 589888 bytes
> i915/dg2_guc_70.bin | Bin 0 -> 369600 bytes
> i915/tgl_guc_70.bin | Bin 0 -> 285888 bytes
> i915/tgl_huc.bin | Bin 0 -> 589888 bytes
> 7 files changed, 18 insertions(+)
> create mode 100644 i915/adlp_guc_70.bin
> create mode 100644 i915/dg1_guc_70.bin
> create mode 100644 i915/dg1_huc.bin
> create mode 100644 i915/dg2_guc_70.bin
> create mode 100644 i915/tgl_guc_70.bin
> create mode 100644 i915/tgl_huc.bin
prev parent reply other threads:[~2022-09-26 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 20:41 PR for new GuC v70.5.1 and GuC/HuC with new names John.C.Harrison
2022-09-26 14:30 ` 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+5PVA7inRVU=ux3cC9bvu3aOWydGLBQDbfCFoGUhAqfxPQG3g@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=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 NNTP newsgroup(s).