From e8da28d5e88308e7381af74315fde6383de96292 Mon Sep 17 00:00:00 2001 From: Emma Anholt Date: Sun, 23 Jan 2022 21:39:02 -0800 Subject: [PATCH] docs/ci: Update some bare-metal CI docs. We haven't been using initramfs in a long time, don't point people that direction. Do point people at existing instances of these CI variants, though. Reviewed-by: Christian Gmeiner Part-of: --- docs/ci/bare-metal.rst | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/docs/ci/bare-metal.rst b/docs/ci/bare-metal.rst index 5cb192e78fa..28c98c6da60 100644 --- a/docs/ci/bare-metal.rst +++ b/docs/ci/bare-metal.rst @@ -25,11 +25,17 @@ should probably have the console on a serial connection, so that you can see bootloader progress. The boards need to be able to have a kernel/initramfs supplied by the -gitlab-runner system, since the initramfs is what contains the Mesa -testing payload. +gitlab-runner system, since Mesa often needs to update the kernel either for new +DRM functionality, or to fix kernel bugs. -The boards should have networking, so that we can extract the dEQP .xml -results to artifacts on GitLab. +The boards must have networking, so that we can extract the dEQP .xml results to +artifacts on GitLab, and so that we can download traces (too large for an +initramfs) for trace replay testing. Given that we need networking already, and +our deqp/piglit/etc. payload is large, we use nfs from the x86 runner system +rather than initramfs. + +See `src/freedreno/ci/gitlab-ci.yml` for an example of fastboot on DB410c and +DB820c (freedreno-a306 and freereno-a530). Requirements (servo) -------------------- @@ -68,6 +74,9 @@ call "servo":: dhcp-option=tag:cheza1,option:root-path,/srv/nfs/cheza1 dhcp-option=tag:cheza2,option:root-path,/srv/nfs/cheza2 +See `src/freedreno/ci/gitlab-ci.yml` for an example of servo on cheza. Note +that other servo boards in CI are managed using LAVA. + Setup -----