From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Zhi Wang" <zhiw@nvidia.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alice Ryhl" <aliceryhl@google.com>,
"Benno Lossin" <lossin@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"John Hubbard" <jhubbard@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
<nova-gpu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH] gpu: nova-core: fix incorrect naming/framing of GSP-FMC firmware
Date: Thu, 27 Aug 2026 09:37:34 +0900 [thread overview]
Message-ID: <DKZB1C3502I9.1NBE2D1W50UZZ@nvidia.com> (raw)
In-Reply-To: <20260826111408.34d47a7d@inno-dell>
On Wed Aug 26, 2026 at 5:14 PM JST, Zhi Wang wrote:
> On Tue, 25 Aug 2026 21:40:58 +0200
> "Danilo Krummrich" <dakr@kernel.org> wrote:
>
>> On Tue Aug 25, 2026 at 10:31 AM CEST, Alexandre Courbot wrote:
>> > The GSP-FMC firmware code lived in `firmware/fsp.rs` and described
>> > itself as running on the FSP. This is incorrect: GSP-FMC is loaded
>> > by the FSP, but runs on the GSP as the loader and verifier of
>> > GSP-RM. FSP secure-boots on its own before the driver even starts.
>> >
>> > Correct the naming and files used to contain the GSP-FMC code, by:
>> >
>> > - Renaming `firmware/fsp.rs` to `firmware/gsp_fmc.rs` (as GSP-FMC
>> > is not the FSP firmware),
>> > - Changing the prefix of some declarations in that file to `FMC` or
>> > `GspFmc` (interestingly some were already correct),
>> > - Fixing a mismatch (FMC means "First Mutable Code") in `fsp.rst`.
>>
>> Good catch,
>>
>> Reviewed-by: Danilo Krummrich <dakr@kernel.org>
>>
>> > FSP (hardware root of trust, boots from ROM)
>> > - -> FMC (Falcon Microcontroller, verified by FSP)
>> > + -> FMC (First Mutable Code, verified by FSP)
>>
>> That reminds me that I'd like to have a table in
>> Documentation/gpu/nova/ listing and explaining all abbreviations.
>>
>
> Thanks for catching this. I got this abbreviation from other patch
> comments.
>
>> In nouveau it's a huge mess and all the abbreviations became rather
>> confusing.
>>
>
> ...
>
>> We already have something is fsp.rst, but I think it is misleading
>> and needs to be fixed as well.
>>
>
> I just dig some docs, there are multiple FMCs for different
> controllers, here should be GSP-FMC as well.
>
> Alex, you can include the following diff for fixing the chart.
Actually, since you have your own patch fixing the documentation [1],
let's move everything there - can you fold the documentation
abbreviation fix from this patch into yours, since the chart fix also
seems to be there? I will drop that part from this patch when applying.
No need for attribution tag as this is a one-liner.
[1] https://lore.kernel.org/cover.1787754628.git.zhiw@nvidia.com
next prev parent reply other threads:[~2026-08-27 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 8:31 Alexandre Courbot
2026-08-25 19:40 ` Danilo Krummrich
2026-08-26 8:14 ` Zhi Wang
2026-08-27 0:37 ` Alexandre Courbot [this message]
2026-08-25 23:21 ` Eliot Courtney
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=DKZB1C3502I9.1NBE2D1W50UZZ@nvidia.com \
--to=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=zhiw@nvidia.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
all inboxes | Powered by JetHome®