[Question] TI's u-boot.img is built twice

Simon Glass sjg at chromium.org
Fri Sep 22 17:04:20 CEST 2023


Hi Masahiro,

On Fri, 22 Sept 2023 at 01:19, Masahiro Yamada <masahiroy at kernel.org> wrote:
>
> On Fri, Sep 22, 2023 at 2:27 PM Neha Malcom Francis <n-francis at ti.com> wrote:
> >
> > Hi Masahiro
> >
> > On 21/09/23 21:06, Masahiro Yamada wrote:
> > > Hi.
> > >
> > > Since the TI platform migrated to binman,
> > > u-boot.img is built twice.
> > >
> > > It is created by "mkimage -E",
> > > then overwritten by binman.
> > >
> > >
> > > So, the data are embedded in the FIT structure
> > > instead of being appended.
> > >
> > > Is this intentional?
> > >
> > > To me, it looks weird.
> > >
> > >
> >
> > I haven't added the fit,external-offset property in the binman.dtsi so it was
> > not appended as external data and I did not find reason to. Is there any benefit
> > in having the data appended than embedded?
>
>
>
> Placing payload data outside the FIT structure is a U-Boot hack.

No, it isn't a hack. It is part of the specification[1].

[..]

Regards,
Simon

[1] https://github.com/open-source-firmware/flat-image-tree/releases/tag/v0.8


More information about the U-Boot mailing list