From: lane-brain <lane-brain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sof-firmware doesn't install alsa-ucm-conf, a necessary package for sof audio driver initialization
Date: Tue, 24 Nov 2020 05:07:42 +0100 [thread overview]
Message-ID: <20201124040742.3bLE6dheuqKeioVVoJEtRnjKCiCZuDNASNFcUMmgEyI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
New comment by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/issues/26419#issuecomment-732547623
Comment:
Here is my template, it was based off of your template for `sof-firmware`.
One last word, in my troubleshooting last year I learned that pulseaudio makes use of these ucm config files to autoconfigure detected cards, I'm not sure what decision would be proper to make considering dependencies on pulseaudio because in certain cases it still works out of the box without the ucm conf files. For example, using snd_hda_intel I had speakers working but no mic, but that driver doesn't fully support my laptop's dsp so that's to be expected. Definitely they should be deps for `sof-firmware`.
```
# Template file for 'alsa-ucm-conf'
pkgname=alsa-ucm-conf
version=1.2.4
revision=1
archs="i686* x86_64*"
depends="alsa-lib"
wrksrc=${pkgname}-${version}
short_desc="ALSA Use Case Manager topology configurations"
maintainer="lane-brain <lane@mailbox.org>"
license="BSD-3-Clause"
homepage="https://github.com/alsa-project/alsa-ucm-conf"
distfiles="https://www.alsa-project.org/files/pub/lib/${pkgname}-${version}.tar.bz2"
checksum=2c3b535c77dcb9aaf62a61f4f8324f1ab184162f105f7ec9ed1e37c742fcd340
do_install() {
cd ${wrksrc}
find ucm2 -type f -iname "*.conf" -exec install -vDm 644 {} "${DESTDIR}/usr/share/alsa/"{} \;
find ucm2 -type l -iname "*.conf" -exec cp -dv {} "${DESTDIR}/usr/share/alsa/"{} \;
install -vDm 644 README.md -t "${DESTDIR}/usr/share/doc/${pkgname}"
install -vDm 644 ucm2/README.md -t "${DESTDIR}/usr/share/doc/${pkgname}/ucm2"
vlicense LICENSE
}
```
next prev parent reply other threads:[~2020-11-24 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 0:29 [ISSUE] " lane-brain
2020-11-24 0:26 ` cinerea0
2020-11-24 2:33 ` lane-brain
2020-11-24 2:35 ` lane-brain
2020-11-24 2:35 ` lane-brain
2020-11-24 4:07 ` lane-brain [this message]
2020-12-10 18:48 ` [ISSUE] [CLOSED] " ericonr
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=20201124040742.3bLE6dheuqKeioVVoJEtRnjKCiCZuDNASNFcUMmgEyI@z \
--to=lane-brain@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).