linux-kernel - Re: [PATCH v10] drm: Add initial ci/ subdirectory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <338ed966-0337-16e0-3758-55ede0e2ea0d@collabora.com>
Date:   Wed, 2 Aug 2023 14:32:12 +0300
From:   David Heidelberg <david.heidelberg@...labora.com>
To:     Juan A. Suárez <jasuarez@...lia.com>,
        Maira Canal <mcanal@...lia.com>,
        Helen Koike <helen.koike@...labora.com>,
        dri-devel@...ts.freedesktop.org, eric@...lia.com
Cc:     emma@...olt.net, linux-doc@...r.kernel.org,
        linux-amlogic@...ts.infradead.org, jbrunet@...libre.com,
        robdclark@...gle.com, corbet@....net, khilman@...libre.com,
        sergi.blanch.torne@...labora.com, gustavo.padovan@...labora.com,
        linux-rockchip@...ts.infradead.org, daniels@...labora.com,
        martin.blumenstingl@...glemail.com, robclark@...edesktop.org,
        anholt@...gle.com, linux-mediatek@...ts.infradead.org,
        mripard@...nel.org, matthias.bgg@...il.com,
        linux-arm-kernel@...ts.infradead.org,
        angelogioacchino.delregno@...labora.com, neil.armstrong@...aro.org,
        guilherme.gallo@...labora.com, linux-kernel@...r.kernel.org,
        tzimmermann@...e.de
Subject: Re: [PATCH v10] drm: Add initial ci/ subdirectory

On 31/07/2023 10:38, Juan A. Suárez wrote:
> On Sat, 2023-07-29 at 12:08 +0300, David Heidelberg wrote:
>> Hello Maira,
>>
>> Regarding the second question about V3D and V3DV: in the Mesa3D CI, we
>> currently use downstream kernels, so we don't build the kernel for
>> Raspberry Pi.
>>
>>
>>
>
> BM_BOOTFS option can point to a link tarball containing an alternative 
> kernel to use instead of downstream one.
>
> The only drawback is that this tarball must be an already compiled 
> kernel; it won't compile it.
It would be great if you could fill in missing kernel config options for 
machines you use for V3D(V) in
the `kernel/configs/mesa*.config` within the `gfx-ci/Linux repository 
(the config files here origin from there).

If the compiled kernel will work on RPis, then the next step would be 
adding kernel format
and DTB names to the `src/broadcom/ci/gitlab-ci.yml` in the Mesa 
repository so that you can use my Mesa draft MR [1]
to quickly test if your jobs would work with the mainline kernel and any 
other board that won't break due to your changes.

When this integration is done ‒ it's easy to run drm-ci testing on these 
machines.

David

[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23563


>
>> However, I've been thinking about the possibility of adding an override
>> for the kernel from an external source to our CI. This way, we can also
>> test with a provided kernel and override the default option of using the
>> downstream kernel on Raspberry Pi.
>>
>> If we proceed with this, it would be sensible to include V3D* options in
>> our kernel builds.
>>
>> I'm including Juan and Eric for their input on this topic.
>>
>>
>
> The idea sounds great. Aren't we already compiling kernels for other 
> hardware? Maybe we can include specific versions for Rpi.
>
> J.A.
>
-- 
David Heidelberg
Consultant Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718


Download attachment "OpenPGP_0x69F567861C1EC014.asc" of type "application/pgp-keys" (682 bytes)

Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (229 bytes)