[Bug 2121690] Re: Add support for RISC-V StarFive VisionFive 2 Lite

[Dave Jones]

** Description changed:

  [ Impact ]
  
  The StarFive VisionFive 2 Lite is a new RISC-V development board based
- on a JH7710S CPU.
- 
- We want to enable this board in Ubuntu 24.04.
+ on a JH7710S CPU. We want to enable this board in Ubuntu 24.04 as part
+ of our support for RVA20 devices via the current LTS.
  
  The required changes in U-Boot are mostly on the device-tree side. There
  is a minor addition in the PCI driver to allow for an enablement GPIO.
  
  None of the JH7710 based devices is supporting RVA23. So this change
  does not require a feature freeze exception for release 25.10.
  
  [ Test Plan ]
  
- Test booting on all supported JH7710 and JH7710S based devices.
+ The following test plan requires some familiarity with the u-boot
+ console, and the specific boot processes for the devices to be tested.
+ For every supported $device, in all affected $series:
+ 
+ * Flash or install appropriate image for $series on $device
+ * Boot the device from cold
+ * Interrupt u-boot and check reading from SD-card, eMMC and from NVMe (where applicable); use mmc, usb, and fatls commands as required
+ * Check networking; use dhcp, tftpboot commands as required
+ * Boot the OS fully
+ * Login, then test "sudo reboot"
+ * Ensure OS boots fully again
+ 
+ At a bare minimum the following devices MUST be tested:
  
  * Milk-V Mars
  * StarFive Vision Five 2
  * StarFive Vision Five 2 Lite
  * Pine64 Star64
  * DeepComputing FML13V01
  
- In U-Boot check
+ The following devices SHOULD additionally be tested:
  
- * reading from SD-card, eMMC and from NVMe (where applicable)
- * networking (DHCP, tftp)
+ * QEMU on arm64, and riscv64 archs
+ * Raspberry Pi 3 series
+ * Raspberry Pi 4 series
  
  [ Where problems could occur ]
  
- The device-tree changes might lead to boot failures on other JH7110
- based devices.
+ SRU'ing a new version of the bootloader carries obvious risks of
+ breaking the boot on any board using it. At present, the only official
+ Ubuntu images using u-boot are the RISC-V images, hence the requirement
+ to test them.
  
- [ Other Info ]
+ However, u-boot has other uses in a wide variety of hardware, hence we
+ should also test any other hardware available to us that can use u-boot
+ (this is why QEMU and certain raspi [1] boards are on the list)
  
- n/a
+ Testing can be limited to boot and reboot functionality as the
+ bootloader plays no role the in the system at runtime.
+ 
+ [1] We transitioned away from u-boot on the raspi images back in focal,
+ but it should still theoretically run. In case anyone is relying on this
+ for other purposes, we should put it through its paces on the
+ historically supported models.

** Summary changed:

- Add support for RISC-V StarFive VisionFive 2 Lite
+ [SRU] Add support for RISC-V StarFive VisionFive 2 Lite

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/2121690

Title:
  [SRU] Add support for RISC-V StarFive VisionFive 2 Lite

Status in u-boot package in Ubuntu:
  Fix Released
Status in u-boot source package in Noble:
  New
Status in u-boot source package in Plucky:
  New
Status in u-boot source package in Questing:
  New

Bug description:
  [ Impact ]

  The StarFive VisionFive 2 Lite is a new RISC-V development board based
  on a JH7710S CPU. We want to enable this board in Ubuntu 24.04 as part
  of our support for RVA20 devices via the current LTS.

  The required changes in U-Boot are mostly on the device-tree side.
  There is a minor addition in the PCI driver to allow for an enablement
  GPIO.

  None of the JH7710 based devices is supporting RVA23. So this change
  does not require a feature freeze exception for release 25.10.

  [ Test Plan ]

  The following test plan requires some familiarity with the u-boot
  console, and the specific boot processes for the devices to be tested.
  For every supported $device, in all affected $series:

  * Flash or install appropriate image for $series on $device
  * Boot the device from cold
  * Interrupt u-boot and check reading from SD-card, eMMC and from NVMe (where applicable); use mmc, usb, and fatls commands as required
  * Check networking; use dhcp, tftpboot commands as required
  * Boot the OS fully
  * Login, then test "sudo reboot"
  * Ensure OS boots fully again

  At a bare minimum the following devices MUST be tested:

  * Milk-V Mars
  * StarFive Vision Five 2
  * StarFive Vision Five 2 Lite
  * Pine64 Star64
  * DeepComputing FML13V01

  The following devices SHOULD additionally be tested:

  * QEMU on arm64, and riscv64 archs
  * Raspberry Pi 3 series
  * Raspberry Pi 4 series

  [ Where problems could occur ]

  SRU'ing a new version of the bootloader carries obvious risks of
  breaking the boot on any board using it. At present, the only official
  Ubuntu images using u-boot are the RISC-V images, hence the
  requirement to test them.

  However, u-boot has other uses in a wide variety of hardware, hence we
  should also test any other hardware available to us that can use
  u-boot (this is why QEMU and certain raspi [1] boards are on the list)

  Testing can be limited to boot and reboot functionality as the
  bootloader plays no role the in the system at runtime.

  [1] We transitioned away from u-boot on the raspi images back in
  focal, but it should still theoretically run. In case anyone is
  relying on this for other purposes, we should put it through its paces
  on the historically supported models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2121690/+subscriptions