diff options
| author | Alexandre Courbot <acourbot@nvidia.com> | 2026-07-23 22:54:37 +0900 |
|---|---|---|
| committer | Alexandre Courbot <acourbot@nvidia.com> | 2026-09-01 08:42:31 +0900 |
| commit | b705c185105762676aa6ec16cf976101df87cc35 (patch) | |
| tree | 9d1b7047a8ab587aaaa59d986c6a3028c3f9c80f /scripts/Makefile.thinlto | |
| parent | c63829528980507a0a9146031e0c08499f53cf3d (diff) | |
| download | linux-next-b705c185105762676aa6ec16cf976101df87cc35.tar.gz linux-next-b705c185105762676aa6ec16cf976101df87cc35.zip | |
gpu: nova-core: fix incorrect naming/framing of GSP-FMC firmware
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 location of 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),
- Rewording the `fsp.rs` module documentation to describe the actual
boot flow.
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
Reviewed-by: Eliot Courtney <ecourtney@nvidia.com>
Link: https://patch.msgid.link/20260825-gsp-fmc-rename-v1-1-f82526f01d7d@nvidia.com
[acourbot: drop the documentation change to be picked up by Zhi, reword
commit message a bit.]
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
