Alsa-lib problem

Alsa-lib problem

[Nambiar, Anil]

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

Hi,

            I am developing ALSA based sound driver for our arm based soc.
The driver is built as part of the kernel rather than as a loadable module.
If I run a simple wave player which has OSS based interface, it works fine.
Even mplayer works fine in OSS emulation mode. But if I run any native alsa
based player it gives error opening the device. For eg: running 'aplay -D
default demo.wav" give the following error: 

ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default

aplay: main:533: audio open error: No such file or directory

 

The /dev/snd/ looks like this:

drwxr-xr-x    2 root     root         4096 Aug  9  2005 .

drwxr-xr-x    6 root     root         4096 Aug  9  2005 ..

crw-rw-rw-    1 root     root     116,   0 Aug  9  2005 controlC0

crw-rw-rw-    1 root     root     116,  24 Aug  9  2005 pcmC0D0c

crw-rw-rw-    1 root     root     116,  16 Aug  9  2005 pcmC0D0p

crw-rw-rw-    1 root     root     116,   1 Aug  9  2005 seq

crw-rw-rw-    1 root     root     116,  33 Aug  9  2005 timer

 

            If I do "cat demo.wav > dev/snd/pcmC0D0p", it prints the 'open'
msg in my driver. So it seems like the devices I have created are able to
link to my driver. But using alsa-lib it doen't even print the 'open' msg in
the driver. So looks like Alsa-lib does not link to my driver. 

I would appreciate if someone could point and tell me if I'm missing
something as this is the first time I'm developing Alsa device driver. Do I
have to create any configuration files on the root file system? I'm using
the linux kernel 2.6.12.3 and the latest Alsa-lib 1.0.9. 

 

Thanks,

AniL


[-- Attachment #2: Type: text/html, Size: 5045 bytes --]

Re: Alsa-lib problem

[Lee Revell]

On Tue, 2005-08-09 at 17:57 -0400, Nambiar, Anil wrote:
> Hi,
> 
>             I am developing ALSA based sound driver for our arm based
> soc. The driver is built as part of the kernel rather than as a
> loadable module. If I run a simple wave player which has OSS based
> interface, it works fine. Even mplayer works fine in OSS emulation
> mode. But if I run any native alsa based player it gives error opening
> the device. For eg: running 'aplay -D default demo.wav" give the
> following error: 
> 
> ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
> 
> aplay: main:533: audio open error: No such file or directory

It looks like alsa-lib is not finding the default PCM config for your
chip.  Someone else developing a driver for ARM reported the same
problem.

Try stracing the aplay process, you will see alsa-lib trying to open the
various config files ~/.asoundrc, /etc/asound.conf, and (most
important) /usr/share/alsa/*, and compare the results to what you get
when you strace aplay on a known good driver like snd-intel8x0.

Lee



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Alsa-lib problem

[James Courtier-Dutton]

Nambiar, Anil wrote:
> Hi,
> 
>             I am developing ALSA based sound driver for our arm based soc.
> The driver is built as part of the kernel rather than as a loadable module.
> If I run a simple wave player which has OSS based interface, it works fine.
> Even mplayer works fine in OSS emulation mode. But if I run any native alsa
> based player it gives error opening the device. For eg: running 'aplay -D
> default demo.wav" give the following error: 
> 
> ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
> 
> aplay: main:533: audio open error: No such file or directory
> 

You probably do not have a "default" device defined for your card due to 
the lack of a config file.
But, in order to test it, even though you don't have a config file, try
speaker-test -c2 -Dplughw:0,0

if that works, all you then need is a config file for your card.
cat /proc/asound/cards  and note down whatever is in the [....    ] bit.
Here I get:
0 [Audigy2        ]: Audigy2 - Audigy 4 PRO [SB0380]
                      Audigy 4 PRO [SB0380] (rev.4, serial:0x20071102) 
at 0x9800, irq 20


So I have an "Audigy2" file in /usr/share/alsa/cards
You will need to create one for your card.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Alsa-lib problem

[Takashi Iwai]

At Tue, 09 Aug 2005 23:18:43 +0100,
James Courtier-Dutton wrote:
> 
> Nambiar, Anil wrote:
> > Hi,
> > 
> >             I am developing ALSA based sound driver for our arm based soc.
> > The driver is built as part of the kernel rather than as a loadable module.
> > If I run a simple wave player which has OSS based interface, it works fine.
> > Even mplayer works fine in OSS emulation mode. But if I run any native alsa
> > based player it gives error opening the device. For eg: running 'aplay -D
> > default demo.wav" give the following error: 
> > 
> > ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
> > 
> > aplay: main:533: audio open error: No such file or directory
> > 
> 
> You probably do not have a "default" device defined for your card due to 
> the lack of a config file.

The "default" PCM isn't necessarily defined explicitly per card.
If not defined, plughw is used as fallback.


Takashi


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Compulab sound device

[Chow Raymond]

Hi All,

I got a question here. Does ALSA support ac97 codec as
a soundcard? Im not too sure whether ac97 can work on
the Compulab Armcore board. This is because when i
type "cat /proc/asound/devices", all i get is this.

[root@ARMCore root]$ cat /proc/asound/devices
 33:       : timer

Does this mean that i got it wrong during building my
kernel? Or does this mean that the ac97 interface in
the armcore is not supported by ALSA?

Please advice me. Hope to hear from you guys soon.

Thanks.

Regards

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> Does ALSA support ac97 codec as a soundcard?

An AC'97 codec is always connected to an AC'97 controller.  It's the
controller that would be supported (or not) by ALSA.

> Im not too sure whether ac97 can work on the Compulab Armcore
> board.

ALSA has a driver for the AC'97 controller in the PXA2xx chip
(snd-pxa2xx-ac97).


HTH
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

--- Clemens Ladisch <clemens@ladisch.de> wrote:
> An AC'97 codec is always connected to an AC'97
> controller.  It's the
> controller that would be supported (or not) by ALSA.
> 

Umm..so is the ac97 controller supported by ALSA? I
select that driver during kernel configuration (Sound
-> ALSA -> ALSA Arm Devices). However, when i flash
the kernel into the Compulab Armcore, it could not
detect any sound devices. 

[root@ARMCore root]$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.4
(Mon May 17 14:31:44 200.
Compiled on Aug 10 2005 for kernel 2.6.7-armcore.

[root@ARMCore root]$ cat /proc/asound/devices
 33:       : timer

There is no digital audio playback/capture. Did I miss
something here? How do I know whether ALSA works on
Compulab's Armcore? 

Regards,
Raymond


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> --- Clemens Ladisch <clemens@ladisch.de> wrote:
> > An AC'97 codec is always connected to an AC'97
> > controller.  It's the
> > controller that would be supported (or not) by ALSA.
>
> Umm..so is the ac97 controller supported by ALSA?

Yes.  The Compulab website says it's using a PXA255 chip,
and the "AC97 driver for the Intel PXA2xx chip" should
support it.

> I select that driver during kernel configuration (Sound
> -> ALSA -> ALSA Arm Devices). However, when i flash
> the kernel into the Compulab Armcore, it could not
> detect any sound devices.
>
> [root@ARMCore root]$ cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.4

I don't think you were able to select the PXA driver
with that ALSA version.

Get the CVS version of ALSA, and try to copy the
contents of the alsa-kernel/arm/ directory into your
kernel's sound/arm/ directory.


HTH
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

Im not sure how to use CVS. Anyway I followed what you
suggested which is to copy the content in
alsa-kernel/arm to kernel's sound/arm. However, when i
rebuild the kernel, i face a missing header file. 

CC      sound/arm/pxa2xx-ac97.o
sound/arm/pxa2xx-ac97.c:31:28: asm/arch/audio.h: No
such file or directory
sound/arm/pxa2xx-ac97.c: In function
`pxa2xx_ac97_read':
sound/arm/pxa2xx-ac97.c:60: warning: implicit
declaration of function `wait_even
t_timeout'
sound/arm/pxa2xx-ac97.c: At top level:
sound/arm/pxa2xx-ac97.c:175: error: parse error before
"pxa2xx_ac97_ops"
sound/arm/pxa2xx-ac97.c:175: warning: type defaults to
`int' in declaration of `
pxa2xx_ac97_ops'
sound/arm/pxa2xx-ac97.c:176: error: field name not in
record or union initialize
r
sound/arm/pxa2xx-ac97.c:176: error: (near
initialization for `pxa2xx_ac97_ops')
sound/arm/pxa2xx-ac97.c:176: warning: initialization
makes integer from pointer
without a cast
sound/arm/pxa2xx-ac97.c:177: error: field name not in
record or union initialize
r
sound/arm/pxa2xx-ac97.c:177: error: (near
initialization for `pxa2xx_ac97_ops')
sound/arm/pxa2xx-ac97.c:177: warning: excess elements
in scalar initializer
.
.
.
.
sound/arm/pxa2xx-ac97.c:353: warning: pasess elements
in scalar initializer
' from incompatible pointer type initialization for
`pxa2xx_ac97_ops'
make[2]: *** [sound/arm/pxa2xx-ac97.o] Error 1
make[1]: *** [sound/arm] Error 2         
make: *** [sound] Error 2  

Do I miss anything? Where can i get audio.h file?

Raymond


--- Clemens Ladisch <clemens@ladisch.de> wrote:

> Chow Raymond wrote:
> > --- Clemens Ladisch <clemens@ladisch.de> wrote:
> > > An AC'97 codec is always connected to an AC'97
> > > controller.  It's the
> > > controller that would be supported (or not) by
> ALSA.
> >
> > Umm..so is the ac97 controller supported by ALSA?
> 
> Yes.  The Compulab website says it's using a PXA255
> chip,
> and the "AC97 driver for the Intel PXA2xx chip"
> should
> support it.
> 
> > I select that driver during kernel configuration
> (Sound
> > -> ALSA -> ALSA Arm Devices). However, when i
> flash
> > the kernel into the Compulab Armcore, it could not
> > detect any sound devices.
> >
> > [root@ARMCore root]$ cat /proc/asound/version
> > Advanced Linux Sound Architecture Driver Version
> 1.0.4
> 
> I don't think you were able to select the PXA driver
> with that ALSA version.
> 
> Get the CVS version of ALSA, and try to copy the
> contents of the alsa-kernel/arm/ directory into your
> kernel's sound/arm/ directory.
> 
> 
> HTH
> Clemens
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> Im not sure how to use CVS. Anyway I followed what you
> suggested which is to copy the content in
> alsa-kernel/arm to kernel's sound/arm. However, when i
> rebuild the kernel, i face a missing header file.
>
> asm/arch/audio.h: No such file or directory

It seems your kernel is too old.
A newer kernel would have a newer ALSA, too.


HTH
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

I can't compile a newer kernel version. This is
because Compulab Armcore only supports till kernel
2.6.7 and in that contains ALSA 1.0.4. 

Anymore options to solve this? Really appreciate the
help all this while.

Regards,
Chow Raymond

--- Clemens Ladisch <clemens@ladisch.de> wrote:

> Chow Raymond wrote:
> > Im not sure how to use CVS. Anyway I followed what
> you
> > suggested which is to copy the content in
> > alsa-kernel/arm to kernel's sound/arm. However,
> when i
> > rebuild the kernel, i face a missing header file.
> >
> > asm/arch/audio.h: No such file or directory
> 
> It seems your kernel is too old.
> A newer kernel would have a newer ALSA, too.
> 
> 
> HTH
> Clemens
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is Sponsored by the Better Software
> Conference & EXPO
> September 19-22, 2005 * San Francisco, CA *
> Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects
> & Teams * Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> I can't compile a newer kernel version. This is
> because Compulab Armcore only supports till kernel
> 2.6.7 and in that contains ALSA 1.0.4.

You could backport the ARM audio changes between 2.6.7 and 2.6.12, or
you could port Compulab's changes (if any) to 2.6.12.


HTH
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

Ok..I backport ARM audio changes from 2.6.12 to 2.6.7.
I manage to build a zImage file and manage to make
modules too. However..there are few warnings that i
encounter during make modules

sound/pci/ac97/ac97_codec.c: In function
`snd_ac97_mixer':
sound/pci/ac97/ac97_codec.c:1771: warning: unused
variable `pid'
sound/pci/ac97/ac97_codec.c: At top level:
sound/pci/ac97/ac97_codec.c:1740: warning:
`null_build_ops' defined but not used

Building modules, stage 2.
  MODPOST
*** Warning: "dma_mmap_writecombine"
[sound/arm/snd-pxa2xx-pcm.ko] undefined!
*** Warning: "pxa_set_cken"
[sound/arm/snd-pxa2xx-ac97.ko] undefined!
*** Warning: "snd_ac97_get_short_name"
[sound/arm/snd-pxa2xx-ac97.ko] undefined!

I thought warnings would be ok. I started inserting
modules but when I want to insert the snd-pxa2xx-ac97
module, I get the following error.

[root@ARMCore sound1]$ insmod snd-pxa2xx-ac97.ko
snd_pxa2xx_ac97: Unknown symbol pxa2xx_pcm_new
snd_pxa2xx_ac97: Unknown symbol
snd_ac97_get_short_name
snd_pxa2xx_ac97: Unknown symbol pxa_set_cken
insmod: error inserting 'snd-pxa2xx-ac97.ko': -1
Unknown symbol in module

Which file should I fix? There is not any
snd-pxa2xx-ac97.c file. What does unknown symbol in
module means?

Hope to hear from you soon.

Raymond

--- Clemens Ladisch <clemens@ladisch.de> wrote:

> Chow Raymond wrote:
> > I can't compile a newer kernel version. This is
> > because Compulab Armcore only supports till kernel
> > 2.6.7 and in that contains ALSA 1.0.4.
> 
> You could backport the ARM audio changes between
> 2.6.7 and 2.6.12, or
> you could port Compulab's changes (if any) to
> 2.6.12.
> 
> 
> HTH
> Clemens
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is Sponsored by the Better Software
> Conference & EXPO
> September 19-22, 2005 * San Francisco, CA *
> Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects
> & Teams * Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> Ok..I backport ARM audio changes from 2.6.12 to 2.6.7.
> I manage to build a zImage file and manage to make
> modules too. However..there are few warnings that i
> encounter during make modules
>
> Building modules, stage 2.
>   MODPOST
> *** Warning: "dma_mmap_writecombine" [sound/arm/snd-pxa2xx-pcm.ko] undefined!
> *** Warning: "pxa_set_cken" [sound/arm/snd-pxa2xx-ac97.ko] undefained!
> *** Warning: "snd_ac97_get_short_name" [sound/arm/snd-pxa2xx-ac97.ko] undefined!
>
> I thought warnings would be ok.

Those aren't.

It seems the audio changes depend on other kernel changes.  You'd
better just use 2.6.12.


HTH
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Liam Girdwood]

On Fri, 2005-08-19 at 05:47 -0700, Chow Raymond wrote:
> Ok..I backport ARM audio changes from 2.6.12 to 2.6.7.
> I manage to build a zImage file and manage to make
> modules too. However..there are few warnings that i
> encounter during make modules
> 

You might want to back port from ALSA kernel CVS as this has some
updates to pxa2xx-ac97.c for PM and ac97 warm resets. 


> sound/pci/ac97/ac97_codec.c: In function
> `snd_ac97_mixer':
> sound/pci/ac97/ac97_codec.c:1771: warning: unused
> variable `pid'
> sound/pci/ac97/ac97_codec.c: At top level:
> sound/pci/ac97/ac97_codec.c:1740: warning:
> `null_build_ops' defined but not used
> 
> Building modules, stage 2.
>   MODPOST
> *** Warning: "dma_mmap_writecombine"
> [sound/arm/snd-pxa2xx-pcm.ko] undefined!
> *** Warning: "pxa_set_cken"
> [sound/arm/snd-pxa2xx-ac97.ko] undefined!
> *** Warning: "snd_ac97_get_short_name"
> [sound/arm/snd-pxa2xx-ac97.ko] undefined!

Has sound/pci/ac97/ac97_codec.c and sound/arm/pxa2xx-pcm.c been built ?
They are both required form pxa2xx ac97 audio. 

> 
> I thought warnings would be ok. I started inserting
> modules but when I want to insert the snd-pxa2xx-ac97
> module, I get the following error.
> 
> [root@ARMCore sound1]$ insmod snd-pxa2xx-ac97.ko
> snd_pxa2xx_ac97: Unknown symbol pxa2xx_pcm_new
> snd_pxa2xx_ac97: Unknown symbol
> snd_ac97_get_short_name
> snd_pxa2xx_ac97: Unknown symbol pxa_set_cken
> insmod: error inserting 'snd-pxa2xx-ac97.ko': -1
> Unknown symbol in module
> 

This means that snd-pxa2xx-pcm.ko has not been inserted. It's built from
pxa2xx-pcm.c

> Which file should I fix? There is not any
> snd-pxa2xx-ac97.c file. What does unknown symbol in
> module means?
> 

This relates to sound/arm/pxa2xx-ac97.c

You should have the following rules in sound/arm/Makefile:-

snd-pxa2xx-pcm-objs := pxa2xx-pcm.o
snd-pxa2xx-ac97-objs := pxa2xx-ac97.o

obj-$(CONFIG_SND_PXA2xx_PCM) += snd-pxa2xx-pcm.o
obj-$(CONFIG_SND_PXA2xx_AC97) += snd-pxa2xx-ac97.o

and the following options in sound/arm/Kconfig

config SND_PXA2xx_AC97
	tristate "AC97 driver for the Intel PXA2xx chip"
	depends on ARCH_PXA && SND
	select SND_PXA2xx_PCM
	select SND_AC97_CODEC
	help
	  Say Y or M if you want to support any AC97 codec attached to
	  the PXA2xx AC97 interface.

config SND_PXA2xx_PCM
	tristate
	select SND_PCM
	help
	  Generic PCM module for PXA2xx


HTH

Liam



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

> You might want to back port from ALSA kernel CVS as
> this has some
> updates to pxa2xx-ac97.c for PM and ac97 warm
> resets. 

Ok. I will to do that.


> 
> Has sound/pci/ac97/ac97_codec.c and
> sound/arm/pxa2xx-pcm.c been built ?
> They are both required form pxa2xx ac97 audio. 

yes they have been built. 
[crc088@ linux-2.6.7]$ ls sound/arm/
built-in.o     Makefile.rej   pxa2xx-pcm.o          
snd-pxa2xx-ac97.o
Kconfig        pxa2xx-ac97.c  sa11xx-uda1341.c      
snd-pxa2xx-pcm.ko
Kconfig.orig   pxa2xx-ac97.o  snd-pxa2xx-ac97.ko    
snd-pxa2xx-pcm.mod.c
Makefile       pxa2xx-pcm.c   snd-pxa2xx-ac97.mod.c 
snd-pxa2xx-pcm.mod.o
Makefile.orig  pxa2xx-pcm.h   snd-pxa2xx-ac97.mod.o 
snd-pxa2xx-pcm.o

[crc088@ linux-2.6.7]$ ls sound/pci/ac97/
ac97_codec.c               .ac97_pcm.o.cmd
ac97_codec.c.orig          ac97_proc.c
ac97_codec.c.rej           ac97_proc.o
ac97_codec.o               .ac97_proc.o.cmd
.ac97_codec.o.cmd          ak4531_codec.c
ac97_id.h                  built-in.o
ac97_local.h               .built-in.o.cmd
ac97_patch.c               Makefile
ac97_patch.c.orig          snd-ac97-codec.ko
ac97_patch.c.rej           .snd-ac97-codec.ko.cmd
ac97_patch.h               snd-ac97-codec.mod.c
ac97_patch.o               snd-ac97-codec.mod.o
.ac97_patch.o.cmd          .snd-ac97-codec.mod.o.cmd
ac97_pcm.c                 snd-ac97-codec.o
ac97_pcm.o                 .snd-ac97-codec.o.cmd



> This means that snd-pxa2xx-pcm.ko has not been
> inserted. It's built from
> pxa2xx-pcm.c

I cant even insmod snd-pxa2xx-pcm. It gives me the
following error. 

[root@ARMCore sound1]$ insmod snd-pxa2xx-pcm.ko
snd_pxa2xx_pcm: Unknown symbol dma_mmap_writecombine
insmod: error inserting 'snd-pxa2xx-pcm.ko': -1
Unknown symbol in module
 
 
> This relates to sound/arm/pxa2xx-ac97.c
> 
> You should have the following rules in
> sound/arm/Makefile:-
> 
> snd-pxa2xx-pcm-objs := pxa2xx-pcm.o
> snd-pxa2xx-ac97-objs := pxa2xx-ac97.o
> 
> obj-$(CONFIG_SND_PXA2xx_PCM) += snd-pxa2xx-pcm.o
> obj-$(CONFIG_SND_PXA2xx_AC97) += snd-pxa2xx-ac97.o
> 
> and the following options in sound/arm/Kconfig
> 
> config SND_PXA2xx_AC97
> 	tristate "AC97 driver for the Intel PXA2xx chip"
> 	depends on ARCH_PXA && SND
> 	select SND_PXA2xx_PCM
> 	select SND_AC97_CODEC
> 	help
> 	  Say Y or M if you want to support any AC97 codec
> attached to
> 	  the PXA2xx AC97 interface.
> 
> config SND_PXA2xx_PCM
> 	tristate
> 	select SND_PCM
> 	help
> 	  Generic PCM module for PXA2xx
> 
I really got all those above in Makefile and Kconfig.
Serious, I have checked a thousand times before make
modules modules_install.

Regards,
Raymond

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Liam Girdwood]

On Fri, 2005-08-19 at 06:51 -0700, Chow Raymond wrote:

> 
> > This means that snd-pxa2xx-pcm.ko has not been
> > inserted. It's built from
> > pxa2xx-pcm.c
> 
> I cant even insmod snd-pxa2xx-pcm. It gives me the
> following error. 
> 
> [root@ARMCore sound1]$ insmod snd-pxa2xx-pcm.ko
> snd_pxa2xx_pcm: Unknown symbol dma_mmap_writecombine
> insmod: error inserting 'snd-pxa2xx-pcm.ko': -1
> Unknown symbol in module
>  

It looks like your arch/arm and include/asm/ also has to be back ported
from 2.6.12. I've now read Clemens reply and also believe it's better to
port your machine from 2.6.7 to 2.6.12.

Liam




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

I also wish to port from 2.6.7 to 2.6.12. However,
Compulab only supports till 2.6.7. I can't build
2.6.12 kernel to run on Compulab's board.

Raymond

--- Liam Girdwood <liam.girdwood@wolfsonmicro.com>
wrote:

> On Fri, 2005-08-19 at 06:51 -0700, Chow Raymond
> wrote:
> 
> > 
> > > This means that snd-pxa2xx-pcm.ko has not been
> > > inserted. It's built from
> > > pxa2xx-pcm.c
> > 
> > I cant even insmod snd-pxa2xx-pcm. It gives me the
> > following error. 
> > 
> > [root@ARMCore sound1]$ insmod snd-pxa2xx-pcm.ko
> > snd_pxa2xx_pcm: Unknown symbol
> dma_mmap_writecombine
> > insmod: error inserting 'snd-pxa2xx-pcm.ko': -1
> > Unknown symbol in module
> >  
> 
> It looks like your arch/arm and include/asm/ also
> has to be back ported
> from 2.6.12. I've now read Clemens reply and also
> believe it's better to
> port your machine from 2.6.7 to 2.6.12.
> 
> Liam
> 
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is Sponsored by the Better Software
> Conference & EXPO
> September 19-22, 2005 * San Francisco, CA *
> Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects
> & Teams * Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Lee Revell]

On Mon, 2005-08-22 at 00:06 -0700, Chow Raymond wrote:
> I also wish to port from 2.6.7 to 2.6.12. However,
> Compulab only supports till 2.6.7. I can't build
> 2.6.12 kernel to run on Compulab's board. 

Do you mean the vendor won't provide support for anything but 2.6.7, or
that 2.6.12 literally will not run on the board?

If it's the former then ask your support rep how to get a new ALSA to
work with it.  If it's the latter then report the bug to the kernel
people.

Lee





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Takashi Iwai]

At Mon, 22 Aug 2005 23:57:26 -0400,
Lee Revell wrote:
> 
> On Mon, 2005-08-22 at 00:06 -0700, Chow Raymond wrote:
> > I also wish to port from 2.6.7 to 2.6.12. However,
> > Compulab only supports till 2.6.7. I can't build
> > 2.6.12 kernel to run on Compulab's board. 
> 
> Do you mean the vendor won't provide support for anything but 2.6.7, or
> that 2.6.12 literally will not run on the board?
> 
> If it's the former then ask your support rep how to get a new ALSA to
> work with it.  If it's the latter then report the bug to the kernel
> people.

IIRC, some of the core part regarding DMA on ARM was added recently,
which is used by pxa2xx driver.  You can backport that code, though.


Takashi


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

Takashi,

Would appreciate if you can mention the file that has
changes.

Thanks

Regards
--- Takashi Iwai <tiwai@suse.de> wrote:

> At Mon, 22 Aug 2005 23:57:26 -0400,
> Lee Revell wrote:
> > 
> > On Mon, 2005-08-22 at 00:06 -0700, Chow Raymond
> wrote:
> > > I also wish to port from 2.6.7 to 2.6.12.
> However,
> > > Compulab only supports till 2.6.7. I can't build
> > > 2.6.12 kernel to run on Compulab's board. 
> > 
> > Do you mean the vendor won't provide support for
> anything but 2.6.7, or
> > that 2.6.12 literally will not run on the board?
> > 
> > If it's the former then ask your support rep how
> to get a new ALSA to
> > work with it.  If it's the latter then report the
> bug to the kernel
> > people.
> 
> IIRC, some of the core part regarding DMA on ARM was
> added recently,
> which is used by pxa2xx driver.  You can backport
> that code, though.
> 
> 
> Takashi
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

The problem that I encountered.

MODPOST
*** Warning: "dma_mmap_writecombine"
[sound/arm/snd-pxa2xx-pcm.ko] undefined!
*** Warning: "pxa_set_cken"
[sound/arm/snd-pxa2xx-ac97.ko] undefined!
*** Warning: "snd_ac97_get_short_name"
[sound/arm/snd-pxa2xx-ac97.ko] undefined!

Currently im tackling the warning for
dma_mmap_writecombine. I realised that the above
warning message is due to dma_mmap_writecombine symbol
is not exported. Found out it is true when i edit
arch/arm/mm/consistent.c. There is no
dma_mmap_writecombine function. Found out that struct
dma_mmap is not defined too. Thus, I back port that
particular file based on kernel 2.6.12. I do not face
the above warning after make modules. However, when i
try to insmod, i've encounter this.

Unable to handle kernel NULL pointer dereference at
virtual address 00000000
[00000000] *pgd=a34f3011, *pte=00000000,
*ppte=00000000
Internal error: Oops: 0 [#1]
Modules linked in: snd_pxa2xx_pcm snd_ac97_codec
snd_pcm_oss snd_mixer_oss snd_e
CPU: 0
PC is at 0x0
LR is at sys_init_module+0x1a4/0x308
pc : [<00000000>]    lr : [<c0051e34>]    Not tainted
sp : c35d3f88  ip : 60000013  fp : c35d3fa4
r10: befffe47  r9 : c35d2000  r8 : c0026364
r7 : 00000000  r6 : c022123c  r5 : bf0540a0  r4 :
c0221254
r3 : 60000013  r2 : bf0540a0  r1 : 00000001  r0 :
00000000
Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  Segment
user
Control: 397F  Table: A3470000  DAC: 00000015
Process insmod (pid: 517, stack limit = 0xc35d20fc)
Stack: (0xc35d3f88 to 0xc35d4000)
3f80:                   0000909c 00000002 befffd54
00000080 00000000 c35d3fa8
3fa0: c00261e0 c0051c9c 0000909c c002e3d8 40137008
00027f9b 00012008 00027f9b
3fc0: 0000909c 00000002 befffd54 00012008 00000002
00009210 befffe47 befffd30
3fe0: 400e9010 befffcf8 00008fec 400e901c 60000010
40137008 00000000 00000000
Backtrace:
[<c0051c90>] (sys_init_module+0x0/0x308) from
[<c00261e0>] (ret_fast_syscall+0x)
 r7 = 00000080  r6 = BEFFFD54  r5 = 00000002  r4 =
0000909C
Code: bad PC value.a
Segmentation fault


Segmentation fault? I just added a structure and a
function and i do not expect a segmentation fault.
Therefore i would like to know,

1) What does remap_pfn_range function does? 
2) How does remap_pfn_range different compare to
remap_page_range? 

I suspect is due to those functions. Hope you guys can
tell me. Thanks in advance.

Regards,
Raymond

--- Takashi Iwai <tiwai@suse.de> wrote:

> At Mon, 22 Aug 2005 23:57:26 -0400,
> Lee Revell wrote:
> > 
> > On Mon, 2005-08-22 at 00:06 -0700, Chow Raymond
> wrote:
> > > I also wish to port from 2.6.7 to 2.6.12.
> However,
> > > Compulab only supports till 2.6.7. I can't build
> > > 2.6.12 kernel to run on Compulab's board. 
> > 
> > Do you mean the vendor won't provide support for
> anything but 2.6.7, or
> > that 2.6.12 literally will not run on the board?
> > 
> > If it's the former then ask your support rep how
> to get a new ALSA to
> > work with it.  If it's the latter then report the
> bug to the kernel
> > people.
> 
> IIRC, some of the core part regarding DMA on ARM was
> added recently,
> which is used by pxa2xx driver.  You can backport
> that code, though.
> 
> 
> Takashi
> 



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Takashi Iwai]

At Wed, 24 Aug 2005 03:32:51 -0700 (PDT),
Chow Raymond wrote:
> 
> The problem that I encountered.
> 
> MODPOST
> *** Warning: "dma_mmap_writecombine"
> [sound/arm/snd-pxa2xx-pcm.ko] undefined!
> *** Warning: "pxa_set_cken"
> [sound/arm/snd-pxa2xx-ac97.ko] undefined!
> *** Warning: "snd_ac97_get_short_name"
> [sound/arm/snd-pxa2xx-ac97.ko] undefined!
> 
> Currently im tackling the warning for
> dma_mmap_writecombine. I realised that the above
> warning message is due to dma_mmap_writecombine symbol
> is not exported. Found out it is true when i edit
> arch/arm/mm/consistent.c. There is no
> dma_mmap_writecombine function. Found out that struct
> dma_mmap is not defined too. Thus, I back port that
> particular file based on kernel 2.6.12. I do not face
> the above warning after make modules. However, when i
> try to insmod, i've encounter this.
> 
> Unable to handle kernel NULL pointer dereference at
> virtual address 00000000
> [00000000] *pgd=a34f3011, *pte=00000000,
> *ppte=00000000
> Internal error: Oops: 0 [#1]
> Modules linked in: snd_pxa2xx_pcm snd_ac97_codec
> snd_pcm_oss snd_mixer_oss snd_e
> CPU: 0
> PC is at 0x0
> LR is at sys_init_module+0x1a4/0x308
> pc : [<00000000>]    lr : [<c0051e34>]    Not tainted
> sp : c35d3f88  ip : 60000013  fp : c35d3fa4
> r10: befffe47  r9 : c35d2000  r8 : c0026364
> r7 : 00000000  r6 : c022123c  r5 : bf0540a0  r4 :
> c0221254
> r3 : 60000013  r2 : bf0540a0  r1 : 00000001  r0 :
> 00000000
> Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  Segment
> user
> Control: 397F  Table: A3470000  DAC: 00000015
> Process insmod (pid: 517, stack limit = 0xc35d20fc)
> Stack: (0xc35d3f88 to 0xc35d4000)
> 3f80:                   0000909c 00000002 befffd54
> 00000080 00000000 c35d3fa8
> 3fa0: c00261e0 c0051c9c 0000909c c002e3d8 40137008
> 00027f9b 00012008 00027f9b
> 3fc0: 0000909c 00000002 befffd54 00012008 00000002
> 00009210 befffe47 befffd30
> 3fe0: 400e9010 befffcf8 00008fec 400e901c 60000010
> 40137008 00000000 00000000
> Backtrace:
> [<c0051c90>] (sys_init_module+0x0/0x308) from
> [<c00261e0>] (ret_fast_syscall+0x)
>  r7 = 00000080  r6 = BEFFFD54  r5 = 00000002  r4 =
> 0000909C
> Code: bad PC value.a
> Segmentation fault
> 
> 
> Segmentation fault? I just added a structure and a
> function and i do not expect a segmentation fault.
> Therefore i would like to know,
> 
> 1) What does remap_pfn_range function does? 

It's a more generic replacement of remap_page_range().

> 2) How does remap_pfn_range different compare to
> remap_page_range? 

The start argument is shifted in page size.


But, what is the exact reason that you cannot use newer kernel
version?


Takashi


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

The exact reason is Compulab only supports till 2.6.7.
They only have 2.6.7 patch in order to support their
board. 


> > 2) How does remap_pfn_range different compare to
> > remap_page_range? 
> 
> The start argument is shifted in page size.
> 

So does it mean that this might probably cause the
segmentation fault?

Regards,
Raymond


		
__________________________________ 
Yahoo! Mail for Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Clemens Ladisch]

Chow Raymond wrote:
> The exact reason is Compulab only supports till 2.6.7.
> They only have 2.6.7 patch in order to support their
> board.

Couldn't that patch be ported to 2.6.12?  Is it available somewhere?


Regards,
Clemens



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Compulab sound device

[Chow Raymond]

The patch can be ported but i cant build the kernel
image. It tells me there's an error and i got to back
port all the 2.6.7 header files to support the patches
(which is more tedious for me to do). The patch is
available at Compulab's website

Raymond

--- Clemens Ladisch <clemens@ladisch.de> wrote:

> Chow Raymond wrote:
> > The exact reason is Compulab only supports till
> 2.6.7.
> > They only have 2.6.7 patch in order to support
> their
> > board.
> 
> Couldn't that patch be ported to 2.6.12?  Is it
> available somewhere?
> 
> 
> Regards,
> Clemens
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is Sponsored by the Better Software
> Conference & EXPO
> September 19-22, 2005 * San Francisco, CA *
> Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects
> & Teams * Testing & QA
> Security * Process Improvement & Measurement *
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

RE: Alsa-lib problem

[Nambiar, Anil]

Hi,
 Thanks for the reply. I tried running speaker-test with those parameters
and it gave this dump.
speaker-test 0.0.8
Playback device is plughw:0,0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM plughw:0,0
Playback open error: -2,No such file or directory
speaker-test: conf.c: 3095: snd_config_update_free: Assertion `update->count
> 0
 && update->finfo' failed.
Aborted

I'll create a config file, but not sure if that would work. I tried using
strace, but it gives some syscall err!!

Thanks,
AniL


-----Original Message-----
From: James Courtier-Dutton [mailto:James@superbug.demon.co.uk] 
Sent: Tuesday, August 09, 2005 3:19 PM
To: Nambiar, Anil
Cc: 'alsa-devel@lists.sourceforge.net'
Subject: Re: [Alsa-devel] Alsa-lib problem

Nambiar, Anil wrote:
> Hi,
> 
>             I am developing ALSA based sound driver for our arm based soc.
> The driver is built as part of the kernel rather than as a loadable
module.
> If I run a simple wave player which has OSS based interface, it works
fine.
> Even mplayer works fine in OSS emulation mode. But if I run any native
alsa
> based player it gives error opening the device. For eg: running 'aplay -D
> default demo.wav" give the following error: 
> 
> ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
> 
> aplay: main:533: audio open error: No such file or directory
> 

You probably do not have a "default" device defined for your card due to 
the lack of a config file.
But, in order to test it, even though you don't have a config file, try
speaker-test -c2 -Dplughw:0,0

if that works, all you then need is a config file for your card.
cat /proc/asound/cards  and note down whatever is in the [....    ] bit.
Here I get:
0 [Audigy2        ]: Audigy2 - Audigy 4 PRO [SB0380]
                      Audigy 4 PRO [SB0380] (rev.4, serial:0x20071102) 
at 0x9800, irq 20


So I have an "Audigy2" file in /usr/share/alsa/cards
You will need to create one for your card.




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

RE: Alsa-lib problem

[Nambiar, Anil]

I was able to get it running. Had to export
ALSA_CONFIG_PATH=/etc/alsa/alsa.conf. It would be nice if this is documented
somewhere. 


Thanks,
AniL

-----Original Message-----
From: James Courtier-Dutton [mailto:James@superbug.demon.co.uk] 
Sent: Tuesday, August 09, 2005 3:19 PM
To: Nambiar, Anil
Cc: 'alsa-devel@lists.sourceforge.net'
Subject: Re: [Alsa-devel] Alsa-lib problem

Nambiar, Anil wrote:
> Hi,
> 
>             I am developing ALSA based sound driver for our arm based soc.
> The driver is built as part of the kernel rather than as a loadable
module.
> If I run a simple wave player which has OSS based interface, it works
fine.
> Even mplayer works fine in OSS emulation mode. But if I run any native
alsa
> based player it gives error opening the device. For eg: running 'aplay -D
> default demo.wav" give the following error: 
> 
> ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
> 
> aplay: main:533: audio open error: No such file or directory
> 

You probably do not have a "default" device defined for your card due to 
the lack of a config file.
But, in order to test it, even though you don't have a config file, try
speaker-test -c2 -Dplughw:0,0

if that works, all you then need is a config file for your card.
cat /proc/asound/cards  and note down whatever is in the [....    ] bit.
Here I get:
0 [Audigy2        ]: Audigy2 - Audigy 4 PRO [SB0380]
                      Audigy 4 PRO [SB0380] (rev.4, serial:0x20071102) 
at 0x9800, irq 20


So I have an "Audigy2" file in /usr/share/alsa/cards
You will need to create one for your card.




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf