summaryrefslogtreecommitdiffstats
path: root/board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch
diff options
context:
space:
mode:
authorJoel Stanley <joel@jms.id.au>2018-04-12 15:59:40 +0930
committerJoel Stanley <joel@jms.id.au>2018-04-12 15:59:40 +0930
commita8d11267c2bfad3ff410ea342778f2791982da51 (patch)
tree98f7058a6f58fc3f63d1e8bb499531a0a01e15fd /board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch
parente17668bbe3538d42b0a0fab64251e60ff6c81d68 (diff)
parent9565a37e0d2aa3c5fb9a4148760c490f2e5226d4 (diff)
downloadbuildroot-2018.02-op-build.tar.gz
buildroot-2018.02-op-build.zip
Merge tag '2018.02.1' into 2018.02-op-build2018.02-op-build
Release 2018.02.1
Diffstat (limited to 'board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch')
-rw-r--r--board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch55
1 files changed, 55 insertions, 0 deletions
diff --git a/board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch b/board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch
new file mode 100644
index 0000000000..92eff7574d
--- /dev/null
+++ b/board/freescale/imx6sabre/patches/uboot/0002-imximage-Remove-failure-when-no-IVT-offset-is-found.patch
@@ -0,0 +1,55 @@
+From 24ba28680abe868e8db3442a9bf523ad3af1febd Mon Sep 17 00:00:00 2001
+From: Fabio Estevam <fabio.estevam@nxp.com>
+Date: Fri, 9 Mar 2018 08:25:00 -0300
+Subject: [PATCH] imximage: Remove failure when no IVT offset is found
+
+Sometimes imximage throws the following error:
+
+ CFGS board/freescale/vf610twr/imximage.cfg.cfgtmp
+ CFGS board/freescale/vf610twr/imximage.cfg.cfgtmp
+ MKIMAGE u-boot-dtb.imx
+Error: No BOOT_FROM tag in board/freescale/vf610twr/imximage.cfg.cfgtmp
+arch/arm/mach-imx/Makefile:100: recipe for target 'u-boot-dtb.imx' failed
+
+Later on, when running mkimage for the u-boot.imx it will succeed in
+finding the IVT offset.
+
+Looks like some race condition happening during parallel build when
+processing mkimage for u-boot-dtb.imx and u-boot.imx.
+
+A proper fix still needs to be implemented, but as a workaround let's
+remove the error when the IVT offset is not found.
+
+It is useful to have such message, especially during bring-up phase,
+but the build error that it causes is severe, so better avoid the
+build error for now.
+
+The error checking can be re-implemented later when we have a proper
+fix.
+
+Reported-by: Breno Lima <breno.lima@nxp.com>
+Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
+Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
+---
+ tools/imximage.c | 5 -----
+ 1 file changed, 5 deletions(-)
+
+diff --git a/tools/imximage.c b/tools/imximage.c
+index 0c43196..bef56f8 100644
+--- a/tools/imximage.c
++++ b/tools/imximage.c
+@@ -765,11 +765,6 @@ static uint32_t parse_cfg_file(struct imx_header *imxhdr, char *name)
+ (*set_dcd_rst)(imxhdr, dcd_len, name, lineno);
+ fclose(fd);
+
+- /* Exit if there is no BOOT_FROM field specifying the flash_offset */
+- if (imximage_ivt_offset == FLASH_OFFSET_UNDEFINED) {
+- fprintf(stderr, "Error: No BOOT_FROM tag in %s\n", name);
+- exit(EXIT_FAILURE);
+- }
+ return dcd_len;
+ }
+
+--
+2.7.4
+
OpenPOWER on IntegriCloud