On Sun, 07 Jun 2026 14:48, "Casey Connolly via groups.io"
<[email protected]> wrote:
<...>
I'm really not in favour of adding a binman node to the DTB that U-Boot
uses, and I think it's kinda dumb that this is the only sensible way to
configure binman today...
I see nothing wrong with that. Can you expand on your concerns a little more?
It really just goes against the goal of using upstream DT. Previously I
managed to get binman to parse its config from a separate DTB but that
was hellish to integrate the tooling for.
Having this random node at runtime for completely unnecessary arbitrary
reasons feels just wrong to me.
For what is worth, binman config typically goes in -u-boot.dtsi, not the
device upstream .dts. It also doesn't have to be in <device-name>-u-boot.dtsi,
see for example rockchip-u-boot.dtsi and meson-gx-u-boot.dtsi.
I'd guess binman is more geared towards boards where multiple firmware
stages are loaded though (e.g. you have to load u-boot TPL then SPL then
TF-A etc), rather than just one u-boot.bin that's inside an android
boot.img.
Best regards,
Ferass
