From: David Heidelberg <david.heidelberg@collabora.com>
To: "Juan A. Suárez" <jasuarez@igalia.com>,
"Maira Canal" <mcanal@igalia.com>,
"Helen Koike" <helen.koike@collabora.com>,
dri-devel@lists.freedesktop.org, eric@igalia.com
Cc: emma@anholt.net, linux-doc@vger.kernel.org,
linux-amlogic@lists.infradead.org, jbrunet@baylibre.com,
robdclark@google.com, corbet@lwn.net, khilman@baylibre.com,
sergi.blanch.torne@collabora.com, gustavo.padovan@collabora.com,
linux-rockchip@lists.infradead.org, daniels@collabora.com,
martin.blumenstingl@googlemail.com, robclark@freedesktop.org,
anholt@google.com, linux-mediatek@lists.infradead.org,
mripard@kernel.org, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org,
angelogioacchino.delregno@collabora.com,
neil.armstrong@linaro.org, guilherme.gallo@collabora.com,
linux-kernel@vger.kernel.org, tzimmermann@suse.de
Subject: Re: [PATCH v10] drm: Add initial ci/ subdirectory
Date: Wed, 2 Aug 2023 14:32:12 +0300 [thread overview]
Message-ID: <338ed966-0337-16e0-3758-55ede0e2ea0d@collabora.com> (raw)
In-Reply-To: <ef84ccedbf880c8605688f26ebedc04046c1dd78.camel@igalia.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 2058 bytes --]
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
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 695 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-02 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230720152737.102382-1-helen.koike@collabora.com>
2023-07-27 19:49 ` [PATCH v10] drm: Add initial ci/ subdirectory Rob Clark
2023-07-27 21:47 ` Rob Clark
2023-07-28 5:26 ` Daniel Stone
2023-07-28 8:48 ` Maxime Ripard
2023-07-28 14:37 ` Rob Clark
2023-07-31 12:25 ` Helen Mae Koike Fornazier
2023-07-31 14:51 ` Rob Clark
2023-07-28 11:58 ` Maira Canal
[not found] ` <52d1d9e5-00c8-2260-57fc-310cc2f712fd@igalia.com>
[not found] ` <ad029e1c-8f00-9f5e-e25a-957b3f70c385@collabora.com>
[not found] ` <ef84ccedbf880c8605688f26ebedc04046c1dd78.camel@igalia.com>
2023-08-02 11:32 ` David Heidelberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=338ed966-0337-16e0-3758-55ede0e2ea0d@collabora.com \
--to=david.heidelberg@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=anholt@google.com \
--cc=corbet@lwn.net \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=eric@igalia.com \
--cc=guilherme.gallo@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=helen.koike@collabora.com \
--cc=jasuarez@igalia.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=matthias.bgg@gmail.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robclark@freedesktop.org \
--cc=robdclark@google.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox