(It seems I sent to the wrong mailing list, what I wanted to send is below)
On Thu, 23 Jul 2026 19:07, "Casey Connolly via groups.io"
<[email protected]> wrote:
<...>
I feel we are complicating it by trying to go for dynamic fw_images.
Rather than introducing a solution that diverges from the UEFI
specification, shall we use a board-specific static fw_images[]
Well, the solution I proposed at the end very much doesn't diverge from
the spec, that was kinda the point.
definition. This approach is simpler, remains spec-compliant, and other
Simpler for you to implement or simpler to maintain? I think that's
quite debatable...
vendors (like NXP, TI) have also implemented static fw_images (in board/
nxp, board/ti).
It is worth noting that mach-snapdragon isn't the only one using dynamic
fw_images[], Amlogic has also been switched to that approach too, while
previously hardcoding them per-board (mostly was only done for Libre Computer
boards with an SPI flash). On Amlogic side though we just use one giant image
with U-Boot and all the other bootloader stages before it, though with
U-Boot SPL enabled on GX SoCs this image contains a U-Boot SPL binary and
embedded FIT image containing everything else.
It really does make it much easier to bring capsule updates easily everywhere
and I think its advantages will become more appealing to other maintainers
over time. But just saying, Qualcomm boards are not alone doing this :)
Best regards,
Ferass
