[linux-audio-dev] ok, jump on slashdot right now, ALSA story in progress

Vincent Touquet vincent.touquet at pandora.be
Sat Nov 2 04:37:01 UTC 2002

On Fri, Nov 01, 2002 at 11:10:40PM -0500, Paul Davis wrote:
>i don't want to blow my moderator points this time, so get busy. there
>is lots of confusion, mis-information and general cluelessness in the
>responses so far. get to it, provide me with some stuff to moderate
>upward ...

I use Debian on every machine I control
and I like it a lot, however configuring
alsa has proven difficult even to me.

Only recently I 'noticed' I can just
run alsaconf, and copy the output from
the app from /etc/alsa/modutils/0.5
to /etc/modutils/alsa (or was it 
/ets/alsa/modutils/0.9, I fail to remember :),
where it gets picked up by the init script ...
Its possible you need to change the names
of some modules in the process too.

Its easy, but undocumented (at least
I didn't figure out where to find this info).

I wouldn't go as fas as to blame any
developers for this. ALSA is being
integrated in the mainline kernel
and that by itself should keep
everyone busy.

I think its somehow the duty of the
people who figured out how to
configure it in an easy way to
write it up (cfr. Patricks quicktoots 

I'm willing to do just that.

The question is, what is the best place
to write these things up ?
Do I start to work on Debian specific
documentation, or is it better to help
on some general alsa documentation ?

Or maybe this documentation exists
and there needs to be some more
advocacy to point everyone in the
right direction.

the will is present,
it only needs some direction to go in IMHO,
regards (and thanks to all the coders)

More information about the Linux-audio-dev mailing list