Hi All,
Please find below a brief summary of the progress Collabora have made last week on Weston/Wayland.
Weston / Wayland
Marius:
- Re-worked a bit the order in which the (remote) outputs are
enabled such that we delay enabling
remote outputs to avoid the situation where the client shell
determines that primay output is
the remote one (SPEC-3280 -' Remote-display windows for CES IC
demo').
A similar patch exists for weston from what I've seen. Added for
both local output and remote output
the option to specify the application id which should allow
assiging outputs to distinct application.
tbtnavi and homescreen (client shell) now contain example code how
to place panels/bg and regular application
on different outputs. This uses underneath the xdg_output
(wayland-extension) protocol extension
to distribute output names, which the toolkit makes use of and
ultimately allows application to identify
outputs in human-like form.
Found that for remote outputs, the remoting plug-in (the one
streaming data using a gst pipeline)
is using the same connector name. A patch can be easily added to
remidy this issue if there's a need to
use multiple remote outputs.
Still related to this item, found that QEMU virtio-gpu is lacking
DMA buf imports resulting in gstreamer
throwing in some errors and is unable to use remote output. There
seems to be a pending series to
address it but will take some time for those to be merged in and
reach AGL.
- Tested H3 once more and found that two issues: one related to
the fact that the compositor seems
to be started after the widgets (have started, homescreen &
launcher) which means we need some
proper depedency (SPEC-3411) for the compositor from applications
require to be started at start-up and
need to use the display.
An indirect consequence of this is the alexa-viewer application
which, when started last, will receive
keyboard/pointer/touch focus and occludes the lowered stack
surfaces (panels/regular application). Due to the
fact that (presumably, by using local alpha) to hide its contents,
the situation was hard to spot. Provided
already a temporary fix, but looking at a better alternative, by
modifying the application and by using
the agl-shell-desktop protocol (see SPEC-3412 for a lengthier and
thorough investigation and explanation).
- Fixed (SPEC-3403) mixer application. All applications should be
displayed correctly.
Things currently looking into:
- (hopefully) publish SPEC-3280 series, depending on SPEC-3334 to
be merged
- SPEC-3386 - Documentation improvements -- provide a diagram
interaction / overall architecture
picture, requested
- SPEC-3413 & SPEC-3394 - additional hooks to control the
binding of agl-shell-desktop interface and provide a deny-all
policy engine to use as examples, requested
- SPEC-3412 - alexa-viewer occluding surfaces even if not
displayed -- modify application to use agl-shell-desktop
instead of 'fixing' from the compositor
Kind regards,
Nick
Links:
You receive all messages sent to this group.
View/Reply Online (#8412) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
