[RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[Icenowy Zheng]

在 2025-11-26星期三的 15:42 -0800，E Shattow写道：
> 
> On 11/26/25 14:34, Heinrich Schuchardt wrote:
> > Am 26. November 2025 23:15:25 MEZ schrieb E Shattow
> > <e at freeshell.de>:
> > > Xunlong Orange Pi RV patches are now queued up for the next merge
> > > window
> > > to Linux v6.19, so let's introduce support for this board.
> > > 
> > > Note: The content of EEPROM is not known to be unique on this
> > > board, and
> > > in this RFC there is a placeholder value of "XOPIRV".
> > 
> > If OrangePi is not providing a unique value, shouldn't we create a
> > separate defconfig (including the vf2 one) and override the output
> > of the eeprom reading function by a configuration value?
> > 
> > That way we can reuse most code and avoid that users have to update
> > the EEPROM to "XOPIRV".
> > 
> > Best regards
> > 
> > Heinrich
> > 
> > > 
> > > E Shattow (4):
> > >  riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-
> > > next
> > >  board: starfive: visionfive2: Add Orange Pi RV selection by
> > > product_id
> > >  riscv: dts: Add placeholder files for pending upstream Orange Pi
> > > RV
> > >  configs: starfive: Add Orange Pi RV to visionfive2
> > > 
> > > arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76
> > > +++++++++++++++++++
> > > board/starfive/visionfive2/spl.c              |  3 +
> > > .../visionfive2/starfive_visionfive2.c        |  2 +
> > > configs/starfive_visionfive2_defconfig        |  2 +-
> > > .../src/riscv/starfive/jh7110-orangepi-rv.dts |  0
> > > 5 files changed, 82 insertions(+), 1 deletion(-)
> > > create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
> > > create mode 100644 dts/upstream/src/riscv/starfive/jh7110-
> > > orangepi-rv.dts
> > > 
> > > 
> > > base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9
> > 
> 
> Sure I'd like more testing data about these boards, I don't have the
> board myself so I don't know the answer to that.
> 
> What is the content of EEPROM, for reference?

```
root at opirv [ ~ ] # i2cdump 5 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-5, address 0x50, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 53 46 56 46 02 00 02 00 88 00 00 00 01 00 01 00    SFVF?.?.?...?.?.
10: 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    X...............
20: 00 00 00 00 00 00 00 00 20 20 53 74 61 72 46 69    ........  StarFi
30: 76 65 20 54 65 63 68 6e 6f 6c 6f 67 79 20 43 6f    ve Technology Co
40: 2e 2c 20 4c 74 64 2e 00 00 00 56 46 37 31 31 30    ., Ltd....VF7110
50: 42 31 2d 32 32 32 38 2d 44 30 30 34 45 30 30 30    B1-2228-D004E000
60: 2d 30 30 30 30 30 32 37 31 00 6d da 04 00 02 00    -00000271.m??.?.
70: 14 00 00 00 02 00 01 41 c0 74 2b fc f4 0e 6c cf    ?...?.?A?t+???l?
80: 39 00 00 00 00 00 f4 9e ff ff ff ff ff ff ff ff    9.....??........
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
```

>From my OPi RV, where the original Linux upstream DT is developed.

> 
> If it's all the same as VisionFive 2 and boots with dts from
> VisionFive
> 2 (1.3b?) then it might not be needed to do more than add
> documentation
> for the board to reference the VisionFive 2 and explain how to
> properly
> set fdtfile. Inventing a new board identifier when the manufacturer
> has
> not provided one sounds convenient to me, and it is not to the
> exclusion
> of a separate board config just for that special situation. The
> documentation can explain either or both situations, expanding how to
> compile for the board.
> 
> How does network and eMMC function with the series applied, not
> changing
> the EEPROM content (remains what I was understood is the same as
> VisionFive 2), and manually setting the fdtfile variable?
> 
> -E