[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images

[Adam Smith]

I don't agree with the alterations to u-boot either.  Arm64 doesn't need
to be called kernel8.img.  The config.txt should be changed to tell the
pi's bootloader to expect aarch64.  That way you can keep the uboot.bin
name and it is consistent between armhf and arm64.


This bug fails to address flash-kernel which is the major problem with the ubuntu setup.  raspi3-firmware is not the answer - it is awful.  What is required is a new package with simplified scripts that replaces Linux-firmware-raspi2.  Making big changes to existing packages is very risky.


Before backporting any changes to bionic please be aware of how people are using Ubuntu - https://wiki.ubuntu.com/ARM/RaspberryPi .  Different versions of u-boot could be used, requiring different FDT addresses.  Or more likely, u-boot is not used at all.  Previously updates to u-boot/flash-kernel/Linux-firmware-raspi2 have caused major problems (e.g. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270 ).  We definitely don't want some packages postinst script messing with config.txt.

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

Title:
  Building armhf and arm64 Raspberry Pi 3 images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in raspi3-firmware package in Ubuntu:
  Fix Released
Status in u-boot package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  New
Status in raspi3-firmware source package in Bionic:
  New
Status in u-boot source package in Bionic:
  New
Status in livecd-rootfs source package in Cosmic:
  Won't Fix
Status in raspi3-firmware source package in Cosmic:
  New
Status in u-boot source package in Cosmic:
  New

Bug description:
  [Impact]

  One of our long-term goals is to support the same set of platforms for both classical Ubuntu and ubuntu-core. We currently provide official images for the Raspberry Pi 3 for both the core16 and core18 bases but do not provide the same for Ubuntu classic.
  Since it's a 'feature' we're essentially lacking since long, we want to have the new device also supported in our current LTS (bionic).

  [Fix]

  For the classic raspi3 support we will be using the ubuntu-image classic image building tool which is specifically designed for creating preinstalled images. The support for that has already been SRUed in the latest ubuntu-image.
  For the full image build support to be complete, the following list of changes need to be backported (SRUed) into the respective stable series:

   * livecd-rootfs - all the changes regarding classic image build, gadget tree selection and raspi3 rootfs generation.
   * u-boot - bionic will need to be updated to at least 2018.03+dfsg1-2ubuntu2.
   * raspi3-firmware (bionic only) - needs to be updated to at least the version we have in cosmic. Without this change, the console is flooded with firmware error messages every 2 seconds.

  [Test Case]

   * Run a bionic livefs build of raspi3+armhf with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Run a bionic livefs build of raspi3+arm64 with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
   * Make sure that none of the other bionic daily images fail to build

  [Regression Potential]

  There is some potential that an invalid backport of livecd-rootfs
  functionality could result in the inability to create new ubuntu-core
  images or any of the other existing flavors. But in case of such a
  regression we would see it instantly after the package lands in
  bionic-proposed as we are building daily images with -proposed
  enabled. As for the other packages, there probably is some regression
  potential, but since the versions are backports from disco/cosmic, the
  risk is probably very small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions