On Sat Sep 13, 2025 at 11:12 PM JST, Alexandre Courbot wrote: > Sending a final revision to have the `Link:` tags that dim requires, and > for the record. > > This series makes more progress on the GSP boot process for Ampere GPUs. > > At the end of the previous series [1], we were left with a WPR memory > region created by the FRTS firmware, but still far from the GSP running. > This series brings us closer to that goal by preparing 2 new firmware > packages: > > * The Booter firmware, which the driver loads and runs on the SEC2 > falcon; > * The GSP bootloader and firmware, with the bootloader loaded by Booter > onto the GSP RISC-V core to verify and load the actual GSP firmware. > > There firmwares are involved in a rather complex dance that is made > necessary by limitations related to the level of privilege required to > load code onto the GSP (doing so requires a Heavy Secured signed > firmware, which is the role fulfilled by Booter). > > The first 5 patches perform some cleanup and preparatory work for the > remainder of the series. Notably, the GSP boot is moved to a new method > of `Gpu` to get ready for the additional steps that will be added to it, > and the `Gpu` object is now fully built in-place. We also simplify > chipset name generation a bit and move the code requesting a firmware > file into a dedicated function in prevision of the removal of the > `Firmware` structure. > > Patch 6 parses the Booter firmware file, queries the hardware for the > right signature to use, and patch it into the firmware blob. This makes > Booter ready to load and run. > > Patches 7 and 8 prepare the GSP firmware and its bootloader, and keep > them into a single structure as they are closely related. > > Patches 9 and 10 switch to the 570.144 firmware and introduce the > layout for its bindings. The raw bindings are stored in a private > module, and abstracted by the parent module as needed. This allows > consumer modules to access a safer/nicer form of the bindings than the > raw one, and also makes it easier to switch to a different (and > potentially incompatible) firmware version in the future. > > 570.144 has been picked because it is the latest firmware currently in > linux-firmware, but as development progresses the plan is to switch to a > newer one that is designed with the constraint of upstream in mind. So > support for 570.144 will be dropped in the future. Support for multiple > firmware versions is not considered at the moment: there is no immediate > need for it as the driver is still unstable, and we can think about this > point once we approach stability (and have better visibility about the > shape of the firmware at that point). > > The last patch introduces the first bindings and uses them to compute > more framebuffer layout information needed for booting the GSP. A > separate patch series will pick up from there to use this information > and finally run these firmware blobs. > > The base of this series is today's drm-rust-next, with the Alignment [2] > series required for the last patch. > > A tree with all these dependencies and the patches of this series is > available at [3]. > > [1] > https://lore.kernel.org/rust-for-linux/[email protected]/ > [2] > https://lore.kernel.org/rust-for-linux/[email protected]/ > [3] https://github.com/Gnurou/linux/tree/b4/nova_firmware > > Signed-off-by: Alexandre Courbot <[email protected]>
Patches 1 to 10 merged to drm-rust-next, as agreed with Danilo.
