diff options
| author | Reuben Dowle <reuben.dowle@4rf.com> | 2020-09-01 21:32:01 +0000 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2020-09-11 17:13:56 -0400 |
| commit | eb39d8ba5f0d1468b01b89a2a464d18612d3ea76 (patch) | |
| tree | 93782078ccf62a0559a5b152171bb7ece6f5a717 /arch | |
| parent | 1e2c5bb9e7f9fdad05a5b1f36c44da5cc430b8a9 (diff) | |
| download | u-boot-eb39d8ba5f0d1468b01b89a2a464d18612d3ea76.tar.gz | |
Fix data abort caused by mis-aligning FIT data
Attempting to place device tree immediately after an image in memory can lead
to mis-aligned data accesses if that image size is not divisible by the
alignment requirements of the architecture.
Data aborts caused by this were observed on a custom Marvel A388 based system,
where the image was a uboot FIT file. The total size varies depending on the
uboot device tree size, which does not always lead to correct alignment.
The minimum alignment specified for ARM [1] and ARM64 [2] linux booting has been
used
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/arm/booting.rst#n126
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/arm64/booting.rst#n45
Signed-off-by: Reuben Dowle <reuben.dowle@4rf.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions