From: Aurabindo Pillai <aurabindo.pillai@amd.com>
To: Josh Boyer <jwboyer@kernel.org>, <linux-firmware@kernel.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Deepak Sharma <deepak.sharma@amd.com>
Subject: V2: pull request: amdgpu: update DMCUB firmware to v0.0.204.0
Date: Wed, 7 Feb 2024 16:27:52 -0500 [thread overview]
Message-ID: <20240207212752.1614192-1-aurabindo.pillai@amd.com> (raw)
The following changes since commit bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20:
amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32 (2024-02-02 16:58:17 -0500)
are available in the Git repository at:
git@gitlab.freedesktop.org:drm/firmware.git tags/amd-2024-02-07
for you to fetch changes up to e34e1e5078b8020c789c7f11e0176c86630f4d3f:
amdgpu: DMCUB Updates for DCN321: 7.0.38.0 (2024-02-07 16:13:19 -0500)
V1 PR had a wrong path for the files, which has been fixed in this V2.
----------------------------------------------------------------
Aurabindo Pillai (2):
amdgpu: DMCUB updates for Yellow Carp: 4.0.68.0
amdgpu: DMCUB Updates for DCN321: 7.0.38.0
amdgpu/dcn_3_2_1_dmcub.bin | Bin 232224 -> 232224 bytes
amdgpu/yellow_carp_dmcub.bin | Bin 234768 -> 234768 bytes
2 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/amdgpu/dcn_3_2_1_dmcub.bin b/amdgpu/dcn_3_2_1_dmcub.bin
index 42790cd8..e463012b 100644
Binary files a/amdgpu/dcn_3_2_1_dmcub.bin and b/amdgpu/dcn_3_2_1_dmcub.bin differ
diff --git a/amdgpu/yellow_carp_dmcub.bin b/amdgpu/yellow_carp_dmcub.bin
index a72743bc..5b634a72 100644
Binary files a/amdgpu/yellow_carp_dmcub.bin and b/amdgpu/yellow_carp_dmcub.bin differ
next reply other threads:[~2024-02-07 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 21:27 Aurabindo Pillai [this message]
2024-02-07 21:35 ` V2: pull request: amdgpu: update DMCUB firmware to v0.0.204.0 Limonciello, Mario
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=20240207212752.1614192-1-aurabindo.pillai@amd.com \
--to=aurabindo.pillai@amd.com \
--cc=alexander.deucher@amd.com \
--cc=deepak.sharma@amd.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=mario.limonciello@amd.com \
/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).