On Tue, Dec 29, 2009 at 05:27:21PM -0700, Robert Holtzman wrote:
> On Mon, Dec 28, 2009 at 09:32:40PM +1030, Arthur Marsh wrote:
> > Robert Holtzman wrote, on 28/12/09 18:14:
> >
> > >
> > > One thing I forgot to include in my post is that when I got the computer
> > > the headphone volume was f
>> Can you tell me if hw:0,0 is exactly equivalent to the "default" ALSA
>> device *if* dmix is disabled with the following in /etc/asound.conf:
>>
>> pcm.!default {
>> type plug
>> slave.pcm hw
>> }
>
> No hw:0,0 talks directly to hardware (without conversions. Plug is a plugin to
> convert the fo
>> My Wavelength Proton USB DAC works with the "default" device and with
>> "plughw:0,0", but it does not work with "hw:0,0". I get the following
>> error:
>>
>> output: Failed to open "Wavelength Proton" [alsa]: ALSA device
>> "hw:0,0" does not support format 16: Invalid argument
>>
>> When tryin
Hi all,
Recently I downloaded alsa-driver 1.0.22 and tried to build for i.MX27
platform.
The "INSTALL" file enclosed in this release requires
"--with-cross=arm-linux-" configuration option to cross-compile alsa
driver for this ARM platform.
Here is my build process
#./configure --with-cross=ar
/usr/sbin/alsactl: set_control:1266: failed to obtain info for control #9
(No such file or directory)
/usr/sbin/alsactl: set_control:1266: failed to obtain info for control #10
(No such file or directory)
/usr/sbin/alsactl: set_control:1266: failed to obtain info for control #11
(No such file or di
