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)
--------------------
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
-----