[alsa-devel] how does hw:0, 1 eventually get mapped to /dev/snd/controlC0 and company? is this on the wiki somewhere?
John.Utz at dmx.com
Fri Mar 30 20:22:47 CEST 2007
From: alsa-devel-bounces at alsa-project.org on behalf of Takashi Iwai
Sent: Fri 3/30/2007 11:18 AM
To: John Utz
Cc: alsa-devel at 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 at suse.de]
> Sent: Fri 3/30/2007 5:52 AM
> To: Lee Revell
> Cc: John Utz; alsa-devel at 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.
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!
Alsa-devel mailing list
Alsa-devel at alsa-project.org
More information about the Alsa-devel