On Tue, Jul 16, 2013 at 2:40 PM, Sébastien Taylor wrote:
> What I mean is for gpu-viv-opencl package libCL and libCLC would be provided.
> Then the gpu-viv-opencl package would provide virtual/opencl. It might also
> be worth seeing if any of the other BSP provide OpenCL support and see how
>
What I mean is for gpu-viv-opencl package libCL and libCLC would be provided.
Then the gpu-viv-opencl package would provide virtual/opencl. It might also be
worth seeing if any of the other BSP provide OpenCL support and see how their
libraries are packaged.
The main concern, libCL requires l
On Mon, Jul 15, 2013 at 7:36 PM, Sébastien Taylor wrote:
> I don't understand your question, I think my description details why both
> would be required. I guess a good way to go would be with a virtual/opencl
> that includes libCL and libCLC in Vivante's case.
If we use a virtual, people need
I don't understand your question, I think my description details why both would
be required. I guess a good way to go would be with a virtual/opencl that
includes libCL and libCLC in Vivante's case.
On 2013-07-12, at 7:44 AM, Otavio Salvador wrote:
> On Tue, Jun 25, 2013 at 12:26 PM, Sébastie
On Tue, Jun 25, 2013 at 12:26 PM, Sébastien Taylor wrote:
> User needs libCL to use OpenCL, to do anything useful you need to compile
> kernels (shader programs) using libCLC (CL Compiler). Though technically a
> pre-compiled shader could be loaded without the need of libCLC I'm not sure
> if
User needs libCL to use OpenCL, to do anything useful you need to compile
kernels (shader programs) using libCLC (CL Compiler). Though technically a
pre-compiled shader could be loaded without the need of libCLC I'm not sure if
the Vivante libraries actually support this (to pull the objects ba
On Mon, Jun 17, 2013 at 12:33 PM, Sébastien Taylor wrote:
> The issue is dependency between the Vivante OpenCL libraries that isn't
> implicit. If the libCLC.so isn't found the compilation simply fails every
> time. I understand that it makes sense to separate the CL and CLC libraries
> as on
The issue is dependency between the Vivante OpenCL libraries that isn't
implicit. If the libCLC.so isn't found the compilation simply fails every
time. I understand that it makes sense to separate the CL and CLC libraries as
one might want to use pre-compiled .cl files but the silently failing
I'm so sorry, but I still does not understand what is the issue...
On 06/02/2013 04:44 PM, Sébastien Taylor wrote:
Sorry I wasn't clear. Using my old LTIB setup I was able to correctly
get the compiler errors on the console, fixing them allows the
application to run.
So, using LTIB you got a
On Sun, Jun 2, 2013 at 4:44 PM, Sébastien Taylor wrote:
> Sorry I wasn't clear. Using my old LTIB setup I was able to correctly get
> the compiler errors on the console, fixing them allows the application to
> run. Meanwhile my yocto installation still wouldn't run with the fix. I
> confirmed
Sorry I wasn't clear. Using my old LTIB setup I was able to correctly get the
compiler errors on the console, fixing them allows the application to run.
Meanwhile my yocto installation still wouldn't run with the fix. I confirmed
to be using the same Vivante libraries but noticed my installat
On Fri, May 31, 2013 at 2:28 PM, Sébastien Taylor wrote:
> It looks like there's an issue with libOpenCL on the Yocto builds, I can't
> get it to compile any kernels which work correctly under LTIB.
I didn't get what you mean:
* does it work in LTIB?
* how someone can reproduce it?
Regards,
It looks like there's an issue with libOpenCL on the Yocto builds, I can't get
it to compile any kernels which work correctly under LTIB.
On 2013-05-30, at 11:34 PM, Sébastien Taylor wrote:
> Running the same code under the LTIB BSP I am getting the compiler errors so
> this is specific to the
Running the same code under the LTIB BSP I am getting the compiler errors so
this is specific to the version in Yocto 1.4. I'll dig more to see library
version differences.
In terms of the error, it was complaining about the const sampler_t outside the
function.
On 2013-05-30, at 9:10 PM, Sé
I am unable to find the source code for the Vivante SDK OpenCL samples. I am
having issues with the most basic of kernels failing to build with the error
CL_BUILD_PROGRAM_FAILURE and clGetProgramBuildInfo with CL_PROGRAM_BUILD_LOG is
returning an empty string. I have tested this code against t
15 matches
Mail list logo
