From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: U-Boot Mailing List <u-boot@lists.u-boot-project.org>
Subject: Re: [PATCH v3 0/4] Spacemit K3 enable Linux boot
Date: Wed, 18 Nov 2026 07:32:03 +0000 [thread overview]
Message-ID: <20261118073203-GKC156369@kernel.org> (raw)
In-Reply-To: <20261116102653.36927-1-e@freeshell.de>
On 02:26 Mon 16 Nov , E Shattow wrote:
> Adopt some fixes needed for Linux v7.2.10+ boot and enable
> BOOTSTD_FULL together with minimal env addr variable defaults.
>
> Build and test only with vendor BSP k3-br-v1.0.10 having reduced [1]
> configuration to avoid a memory resource conflict. The vendor BSP SPL
> in its default configuration attempts to load opensbi separately from
> u-boot main app, and also attempts to load an embedded controller OS
> image, neither of which is useful for mainline opensbi, mainline
> Linux, and mainline U-Boot.
>
> Changes since v2:
> - Add patch 4/4 which adopts a proposed Linux series [2] to reduce the
> initial memory configuration to 8GiB for CoM260 and Pico-ITX boards
>
> 1: https://lore.kernel.org/u-boot/20261029003327.1890979-1-e@freeshell.de/
> 2: https://lore.kernel.org/linux-riscv/20261115195112.32120-1-e@freeshell.de/
>
> E Shattow (3):
> riscv: dts: spacemit: k3: override reserved status of mimsic and
> maplic
> configs: spacemit: k3: enable CONFIG_BOOTSTD_FULL
> riscv: dts: spacemit: k3: adopt com260/pico-itx 8gb memory override
>
> Junhui Liu (1):
> riscv: dts: spacemit: k3: Drop guest properties from M-level IMSIC
>
> arch/riscv/dts/k3-com260-ifx-u-boot.dtsi | 9 +++++++++
> arch/riscv/dts/k3-pico-itx-u-boot.dtsi | 9 +++++++++
> arch/riscv/dts/spacemit-k3-u-boot.dtsi | 4 ++++
> configs/spacemit_k3_defconfig | 9 +--------
> dts/upstream/src/riscv/spacemit/k3.dtsi | 2 --
> include/configs/spacemit-k3.h | 6 ++++++
> 6 files changed, 29 insertions(+), 10 deletions(-)
> create mode 100644 arch/riscv/dts/k3-com260-ifx-u-boot.dtsi
> create mode 100644 arch/riscv/dts/k3-pico-itx-u-boot.dtsi
>
For the series,
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-11-18 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 10:26 [PATCH v3 0/4] Spacemit K3 enable Linux boot E Shattow
2026-11-16 10:26 ` [PATCH v3 1/4] riscv: dts: spacemit: k3: override reserved status of mimsic and maplic E Shattow
2026-11-16 10:26 ` [PATCH v3 2/4] riscv: dts: spacemit: k3: Drop guest properties from M-level IMSIC E Shattow
2026-11-16 10:26 ` [PATCH v3 3/4] configs: spacemit: k3: enable CONFIG_BOOTSTD_FULL E Shattow
2026-11-16 10:26 ` [PATCH v3 4/4] riscv: dts: spacemit: k3: adopt com260/pico-itx 8gb memory override E Shattow
2026-11-18 7:32 ` Yixun Lan [this message]
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=20261118073203-GKC156369@kernel.org \
--to=dlan@kernel.org \
--cc=e@freeshell.de \
--cc=u-boot@lists.u-boot-project.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.