From: Tom Rini Date: Fri, 1 Nov 2019 09:29:02 -0400 Subject: [U-Boot] [RFC/RFT U-Boot PATCH] image: Add Image.gz parsing support in booti. In-Reply-To: <20191010212317.3884-1-atish.patra@wdc.com> References: <20191010212317.3884-1-atish.patra@wdc.com> Message-ID: <20191101132902.GQ11173@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 Thu, Oct 10, 2019 at 02:23:17PM -0700, Atish Patra wrote: > Add gz parsing logic so that booti can parse both Image > and Image.gz to boot Linux. Currently, it is difficult to calculate > a safe address for every board where the Image.gz can be decompressed. > It is also not possible to figure out the size of the compressed file > as well. Thus, user need to set two additional environment variables > kernel_gz_addr_r and kernel_gz_size to make Image.gz work. > > Tested on HiFive Unleashed and Qemu for RISC-V. > > Signed-off-by: Atish Patra > --- > I could not test this patch on any ARM64 devices due to lack of > access to any ARM64 board. If anybody can test it on ARM64, that > would be great. Can we do the compression check more generally? I'd like to be able to see Image.xz/lz4/etc be able to be handled cleanly. When you say the compressed file, you do mean the Image.gz (for example) itself, right? I would suggest documenting using $filesize after loading the compressed image as that should always be set. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: