[Bug 1811216] Re: Support both armhf and arm64 raspi3 in flash-kernel

[Brian Murray]

Hello Łukasz, or anyone else affected,

Accepted flash-kernel into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.90ubuntu3.18.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: flash-kernel (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Support both armhf and arm64 raspi3 in flash-kernel

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

Bug description:
  [Impact]

  Currently the boot.scr provided by flash-kernel for rpi3 uses bootz for booting the kernel, an uboot command that only works for armhf kernels. This means that in case the boot.scr on a pi3 arm64 gets updated on upgrade, the system will stop booting. Easiest way is to support separate bootscripts for arm64 and armhf.
  Also, to fully support all the strange cases for arm64, the boot address parameters need to be adjusted for a bigger kernel. The arm64 kernel, in contrast to the armhf one, is not compressed and takes up much more space in memory.

  This is basically only needed for bionic as we don't intend to build
  raspi3 images on cosmic, but SRUs will be provided for all series.

  [Test Case]

   * Boot up an arm64 based image on a raspi3 and log into it
   * Run flash-kernel
   * Check for errors
   * Check if /boot/firmware/boot.scr still has booti as its boot command
   * Reboot
   * Check if system still boots correctly

  [Regression Potential]

  The only regression potential is in actually making the image not
  booting, so running the SRU test case should validate that. There's
  basically no other regression potential I can think of.

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