Dear Prafulla Wadaskar,
In message 1247498802-12488-1-git-send-email-prafulla@marvell.com you wrote:
From: prafulla_wadaskar prafulla@marvell.com
In some cases the u-boot.bin need to be processed further to create bootable u-boot binary from boot device This processing may be cpu,soc and/or board spcific bin_dep.sh provides a mechanism to execute bin_dep.sh if present in above platform specific folders
Signed-off-by: prafulla_wadaskar prafulla@marvell.com
Makefile | 2 + tools/bin_dep.sh | 79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+), 0 deletions(-) create mode 100755 tools/bin_dep.sh
diff --git a/Makefile b/Makefile index f857641..8bf36ce 100644 --- a/Makefile +++ b/Makefile @@ -318,6 +318,7 @@ $(obj)u-boot.srec: $(obj)u-boot
$(obj)u-boot.bin: $(obj)u-boot $(OBJCOPY) ${OBJCFLAGS} -O binary $< $@
@./tools/bin_dep.sh $(CPU) $(BOARD) $(VENDOR) $(SOC) $@
NAK. I reject this patch, and I will continue to reject all attempts to perform additional operations on the u-boot.bin image.
u-boot.bin is by definition the raw binary image of U-Boot. If you use additional tools to post-process this image, then you are creating a new image format, which must have it's own name.
Best regards,
Wolfgang Denk