Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-26 Thread Marek Olšák
On Sat, Feb 6, 2016 at 6:53 PM, Jason Ekstrand wrote: > I'm adding Chad to the Cc. At some point, it would be good to get Beignet > playing well with mesa. Personally, I have substantial reservations about > getting the kernel involved in surface layout for anything more

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-17 Thread Marek Olšák
On Sat, Feb 6, 2016 at 10:43 PM, Marek Olšák wrote: > On Sat, Feb 6, 2016 at 6:53 PM, Jason Ekstrand wrote: >> I'm adding Chad to the Cc. At some point, it would be good to get Beignet >> playing well with mesa. Personally, I have substantial

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-06 Thread Marek Olšák
On Sat, Feb 6, 2016 at 6:53 PM, Jason Ekstrand wrote: > I'm adding Chad to the Cc. At some point, it would be good to get Beignet > playing well with mesa. Personally, I have substantial reservations about > getting the kernel involved in surface layout for anything more

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-06 Thread Jason Ekstrand
I'm adding Chad to the Cc. At some point, it would be good to get Beignet playing well with mesa. Personally, I have substantial reservations about getting the kernel involved in surface layout for anything more than 2-D non-mipmapped non-array surfaces. Laying them out can be complicated, and

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-06 Thread Marek Olšák
Also, to clear up some confusion about libdrm_amdgpu, there is always one amdgpu_device instance per device (not per fd, reopened and dup'd fds are matched to one device and one instance). (Also, the uniqueness of amdgpu_device extends to amdgpu_winsys and pipe_screen, because the winsys only

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-05 Thread Nicolai Hähnle
Hi, On 04.02.2016 17:25, Marek Olšák wrote: I would like to start a discussion about an OpenGL-OpenCL interop interface where OpenCL is not part of Mesa. I think the only way to do this is to have Mesa export functions that convert Mesa OpenGL objects into DMABUF handles. Such functions can be

Re: [Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-05 Thread Marek Olšák
On Fri, Feb 5, 2016 at 8:31 PM, Nicolai Hähnle wrote: > Hi, > > > On 04.02.2016 17:25, Marek Olšák wrote: >> >> I would like to start a discussion about an OpenGL-OpenCL interop >> interface where OpenCL is not part of Mesa. >> >> I think the only way to do this is to have

[Mesa-dev] MesaGL <-> non-Mesa OpenCL interop interface

2016-02-04 Thread Marek Olšák
Hi, I would like to start a discussion about an OpenGL-OpenCL interop interface where OpenCL is not part of Mesa. I think the only way to do this is to have Mesa export functions that convert Mesa OpenGL objects into DMABUF handles. Such functions can be exported by DRI driver modules or libGL &