[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 01:50:20 CEST 2007
man, it sux to have to type in all the little '>' myself, outlook web access's non rfc compliant behavior diminishes my productivity...
From: alsa-devel-bounces at alsa-project.org on behalf of Takashi Iwai
Sent: Wed 3/28/2007 3:11 AM
To: John Utz
Cc: 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?
>>At Tue, 27 Mar 2007 17:55:56 -0700, John Utz wrote:
>> how does this work?
>> an explicit explanation would be great, but i'd even settle for a
>> vague handwavy one at this point.
> Please elaborate the question...
absolutely! sorry i wasnt clear enuf.
here is the next phase of the problem that i need to solve:
i am working on a space constrained embedded system. it will always have the same:
hardware (via8237rplus with a via vt1618 codec)
software (the audio player application that i maintain)
content format (the music get's encoded by my music programmer coworkers to a fixed format)
since i dont need a generic solution, it would be very helpful to me to not use alsa-lib and just use the alsa modules the way that our current version of the player uses /dev/dsp from the alsa oss-compat kernel modules.
i'd like to open and playback to /dev/snd/pcmC0D0p and /dev/snd/pcmC0D1p directly if it's a reasonable thing to do.
Alsa-devel mailing list
Alsa-devel at alsa-project.org
More information about the Alsa-devel