From: "Gong, Richard" <richard.gong@amd.com>
To: stable@vger.kernel.org
Cc: Mario Limonciello <mario.limonciello@amd.com>
Subject: AMD Navi3x dGPU experience improvement
Date: Mon, 8 May 2023 08:19:41 -0500 [thread overview]
Message-ID: <5ca2e61d-08d6-3070-f281-e2483cb7718a@amd.com> (raw)
Hi,
Since AMD introduced Navi3x dGPUs, setting them up is more difficult
than it need to be, as you need the GPU firmware binaries present in the
filesystem before the kernel drivers can be loaded. If you don't, you'll
just "hang" at a black screen. This is awkward because you must do
modprobe.blacklist=amdgpu and then load the file.
A large commit series went into 6.3 that improve this experience, but
not all of it is stable materiel.
As the dGPUs are supported on 6.1.y and 6.2.y, we can improve the
experience specifically for these new produces by back-porting a small
subset of commits that correspond to firmware files that are uniquely
loaded by the new products. With these commits amdgpu driver will return
an error code and you can continue to use framebuffer provided by UEFI
GOP driver until you have GPU firmware binaries loaded onto your system.
Commits needed for 6.2.y
cc42e76e7de5 "drm/amd: Load MES microcode during early_init"
2210af50ae7f "drm/amd: Add a new helper for loading/validating microcode"
11e0b0067ec0 "drm/amd: Use `amdgpu_ucode_*` helpers for MES"
Commits needed for 6.1.y
6040517e4a29 "drm/amdgpu: remove deprecated MES version vars"
cc42e76e7de5 "drm/amd: Load MES microcode during early_init"
2210af50ae7f "drm/amd: Add a new helper for loading/validating microcode"
11e0b0067ec0 "drm/amd: Use `amdgpu_ucode_*` helpers for MES"
Regards,
Richard
next reply other threads:[~2023-05-08 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 13:19 Gong, Richard [this message]
2023-05-13 7:28 ` AMD Navi3x dGPU experience improvement Greg KH
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=5ca2e61d-08d6-3070-f281-e2483cb7718a@amd.com \
--to=richard.gong@amd.com \
--cc=mario.limonciello@amd.com \
--cc=stable@vger.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