From: Marek Vasut Date: Tue, 9 Apr 2019 16:25:40 +0200 Subject: [U-Boot] [PATCH v2 1/2] image: android: allow booting lz4-compressed kernels In-Reply-To: <20190409140847.GA28398@vmlxhi-102.adit-jv.com> References: <20190408153528.23783-1-erosca@de.adit-jv.com> <7fe515ff-685f-b346-4833-9344da7746e7@gmail.com> <20190409122918.GA31459@vmlxhi-102.adit-jv.com> <20190409140847.GA28398@vmlxhi-102.adit-jv.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 4/9/19 4:08 PM, Eugeniu Rosca wrote: > On Tue, Apr 09, 2019 at 02:38:08PM +0200, Marek Vasut wrote: >> On 4/9/19 2:29 PM, Eugeniu Rosca wrote: >>> On Tue, Apr 09, 2019 at 01:06:31PM +0200, Marek Vasut wrote: >>>> On 4/8/19 5:35 PM, Eugeniu Rosca wrote: >>>>> According to Android image format [1], kernel image resides at 1 page >>>>> offset from the boot image address. Grab the magic number from there >>>>> and allow U-Boot to handle LZ4-compressed KNL binaries instead of >>>>> hardcoding compression type to IH_COMP_NONE. Other compression types, >>>>> if needed, can be added later. >>>>> >>>>> Tested on H3ULCB-KF using the image detailed in [2]. >>>> >>>> H3ULCB Kingfisher is not supported in mainline ;-) >>> >>> Well, my H3 ES2.0 ULCB attached to Kingfisher-M06 boots just fine with >>> the recently released v2019.04 U-Boot. I guess U-Boot simply doesn't >>> (need to) care about the fancy peripherals present on the KF extension >>> board (hence no need to spawn another KF defconfig)? >> >> Glad to hear it boots well. Is there anything interesting on the KF >> that'd be worth supporting ? I think it could be handled via DTOs. > > My vote goes for having a mainline-grade USB gadget/peripheral > support needed by fastboot :) simply because we currently rely on > a "20 files changed, 6294 insertions(+)" driver from Renesas which > didn't undergo any deep review and is unlikely ready for upstreaming. > > FWIW my other wishes for R-Car3 are: > - Add fastboot support, which includes choosing a proper DRAM > address/size for the fastboot buffer (currently we make it > 16 MiB and place it at 0x4A000000) > - Add Android boot image support > - Define a flexible unified U-Boot environment which we see on other > platforms (e.g. TI), allowing users to boot Linux and Android from > various boot media without build-time tunables > - [KF-agnostic] Decrease the defconfig maintenance overhead as > discussed in a parallel thread > - [KF-agnostic] Build/boot U-Boot with UBSAN=y (there are issues) > - many others! Noted -- Best regards, Marek Vasut