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

[Steve Langasek]

On Tue, Dec 04, 2018 at 09:49:17AM -0000, Adam Smith wrote:
> To answer the description update by vorlon: The raspi3-firmware package
> contains scripts that get run on a kernel update.  This creates a new
> config.txt and makes copies of kernel/dtb etc.  Pretty certain this is
> not how gadget snaps work (the firmware is obtained directly from git is
> it not?).  U-boot will be by-passed by raspi3-firmware.

The fact that gadget snaps don't use the same scripts as contained in the
raspi3-firmware package is orthogonal to the question of keeping Ubuntu Core
and Ubuntu Classic in sync with respect to the firmware bits being used.

-- 
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:
  Fix Committed
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.
   (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/livecd-rootfs/+bug/1805668/+subscriptions