From: Christian Heusel <christian@heusel.eu>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"Patil Rajesh" <Patil.Reddy@amd.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"linux@frame.work" <linux@frame.work>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION][BISECTED] Firmware load error for TEE on Framework Desktop
Date: Mon, 7 Apr 2025 15:43:07 +0200 [thread overview]
Message-ID: <d77dc639-dd7c-4a48-ae0a-26829d6fcdca@heusel.eu> (raw)
In-Reply-To: <195e5df0-d044-4d7a-afa1-4361c760c1f3@amd.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On 25/04/07 08:20AM, Mario Limonciello wrote:
> On 4/7/2025 1:36 AM, S-k, Shyam-sundar wrote:
> > Hi,
Hey Mario, hey Shyam,
> > The file "f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin" is missing from
> > the "/lib/firmware/amdtee" folder, which is causing the issue. This
> > is because there have been some last-minute modifications to the TA
> > firmware, and as a result, the firmware has not yet been updated. I
> > will inform you once the updated TA firmware is available, so you
> > can provide your feedback at that time.
> >
> > Thanks,
> > Shyam
> >
>
> FWIW - this below error is noisy but should be totally harmless on the
> Framework desktop as well. AFAIK - BIOS on FW desktop doesn't contain
> any PMF policies in the first place.
thanks for your answers, that's good to know! I guess we don't need an
urgent fix on the kernel side (or revert) then, let's just wait for the
firmware to land.
Cheers,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-04-07 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 19:20 Christian Heusel
2025-04-07 6:36 ` S-k, Shyam-sundar
2025-04-07 13:20 ` Mario Limonciello
2025-04-07 13:43 ` Christian Heusel [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=d77dc639-dd7c-4a48-ae0a-26829d6fcdca@heusel.eu \
--to=christian@heusel.eu \
--cc=Patil.Reddy@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@frame.work \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®