From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: u-boot@lists.u-boot-project.org, Yao Zi <me@ziyao.cc>,
Tim Ouyang <tim609@andestech.com>,
Leo Liang <leo.liang@sifive.com>, Tom Rini <trini@konsulko.com>,
Michal Simek <michal.simek@amd.com>,
Raymond Mao <raymond.mao@riscstar.com>,
Hiago De Franco <hfranco@baylibre.com>,
Junhui Liu <junhui.liu@pigmoral.tech>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH 0/4] riscv: spacemit: Add support for K3 Pico-ITX board
Date: Thu, 1 Oct 2026 11:19:04 +0000 [thread overview]
Message-ID: <20261001111904-GKA51329@kernel.org> (raw)
In-Reply-To: <b9150c66-37f2-4348-98c4-92e5764e74bc@freeshell.de>
Hi E Shattow,
On 22:26 Thu 24 Sep , E Shattow wrote:
> Hi Yixun, Add CC: Aurelien (per our chat about DMI on K3 and Debian d-i
> you may find this interesting)
>
> I have included my report of testing this series with step-by-step build
> instructions, after the reply-quote. I was not successful to boot Debian
> daily netinst debian-installer ramdisk. However, as an aside, I did
> produce build instructions that result in the vendor u-boot v2022.10
> fork with additional fixes that is successful when flashed to SPI NOR to
I've not tested with SPI NOR, just using fastboot
> run netinst debian-installer and that success is measured as my baseline
> for comparison. I omit my T-by tag for this series until it goes through
> a few revisions and I understand better what your goals are if it should
> be successful to boot and run debian-installer for example. -E
>
My current goal here is getting a basically functional mainline U-Boot
(with the network/ethernet support), as for booting mainline opensbi + kernel,
a few patches[1] still needed, e.g for opensbi, and the address overlap issue
also need to be fixed..
FYI, I've put all patches together and push a branch here[2], for people
who interested to test, some patches are just a quick hack and need to
improve later..
[1] https://patch.msgid.link/20260729-k3-mimsic-fix-v1-1-368c0aec04b9@pigmoral.tech
https://patch.msgid.link/20260918-k3-aclint-v3-6-cf4fd4050e14@pigmoral.tech
https://patch.msgid.link/20260817033038.2286436-1-guoren@kernel.org
[2] https://github.com/spacemit-com/u-boot/commits/k3/for-next
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-10-01 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:46 [PATCH 0/4] riscv: spacemit: Add support for K3 Pico-ITX board Yixun Lan
2026-09-23 12:46 ` [PATCH 1/4] board: spacemit: add SpacemiT K3 Pico-ITX Yixun Lan
2026-09-23 18:00 ` Yao Zi
2026-09-24 1:21 ` Yixun Lan
2026-09-23 12:46 ` [PATCH 2/4] riscv: dts: spacemit: k3: add binman node Yixun Lan
2026-09-23 12:46 ` [PATCH 3/4] configs: spacemit: Add K3 default configuration Yixun Lan
2026-09-23 12:46 ` [PATCH 4/4] doc: spacemit: k3: Add Pico-ITX board Yixun Lan
2026-09-25 5:26 ` [PATCH 0/4] riscv: spacemit: Add support for K3 " E Shattow
2026-10-01 11:19 ` 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=20261001111904-GKA51329@kernel.org \
--to=dlan@kernel.org \
--cc=aurelien@aurel32.net \
--cc=e@freeshell.de \
--cc=hfranco@baylibre.com \
--cc=junhui.liu@pigmoral.tech \
--cc=leo.liang@sifive.com \
--cc=me@ziyao.cc \
--cc=michal.simek@amd.com \
--cc=raymond.mao@riscstar.com \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox