Re: Questions on agl-weston-remoting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 16, 2020 at 03:29:45PM +0900, 변준기 wrote:
> Hello, I am Jungi Byun at LG Electronics.
Hi Jungi,
> 
> 
> Recently I am interested in Automotive Grade Linux(AGL), especially the
> agl-weston-remoting feature.
> I have tried to see this feature on raspberrypi 4 but I do not know how to
> configure this feature and to see it works well.
> 
> 
> What I did to take look into agl-weston-remoting are followings:
>     1) Referring https://wiki.automotivelinux.org/agl-distro/agl-raspberrypi, I
> made the agl-demo-platform image on RPi4.
>     2) I checked that the image does not have remoting-plugin.so.
>     3) Referring Vlad's patch https://gerrit.automotivelinux.org/gerrit/c/AGL/
> meta-agl/+/25671,
> 
>        I made the agl-demo-platform image on RPi4 again and then checked that
> this image has remotin-plugin.so.
>     4) Referring Murray's patch https://gerrit.automotivelinux.org/gerrit/c/AGL
> /meta-agl/+/24567,
> 
>        I appended the remote-output section in weston.ini on RPi4 of receiver's
> side.
>     5) Referring https://github.com/wayland-project/weston/tree/master/remoting
> and using the script remoting-client-receive.bash in it,
The gerrit patches are for a different feature that, besides streaming
out buffers, it would also be able to transfer back to the compositor
input events. At the moment it is in state of flux due to other pending
changes. Fyi, 'agl-weston-remoting' is for intended to work with
cluster-demo, not demo-platform.

Nevertheless, if the plug-in is built and the compositor loads it you
should be able to use it.

> 
>        I tried to take look into agl-weston-remoting but there are no changes
> on receiver's display.
> 
> 
> I think that this feature is similar to mirroring(or screen-sharing) so I
> expected that receiver's display shows some(or all) of sender's one.
> Using the remoting-client-receive.bash, some lines prints but receiver's
> display is the same as before:
> 
> 
>     raspberrypi4-64:~# ./remoting-client-receive.bash 5005
>     Setting pipeline to PAUSED ...
>     Pipeline is live and does not need PREROLL ...
>     Got context from element 'autovideosink0': gst.gl.GLDisplay=context,
> gst.gl.GLDisplay=(GstGLDisplay)"\(GstGLDisplayWayland\)\
>     gldisplaywayland0";
>     Setting pipeline to PLAYING ...
>     New clock: GstSystemClock
> 
> 
> I also found these log messages in /run/platform/display/compositor.log but I
> do not know whether these are related to see this feature.
> 
> 
>     [03:06:45.075] Loading module '/usr/lib/libweston-8/
> remoting-plugin.so'                                                                 
>     [03:06:45.154] Registered plugin API 'weston_remoting_api_v1' of size
> 64
>     [03:06:46.503] Installing 'allow-all' policy engine
> 
>     ...
> 
>     [03:06:46.505] GST pipeline: rtpbin name=rtpbin appsrc name=src !
> videoconvert ! video/x-raw,format=I420 ! jpegenc ! rtpjpegpay !
>     rtpbin.send_rtp_sink_0 rtpbin.send_rtp_src_0 ! udpsink name=sink host=
> 192.168.0.49 port=5005 rtpbin
^^ this means gstreamer pipeline has been created.
> 
>     [03:06:46.642] Output 'remote-1' enabled with head(s) remoting
> 
>     [03:06:46.642] remoted output 'remote-1' enabled
> 
>     [03:06:46.643] Sending ready to systemd
> 
>     [03:06:47.138] gst: Warning: sink: Pipeline construction is invalid, please
> add queues.
> 
>     [03:06:48.543] gst: Warning: sink: Error sending UDP packets
> 
>     ...                                                                                                                                                     
> 
>     [03:06:49.653] gst: Warning: udpsink1: Error sending UDP packets
> 
>     Date: 2020-12-16 UTC
> 
>     [01:10:57.350] WARNING: Output does not have a background       
> 
>     [01:10:57.350] Usable area: 1920x1080+0,0                           
> 
>     [01:10:57.350] (background) position view 0x55b4fb2dc0, x 0, y 0, on output
> HDMI-A-1
> 
> 
> Please let me know any guidance or reference to solve this problem or if you
> need further information about this.
You need to let the compositor know which surfaces to stream and for
that you can use agl-shell-app-id=app_id_of_the_application, under the
'[remoting-output]' section, where you define remoting parameters. 

Then start your application. The application has to set an appid for itself.
All demo applications using Qt have that set-up so you can use
that/those as an example. The compositor should also print the fact it will 
forward it to another output.

Also, programmatically you should be able to do that using agl-shell-desktop
protocol.
> 
> I am sure your expertise will be helpful for me.
If that doesn't help, please, open a JIRA ticket to continue there.
> 
> 
> 
> Best Regards,
> 
> 
> Jungi Byun
> 
> Research Engineer
> 
> Software Platform Lab., SW Center, LG Electronics Inc.
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8945): https://lists.automotivelinux.org/g/agl-dev-community/message/8945
Mute This Topic: https://lists.automotivelinux.org/mt/78996233/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-


Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux