From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: trying to open ucm2/conf.d/simple-card/Unknown-UnknownProduct-.conf for PinePhonePro
Date: Mon, 15 Aug 2022 18:45:41 +0200 (CEST) [thread overview]
Message-ID: <20220815164541.DC5FCF804AE@alsa1.perex.cz> (raw)
In-Reply-To: <1660581935143290997-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #199 was edited from ollieparanoid:
Hi,
we are trying to narrow down why alsa-lib tries to open `/usr/share/alsa/ucm2/conf.d/simple-card/Unknown-UnknownProduct-.conf` instead of the proper path `/usr/share/alsa/ucm2/PinePhonePro/PINE64-PinePhonePro-.conf` with custom (to-be-upstreamed to alsa-ucm-conf.git) ucm configurations we are using in postmarketOS for the PinePhonePro: https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/community/device-pine64-pinephonepro/ucm
It only happens for some users, but not for everybody. I've taken a quick look at the code but didn't see right away where the wrong path is built, `git grep UnknownProduct` gives no results.
Could somebody give us a hint where to look? I don't really have a clue how this works. Thanks!
Downstream discussion: https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3356
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/199
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2022-08-15 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1660581935143290997-webhooks-bot@alsa-project.org>
2022-08-15 16:45 ` GitHub issues - edited [this message]
[not found] <1660581933620764971-webhooks-bot@alsa-project.org>
2022-08-15 16:45 ` trying to open ucm2/conf.d/simple-card/Unknown-UnknownProduct-.conf for PinePhonePro GitHub issues - opened
[not found] <1660581465346544981-webhooks-bot@alsa-project.org>
2022-08-15 16:37 ` GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220815164541.DC5FCF804AE@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox