Lines Matching refs:kernel

4 Occasionally, the Gitlab CI needs a Linux Kernel update to enable new kernel
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,
31 the script located at `.gitlab-ci/container/build-kernel.sh`.
57 Every kernel uprev should update 3 image tags, located at two files.
61 - **KERNEL_URL** for the location of the new kernel
65 - **KERNEL_ROOTFS_TAG** to rebuild rootfs with the new kernel
71 1. Compile the newer kernel locally for each platform.
74 4. Push a new development branch to `Kernel repository`_ based on the latest kernel tag used in Git…
75 5. Hack `build-kernel.sh` script to clone kernel from your development branch
92 To have the most confidence that a kernel uprev does not break anything in Mesa,
98 …branch in the same git ref (should be the main branch) before branching to the kernel uprev kernel.
101 4. Now do the same for the kernel uprev branch
102 5. Compare the job results. If a CI job turned red on your uprev branch, it means that the kernel u…
107 Some CI jobs have support to plug in a custom kernel by simply changing a variable.
108 This is great, since rebuilding the kernel and rootfs may takes dozens of minutes.
111 `BM_KERNEL`. If one puts a gz-compressed kernel URL there, the job will use that
112 kernel to boot the freedreno bare-metal devices. The same works for `BM_DTB` in
118 Sometimes a job may turn to red for reasons unrelated to the kernel update, e.g.