[U-Boot] [RFC] Extend 'bootm' to support Linux kernel generated images
Simon Glass
sjg at chromium.org
Tue Jun 3 19:01:21 CEST 2014
Hi Tom,
On 3 June 2014 10:59, Tom Rini <trini at ti.com> wrote:
> On Mon, Jun 02, 2014 at 07:11:14PM -0600, Simon Glass wrote:
>> Hi Tom,
>>
>> On 24 May 2014 06:21, Tom Rini <trini at ti.com> wrote:
>>
>> > On Fri, May 23, 2014 at 03:57:34PM -1000, Simon Glass wrote:
> [snip]
>> > > It surprises me the lengths to which people are going to try to
>> > > shoehorn .dtbs, compression, multiple dtbs, multi-arch etc. into the
>> > > kenel zImage format. The decompression header is ugly, plus it is
>> > > slower than doing these things in U-Boot.
>> >
>> > Well, with arm64 the kernel is just getting out of the business, hence
>> > booti (or however we add Image support) and not do the zImage dance.
>>
>> Does this mean a clean Image with no add-ons?
>
> Yes, Image only, and different from arch/arm/boot/Image. Leaving the
> details of how to find/place the device tree and initrd up to the
> bootloader.
That sounds promising. So no more decompression / serial UART /
cache-enable header?
Regards,
Simon
More information about the U-Boot
mailing list