diff options
| author | Stefan Agner <stefan.agner@toradex.com> | 2018-06-25 11:19:12 +0200 |
|---|---|---|
| committer | Heiko Schocher <hs@denx.de> | 2018-07-12 07:25:32 +0200 |
| commit | 68c7025d99dbac9ddf1a166a19efc3f9e98f1301 (patch) | |
| tree | 331d1c8e460341808d63413f712834c8bd169f99 /configs/xilinx_zynqmp_zcu104_revC_defconfig | |
| parent | 1612ff0dfba57b1002d8c7a54778eb553ace98f4 (diff) | |
cmd: ubi: print load size after establishing volume size
When using static volumes, the file size stored in the volume is
determined at runtime. Currently the ubi command prints the file
size specified on the console, which leads to a rather confusing
series of messages:
# ubi read ${fdt_addr_r} testvol
Read 0 bytes from volume testvol to 82000000
No size specified -> Using max size (179924992)
Make sure to print the actual size read in any case:
# ubi read ${fdt_addr_r} testvol
No size specified -> Using max size (179924992)
Read 179924992 bytes from volume testvol to 82000000
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Diffstat (limited to 'configs/xilinx_zynqmp_zcu104_revC_defconfig')
0 files changed, 0 insertions, 0 deletions