Lines Matching +full:- +full:- +full:mesa +full:- +full:url

7 side-effects since many devices from different platforms are involved in the
11 -----------------
14 https://gitlab.freedesktop.org/gfx-ci/linux
16 It is common that Mesa kernel brings some patches that were not merged on the
17 Linux mainline, that is why Mesa has its own kernel version which should be used
20 So, one should base the kernel uprev from the last tag used in the Mesa CI,
21 please refer to ``.gitlab-ci/image-tags.yml`` ``KERNEL_TAG`` variable.
22 Every tag has a standard naming: ``vX.YZ-for-mesa-ci-<commit_short_SHA>``, which
25 :code:`git tag vX.YZ-for-mesa-ci-$(git rev-parse --short HEAD)`
28 ---------------
30 The kernel files are loaded from the artifacts uploaded to S3 from gfx-ci/linux.
35 When a Kernel uprev happens, it is worth compiling and cross-compiling the
37 resulting Kconfig is a merge between *Mesa CI Kconfig* and *Linux tree
43 +------------+------------------------------------------------------+------------------------------…
44 | Platform   | Mesa CI Kconfig location                             | Linux tree defconfig         …
46 | arm        | kernel/configs/mesa3d-ci_arm.config\@gfx-ci/linux    | arch/arm/configs/multi_v7_def…
47 +------------+------------------------------------------------------+------------------------------…
48 | arm64      | kernel/configs/mesa3d-ci_arm64.config\@gfx-ci/linux  | arch/arm64/configs/defconfig …
49 +------------+------------------------------------------------------+------------------------------…
50 | x86-64     | kernel/configs/mesa3d-ci_x86_64.config\@gfx-ci/linux | arch/x86/configs/x86_64_defco…
51 +------------+------------------------------------------------------+------------------------------…
54 -------------------
58 :code:`.gitlab-ci/container/gitlab-ci.yml` tag
60 - **KERNEL_URL** for the location of the new kernel
62 :code:`.gitlab-ci/image-tags.yml` tags
64 - **KERNEL_ROOTFS_TAG** to rebuild rootfs with the new kernel
65 - **DEBIAN_X86_TEST_GL_TAG** to ensure that the new rootfs is being used by the GitLab x86 jobs
68 -------------------
74 5. Hack ``build-kernel.sh`` script to clone kernel from your development branch
81 1. Push a new tag to Mesa CI `Kernel repository`_
82 2. Update KERNEL_URL ``debian/x86_test-gl`` job definition
86 ---------------
91 To have the most confidence that a kernel uprev does not break anything in Mesa,
94 Step-by-step
103 Bare-metal custom kernels
110 ``BM_KERNEL``. If one puts a gz-compressed kernel URL there, the job will use that
111 kernel to boot the Freedreno bare-metal devices. The same works for ``BM_DTB`` in