June 2007 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] $1000 bounty for getting audio working under linux on a Osprey 440
by Nathan Allen Stratton 25 Jun '07

25 Jun '07

Need to get audio working on Osprey 440 card. http://www.viewcast.com/pages.asp?page=osprey-440 The card is bt878 based, and ViewCast says it is supported on linux however not something they support. Audio is not detected by default, but does how up when you do a modprobe snd-bt87x load-all(see below). However I have not been able to pull audio from the card (only get high pitched noise). Bid may require patching bt878.c if modprobe options don't work. Only mono support is required. [root@… [View More]video share]# amixer Simple mixer control 'Bass',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 48 Mono: 30 [62%] Simple mixer control 'Bass Boost',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Treble',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 48 Mono: 24 [50%] Simple mixer control 'PCM',0 Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined Playback channels: Front Left - Front Right Capture channels: Mono Limits: Playback 0 - 44 Capture 0 - 15 Mono: Capture 15 [100%] [15.00dB] [on] Front Left: Playback 44 [100%] [3.00dB] [on] Front Right: Playback 44 [100%] [3.00dB] [on] Simple mixer control 'PCM Capture Source',0 Capabilities: enum Items: 'PCM' 'Mic' 'Input 2' Item0: 'Input 2' Simple mixer control 'PCM',1 Capabilities: cvolume Capture channels: Mono Limits: Capture 0 - 656 Mono: Capture 0 [0%] [-41.00dB] Simple mixer control 'Mic',0 Capabilities: cvolume Capture channels: Mono Limits: Capture 0 - 15 Mono: Capture 0 [0%] [16.00dB] Simple mixer control 'Auto Gain Control',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] [root@video share]# amixer -c 1 Simple mixer control 'FM',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] Simple mixer control 'Mic/Line',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Mono Mono: Capture [on] Simple mixer control 'Capture',0 Capabilities: cvolume Capture channels: Mono Limits: Capture 0 - 15 Mono: Capture 15 [100%] Simple mixer control 'Capture Boost',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'TV Tuner',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] :::::::::::::: cards :::::::::::::: 0 [INport ]: USB-Audio - INport Xitel INport at usb-0000:00:1d.0-1, full speed 1 [Bt878 ]: Bt87x - Brooktree Bt878 Brooktree Bt878 at 0xd8001000, irq 16 2 [Bt878_1 ]: Bt87x - Brooktree Bt878 Brooktree Bt878 at 0xd8003000, irq 17 3 [Bt878_2 ]: Bt87x - Brooktree Bt878 Brooktree Bt878 at 0xd8005000, irq 18 4 [Bt878_3 ]: Bt87x - Brooktree Bt878 Brooktree Bt878 at 0xd8007000, irq 19 :::::::::::::: devices :::::::::::::: 2: : timer 3: : sequencer 4: [ 0- 0]: digital audio playback 5: [ 0- 0]: digital audio capture 6: [ 0] : control 7: [ 1- 1]: digital audio capture 8: [ 1- 0]: digital audio capture 9: [ 1] : control 10: [ 2- 1]: digital audio capture 11: [ 2- 0]: digital audio capture 12: [ 2] : control 13: [ 3- 1]: digital audio capture 14: [ 3- 0]: digital audio capture 15: [ 3] : control 16: [ 4- 1]: digital audio capture 17: [ 4- 0]: digital audio capture 18: [ 4] : control :::::::::::::: hwdep :::::::::::::: *** INport: directory *** :::::::::::::: modules :::::::::::::: 0 snd_usb_audio 1 snd_bt87x 2 snd_bt87x 3 snd_bt87x 4 snd_bt87x *** oss: directory *** :::::::::::::: pcm :::::::::::::: 00-00: USB Audio : USB Audio : playback 1 : capture 1 01-01: Bt87x Analog : Bt87x Analog : capture 1 01-00: Bt87x Digital : Bt87x Digital : capture 1 02-01: Bt87x Analog : Bt87x Analog : capture 1 02-00: Bt87x Digital : Bt87x Digital : capture 1 03-01: Bt87x Analog : Bt87x Analog : capture 1 03-00: Bt87x Digital : Bt87x Digital : capture 1 04-01: Bt87x Analog : Bt87x Analog : capture 1 04-00: Bt87x Digital : Bt87x Digital : capture 1 *** seq: directory *** :::::::::::::: timers :::::::::::::: G0: system timer : 1000.000us (10000000 ticks) P0-0-0: PCM playback 0-0-0 : SLAVE P0-0-1: PCM capture 0-0-1 : SLAVE P1-0-1: PCM capture 1-0-1 : SLAVE P1-1-1: PCM capture 1-1-1 : SLAVE P2-0-1: PCM capture 2-0-1 : SLAVE P2-1-1: PCM capture 2-1-1 : SLAVE P3-0-1: PCM capture 3-0-1 : SLAVE P3-1-1: PCM capture 3-1-1 : SLAVE P4-0-1: PCM capture 4-0-1 : SLAVE P4-1-1: PCM capture 4-1-1 : SLAVE :::::::::::::: version :::::::::::::: Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC). unknown card 0x878-0x70:0xff07, using default rate 32000 please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)lists.sf.net> ACPI: PCI Interrupt 0000:06:04.1[A] -> GSI 16 (level, low) -> IRQ 16 unknown card 0x878-0x70:0xff07, using default rate 32000 please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)lists.sf.net> ACPI: PCI Interrupt 0000:06:05.1[A] -> GSI 17 (level, low) -> IRQ 17 unknown card 0x878-0x70:0xff07, using default rate 32000 please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)lists.sf.net> ACPI: PCI Interrupt 0000:06:06.1[A] -> GSI 18 (level, low) -> IRQ 18 unknown card 0x878-0x70:0xff07, using default rate 32000 please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)lists.sf.net> ACPI: PCI Interrupt 0000:06:07.1[A] -> GSI 19 (level, low) -> IRQ 19 ><> Nathan Stratton CTO, Voila IP Communications nathan at robotics.net nathan at voilaip.com http://www.robotics.net http://www.voilaip.com [View Less]

2 3

[alsa-devel] pcm->private_data is NULL in alsa core!!
by Pharaoh . 22 Jun '07

22 Jun '07

Hi I am writing an alsa driver for my omap based board. I am testing it using cat /dev/audio currently, i.e. I have OSS emulation turned on. This is an initial round of testing and I will use alsa-libs and utils later. My problem is: I have set the pcm->private_data = my_chip after registering the pcm ops, after referring various standard drivers in alsa tree. My module is insmoded properly but after I do snd_card_register(card) the pcm->private_data is corrupted !! Before this step, … [View More]

2 14

[alsa-devel] AT91 SoC PCM Capture
by Paul Kavan 22 Jun '07

22 Jun '07

I am wondering what piece of code contains the capture functionality for the at91 soc. I am hoping to see how and when the pcm activates the ssc at read time. I just cannot figure out why TD0 would behave at such with this set of code and yet behave correctly with my polling code. Not a criticism....just wanting to figure this out. Paul -- *************************************** Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan(a)gmail.com ***************************************

2 1

[alsa-devel] Osprey 440 almost supported!!! Need X9221 i2c support!
by Nathan Allen Stratton 22 Jun '07

22 Jun '07

This card does not use analog bt878a inputs, but rather the digital input. To get audio working I set the mask to 000303, first two bits are for the audio rate, 00 is 32000, 01 is 41000, 10 is 4800. The first two bits in the next byte are for balanced or unbalanced audio input. 0x00 for unbalanced and 0x100 for balanced. So I am using: modprobe bttv card=140 bttv_gpio=1 bttv_verbose=2 bttv_debug=1 gpiomask=0x020303 audioall=0xFFFDFC bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at 0000:08:… [View More]

2 2

[alsa-devel] Driver for Creamware / SonicCore Pulsar, which information needed?
by Kaspar Schleiser 22 Jun '07

22 Jun '07

Hey, I've got a Creamware Pulsar DSP card. As it actually has NO support for linux, I asked the vendor whether support was planned or if I could get necessary technical information. they answered they'd not have concrete plans on supporting linux and what information I'd need for the development of a driver. As I never wrote a driver, I don't know that, so maybe you could help me giving a useful answer ... What do we need to write a driver? Would anyone be interested in writing a driver? I … [View More]

1 0

[alsa-devel] Steps get aplay and arecord working on an embedded board
by Pharaoh . 22 Jun '07

22 Jun '07

Hi I have to test my audio driver on an omap based board. I have got the lib and utils on my board but dont know the exact steps to follow for using aplay etc. Can anyone point me to relevant documentation? Couldn't find any. Or just brief outline about the steops to follow would be great help. -pharaoh

2 2

[alsa-devel] What is CONFIG_I2C_MODULE?
by Timur Tabi 21 Jun '07

21 Jun '07

In a lot of ALSA drivers, I see this: #if defined(CONFIG_I2C) || defined(CONFIG_I2C_MODULE) What is CONFIG_I2C_MODULE? I've searched all the Kconfigs, and I cannot see this configuration option. -- Timur Tabi Linux Kernel Developer @ Freescale

1 0

[alsa-devel] HDA - Change default configuration for Fujitsu Si3515.
by Tobin Davis 21 Jun '07

21 Jun '07

This patch changes the default configuration for the Fujitsu Siemens Si3515 Laptop. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

1 0

[alsa-devel] Help with SoC alsa.conf
by Paul Kavan 21 Jun '07

21 Jun '07

I am trying to determine an appropriate conf file for my AT91SAM9260ek running linux-2.6.22-rc1 and the following alsa drivers: <6>Advanced Linux Sound Architecture Driver Version 1.0.14rc4 (Wed May 09 09:51:39 2007 UTC). <6>ASoC version 0.13.0 <4>AT91SAM9260EK W6811 Driver <1> <6>w6811: W6811 PCM SoC Audio 0.1 <6>asoc: W6811 <-> at91-ssc0 mapping ok <6>grh_ek_w6811: W6811 PCM in Slave Mode <6>ALSA device list: <6> #0: GRH_EK_W6811 (… [View More]W6811) I have installed alsa-lib-1.0.14a and alsa-utils-1.0.14 on the at91sam9260. The default conf file produces sound using speaker-test and aplay, but will not record using arecord. Frank Mandarino has been kind enough to lend me a barebones conf that worked for him: pcm.!default { type hw card 0 } pcm.hw { type hw card 0 device 0 subdevice 0 } ctl.!default { type hw card 0 } ctl.hw { type hw card 0 } but produces the following for me: /usr/share/alsa $ aplay -l **** List of PLAYBACK Hardware Devices **** ALSA lib conf.c:3949:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL hw:0 aplay: device_list:213: control open (0): Invalid argument ALSA is *very* new to me and I am unsure how to interpret any of this. I am using a dumb W6811 pcm codec. I am fairly confident the machine/codec driver is working as expected, so I need to determine what I can do to get alsa to play nice with it as well. When I use the default alsa.conf produced from making alsa-libs, I get the following: /usr/share/alsa $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: GRHEKW6811 [GRH_EK_W6811], device 0: W6811 W6811-PCM-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 record and playing do not seem to work. When I try: /usr/share/alsa $ arecord -d5 test.wav Recording WAVE 'test.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono Aborted by signal Interrupt... It does not stop at 5 seconds....I have to interrupt it manually. Furthermore, it does not appear to record anything as when I: /usr/share/alsa $ aplay test.wav Playing WAVE ' test.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono The speaker pops once, but no audio. Finally, when I use speaker-test, I get some weird results. Doing: /usr/share/alsa $ speaker-test -r8000 -c1 -f1000 -tsine -l1 speaker-test 1.0.14 Playback device is default Stream parameters are 8000Hz, S16_LE, 1 channels Sine wave rate is 1000.0000Hz Rate set to 8000Hz (requested 8000Hz) Buffer size range from 64 to 32768 Period size range from 32 to 8192 Using max buffer size 32768 Periods = 4 was set period_size = 8192 was set buffer_size = 32768 0 - Front Left Time per period = 5.086305 Gives me a wave composed of both the 1k sine and likely a 2k sine. If I go much below 1k, I get a periodic wave, but it looks more like a heart beat. My codec expects u-law, so that may be the problem with speaker-test. However, the fact the aplay and arecord are not working give me pause. I would be greatly appreciative of any insights, pointers, etc. If there is more information that would be helpful, please ask. Thanks. Paul -- *************************************** Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan(a)gmail.com *************************************** [View Less]

1 3

Re: [alsa-devel] OSS/4Front
by Ash Willis 21 Jun '07

21 Jun '07

Hi Clemens, > You could compare <http://manuals.opensound.com/devlists/Linux.html> > with ALSA's sound card matrix, but the latter tends to be out of date. > Yeah, that thing is oooooold. Hopefully the new wiki on't be too bad. > > With the recent open sourcing of OSS, it would be nice to port code > > to ALSA for devices that are only currently covered by OSS. > > AFAICS all devices supported by the open-source OSS are also supported > by ALSA. > … [View More]

1 0

[alsa-devel] OSS/4Front
by Ash Willis 21 Jun '07

21 Jun '07

Hi, Does anyone know if there's any kind of list showing a comparison of hardware support between ALSA and OSS/4Front? With the recent open sourcing of OSS, it would be nice to port code to ALSA for devices that are only currently covered by OSS. There has to be at least a few devices that we can grab support for, right? It may at least provide us with insight into a few bugfixes. Ash -- Get a Free E-mail Account at Mail.com! Choose From 100+ Personalized Domains Visit http://www.mail.com today

4 3

[alsa-devel] Yamaha Cards
by derek＠darlingsong.net 21 Jun '07

21 Jun '07

Hi all, first post for me. I have a Yamaha DS2416 mixer card and Yamaha SW1000XG sound card that I would like to use onLinux (Fedora 6). I have used them on the "other" OS, along with ProTools, etc. Does anyone know if Linux drivers are available? I have looked around, and it seems not to be the case. any help would bve appreciated. Derekd Vancouver, BC

2 1

[alsa-devel] No time for cs4624
by chris＠idlelion.net 21 Jun '07

21 Jun '07

I really wanted to work on the cs4624 suspend resume bug (#305), but there is no time, especially given the lack of technical information. I'm wondering if I were to lend or give a laptop that exhibits the problem to one of you alsa developers, if that would be useful and provide some impetus to fix the bug, or if it would just be a big pain? Opinions? Chris

1 0

[alsa-devel] [1/2] 2.6.22-rc5: known regressions
by Michal Piotrowski 21 Jun '07

21 Jun '07

Hi all, Here is a list of some known regressions in 2.6.22-rc5. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions Unclassified Subject : Kernel hang on CMOS_READ References : http://lkml.org/lkml/2007/6/3/138 Submitter : Rodrigo Luiz <troops.of.doom(a)gmail.com> Status : Unknown Subject : Device hang when offlining a CPU due to IRQ misrouting References : http://lkml.org/lkml/2007/5/31/419 Submitter : Darrick J. Wong <… [View More]

3 5

Re: [alsa-devel] Using aplay and arecord on an ARM
by Paul Kavan 20 Jun '07

20 Jun '07

On 6/20/07, Paul Kavan <pkavan(a)gmail.com> wrote: > > Okay: > > Here is where I ran into troubles yesterday. I am working on configuring > alsa-utils. When I do: > > CC=arm-linux-gcc ./configure --target=arm-linux --with-versioned=no > --prefix=/usr --host=i686-pc-linux-gnu > > I get the error: > > grhuser@pcL7:$ CC=arm-linux-gcc ./configure --target=arm-linux > --with-versioned=no --prefix=/usr --host=i686-pc-linux-gnu > configure: WARNING: If … [View More]you wanted to set the --build type, don't use > --host. > If a cross compiler is detected then cross compile mode will be used. > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking for i686-pc-linux-gnu-strip... no > checking for strip... strip > checking whether NLS is requested... yes > checking for msgfmt... /usr/bin/msgfmt > checking for gmsgfmt... /usr/bin/msgfmt > checking for xgettext... /usr/bin/xgettext > checking for msgmerge... /usr/bin/msgmerge > checking for style of include used by make... GNU > checking for i686-pc-linux-gnu-gcc... arm-linux-gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... yes > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether arm-linux-gcc accepts -g... yes > checking for arm-linux-gcc option to accept ISO C89... none needed > checking dependency style of arm-linux-gcc... gcc3 > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for ld used by GCC... > /home/grhuser/Linux_Builds/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld > checking if the linker > (/home/grhuser/Linux_Builds/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld) > is GNU ld... yes > checking for shared library run path origin... done > checking for CFPreferencesCopyAppValue... no > checking for CFLocaleCopyCurrent... no > checking for GNU gettext in libc... no > checking for iconv... no, consider installing GNU libiconv > checking for GNU gettext in libintl... no > checking whether to use NLS... no > checking for i686-pc-linux-gnu-gcc... (cached) arm-linux-gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether arm-linux-gcc accepts -g... (cached) yes > checking for arm-linux-gcc option to accept ISO C89... (cached) none > needed > checking dependency style of arm-linux-gcc... (cached) gcc3 > checking for a BSD-compatible install... /usr/bin/install -c > checking whether ln -s works... yes > checking for ALSA CFLAGS... > checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread > checking for libasound headers version >= 1.0.12... not present. > configure: error: Sufficiently new version of libasound not found. > > I know there has to be a flag or something here I need to set. Does anyone > know what that might be? > > Paul > I think what occurs here is that the configure script is using my cross-compilers and associated libs in $HOME/Linux_Builds/buildroot/build_arm/staging_dir/ while the libs are actually given in $HOME/Linux_Builds/buildroot/build_arm/root/usr/lib/ I am looking at the README and INSTALL and do not see a solution to this. Does anyone have a solution to this? Thanks. Paul [View Less]

4 11

[alsa-devel] Kernel 2.6.21 M-Audio Delta 1010L
by Suso Comesaña 20 Jun '07

20 Jun '07

Hello... My name is Suso Comesaña...I have 2 computers with a M-Audio card Delta 1010L...the problem is the following one: With kernel 2.6.17-2-multimedia-486... I can record sounds perfectly... but, kernel 2.6.21... I cannot record nothing... You have some idea?... You need that she sends some information to you? Tanks... Suso Comesaña. Peatón. susobaco(a)yahoo.es Usuario de Musix, GNU-Linux, basada en Debian/Knoppix. 100% Software Libre. ¡Descubre una nueva … [View More]

2 1

[alsa-devel] Output levels on SBLive! 5.1 on ALSA vs WIndows
by ChernYue Kwok 20 Jun '07

20 Jun '07

Hello, I am using an SBLive! 5.1 sound card (emu10k1 chipset) with 6 channel output. Due to the nature of my work, I need to be able to play sound through all 6 channels at the same output level to an amplifier. Using Linux and the emu10k1 ALSA driver, I measured output voltage levels on an oscilloscope while playing a sine wave on all 6 channels, and I got three different output voltage amplitudes for the front, rear and center/subwoofer channels. Repeating the same test with the same … [View More]

2 3

[alsa-devel] Using aplay and arecord on an ARM
by Paul Kavan 20 Jun '07

20 Jun '07

Liam: I have managed to get the alsa-libs and aplay, arecord, and speaker-test on my board, but I am unsure how to get them to play. I have tried making the device nodes and am using a simple alsa.conf, but still no joy. I am sure there is something simple I am missing. Trying to find some documentation on this. I am assuming there is some disconnect between the interface and my conf file. I have my alsa.conf file in /usr/share/alsa/ and it is: pcm.!default { type hw card 0 } pcm.hw { … [View More] type hw card 0 device 0 subdevice 0 } ctl.!default { type hw card 0 } ctl.hw { type hw card 0 } ctl.w6811 { type hw card 0 } pcm.w6811 { type hw card 0 device 0 subdevice 0 } ctl.!default = ctl.w6811 pcm.!default = pcm.w6811 ctl.hw { @args[ CARD ] @args.CARD { type string default "0" } type hw card $CARD } pcm.hw { @args[ CARD DEV SUBDEV ] @args.CARD { type string default "0" } @args.DEV { type integer default 0 } @args.SUBDEV { type integer default 0 } type hw card $CARD device $DEV subdevice $SUBDEV } I have some /proc/ entries: /proc/asound $ ls GRHEKW6811 cards pcm version card0 devices timers /proc/asound $ cat cards 0 [GRHEKW6811 ]: W6811 - GRH_EK_W6811 GRH_EK_W6811 (W6811) /proc/asound $ cat devices 0: [ 0] : control 16: [ 0- 0]: digital audio playback 24: [ 0- 0]: digital audio capture 33: : timer /proc/asound $ cat pcm 00-00: W6811 W6811-PCM-0 : : playback 1 : capture 1 /proc/asound $ cat timers G0: system timer : 10000.000us (10000000 ticks) P0-0-0: PCM playback 0-0-0 : SLAVE P0-0-1: PCM capture 0-0-1 : SLAVE /proc/asound $ cat version Advanced Linux Sound Architecture Driver Version 1.0.14rc4 (Wed May 09 09:51:39. Now, into GRHEKW6811 (which takes me to card0) I get a pcm0c and pcm0p directory. Using cat info, I get: /proc/asound/card0/pcm0c $ cat info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: W6811 W6811-PCM-0 name: subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 /proc/asound/card0/pcm0c $ cd ../pcm0p/ /proc/asound/card0/pcm0p $ cat info card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: W6811 W6811-PCM-0 name: subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 I then did: mknod -m 666 /dev/snd/pcm0p c 116 0 mknod -m 666 /dev/snd/pcm0c c 116 0 However, when I try speaker-test, I get: /usr/lib/bin $ ./speaker-test -D pcm0p speaker-test 1.0.14 Playback device is pcm0p Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM pcm0p Playback open error: -2,No such file or directory Same for default: /usr/lib/bin $ ./speaker-test -D default speaker-test 1.0.14 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM default Playback open error: -2,No such file or directory When I try aplay -l and arecord -l, I get: /usr/lib/bin $ ./aplay -l aplay: device_list:204: no soundcards found... /usr/lib/bin $ ./arecord -l arecord: device_list:204: no soundcards found... I am at a loss here. Anyone have any advice, pointers, tips, etc...... Thanks. Paul -- *************************************** Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan(a)gmail.com *************************************** [View Less]

4 9

[alsa-devel] ALSA always writes _whole_ periods, right?
by Joachim Förster 20 Jun '07

20 Jun '07

Hi ALSA devs, I have a quick question regarding the filling of the usual ring buffer in RAM (used by sound controllers via DMA), just to be really sure: Is it true, that ALSA always writes (via mmap'ing) _whole_ periods? I took snd-dummy and modified it to use "ack()" method and tried to confirm, if the above is true _without_ memory mapping (classical read/write). It seem's to be true, ALSA is "filling up" the last (not always complete) period - e.g. if the played wav file is not a multiple … [View More]

2 3

[alsa-devel] Surround problems with cs46xx
by Vasilis Manwlopoulos 20 Jun '07

20 Jun '07

Hi, Sorry for bothering the list again, but I have major problems with the surround 5.1 sound. I have manually compiled/installed th latest alsa-1.0.14 drivers but nothing improved. I am using Ubuntu 7.04 and my soundcard is the Hercules Fortissimo III. This is, as far as I know by reading on Internet, supported by the module snd-cs46xx in ALSA. I have enabled the surround sound by creating the following .asoundrc file. pcm.!default { type plug slave.pcm "surround51" slave.… [View More]

3 3

[alsa-devel] Kernel 2.6.21 M-Audio Delta 1010L
by Suso Comesaña 20 Jun '07

20 Jun '07

Hello... My name is Suso Comesaña...I have 2 computers with a M-Audio card Delta 1010L...the problem is the following one: With kernel 2.6.17-2-multimedia-486... I can record sounds perfectly... but, kernel 2.6.21... I cannot record nothing... You have some idea?... You need that she sends some information to you? Tanks... Suso Comesaña. Peatón. susobaco(a)yahoo.es Usuario de Musix, GNU-Linux, basada en Debian/Knoppix. 100% Software Libre. ¡Descubre una nueva … [View More]

1 0

[alsa-devel] [PATCH] Output MFG information for HDA devices
by Jonathan Phénix 19 Jun '07

19 Jun '07

Hi, this patch output information about the MFG (Modem Function Group) to the /proc/asound/card?/codec#? file. This information is important to identify if a HDA device has a modem or not. Regards, Jonathan Phénix Technical specialist / Linuxant www.linuxant.com jonathan(a)linuxant.com

2 3

Re: [alsa-devel] Writing an AT91SAM9260-EK Dumb Codec Driver
by Paul Kavan 19 Jun '07

19 Jun '07

On 6/19/07, Liam Girdwood <lg(a)opensource.wolfsonmicro.com> wrote: > > On Mon, 2007-06-18 at 14:30 -0500, Paul Kavan wrote: > > > > > Am I at a point now where I can try to get alsa-lib and alsa-util in > > place? If so, what version? I found some tars at: > > > > http://www.alsa-project.org/alsa/ftp/lib/ > > > > Is that the best place to get them? I am using buildroot, but not sure > > if ALSA stuff is ready for primetime there. I … [View More]guess I should check on > > this asap. > > > > Afaik, there is an issue with buildroot atm (please someone correct me > if it's now fixed) when it comes to building alsa-lib for ARM. (please > search archives for details). No, I think you are right. I have tried a few recommended patches, but they do not work. Fwiw, I use openembedded for all my embedded builds without any problems > atm. http://www.openembedded.org At some point when I have some time, I am going to give it a try. I have managed to build the libs and have those in my rfs using: CC=arm-linux-gcc ./configure --host=arm-linux --prefix=$HOME/buildroot/build_arm/root/usr --with-versioned=no ...and then... make install With this, I get the /usr/ entries in my rfs. However, I have had troubles building alsa-utils. When I try: CC=arm-linux-gcc ./configure --host=arm-linux --prefix=$HOME/buildroot/build_arm/root/usr --with-versioned=no I get: grhuser@pcL7:$ CC=arm-linux-gcc ./configure --host=arm-linux --prefix=$HOME/buildroot/build_arm/root/usr --with-versioned=no configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for arm-linux-strip... arm-linux-strip checking whether NLS is requested... yes checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for style of include used by make... GNU checking for arm-linux-gcc... arm-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-linux-gcc accepts -g... yes checking for arm-linux-gcc option to accept ISO C89... none needed checking dependency style of arm-linux-gcc... gcc3 checking build system type... i686-pc-linux-gnu checking host system type... arm-unknown-linux-gnu checking for ld used by GCC... /home/grhuser/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld checking if the linker (/home/grhuser/buildroot/build_arm/staging_dir/arm-linux-uclibc/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking for GNU gettext in libc... no checking for iconv... no, consider installing GNU libiconv checking for GNU gettext in libintl... no checking whether to use NLS... no checking for arm-linux-gcc... (cached) arm-linux-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether arm-linux-gcc accepts -g... (cached) yes checking for arm-linux-gcc option to accept ISO C89... (cached) none needed checking dependency style of arm-linux-gcc... (cached) gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for ALSA CFLAGS... checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread checking for libasound headers version >= 1.0.12... not present. configure: error: Sufficiently new version of libasound not found. Not sure what is the problem here. I have file:///home/grhuser/buildroot/build_arm/root/usr/lib/libasound.so.2.0.0 in my rfs. Any suggestions? Paul Liam > > -- *************************************** Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan(a)gmail.com *************************************** [View Less]

2 1

[alsa-devel] [PATCH] hda: add eapd support to additional idt codecs
by Matthew Ranostay 19 Jun '07

19 Jun '07

Added support for EAPD on the 927x, and 9227-8 IDT HDA codecs. Enabling EAPD powers the internal speaker amp otherwise there is no sound on systems with an internal amp. --- Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> diff -r 96495fe7cc13 pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Thu Jun 14 12:58:23 2007 +0200 +++ b/pci/hda/patch_sigmatel.c Mon Jun 18 17:10:38 2007 -0400 @@ -832,6 +832,18 @@ static void stac92xx_set_config_regs(str } } +static void … [View More]

2 1

[alsa-devel] Is snd_magic_kcalloc() deprecated?
by Pharaoh . 19 Jun '07

19 Jun '07

2 1