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

[alsa-devel] DMIX and Alsa Drivers
by Barclay, Bruce 02 Apr '08

02 Apr '08

I wrote an Alsa driver with copy callbacks and it worked. Later read that you can use copy callbacks if you want to use dmix so I rewrote it to not use copy callbacks. I don't see much documentation on dmix (/etc/asound.conf). When I put dmix in there, I can run two versions but the framework never updates the application pointer so I get no data. I take the dmix out and it works fine. No clue on what to do. Bruce

1 0

Re: [alsa-devel] PXA2xx/3xx AC97 Driver(s)
by Mark Brown 02 Apr '08

02 Apr '08

On Mon, Mar 24, 2008 at 12:38:00PM +0000, Oliver Ford wrote: > Is there any work currently under way on an AC97 driver for the PXA3xx? There is PXA3xx AC97 support present in the ASoC tree: git://opensource.wolfsonmicro.com/linux-2.6-asoc It's under the asoc-v2-dev branch at the minute and is probably only done for the ASoC AC97 driver, I'd need to check. The main reason it's only there is that it depends on the ARM architecture changes that you identified (which are also applied on the asoc-v2-dev branch) and it makes life easier to manage the cross-tree changes in only one tree. All the ARM architecture changes have been submitted and marked as applied in the patch system so should hopefully appear in Linus' kernel early in the 2.6.26 cycle. Once this has happened I will submit the AC97 driver PXA3xx support. > I want to get the touch screen working on my iPAQ 214, which uses the > PXA310. It's a WM97xx chip on the AC97 interface. I'm not really too I know that there are a number of users currently using the tree for that use case so the asoc-v2-dev branch should hopefully work for you. If you run into trouble please let me know. > include/asm-arm/arch-pxa/pxa3xx-regs.h). Does the pxa310 require > anything special like this or should just setting the cold-reset in > the AC97 GCR work? It also doesn't support the use of interrupts during reset operations, requiring another special case, but I think that's about it. > The Wolfson Microelectronics open-source page indicates that work is on > going with the 3xx driver but there doesn't seem to be anything more > than the pxa2xx driver in their source tree. Does anyone know how active > / close to producing anything this is? Like I say, it's there. The changes are fairly straightforward and should be easy to backport to whatever kernel you need - if you need help identifying what needs merging over please just ask. > More generally, I'm a little confused as to why there is both the > standard (sound/arm/pxa2xx-ac97.c) and SoC (sound/soc/pxa/pxa2xx-ac97) > driver. Is one of these obsolete now or are they both still in > development? If guessing, I'd say the SoC driver is now the one to use The SoC driver is generally preferable, though it requires a bit more work to use (since you have to write a platform driver to use it). Both are still maintained. SoC offers better power management and support for a wider range of board configurations, especially those that also have non-AC97 interfaces (such as the I2S interface on the WM97xx parts). > but am not sure. Compiling either gives the warning "'pxa_set_cken' is > deprecated". I suspect calling this won't work for the pxa310 since it's This is also fixed in the patches currently queued in the ARM tree - the drivers have been converted to use the clk_() API. > clocks are different, but given that I'm booting linux from windows > (which will leave the clock on) and don't particularly care about > suspend/resume, should not being able to switch it off be a problem? The cken calls should actually work fine.

2 3

[alsa-devel] Marian sound card support
by Peter Brooks 02 Apr '08

02 Apr '08

Hi all, I'm looking at a Marian 8 sound card (http://www.marian.de/en/products/trace8), and it has no mention on the alsa site. Is there any support for this card? I'm looking for a sound card with the maximum amount of outputs, I don't need many inputs. Currently the only one after this card I see is an M-Audio 1010. Cheers -- Peter Brooks

1 0

[alsa-devel] snd-powermac
by Risto Suominen 02 Apr '08

02 Apr '08

I'm about to send the following to alsa-user mailing list: I've been trying to fix ALSA support for older PowerMacs. Anyone experiencing problems - like missing or inoperative or wrongly directed controls in alsamixer - could you, please, test my patch and write the results into this list or directly to me? If you are still with me, check first with lsmod that you are using snd-powermac: $ lsmod | grep ^snd.powermac snd_powermac 56576 0 $ Then you will need to install make, C-compiler and kernel headers corresponding to your running kernel, f.ex (Ubuntu Dapper 6.06.1): $ sudo aptitude install make gcc linux-headers-2.6.15-26-powerpc and fetch the ALSA driver source code and my patch: $ wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.16.tar.bz2 $ wget http://ristosu.wippiespace.com/pub/alsa-driver-1.0.16-p4.diff Unpack the source and apply the patch: $ tar xjf alsa-driver-1.0.16.tar.bz2 $ cd alsa-driver-1.0.16 $ patch -p0 < ../alsa-driver-1.0.16-p4.diff Finally configure: $ ./configure --disable-verbose-printk --with-kernel=/usr/src/linux-headers-2.6.15-26-powerpc --with-build=/usr/src/linux-headers-2.6.15-26-powerpc --with-moddir=/lib/modules/2.6.15-26-powerpc/updates/sound --with-isapnp=no --with-oss=yes --with-pcm-oss-plugins=yes --with-cards=powermac make and install: $ make $ sudo make install-modules To load the new modules without rebooting: $ sudo modprobe -r snd-powermac $ sudo modprobe -r snd-pcm-oss $ sudo modprobe snd-powermac Risto

1 3

[alsa-devel] Alsa : GPL or LGPL ?
by liste＠votreservice.com 02 Apr '08

02 Apr '08

Wikipedia says Alsa is under the GPL and LGPL ? Can I use Alsa for recording and playing sound in my proprietary game under Linux ? Dsant

2 1

[alsa-devel] Detecting new alsa sequencer clients (with some event loop) so that i can subscribe them
by R. Dresens 01 Apr '08

01 Apr '08

Hello, I'm currently writing an application that will be able to 'auto subscribe' itself to a certain sequencer client when that client becomes available to the system. I want (for example) to be able to plug in a USB MIDI interface, and when I do that then my application detects this and does a subscription on it, just like aconnect would do. A possible solution is polling; every second or so, i could generate a list of clients with snd_seq_query_next_client and look for a certain client name (libpcre comes to mind here;), but I was wondering if there is a better solution? ..in other words, is it possible to get such events from the system in a similar way like one would receive regular MIDI events? http://www.alsa-project.org/alsa-doc/alsa-lib/structsnd__seq__event.html list all the events; an interesting one could be snd_seq_connect_t for monitoring connections on my own ports, but that's not what I'm looking for. I can't seem to find an event related to this functionality. Is there something what I'm currently overlooking? Such functionality may be usefull for GUI versions of aconnect. I looked in the source of qjackctl (it has an alsa patchbay), but I haven't found nothing usefull yet since it seems to me that this software also does polling/refresh on a certain interval. Has anyone a usefull tip for me? Thanks in advance, Greetings, Raymond Dresens.

2 2

[alsa-devel] [Fwd: Re: [regression] 2.6.25-rc4 snd-es18xx broken on Alpha]
by Tyson Whitehead 01 Apr '08

01 Apr '08

Sorry. Bob was just saying this could be an important observation, but it didn't get to everyone as the CC list got shortened. Cheers! -Tyson

1 0

Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
by rct＠frus.com 01 Apr '08

01 Apr '08

rct wrote: > Rene Herman wrote: > > Okay, and applying the attached just makes your sound completely dead in the > > water? > > (patch to remove es1888_init from a Miata build omitted) > > I'll try a build with the old OSS "sb" driver, and if that works ok, we > may be able to do away with es1888_init() on the Miata. Tyson -- I > think you have a Miata if I'm remembering correctly: can you confirm > these observations? Quick followup: OSS "sb" driver works fine without es1888_init(). -- ------------------------------------------------------------------------ Bob Tracy | "I was a beta tester for dirt. They never did rct(a)frus.com | get all the bugs out." - Steve McGrew on /. ------------------------------------------------------------------------

5 8

[alsa-devel] How to reduce delay between playback and capture for echo canceller
by Cliff Cai 01 Apr '08

01 Apr '08

Hi all, I'm playing a linphone based VOIP demo board these days,the board can connect different soundcard daughter board as playback and capture devices through I2S or AC97.Then I experience a bad echo on my PC(using liphone and headset) when talk with the board (with speaker and MIC on board).So I enable the echo canceller (based on speex) for it. One of my sound card (connected by I2S) works pretty well,but the other one (connected by AC97) doesn't work. Through the diagnostic tool provided by speex I find that the ac97 one has a big delay between played signal(reference signal) and captured signal.Just the delay make echo canceller don't work as expectation.So I think the driver for the AC97 soundcard need some improvement to reduce the delay. Has anyone a usefull direction for me? Thanks in advance,Best Regards Cliff Cai _________________________________________________________________ MSN 中文网，最新时尚生活资讯，白领聚集门户。 http://cn.msn.com

1 0

[alsa-devel] [Fwd: Re: Davinci ASoC support (patch)]
by lokowich 01 Apr '08

01 Apr '08

Forwarded from davinci-linux-open-source list: I've built this ASoC patch into my DaVinci git kernel (thanks for the SENSORS tip), and can use aplay and speaker-test, but no sound. Figured it may be a mixer/volume control issue, but the alsamixer is unable to open for a failed ioctl on USBDEVFS_IOCTL. Not sure why there is a USB dependency. Noted that there is no /sys/class/sound/mixer in my sysfs. Any ideas? Mark Bernard Blackham wrote: > Behme wrote: > >> While searching something different, I just found >> >> http://www.spinics.net/lists/alsa-devel/msg12535.html >> >> As I'm not subscribed to alsa-devel, I don't have the original post. >> Maybe any of the authors can post it do this list as well? >> >> The patch mainly applies to our git. I fixed two small rejects in >> Kconfig and Makefile as the patch is for newer kernel than our git. >> Untested patch against our git in attachment. Anybody likes to test? >> > > Well, I tried compiling it and it failed to build. It appears that it's > built on a set of patches for Davinci posted to LAK, including this > completely revamped EDMA support[1]: > > http://www.spinics.net/lists/arm-kernel/msg47450.html > > So I had to change a few definitions, import a few functions from the new > DMA support and managed to get it compiling and loading, but not yet working > (tried various sample rates and formats): > > root@davinci-dvevm:/tst$ aplay test.wav > Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo > ALSA lib pcm_params.c:2152:(snd_pcm_hw_refine_slave) Slave PCM not usable > aplay: set_params:878: Broken configuration for this PCM: no configurations > available > > root@davinci-dvevm:/tst$ arecord -r 48000 -f S16_LE > Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono > ALSA lib pcm_params.c:2152:(snd_pcm_hw_refine_slave) Slave PCM not usable > arecord: set_params:878: Broken configuration for this PCM: no > configurations available > > > And this is the extent of my knowledge of ALSA - I can continue digging, but > maybe somebody else will beat me to it =) It's looking promising though. > > Attached is the patch I have so far that applies against current git. This > is not for going upstream, but just for testing. Notes: > - Apply patch > - Enable SND_SOC, SND_DAVINCI_SOC, SND_DAVINCI_SOC_I2S, SND_DAVINCI_SOC_EVM > and SND_SOC_TLV320AIC3X. > - Make sure CONFIG_I2C_DAVINCI is enabled, but disable the > CONFIG_SENSORS_TLV320* options. > - Build. > - Load the snd-soc-evm module. > > Bernard. > > [1] These patches appear to have gone absolutely nowhere beyond that list. I > can't find them in any tree. But they are cleaner and more conforming to the > Linux Kernel style than what's currently in git. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Davinci-linux-open-source mailing list > Davinci-linux-open-source(a)linux.davincidsp.com > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source >

4 8