On Tue Jul 7, 2026 at 4:21 PM JST, Alexandre Courbot wrote: > By being in the TU102 HAL, we already know that the GSP boot method is > the SEC2 Booter, so the only variable is whether the FWSEC bootloader is > used or not. Since `Chipset` also includes the variants that boot FSP, > querying it for that information introduces a potential code path (a > chipset that boots via FSP) that the current code doesn't handle. > > Turn the use of the FWSEC bootloader into a property of the `Tu102` HAL, > and give GA102+ chipsets their own instance with that property set to > `false`. This removes the invalid code path and the only use of > `Chipset` is now to load the correct firmware files. > > This also removes some uses of the `Chipset::needs_fwsec_bootloader` > method and prepares the ground for removing it. > > Signed-off-by: Alexandre Courbot <[email protected]> > ---
Reviewed-by: Eliot Courtney <[email protected]>
