No subject
Fri Aug 8 16:41:39 CEST 2008
if (board_config < 0 || board_config >= ALC882_MODEL_LAST) {
/* Pick up systems that don't supply PCI SSID */
switch (codec->subsystem_id) {
case 0x106b0c00: /* Mac Pro */
board_config = ALC885_MACPRO;
break;
case 0x106b1000: /* iMac 24 */
board_config = ALC885_IMAC24;
break;
case 0x106b00a1: /* Macbook (might be wrong - PCI SSID?) */
case 0x106b2c00: /* Macbook Pro rev3 */
case 0x106b3600: /* Macbook 3.1 */
board_config = ALC885_MBP3;
break;
default:
/* ALC889A is handled better as ALC888-compatible */
if (codec->revision_id == 0x100103) {
alc_free(codec);
return patch_alc883(codec);
}
printk(KERN_INFO "hda_codec: Unknown model for ALC882, "
"trying auto-probe from BIOS...\n");
board_config = ALC882_AUTO;
}
}
------------------------------
Message: 2
Date: Fri, 15 Aug 2008 16:15:45 -0700
From: "John L. Utz III" <john.utz at dmx.com>
Subject: [alsa-devel] alsa git: which version of ac97_codec.c am i
supposed to hxr?
To: "ALSA Developers" <alsa-devel at alsa-project.org>
Message-ID: <op.ufyawjke647oa9 at jutz-gnto64>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Hello All;
I feel confused by the presence of 2 different copies of ac97_codec.c:
jutz-gnto ~ # find . -name ac97_codec.c
./alsa-driver/pci/ac97/ac97_codec.c
./alsa-kmirror/pci/ac97/ac97_codec.c
worse yet,they are not in sync:
jutz-gnto ~ # diff -w ./alsa-driver/pci/ac97/ac97_codec.c
./alsa-kmirror/pci/ac97/ac97_codec.c
1d0
< #include "adriver.h"
38c37
< #include "../../alsa-kernel/pci/ac97/ac97_id.h"
---
> #include "ac97_id.h"
40c39
< #include "../../alsa-kernel/pci/ac97/ac97_patch.c"
---
> #include "ac97_patch.c"
1917d1915
< #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 0)
1929d1926
< #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 14)
1931d1927
< #endif
1953,1956d1948
< #else /* <= 2.6.0 */
< #define snd_ac97_dev_register NULL
< #define snd_ac97_dev_disconnect NULL
< #endif
Which of these am i supposed to use? am i supposed to change both of them
for some backward compatibility purpose?
tnx!
johnu
------------------------------
Message: 3
Date: Sat, 16 Aug 2008 06:27:02 +0000 (UTC)
From: Simon Tremblay <bidou at videotron.qc.ca>
Subject: [alsa-devel] Configure and use dmix with a new ASoC driver
To: alsa-devel at alsa-project.org
Message-ID: <loom.20080816T061550-625 at post.gmane.org>
Content-Type: text/plain; charset=us-ascii
Hi,
I don't know if there is something special I should do to be able to use dmix
with my new ASoC driver I made (TLV320AIC23b codec running on a AT91RM9200
board).
The problem is when I try to use dmix with aplay, it doesn't work and I got
this error message:
# aplay -v -D plug:dmix /media/usb0/tada.wav
aplay: main:545: audio open error: Operation not permitted
#
Listing of my /dev/snd:
# ls -al /dev/snd
drwxr-xr-x 2 root root 0 Jan 1 00:01 .
drwxr-xr-x 7 root root 0 Jan 1 00:01 ..
crw-rw---- 1 root audio 116, 0 Jan 1 00:01 controlC0
crw-rw---- 1 root audio 116, 16 Jan 1 00:01 pcmC0D0p
Notice I have a default /usr/share/alsa/alsa.conf file too. I'm running ALSA
1.0.15. Of course, it works well when I play a sound without the -D plug:dmix
parameter...
# aplay /media/usb0/tada.wav
at91-ssc:ssc_startup: SSC_SR=0x000004c3
armus_tlv320aic23b: pck1 started
asoc: aic23b <-> at91-ssc1 info:
asoc: rate mask 0x6fe
asoc: min ch 1 max ch 2
asoc: min rate 8000 max rate 96000
Playing WAVE '/media/usb0/tada.wav' : Signed 16 bit Little Endian, Rate 48000
Hz, Stereo
#
I tried to find some useful documentation about dmix but mainly it says that
when we have a recent version of ALSA, we don't need to configure it because
it's already done?
------------------------------
_______________________________________________
Alsa-devel mailing list
Alsa-devel at alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
End of Alsa-devel Digest, Vol 18, Issue 45
******************************************
More information about the Alsa-devel
mailing list