[Bug 2121785] Re: [SRU] Support StarFive VisionFive 2 Lite

[Launchpad Bug Tracker]

This bug was fixed in the package opensbi - 1.7-1~25.10.1

---------------
opensbi (1.7-1~25.10.1) questing; urgency=medium

  * Backport of 1.7-1 to support StarFive VisionFive 2 Lite (LP:
#2121785)

opensbi (1.7-1) unstable; urgency=medium

  * New upstream release.

  [ Vagrant Cascadian ]
  * debian/copyright: Update for v1.7.

  [ Valentin Haudiquet ]
  * debian/copyright: Fix old-fsf-address-in-copyright-file
  * d/patches: Include gcc swap error bugfix from upstream
  * d/patches: Include jh7110s board support from upstream

  [ Vagrant Cascadian ]
  * debian/control: Update to Standards-Version 4.7.2.

 -- Dave Jones <dave.jones at canonical.com>  Mon, 01 Dec 2025 14:09:03
+0000

** Changed in: opensbi (Ubuntu Questing)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] Support StarFive VisionFive 2 Lite

Status in opensbi package in Ubuntu:
  Fix Released
Status in opensbi source package in Noble:
  Fix Released
Status in opensbi source package in Plucky:
  Fix Released
Status in opensbi source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

  The StarFive VisionFive 2 Lite is a new RISC-V RVA20 board that we can
  support with Ubuntu 24.04 (the release we are using for ongoing
  support of RVA20, given that questing onwards will be restricted to
  RVA23).

  The board features a JH7710S SoC which only differs from the JH7710 by
  the allowable CPU frequency and temperature range. To make OpenSBI
  recognize the board the compatibility string of the new SoC needs to
  be added to OpenSBI 1.7:

  diff --git a/platform/generic/starfive/jh7110.c b/platform/generic/starfive/jh7110.c
  index 4163e416..c1328437 100644
  --- a/platform/generic/starfive/jh7110.c
  +++ b/platform/generic/starfive/jh7110.c
  @@ -322,6 +322,7 @@ static int starfive_jh7110_platform_init(const void *fdt, int nodeoff,

   static const struct fdt_match starfive_jh7110_match[] = {
          { .compatible = "starfive,jh7110" },
  +       { .compatible = "starfive,jh7110s" },
          { },
   };

  This change is already present in 1.7-1 in resolute. We will execute
  the change in Questing, Plucky, Noble to keep the code the same but as
  the new board will not be supported in Questing no feature freeze
  exception is needed.

  [ Test Plan ]

  For each backported $series (questing, plucky, noble), for each
  potentially affected $board supported by $series (see
  https://ubuntu.com/download/risc-v/canonical-built for definitions):

  * Flash image for $board to appropriate storage (see board specific instructions [2] if required).
  * Build U-Boot for the board using the updated OpenSBI with SBI sysreset being the only sysreset driver
  * Update U-boot
  * Test that the 'reset' command reboots the board.

  [1]: https://ubuntu.com/download/risc-v/canonical-built

  [2]: https://canonical-ubuntu-boards.readthedocs-
  hosted.com/en/latest/how-to/

  [ Where problems could occur ]

  This backport potentially upgrades a part of the bootloader on all
  RISC-V boards supported, hence the test plan ensures that (re)boot is
  not affected on all such boards. Note that only RISC-V boards are
  potentially affected so testing is limited to this architecture.

  One potential hole in testing is that questing (25.10) cannot be
  tested on actual hardware. We require RVA23 in questing, and no RVA23
  hardware yet exists, so the only testing that can be done is in QEMU.
  However, this also means no actual hardware can be regressed by this
  change, hence the risk of regression in questing at least is minimal.

  [ Other Info ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/2121785/+subscriptions