Hi All,
Please find below a brief summary of the progress Collabora have made last week on Pipewire and Weston/Wayland.
Week 10 2020
PipeWire
George:
- Reviewed and merged Julian's MRs, which add:
- support for handling JACK clients
- support for running on top of a JACK server, slaved
- support for discovering and linking video cameras to video
capture applications
This work is mostly addressing desktop needs, targetting to
make WirePlumber
the default session manager on the desktop.
- Continued work on the new session management APIs
- implemented WpTransition, a class to handle complex async
operations using a state machine
- layed out a plan to integrate hooks that will allow
scripting parts of the logic
- documented the design at
https://gitlab.freedesktop.org/pipewire/wireplumber/-/wikis/Session-Graph-Items
Julian:
- Finished adding support for Video in Wireplumber
- Implemented DBus Device Reservation logic in Wireplumber to
release/acquire
an audio device when idle/running in case a second audio
server is running.
Still need to implement unit tests to make sure the logic
works properly.
Weston / Wayland
Daniel:
Marius:
- re-polished the agl-shell-desktop protocol, version now has a MR
open. Should allow
regular XDG applications to instruct the compositor to switch
applications. This is a distinct
protocol from agl-shell and only intenteded for regular
applications. In combination with the policy
part should provide the means to further granulate which
application can actually make use of it.
- policy framework API done. MR open to discussion. The framework
adds hooks for activation/
creation and committing (of surfaces). Transitional states are
handled with the help of policy rules,
which allow to handle various situations specific to automotive
scenarios: car in state X, perform operation Y,
at timeout Z. This contains the bare minumum to incorporate a more
specialized policy engine. Fairly
minimal documentation added as well, with a default policy
installed to provide a nice and
easier example that allows further customization.
- WAM/chromium68. The only update here is that I've started to
ramp up a bit and started to read
up more about integrating (the agl-shell) protocol inside
chromium68 and expose it as a interface to WAM.
I'm still learning about the processes separation and this might a
bit problematic in case there's a
need to pass data between runtime process (which is starting the
application) and renderer one (which
handles the wayland connection and surface creation). All the
feedback I have around this suggests that
it easier to proceed on doing it under/in chromium68, but this is
will take considerable amount of time.
This will be focus of the current week.
Kind regards,
Nick
Links:
You receive all messages sent to this group.
View/Reply Online (#8151) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
