Simon, [...]
> > + Properties / Entry arguments: > > + - filename: Filename of u-boot MBN (default 'u-boot.mbn') > > U-Boot (not u-boot) Ok. > > + This is the U-Boot MBN image. > > It is good to have this etype, but please document it properly. We > need to know what MBN stands for, along with a link to the spec, etc. > Also please describe its role in booting. > > Please do the same for the others below too. MBN is a Qualcomm‑specific signed firmware container that packages executable images (typically ELF) along with metadata such as hash, signature, and certificate chain, enabling the secure boot chain and Root of Trust (RoT) to load and authenticate images. [...] > > +class Entry_qcom_config(Entry_blob_named_by_arg): > > + """QC Config ELF > > Does QC Config mean Qualcomm Config? Is this a configuration file? If > so, why is it in elf format? Although the QC Config image primarily contains configuration data that could be represented as a raw binary, it is maintained in ELF format to ensure compatibility with Root of Trust (RoT)–based image authentication during the secure boot process. The current implementation aligns with standard verified boot requirements, however, support for full secure boot is planned for future enablement. In that context, retaining the ELF format allows the image to be processed and signed using the standard Qualcomm image signing infrastructure, ensuring seamless integration with the trusted boot chain. Thanks Varada [...]
