aboutsummaryrefslogtreecommitdiff
path: root/arch/arm/dts/sunxi-u-boot.dtsi
diff options
context:
space:
mode:
authorMaxime Ripard2017-10-19 11:36:35 +0200
committerMaxime Ripard2017-10-25 10:05:06 +0200
commit819f1e081c527d2d02cdaeec0027384688cf5de0 (patch)
tree83a1ff0b1e1fa0a6c7355a9a3566b66a7385a239 /arch/arm/dts/sunxi-u-boot.dtsi
parentce2e44d836dc790deb21707729d89d54d1bb6e7d (diff)
sunxi: binman: Add U-Boot binary size check
The U-Boot binary may trip over its actual allocated size in the storage. In such a case, the environment will not be readable anymore (because corrupted when the new image was flashed), and any attempt at using saveenv to reconstruct the environment will result in a corrupted U-Boot binary. Reviewed-by: Andre Przywara <andre.przywara@arm.com> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Diffstat (limited to 'arch/arm/dts/sunxi-u-boot.dtsi')
-rw-r--r--arch/arm/dts/sunxi-u-boot.dtsi12
1 files changed, 12 insertions, 0 deletions
diff --git a/arch/arm/dts/sunxi-u-boot.dtsi b/arch/arm/dts/sunxi-u-boot.dtsi
index 5adfd9bca2e..72e95afd780 100644
--- a/arch/arm/dts/sunxi-u-boot.dtsi
+++ b/arch/arm/dts/sunxi-u-boot.dtsi
@@ -1,5 +1,14 @@
#include <config.h>
+/*
+ * This is the maximum size the U-Boot binary can be, which is basically
+ * the start of the environment, minus the start of the U-Boot binary in
+ * the MMC. This makes the assumption that the MMC is using 512-bytes
+ * blocks, but devices using something other than that remains to be
+ * seen.
+ */
+#define UBOOT_MMC_MAX_SIZE (CONFIG_ENV_OFFSET - (CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR * 512))
+
/ {
binman {
filename = "u-boot-sunxi-with-spl.bin";
@@ -8,6 +17,9 @@
filename = "spl/sunxi-spl.bin";
};
u-boot-img {
+#ifdef CONFIG_MMC
+ size = <UBOOT_MMC_MAX_SIZE>;
+#endif
pos = <CONFIG_SPL_PAD_TO>;
};
};