Hi,
On 3 March 2015 at 23:26, Kristian Høgsberg k...@bitplanet.net wrote:
On Tue, Mar 3, 2015 at 10:43 AM, Chad Versace chad.vers...@intel.com wrote:
Please use EGLImages as the import/export object. That provides
consistency with existing similar EGL APIs. And it allows a clean
separation
On 03/02/2015 09:36 PM, Dave Airlie wrote:
On 3 March 2015 at 13:57, Dave Airlie airl...@gmail.com wrote:
Okay I've revised this to add some more info to the interface,
essentially I need to get the fourcc back so I can later pass
it across the wire to the EGL_EXT_image_dma_buf_import, also
On Tue, Mar 3, 2015 at 10:43 AM, Chad Versace chad.vers...@intel.com wrote:
On 03/02/2015 09:36 PM, Dave Airlie wrote:
On 3 March 2015 at 13:57, Dave Airlie airl...@gmail.com wrote:
Okay I've revised this to add some more info to the interface,
essentially I need to get the fourcc back so I
On 3 March 2015 at 13:57, Dave Airlie airl...@gmail.com wrote:
Okay I've revised this to add some more info to the interface,
essentially I need to get the fourcc back so I can later pass
it across the wire to the EGL_EXT_image_dma_buf_import, also
the number of planes (though for my usecase
Okay I've revised this to add some more info to the interface,
essentially I need to get the fourcc back so I can later pass
it across the wire to the EGL_EXT_image_dma_buf_import, also
the number of planes (though for my usecase I don't care so much).
The problem with EGL_MESA_drm_image is that
