Age | Commit message (Collapse) | Author | Files | Lines |
|
It seems that gRPC channel might not be ready when issueing floating
request so add a wait_for_ready + deadline to make sure we don't send
the request until the channel is available. Initial testing (though we
might need more) shows that this fixes the issue.
The way this works is that the client (if started with wait_for_ready
set to true, passed in the AglShellGrpcClient constructor) will wait for
the channel to be ready and then issue a floating request. There's a
hidden deadline of 2 seconds in case that doesn't happen.
Bug-AGL: SPEC-5235
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I40a5ad0dd760dc4559839ae7c302c1d6bc1ff973
|
|
This is a bigger change to move the from Cmake to meson and
use gPRC instead of agl-shell-desktop protocol.
Bug-AGL: SPEC-5300, SPEC-5301
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: Ib649b7fd38eef5653bc401a8eb159882a2f41e6b
|
|
Apply similar changes as were done in camera-gstreamer commit
19ed4e26 to allow building with gstreamer 1.22.
Bug-AGL: SPEC-5121
Change-Id: Icbf013abffcb4fc95aa14654c0cb53bf55ca7f50
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Rework things a bit to read the window geometry from the .ini style
configuration file etc/xdg/AGL.conf if it is present. This allows
overriding the window geometry for use with the Flutter cluster
demo image.
Bug-AGL: SPEC-4640
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Icd91bf4a2ce43c0fc1ed7ea64f730451326edbd7
(cherry picked from commit 26197c79389784a24f565986c54762f4510cff3c)
|
|
This has run-by-default enabled.
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I99c85373965339a990476eec1772a27cfd360d6c
|
|
Bug-AGL: SPEC-3382
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I7bbb34a377921bc5f741495f14951a0df70694cb
|
|
- Use Qt/QtWayland to set-up an app_id for the main surface. We use that
surface and pass it to waylandsink. Waylandsink create a sub-surface
with the parent the Qt/QtWayland one.
- Install a handler for handling bus messages With it, it allows to pass
the wl_display with the help of a context and the surface backing up
the Widget.
- Installs a timer to wait for Qt to create/get the xdg_surface and
attach a buffer to it. Without we won't be able receive the commit
for the parent event in order to handle it.
Bug-AGL: SPEC-3382
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I4237b7dad110ce36e3a01226e67cb508b6d9a6d9
|
|
Remoting plugin uses jpeg element as default.
This pipeline is refered from sample script in
https://gitlab.freedesktop.org/wayland/weston/blob/master/doc/remoting-client-receive.bash
Bug-AGL : SPEC-2420
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
Change-Id: I83e3bf9e75af24d80993ed1ef78c01154ae94c1b
|
|
Add a check for vaapisink availability, and fall back to using
waylandsink if it is unavailable. This should allow using a non-Intel
board for the cluster demo, though there are potentially issues around
having a H.264 decoder plugin available that may need to be addressed
in the target platform BSP (e.g. Raspberry Pi).
Change-Id: Ie351fe0cd6e36e3db6707b9202b3b1fd7c66d3ce
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Demo instrument cluster receiver application to receive a h264 stream
sent via RTP from another host running Wayland and Weston with the
gst-recorder feature for streaming a virtual display patched in.
The gstreamer pipeline used is based on what was being used with
gst-launch-1.0 in the previously hand-constructed instrument cluster
demo. The use of vaapisink likely constrains use to Intel based
platforms at present, future work should allow working on other
platforms.
The app/surface.{hpp,cpp} files are adapted from code from
xdg-launcher:
https://gerrit.automotivelinux.org/gerrit/staging/xdg-launcher
Note that they are MIT licensed while all other source files are
Apache 2.0. Other than significant refactoring to ease integration,
the functional differences from the runxdg code in xdg-launcher are
that homescreen support has been removed, as the instrument cluster
platform does not use it, and the logging has been reworked to use the
hmi-debug mechanism used by the windowmanager and homescreen.
There is also an implicit assumption that the windowmanager
configuration is such that the "app" role will map the receiver's
surface to the desired location in the center of the dashboard.
Change-Id: Ieddef6463efb744d9c9c28b1508cc930a32981a4
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|