From: Tom Rini <trini@konsulko.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Simon Glass <sjg@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-arm-kernel@lists.infradead.org,
U-Boot Mailing List <u-boot@lists.denx.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nick Terrell <terrelln@fb.com>,
Nicolas Schier <nicolas@fjasle.eu>, Will Deacon <will@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: boot: Support Flat Image Tree
Date: Mon, 30 Oct 2023 12:12:09 -0400 [thread overview]
Message-ID: <20231030161209.GU496310@bill-the-cat> (raw)
In-Reply-To: <ZT/NRvLkvR8uuP5+@shell.armlinux.org.uk>
On Mon, Oct 30, 2023 at 03:35:34PM +0000, Russell King (Oracle) wrote:
> On Sun, Oct 29, 2023 at 05:46:12AM +1300, Simon Glass wrote:
> > Hi Masahiro,
> >
> > Sure, but that is a separate issue, isn't it? We already support
> > various boot targets in arm64 but not one that includes the DTs, so
> > far as I can see. The old arm 'uImage' target is pretty out-of-date
> > now.
>
> Does that mean it can be removed? ;)
>
> I've NAK'd FIT support on 32-bit Arm in the past, and I remain of the
> opinion that boot loader specific packaging of the kernel should not
> be in the kernel but should be external to it - even more so given the
> multi-platform nature of 32-bit Arm kernels.
I'll point it out here rather than Simon. As part of
https://github.com/open-source-firmware FIT is a standard and not "boot
loader specific". And one of the points of a FIT image is that you can
easily support multi-platform kernels in a single file (without
optimizing things further, at a cost in tens of milliseconds on a Pi 3
anyhow) and with user-controlled security.
--
Tom
WARNING: multiple messages have this Message-ID (diff)
From: Tom Rini <trini@konsulko.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Simon Glass <sjg@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-arm-kernel@lists.infradead.org,
U-Boot Mailing List <u-boot@lists.denx.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nick Terrell <terrelln@fb.com>,
Nicolas Schier <nicolas@fjasle.eu>, Will Deacon <will@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: boot: Support Flat Image Tree
Date: Mon, 30 Oct 2023 12:12:09 -0400 [thread overview]
Message-ID: <20231030161209.GU496310@bill-the-cat> (raw)
In-Reply-To: <ZT/NRvLkvR8uuP5+@shell.armlinux.org.uk>
On Mon, Oct 30, 2023 at 03:35:34PM +0000, Russell King (Oracle) wrote:
> On Sun, Oct 29, 2023 at 05:46:12AM +1300, Simon Glass wrote:
> > Hi Masahiro,
> >
> > Sure, but that is a separate issue, isn't it? We already support
> > various boot targets in arm64 but not one that includes the DTs, so
> > far as I can see. The old arm 'uImage' target is pretty out-of-date
> > now.
>
> Does that mean it can be removed? ;)
>
> I've NAK'd FIT support on 32-bit Arm in the past, and I remain of the
> opinion that boot loader specific packaging of the kernel should not
> be in the kernel but should be external to it - even more so given the
> multi-platform nature of 32-bit Arm kernels.
I'll point it out here rather than Simon. As part of
https://github.com/open-source-firmware FIT is a standard and not "boot
loader specific". And one of the points of a FIT image is that you can
easily support multi-platform kernels in a single file (without
optimizing things further, at a cost in tens of milliseconds on a Pi 3
anyhow) and with user-controlled security.
--
Tom
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-30 16:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 7:26 [PATCH 0/3] arm64: Add a build target for Flat Image Tree Simon Glass
2023-10-26 7:26 ` Simon Glass
2023-10-26 7:26 ` [PATCH 1/3] kbuild: Correct missing architecture-specific hyphens Simon Glass
2023-10-26 7:26 ` Simon Glass
2023-10-28 9:50 ` Masahiro Yamada
2023-10-28 9:50 ` Masahiro Yamada
2023-10-28 16:00 ` Randy Dunlap
2023-10-28 16:00 ` Randy Dunlap
2023-10-26 7:26 ` [PATCH 2/3] kbuild: arm64: Add BOOT_TARGETS variable Simon Glass
2023-10-26 7:26 ` Simon Glass
2023-10-26 7:26 ` [PATCH 3/3] arm64: boot: Support Flat Image Tree Simon Glass
2023-10-26 7:26 ` Simon Glass
2023-10-26 13:24 ` Masahiro Yamada
2023-10-26 13:24 ` Masahiro Yamada
2023-10-28 16:46 ` Simon Glass
2023-10-28 16:46 ` Simon Glass
2023-10-30 15:35 ` Russell King (Oracle)
2023-10-30 15:35 ` Russell King (Oracle)
2023-10-30 16:12 ` Tom Rini [this message]
2023-10-30 16:12 ` Tom Rini
2023-10-31 7:03 ` Masahiro Yamada
2023-10-31 7:03 ` Masahiro Yamada
2023-10-31 11:46 ` Tom Rini
2023-10-31 11:46 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231030161209.GU496310@bill-the-cat \
--to=trini@konsulko.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sjg@chromium.org \
--cc=terrelln@fb.com \
--cc=u-boot@lists.denx.de \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.