public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: E Shattow <e@freeshell.de>
Cc: Minda Chen <minda.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v3 0/5] Add upstream board Xunlong Orange Pi RV
Date: Mon, 9 Feb 2026 19:18:16 +0800	[thread overview]
Message-ID: <aYnCeDTZDSiU3_7C@swlinux02> (raw)
In-Reply-To: <20260120155406.34916-1-e@freeshell.de>

On Tue, Jan 20, 2026 at 07:53:33AM -0800, E Shattow wrote:
> Xunlong Orange Pi RV patches are now in the Linux v6.19 release candidate,
> 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.
> 
> 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
> 
> Icenowy Zheng (2):
>   dt-bindings: riscv: starfive: add xunlong,orangepi-rv
>   riscv: dts: starfive: add Orange Pi 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 +++++++++
>  dts/upstream/Bindings/riscv/starfive.yaml     |  1 +
>  .../src/riscv/starfive/jh7110-orangepi-rv.dts | 76 +++++++++++++++++++
>  7 files changed, 119 insertions(+), 1 deletion(-)
>  create mode 100644 doc/board/starfive/orangepi_rv.rst
>  create mode 100644 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

      parent reply	other threads:[~2026-02-09 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 15:53 [PATCH v3 0/5] Add upstream board Xunlong Orange Pi RV E Shattow
2026-01-20 15:53 ` [PATCH v3 1/5] dt-bindings: riscv: starfive: add xunlong,orangepi-rv E Shattow
2026-01-20 15:53 ` [PATCH v3 2/5] riscv: dts: starfive: add Orange Pi RV E Shattow
2026-01-20 15:53 ` [PATCH v3 3/5] board: starfive: visionfive2: Add Orange Pi RV selection by product_id E Shattow
2026-01-20 15:53 ` [PATCH v3 4/5] configs: starfive: Add Orange Pi RV to visionfive2 E Shattow
2026-01-20 15:53 ` [PATCH v3 5/5] doc: board: starfive: Add Xunlong OrangePi RV E Shattow
2026-02-09 11:18 ` Leo Liang [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=aYnCeDTZDSiU3_7C@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=minda.chen@starfivetech.com \
    --cc=u-boot@lists.denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox