On 9/14/26 8:35 AM, Carlo Caione wrote:
> Some provisioning flows need U-Boot's command support in addition to
> fastboot. Provide a U-Boot-based download agent for Genio 510 and 700 so
> these flows can run without relying on firmware already stored on the
> board.
So this is providing the same utility as in the previous patch, but also
uses U-Boot proper? Why do we need both?
> diff --git a/arch/arm/mach-mediatek/spl.c b/arch/arm/mach-mediatek/spl.c
> index 6f1ec052b95..75b51f4986e 100644
> --- a/arch/arm/mach-mediatek/spl.c
> +++ b/arch/arm/mach-mediatek/spl.c
> @@ -33,6 +33,9 @@ void board_init_f(ulong dummy)
>
> u32 spl_boot_device(void)
> {
> + if (CONFIG_IS_ENABLED(RAM_DEVICE))
> + return BOOT_DEVICE_RAM;
> +
It seems like this could unintentionally affect other MediaTek targets since
they all share this code. Should we also check one of the FASTBOOT config
options here?
> #if defined(CONFIG_SPL_SPI)
> return BOOT_DEVICE_SPI;
> #elif defined(CONFIG_SPL_MMC)
Should we have a precursor patch to clean up the existing entries to also
use CONFIG_IS_ENABLED() to keep this consistent?
(And I assume in the config from the first patch, this would fall though to
BOOT_DEVICE_NONE since there is no u-boot proper in that case?)
