linux-kernel - Re: uImage target support on arm64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180524213859.GA17671@n2100.armlinux.org.uk>
Date:   Thu, 24 May 2018 22:38:59 +0100
From:   Russell King - ARM Linux <linux@...linux.org.uk>
To:     Ramon Fried <ramon.fried@...il.com>
Cc:     Baruch Siach <baruch@...s.co.il>, catalin.marinas@....com,
        will.deacon@....com, open list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: uImage target support on arm64

On Thu, May 24, 2018 at 11:17:19PM +0300, Ramon Fried wrote:
> On Thu, May 24, 2018 at 10:34 PM, Baruch Siach <baruch@...s.co.il> wrote:
> > Hi Ramon,
> >
> > On Thu, May 24, 2018 at 10:05:15PM +0300, Ramon Fried wrote:
> >> I've noticed that it's not supported.
> >> Is it on purpose ?
> >
> > Yes. The 32bit load address in the uImage header in pretty limited when
> > applied to 64bit ARM64. Even for ARM zImage is the preferred kernel format for
> > quite some time now, since it allows flexible load address, as well as
> > multi-platform kernels.
> Hi Baruch.
> I though that in terms of U-boot, the new FIT image is the preferred
> kernel format.

u-boot keeps inventing new image formats for itself that are specific
to u-boot.  Not every boot loader is u-boot.

For 32-bit ARM, zImage has _always_ since day one been the preferred
format.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up