Hi erebion,

I noticed you filed this ITP for tinyalsa back in August 2024. Thanks
for that!

Are you still working on it? If not, I'd like to take over ownership.
I have a package ready to go: it builds, is lintian-clean and has
autopkgtests. After coordination with Jordi from the ALSA team,
the source is on Salsa, maintained under the ALSA team
umbrella:

  https://salsa.debian.org/alsa-team/tinyalsa

It provides libtinyalsa2, libtinyalsa-dev and the tinyalsa utilities
(tinyplay, tinycap, tinymix, tinypcminfo). There's also a
tinyalsa-tests package with the upstream gtest suite, which the
autopkgtests run against snd-aloop virtual cards.

Why I think tinyalsa is worth having in Debian:

TinyALSA is a very thin layer around the kernel's ALSA PCM and control
ioctl interface (/dev/snd/pcmC*D*, /dev/snd/controlC*). There is no
alsa-lib plugin/configuration stack and no sound server like PipeWire
or PulseAudio in between, and it only depends on libc.

That makes it especially useful for:

 * embedded and resource-constrained systems, where a full alsa-lib
   plus a sound server is too heavy, or not wanted for a dedicated
   audio path;
 * low-level debugging of kernel audio drivers (e.g. ASoC/DPCM on SoC
   platforms). tinyplay/tinycap/tinymix exercise the hw device
   directly with exactly the parameters you give them, so you can
   tell whether a problem is in the driver or firmware or in one of
   the userspace layers on top (alsa-lib config, plugins, the session
   manager or the sound server);
 * bring-up of new boards, where the ALSA UCM profiles and
   PipeWire/WirePlumber configuration often don't exist yet;

If you'd still like to be involved, I'd be happy to add you to
Uploaders and co-maintain it within the ALSA team. If I don't hear
back within the next two weeks or so, I'd like to take ownership of
this ITP bug.

Cheers,
  Lukas

Reply via email to