Hi All,
Please find below a brief summary of the progress Collabora have made last week on Weston/Wayland.
Weston / Wayland
Marius
- SPEC-3518 (agl-compositor exits prematurely on upsquared). It
seems that on some platforms
the DRM device node doesn't exists when the compositor starts up.
Due to some missing clean-up
code in the DRM-backend of the compositor, it results in a
combination of factors that will not
allow the compositor to start up correctly, even if the DRM node
is created at a rather short
period time after that. I've posted an upstream patch to fix the
later issue but the original
issue (as why the DRM device isn't available at the time is
something that need further
investigation.
I've recommended a few tests to narrow the issue, and an update
the systemd unit file
to wait until the DRM device is created). I suspect that the
driver had some issues in the
past but that was masked by systemd service unitd that resets the
tty upon starting/ending
the compositor (which were removed from unitd systemd at some
point) or updates the
driver/kernel caused this issue. Even so, we would've expected
that this issue to pop-up much
sooner, so maybe another explanation or a combination of factors
are leading to this.
- SPEC-3522 (Resize & Flickering of applications at start-up).
Applications do not have an initial
size will default to a initial size set-up by qtwayland (500x500).
Right after that, the compositor
will instruct the applications to resize to a different size (the
geometry area without the panels).
This seems to "generate" a short flicker (drawing a few white
frames -- similar to a clear color
-- the default background color in qtwayland). If the application
will instead use hard-coded values,
matching the geometry area but even smaller or higher sizes), or
handing it over the information
size before trying to load the QML file, will not trigger that
"flickering" effect. Requires
more investigation into qtwayland resize/repainting mechanism to
see why using the default qtwayland
size results in that flickering issue.
Walter
General reaseach about AGL and its components
- SPEC-3410 (PipeWire not working on i.MX8MQ EVK). It seems that
due to a bad reporting about the frames
processed by the audio stack PipeWire is not able to reproduce
audio on iMX8MQ EVK. In this sense, review
Pipewire and ALSA drivers to understand the audio issue. Improve
sound driver fsl_sai to report FIFO usage.
Kind regards,
Nick
Links:
You receive all messages sent to this group.
View/Reply Online (#8561) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
