From: John.C.Harrison@Intel.com
To: linux-firmware@kernel.org
Cc: jwboyer@kernel.org, intel-gfx@lists.freedesktop.org,
kyle@kernel.org, ben@decadent.org.uk
Subject: [Intel-gfx] PR for new GuC v70.6.6 for MTL
Date: Wed, 3 May 2023 09:58:28 -0700 [thread overview]
Message-ID: <20230503165828.1002609-1-John.C.Harrison@Intel.com> (raw)
The following changes since commit 312c61f5a6c9c6a313383a8f0c2b02711ec15262:
amdgpu: update DCN 3.1.6 DMCUB firmware (2023-05-03 09:11:02 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware mtl_guc_70.6.6
for you to fetch changes up to 192ee6d1a7806620eeb6f8478e6a3ec6ea44821c:
i915: Add GuC v70.6.6 for MTL (2023-05-03 06:45:11 -0700)
----------------------------------------------------------------
John Harrison (1):
i915: Add GuC v70.6.6 for MTL
WHENCE | 3 +++
i915/mtl_guc_70.bin | Bin 0 -> 303936 bytes
2 files changed, 3 insertions(+)
create mode 100644 i915/mtl_guc_70.bin
next reply other threads:[~2023-05-03 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 16:58 John.C.Harrison [this message]
2023-05-04 11:20 ` [Intel-gfx] PR for new GuC v70.6.6 for MTL 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=20230503165828.1002609-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@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