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

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.525.14

---------------
livecd-rootfs (2.525.14) bionic; urgency=medium

  * More changes for raspi3 build support (LP: #1805668):
    - Fix 100-purge-grub-legacy-ec2-arm.chroot to not gate on ARCH as that's
      not defined in .chroot hooks.
    - Use the new linux-firmware-raspi2 for boot binary blobs as
      raspi3-firmware includes upgrade hooks that conflict with our image
      configuration.

livecd-rootfs (2.525.13) bionic; urgency=medium

  [ Balint Reczey ]
  * Update Vcs-* fields in debian/control to point to git.

  [ Łukasz 'sil2100' Zemczak ]
  * Another batch of cherry-picks for raspi3 support (LP: #1805668)
    - Add wpasupplicant to the additional packages installed for the raspi2 and
      raspi3 targets.
    - Default to IMAGEFORMAT=ubuntu-image for raspi3 ubuntu-cpc builds.
    - Link the resulting raspi3 image to a filename that cdimage expects from a
      preinstalled image build.
  * Add the 100-purge-grub-legacy-ec2-arm.chroot hook to remove
    grub-legacy-ec2 from any ARM based ubuntu-cpc images we create. The package
    is no longer in the server seed of newer series anyway.

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com>  Fri, 18 Jan
2019 16:56:58 +0100

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
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 linux-firmware-raspi2 package in Ubuntu:
  New
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 linux-firmware-raspi2 source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  Fix Released
Status in raspi3-firmware source package in Bionic:
  Invalid
Status in u-boot source package in Bionic:
  Fix Released
Status in linux-firmware-raspi2 source package in Cosmic:
  Won't Fix
Status in livecd-rootfs source package in Cosmic:
  Won't Fix
Status in raspi3-firmware source package in Cosmic:
  Invalid
Status in u-boot source package in Cosmic:
  Fix Released

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.
   (vorlon) this should be updated specifically to the version of raspi3-firmware that we are using in the gadget snap - currently 1.20180919 - and not to another.

  [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/linux-firmware-raspi2/+bug/1805668/+subscriptions