summaryrefslogtreecommitdiff
path: root/include/usb_mass_storage.h
diff options
context:
space:
mode:
authorMarek Vasut <marek.vasut+renesas@gmail.com>2018-11-27 00:19:03 +0100
committerMarek Vasut <marex@denx.de>2018-12-04 09:21:06 +0100
commit07a8060a12771d3d10583a6295a0c89e0a2e83f0 (patch)
tree695a407b8b0f7996d663c0df9152bd12493982f4 /include/usb_mass_storage.h
parentcf345760bdf7b8f7514dc7d02defe0fc1b9fd52c (diff)
ARM: rmobile: Convert to bootm_size
Convert all Renesas R-Car boards to bootm_size of 256 MiB and drop both fdt_high and initrd_high. This change implies that the FDT and initrd will always be copied into the first 256 MiB of RAM instead of being used in place, which can cause various kinds of inobvious problems. The simpler problems include FDT or initrd being overwritten or being used from unaligned addresses, especially on ARM64. The overhead of copying the FDT to aligned location is negligible and these problems go away, so the benefit is significant. Regarding alignment problems with fitImage. The alignment of DT properties is always 32 bits, which implies that the alignment of the "data" property in fitImage is also 32 bits. The /incbin/ syntax plays no role here. The kernel expects all elements, including DT and initrd, to be aligned to 64 bits on ARM64, thus using them in place may not be possible. Using the bootm_size assures correct alignment, again with negligible overhead. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org> Cc: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'include/usb_mass_storage.h')
0 files changed, 0 insertions, 0 deletions