Please find below a brief summary of the progress Collabora have made last week on Pipewire and Weston/Wayland.
PipeWire
George:- Wrote extensive API documentation for WirePlumber's library, documenting
all the methods and objects. The generated HTML is not hosted anywhere
online yet, but you can easily build it from WirePlumber's source tree
(it is automatically built when compiling, if the 'hotdoc' tool is available)
- Studied the concepts of ALSA UCM in detail in order to recap the design
decisions that were made at the PipeWire hackfest in November 2019 and
document them
- Wrote a document explaining the design of the media & session management
objects and graphs in PipeWire:
https://gitlab.freedesktop.org/pipewire/pipewire/blob/master/doc/objects_design.md
This also mentions how objects are mapped to other subsystems and libraries,
including ALSA, ALSA UCM, V4L2, PulseAudio and JACK.
- Reviewed Julian's work on implementing volume fade in/out in wireplumber
Julian:
- Created wireplumber fade merge request and addressed all comments
- Started debuging why config-policy unit tests hang sometimes in wireplumber
- Off on Friday
Weston / Wayland
Marius:
- added server implementation (and some demo client examples)
for using agl-shell-desktop,
which is a protocol extension for regular XDG clients to bind
to and allow activating other
dekstop applications. This only resides in a sandbox branch
for now until next is back-merged
into master. Clients using it will receive XDG top level
surfaces events when these (surfaces)
get mapped, as well as those already mapped (at bind time).
- started doing agl-demo-platform-html5 builds for both
master/next. Found a couple of build failures,
one for web-runtime (chromium68) related to a missing include
header for the yocto kernel version,
and one for CAN requiring a newer kernel version (not really
sure what is the problem here)
generated by agl-service-can-low-level package.
- started looking into WAM and determine what is needed to be
done to convert/adapat to use
the agl-shell protocol (remove libwindowmanager/libhomescreen
dependencies and add supporting code for
using the private extension). Once I can generate/build the
web-runtime I should be able to continue.
Most likely, a more generic approach would be needed here to
allow, at run-time, to switch between the two
(that is, build WAM once but allow to bind to agl-shell and
chat with libwindowmanager/libhomescreen,
on the flip of a swich from an environment variable), but this
will be a collboration effort from
Collabora and Igalia.
Kind regards,
Nick
Links:
You receive all messages sent to this group.
View/Reply Online (#8119) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
