[U-Boot] [RFC] Extend 'bootm' to support Linux kernel generated images

[Tom Rini]

On Tue, Jun 03, 2014 at 11:01:21AM -0600, Simon Glass wrote:
> 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?

For the time being, yes.  We'll see what happens when more people are
using real hardware rather than simulator and not the boot-wrapper tool.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140603/d06c7211/attachment.pgp>