Building armhf and arm64 Raspberry Pi 3 images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-firmware-raspi2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
raspi3-firmware (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Cosmic |
Invalid
|
Undecided
|
Unassigned | ||
u-boot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
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+
* 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=
* Run a bionic livefs build of raspi3+arm64 with proposed enabled (IMAGEFORMAT=
* 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.
description: | updated |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Fix Released |
Changed in raspi3-firmware (Ubuntu): | |
status: | New → Fix Released |
Changed in u-boot (Ubuntu): | |
status: | New → Fix Released |
Changed in livecd-rootfs (Ubuntu Cosmic): | |
status: | New → Won't Fix |
description: | updated |
Changed in raspi3-firmware (Ubuntu Bionic): | |
milestone: | none → ubuntu-18.04.2 |
Changed in u-boot (Ubuntu Bionic): | |
milestone: | none → ubuntu-18.04.2 |
Changed in livecd-rootfs (Ubuntu Bionic): | |
milestone: | none → ubuntu-18.04.2 |
Changed in linux-firmware-raspi2 (Ubuntu): | |
status: | New → Fix Released |
I have skipped uploading the livecd-rootfs changes for cosmic as we are not planning on enabling raspi3 images for this distro-series as far as I know. This package is only used during build time so there is no reason to worry about missing functionality.