From: Yao Zi <me@ziyao.cc>
To: Tom Rini <trini@konsulko.com>, Yao Zi <me@ziyao.cc>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v3 10/19] LoongArch: Boot Image bits
Date: Sat, 22 Aug 2026 17:52:14 +0000 [thread overview]
Message-ID: <aonhzngo6A-kZ9pF@pie> (raw)
In-Reply-To: <20260821162048.GN523975@bill-the-cat>
On Fri, Aug 21, 2026 at 10:20:48AM -0600, Tom Rini wrote:
> On Fri, Aug 21, 2026 at 08:42:10AM +0000, Yao Zi wrote:
>
> > From: Jiaxun Yang <jiaxun.yang@flygoat.com>
> >
> > Implement loading and booting functions for LoongArch
> > standard kernel image as per spec.
> >
> > LoongArch kernel do expect us to fake a efi systemtable
I occasionally noticed this typo ('a' -> 'an'), will fix it.
> > for passing fdt to kernel, we don't need to implement any
> > EFI functions for kernel because it won't look into anything
> > beside devicetree from that table if we tell kernel we are
> > not efi compatible by setting a0 boot argument to zero.
> >
> > Link: https://docs.kernel.org/arch/loongarch/booting.html
> > Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > Signed-off-by: Yao Zi <me@ziyao.cc>
> [snip]
> > diff --git a/arch/loongarch/Kconfig b/arch/loongarch/Kconfig
> > index ac4be2c837c0..5654de5a58c7 100644
> > --- a/arch/loongarch/Kconfig
> > +++ b/arch/loongarch/Kconfig
> > @@ -56,4 +56,7 @@ config STACK_SIZE_SHIFT
> > config OF_BOARD_FIXUP
> > default y if OF_SEPARATE
> >
> > +config LIB_BOOTM
> > + select CRC32
>
> If this is needed, it's a generic problem (and to be fixed outside this
> series) where LIB_BOOTM (and possibly LIB_BOOTI/Z since you know what to
> look for) need to select CRC32 and SPL_LIB_BOOTM SPL_CRC32. Thanks.
I think the dependency is specific to LoongArch, since CRC32 is
necessary only because we need to fake an EFI system table, which is
CRC32-checksum'ed, to pass FDT to the kernel on LoongArch. AFAIK other
architectures don't require such treatment, so I keep this
LoongArch-only.
Should I include a comment here to explain the dependency?
> --
> Tom
Regards,
Yao Zi
next prev parent reply other threads:[~2026-08-22 17:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 8:42 [PATCH v3 00/19] LoongArch initial support Yao Zi
2026-08-21 8:42 ` [PATCH v3 01/19] lib: fdtdec: Handle multiple memory nodes Yao Zi
2026-08-21 8:42 ` [PATCH v3 02/19] linux/io.h: Use map_physmem to implement ioremap Yao Zi
2026-08-21 8:42 ` [PATCH v3 03/19] image: Take entry point as an output of setup_booti Yao Zi
2026-08-21 16:20 ` Tom Rini
2026-08-21 8:42 ` [PATCH v3 04/19] elf: Define LoongArch bits Yao Zi
2026-08-21 8:42 ` [PATCH v3 05/19] image: Define IH_ARCH_LOONGARCH Yao Zi
2026-08-21 8:42 ` [PATCH v3 06/19] LoongArch: skeleton and headers Yao Zi
2026-08-21 8:42 ` [PATCH v3 07/19] LoongArch: lib: General routines Yao Zi
2026-08-21 8:42 ` [PATCH v3 08/19] LoongArch: CPU assembly routines Yao Zi
2026-08-21 8:42 ` [PATCH v3 09/19] LoongArch: Exception handling Yao Zi
2026-08-21 8:42 ` [PATCH v3 10/19] LoongArch: Boot Image bits Yao Zi
2026-08-21 16:20 ` Tom Rini
2026-08-22 17:52 ` Yao Zi [this message]
2026-08-22 19:03 ` Tom Rini
2026-08-22 19:06 ` Tom Rini
2026-08-22 20:47 ` Yao Zi
2026-08-21 8:42 ` [PATCH v3 11/19] LoongArch: Generic platform type Yao Zi
2026-08-21 8:42 ` [PATCH v3 12/19] cpu: Add loongarch_cpu driver Yao Zi
2026-08-21 8:42 ` [PATCH v3 13/19] timer: Add loongarch_timer driver Yao Zi
2026-08-21 8:42 ` [PATCH v3 14/19] board: emulation: Add qemu-loongarch Yao Zi
2026-08-21 16:20 ` Tom Rini
2026-08-22 20:40 ` Yao Zi
2026-08-22 20:51 ` Tom Rini
2026-08-21 8:42 ` [PATCH v3 15/19] efi: LoongArch: Define LoongArch bits everywhere Yao Zi
2026-08-21 8:42 ` [PATCH v3 16/19] efi: LoongArch: Implement everything Yao Zi
2026-08-21 8:42 ` [PATCH v3 17/19] doc: arch: Add documentation for LoongArch Yao Zi
2026-08-21 8:42 ` [PATCH v3 18/19] MAINTAINERS: Add entry " Yao Zi
2026-08-21 8:42 ` [PATCH v3 19/19] CI: Wire up qemu-loongarch64 Yao Zi
2026-08-21 16:21 ` 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=aonhzngo6A-kZ9pF@pie \
--to=me@ziyao.cc \
--cc=ilias.apalodimas@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=xypron.glpk@gmx.de \
/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.