Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
Date:   Wed, 29 Nov 2023 15:10:09 -0500
From:   Tom Rini <trini@konsulko.com>
To:     Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc:     Simon Glass <sjg@chromium.org>,
        linux-arm-kernel@lists.infradead.org,
        Masahiro Yamada <masahiroy@kernel.org>,
        lkml <linux-kernel@vger.kernel.org>,
        U-Boot Mailing List <u-boot@lists.denx.de>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Nathan Chancellor <nathan@kernel.org>,
        Nick Terrell <terrelln@fb.com>,
        Nicolas Schier <nicolas@fjasle.eu>,
        Will Deacon <will@kernel.org>, linux-kbuild@vger.kernel.org,
        Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v7 2/2] arm64: boot: Support Flat Image Tree
Message-ID: <20231129201009.GO2513409@bill-the-cat>
References: <20231129172200.430674-1-sjg@chromium.org>
 <20231129172200.430674-3-sjg@chromium.org>
 <30f32467-51ea-47de-a272-38e074f4060b@pengutronix.de>
 <20231129190220.GN2513409@bill-the-cat>
 <62e767da-5e4f-4b92-a5c9-5d523896d68e@pengutronix.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="upRn5Ae3/4tCAJ9Z"
Content-Disposition: inline
In-Reply-To: <62e767da-5e4f-4b92-a5c9-5d523896d68e@pengutronix.de>
Precedence: bulk


--upRn5Ae3/4tCAJ9Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 29, 2023 at 08:16:20PM +0100, Ahmad Fatoum wrote:
> Hello Tom,
>=20
> On 29.11.23 20:02, Tom Rini wrote:
> > On Wed, Nov 29, 2023 at 07:59:00PM +0100, Ahmad Fatoum wrote:
> >> Hi,
> >>
> >> a few more comments after decompiling the FIT image:
> >>
> >> On 29.11.23 18:21, Simon Glass wrote:
> >>> +    with fsw.add_node('kernel'):
> >>> +        fsw.property_string('description', args.name)
> >>> +        fsw.property_string('type', 'kernel_noload')
> >>
> >> The specification only says no loading done, but doesn't explain what =
it
> >> means for a bootloader to _not_ load an image. Looking into the U-Boot=
 commit
> >> b9b50e89d317 ("image: Implement IH_TYPE_KERNEL_NOLOAD") that introduce=
s this,
> >> apparently no loading means ignoring load and entry address?
> >>
> >> I presume missing load and entry is something older U-Boot versions
> >> were unhappy about? Please let me know if the semantics are as I under=
stood,
> >> so I can prepare a barebox patch supporting it.
> >=20
> > So the matching side for this series in U-Boot is:
> > https://patchwork.ozlabs.org/project/uboot/list/?series=3D382849&state=
=3D*
> >=20
> > And in short, for IH_TYPE_KERNEL_NOLOAD we do our best to use it
> > in-place. For decompression we allocate some space to decompress to.
>=20
> Thanks. I am still curious why "kernel" couldn't have been used back then
> with missing entry and load address to arrive at the same result?

Some level or another of historical oversight, yeah.

--=20
Tom

--upRn5Ae3/4tCAJ9Z
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAmVnmpoACgkQFHw5/5Y0
tyzzPQv/T8LXUXPqwGoY3YrFdNeX1WZi9rMh14B6pOopoK3qGJJNFa4mnkbQVoh7
gqLKSw9504+kra8XSpnVgy4U0EDBw9f4YKceXrB4n+afk8Ekgt+Qlj4+Cc3MhxvE
VNB006Qxd2fitSUXrvskfyRbn9lEwY8yvKKccd9yEYWjouIK4VzERemejViQsFVY
chJrr1kYTMbys9VNx1a2d4dXfkzu+njkmeR6+SySeITyOyQQjvu8uYmijbG95cEd
hRZn7zbYy8uWO9h2lvtVRBzWWxwAip35RxgL//FWUib3Ge46h85T3SVLs48k6cSW
1BEesLSpxUqz6OllGSviBLPPkcmY2qXQVNDzKalpSSC2JJRtx1HRnGEqcugJpBRH
wGOxa0mmc7QZgFUFqjc5/i2E9X/pn4MBapWLIfecBvy8KdyGADKkWvUG7Y4lpIvz
7QytagHjDQs1bFr88tSgXITHYlLipkr5nGN6/KN0GI/gtlbTBYBYrxB+O+705BgR
h+03xQrY
=HJAr
-----END PGP SIGNATURE-----

--upRn5Ae3/4tCAJ9Z--