From: Leo Liang <ycliang@andestech.com>
To: <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>, <ycliang@andestech.com>
Subject: [PULL] u-boot-riscv/next
Date: Thu, 21 Sep 2023 09:28:46 +0800 [thread overview]
Message-ID: <ZQucTuzK1hvN9NMl@swlinux02> (raw)
Hi Tom,
The following changes since commit c58ee1c9946a1550b1f6fee2b25da9ecc89baf71:
Merge branch '2023-09-19-tidy-up-some-kconfig-options' into next (2023-09-19 17:44:18 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-riscv.git next
for you to fetch changes up to 90602e779d3ae3bd02faae0eb40b4fcefec419f7:
riscv: dts: starfive: generate u-boot-spl.bin.normal.out (2023-09-20 21:05:16 +0800)
CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/17779
----------------------------------------------------------------
+ Add NVMe & USB boot devices for VisionFive2
+ Add StarFive SPL image support in mkimage tool
----------------------------------------------------------------
Heinrich Schuchardt (4):
riscv: set fdtfile on VisionFive 2
configs: NVMe/USB target boot devices on VisionFive 2
tools: mkimage: Add StarFive SPL image support
riscv: dts: starfive: generate u-boot-spl.bin.normal.out
Milan P. Stanić (1):
starfive: visionfive2: add mmc0 and nvme boot targets
arch/riscv/Kconfig | 1 +
.../dts/jh7110-starfive-visionfive-2-u-boot.dtsi | 11 ++
board/starfive/visionfive2/starfive_visionfive2.c | 43 ++++-
boot/image.c | 1 +
doc/board/starfive/visionfive2.rst | 14 +-
include/configs/starfive-visionfive2.h | 3 +
include/image.h | 1 +
tools/Makefile | 1 +
tools/sfspl.c | 174 +++++++++++++++++++++
9 files changed, 235 insertions(+), 14 deletions(-)
create mode 100644 tools/sfspl.c
Best regards,
Leo
next reply other threads:[~2023-09-21 1:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 1:28 Leo Liang [this message]
2023-09-21 19:56 ` [PULL] u-boot-riscv/next Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2025-06-03 6:45 Leo Liang
2025-06-05 20:05 ` Tom Rini
2025-06-08 2:37 ` Yao Zi
2025-06-09 8:04 ` Leo Liang
2025-06-30 12:02 ` Leo Liang
2024-09-12 6:39 Leo Liang
2024-09-12 17:44 ` Tom Rini
2022-09-26 7:39 Leo Liang
2022-09-27 12:53 ` Tom Rini
2021-06-16 7:44 Leo Liang
2021-06-16 8:07 ` Bin Meng
2021-06-16 8:28 ` Leo Liang
2021-06-16 12:06 ` 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=ZQucTuzK1hvN9NMl@swlinux02 \
--to=ycliang@andestech.com \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox