The example I mentioned in http://devgurus.amd.com/thread/159639: https://code.google.com/p/opencl-book-samples/source/browse/trunk/src/Chapter_10/GLinterop/GLinterop... doesn't work anymore since APP SDK 2.8 and fglrx driver 13.2~beta3 under Debian GNU/Linux on Intel Core 2 Duo T7250 and GM45 integrated video. (The last working are APP SDK 2.7 and fglrx 13.1)
The call to
*p_cl_tex_mem = clCreateFromGLTexture(context, CL_MEM_READ_WRITE, GL_TEXTURE_RECTANGLE_ARB, 0, texture, &errNum );
Using GL_TEXTURE_RECTANGLE for texture_target requires OpenGL 3.1. Alternatively, GL_TEXTURE_RECTANGLE_ARB may be specified if the OpenGL extension GL_ARB_texture_rectangle is supported.
$ glxinfo | grep OpenGL
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 8.0.5
OpenGL shading language version string: 1.20
$ glxinfo | grep GL_ARB_texture_rectangle
GL_ARB_texture_rectangle, GL_EXT_packed_float, GL_EXT_pixel_buffer_object,
$ glxinfo | grep 'GLX ver'
GLX version: 1.4
Does AMD already aware of this regression or I'm missing something?
I tried in Windows7_64 platform , catalyst 13.8, APU Trinity machine.Its working fine without any problem.
But when i tried with Linux Ubuntu machine, catalyst 13.8 beta.
Compiled using :
sudo g++ GLintrop.cpp -I "/opt/AMDAPP/include/" -L "/opt/AMDAPP/lib/x86_64/" -lOpenCL -lGL -lglut -lGLU -lGLEW
I am getting following error from glewIsSupported() function
freeglut (./a.out): Unable to create direct context rendering for window 'GL interop'
This may hurt performance.
Warning: Detected that OpenGL 2.1 not supported
Segmentation fault (core dumped)
Please suggest what can be done. since am not a GL expert.
All recent version still don't work. I'd like to clarify, that the working versions I mentioned:
> (The last working are APP SDK 2.7 and fglrx 13.1)
are still perfectly working with Mesa libGL (not fglrx one). Only AMD delivered an opencl library able to work on Intel CPU with Mesa libGL. But it's sadly no more the case. I hoped AMD could check changes between working/not working versions I've found to fix the issue. Maybe it could be done?