[Bug 2110301] Re: [SRU] Backport u-boot 2025.01-3 to Noble

[Dave Jones]

Targetting to noble .3; leaving oracular as that will be EOL before
noble's .3 is release. Marking invalid in devel as this bug is purely
for backport purposes

** Also affects: u-boot (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: u-boot (Ubuntu)
       Status: New => Invalid

** Changed in: u-boot (Ubuntu Noble)
       Status: New => Confirmed

** Changed in: u-boot (Ubuntu Noble)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: u-boot (Ubuntu)
     Assignee: Dave Jones (waveform) => (unassigned)

** Changed in: u-boot (Ubuntu Noble)
    Milestone: None => ubuntu-24.04.3

-- 
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/2110301

Title:
  [SRU] Backport u-boot 2025.01-3 to Noble

Status in u-boot package in Ubuntu:
  Invalid
Status in u-boot source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  With the release of Ubuntu 25.04 (Plucky) we support new RISC-V
  hardware:

  * Pine64 Star64
  * DeepComputing FML13V01

  In the 25.10 cycle we will upgraded the ISA from RVA20 to presumably
  RVA23. This implies that hardware that is not RVA23 compliant will
  only be supported on 24.04 in the long term.

  We therefore need to backport the hardware support to 24.04. This
  includes:

  * U-Boot
  * Kernel 6.14

  With this SRU we will backport U-Boot 2025.01-3 to Noble.

  [ Test Plan ]

  Install the updated U-Boot and check booting on the following boards:

  DeepComputing FML13V01
  Microchip Icicle Kit
  Milk-V Mars
  Pine64 Star64
  StarFive VisionFive 2
  SiFive Unmatched

  Check that U-Boot's variable $fdtfile shows the value matching the board.
  (With the current U-Boot on Noble this will not work for the FML13V01 and Pine64 Star64.)

  Check that booting via GRUB into Ubuntu works.

  See the descriptions in the Ubuntu manual tests for the respective
  boards.

  For testing best use preinstalled Plucky images which will have the
  matching kernel.

  [ Where problems could occur ]

  The wrong device-tree might be loaded.

  Booting might fail.

  [ Other Info ]

  N/A

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