Craig,If I recompile the filesystem enabling the following packages: aumix and bplay will i simply be able to use them when I flash the new file system. I suppose getting nitty gritty, my real question is about how one uses the menuconfig in the buildroot.Mark
On 6/20/06, Engel, Nick <email@example.com > wrote:
> You'll want to use the OSS emulation layer though, which is much,
> much lighter weight than the ALSA userspace libraries & utils.
Has anyone had success using native ALSA? i.e. not using OSS emulation?
I'm using the latest SVN build 1005 and can't get any apps to open the
Using http://alsa.opensrc.org/faq/#FAQ007 as an 'Is ALSA working?'
reference, I find that the modules are correctly loaded and /dev/snd and
/proc/asound all appear to list and say the right things.
ALSA lib control.c:817:(snd_ctl_open_noupdate) Invalid CTL default
amixer: Mixer attach default error: No such file or directory
ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:547: audio open error: No such file or directory
I'm wondering if the PXA2XX drivers do things a little differently.
There is no /dev/snd/hw* like my PC.
Both the kernel and userland libs are the same version ( 1.0.11rc2).
I also figured I should be able to do something like this (as I'm
assuming pcmC0d0c is a character device):
# cat /dev/urandom > /dev/snd/pcmC0D0c
cat: Write Error: Invalid argument
Am I missing something? Anyone have any ideas?
This message (including any attachments) may contain confidential
information intended for a specific individual and purpose. If you
are not the intended recipient, delete this message. If you are
not the intended recipient, disclosing, copying, distributing, or
taking any action based on this message is strictly prohibited.
gumstix-users mailing list