From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 24 Apr 2019 09:22:23 -0400 Subject: [U-Boot] Support boot Android image without address on bootm command In-Reply-To: <20190222082806.4169-1-shawn.guo@linaro.org> References: <20190222082806.4169-1-shawn.guo@linaro.org> Message-ID: <20190424132223.GS31207@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Feb 22, 2019 at 04:28:06PM +0800, Shawn Guo wrote: > It works perfectly fine to boot an Android boot.img with bootm command > followed by an explicit address argument that holds the image. But if > we have boot.img downloaded into default 'loadaddr', and then boot it > using bootm command without the address argument, we will run into > problem, because U-Boot fails to find ramdisk and fdt (second area) in > boot.img. > > The current Android image support assumes there is always an address > argument on bootm command. However just like booting any other images, > 'loadaddr' should be used when address argument is missing from bootm > command. It patches boot_get_ramdisk() and boot_get_fdt() a bit to > support this quite common usage of bootm command for Android image. > > Signed-off-by: Shawn Guo > Reviewed-by: Tom Rini Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: