ci: Include db410c support in the ARM container

Graphics / Mesa 3D Graphics Library / Mesa - Eric Anholt [anholt.net] - 27 February 2020 17:36 EST

I'm working on moving the db410c CI from docker to LAVA, which means we get to boot a custom kernel. To do that, we need to enable ARCH_QCOM in the kernel, save the dtb around, and include abootimg in our container so that we can generate combined kernel/dtb/ramdisk images for fastboot.

LAVA's fastboot support is unable to pack the overlay into an abootimg image, just a cpio rootfs. We could flash the cpio rootfs after overlay addition, but that takes 2 minutes to do, and causes wear on the devices. Instead, we'll bring up the network at boot and use wget to fetch the overlay. We'll want network support anyway, so that we can transfer the failure xmls back to the gitlab job's artifacts at some point.

Since the msm GPU and realtek network firmware increase our payload by 3MB, add in firmware compression so that it doesn't waste as much RAM on devices not using it.

33f38605e9a ci: Include db410c support in the ARM container.
.gitlab-ci.yml | 2 +-
.gitlab-ci/arm.config | 1 +
.gitlab-ci/arm64.config | 9 ++++++++-
.gitlab-ci/container/arm_build.sh | 2 ++
.gitlab-ci/container/lava_arm.sh | 11 +++++++++--
.gitlab-ci/create-rootfs.sh | 11 ++++++++---
6 files changed, 29 insertions(+), 7 deletions(-)

Upstream: cgit.freedesktop.org


  • Share