On Thu, 4 Oct 2018 10:15:52 +0200
Dirk Eibach wrote:
> Hi Pekka,
>
> > > > I suppose that means you still do a copy from the gbm_bo/dmabuf into a
> > > > window surface? If you used zwp_linux_dmabuf manually from your Wayland
> > > > client, you could avoid even that copy. It has the same caveat
Hi Pekka,
> > > I suppose that means you still do a copy from the gbm_bo/dmabuf into a
> > > window surface? If you used zwp_linux_dmabuf manually from your Wayland
> > > client, you could avoid even that copy. It has the same caveat as below
> > > though.
> >
> > I don't think so. The grabber doe
On Tue, 2 Oct 2018 17:08:25 +0200
Dirk Eibach wrote:
> Hi Pekka,
>
Re-adding wayland-devel to cc, hope that's ok.
> > I suppose that means you still do a copy from the gbm_bo/dmabuf into a
> > window surface? If you used zwp_linux_dmabuf manually from your Wayland
> > client, you could avoid e
On Tue, 2 Oct 2018 15:06:14 +0200
Dirk Eibach wrote:
> Hi Pekka,
>
> I finally got everything working. I am using gbm_bo_create() and
> gbm_bo_get_fd() to get a buffer that is filled by my grabber. Then I
> use eglCreateImageKHR() and glEGLImageTargetTexture2DOES() to display
> it.
Hi Dirk,
ni
Hi Pekka,
I finally got everything working. I am using gbm_bo_create() and
gbm_bo_get_fd() to get a buffer that is filled by my grabber. Then I
use eglCreateImageKHR() and glEGLImageTargetTexture2DOES() to display
it.
My only problem left is that glEGLImageTargetTexture2DOES() does only
accept ARG
On Wed, 12 Sep 2018 11:51:39 +0200
Dirk Eibach wrote:
> Hi Pekka,
>
> > yes, simple-dmabuf-v4l does exactly what I wrote in the above quote.
> > However, it does not allocate from the GPU device or from the display
> > device. Instead, it allocates from the V4L2 device and hopes that the
> > com
On Wed, 12 Sep 2018 08:30:55 +0200
Dirk Eibach wrote:
> Hi Pekka,
>
> > that would not involve Weston in any special way at all. Buffer
> > allocation is usually done in the client any way the client wants. To
> > ensure the buffer can be used by the compositor before you fill it with
> > data,
Hi Pekka,
> that would not involve Weston in any special way at all. Buffer
> allocation is usually done in the client any way the client wants. To
> ensure the buffer can be used by the compositor before you fill it with
> data, you would export your buffer as a dmabuf and use
> zwp_linux_dmabuf_
On Tue, 11 Sep 2018 15:28:35 +0200
Dirk Eibach wrote:
> I have a grabber device on The PCIe-bus that is able to transfer image
> data to other PCIe devices.
> I want to setup a wayland client, that reserves a buffer in GPU
> memory. Then the grabber could DMA to the buffer address. After
> finish
I have a grabber device on The PCIe-bus that is able to transfer image
data to other PCIe devices.
I want to setup a wayland client, that reserves a buffer in GPU
memory. Then the grabber could DMA to the buffer address. After
finishing the transfer, the client could flip the buffer.
Is there alrea
10 matches
Mail list logo