According to the aopencl project:
The OpenCL functions are found in
on Nexus 10 T604 based devices
on Nexus 4 Adreno 320 based GPU's
We need to enhance the JOCL dynamic library look-up to search for OpenCL symbols in non standard locations. This will allow use of JOCL on the first generation OpenCL Android devices.
For more info see:
Some nexus 4 devices got OpenCL in:
I'm working with the ODROID-XU Android development board. It uses an Exynos 5410 SoC w/ PowerVR SGX544MP3 GPU supporting OpenCL 1.1 EP.
The driver is located here:
I have initially tested it via modifying the aopencl project mentioned in reply #1 above. I assume this is the general location for other PowerVR GPU OpenCL drivers. I'm now taking a look at getting this working with JOCL.
(In reply to comment #2)
> I'm working with the ODROID-XU Android development board. It uses an Exynos
> 5410 SoC w/ PowerVR SGX544MP3 GPU supporting OpenCL 1.1 EP.
> The driver is located here:
> I have initially tested it via modifying the aopencl project mentioned in
> reply #1 above. I assume this is the general location for other PowerVR GPU
> OpenCL drivers. I'm now taking a look at getting this working with JOCL.
The JOCL JNI Lib loader is currently located in com.jogamp.opencl.JOCLJNILibLoader
The best way to resolve this bug is to move the implementation into a new class
com.jogamp.opencl.CLDynamicLibraryBundleInfo and use the DynamicLibraryBundle helper class provided by Gluegen.
I suggest to make JOCL library and symbol look-up similar to how we do dynamic library symbol look-up inside multiple librarys for the JOGL project. You may take a look at the com.jogamp.opengl.GLDynamicLibraryBundleInfo implementation to see how we prefer to do dynamic library loading and symbol look-up inside the JogAmp projects.
Bug 773 - Device specific JOCL dynamic library look-up on Android - Part 1/2
Use DynamicLibraryBundleInfo w/ alternative native library names,
drop manual coding of loading and binding, i.e. JOCLJNILibLoader.
After trying opencl native libs (and failing), try GL libs ..
We use a manual impl. to CL's 'clGetExtensionFunctionAddress' similar to JOAL, JOGL ...
Part 2/2 would be to add a Android test activity (jocl test) similar to JOGL's test activities
and let it show some JOCL information ..
Anybody up to the task ?
Me off till Tuesday ..
CLDynamicLibraryBundleInfo: Add libPVROCL.so lookup if Android ..
.. forgot that detail.
Continue at Bug 863