Hi Alexey, On 6/9/26 6:52 PM, Alexey Charkov wrote:
Modern Rockchip SoCs such as RK3576 require ATF to be running to provide firmware services to the OS. To enable booting Linux in Falcon mode on such SoCs, add binman support for generation of FIT images containing appropriately split ATF raw binaries (as is currently done by binman for U-boot proper images), externally preprocessed DTB and a Linux kernel.
This is a bit misleading I believe. This is generating an image for falcon booting via USB download mode. The earlier patches support falcon boot when booting from standard storage media. We do not need this to do falcon boot in general (or maybe I misunderstood).
I'm against this patch, specifically the part modifying rockchip-u-boot.dtsi. The only U-Boot part in the whole process is concatenating SPL with the new FIT image (which has the FDT optionally coming from it else externally), which you can do outside of U-Boot yourself. I don't see why U-Boot should accept this patch but maybe I'm missing something?
This implementation is also specific to Linux, will we have patches to support Zephyr, FreeBSD, etc... in the future? I see this as opening a door for things we don't want to have to deal with. How will you deal with multiple device trees? With device tree overlays? How will you deal with A/B update mechanism with falcon boot?
To be clear, I'm not saying what this allows is a bad idea, I'm saying U-Boot is not the right place for this.
Cheers, Quentin
