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

[alsa-devel] [PATCH] Device ID for Macbook sound card
by Jiang zhe 10 Jan '08

10 Jan '08

Hi, Please refer to the [0003680] on bugtracking system. The user found that "model=mbp3" works and provided the ID. --- alsa-driver-hg20080110/alsa-kernel/pci/hda/patch_realtek.c 2008-01-09 09:00:15.000000000 +0800 +++ b/alsa-kernel/pci/hda/patch_realtek.c 2008-01-10 16:07:20.000000000 +0800 @@ -6122,6 +6122,7 @@ static int patch_alc882(struct hda_codec case 0x106b1000: /* iMac 24 */ board_config = ALC885_IMAC24; break; + case 0x106b00a1: /* Macbook */ case 0x106b2c00: /* Macbook Pro rev3 */ board_config = ALC885_MBP3; break;

2 1

[alsa-devel] [PATCH] hda: STAC9228 VT fixes
by Matthew Ranostay 10 Jan '08

10 Jan '08

Moved 2 systems PCI_QUIRK values to STAC_DELL_BIOS. Also the second front HP jack is incorrect defined in the BIOS VT's for some laptops, this patch corrects this. --- Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> diff -r d09f88bf00e8 pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Wed Jan 09 12:30:20 2008 +0100 +++ b/pci/hda/patch_sigmatel.c Wed Jan 09 12:34:59 2008 -0500 @@ -1428,13 +1428,13 @@ static struct snd_pci_quirk stac927x_cfg SND_PCI_QUIRK(PCI_VENDOR_ID_INTEL, 0x2002, "Intel D965", STAC_D965_3ST), SND_PCI_QUIRK(PCI_VENDOR_ID_INTEL, 0x2001, "Intel D965", STAC_D965_3ST), /* Dell 3 stack systems */ - SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01f3, "Dell Inspiron 1420", STAC_DELL_3ST), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01f7, "Dell XPS M1730", STAC_DELL_3ST), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01dd, "Dell Dimension E520", STAC_DELL_3ST), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01ed, "Dell ", STAC_DELL_3ST), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01f4, "Dell ", STAC_DELL_3ST), - SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0227, "Dell Vostro 1400 ", STAC_DELL_3ST), /* Dell 3 stack systems with verb table in BIOS */ + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x01f3, "Dell Inspiron 1420", STAC_DELL_BIOS), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0227, "Dell Vostro 1400 ", STAC_DELL_BIOS), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x022f, "Dell ", STAC_DELL_BIOS), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x022e, "Dell ", STAC_DELL_BIOS), SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0242, "Dell ", STAC_DELL_BIOS), @@ -3332,6 +3332,8 @@ static int patch_stac927x(struct hda_cod spec->mixer = stac927x_mixer; break; case STAC_DELL_BIOS: + /* correct the front output jack as a hp out */ + stac92xx_set_config_reg(codec, 0x0f, 0x02270110); /* correct the front input jack as a mic */ stac92xx_set_config_reg(codec, 0x0e, 0x02a79130); /* fallthru */

2 1

[alsa-devel] can not access the alsa driver
by Ning Zhang 10 Jan '08

10 Jan '08

Dear all, I wrote an alsa device driver for my arm_based platform. Then I cross compiled the alsa-lib-1.0.15, and build an application (static) with the lib. I build the driver in the kernel, so after the kernel booted, I can get these information: # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC). cat /proc/asound/devices 0: [ 0] : control 16: [ 0- 0]: digital audio playback 24: [ 0- 0]: digital audio capture 33: : timer # cat /proc/asound/cards 0 [XYZ ]: XYZ - ARM XYZ at 0xc485e000 0xc4870000 irq 57 ( I did not found /dev/snd or /dev/dsp ) But when I run the application, I got these errors: # /tmp/pcm_play_arm_s default ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default Playback open error: No such file or directory I googled the Internet, and add two files manually : # cat /etc/alsa/alsa.conf pcm.default{ type hw card 0 } # cat ~/.asoundrc pcm.default { type hw card 0 } But I still can not let the application to access the pcm device, this time I got the following information: # /tmp/pcm_play_arm_s default cannot open audio device default (No such file or directory) Here are my questions: 1, When we install the alsa-lib, we can get some libs, besides those, do we also get some config files according to the local linux environment and alsa-lib will use these config files to access the real driver? If that, how can I install the alsa-lib to a embedded platform directly or what config files should I port to embedded platform? 2, Must I edit ~/.asoundrc and /etc/alsa/alsa.conf ? In my situation, what should I do ? Is somebody so kind can give me a simple template? Because I am a newbie in alsa world, I must make some mistakes, so I am lookinf forward to your advice. Thanks in advance for your help. David.

4 4

[alsa-devel] [w/ formating this time] Any alsa cards with PLD/FPGA? (similar to Gadget Labs)
by mazarick＠bellsouth.net 09 Jan '08

09 Jan '08

[that's what I get for sending mail from a lame webmail browser] First, I wanted to report that there is good progress being made on developing an alsa linux driver for the Gadget Labs card. It's not 'done yet' but there is steady progress being made. As was mentioned earlier, any interested developers, testers, or other parties are welcomed to join in the discussions or coding, however the mailing list will go 'private' in the next week (to eliminate the fear of spam and email address havesting). The archive is busted right now; not sure if/when it will be fixed. We're using the mailing list for any interested parties, and are making project members of people who would like to contribute to the effort. http://sourceforge.net/projects/wavepro-driver/ Since the small team has a variety of experience and familiarity with writing drivers, an experimental 'branch' of the SVN repo has been set up to place reference material (like existing, known good alsa drivers, known good windows code, etc) and eventually, the skeleton of what is to be done next. The 'good stuff' lives in the trunk and there will be a merge at an appropriate time in the future (when 'soups done'). The heart of the Gadget Labs card is an Altera PLD, and it has a bus interface chip PLX9052 (and some on-board memory, DAC/ADC, etc). We are planning on putting the alsa code for the Delta 1010 in the branch because it is the most similar from a user perspective. However, it uses a vlsi ICE chip to do the job, and it doesn't have to have the PLD/FPGA code downloaded each time it is initialized. If there is a known good driver that can/should have it's code used as a reference, please let us know via this list. A good technical reference to us would be cards that have to download PLD/FPGA as part of initialization and/or cards that use the PLX9052. There are a couple of wireless modem cards, etc with linux drivers that fit the description, but it is unknown if there is already an alsa driver for an existing card that would be good reference code. As you are aware, this effort is not what repos are normally used for, but it was felt that having this would allow people at a variety of different skill levels to quickly pick up on what is trying to be accomplished without having to hunt all over the net, read a bunch of different emails, etc in order to make a contribution. -Mike Mazarick

1 0

[alsa-devel] Any alsa cards with PLD/FPGA? (similar to Gadget Labs)
by mazarick＠bellsouth.net 09 Jan '08

09 Jan '08

First, I wanted to report that there is good progress being made on developing an alsa linux driver for the Gadget Labs card. It's not 'done yet' but there is steady progress being made. As was mentioned earlier, any interested developers, testers, or other parties are welcomed to join in the discussions or coding, however the mailing list will go 'private' in the next week (to eliminate the fear of spam and email address havesting). The archive is busted right now; not sure if/when it will be fixed. We're using the mailing list for any interested parties, and are making project members of people who would like to contribute to the effort. http://sourceforge.net/projects/wavepro-driver/ Since the small team has a variety of experience and familiarity with writing drivers, an experimental 'branch' of the SVN repo has been set up to place reference material (like existing, known good alsa drivers, known good windows code, etc) and eventually, the skeleton of what is to be done next. The 'good stuff' lives in the trunk and there will be a merge at an appropriate time in the future (when 'soups done'). The heart of the Gadget Labs card is an Altera PLD, and it has a bus interface chip PLX9052 (and some on-board memory, DAC/ADC, etc). We are planning on putting the alsa code for the Delta 1010 in the branch because it is the most similar from a user perspective. However, it uses a vlsi ICE chip to do the job, and it doesn't have to have the PLD/FPGA code downloaded each time it is initialized. If there is a known good driver that can/should have it's code used as a reference, please let us know via this list. A good technical reference to us would be cards that have to download PLD/FPGA as part of initialization and/or cards that use the PLX9052. There are a couple of wireless modem cards, etc with linux drivers that fit the description, but it is unknown if there is already an alsa driver for an existing card that would be good reference code. As you are aware, this effort is not what repos are normally used for, but it was felt that having this would allow people at a variety of different skill levels to quickly pick up on what is trying to be accomplished without having to hunt all over the net, read a bunch of different emails, etc in order to make a contribution. -Mike Mazarick

1 0

Re: [alsa-devel] snd-hda-intel support for SPDIF-in wiht vt1708 card?
by Takashi Iwai 09 Jan '08

09 Jan '08

At Wed, 09 Jan 2008 02:06:53 -0800, John Stile wrote: > > On Wed, 2008-01-09 at 08:39 +0100, Takashi Iwai wrote: > > Thanks. > You are welcome. Thank you for your patience. > > > You can put alsa-driver and alsa-kernel in the same directory level. > > Make in alsa-driver will create a symlink automatically from > > ../alsa-kernel. > My procedure is changed: > cd /usr/src/ > rm -rf alsa-lib > rm -rf alsa-utils > rm -rf alsa-driver > rm -rf alsa-driver > hg clone http://hg-mirror.alsa-project.org/alsa-lib alsa-lib > hg clone http://hg-mirror.alsa-project.org/alsa-utils alsa-utils > hg clone http://hg-mirror.alsa-project.org/alsa-kernel alsa-kernel > hg clone http://hg-mirror.alsa-project.org/alsa-driver alsa-driver > pushd alsa-lib > ./hgcompile && make install To be sure: you are using 32bit version, right? For 64bit, the library path might be /usr/lib64, instead of /usr/lib (depending on distro). > popd > pushd alsa-utils > ./hgcompile && make install > popd > cd alsa-driver > ./hgcompile && make install > popd > # Build completed successfully. Yay. > /usr/sbin/alsaconf > # Chose 'hda-intel VIA Technologies, Inc. VIA High Definition Audio Controller" > /usr/bin/alsamixer -Vall So far so good. > > IEC958 shows > ┌──┐ > │MM│ > L└──┘R > CAPTUR > > There are 2 'CAPTURE' columns where I maxed levels. > 'Input So' is set to 'Stereo M' Attach the generated file via "alsactl -f somefile store" instead of ascii art. This contains the all mixer information. > Play tests all work > songs="/usr/share/sounds/alsa/Front_Right.wav > /usr/share/sounds/alsa/Rear_Right.wav > /usr/share/sounds/alsa/Rear_Left.wav > /usr/share/sounds/alsa/Rear_Center.wav > /usr/share/sounds/alsa/Front_Left.wav > /usr/share/sounds/alsa/Noise.wav > /usr/share/sounds/alsa/Side_Right.wav > /usr/share/sounds/alsa/Side_Left.wav > /usr/share/sounds/alsa/Front_Center.wav" > echo "not setting hardware" > for song in $songs; > do > aplay $song > done > > arecord -l > **** List of CAPTURE Hardware Devices **** > card 0: VT82xx [HDA VIA VT82xx], device 0: VT1708 Analog [VT1708 Analog] > Subdevices: 2/2 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > card 0: VT82xx [HDA VIA VT82xx], device 1: VT1708 Digital [VT1708 > Digital] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > One digital device is listed with: arecord -L > iec958:CARD=VT82xx,DEV=0 > HDA VIA VT82xx, VT1708 Digital > IEC958 (S/PDIF) Digital Audio Output > null > Discard all samples (playback) or generate zero samples (capture) > > Arecord without specifying -D makes a pulsing screech. > arecord -d 10 -f dat -t wav |aplay > > This records 10 seconds and ends in an I/O error: > arecord -D hw:0,1 -d 10 -f dat -t wav |aplay > > Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo > Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo > arecord: pcm_read:1324: read error: Input/output error > > All these record tests fail. > arecord -D cards.pcm.Digital -d 10 -f dat -t wav |aplay > ALSA lib pcm.c:2121:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.Digital > arecord: main:540: audio open error: No such file or directory > aplay: playback:1995: read error > > arecord -D cards.pcm.iec958 -d 10 -f dat -t wav |aplay > > ALSA lib dlmisc.c:118:(snd_dlsym_verify) unable to verify version for symbol _snd_pcm_hook_ctl_elems_install > ALSA lib pcm_hooks.c:392:(snd_pcm_hook_add_conf) symbol _snd_pcm_hook_ctl_elems_install is not defined inside (null) > arecord: main:540: audio open error: No such device or address > aplay: playback:1995: read error > > arecord -D hwplug:0,1 -d 10 -f dat -t wav |aplay > > ALSA lib pcm.c:2121:(snd_pcm_open_noupdate) Unknown PCM hwplug:0,1 > arecord: main:540: audio open error: No such file or directory > aplay: playback:1995: read error It's a user error :) The usage below, -D plug:spdif, is correct, though. > arecord -D plug:spdif -d 10 -f dat -t wav |aplay > > ALSA lib dlmisc.c:118:(snd_dlsym_verify) unable to verify version for symbol _snd_pcm_hook_ctl_elems_install OK, this is a bug in the recent alsa-lib. I fixed it now on HG tree. Please update your alsa-lib repo (maybe better from hg.alsa-project.org). Takashi

2 1

[alsa-devel] snd_pcm_htimestamp & more PCM mmap timestamping in driver
by Jaroslav Kysela 09 Jan '08

09 Jan '08

Hi all, I just added snd_pcm_htimestamp() function to alsa-lib: int snd_pcm_htimestamp(snd_pcm_t *pcm, snd_pcm_uframes_t *avail, snd_htimestamp_t *tstamp); If you have any complaints, please, do now. Also, I would like to change SNDRV_PCM_TSTAMP_MMAP semantics to SNDRV_PCM_TSTAMP_ENABLE - when hw_ptr is updated in the driver, a timestamp would be always grabbed to ensure that we have always a valid timestamp & position pair. In current implementation, if an application updates hw_ptr in driver (using for example PCM delay ioctl), timestamp grabbed in the interrupt handler won't be associated with any real ring buffer position which makes things complicated and not too much abstract. Opinions? Jaroslav ----- Jaroslav Kysela <perex(a)perex.cz> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.

2 1

[alsa-devel] [PATCH] hda: 92HD71BXX Mono Mute Support
by Matthew Ranostay 09 Jan '08

09 Jan '08

Added a mono output mute mixer for the 92hd71bxx family of codecs, this also removes the need for the mono out node to explicitly unmuted in the core init. --- Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> diff -r b3915b3a8a22 pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Tue Jan 08 12:33:19 2008 +0100 +++ b/pci/hda/patch_sigmatel.c Tue Jan 08 17:58:12 2008 -0500 @@ -534,8 +534,6 @@ static struct hda_verb stac92hd71bxx_cor { 0x0a, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, { 0x0d, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, { 0x0f, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, - /* unmute mono out node */ - { 0x14, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, }; static struct hda_verb stac92hd71bxx_analog_core_init[] = { @@ -553,8 +551,6 @@ static struct hda_verb stac92hd71bxx_ana { 0x0a, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, { 0x0d, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, { 0x0f, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, - /* unmute mono out node */ - { 0x14, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, {} }; @@ -714,6 +710,8 @@ static struct snd_kcontrol_new stac92hd7 HDA_CODEC_MUTE("Analog Loopback 1", 0x17, 0x3, HDA_INPUT), HDA_CODEC_MUTE("Analog Loopback 2", 0x17, 0x4, HDA_INPUT), + + HDA_CODEC_MUTE_MONO("Mono Playback Switch", 0x14, 0x1, 0, HDA_INPUT), { } /* end */ }; @@ -728,6 +726,8 @@ static struct snd_kcontrol_new stac92hd7 HDA_CODEC_VOLUME_IDX("Capture Volume", 0x1, 0x1d, 0x0, HDA_OUTPUT), HDA_CODEC_MUTE_IDX("Capture Switch", 0x1, 0x1d, 0x0, HDA_OUTPUT), HDA_CODEC_VOLUME_IDX("Capture Mux Volume", 0x1, 0x1b, 0x0, HDA_OUTPUT), + + HDA_CODEC_MUTE_MONO("Mono Playback Switch", 0x14, 0x1, 0, HDA_INPUT), { } /* end */ };

2 1

[alsa-devel] No sound over HDMI on HDA-Intel - HDA ATI HDMI
by Georgi Chorbadzhiyski 09 Jan '08

09 Jan '08

Hi, I have an Asus MB with integrated ATI X1200 audio controller connected over HDMI to an LCD TV. intel-hda driver correctly identifies and drives the card, but I get no sound over HDMI only over the standard stereo output jack. I've unmuted iec958 control on the HDMI card. I'm testing the card like this: root@browser:~# aplay -D plughw:1,0 test.wav Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo No sound. root@browser:~# aplay -D plughw:0,0 test.wav Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo Sound is ok. Is there some patches that I could try to get the HDMI output working? Similar reports: http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg590477.html http://www.redhat.com/archives/rhl-list/2007-November/msg00372.html aplay -l **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 0: ATI HDMI [ATI HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 /proc/asound/cards 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe8f4000 irq 16 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeae8000 irq 19 lspci 00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge 00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) 00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2) 00:07.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3) 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series] 01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) lspci -vv 01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller Subsystem: ASUSTeK Computer Inc. Unknown device 8287 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 19 Region 0: Memory at feae8000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 dmesg: Linux version 2.6.24-rc6 (gf@gf) (gcc version 4.1.2) #32 SMP PREEMPT Tue Jan 8 19:08:44 EET 2008 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000037fb0000 (usable) BIOS-e820: 0000000037fb0000 - 0000000037fbe000 (ACPI data) BIOS-e820: 0000000037fbe000 - 0000000037fe0000 (ACPI NVS) BIOS-e820: 0000000037fe0000 - 0000000038000000 (reserved) BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) 895MB LOWMEM available. found SMP MP-table at 000ff780 Entering add_active_range(0, 0, 229296) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 229296 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0 -> 229296 On node 0 totalpages: 229296 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4064 pages, LIFO batch:0 Normal zone: 1759 pages used for memmap Normal zone: 223441 pages, LIFO batch:31 Movable zone: 0 pages used for memmap DMI present. ATI board detected. Disabling timer routing over 8254. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: ASUS Product ID: APIC at: 0xFEE00000 Processor #0 15:15 APIC version 16 I/O APIC #1 Version 33 at 0xFEC00000. Enabling APIC mode: Flat. Using 1 I/O APICs Processors: 1 Allocating PCI resources starting at 40000000 (gap: 38000000:c7f00000) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227505 Kernel command line: auto BOOT_IMAGE=Linux ro root=801 quiet mapped APIC to ffffb000 (fee00000) mapped IOAPIC to ffffa000 (fec00000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 2009.066 MHz processor. Console: colour dummy device 80x25 console [tty0] enabled Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 906216k/917184k available (1460k kernel code, 10468k reserved, 560k data, 172k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffba000 - 0xfffff000 ( 276 kB) vmalloc : 0xf8800000 - 0xfffb8000 ( 119 MB) lowmem : 0xc0000000 - 0xf7fb0000 ( 895 MB) .init : 0xc02ff000 - 0xc032a000 ( 172 kB) .data : 0xc026d14d - 0xc02f9154 ( 560 kB) .text : 0xc0100000 - 0xc026d14d (1460 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 4109.60 BogoMIPS (lpj=2054803) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000001d 00000000 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff ebd3fbff 00000000 00000410 00002001 00000000 0000001d 00000000 Compat vDSO mapped to ffffe000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 8k freed CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 02 Total of 1 processors activated (4109.60 BogoMIPS). ExtINT not setup in hardware but reported by MP table ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0 Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=4 Setting up standard PCI resources SCSI subsystem initialized libata version 3.00 loaded. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Transparent bridge - 0000:00:14.4 PCI: Using IRQ router default [1002/438d] at 0000:00:14.3 PCI->APIC IRQ transform: 0000:00:12.0[A] -> IRQ 22 PCI->APIC IRQ transform: 0000:00:13.0[A] -> IRQ 16 PCI->APIC IRQ transform: 0000:00:13.1[B] -> IRQ 17 PCI->APIC IRQ transform: 0000:00:13.2[C] -> IRQ 18 PCI->APIC IRQ transform: 0000:00:13.3[B] -> IRQ 17 PCI->APIC IRQ transform: 0000:00:13.4[C] -> IRQ 18 PCI->APIC IRQ transform: 0000:00:13.5[D] -> IRQ 19 PCI->APIC IRQ transform: 0000:00:14.1[A] -> IRQ 16 PCI->APIC IRQ transform: 0000:00:14.2[A] -> IRQ 16 PCI->APIC IRQ transform: 0000:01:05.0[A] -> IRQ 18 PCI->APIC IRQ transform: 0000:01:05.2[B] -> IRQ 19 PCI->APIC IRQ transform: 0000:03:00.0[A] -> IRQ 19 PCI: Bridge: 0000:00:01.0 IO window: e000-efff MEM window: fe900000-feafffff PREFETCH window: f0000000-f7ffffff PCI: Bridge: 0000:00:06.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:07.0 IO window: disabled. MEM window: feb00000-febfffff PREFETCH window: disabled. PCI: Bridge: 0000:00:14.4 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Setting latency timer of device 0000:00:06.0 to 64 PCI: Setting latency timer of device 0000:00:07.0 to 64 NET: Registered protocol family 2 Time: tsc clocksource has been installed. IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered io scheduler noop registered (default) Boot video device is 0000:01:05.0 vesafb: framebuffer at 0xf0000000, mapped to 0xf8800000, using 2000k, total 16384k vesafb: mode is 640x400x32, linelength=2560, pages=15 vesafb: protected mode interface info at c000:a034 vesafb: pmi: set display start = c00ca0be, set palette = c00ca17c vesafb: scrolling: redraw vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0 Console: switching to colour frame buffer device 80x25 fb0: VESA VGA frame buffer device Real Time Clock Driver v1.12ac Linux agpgart interface v0.102 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled PCI: Setting latency timer of device 0000:03:00.0 to 64 atl1 0000:03:00.0: version 2.0.7 ahci 0000:00:12.0: version 3.0 ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci ata1: SATA max UDMA/133 abar m1024@0xfe8ff800 port 0xfe8ff900 irq 22 ata2: SATA max UDMA/133 abar m1024@0xfe8ff800 port 0xfe8ff980 irq 22 ata3: SATA max UDMA/133 abar m1024@0xfe8ff800 port 0xfe8ffa00 irq 22 ata4: SATA max UDMA/133 abar m1024@0xfe8ff800 port 0xfe8ffa80 irq 22 ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7: ST380815AS, 3.AAD, max UDMA/133 ata2.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32) ata2.00: configured for UDMA/133 ata3: SATA link down (SStatus 0 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) scsi 1:0:0:0: Direct-Access ATA ST380815AS 3.AA PQ: 0 ANSI: 5 sd 1:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sd 1:0:0:0: [sda] Attached SCSI disk ehci_hcd 0000:00:13.5: EHCI Host Controller ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:13.5: debug port 1 ehci_hcd 0000:00:13.5: irq 19, io mem 0xfe8ff000 ehci_hcd 0000:00:13.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 10 ports detected ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver ohci_hcd 0000:00:13.0: OHCI Host Controller ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:13.0: irq 16, io mem 0xfe8fe000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ohci_hcd 0000:00:13.1: OHCI Host Controller ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3 ohci_hcd 0000:00:13.1: irq 17, io mem 0xfe8fd000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ohci_hcd 0000:00:13.2: OHCI Host Controller ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4 ohci_hcd 0000:00:13.2: irq 18, io mem 0xfe8fc000 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ohci_hcd 0000:00:13.3: OHCI Host Controller ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5 ohci_hcd 0000:00:13.3: irq 17, io mem 0xfe8fb000 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected usb 3-2: new low speed USB device using ohci_hcd and address 2 ohci_hcd 0000:00:13.4: OHCI Host Controller ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6 ohci_hcd 0000:00:13.4: irq 18, io mem 0xfe8fa000 usb 3-2: configuration #1 chosen from 1 choice usb usb6: configuration #1 chosen from 1 choice hub 6-0:1.0: USB hub found hub 6-0:1.0: 2 ports detected USB Universal Host Controller Interface driver v3.0 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.1/usb3/3-2/3-2:1.0/input/input0 input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.1-2 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC). input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 ALSA device list: #0: HDA ATI SB at 0xfe8f4000 irq 16 #1: HDA ATI HDMI at 0xfeae8000 irq 19 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 172k freed atl1 0000:03:00.0: eth0 link is up 100 Mbps full duplex -- Georgi Chorbadzhiyski http://georgi.unixsol.org/ - To unsubscribe from this list: send the line "unsubscribe alsa-devel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

2 2

Re: [alsa-devel] snd-hda-intel support for SPDIF-in wiht vt1708 card?
by forumjunk＠comcast.net 09 Jan '08

09 Jan '08

Ok, here's the current state of affairs... both the compilation and driver seem to work well now, though I haven't tested SPDIF yet. I don't know why both John Stile and I were getting ioctl errors, perhaps if it is still happening to him he can elucidate, but it isn't happening to me any more with the latest build. I obtained and built a clean mercurial clone this morning (07 Jan 08): %> cd /usr/src %> rm -rf alsa-driver %> hg clone http://hg-mirror.alsa-project.org/alsa-driver alsa-driver %> cd alsa-driver %> hg clone http://hg-mirror.alsa-project.org/alsa-kernel alsa-kernel %> hgcompile [...] compilation proceeds cleanly... %> make install %> alsaconf [...] select card and configure it via alsamixer Lo and belold, it all worked! I have a clean compilation and good response from aplay and other user space tools. I haven't applied any patches, and I haven't been able to test SPDIF input yet but I'm betting John Stile should be able to report that faster than I can get to it... Thank you very much for your help with this and for all of the work you and the ALSA team do! -- Darryl -------------- Original message ---------------------- From: Takashi Iwai <tiwai(a)suse.de> > At Wed, 02 Jan 2008 22:31:19 +0000, > Darryl House wrote: > > > > > > -------------- Original message ---------------------- > > [...] > > > > I'd like to get this card's spdif working. What else can I do to help? > > > > Although the driver loads, the user space tools can't use the card any > > > > more. Thank you. > > > > > > > Should I assume at this point no more work will be done on the > > > snd-hda-intel driver to fixing SPDIF-in for the vt1708 sound card? > > > Thank you for all your work so far. > > > > > > > I think it is a bit early to make that assumption. There isn't a lot > > of demand for this particular card, but it doesn't seem that it > > will take too much work to get it going again... after all, it did > > basically work before the last patch, and I am hoping that Takashi > > will find some time soon to address the issues. > > Hm, I see no obvious error in the patch. Are you sure that the latest > HG driver works properly if you don't apply the patch? > > Let's begin with that. > > > Takashi > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

3 7