From: Tom Rini Date: Tue, 7 Oct 2025 19:02:52 +0000 (-0600) Subject: Merge patch series "Add support for secure falcon mode: load kernel image before... X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6f180984700fdff706e3a0ed6d84ce7ca50f17fc;p=thirdparty%2Fu-boot.git Merge patch series "Add support for secure falcon mode: load kernel image before args" Anshul Dalal says: During the implementation of falcon mode for TI's K3 devices [1], I encountered several limitations in regards to the current falcon mode support in U-Boot especially in ensuring a secure boot flow. Although the current implementation allows for loading of a signed fitImage as the SPL payload, there are still a few edge cases that might allow bypassing the verified boot path. The following issues with current falcon mode need to be resolved: 1) No fallback: We currently fallback to regular boot flow if falcon mode fails, this might not be secure. 2) No arguments file: We currently load a kernel file (which could be a raw image or FIT) alongside an args file (usually the DT). The args file here doesn't have any verification mechanism, so should be skipped altogether as the FIT can contain the DT. 3) No access to env: In ext and fat fs boot, currently we also reads the environment to get the names of the kernel and the arg file. This should be disabled in secure falcon flow as the env might not be secure. 4) No raw image boot: Boot should fail when the kernel file is a raw kernel image, only FIT should be allowed. As per the recommendation of maintainers[2], I have decided to split the above set of tasks into multiple patch series. This is the first one which fixes the load order of kernel image and the args file in falcon mode. Along with some minor cleanup. [1]: https://lore.kernel.org/u-boot/20250603142452.2707171-1-anshuld@ti.com/ [2]: https://lore.kernel.org/u-boot/20250911172313.GT124814@bill-the-cat/ Link: https://lore.kernel.org/r/20250923124639.667718-1-anshuld@ti.com --- 6f180984700fdff706e3a0ed6d84ce7ca50f17fc