July 2008 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] cross compile errors
by SunZhibin 21 Jul '08

21 Jul '08

Hello, I want to cross compile alsa-driver for my arm9 custom board , when I build it, I get the following errors: CC [M] /home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.oIn file included from /home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:25:/home/zb/alsa/alsa-driver-1.0.17/include/adriver.h:828: error: static declaration of 'jiffies_to_msecs' follows non-static declarationinclude/linux/jiffies.h:264: error: previous declaration of 'jiffies_to_msecs' was here/home/zb/alsa/alsa-driver-1.0.17/include/adriver.h:847: error: static declaration of 'msecs_to_jiffies' follows non-static declarationinclude/linux/jiffies.h:266: error: previous declaration of 'msecs_to_jiffies' was hereIn file included from /home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:25:/home/zb/alsa/alsa-driver-1.0.17/include/adriver.h:1552:1: warning: "page_to_pfn" redefinedIn file included from include/asm/memory.h:329, from include/asm/system.h:6, from include/linux/list.h:9, from include/linux/module.h:9, from /home/zb/alsa/alsa-driver-1.0.17/include/adriver.h:26, from /home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:25:include/asm-generic/memory_model.h:79:1: warning: this is the location of the previous definitionIn file included from /home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:26:include/linux/mm.h: In function 'lowmem_page_address':include/linux/mm.h:538: error: implicit declaration of function 'page_to_pfn'/home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c: In function 'snd_compat_vmalloc_to_page':/home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:44: error: implicit declaration of function 'VMALLOC_VMADDR'/home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:50: error: implicit declaration of function 'pte_offset'/home/zb/alsa/alsa-driver-1.0.17/acore/memory_wrapper.c:50: warning: assignment makes pointer from integer without a cast I use the following configure options: export $PREFIX=/opt/alsaexport ARCH=armexport CROSS_COMPILE=/opt/arm-linux/bin/arm-linux- ./configure --prefix=$PREFIX --host=arm-linux --enable-shared --enable-static \ --with-cross=$CROSS_COMPILE \ --with-kernel=/home/zb/embedded/linux-2.6.24.7 \ --with-debug=verbose \ --with-isapnp=no \ --with-cards=s3c2410,soc,s3c24xx-soc,s3c24xx-soc-neo1973-wm8753,s3c24xx-soc-smdk2443-wm9710,s3c24xx-soc-ln2440sbc-alc650 how can is solve this problem ? Thanks _________________________________________________________________ 这里好多好玩的视频，用鼠标点到视频看看，有惊喜！ http://cnweb.search.live.com/video/results.aspx?q=%E5%A5%A5%E8%BF%90%E5%9C%…

1 0

[alsa-devel] ASOC and 12 bit volume control
by Jon Smirl 21 Jul '08

21 Jul '08

How do I define a volume control that is the bottom 12 bits of a 32 bit register? #define SOC_SINGLE_VALUE(reg, shift, max, invert) ((reg) | ((shift) << 8) |\ ((shift) << 12) | ((max) << 16) | ((invert) << 24)) This looks like it only support an 8 bit max. Is there another way to do it? -- Jon Smirl jonsmirl(a)gmail.com

2 8

[alsa-devel] 1.0.17
by Elimar Riesebieter 20 Jul '08

20 Jul '08

For the first step alsa-lib is upgraded in svn. I am very busy at the moment and will see what I can do nest week. My goal: Upload latest in week 31. Elimar -- Numeric stability is probably not all that important when you're guessing;-)

1 1

[alsa-devel] [PATCH] wss: fix capture formats limitations
by Krzysztof Helt 20 Jul '08

20 Jul '08

From: Krzysztof Helt <krzysztof.h1(a)wp.pl> Fix copy-paste error with Interwave instead of ad1848 chip condition. Limit opti93x cards capture formats to only linear ones. Signed-off-by: Krzysztof Helt <krzysztof.h1(a)wp.pl> --- Thank you Rene for collecting, testing and reviewing my patches. I found one mistake in the series and this patch fixes it. I have also limited capture formats for opti93x chips because the opti93x manual states that it supports mu-law, a-law and ADPCM decompression. The word "decompression" probably suggest that compression (recording) is not possible as its manufacturer could just state the card supported mu-law, a-law and ADPCM. Regards, Krzysztof diff -urp linux-alsa/sound/isa/wss/wss_lib.c linux-mm/sound/isa/wss/wss_lib.c --- linux-alsa/sound/isa/wss/wss_lib.c 2008-07-18 22:47:02.056943647 +0200 +++ linux-mm/sound/isa/wss/wss_lib.c 2008-07-18 22:56:38.200949874 +0200 @@ -1460,14 +1460,16 @@ static int snd_wss_capture_open(struct s runtime->hw = snd_wss_capture; /* hardware limitation of older chipsets */ - if (chip->hardware == WSS_HW_INTERWAVE && chip->dma1 > 3) + if (chip->hardware & WSS_HW_AD1848_MASK) runtime->hw.formats &= ~(SNDRV_PCM_FMTBIT_IMA_ADPCM | SNDRV_PCM_FMTBIT_S16_BE); /* hardware limitation of cheap chips */ if (chip->hardware == WSS_HW_CS4235 || - chip->hardware == WSS_HW_CS4239) - runtime->hw.formats = SNDRV_PCM_FMTBIT_U8 | SNDRV_PCM_FMTBIT_S16_LE; + chip->hardware == WSS_HW_CS4239 || + chip->hardware == WSS_HW_OPTI93X) + runtime->hw.formats = SNDRV_PCM_FMTBIT_U8 | + SNDRV_PCM_FMTBIT_S16_LE; snd_pcm_limit_isa_dma_size(chip->dma2, &runtime->hw.buffer_bytes_max); snd_pcm_limit_isa_dma_size(chip->dma2, &runtime->hw.period_bytes_max); ---------------------------------------------------------------------- W kosciele tez zdarzaja sie wpadki! Smieszny filmik >>> http://link.interia.pl/f1e61

2 2

[alsa-devel] [0/2] Jack reporting
by Mark Brown 20 Jul '08

20 Jul '08

This is a repost of the the jack reporting API I posted recently. There are no chances since the last submission - as discussed in that thread the existing users and the need to support buttons implemented in jacks pushes me towards use of an input device to represent jacks.

3 11

[alsa-devel] Repost: snd-hda-intel[ALC883] scratching and stuttering sound on MCP78S board
by Hans-Frieder Vogt 20 Jul '08

20 Jul '08

Hi List, This is just an updated repost of my request from a month ago. So far I have not achieved to solve the problem myselves, therefore I would very much appreciate ANY hint as to what (and even more important: where) to look for. Here is a summary of my problem and some related info: I am experiencing severely scratching and stuttering sound on my nVidia MCP78S (GeForce 8200) based Asus M3N78-EMH HDMI mainboard, which has an ALC883 on board, running with an Athlon X2 4850e dual-core CPU. It sounds, as if the sound buffers are not filled in time and are therefore repeated many times (2 to 4 times) per second. The problem seems to be kernel / alsa-driver related, because I experience the problem also when running runlevel 1 with only a minimum of active processes (e.g. without graphics). Strange enough, the sound is OK when I do a larger compilation in parallel (kernel make with make -j 2), but the sound is not OK when I run burnK7 (two instances to sufficiently load both CPU cores) => What is different in CPU loading or scheduling between these two load cases? Also, the sound is OK when I copy large files in parallel. Could it be related, that lspci gives me for all devices a latency of 0, even though the kernel message tell me that it was set to 64? I cannot change the PCI latency to another value via setpci. I am using Message Signal Interrupts for HD Audio, although switching it off also makes no audible difference. My Interrupt distribution is: CPU0 CPU1 0: 39 1 IO-APIC-edge timer 1: 61 27962 IO-APIC-edge i8042 6: 0 5 IO-APIC-edge floppy 7: 1 0 IO-APIC-edge 8: 0 1 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 20: 826 748020 IO-APIC-fasteoi nvidia 22: 0 3 IO-APIC-fasteoi ehci_hcd:usb2, ehci_hcd:usb4 23: 437 175388 IO-APIC-fasteoi ohci_hcd:usb1, ohci_hcd:usb3 314: 2891 1330645 PCI-MSI-edge eth1 315: 0 0 PCI-MSI-edge cx23885[0] 316: 258 115865 PCI-MSI-edge HDA Intel 317: 286 118802 PCI-MSI-edge ahci NMI: 0 0 Non-maskable interrupts LOC: 977113 1020994 Local timer interrupts RES: 327021 99771 Rescheduling interrupts CAL: 1408 972 function call interrupts TLB: 11275 4795 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts SPU: 0 0 Spurious interrupts ERR: 1 I tried several things so far: Debian kernel image 2.6.25-2-amd64 (2.6.25-5 and 2.6.25-7) Ubuntu 8.04 with kernel 2.6.24-16 self-compiled 2.6.25.x (with x in nothing to 5), with and without -rt patches self-compiled 2.6.26-rc5 to 2.6.26 final latest alsa-driver 1.0.17rc2, 1.0.17-rc3 and 1.0.17 alsa-library versions 1.0.16 and 1.0.17 all these versions give the similar distorted output. please find the alsa-info output here: http://pastebin.ca/1077615 (previously posted info: http://pastebin.ca/1052359 ) attached is my latest kernel setup (2.6.26, alsa driver modules now replaced by version 1.0.17). Please tell me your suggestions what the problem may be or how I could debug the problem. Thanks very much. -- -- Hans-Frieder Vogt e-mail: hfvogt <at> gmx .dot. net

1 0

[alsa-devel] [PATCH] wm9712 mono mixer
by Marek Vasut 20 Jul '08

20 Jul '08

Hi, this fixes typo in wm9712 codec which prevents it from registering all audio routes (and thus working correctly). Please consider applying. (Tested and works on palmtx, palmld and palmt5)

3 2

[alsa-devel] softvol and snd_pcm_rewind() is broken
by Lennart Poettering 20 Jul '08

20 Jul '08

Heya! With 1.0.17rc3 snd_pcm_rewind() is broken for softvol as it seems: - Sometimes the sound becomes heavily distorted after such a seek: http://mailman.alsa-project.org/pipermail/alsa-devel/2008-June/008860.html - And snd_pcm_rewind() might return a value that is higher than was passed in, which as far as I understood should never happen: http://mailman.alsa-project.org/pipermail/alsa-devel/2008-April/007308.html These two issues might be caused by the same error. Takashi, Jaroslav, how can I bribe you into fixing this? I'd love to release my new PulseAudio version soon which heavily relies on snd_pcm_rewind(), but unfortunately the most important driver (hda with softvol) makes the most problems with it. :-( Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4

3 7

[alsa-devel] No sound with ice_1724 when I restart the system since I upgrade to 2.6.26 (+workaround)
by Amaury De Ganseman 20 Jul '08

20 Jul '08

Hi all, I think it's better to send here ;-) Additional infos: Kernel 2.6.26 from kernel.org /proc/asound/cards: 0 [Juli ]: ICE1724 - ESI Juli@ ESI Juli@ at 0xb400, irq 18 + /var/lib/alsa/asound.state in attach (after stop alsasound, rm asound.state and then restart alsa --> so sound is working) ---------- Forwarded message ---------- From: Amaury De Ganseman <amaury.deganseman(a)gmail.com> Date: Tue, Jul 15, 2008 at 9:50 PM Subject: No sound when I restart the system since I upgrade to 2.6.26 (+workaround) To: alsa-user(a)lists.sourceforge.net Hi all, Here is the description and workaround to have sound. It's related to mixer..but I don't know why it saves wrong mixer settings. Thanks for help #I have this problem (no sound when I start the system) since I upgrade to kernel 2.6.26 (driver: ice1724) #rm asound.state helps but after stopping alsa #This is in /var/lib/alsa: localhost alsa # rm asound.state rm: remove regular file `asound.state'? y localhost alsa # /etc/init.d/alsasound restart * WARNING: you are stopping a boot service. * Stopping pulseaudio ... [ ok ] * Storing ALSA Mixer Levels ... [ ok ] * Killing processes using ALSA ... [ ok ] * Unloading ALSA modules ... [ ok ] * Loading ALSA modules ... * Could not detect custom ALSA settings. Loading all detected alsa drivers. * Loading: snd_ice1724 ... [ ok ] * Restoring Mixer Levels ... alsactl: set_control:1300: incompatible field type for control #1 alsactl: set_control:1300: incompatible field type for control #32 [ ok ] * Starting pulseaudio ... #No sound with amarok (I restart amarok) [ ok ] localhost alsa # /etc/init.d/alsasound stop * WARNING: you are stopping a boot service. * Stopping pulseaudio ... [ ok ] * Storing ALSA Mixer Levels ... [ ok ] * Killing processes using ALSA ... [ ok ] * Unloading ALSA modules ... [ ok ] localhost alsa # rm asound.state rm: remove regular file `asound.state'? y localhost alsa # /etc/init.d/alsasound start * Loading ALSA modules ... * Could not detect custom ALSA settings. Loading all detected alsa drivers. * Loading: snd_ice1724 ... [ ok ] * Restoring Mixer Levels ... * No mixer config in /var/lib/alsa/asound.state, you have to unmute your card! [ ok ] #So I raise up the level of PCM: localhost alsa # alsamixer localhost alsa # /etc/init.d/pulseaudio start * Starting pulseaudio ... [ ok ] localhost alsa # #Now I have sound....

1 0

[alsa-devel] Altec Lansing FX5051 USB Speakers
by Jeremy Nickurak 19 Jul '08

19 Jul '08

This didn't appear to make it through to the list when I tried a few days ago to send it, so I'll try again. --- It's been about 7 months since I last brought this up, and didn't really get any success at the time, so I thought I'd check and see if anybody has any insights again. About a year ago I posted my original request here for any suggestions in getting a set of USB speakers from Altec Lansing, model# FX5051, working with ALSA. They're a set of 5.1 speakers with a built in USB sound card. Sound does appear to work, but the mixer is locked at 100%. There is no analog manual mixer, and the digital control dial exhibits the same problem as alsamixer, so I have to find a way to adjust the usb device's mixer volume in order to make the speakers usable. The speakers work fine in Windows XP, without installing any drivers, so it would seem that this device is operating based on some standard. In windows, adjusting the mixer via the digital control dial, or via the windows mixer control both result in the LED display moving in sync to indicate the new volume setting. In alsa, adjusting the digital control dial doesn't appear to have any effect, other then waking the LED display from its low-light mode. Attempting to adjust volume from alsamixer likewise wakes the display from low-light mode, but also fails to significantly change the mixer setting. When I say significantly, I mean that the mixer flips between about 98% and 100%, when using the Up/Down keys (or PgUp or PgDown). End appears to drop the volume to 0%, but Home doesn't restore it. Pressing the device's 'Power' button also behaves strangely. I can turn the device off, but it is turned back on shortly afterward. No usb connect/disconnect events appear here, instead, the power button seems to function more like a mute. amixer -c 2 contents yields: atrus@kedri:~$ amixer -c 2 contents numid=3,iface=MIXER,name='Tone Control - Bass' ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0 : values=1 numid=4,iface=MIXER,name='Tone Control - Treble' ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0 : values=3 numid=1,iface=MIXER,name='PCM Playback Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on numid=2,iface=MIXER,name='PCM Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=49,step=0 : values=48,48 | dBscale-min=-49.00dB,step=1.00dB,mute=0 I'm attaching the contents of 'lsusb -v'. Any suggestions would be appreciated, and any requests for further information about this device will be accomodated ASAP. Thanks in advance. -- Jeremy Nickurak

1 1