From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Gray <jsg@jsg.id.au>
Cc: stable@vger.kernel.org, flora.cui@amd.com, alexander.deucher@amd.com
Subject: Re: 6.12 drm/amdgpu ip discovery for legacy asics
Date: Sat, 12 Jul 2025 14:05:05 +0200 [thread overview]
Message-ID: <2025071258-name-number-b179@gregkh> (raw)
In-Reply-To: <aHCFws53G5vjFheh@largo.jsg.id.au>
On Fri, Jul 11, 2025 at 01:32:18PM +1000, Jonathan Gray wrote:
> After 6.12.36, amdgpu on a picasso apu prints an error:
> "get invalid ip discovery binary signature".
>
> Both with and without picasso_ip_discovery.bin from
> linux-firmware 20250708.
>
> The error is avoided by backporting more ip discovery patches.
>
> 25f602fbbcc8 drm/amdgpu/discovery: use specific ip_discovery.bin for legacy asics
> 2f6dd741cdcd drm/amdgpu/ip_discovery: add missing ip_discovery fw
>
> second is a fix for the first
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-07-12 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 3:32 6.12 drm/amdgpu ip discovery for legacy asics Jonathan Gray
2025-07-12 12:05 ` Greg KH [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=2025071258-name-number-b179@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=flora.cui@amd.com \
--cc=jsg@jsg.id.au \
--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;
as well as URLs for NNTP newsgroup(s).