Hi,
For me mmap capability means that both server and client can call
mmap() on the provided file descriptor.
I have no simple way to know if the driver support mmap().
The better option I see today is to create a dumb buffer and to try to
mmap it at server initialization.
Anyway client and server
On Thu, 5 Dec 2013 18:36:38 +0100
benjamin.gaign...@linaro.org wrote:
> From: Benjamin Gaignard
>
> It allow to use a dmabuf file descriptor in a wayland protocol.
> To make as generic as possible it is up to the server to call
> wl_dmabuf_send_format() and/or wl_dmabuf_send_capabilities() to s
From: Benjamin Gaignard
It allow to use a dmabuf file descriptor in a wayland protocol.
To make as generic as possible it is up to the server to call
wl_dmabuf_send_format() and/or wl_dmabuf_send_capabilities() to signal
it capabilities.
Signed-off-by: Benjamin Gaignard
---
protocol/Makefile.a
On 03/12/2013, benjamin.gaign...@linaro.org wrote :
Here are a few comments:
+
+
What's the point of creating a new interface, and skipping version 1?
You should have removed too the since="2" you have in some functions.
+
+
+
+Bitmask of capabilities.
+
+
+
From: Benjamin Gaignard
This protocol is widely derivated of wl_drm protocol
but without unneeded function like flink or authentification.
It allow to use a dmabuf file descriptor in a wayland protocol
which could be useful in case we don't have (or can't use) Mesa EGL.
Signed-off-by: Benjamin G
