![](https://secure.gravatar.com/avatar/4c5cb07bd220c6cf7084e2debf005337.jpg?s=120&d=mm&r=g)
-----Original Message----- From: alsa-devel-bounces@alsa-project.org on behalf of Takashi Iwai Sent: Fri 3/30/2007 11:18 AM To: John Utz Cc: alsa-devel@alsa-project.org; Lee Revell Subject: Re: [alsa-devel] how does hw:0, 1 eventually get mapped to /dev/snd/controlC0 and company? is this on the wiki somewhere?
At Fri, 30 Mar 2007 10:00:37 -0700, John Utz wrote:
-----Original Message----- From: Takashi Iwai [mailto:tiwai@suse.de] Sent: Fri 3/30/2007 5:52 AM To: Lee Revell Cc: John Utz; alsa-devel@alsa-project.org Subject: Re: [alsa-devel] how does hw:0, 1 eventually get mapped to /dev/snd/ controlC0 and company? is this on the wiki somewhere?
The alsa-lib <-> kernel interface is intentionally undocumented. The only officially supported interface to ALSA is via alsa-lib.
- Well, not completely intentional. But we _recommend_ alsa-lib as the
- primary accessor, and at least I have no interest in writing another
- accessor right now. The documentaion itself is always good ;)
which documentation? i thought that i'd looked at it all and i didnt get a sense of what i needed, did i miss something?
* * Well, I should have written "the documentation would be good". It's a * follow up to Lee's comment.
:-)
dang.
i was *really* hopeful there for a while!
* There is no official documentation for now indeed, but you can guess * the necessary syscalls easily from asound.h.
thankyou, i'll go look at that!
* Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel