All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: Khem Raj <raj.khem@gmail.com>,
	"steven.monsees@baesystems.com" <steven.monsees@baesystems.com>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #yocto opencl
Date: Thu, 29 Apr 2021 02:15:43 +0000	[thread overview]
Message-ID: <e37281fac1264c73b4e28c3722049d22@intel.com> (raw)
In-Reply-To: <158a82d4-064b-72fe-01c8-ae8e6ba5f69e@gmail.com>

> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of
> Khem Raj
> Sent: Thursday, April 29, 2021 10:07 AM
> To: steven.monsees@baesystems.com; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto opencl
> 
> 
> 
> On 4/28/21 10:30 AM, Monsees, Steven C (US) via lists.yoctoproject.org
> wrote:
> > Can someone tell me is this supported under Yocto in any way?
> >
> > meta-beignet/recipes-opencl at ross * rossburton/meta-beignet * GitHub
> > <https://github.com/rossburton/meta-beignet/tree/ross/recipes-opencl>
> >
> > Any docs, or updates ?
> >
> > Wanted to know if this would work under Zeus, with meta-clang ?
> >
> > Looking to build opencl shared library support...
> 
> meta-intel has it see
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/dynamic-layers/clang-
> layer/recipes-opencl/opencl-clang?h=zeus
> 

Yes, please see the compute-runtime recipe that builds NEO driver instead for later platforms. More details on the project site:

https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md

Thanks,

Anuj

      reply	other threads:[~2021-04-29  2:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 17:30 #yocto opencl Monsees, Steven C (US)
2021-04-29  2:07 ` [yocto] " Khem Raj
2021-04-29  2:15   ` Anuj Mittal [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=e37281fac1264c73b4e28c3722049d22@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=raj.khem@gmail.com \
    --cc=steven.monsees@baesystems.com \
    --cc=yocto@lists.yoctoproject.org \
    /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.