viddec3test using wayland

For wayland clients, weston should be launched first. Please launch weston using /etc/init.d weston start   and then try.

There is one issue with omapdrmtest with wayland, fd is not initialized and results in buf_lock error

Apply this patch and then try.

diff --git a/util/display-wayland.c b/util/display-wayland.c
index c0d6175..030a12a 100644
--- a/util/display-wayland.c
+++ b/util/display-wayland.c
@@ -95,7 +95,7 @@ alloc_buffer(struct display *disp, uint32_t fourcc, uint32_t w, uint32_t h)
 	buf->fourcc = fourcc;
 	buf->width = w;
 	buf->height = h;
-	buf->multiplanar = true;
+	buf->multiplanar = false;
 
 	buf->nbo = 1;
 
@@ -135,6 +135,7 @@ alloc_buffer(struct display *disp, uint32_t fourcc, uint32_t w, uint32_t h)
 				&bo_handles[0], &buf->pitches[0]);
 
 		omap_bo_get_name(buf->bo[0], &buf_wl->name);
+		buf->fd[0] = omap_bo_dmabuf(buf->bo[0]);
 		/* NV12: Create a planar buffer */
 		buf_wl->wl_buf = wl_drm_create_planar_buffer(disp_wl->drm,
 			buf_wl->name, buf->width, buf->height, wl_fmt,

when trying to launch weston, we are getting failures (PSDKLA for Linux kernel 4.4):

1) Directly launch weston  (/usr/bin):

#weston tty=1

failure, unable to find wayland-backend.so, it is also not present in the /usr/lib or in the file system at all

00:01:22.470] Using config file '/etc//weston.ini'
[00:01:22.470] Loading module '/usr/lib/weston/wayland-backend.so'
[00:01:22.470] Failed to load module: /usr/lib/weston/wayland-backend.so: cannot open shared object file: No such file or directory

2) there is a weston utility in /etc/init.d, it does not give any failure but still i am unable to run viddec3test with -w (unable to open wayland)

can you please tell why there is an inconsistency and which weston to use

weston is expecting input devices (/dev/input/eventX), currently we dont have any input source other than USB.

How do we enable USB mouse as /dev/input/eventX source from Menuconfig, any idea?

Failure:

[00:03:28.468] Loading module '/usr/lib/weston/drm-backend.so'
[00:03:28.472] Output repaint window is 7 ms maximum.
[00:03:28.472] initializing drm backend
[00:03:28.474] using /dev/dri/card0
[00:03:28.474] Loading module '/usr/lib/weston/gl-renderer.so'
failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory
failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[00:03:28.480] warning: either no EGL_EXT_platform_base support or specific platform support; falling back to eglGetDisplay.
[00:03:28.487] warning: EGL_EXT_buffer_age not supported. Performance could be affected.
[00:03:28.487] Retrieving EGL client extension string failed.
[00:03:28.488] warning: no input devices on entering Weston. Possible causes:
        - no permissions to read /dev/input/event*
        - seats misconfigured (Weston backend option 'seat', udev device property ID_SEAT)
[00:03:28.488] failed to create input devices
[00:03:28.541] fatal: failed to create compositor backend

You will observe this error if FD submitted to dce_buf_lock is zero

Please make sure you have applied the patch in display-wayland.c to get FD from Bo and set multiplanar to false.

hi ramprasad

would you have any idea on this.

regards

The green patches at the right and bottom are due to padding added by H264 decoder. 

In KMS case, disp_post_vid_buffer takes offset where active video starts is sent as argument and drmModeSetPlane's last four arguments are crop info and hence we don't see padded region with KMS.

In Wayland case since full buffer with padding is sent for the surface, it is expected to see padded region.

There should be some API to crop in wayland also.