> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Alexander Kravchenko > Sent: May 27, 2018 11:19 AM > To: 'FFmpeg development discussions and patches' <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop extension > for NV12 and P010 textures - split planes > > > > > -----Original Message----- > > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > > Of Mark Thompson > > Sent: Sunday, May 27, 2018 3:29 PM > > To: ffmpeg-devel@ffmpeg.org > > Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop > > extension for NV12 and P010 textures - split planes > > > > On 27/05/18 07:57, Alexander Kravchenko wrote: > > > сб, 26 мая 2018 г. в 19:45, Mark Thompson <s...@jkqxz.net>: > > > > > >> On 24/05/18 15:26, Mironov, Mikhail wrote: > > >>> AMD has published OpenCL extension which allows split D3D11 > > >>> texture > > >> interoped as a single 2D image into two 2D images representing Y > > >> and UV planes. > > >>> > > >> > https://www.khronos.org/registry/OpenCL/extensions/amd/cl_amd_plana > > >> r_ > > >> yuv.txt > > >> > > >> Nice! That looks like exactly what we want :) > > >> > > >> Is there any timeline for when this will be available in released > > >> drivers? > > >> > > > Hi Mark. > > > This extension was implemented while ago, so it can be used now. > > > > I have what claims to be the most recent version of the Radeon drivers > > (18.5.1, driver version 18.10.16, OpenCL version 24.20.11016.4 > > - I don't know which of these is relevant), and it gives me: > > > > Platform extensions: > > cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing > > cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices > > > > Device extensions: > > cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics > > cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics > > cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics > > cl_khr_int64_extended_atomics cl_khr_3d_image_writes > > cl_khr_byte_addressable_store cl_khr_gl_sharing cl_khr_gl_depth_images > > cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf > > cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt > cl_khr_d3d10_sharing > > cl_khr_d3d11_sharing cl_khr_dx9_media_sharing > > cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups > > cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image > > cl_khr_mipmap_image_writes cl_amd_liquid_flash > > > > which doesn't include this extension? > > > > > Hi Mark, > > It does include the extension. > Extension was implemented while ago (years ago), but wasn't officially > published till now. > > Probably the extension is still not enumerated in device/platform extensions > list Any way it can be used now. > > > Thanks, > Alexander >
Since it was a private extension it is not visible as device extension but if one asks for the function pointer it is there. The implementation was done 3-4 years ago, I can dig the driver eversion if needed. I will check with developer if he plans to expose it in device extension list. Mikhail > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
