diff options
author | Kenta <murakami.kenta002@jp.panasonic.com> | 2024-10-10 18:10:32 +0900 |
---|---|---|
committer | Jan-Simon Moeller <jsmoeller@linuxfoundation.org> | 2024-10-24 08:24:43 +0000 |
commit | dd48c93dc7ca4e37156413652ba716d008c2edcd (patch) | |
tree | 0e7d6833f00b2290b8696b2a1e76fc287ef1912f /meta-uhmi/meta-rvgpu/README.md | |
parent | 58da6681f4cd53670cb10d63f37ffaae3e6346c4 (diff) |
Unified HMI: Consolidate recipes under meta-uhmi
Move all recipes from meta-rvgpu and meta-distributed-display-fw
into meta-uhmi. And, document the build instructions for RVGPU and
DDFW in the README.
Bug-AGL: SPEC-5254
Change-Id: I0f3362b0f79105de39584d0a5659ac9e3c9d3a2b
Signed-off-by: Kenta <murakami.kenta002@jp.panasonic.com>
Diffstat (limited to 'meta-uhmi/meta-rvgpu/README.md')
-rw-r--r-- | meta-uhmi/meta-rvgpu/README.md | 54 |
1 files changed, 0 insertions, 54 deletions
diff --git a/meta-uhmi/meta-rvgpu/README.md b/meta-uhmi/meta-rvgpu/README.md deleted file mode 100644 index 3d524fef..00000000 --- a/meta-uhmi/meta-rvgpu/README.md +++ /dev/null @@ -1,54 +0,0 @@ -## How to run RVGPU remotely -Prepare two images, one as the Sender and the other as the Receiver. -It is necessary for the Sender and Receiver to be within the same network. - -**Receiver side** -``` -$ export XDG_RUNTIME_DIR=/run/user/<your_UID> -$ rvgpu-renderer -b <your_Area>@0,0 -p <Port_Number> & -``` - -Replace the placeholders with the appropriate values: -- `<your_UID>`: Specify according to your environment, for example: 200 -- `<your_Area>`: Enter an usable area for example: 1920x1080 -- `<Port_Number>`: Enter an available port number, for example: 55555 - -**Sender side** -Create the following shell script **run_remote_app.sh** in any `<WORKDIR>` for a smooth experience. -``` -#!/bin/bash - -export XDG_RUNTIME_DIR=/tmp -export LD_LIBRARY_PATH=/usr/lib/mesa-virtio - -# ------------- -# launch app -# ------------- -$@ -``` - -Save the file and run the following to start weston. - -``` -$ rvgpu-proxy -s <your_Area>@0,0 -n <IP_address_of_Receiver>:<Port_Number> & -$ EGLWINSYS_DRM_DEV_NAME=<RVGPU_DRM_DEVICE_PATH> <WORKDIR>/run_remote_app.sh rvgpu-wlproxy -s <your_Area> -S <your_WAYLAND_DISPLAY> & -``` -Replace the placeholders with the appropriate values: -- `<Port_Number>`: Port set in the renderer. -- `<your_WAYLAND_DISPLAY>`: Specify your WAYLAND_DISPLAY socket name, for example: wayland-uhmi-0 -- `<RVGPU_DRM_DEVICE_PATH>`: Specify rvgpu drm device path generated by rvgpu-proxy, for example: /dev/dri/rvgpu_virtio0 - -After completing these steps, the Weston screen from the Sender will be transferred and displayed on the Receiver using rvgpu-proxy and rvgpu-renderer. You can verify that everything is functioning properly by launching wayland applications on the Sender side, such as: -``` -$ WAYLAND_DISPLAY=<your_WAYLAND_DISPLAY> <WORKDIR>/run_remote_app.sh weston-simple-egl -f -``` - -You can also verify the touch or keyboard operation support of the RVGPU by using app such as -``` -$ WAYLAND_DISPLAY=<your_WAYLAND_DISPLAY> <WORKDIR>/run_remote_app.sh weston-smoke -$ WAYLAND_DISPLAY=<your_WAYLAND_DISPLAY> <WORKDIR>/run_remote_app.sh weston-editor -``` - -**Appendix** -- By building the RVGPU on Ubuntu, it is possible to enable bidirectional remote rendering between the agl-demo-platform and Ubuntu. -For the build procedure on Ubuntu, see the following URL: https://github.com/unified-hmi/remote-virtio-gpu
\ No newline at end of file |