Hi Sam, On Wed, 23 Oct 2019 at 08:34, Sam Protsenko <semen.protse...@linaro.org> wrote: > > This command can be used to extract fields and image payloads from > Android Boot Image. It can be used for example to implement boot flow > where dtb is taken from boot.img (as v2 incorporated dtb inside of > boot.img). Using this command, one can obtain needed dtb file from > boot.img in scripting manner, and then apply needed dtbo's (from "dtbo" > partition) on top of that, providing then the resulting image to bootm > command in order to boot the Android. > > Also right now this command has the sub-command to get an address and > size of recovery dtbo from recovery image. It can be further parsed using > 'dtimg' command and merged into dtb file (for non-A/B devices only, see > [1,2] for details). > > [1] https://source.android.com/devices/bootloader/boot-image-header > [2] https://source.android.com/devices/architecture/dto/partitions > > Signed-off-by: Sam Protsenko <semen.protse...@linaro.org> > --- > Changes in v2: > - add "set_addr" sub-command > - provide mem mappings for sandbox > - rebase on top of master > > cmd/Kconfig | 8 ++ > cmd/Makefile | 1 + > cmd/bootimg.c | 210 ++++++++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 219 insertions(+) > create mode 100644 cmd/bootimg.c
Sorry I still think this name 'bootimg' is confusing. How would anyone know that it is specific to Android? How about abootimg? Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
