Skip to content

feat: prefer greetd from backports & install more CamX packages - #631

Open
Christopher Obbard (obbardc) wants to merge 3 commits into
mainfrom
wip/obbardc/multimedia-new-pkgs
Open

feat: prefer greetd from backports & install more CamX packages#631
Christopher Obbard (obbardc) wants to merge 3 commits into
mainfrom
wip/obbardc/multimedia-new-pkgs

Conversation

@obbardc

Copy link
Copy Markdown
Contributor
  • prefer greetd from backports to allow password change on login
  • install more camx packages

@obbardc

Copy link
Copy Markdown
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...

# audioreach-conf
# - audioreach-conf
# - audioreach-calibration-data

# tinyalsa
# - tinyalsa                                # provides /usr/bin/tinycap, /usr/bin/tinymix, /usr/bin/tinypcminfo, /usr/bin/tinyplay
# - tinycompress                            # provides /usr/bin/cplay, /usr/bin/crecord, /usr/bin/sofprobeclient


# Test suites
# - tinyalsa-tests                          # /usr/libexec/tinyalsa/tinyalsa_test
# - userspace-resource-manager-tests        # provides /usr/bin/UrmComponentTests, /usr/bin/UrmIntegrationTests
# - qmi-framework-utils                     # not sure what this does

# Broken apps - diag
# - qcom-diag                               # broken test app?
# - qcom-diag-router                        # broken service?

# broken sensor apps
# - qcom-sensors-test-apps                  # broken app?
# - sensinghub-session-client               # broken app?

{{- if eq $suite "trixie" }}
# device-specific CamX libraries; only pulled in on trixie as the
# camx-glymur and camx-hamoa packages it depends on are not ready
# for forky yet; see

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thinking about it, the prebuilts are only released for trixie so this may make sense and won't be fixed for a while?

another separate thought, perhaps we should gate the multimedia image on trixie only ?

@lool Loïc Minier (lool) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like there are some build/install issues, but otherwise happy with the changes

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 multimedia images install the out-of-tree drivers as DKMS source
packages, so every image build compiles kgsl-dkms and iris-vpu-dkms
against the target kernel. That burns CI minutes and leaves the build
disk almost full and it is unreliable at the moment: camx-dkms never
built under fakemachine at all and was already commented out.

These modules are about to be shipped prebuilt alongside the kernel
package, so pre-emptively stop building them here. Drop the DKMS
source packages together with the gcc and dkms packages installed to
build them and the fakemachine build parallelism workaround along
with the step which cleaned it up.

Until the prebuilt modules land, multimedia images therefore ship
without the Adreno GPU and Iris VPU kernel modules.

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
and 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants