feat: multimedia variant improvements - #631
Merged
Merged
Conversation
Contributor
Author
|
There are also these packages in QLI; I left them out of this PR as they are not strictly "QTI multimedia" apps, but arguably the audioreach/tinyalsa/tinycompress packages could be... |
Loïc Minier (lool)
requested changes
Sep 10, 2026
Loïc Minier (lool)
left a comment
Contributor
There was a problem hiding this comment.
looks like there are some build/install issues, but otherwise happy with the changes
Christopher Obbard (obbardc)
force-pushed
the
wip/obbardc/multimedia-new-pkgs
branch
2 times, most recently
from
September 16, 2026 15:07
72c0694 to
5532a37
Compare
Test Results 7 files ±0 21 suites ±0 16m 8s ⏱️ ±0s For more details on these failures, see this check. Results for commit 5532a37. ± Comparison against base commit 527975a. |
The Weston session logs in through greetd/agreety on a virtual console. greetd 0.10.3-4 in trixie cannot handle accounts with an expired password, preventing users from changing it on their first console login. greetd 0.10.3-7 includes the upstream fix: d/p/pam-change-authentication-token.patch: support expired passwords Cherry-pick the upstream fix so that an expired password no longer causes a login to fail outright: when pam_acct_mgmt() returns PAM_NEW_AUTHTOK_REQD, greetd now calls pam_chauthtok() with PAM_CHANGE_EXPIRED_AUTHTOK to let the user set a new password. Pin binary packages built from src to backports so that greetd >= 0.10.3-7~bpo13+1 is installed. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
The CamX firmware is already installed in the multimedia variant, but nothing exposes the cameras to userspace. Install qti-camera-server, the CamX service which exposes the cameras, along with the device-specific runtime libraries it needs to drive them. Also install CamX and FastCV test applications so the stack can be exercised. The device-specific libraries (camx-server-runtime-all) are restricted to trixie for now; the package depends on camx-glymur and camx-hamoa which are not yet built for forky. Link: qualcomm-linux/pkg-camx-glymur#8 Link: qualcomm-linux/pkg-camx-hamoa#20 Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Christopher Obbard (obbardc)
force-pushed
the
wip/obbardc/multimedia-new-pkgs
branch
2 times, most recently
from
September 17, 2026 18:51
9d7d434 to
dae42fd
Compare
The accelerated multimedia stack does not fit in the default 6GiB image. On trixie, CamX runtime packages fill the root filesystem during the build (e.g. currently around 5.6GiB, which leaves little free space for overhead). Build weston-multimedia as an 8GiB image while leaving the default size unchanged. The root filesystem grows to the storage device on first boot and unused space is compressed in the published artifacts. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
The image recipe unpacks rootfs.tar into the debos scratch directory before copying the tree into the mounted filesystem image with the filesystem-deploy action, so the disk-backed scratch space set with --scratchsize has to hold the whole uncompressed root filesystem. --scratchsize has been 6GiB since the default imagesize was bumped to 6GiB, which leaves no headroom at all: a root filesystem which fills a 6GiB image cannot be unpacked into a 6GiB scratch area. The weston-multimedia variant makes this unavoidable: it installs the accelerated multimedia stack and is built with -t imagesize:8GiB, so scratch is guaranteed to be too small and the image build fails while unpacking the root filesystem. Bump --scratchsize to an arbitrary 12GiB, comfortably above the largest image we currently build, until scratch is sized from imagesize instead of being hardcoded. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
The accelerated multimedia stack is not yet available for forky because the device-specific CamX runtime packages are missing. Building it is a waste of CI resources: a full image build (and the artifacts that go with it) for an image nobody can use currently. List the image combinations explicitly instead of taking the product of the suite and variant matrices. This avoids building unsupported images and prevents new suites or variants from being enabled unintentionally. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Christopher Obbard (obbardc)
force-pushed
the
wip/obbardc/multimedia-new-pkgs
branch
from
September 17, 2026 21:35
f6f51c0 to
dfdb6b6
Compare
Loïc Minier (lool)
approved these changes
Sep 18, 2026
Loïc Minier (lool)
left a comment
Contributor
There was a problem hiding this comment.
Clean, each commit made sense
For multimedia, I think it's ok for now, but we want to add back a forky flavor with less components "soon"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Multimedia variant changes: