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

[alsa-devel] HG vs GIT
by Jaroslav Kysela 11 Feb '08

11 Feb '08

Hi, it seems that GIT matured somewhat. git-push has been implemneted. It was main reason to not use GIT when we made decision between HG and GIT. As we could have potential problems with branches in HG repository, I would like to consider a switch to GIT althought it means some changes in my scripts on ALSA server and my ksync tool. I just successfully tried (a bit modified hg-to-git.py script) and it seems to be working properly. Any objections? Jaroslav ----- Jaroslav Kysela <perex(a)perex.cz> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.

11 34

[alsa-devel] Some questions about devices supported by alsa
by Sergio Atzori 11 Feb '08

11 Feb '08

Hello, my name is Sergio Atzori. I'm a musician and I love very much linux and open source. I have a lot of hardware for music, something well supported by linux, something else not supported...I have some questions: 1) Esi Juli@: reported as supported by alsa, but it isn't. Looking at http://www.linuxdriverproject.org/twiki/bin/view/Main/DriversNeeded and http://alsa.opensrc.org/index.php/Ice1724, this really beautiful card is unusable in linux. I have one and I tried to get it working with some distros, but nothing..I experience a computer freeze (kernel panic perhaps?) in every attempt to configure it with alsa-conf, or just opening an application that uses midi system (like Rosegarden). So I would know, there is someone working on a better driver? Can I hope to get it working in the near future? According to me there is a lot of people waiting for a driver for this card, I'm waiting since 2005.. 2) Miditech I2 control-37 (http://www.miditech.de/produktee_i2.htm): beatiful usb-keyboard, not mentioned in Linux-USB device site, it does not work in linux...I think the kernel configure it well (as snd-usb-audio device) but I can't see it in Jack midi connections.. 3) RME AES32 (and AES32express) & Lynx AES16: this driver could be important for professional studios..if we want to put linux distros on the professional side. I've none of them, but some people ask me to build a professional multichannel live machine, I'd like to build a linux based machine...there are not alternatives to these cards, because I can build a system with more than one of them (really powerful multichannel environment). Thanks so much for attention. Ciao

4 4

[alsa-devel] external PCM plugin, can't read hw params
by Ben C 11 Feb '08

11 Feb '08

Hi, This is during the init call-back of an external PCM plugin. I'm trying to read the period size. The code is pretty basic, it looks like this: --------------- snd_pcm_hw_params_alloca(&hw); status = snd_pcm_hw_params_any(ext->pcm, hw); if (status < 0) { // some error handling } status = snd_pcm_hw_params_get_period_size(hw, size, NULL); if (status < 0) { // some error handling } -------------- I get size = 0 back, an no errors either. Other information that I needed, such as the rate & format are available in the ext structure, but not the period size. So I query the hw params of ext->pcm. Please let me know if I should be getting this information using a different way. alsa-lib version is 1.0.14a I've done something similar for alsa-lib verion 1.0.13 (I used snd_pcm_hw_params_current() call) which worked. This is based on that same code but for a different target. Thank you, Ben ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

1 0

[alsa-devel] support for jackSense feature in modern sound cards
by Balaji Rao 10 Feb '08

10 Feb '08

Hello people, How well is the jack sense feature in modern soundcards supported in the kernel ? I opened up a few driver sources like hda-intel and found the word 'jack sense' in some files, but i could not find it being used anywhere. Are there standard interfaces in kmix or equivalent software that use the jack sense feature ? If not, wouldn't it be nice to have a standard interface to expose this feature so that kmix and others could make use of in a device independent way ? If yes, I would be more than willing to contribute to its development. Please clarify. -- regards, balaji rao

3 2

[alsa-devel] alsa-info.sh debugging script
by Travis Place 09 Feb '08

09 Feb '08

Hi everyone, I am new to this list, so be nice please :P I am the author of the alsa-info.sh debugging script, and heard you may want to use it within ALSA.. I have been speaking to Tobin, and he mentioned that a few things may need to be added (like alsactl output). I just want to get some ideas of things i can add, and if they should be included automatically, or require a --with-alsactl (for example). I have added the alsactl output to the script now, its included by default.. Any other ideas/changes that need to be made ? Travis Place (wishie) -- Happiness is like peeing your pants. Everyone can see it, but only you can feel its warmth

3 6

[alsa-devel] snd-dummy and snd_pcm_new()
by William Juul 08 Feb '08

08 Feb '08

I am using snd-dummy on a NGW100 card with buildroot provided by Atmel. The alsa version is 1.0.14a and the kernel is 2.6.23. I have compiled three versions of the snd-dummy driver: the original, one with capture_count=0 and one with playback_count=0. When I use snd_pcm_new() with playback_count=0, there will be no PCM devices other than the "null" (see below). Is this expected? Can I still capture from this driver (and a real driver with the same symptoms)? Best regards William Juul Listings (annotated): (with original snd-dummy and modified snd-dummy to use capture_count=0) # modprobe snd-dummy # # arecord -l **** List of CAPTURE Hardware Devices **** card 0: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 # # arecord -L default:CARD=Dummy Dummy, Dummy PCM Default Audio Device null Discard all samples (playback) or generate zero samples (capture) # reboot .. (with modified snd-dummy to use playback_count=0) # modprobe snd-dummy # arecord -l **** List of CAPTURE Hardware Devices **** card 0: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 # arecord -L null Discard all samples (playback) or generate zero samples (capture) #

1 0

[alsa-devel] PATCH: remove duplicate controls in alc268 test mixer
by Jonathan Woithe 08 Feb '08

08 Feb '08

Hi guys I've just noticed that there are a handful of duplicate controls in the ALC268 test model mixer. This patch (against alsa-driver 1.0.16) removes them. Signed-off-by: Jonathan Woithe <jwoithe(a)physics.adelaide.edu.au> --- patch_realtek.c-orig 2008-02-05 19:53:24.000000000 +1030 +++ patch_realtek.c 2008-02-08 09:23:02.000000000 +1030 @@ -9834,11 +9834,6 @@ #ifdef CONFIG_SND_DEBUG static struct snd_kcontrol_new alc268_test_mixer[] = { - HDA_CODEC_VOLUME("Front Playback Volume", 0x2, 0x0, HDA_OUTPUT), - HDA_CODEC_MUTE("Front Playback Switch", 0x14, 0x0, HDA_OUTPUT), - HDA_CODEC_VOLUME("Headphone Playback Volume", 0x3, 0x0, HDA_OUTPUT), - HDA_CODEC_MUTE("Headphone Playback Switch", 0x15, 0x0, HDA_OUTPUT), - /* Volume widgets */ HDA_CODEC_VOLUME("LOUT1 Playback Volume", 0x02, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME("LOUT2 Playback Volume", 0x03, 0x0, HDA_OUTPUT),

2 1

[alsa-devel] [PATCH] Fix race condition in generic bound volume/swtich controls
by Serge A. Suchkov 08 Feb '08

08 Feb '08

Hi all, Attached patch fix race condition in hd_codec generic bound volume/swtich controls oops on this bug can be easy reproduced by two mixer apps on SMP system with PREEMPT kernel dmesg: ALSA /home/ss/ALSA/alsa-driver-1.0.16/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:596: hda_intel: azx_get_response timeout, switching to polling mode: las t cmd=0x014f0900 BUG: unable to handle kernel paging request at virtual address 00070006 printing eip: f8f43e95 *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP Modules linked in: i915 drm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss bnep rfcomm hidp l2cap bluetooth w lan_wep acpi_cpufreq coretemp hwmon mmc_block pcspkr psmouse wlan_scan_sta ath_rate_sample snd_hda_intel ath_pci serio_raw wlan tg3 sdhci snd_pcm firewire_o hci mmc_core i2c_i801 snd_timer firewire_core snd_page_alloc ath_hal(P) snd_hwdep snd iTCO_wdt crc_itu_t iTCO_vendor_support shpchp video output acer_acpi b acklight led_class wmi_acer Pid: 3969, comm: gkrellm Tainted: P (2.6.24-jm #4) EIP: 0060:[<f8f43e95>] EFLAGS: 00010292 CPU: 0 EIP is at snd_hda_mixer_bind_ctls_info+0x20/0x43 [snd_hda_intel] EAX: 00000000 EBX: f7478e00 ECX: f763e000 EDX: f764f788 ESI: 00070002 EDI: edce5e00 EBP: edc3fe64 ESP: edc3fe54 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process gkrellm (pid: 3969, ti=edc3e000 task=f1e4e000 task.ti=edc3e000) Stack: f764f77c f7478e00 edce5e00 f6dd6000 edc3fe84 f8e590e8 edc7a239 f6d14034 f764f34c f6c0f7e0 edc3ff30 f6d14034 edc3fea8 f8e591b7 edc3ff30 edc3ff2c 00000000 f70aa668 f6d14034 f8e59165 bfbfadb0 edc3ff40 f8e587aa edc3ff2c Call Trace: [<c0104fbb>] show_trace_log_lvl+0x1a/0x2f [<c010506d>] show_stack_log_lvl+0x9d/0xa5 [<c0105119>] show_registers+0xa4/0x1bd [<c0105354>] die+0x122/0x206 [<c03daccc>] do_page_fault+0x535/0x623 [<c03d940a>] error_code+0x72/0x78 [<f8e590e8>] snd_mixer_oss_get_volume1_vol+0x74/0xf1 [snd_mixer_oss] [<f8e591b7>] snd_mixer_oss_get_volume1+0x52/0xa5 [snd_mixer_oss] [<f8e587aa>] snd_mixer_oss_ioctl1+0x673/0x71e [snd_mixer_oss] [<f8e588af>] snd_mixer_oss_ioctl+0xb/0xd [snd_mixer_oss] [<c017af0a>] do_ioctl+0x22/0x67 [<c017b186>] vfs_ioctl+0x237/0x24a [<c017b1ca>] sys_ioctl+0x31/0x4b [<c010402e>] syscall_call+0x7/0xb ======================= Code: 3f 49 c7 89 f8 59 5b 5e 5f 5d c3 55 89 e5 57 89 d7 56 53 89 c3 83 ec 04 8b 70 5c 8b 40 60 05 7c 01 00 00 89 45 f0 e8 c0 3f 49 c7 <8b> 46 04 89 fa 89 4 3 5c 89 d8 8b 0e ff 11 89 73 5c 89 c7 8b 45 EIP: [<f8f43e95>] snd_hda_mixer_bind_ctls_info+0x20/0x43 [snd_hda_intel] SS:ESP 0068:edc3fe54 ---[ end trace 0a20bc209e9397cc ]--- similar issue report present in ALSA bugtracking system https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3652 -- Regards, Serge A. Suchkov -- Democracy is a form of government that substitutes election by the incompetent many for appointment by the corrupt few. -- G. B. Shaw

2 1

Re: [alsa-devel] 1.0.16rc2 -build issues
by Alan Horstmann 08 Feb '08

08 Feb '08

Hi Takashi, I tried out yesterdays tarball hg20080207 to confirm DSP2000 Midi stuff before pointing another DSP2000 user to it. Build proceeded OK but I did notice the following warnings, which I might have missed previously, or they could be new. Do you care about redefinitions? pcm_oss.c:639:1: warning: "AFMT_S32_LE" redefined In file included from pcm_oss.c:43: /lib/modules/2.4.21-99-athlon/build/include/linux/soundcard.h:562:1: warning: this is the location of the previous definition pcm_oss.c:640:1: warning: "AFMT_S32_BE" redefined /lib/modules/2.4.21-99-athlon/build/include/linux/soundcard.h:563:1: warning: this is the location of the previous definition pcm_oss.c:641:1: warning: "AFMT_S24_LE" redefined /lib/modules/2.4.21-99-athlon/build/include/linux/soundcard.h:558:1: warning: this is the location of the previous definition pcm_oss.c:642:1: warning: "AFMT_S24_BE" redefined /lib/modules/2.4.21-99-athlon/build/include/linux/soundcard.h:559:1: warning: this is the location of the previous definition Regards Alan

2 1

[alsa-devel] new driver - some initial problems
by William Juul 08 Feb '08

08 Feb '08

I am new to alsa development, but I am trying to write a alsa capture driver for a DAC. The driver is based on at73c213 since it will be running on AVR32 and using the SSC bus. The driver is running on a NGW100 card and I am using buildroot provided by Atmel. The alsa version is 1.0.14a and the kernel is 2.6.23. The DAC is not using any configuration bus so I have switched to using platform_* functions instead of dev/spi (grabbed from snd-dummy). I have also been taking some capture pieces from the snd-dummy driver. I am now stuck with two problems: 1) When using arecord -L, I only get the "null" device 2) When I try to use arecord to do a recording I get "arecord: set_params:1039: unable to install sw params:". I get the same message when trying to use the snd-dummy driver, even though this driver also has PCM device. Any hints on how to proceed? I can post the driver source if that is interesting. Best regards William Juul Listings (annotated): # modprobe -v snd-dummy Loading module snd-page-alloc Loading module soundcore Loading module snd Loading module snd-timer Loading module snd-pcm Loading module snd-dummy # # # arecord -l **** List of CAPTURE Hardware Devices **** card 0: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 # # arecord -L default:CARD=Dummy Dummy, Dummy PCM Default Audio Device null Discard all samples (playback) or generate zero samples (capture) # # # # arecord > dummy.wav Recording WAVE 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono pcm->setup: 1 stream : CAPTURE access : RW_INTERLEAVED format : U8 subformat : STD channels : 1 rate : 8000 exact rate : 8000 (8000/1) msbits : 8 buffer_size : 355 period_size : 355 period_time : 44375 tick_time : 4000 tstamp_mode : NONE period_step : 1 sleep_min : 0 avail_min : 355 xfer_align : 355 start_threshold : 1 stop_threshold : 355 silence_threshold: 0 silence_size : 0 boundary : 1488977920 arecord: set_params:1039: unable to install sw params: start_mode: DATA xrun_mode: STOP tstamp_mode: NONE period_step: 1 sleep_min: 0 avail_min: 0 xfer_align: 0 silence_threshold: 0 silence_size: 0 boundary: 1488977920 # # # arecord -r 22786 -c 1 -f U8 -s 1 -A 100 -v > dummy.wav # (This works OK) # # reboot ... # # # modprobe -v snd-ads127x Loading module soundcore Loading module snd Loading module snd-page-alloc Loading module snd-timer Loading module snd-pcm Loading module snd-ads127x snd_ads127x_probe OK # # # arecord -l **** List of CAPTURE Hardware Devices **** card 0: ads127x_0 [AVR32 NGW100 external DAC], device 0: ads127x [ads127x] Subdevices: 1/1 Subdevice #0: subdevice #0 # arecord -L null Discard all samples (playback) or generate zero samples (capture) # # # # # arecord -r 22786 -c 1 -f S24_LE -s 1 -A 100 > ads127x.wav ALSA /home/williaj/src/ads127x/src/ads127x.c:141: snd_ads127x_pcm_open Recording WAVE 'stdin' : Signed 24 bit Little Endian, Rate 22786 Hz, Mono pcm->setup: 1 stream : CAPTURE accessALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 : RW_INTERLEAVED format : S24_LEALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 subformat : STD channels : 1 raALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 te : 22786 exact rate : 22786 (22786/1) msbits : 32 buffer_size : 4044 period_size : 1011 period_time : 44369 tick_time ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 : 4000 tstamp_mode : NONE period_step ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 : 1 sleep_min : 0 ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 xfer_align : 1011 start_threshold : 1 ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 stop_threshold : 4044 silence_threshold: ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 0 silence_size : 0 boundary : 21202206ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 72 overrun!!! (at least 1.074 ms long) overrun!!! (at least 0.151 ms long) overrun!!! (at least 0.139 ms long) overrun!!! (at least 0.141 ms long) overrALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 un!!! (at least 0.142 ms long) overrun!!! (at lALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 east 0.139 ms long) overrun!!! (at least 0.137 ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 ms long) overrun!!! (at least 0.139 ms long) oALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 verrun!!! (at least 0.138 ms long) overrun!!! (ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 at least 0.149 ms long) overrun!!! (at least 0.ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 145 ms long) overrun!!! (at least 0.154 ms long) overrun!!! (at least 0.146 ms long) overrun!!! (at least 0.146 ms long) overrun!!! (at least 0.724 ms loALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 ng) overrun!!! (at least 0.152 ms long) ALSA sound/core/pcm_lib.c:155: BUG: stream = 1, pos = 0x3b5f034, buffer size = 0xfcc, period size = 0x3f3 overrun!!! (at least 0.125 ms long)

1 0