[U-Boot] [PATCH v2 0/5] boot_get_fdt: clean up and use 'fdtaddr' as fallback for Android
Eugeniu Rosca
erosca at de.adit-jv.com
Mon Apr 1 10:45:32 UTC 2019
The main feature added in this series is being able to boot Android
images with empty/non-DTB contents in the second area by using the
address stored in the 'fdtaddr' environment variable. More details in
"fdt: boot_get_fdt: android: use ENV 'fdtaddr' as fallback".
This is combined with a number of small-sized (review-friendly) cleanup
patches, attempting to increase the readability of boot_get_fdt().
They are partitioned into functional (assumed to add a change in
runtime behavior) and non-functional changes.
Comments/thoughts appreciated! TIA!
Changes in v2:
- Dropped centralized fdt_len verification since it only makes sense
for DT blobs embedded in the U-Boot-supported images (in which case
two FDT size values are available and can be compared, one from the
booted image via an image-specific API and one from the FDT itself
via fdt_totalsize). Centralized fdt_len verification doesn't make
much sense in case of user-provided DT blobs (via boot{m,*} command
or via some environment variable)
- Fixed 'booti' regression on arm64/R-Car3
- Fixed a number of typos
- Link v1: https://patchwork.ozlabs.org/patch/1071586/
Eugeniu Rosca (5):
fdt: boot_get_fdt: remove redundant zeroing out
fdt: boot_get_fdt: really boot w/o FDT when "goto no_fdt"
fdt: boot_get_fdt: simplify no_fdt handling (non-functional)
fdt: boot_get_fdt: android: compress handling (non-functional)
fdt: boot_get_fdt: android: use ENV 'fdtaddr' as fallback
common/image-fdt.c | 33 +++++++++++++++++----------------
1 file changed, 17 insertions(+), 16 deletions(-)
--
2.21.0
More information about the U-Boot
mailing list