Hi Eugeniu,
On Mon, 1 Apr 2019 at 03:54, Eugeniu Rosca erosca@de.adit-jv.com wrote:
Our platform doesn't store the DTB into the Android image second area, but rather copies the DTB to RAM from a dedicated dtb.img partition [0], prior to booting the Android image by calling bootm.
Similar to [1], we find it useful to just call 'bootm' and have the right DTB being passed to OS (assuming its address has been previously stored in 'fdtaddr' by calling `fdt addr <dtb-addr>`).
Booting Android with DTB from 'fdtaddr' will only occur if:
- No DTB is embedded in the second area of Android image
- 'fdtaddr' points to a valid DTB in RAM
[0] https://source.android.com/devices/architecture/dto/partitions [1] https://patchwork.ozlabs.org/patch/1046652/ ("Support boot Android image without address on bootm command")
Signed-off-by: Eugeniu Rosca erosca@de.adit-jv.com
Changes in v2:
- Removed fdt_totalsize() computation, since FDT size verification is only relevant for blobs embedded in U-Boot-supported images
- Link v1: https://patchwork.ozlabs.org/patch/1071591/
common/image-fdt.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
Reviewed-by: Simon Glass sjg@chromium.org
We could really use a simple test of Android booting (not the whole process, just the setup and the different cases we support)
Regards, Simon
Applied to u-boot-dm, thanks!