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

[alsa-devel] [PATCH] Fix for alsa-lib cross-compilation problems with ALSA_CONFIG_DIR and ALSA_PLUGIN_DIR
by Pawel MOLL 07 Mar '08

07 Mar '08

Fix for alsa-lib cross-compilation problems with ALSA_CONFIG_DIR and ALSA_PLUGIN_DIR "./configure" options for selecting ALSA configuration (default /usr/share/alsa) and plugin (/usr/lib/alsa-lib) directories introduced by alsa-hg/alsa-lib changeset 2284 cause problems with cross-compilation and packaging - there is no way to redefine them in runtime, during installation phase. This patch adds a level of indirection between constants and their usage - alsaconfigdir for ALSA_CONFIG_DIR and alsaplugindir for ALSA_PLUGIN_DIR - which can be redefined during "make install" stage. Signed-off-by: Pawel MOLL <pawel.moll(a)st.com> --- Index: alsa-lib-1.0.16/modules/mixer/simple/Makefile.am =================================================================== --- alsa-lib-1.0.16.orig/modules/mixer/simple/Makefile.am +++ alsa-lib-1.0.16/modules/mixer/simple/Makefile.am @@ -1,4 +1,5 @@ -pkglibdir = @ALSA_PLUGIN_DIR@/smixer +alsaplugindir = @ALSA_PLUGIN_DIR@ +pkglibdir = $(alsaplugindir)/smixer pythonlibs = @PYTHON_LIBS@ pythonincludes = @PYTHON_INCLUDES@ Index: alsa-lib-1.0.16/src/conf/Makefile.am =================================================================== --- alsa-lib-1.0.16.orig/src/conf/Makefile.am +++ alsa-lib-1.0.16/src/conf/Makefile.am @@ -10,5 +10,6 @@ endif EXTRA_DIST = $(cfg_files) -alsadir = @ALSA_CONFIG_DIR@ +alsaconfigdir = @ALSA_CONFIG_DIR@ +alsadir = $(alsaconfigdir) alsa_DATA = $(cfg_files) Index: alsa-lib-1.0.16/src/conf/cards/Makefile.am =================================================================== --- alsa-lib-1.0.16.orig/src/conf/cards/Makefile.am +++ alsa-lib-1.0.16/src/conf/cards/Makefile.am @@ -1,4 +1,5 @@ -alsadir = @ALSA_CONFIG_DIR@/cards +alsaconfigdir = @ALSA_CONFIG_DIR@ +alsadir = $(alsaconfigdir)/cards cfg_files = aliases.conf \ AACI.conf \ ATIIXP.conf \ @@ -58,7 +59,7 @@ endif alsa_DATA = $(cfg_files) if BUILD_ALISP -SI7018dir = @ALSA_CONFIG_DIR@/cards/SI7018 +SI7018dir = $(alsaconfigdir)/cards/SI7018 SI7018_files = \ SI7018/sndoc-mixer.alisp \ SI7018/sndop-mixer.alisp Index: alsa-lib-1.0.16/src/conf/pcm/Makefile.am =================================================================== --- alsa-lib-1.0.16.orig/src/conf/pcm/Makefile.am +++ alsa-lib-1.0.16/src/conf/pcm/Makefile.am @@ -7,5 +7,6 @@ cfg_files = default.conf front.conf rear EXTRA_DIST = $(cfg_files) -alsadir = @ALSA_CONFIG_DIR@/pcm +alsaconfigdir = @ALSA_CONFIG_DIR@ +alsadir = $(alsaconfigdir)/pcm alsa_DATA = $(cfg_files)

2 1

Re: [alsa-devel] ALSACTL wrong restore on ARM9
by Liam Girdwood 07 Mar '08

07 Mar '08

On Fri, 2008-03-07 at 16:11 +0100, Alexandre BOUIN wrote: > Hi list, > > I'm using an intern AT91SAM92620-EK board with a WM8900 codec. > ALSACTL restores bad values to controls after doing this : > > $ rm /var/lib/alsa/asound.state > $ alsactl store > $ alsactl restore > > Anyone has seen this issue before ? > Any ideas to solve it ? (I don't know much these utils neither alsa API) > Could it come from our ASoC codec driver ? > Can you describe 'bad values' in a little more detail. Liam

2 1

[alsa-devel] ALSACTL wrong restore on ARM9
by Alexandre BOUIN 07 Mar '08

07 Mar '08

Hi list, I'm using an intern AT91SAM92620-EK board with a WM8900 codec. ALSACTL restores bad values to controls after doing this : $ rm /var/lib/alsa/asound.state $ alsactl store $ alsactl restore Anyone has seen this issue before ? Any ideas to solve it ? (I don't know much these utils neither alsa API) Could it come from our ASoC codec driver ? Thanks in advance. Regards, Alex.

1 0

[alsa-devel] M-Audio Delta Audiophile 192 again
by Computer AG im FSK 07 Mar '08

07 Mar '08

Hi, we didn't recieve an reply on our last email, so once again we are asking for support. Of course we know that everybody's time is small... We would like to know if someone will work on the bug https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3313 We repeat our offer of lending one card to someone who would like to fix it, like the reporter of the bug did. The GPL Version of the Open Sound System get this card working, so I hope it will not be that much work compared to other bugs ? If nobody will find time to fix it, a definetive answer would be nice so we can sell our 4 cards. But the probable loss of selling 4 card and buying 4 new ones could better be a donation for the alsa project ;) So please please help us out, we would be more than glad to give the money to the project than to loose it buying 4 new cards. Greetings, Toast

1 0

[alsa-devel] HDA Codecs: add support for Toshiba Equium L30
by Tobin Davis 07 Mar '08

07 Mar '08

This patch adds support for the Toshiba Equium L30 laptop and renames the mixer controls to match Laptop usages. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

2 1

[alsa-devel] What recommended performance for ALSA(ASoC)?
by Jinyoung Park 07 Mar '08

07 Mar '08

Hello, I tred developing new ALSA(ASoC) driver for our company's embedded processor. Our processor supported I2S and DMA. So, my ALSA drvier implementation using DMA. I was tested my ALSA driver. When I play wav file(sample rate 44100) using aplay( aplay -M -D hw:0,0 test.wav), sometimes occured breaks. Also, play mp3 file(sample rate 44100Hz) using madplay and mpg123, sometimes occured noises. So, I was tested wav file and mp3 file that down sampling 44100 -> 22050. They was not occurring break and decreasing noises. I tried improving my ALSA driver, optimize souce code and change variety buffer size and period size. But It doesn't improve much. In my guess, my target system is not enough performance because ALSA is heavy. Target system' processor(ARM9) clock is 200MHz and BogoMIPS is 99.6(cat /proc/cpuinfo). Linux kernel version is 2.6.24.1. What recommended performance for ALSA(ASoC)? If my target system is enough performance, shall I do that solve problem? Thanks.

3 2

[alsa-devel] [RFC] add a "private" field to the ac97 struct
by Sebastian Siewior 06 Mar '08

06 Mar '08

I have a PowerPC board with an AC97 controller and that one has an UCB1400 attached. Currently the UCB1400 driver discovers the interrupt via probing. This doesn't really work here. The resources are read from the device tree. I haven't found any other driver besides ucb1400_ts that uses the ac97_bus_type so I can't check where others get their HW information from. My proposal is to introduce a new field in struct snd_ac97 where the AC97 driver can leave the required HW info regarding the attached (in my case the interrupt for the ucb1400) before calling snd_card_register(). I attached just a single int field since I am not aware if multiple devices / resource are realistic / possible. In that case maybe a void * or struct platform_device would be a better choice. Signed-off-by: Sebastian Siewior <sebastian(a)breakpoint.cc> --- drivers/input/touchscreen/ucb1400_ts.c | 13 ++++++++----- include/sound/ac97_codec.h | 2 ++ 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/drivers/input/touchscreen/ucb1400_ts.c b/drivers/input/touchscreen/ucb1400_ts.c index 607f993..95d1fea 100644 --- a/drivers/input/touchscreen/ucb1400_ts.c +++ b/drivers/input/touchscreen/ucb1400_ts.c @@ -492,11 +492,14 @@ static int ucb1400_ts_probe(struct device *dev) goto err_free_devs; } - error = ucb1400_detect_irq(ucb); - if (error) { - printk(KERN_ERR "UCB1400: IRQ probe failed\n"); - goto err_free_devs; - } + if (!ucb->ac97->device_irq) { + error = ucb1400_detect_irq(ucb); + if (error) { + printk(KERN_ERR "UCB1400: IRQ probe failed\n"); + goto err_free_devs; + } + } else + ucb->irq = ucb->ac97->device_irq; error = request_irq(ucb->irq, ucb1400_hard_irq, IRQF_TRIGGER_RISING, "UCB1400", ucb); diff --git a/include/sound/ac97_codec.h b/include/sound/ac97_codec.h index 0148058..bf920a2 100644 --- a/include/sound/ac97_codec.h +++ b/include/sound/ac97_codec.h @@ -474,6 +474,8 @@ struct snd_ac97 { struct snd_ac97_build_ops * build_ops; void *private_data; void (*private_free) (struct snd_ac97 *ac97); + /* device attached to the AC97 bus */ + int device_irq; /* --- */ struct snd_ac97_bus *bus; struct pci_dev *pci; /* assigned PCI device - used for quirks */ -- 1.5.3.5

3 3

[alsa-devel] snd_pcm_open device names
by Reiner 06 Mar '08

06 Mar '08

with snd_pcm_open (handle, "default", SND_PCM_STREAM_PLAYBACK, 0) I can open a device twice with snd_pcm_open (handle, "plughw:0,0", SND_PCM_STREAM_PLAYBACK, 0) the 2. call fails with error -16. The docu says: The default device is equal to plug plugin with hw plugin as slave. ???? Reiner

3 3

[alsa-devel] [PATCH] Support for playing WAV files with "extensible format" header using aplay.
by Pawel MOLL 06 Mar '08

06 Mar '08

Support for playing WAV files with "extensible format" header using aplay. WAV files with more than 2 channels or with more than 16 bits per samples can be saved with "extensible format" chunk (see http://msdn2.microsoft.com/en-us/library/ms713496(VS.85).aspx). For instance, sox, when converting data to 24- or 32-bits per sample format uses this format, and aplay was unable to play such file. Now the problem is solved :-) Signed-off-by: Pawel MOLL <pawel.moll(a)st.com> --- diff -r 9c822ff3e9b9 aplay/aplay.c --- a/aplay/aplay.c Thu Feb 21 09:12:53 2008 +0100 +++ b/aplay/aplay.c Thu Mar 06 14:25:52 2008 +0000 @@ -745,16 +745,29 @@ static ssize_t test_wavefile(int fd, u_c check_wavefile_space(buffer, len, blimit); test_wavefile_read(fd, buffer, &size, len, __LINE__); f = (WaveFmtBody*) buffer; + if (LE_SHORT(f->format) == WAV_FMT_EXTENSIBLE) { + WaveFmtExtensibleBody *fe = (WaveFmtExtensibleBody*)buffer; + if (len < sizeof(WaveFmtExtensibleBody)) { + error(_("unknown length of extensible 'fmt ' chunk (read %u, should be %u at least)"), + len, (u_int)sizeof(WaveFmtExtensibleBody)); + exit(EXIT_FAILURE); + } + if (memcmp(fe->guid_tag, WAV_GUID_TAG, 14) != 0) { + error(_("wrong format tag in extensible 'fmt ' chunk")); + exit(EXIT_FAILURE); + } + f->format = fe->guid_format; + } if (LE_SHORT(f->format) != WAV_FMT_PCM && LE_SHORT(f->format) != WAV_FMT_IEEE_FLOAT) { error(_("can't play WAVE-file format 0x%04x which is not PCM or FLOAT encoded"), LE_SHORT(f->format)); exit(EXIT_FAILURE); } - if (LE_SHORT(f->modus) < 1) { - error(_("can't play WAVE-files with %d tracks"), LE_SHORT(f->modus)); - exit(EXIT_FAILURE); - } - hwparams.channels = LE_SHORT(f->modus); + if (LE_SHORT(f->channels) < 1) { + error(_("can't play WAVE-files with %d tracks"), LE_SHORT(f->channels)); + exit(EXIT_FAILURE); + } + hwparams.channels = LE_SHORT(f->channels); switch (LE_SHORT(f->bit_p_spl)) { case 8: if (hwparams.format != DEFAULT_FORMAT && @@ -1805,7 +1818,7 @@ static void begin_wave(int fd, size_t cn f.format = LE_SHORT(WAV_FMT_IEEE_FLOAT); else f.format = LE_SHORT(WAV_FMT_PCM); - f.modus = LE_SHORT(hwparams.channels); + f.channels = LE_SHORT(hwparams.channels); f.sample_fq = LE_INT(hwparams.rate); #if 0 tmp2 = (samplesize == 8) ? 1 : 2; diff -r 9c822ff3e9b9 aplay/formats.h --- a/aplay/formats.h Thu Feb 21 09:12:53 2008 +0100 +++ b/aplay/formats.h Thu Mar 06 14:25:52 2008 +0000 @@ -69,6 +69,10 @@ typedef struct voc_ext_block { #define WAV_FMT_PCM 0x0001 #define WAV_FMT_IEEE_FLOAT 0x0003 #define WAV_FMT_DOLBY_AC3_SPDIF 0x0092 +#define WAV_FMT_EXTENSIBLE 0xfffe + +/* Used with WAV_FMT_EXTENSIBLE format */ +#define WAV_GUID_TAG "\x00\x00\x00\x00\x10\x00\x80\x00\x00\xAA\x00\x38\x9B\x71" /* it's in chunks like .voc and AMIGA iff, but my source say there are in only in this combination, so I combined them in one header; @@ -81,13 +85,22 @@ typedef struct { } WaveHeader; typedef struct { - u_short format; /* should be 1 for PCM-code */ - u_short modus; /* 1 Mono, 2 Stereo */ + u_short format; /* see WAV_FMT_* */ + u_short channels; u_int sample_fq; /* frequence of sample */ u_int byte_p_sec; u_short byte_p_spl; /* samplesize; 1 or 2 bytes */ u_short bit_p_spl; /* 8, 12 or 16 bit */ } WaveFmtBody; + +typedef struct { + WaveFmtBody format; + u_short ext_size; + u_short bit_p_spl; + u_int channel_mask; + u_short guid_format; /* WAV_FMT_* */ + u_char guid_tag[14]; /* WAV_GUID_TAG */ +} WaveFmtExtensibleBody; typedef struct { u_int type; /* 'data' */

2 1

[alsa-devel] Problems with ALSA in embedded device
by Imanol Trapote 06 Mar '08

06 Mar '08

Hi all, I am developing a product in an embedded system that uses ALSA library. This system can't use the dynamic linker, I am using flat binaries. I use this configuration options: --without-libdl \ --with-pthread \ --with-softload \ --disable-alisp \ --disable-hwdep \ --disable-seq \ --disable-resmgr \ --disable-rawmidi \ --disable-old-symbols \ --disable-python \ --disable-mixer I try to use the same configuration options in a PC for debugging, and I get the same problem, when I try to list devices with aplay, I get this: aplay -L ALSA lib conf.c:2699:(snd_config_hooks_call) Cannot open shared library (null) ALSA lib conf.c:3076:(snd_config_update_r) hooks failed, removing configuration It's possible use ALSA without dynamic libraries, with this configuration Thanks in advance. Imanol Trapote ----------------------------------------- PLEASE NOTE ------------------------------------------- This message, along with any attachments, may be confidential or legally privileged. It is intended only for the named person(s), who is/are the only authorized recipients. If this message has reached you in error, kindly destroy it without review and notify the sender immediately. Thank you for your help. ZIV uses virus scanning software but excludes any liability for viruses contained in any attachment. ------------------------------------ ROGAMOS LEA ESTE TEXTO ------------------------------- Este mensaje y sus anexos pueden contener información confidencial y/o con derecho legal. Está dirigido únicamente a la/s persona/s o entidad/es reseñadas como único destinatario autorizado. Si este mensaje le hubiera llegado por error, por favor elimínelo sin revisarlo ni reenviarlo y notifíquelo inmediatamente al remitente. Gracias por su colaboración. ZIV utiliza software antivirus, pero no se hace responsable de los virus contenidos en los ficheros anexos.

2 3