From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/6] OpenCL support
Date: Sun, 21 Oct 2018 00:14:31 +0200 [thread overview]
Message-ID: <20181020221437.12687-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
This series started with the patches from Valentin enabling mesa3d as
an OpenCL provider, and clinfo as a first package using OpenCL.
OpenCL, like OpenGL or EGL, is an API specified by Khronos, so it can
have multiple implementations. Therefore, tying clinfo directly with
mesa3d wasn't the right thing to do.
And indeed, we have at least another package in Buildroot that
provides an OpenCL implementation: nvidia-driver, and clinfo builds
fine against it.
So, this series introduces a virtual-package for OpenCL, and makes
nvidia-driver and mesa3d providers of OpenCL. In order to make
nvidia-driver a provider of OpenCL, we need to teach mesa3d-headers
how to install OpenCL headers, because nvidia-drivers doesn't provide
them (just like it doesn't provide GL, EGL, etc. headers).
Thomas
Thomas Petazzoni (4):
package/opengl/opencl: new virtual package
package/mesa3d-headers: install OpenCL headers when needed
package/nvidia-driver: use += where appropriate
package/nvidia-driver: become an OpenCL provider
Valentin Korenblit (2):
package/mesa3d: enable OpenCL support
package/clinfo: new package
DEVELOPERS | 1 +
package/Config.in | 1 +
package/clinfo/Config.in | 12 ++++++++
package/clinfo/clinfo.hash | 4 +++
package/clinfo/clinfo.mk | 21 ++++++++++++++
package/mesa3d-headers/mesa3d-headers.mk | 4 +++
package/mesa3d/0003-set-LIBCLC_INCLUDEDIR.patch | 37 +++++++++++++++++++++++++
package/mesa3d/Config.in | 14 ++++++++++
package/mesa3d/mesa3d.mk | 12 +++++++-
package/nvidia-driver/Config.in | 5 ++++
package/nvidia-driver/nvidia-driver.mk | 8 ++++--
package/opengl/Config.in | 1 +
package/opengl/libopencl/Config.in | 6 ++++
package/opengl/libopencl/libopencl.mk | 7 +++++
14 files changed, 129 insertions(+), 4 deletions(-)
create mode 100644 package/clinfo/Config.in
create mode 100644 package/clinfo/clinfo.hash
create mode 100644 package/clinfo/clinfo.mk
create mode 100644 package/mesa3d/0003-set-LIBCLC_INCLUDEDIR.patch
create mode 100644 package/opengl/libopencl/Config.in
create mode 100644 package/opengl/libopencl/libopencl.mk
--
2.14.4
next reply other threads:[~2018-10-20 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 22:14 Thomas Petazzoni [this message]
2018-10-20 22:14 ` [Buildroot] [PATCH 1/6] package/opengl/opencl: new virtual package Thomas Petazzoni
2018-10-21 10:46 ` Valentin Korenblit
2018-10-21 14:29 ` Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 2/6] package/mesa3d: enable OpenCL support Thomas Petazzoni
2018-10-21 10:53 ` Valentin Korenblit
2018-10-21 11:10 ` Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 3/6] package/mesa3d-headers: install OpenCL headers when needed Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 4/6] package/nvidia-driver: use += where appropriate Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 5/6] package/nvidia-driver: become an OpenCL provider Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 6/6] package/clinfo: new package Thomas Petazzoni
2018-12-03 22:09 ` [Buildroot] [PATCH 0/6] OpenCL support Thomas Petazzoni
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=20181020221437.12687-1-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.