linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@kernel.org>
To: John.C.Harrison@intel.com
Cc: intel-gfx@lists.freedesktop.org, kyle@kernel.org,
	ben@decadent.org.uk, linux-firmware@kernel.org
Subject: Re: [Intel-gfx] PR for new GuC v62.0.3 and HuC v7.9.3 binaries
Date: Fri, 16 Jul 2021 07:50:40 -0400	[thread overview]
Message-ID: <CA+5PVA5Z5_kgsOwvrW8KYSs=E9X=qqZKLRCNGMdj3MYWg1QmuA@mail.gmail.com> (raw)
Message-ID: <20210716115040.ZAZOsbxhFo306Y73IKj_Y1HoASLge7Vpq138v0zHMAA@z> (raw)
In-Reply-To: <20210708175025.333468-1-John.C.Harrison@Intel.com>

On Thu, Jul 8, 2021 at 1:50 PM <John.C.Harrison@intel.com> wrote:
>
> The following changes since commit d79c26779d459063b8052b7fe0a48bce4e08d0d9:
>
>   amdgpu: update vcn firmware for green sardine for 21.20 (2021-06-29 07:26:03 -0400)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-firmware guc_62.0_huc_7.9
>
> for you to fetch changes up to f4d897acd200190350a5f2148316c51c6c57bc9b:
>
>   firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 (2021-06-29 14:20:03 -0700)
>
> ----------------------------------------------------------------
> John Harrison (3):
>       firmware/i915/guc: Add GuC v62.0.0 for all platforms
>       firmware/i915/guc: Add GuC v62.0.3 for ADL-P
>       firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1

Pulled and pushed out.

josh

>
>  WHENCE                   |  38 +++++++++++++++++++++++++++++++++++++-
>  i915/adlp_guc_62.0.3.bin | Bin 0 -> 336704 bytes
>  i915/bxt_guc_62.0.0.bin  | Bin 0 -> 199616 bytes
>  i915/cml_guc_62.0.0.bin  | Bin 0 -> 200448 bytes
>  i915/dg1_guc_62.0.0.bin  | Bin 0 -> 315648 bytes
>  i915/dg1_huc_7.9.3.bin   | Bin 0 -> 589888 bytes
>  i915/ehl_guc_62.0.0.bin  | Bin 0 -> 327488 bytes
>  i915/glk_guc_62.0.0.bin  | Bin 0 -> 200000 bytes
>  i915/icl_guc_62.0.0.bin  | Bin 0 -> 327488 bytes
>  i915/kbl_guc_62.0.0.bin  | Bin 0 -> 200448 bytes
>  i915/skl_guc_62.0.0.bin  | Bin 0 -> 199552 bytes
>  i915/tgl_guc_62.0.0.bin  | Bin 0 -> 326016 bytes
>  i915/tgl_huc_7.9.3.bin   | Bin 0 -> 589888 bytes
>  13 files changed, 37 insertions(+), 1 deletion(-)
>  create mode 100644 i915/adlp_guc_62.0.3.bin
>  create mode 100644 i915/bxt_guc_62.0.0.bin
>  create mode 100644 i915/cml_guc_62.0.0.bin
>  create mode 100644 i915/dg1_guc_62.0.0.bin
>  create mode 100644 i915/dg1_huc_7.9.3.bin
>  create mode 100644 i915/ehl_guc_62.0.0.bin
>  create mode 100644 i915/glk_guc_62.0.0.bin
>  create mode 100644 i915/icl_guc_62.0.0.bin
>  create mode 100644 i915/kbl_guc_62.0.0.bin
>  create mode 100644 i915/skl_guc_62.0.0.bin
>  create mode 100644 i915/tgl_guc_62.0.0.bin
>  create mode 100644 i915/tgl_huc_7.9.3.bin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-07-16 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 17:50 PR for new GuC v62.0.3 and HuC v7.9.3 binaries John.C.Harrison
2021-07-08 17:50 ` [Intel-gfx] " John.C.Harrison
2021-07-16 11:50 ` Josh Boyer [this message]
2021-07-16 11:50   ` Josh Boyer

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+5PVA5Z5_kgsOwvrW8KYSs=E9X=qqZKLRCNGMdj3MYWg1QmuA@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).