[Bug 1997371] Re: [SRU] add Sipeed Lichee RV Dock and Microchip PolarFire-SoC Icicle Kit in Jammy

[Heinrich Schuchardt]

Tested flash-kernel-2022.01+dfsg-2ubuntu2.1 successfully on Jammy

The debdiff contains only additions to db/all.db. No deletions.

On the PolarFire Icicle Kit board device-tree microchip/mpfs-icicle-
kit.dtb is copied to /boot/dtbs and linked correctly. Reboot with the
device-tree is successful.

On the Sipeed Lichee RV Dock board device-tree
allwinner/sun20i-d1-lichee-rv-dock.dtb is copied to /boot/dtbs and
linked correctly. Reboot with the device-tree is successful.

On the SiFive HiFive Unmatched board device-tree sifive/hifive-
unmatched-a00.dtb is copied to /boot/dtbs and linked correctly. Reboot
with the device-tree is successful.

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

Title:
  [SRU] add Sipeed Lichee RV Dock and Microchip PolarFire-SoC Icicle Kit
  in Jammy

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  Flash-kernel only supports boards maintained in the db/all.db
  database.

  We want to be able to support the 'Sipeed Lichee RV Dock' and the
  'PolarFire Icicle Kit' in Jammy.

  The database entries are copied from the Lunar/Kinetic version for the
  package.

  [ Test Plan ]

  As the database entries are the same as in Kinetic they already
  received some testing.

  Check that no entry is deleted in the database.

  Boot the LicheeRV board using the 22.04 Nezha image. Set
  /etc/flashkernel/machine to 'Sipeed Lichee RV Dock'. Reboot the board.
  Check that /proc/devic-tree/model has the value 'Sipeed Lichee RV
  Dock'.

  Boot the PolarFire Icicle Kit. Set /etc/flashkernel/machine to
  'Microchip PolarFire-SoC Icicle Kit'. Reboot the board. Check that
  /proc/devic-tree/model has the value 'Microchip PolarFire-SoC Icicle
  Kit'.

  [ Where problems could occur ]

  We could by mistake delete entries for other boards in the database.

  We could create a database file that flash-kernel cannot parse.

  This could lead to errors in booting other systems.

  Both causes are not probable as we copy the entries from Kinetic where
  testing already has occurred.

  [ Other Info ]

  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1997371/+subscriptions