From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Feature Request: conf.d for USB-Audio
Date: Mon, 8 Sep 2025 04:00:53 +0200 (CEST) [thread overview]
Message-ID: <18632c2cfcac1e00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18632c2cfab95b00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #609 was edited from FrostyCoolSlug:
The release cadence of `alsa-ucm-conf` tends to be a little on the slow side (generally around 6 months between releases), but the problem I'm hitting currently is the requirement for users to manually edit `USB-Audio.conf` in order to get earlier support for their devices (and depending on distribution, support could be delayed upwards of two years).
I think a method where a package could be created to drop files into a conf.d style directory would allow for a users device to be configured, without the need for manually editing `USB-Audio.conf` to add support.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/609
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2025-09-08 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18632c2cfab95b00-webhooks-bot@alsa-project.org>
2025-09-08 2:00 ` GitHub issues - edited [this message]
[not found] <18632c26b7126d00-webhooks-bot@alsa-project.org>
2025-09-08 2:00 ` Feature Request: conf.d for USB-Audio 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=18632c2cfcac1e00-webhooks-bot@alsa-project.org \
--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;
as well as URLs for NNTP newsgroup(s).