The EGL_KHR_platform_gbm extension has specific behavior
for the EGL_NATIVE_VISUAL_ID.
There is following contents in the EGL officail size,
(https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_platform_gbm.txt)
New Behavior section
"For each EGLConfig that belongs to the GBM platform, the
EGL_NATIVE_VISUAL_ID attribute is a GBM color format, such as
GBM_FORMAT_XRGB8888. "
The EFL EVAS in Tizen requires the GBM_FORMAT_ARGB8888.
And YaGL can support this format. So returns it.
This is W/A patch. Must be resolved correclty.
Change-Id: I402ebb20d17bf1a119ca09154519d57305e539a7
Signed-off-by: Jinhyung Jo <jinhyung.jo@samsung.com>
int *visual_id,
int *visual_type)
{
- *visual_id = 0;
+ /* XXX: W/A for evas
+ efl GIT: platform/upstream/efl
+ evas src: /src/modules/evas/engines/gl_drm/evas_outbuf.c
+ evas func.: _evas_outbuf_egl_setup()
+ reference: https://www.khronos.org/registry/egl/
+ extensions/KHR/EGL_KHR_platform_gbm.txt
+ read 'New Behavior' section
+ */
+ *visual_id = GBM_FORMAT_ARGB8888;
*visual_type = 0;
return 1;