From: <a-christidis@ti.com>
To: <reatmon@ti.com>, <meta-arago@lists.yoctoproject.org>
Subject: [meta-arago][scarthgap][PATCH v4 0/2] Introducing Opencl-cts
Date: Fri, 21 Feb 2025 14:41:51 -0600 [thread overview]
Message-ID: <20250221204153.428129-1-a-christidis@ti.com> (raw)
From: Antonios Christidis <a-christidis@ti.com>
Dear all,
Adding the recipe for opencl-cts, and a patch for it. Also, changing
the version of the opencl-headers, this is done due to compatibility
issues with the header version and cts version.
All of this patch series is meant for scarthgap, which is why I am
not including a patch to add opencl-cts to any package group so that
it can be build and included in our sdk. That patch will be sent out
separately as it is both for scarthgap and master. More info on this
can be found in the upcoming patch.
Regards,
Antonios
Antonios Christidis (2):
meta-arago-test: add recipe opencl-cts
meta-arago-test: opencl_headers 2023.12.14 -> 2024.05.08
.../opencl/opencl-headers_%.bbappend | 4 +++
.../opencl/opencl_headers-ti.inc | 1 +
.../files/0001-Ignore-Compiler-Warnings.patch | 18 +++++++++++++
.../opencl/opencl-cts_2024.08.08.bb | 27 +++++++++++++++++++
4 files changed, 50 insertions(+)
create mode 100644 meta-arago-test/recipes-extended/opencl/opencl-headers_%.bbappend
create mode 100644 meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc
create mode 100644 meta-arago-test/recipes-graphics/opencl/files/0001-Ignore-Compiler-Warnings.patch
create mode 100644 meta-arago-test/recipes-graphics/opencl/opencl-cts_2024.08.08.bb
--
2.34.1
next reply other threads:[~2025-02-21 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:41 a-christidis [this message]
2025-02-21 20:41 ` [meta-arago][scarthgap][PATCH v4 1/2] meta-arago-test: add recipe opencl-cts a-christidis
2025-02-21 22:03 ` Denys Dmytriyenko
2025-02-21 20:41 ` [meta-arago][scarthgap][PATCH v4 2/2] meta-arago-test: opencl_headers 2023.12.14 -> 2024.05.08 a-christidis
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=20250221204153.428129-1-a-christidis@ti.com \
--to=a-christidis@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.