aboutsummaryrefslogtreecommitdiff
path: root/cmd/boot.c
diff options
context:
space:
mode:
authorHeinrich Schuchardt <xypron.glpk@gmx.de>2020-06-19 19:45:55 +0200
committerSimon Glass <sjg@chromium.org>2020-07-09 18:57:22 -0600
commit43913f01b93ef08b87efa63b5ba599026e900e12 (patch)
tree22c3b95c867cb4469bef0da4691ee16801e88126 /cmd/boot.c
parentdde173a204e14a243855ce5414820d61bcc80539 (diff)
downloadu-boot-43913f01b93ef08b87efa63b5ba599026e900e12.zip
u-boot-43913f01b93ef08b87efa63b5ba599026e900e12.tar.gz
u-boot-43913f01b93ef08b87efa63b5ba599026e900e12.tar.bz2
cmd: fdt: remove CMD_FDT_MAX_DUMP
When printing the device tree we want to get an output that can be used as input for the device tree compiler. This requires that we do not write bogus lines like pcie@10000000 { interrupt-map = * 0x4000127c [0x00000280]; For instance the QEMU virt device has a property interrupt-map with 640 bytes which exceeds CMD_FDT_MAX_DUMP=64. So lets do away with the artificial limitation to 64 bytes. As indicated in commit f0a29d43313c ("fdt: Limit printed hex in fdt print and list commands") if a device tree contains binary blobs, it may still be desirable to limit the output length. Provide environment variable fdt_max_dump for this purpose. Fixes: 5d927b428622 ("Kconfig: Drop CONFIG_CMD_FDT_MAX_DUMP") Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'cmd/boot.c')
0 files changed, 0 insertions, 0 deletions