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

Re: [alsa-devel] PROBLEM: snd-au8830: dead after software suspend
by Gert Robben 06 Aug '07

06 Aug '07

>>> Have you reported this to the ALSA people? >> No, I thought this might as well be something for PCI or PM people, and >> I expected some ALSA people are also reading this list. >> If not, where else should I report this exactly? > alsa-devel [...] the author of the driver Done (original message below). Thanks again :) Gert Robben wrote: > After a suspend-resume cycle (using Suspend2), my sound card doesn't > work anymore. It works again after reloading the module. > > dmesg, initial boot: >> Linux version 2.6.22-ck1 > ----8<---- >> PCI driver au8830 lacks driver specific resume support. > > dmesg, after resume, trying to use the card: >> vortex: ac97 codec stuck busy > > Thanks for any help! > > Gert Robben

3 4

[alsa-devel] a newbie overwhelmed with this API
by Adam Seychell 06 Aug '07

06 Aug '07

I'm writing simple audio application and I have successfully used the DirectSound API under Windows. Now I'm looking at porting to Linux using ALSA. I have tried reading the online ALSA API documentation, but it seems too early in development and insufficient compared what one can learn reading Microsoft's DirectX SDK documentation. Excuse my ignorance for a minute, but the API seems quite large compared to DirectSound and so I'm wondering if there is good reason why so many functions exists ? Was there an early design decision not to write ALSA in C++ ? I would like to help out with documentation but of course I thats impossible for someone who is a complete novice to the ALSA project. I know that writing good documentation takes a lot of hard work, especially for software developers who spend enough time on coding. Its an unfortunate paradox among all open source projects. Software developers who posses the knowledge can't readily communicate it to potential volunteer documentation writers in an open source environment. Adam

2 1

[alsa-devel] [PATCH] au88x0: mem leak fix in snd_vortex_create()
by Jesper Juhl 06 Aug '07

06 Aug '07

Hi, In sound/pci/au88x0/au88x0.c::snd_vortex_create() : The Coverity checker found that if we allocate storage for 'chip' but then leave via the regions_out: label, then we end up leaking the storage allocated for 'chip'. I believe simply freeing 'chip' before the "return err;" line is all we need to fix this, but please double-check me :) Signed-off-by: Jesper Juhl <jesper.juhl(a)gmail.com> --- diff --git a/sound/pci/au88x0/au88x0.c b/sound/pci/au88x0/au88x0.c index 5ec1b6f..f70286a 100644 --- a/sound/pci/au88x0/au88x0.c +++ b/sound/pci/au88x0/au88x0.c @@ -232,6 +232,7 @@ snd_vortex_create(struct snd_card *card, struct pci_dev *pci, vortex_t ** rchip) pci_disable_device(chip->pci_dev); //FIXME: this not the right place to unregister the gameport vortex_gameport_unregister(chip); + kfree(chip); return err; }

3 2

[alsa-devel] MPC5200 I2S driver for ASoC
by lokowich 05 Aug '07

05 Aug '07

I'm integrating a ALSA driver for an MPC5200 into the ASoC layer, similar to my successful effort for a PXA255 board. I'm modeling the DMA and ALSA interfaces per ac97mgt driver found in the Lite5200B BSP, rather than the BestComm API example in the 2.4 kernel. The speaker-test with 400Hz sine wave is working, but has a slight audible jitter. A wav file output using aplay produces white noise. Debugging shows I get two requests for buffer pointer per service of my transmit ISR (after the single call to snd_pcm_period_elapsed). I expect only one pointer request per interrupt. Could this be the noise problem? This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com

3 7

[alsa-devel] [PATCH][RESEND] au88x0: mem leak fix in snd_vortex_create()
by Jesper Juhl 04 Aug '07

04 Aug '07

(resend of patch previously submitted on 04-Aug-2007 02:09) Hi, In sound/pci/au88x0/au88x0.c::snd_vortex_create() : The Coverity checker found that if we allocate storage for 'chip' but then leave via the regions_out: label, then we end up leaking the storage allocated for 'chip'. I believe simply freeing 'chip' before the "return err;" line is all we need to fix this, but please double-check me :) Signed-off-by: Jesper Juhl <jesper.juhl(a)gmail.com> Acked-by: Rene Herman <rene.herman(a)gmail.com> --- diff --git a/sound/pci/au88x0/au88x0.c b/sound/pci/au88x0/au88x0.c index 5ec1b6f..f70286a 100644 --- a/sound/pci/au88x0/au88x0.c +++ b/sound/pci/au88x0/au88x0.c @@ -232,6 +232,7 @@ snd_vortex_create(struct snd_card *card, struct pci_dev *pci, vortex_t ** rchip) pci_disable_device(chip->pci_dev); //FIXME: this not the right place to unregister the gameport vortex_gameport_unregister(chip); + kfree(chip); return err; }

1 0

[alsa-devel] SALSA and aplay
by Alan Horstmann 04 Aug '07

04 Aug '07

Quick questions: 1. Does SALSA provide everything needed by aplay? 2. Is there a version or equivalent of aplay that is a function that can be called from other code rather than the command line? Otherwise I shall hack it so for the purpose of some testing only, but ask to avoid re-inventing (no doubt poorly) something that exists. BTW SALSA compiled great (thanks Takashi), but with the following warning (which I ignore apart from mentioning here):- In file included from hcontrol.h:36, from mixer.h:25, from mixer.c:30: hctl_macros.h: In function `snd_hctl_elem_tlv_read': hctl_macros.h:136: warning: `snd_ctl_elem_tlv_read' is deprecated (declared at ctl_macros.h:1134) hctl_macros.h: In function `snd_hctl_elem_tlv_write': hctl_macros.h:142: warning: `snd_ctl_elem_tlv_write' is deprecated (declared at ctl_macros.h:1141) hctl_macros.h: In function `snd_hctl_elem_tlv_command': hctl_macros.h:148: warning: `snd_ctl_elem_tlv_command' is deprecated (declared at ctl_macros.h:1148) Alan

7 34

Re: [alsa-devel] trouble compiling alsa-drivers
by Wallace, Brooke 04 Aug '07

04 Aug '07

Package alsa-driver-1.0.14.tar.b2z also fails to compile with the same error. Is there a particualr version of the Kernel that is recommended to use? I don't think the issue is with including the macro itself, it is defined in adriver.h and including that file directly generates the same error. Seems that MARCO depends on another MACRO "RW_LOCK_UNLOCKED" and somewhere down the line there is a syntax error.... make[1]: Entering directory `/usr/src/kernels/2.6.9-34.EL-smp-i686' CC [M] /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/memallo c.o CC [M] /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/sgbuf.o CC [M] /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/memory_ wrapper.o CC [M] /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/pcm.o CC [M] /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/pcm_nat ive.o /local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/pcm_nat ive.c:75: error: syntax error before "snd_pcm_link_rwlock" ... [Many more similar errors] ... make[4]: *** [/local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore/pcm_na tive.o] Error 1 make[3]: *** [/local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14/acore] Error 2 make[2]: *** [_module_/local/mnt/views/brookew/alsa/workspace/alsa-driver-1.0.14] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.9-34.EL-smp-i686' make: *** [compile] Error 2 I will do some more digging around, but I don't want to go off the deep-end hacking software I don't understand, at least not yet. -Brooke ________________________________ From: Tobin Davis [mailto:tdavis@dsl-only.net] Sent: Thursday, August 02, 2007 6:21 PM To: Wallace, Brooke Subject: Re: [alsa-devel] trouble compiling alsa-drivers Alsa 1.0.14rc4 is NOT the latest. 1.0.14 went final a few weeks after, and there was a patch to fix build issues on Redhat's broken kernels that went into it. Tobin On Thu, 2007-08-02 at 16:53 -0700, Wallace, Brooke wrote: The alsa-drivers INSTALL file tells me: On 2.6 kernels, the build directory has to be given via --with-build=<kernel_build_dir> option additionaly, too. What exactly is mean by kernel_build_dir? I should not have to recompile my kernel because I already have the sourcecore module. Configure seems to work fine and locates my kernel source code: ./configure --with-cards=hda-intel --with-sequencer=yes But when I compile, it fails in acore/pcm_native.c line #75, acore/pcm_native.c line #75 uses the macro DEFINE_RWLOCK which apparently has not been defined yet. Searching thu the alsa-drivers source, I find that include/adriver.h defines this macro. What am I doing wrong? Why doesn't adriver.h get included when I compile acore/pcm_native.c? I'm using the latest release - alsa-driver-1.0.14rc4 My Kernel sources are: 2.6.9-34.EL-smp-i686 Alsa is already working fine on this system using the HDA Intel driver, its a RHEL- 3.4.5-2 system. I just want to re-compile the latest ALSA software and start writing a dummy user space driver that prints to a file or something. I should be able to cmopile all of the latest ALSA software... Any help is appreciated. -Brooke _______________________________________________ Alsa-devel mailing list Alsa-devel(a)alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel -- Tobin Davis Laetrile is the pits.

1 0

Re: [alsa-devel] Will the real alsa wiki please stand up?
by Eliot Blennerhassett 03 Aug '07

03 Aug '07

I'm confused again. Which is the real official wiki? This one "AlsaWiki" http://bugtrack.alsa-project.org/main/index.php/Main_Page (MediaWiki, last change 25 July) OR This one "Official Alsa Wiki for Developers" https://bugtrack.alsa-project.org/wiki/wikka.php?wakka=AlsaWiki (Powered by Wikka Wakka Wiki) approx 28 content pages, last change 24 July) It was made clear a while ago that this is the UNofficial wiki: http://alsa.opensrc.org/index.php/Main_Page (MediaWiki) Gosh!, how much fragmentation do we need???? If 3 wikis really are necessary, can we at least have links to the others on the main page of each wiki, and explanation of which is most approriate for different content? thanks Eliot

5 9

[alsa-devel] User space drivers
by Wallace, Brooke 03 Aug '07

03 Aug '07

Hi, I've been trying to sort thru the ALSA docs and am starting to get the impression that all of the existing drivers are written as Kernel Modules. Doesn't this mean that they are running in Kernel space and infact are not User Space drivers? Shouldn't there be an ALSA Drivers API document that covers an API that User Space Drivers can use? I must be mssing something here... I'm looking into ALSA because my company wants to use this standard for writing User Space drivers for our product running on various linux kernels. The reasoning for this is strictly proprietary licensing - our leagl department is not comfortable with the GPL and the possiblitiy that something written for Kernel space could at some time be considered as required to be GPL - not my decision... -Brooke

4 3

[alsa-devel] Output to Input routing
by Vadim Lebedev 02 Aug '07

02 Aug '07

Hello, I remember reading AC97 specs that there si possibility to configure it in such a way, that when doing stereo capture, left input channel will get actual MIC input and right input channel will get the copy of speaker output. This setting is ideal for echo cancellation algorithm. To my grand dismay i'm unable to find a doc of ALSA mixer API so i'm unsucessuful writing code to put mixer in such mode. Can some kind soul please contibuite a code snippet.... Thanks Vadim

2 3