From: E Shattow <e@freeshell.de>
To: Minda Chen <minda.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
Leo Liang <ycliang@andestech.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, E Shattow <e@freeshell.de>
Subject: [RESEND PATCH v4 0/3] Add upstream board Xunlong Orange Pi RV
Date: Thu, 5 Mar 2026 09:00:19 -0800 [thread overview]
Message-ID: <20260305170043.33994-1-e@freeshell.de> (raw)
Xunlong Orange Pi RV patches are now in the Linux v6.19 release, so let's
introduce support for this board.
Note: The content of EEPROM is known to not be unique on this board, and
an (optional) invented "XOPIRV" identifier is implemented with this
series. Without, there are reports that the board is detected in U-Boot as
StarFive VisionFive 2 1.3b, and is then functional enough to load the
devicetree prior to booting Linux.
RESEND v4: has collected tags that were missing from v4 as sent to list
Changes since v3:
- Collect tags (no code changes) [n.b. this failed, see RESEND v4 instead]
- Cherry-picked dts subtree patches dropped as redundant:
Drop patch 1/5 "dt-bindings: riscv: starfive: add xunlong,orangepi-rv"
Drop patch 2/5 "riscv: dts: starfive: add Orange Pi RV"
Changes since v2:
- Collect tags (no code changes)
- Adjust missing S-o-by tag to first of tags list order for patch 4
"configs: starfive: Add Orange Pi RV to visionfive2".
Changes since RFC v1:
- Cherrypick from devicetree-rebasing instead of importing upstream dts
as -u-boot.dtsi overrides.
- Add basic documentation
- Mention invented "XOPIRV" identifier in commit messages
- Rebase on origin/next
E Shattow (3):
board: starfive: visionfive2: Add Orange Pi RV selection by product_id
configs: starfive: Add Orange Pi RV to visionfive2
doc: board: starfive: Add Xunlong OrangePi RV
board/starfive/visionfive2/spl.c | 3 ++
.../visionfive2/starfive_visionfive2.c | 2 ++
configs/starfive_visionfive2_defconfig | 2 +-
doc/board/starfive/index.rst | 1 +
doc/board/starfive/orangepi_rv.rst | 35 +++++++++++++++++++
5 files changed, 42 insertions(+), 1 deletion(-)
create mode 100644 doc/board/starfive/orangepi_rv.rst
base-commit: c0ca147ac6228949a6d6497531c9f2f4a0dc6c67
--
2.50.0
next reply other threads:[~2026-03-05 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:00 E Shattow [this message]
2026-03-05 17:00 ` [RESEND PATCH v4 1/3] board: starfive: visionfive2: Add Orange Pi RV selection by product_id E Shattow
2026-03-05 17:00 ` [RESEND PATCH v4 2/3] configs: starfive: Add Orange Pi RV to visionfive2 E Shattow
2026-03-05 17:00 ` [RESEND PATCH v4 3/3] doc: board: starfive: Add Xunlong OrangePi RV E Shattow
2026-03-12 8:19 ` [RESEND PATCH v4 0/3] Add upstream board Xunlong Orange Pi RV E Shattow
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=20260305170043.33994-1-e@freeshell.de \
--to=e@freeshell.de \
--cc=hal.feng@starfivetech.com \
--cc=minda.chen@starfivetech.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.com \
/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