** Description changed:
[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.
+ * 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]
- TODO
+ * 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]
- TODO
+ 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.
** Also affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
** Also affects: raspi3-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805668
Title:
Building armhf and arm64 Raspberry Pi 3 images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
