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

[alsa-devel] ESI reply!! (MAYA44 datasheet request)
by Piotr Makowski 22 Aug '07

22 Aug '07

Hi Piotr, thank you very much for your email. The data sheet and information you request does not exist in any format that we could provide and frankly, we are way too busy with our normal work to prepare something like that in a way that would be of general use and would resemble what you require in your request. I am well aware of the general request and I know the text you sent us pretty well ... I have seen it many times before in various versions, usually copied via cut & paste and sent to us in one way or another ... and actually I am a bit tired of it. Unfortunatly we believe that the text and the way the request is sent to us is not really useful and not tailored at all to the special requirements that are common in this industry (pro audio / higher level sound card manufacturers) and that make this industry very different from your auverage computer component manufacturer. It's my personal experience, following the ALSA developer community for years, that this sort of basic cultural understanding is only slowly changing step-by-step but at a much slower pace than it could happen. Unfortunatly the majority of ALSA developers still seem to be "computer guys" and not "music guys" ... causing all sorts of problems that won't help to resolve the culture crash between the different parties. Most "music" companies work in a different way than typical IT companies. Our business are much smaller, and time of every single employee is extremly critical for us. I guess this all may sound ignorant to you, but please understand that I know what I am talking about to a pretty good extent (you can actually look up my name on the ALSA site where I am listed under contributors - http://www.alsa-project.org/main/index.php/ALSA_contributors - so I have experience on both sides). Again, we are happy to be in contact with the individual developer who is actually doing the development. If you volunteer to do the development yourself and/or if you know someone who would do it, please inform me and we can go from there. Please don't get me wrong, I understand what you want and where you are coming from, but this direct contact with the developer is a basic requirement for us - sorry. Best regards, Claus Riethmueller Managing Director ESI Audiotechnik GmbH

2 2

[alsa-devel] include/mixer.h missing from doxygen
by Rolland Dudemaine 22 Aug '07

22 Aug '07

Hi, include/mixer.h seems to be missing from the doxygen input file list. Should be added to the INPUT list in doc/doxygen.cfg. Btw, I'm pretty new do ALSA, why is the Mixer interface marked legacy in a couple places ? Best Regards, --Rolland Dudemaine

2 1

[alsa-devel] unknown card info [snd-bt87x]
by Vincent Minder 22 Aug '07

22 Aug '07

Hello, After loading the snd-bt87x module on my Fedora 7 x86_64 box, here is what I found in the dmesg output: unknown card 0x878-0xbd11:0x1200, using default rate 32000 please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> The card is a rather old and cheap "PINNACLE systems - Studio PCTV rave" The chip on the board is from Conexant: CONEXANT Fusion 878A (chip markings: 25878-13, E32673.1, 0023 KOREA) The card standard is PAL B/G. I think this model supports only MONO audio. It has TV-in, Audio-out (mini jack), Composite-in, S-VIDEO-in. TV playback is working all right (tested with "kdetv" and "tvtime"). I have sound as long as I use the Audio-out connector and bridge it to my motherboard's integrated audio Line-in . However, I didn't manage to use the internal audio capabities of that board. So I have no clue about the "correct digital_rate". (I must admit I am not familiar with these technologies at all.) Here is the output of "arecord -l" regarding this card: $ arecord -l **** List of CAPTURE Hardware Devices **** (...) card 2: Bt878 [Brooktree Bt878], device 0: Bt87x Digital [Bt87x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Bt878 [Brooktree Bt878], device 1: Bt87x Analog [Bt87x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 I am using the stock Alsa package of Fedora 7 x86_64 (fully updated distribution): alsa-lib-1.0.14-1.fc7 I hope this report will be useful to you. Sincerely, Vincent Minder (Belgium)

2 1

[alsa-devel] [PATCH] fix cmi8788 config (was: Re: [alsa-cvslog] alsa-lib: cmi8788: add alsa-lib config)
by Thierry Vignaud 22 Aug '07

22 Aug '07

Clemens Ladisch <clemens(a)ladisch.de> writes: > changeset: 2314:3bf9c6dec8c8 > tag: tip > user: cladisch > date: Wed Aug 22 09:42:13 2007 +0200 > files: src/conf/cards/CMI8788.conf > description: > cmi8788: add alsa-lib config > > Add a .conf file to enable dmix/dsnoop and softvol for CMI8788. > > Using dmix helps mask the bug that all audio is forced to 48 kHz. :-) as usual, here's the missing bit:

2 1

[alsa-devel] problems writing pcm driver
by Trent Piepho 22 Aug '07

22 Aug '07

I'm trying to write an ALSA driver, but there are some thing I'm not clear on and it's not working as well as I'd like. Atomicity: trigger, pointer, and ack are atomic with respect to themselves. e.g., two copies of the trigger callback can't be running at the same time. That much is clear. But are they atomic with respect to each other? Can the trigger callback run at the same time as the pointer callback? How about the atomic callbacks with respect to the non-atomic ones? Can trigger run at the same time as prepare? The pointer callback: What exactly is the current hardware position? My hardware has a counter that tells me how many periods have been DMAed into the buffer. Suppose my period size is 256 frames and I'm doing audio capture. If pointer is called before any DMA transfers have completed, do I return 0? Now suppose it's called after one period of audio has been DMAed into the buffer. Do I return 255 or 256? After two periods have been received, should I return 511 or 0? Why is pointer called so many times? Here's a log of callbacks and irqs my driver is getting. I'm using the cycle counter to give them microsecond timestamps. My period is 256 frames at 48kHz, so each period is 5333 us. There are only two periods in the buffer. Time (us) | Callback or IRQ ---------------------------------------------- 0.000 trigger - start DMA 134.513 pointer - count 1, returned 0 160.254 IRQ - not calling snd_pcm_period_elapsed 5313.030 IRQ - called snd_pcm_period_elapsed 5318.808 pointer - count 2, returned 256 IRQ hander finished 5348.309 pointer - count 2, returned 256 10627.526 IRQ - called snd_pcm_period_elapsed 10633.075 pointer - count 3, returned 0 IRQ hander finished 10659.755 pointer - count 3, returned 0 15941.173 IRQ - called snd_pcm_period_elapsed 15946.601 pointer - count 4, returned 256 IRQ hander finished 15969.743 pointer - count 4, returned 256 [and so on] The pointer callback is called only 134 us after the trigger, before the first IRQ or a period of data could possibly be received. Why is this done? To get the position in the buffer to start at? I assumed the data should start at the beginning of the buffer, but is this not the case? You'll notice the first IRQ is received at only 160 us. The hardware generates an IRQ when each period _starts_, not when one ends. So the first IRQ is ignored, the second IRQ tells me the first period has finished, and so on. The hardware counter is the number of periods started; I have to subtract one to get the number of periods finished. When the IRQ handler calls snd_pcm_period_elapsed(), that calls the pointer callback. That's what I expected from what the docs said. But about 30 us after the pointer callback is called the first time, after the irq handler has exited, it's called again. What is the purpose of this? Is it ok that I return the same value as the previous time it was called?

4 9

Re: [alsa-devel] ESI MAYA44 PCI datasheet request
by Ash Willis 21 Aug '07

21 Aug '07

Hi Piotr, In general, I think this is good. Some points though... * I don't think you should demand firmware source. Asking for that might be seen as quite invasive. It might be a bonus to have, but I don't see anyone hacking on it. Their firmware works, It's a driver that we need. Does this card even use firmware? I guess... * Linking to a mirror probably isn't too smart if they think their infos are going to distributed all over the web. Sorry, that was my fault. I'm an idiot. I think the correct link should be http://www-old.alsa-project.org/alsa/ftp/datasheets/ * I would offer a fall back. I would propose that the approach you have mentioned is in their best interest however if they are unwilling to distribute the information freely, then the next best thing would be to find one developer that is able, willing and possesses the hardware. That's not ideal. I would prefer the second approach to no driver at all, as would you, I'm sure. However, I don't speak for anyone else when I say that. * I'm sure they know the ins and outs of open source but you should confirm with them the terms of this arrangement. NDAs are basically incompatible with this whole thing because, usually, releasing the source will breach the NDA. Make sure they know that the driver being produced is open source and licensed under the GNU GPL. Ash > ----- Original Message ----- > From: Piotrek <oponek(a)gmail.com> > To: alsa-devel(a)alsa-project.org, "Pawe³ Wolniewicz" <admin(a)linux-muzyka.ixion.pl> > Subject: [alsa-devel] ESI MAYA44 PCI datasheet request > Date: Tue, 21 Aug 2007 19:50:27 +0200 > > > I would like toshow you the letter that I am going to send to the ESI > company. I am asking you to accept this letter because I am going to send it > on behalf of the ALSA development team. Any suggestions will be welcome. > > > Dear Sir/Madam, > > In reply to the letter sent 14.07.2007: > > 2007/8/14, ESI UK Support <uksupport(a)esi-audio.com>: > > Dear Piotr > > ESI do not provide and have no plans for Linux drivers for our products > However > ESI are happy to provide /share information to an Individual developer > within the Linux community > That is able and capable to develope drivers > and wishes to develope drivers > > Regards > UK Support > ESI Auditechnik > > > > I would like to ask you to share the information about ESI MAYA44 PCI card > needed to write drivers on behalf of the ALSA development team. ALSA team > needs all the information that you give your programmers to create drivers > for the device. We would like to ask you for: > > - a full datasheet containing IO port layout, register descriptions and > commands, > - ESI MAYA44 PCI firmware, > - EIS MAYA44 PCI firmware source code, > - permission for the firmware to be distributed with ALSA, > - source code for currnet windows drivers would be very helpful but isn't > essential. > > There are many peope that are willing to write the driver for MAYA44 and > because of the way Open-Source software and drivers are developed, in the > interest of it's quality, it is important that the information about the > card are accesable for all of the ALSA developers. We ask for your permision > to place that information on the ALSA server for developers. Thanks to that > any qualified person will have acces to it. Many other companies provided > that kind of information to us this way before: > http://ftp.mj2.org/pub/alsa/datasheets/ > > I am sure that adding this card to the list of the suported cards under the > linux operating system will cause the number of satisfied ESI card users to > increase. Thank you for your co-operation. > > > -- > Best Regards, > Piotr Makowski > ALSA Development Team > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > ----- Original Message ----- > From: Piotrek <oponek(a)gmail.com> > To: alsa-devel(a)alsa-project.org, "Pawe³ Wolniewicz" <admin(a)linux-muzyka.ixion.pl> > Subject: [alsa-devel] ESI MAYA44 PCI datasheet request > Date: Tue, 21 Aug 2007 19:50:27 +0200 > > > I would like toshow you the letter that I am going to send to the ESI > company. I am asking you to accept this letter because I am going to send it > on behalf of the ALSA development team. Any suggestions will be welcome. > > > Dear Sir/Madam, > > In reply to the letter sent 14.07.2007: > > 2007/8/14, ESI UK Support <uksupport(a)esi-audio.com>: > > Dear Piotr > > ESI do not provide and have no plans for Linux drivers for our products > However > ESI are happy to provide /share information to an Individual developer > within the Linux community > That is able and capable to develope drivers > and wishes to develope drivers > > Regards > UK Support > ESI Auditechnik > > > > I would like to ask you to share the information about ESI MAYA44 PCI card > needed to write drivers on behalf of the ALSA development team. ALSA team > needs all the information that you give your programmers to create drivers > for the device. We would like to ask you for: > > - a full datasheet containing IO port layout, register descriptions and > commands, > - ESI MAYA44 PCI firmware, > - EIS MAYA44 PCI firmware source code, > - permission for the firmware to be distributed with ALSA, > - source code for currnet windows drivers would be very helpful but isn't > essential. > > There are many peope that are willing to write the driver for MAYA44 and > because of the way Open-Source software and drivers are developed, in the > interest of it's quality, it is important that the information about the > card are accesable for all of the ALSA developers. We ask for your permision > to place that information on the ALSA server for developers. Thanks to that > any qualified person will have acces to it. Many other companies provided > that kind of information to us this way before: > http://ftp.mj2.org/pub/alsa/datasheets/ > > I am sure that adding this card to the list of the suported cards under the > linux operating system will cause the number of satisfied ESI card users to > increase. Thank you for your co-operation. > > > -- > Best Regards, > Piotr Makowski > ALSA Development Team > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > -- We've Got Your Name at http://www.mail.com ! Get a FREE E-mail Account Today - Choose From 100+ Domains

3 2

[alsa-devel] ESI MAYA44 PCI datasheet request
by Piotrek 21 Aug '07

21 Aug '07

I would like toshow you the letter that I am going to send to the ESI company. I am asking you to accept this letter because I am going to send it on behalf of the ALSA development team. Any suggestions will be welcome. Dear Sir/Madam, In reply to the letter sent 14.07.2007: 2007/8/14, ESI UK Support <uksupport(a)esi-audio.com>: Dear Piotr ESI do not provide and have no plans for Linux drivers for our products However ESI are happy to provide /share information to an Individual developer within the Linux community That is able and capable to develope drivers and wishes to develope drivers Regards UK Support ESI Auditechnik I would like to ask you to share the information about ESI MAYA44 PCI card needed to write drivers on behalf of the ALSA development team. ALSA team needs all the information that you give your programmers to create drivers for the device. We would like to ask you for: - a full datasheet containing IO port layout, register descriptions and commands, - ESI MAYA44 PCI firmware, - EIS MAYA44 PCI firmware source code, - permission for the firmware to be distributed with ALSA, - source code for currnet windows drivers would be very helpful but isn't essential. There are many peope that are willing to write the driver for MAYA44 and because of the way Open-Source software and drivers are developed, in the interest of it's quality, it is important that the information about the card are accesable for all of the ALSA developers. We ask for your permision to place that information on the ALSA server for developers. Thanks to that any qualified person will have acces to it. Many other companies provided that kind of information to us this way before: http://ftp.mj2.org/pub/alsa/datasheets/ I am sure that adding this card to the list of the suported cards under the linux operating system will cause the number of satisfied ESI card users to increase. Thank you for your co-operation. -- Best Regards, Piotr Makowski ALSA Development Team

1 0

[alsa-devel] HDA - Add more support for Dell systems.
by Tobin Davis 21 Aug '07

21 Aug '07

This patch adds support for more Dell systems with Sigmatel/IDT codecs. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

3 11

[alsa-devel] ESI MAYA44 PCI - ESI wants to collaborate!
by Piotrek 21 Aug '07

21 Aug '07

Referring to the lack of the official ALSA support of ESI MAYA44 PCI (in fact, the card does not work) I would like to ask I there are any plans to get this card working with ALSA? I would be thankful to be able to run my soundcard properly under Linux. There are also a lot of people that would appreciate your work and are waiting for maya44 pci drivers for linux: http://www.esiforum.com/show.asp?db=esi&t=esi1&mode=3&msg=793 I wrote a letter to the UK ESI SUPPORT asking if they were going to write drivers for their products for Linux systems as well. There is a reply: " Dear Piotr ESI do not provide and have no plans for Linux drivers for our products However ESI are happy to provide /share information to an Individual developer within the Linux community That is able and capable to develope drivers and wishes to develope drivers Regards UK Support ESI Auditechnik " It means that ESI will collaborate with developers who would like to write such driver and share the documentation. Again the question: Are there any plans to make ESI MAYA44 PCI card working with ALSA? I'm not a programmer but I will help you as much as I could. -- Best Regards, Piotr Makowski

4 4

[alsa-devel] Intel HDA / AD1986A problems
by Peter Skensved 21 Aug '07

21 Aug '07

Configuration : Lenovo 3000 N100 laptop with Intel HDA / Anlog Devices AD1986A soundcard running CentOS5.0 with 2.6.18-8.1.8.el5 kernel ( uses 1.0.12rc1 based alsa driver ). The driver works with the model=laptop-eapd option except for a few things : 1) Plugging in an external headset will not mute the internal speakers ( has to be done manually in alsa-mixer ) 2) The PC speaker ( bell ) appears to be permanently muted. 3) The external microphone input does not appear to be working no matter what I do. 4) When recording from the internal microphone the level is very, very low and almost drowns in static noise. Any easy way to fix the above ? Number 4 in particular ? I've tinkered with backporting what I thought were relevant differences between the latest patch_analog.c and the one used in the kernel I have (alsa-driver 1.0.12rc1 ) but I see no difference. Any other way to tweak or reconfigure the hardware ? Enable microphone boost ?? Looking at /proc/asound/card0/codec#0 makes me believe that the hardware has several unused or permanently disabled features. This particular laptop has a model number which differs slightly from the one listed in patch_analog.c ( 0768-6KU instead of 0768-4JU ). Not sure if is relevant. And finally a ( somewhat ) related question : Is it possible to get the sound card to work with the slmodem package to drive the built in modem ??? ============================================================================================ Partial output from lspci -nv is attached below together with stuff from /proc/asound : 00:1b.0 0403: 8086:27d8 (rev 02) Subsystem: 17aa:2066 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: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 233 Region 0: Memory at b0000000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [70] Express Unknown type IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0 Link: Latency L0s <64ns, L1 <1us Link: ASPM Disabled CommClk- ExtSynch- Link: Speed unknown, Width x0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) more /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xb0000000 irq 233 more /proc/asound/devices 2: : timer 3: : sequencer 4: [ 0- 0]: digital audio playback 5: [ 0- 0]: digital audio capture 6: [ 0] : control more /proc/asound/modules 0 snd_hda_intel more /proc/asound/card0/codec#0 Codec: Analog Devices AD1986A Address: 0 Vendor Id: 0x11d41986 Subsystem Id: 0x17aa2066 Revision Id: 0x100500 Default PCM: rates 0x07f, bits 0x0e, types 0x1 Default Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Default Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital PCM: rates 0x060, bits 0x02, types 0x5 Connection: 2 0x01* 0x06 Node 0x03 [Audio Output] wcaps 0x44d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x1d 0x1d] Power: 0x0 Node 0x04 [Audio Output] wcaps 0x40d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Power: 0x0 Node 0x05 [Audio Output] wcaps 0x40d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Power: 0x0 Node 0x06 [Audio Input] wcaps 0x100511: Stereo PCM: rates 0x07f, bits 0x06, types 0x1 Power: 0x0 Connection: 1 0x12 Node 0x07 [Audio Mixer] wcaps 0x200101: Stereo Connection: 8 0x03 0x09 0x13 0x14 0x15 0x16 0x17 0x18 Node 0x08 [Audio Mixer] wcaps 0x200100: Mono Connection: 1 0x07 Node 0x09 [Audio Mixer] wcaps 0x20010e: Mono Amp-In Amp-Out Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80] [0x80] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80] Connection: 2 0x04 0x05 Node 0x0a [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x07* 0x04 0x05 Node 0x0b [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x07* 0x04 Node 0x0c [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x04* 0x07 Node 0x0d [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x05* 0x08 Node 0x0e [Audio Selector] wcaps 0x300100: Mono Connection: 2 0x08* 0x11 Node 0x0f [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-Out vals: [0x00 0x00] Connection: 8 0x1f* 0x20 0x1d 0x1d 0x27 0x28 0x29 0x2a Node 0x10 [Audio Selector] wcaps 0x300101: Stereo Connection: 3 0x20* 0x1c 0x1f Node 0x11 [Audio Selector] wcaps 0x300941: Stereo Connection: 2 0x0f* 0x2b Node 0x12 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=1 Amp-Out vals: [0x8f 0x8f] Connection: 8 0x11 0x22 0x00 0x21 0x10 0x07* 0x08 0x23 Node 0x13 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x1d 0x1d] Connection: 1 0x11 Node 0x14 [Audio Selector] wcaps 0x30010c: Mono Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80] Connection: 1 0x23 Node 0x15 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Connection: 1 0x22 Node 0x16 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Connection: 1 0x21 Node 0x17 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x15 0x15] Connection: 1 0x10 Node 0x18 [Audio Selector] wcaps 0x30010c: Mono Amp-Out Amp-Out caps: ofs=0x0f, nsteps=0x0f, stepsize=0x0b, mute=1 Amp-Out vals: [0x8f] Connection: 2 0x19* 0x24 Node 0x19 [Beep Generator Widget] wcaps 0x700000: Mono Node 0x1a [Pin Complex] wcaps 0x400185: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x06 0x06] Pincap 0x081f: OUT HP Detect Pin Default 0x02214021: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green Pin-ctls: 0xc0: OUT HP Connection: 1 0x0a Node 0x1b [Pin Complex] wcaps 0x400185: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x06 0x06] Pincap 0x081001f: OUT HP EAPD Detect Pin Default 0x81114011: [Fixed] Speaker at Ext Rear Conn = 1/8, Color = Green Pin-ctls: 0x40: OUT Connection: 1 0x0b Node 0x1c [Pin Complex] wcaps 0x400185: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0837: IN OUT Detect Pin Default 0x41013012: [N/A] Line Out at Ext Rear Conn = 1/8, Color = Blue Pin-ctls: 0x40: OUT Connection: 1 0x0c Node 0x1d [Pin Complex] wcaps 0x400985: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x081737: IN OUT Detect Pin Default 0x41019015: [N/A] Line Out at Ext Rear Conn = 1/8, Color = Pink Pin-ctls: 0x40: OUT Connection: 1 0x0d Node 0x1e [Pin Complex] wcaps 0x400104: Mono Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Amp-Out vals: [0x80] Pincap 0x0810: OUT Pin Default 0x501700f0: [N/A] Speaker at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0x40: OUT Connection: 1 0x0e Node 0x1f [Pin Complex] wcaps 0x400081: Stereo Pincap 0x081727: IN Detect Pin Default 0xc2a190f0: [Both] Mic at Ext Front Conn = 1/8, Color = Pink Pin-ctls: 0x24: IN Node 0x20 [Pin Complex] wcaps 0x400081: Stereo Pincap 0x081727: IN Detect Pin Default 0x418130f0: [N/A] Line In at Ext Rear Conn = 1/8, Color = Blue Pin-ctls: 0x20: IN Node 0x21 [Pin Complex] wcaps 0x400081: Stereo Pincap 0x0827: IN Detect Pin Default 0x509700f0: [N/A] Aux at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0x20: IN Node 0x22 [Pin Complex] wcaps 0x400001: Stereo Pincap 0x0820: IN Pin Default 0x903300f0: [Fixed] CD at Int N/A Conn = ATAPI, Color = Unknown Pin-ctls: 0x20: IN Node 0x23 [Pin Complex] wcaps 0x400000: Mono Pincap 0x0820: IN Pin Default 0x90b70130: [Fixed] Telephony at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0x20: IN Node 0x24 [Pin Complex] wcaps 0x400000: Mono Pincap 0x0820: IN Pin Default 0x90f701f0: [Fixed] Other at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0x20: IN Node 0x25 [Pin Complex] wcaps 0x400301: Stereo Digital Pincap 0x0810: OUT Pin Default 0x014511f0: [Jack] SPDIF Out at Ext Rear Conn = Optical, Color = Black Pin-ctls: 0x40: OUT Connection: 1 0x02 Node 0x26 [Power Widget] wcaps 0x500500: Mono Power: 0x0 Connection: 8 0x07* 0x08 0x13 0x14 0x15 0x16 0x17 0x18 Node 0x27 [Audio Mixer] wcaps 0x200101: Stereo Connection: 2 0x1f 0x1d Node 0x28 [Audio Mixer] wcaps 0x200101: Stereo Connection: 2 0x1f 0x20 Node 0x29 [Audio Mixer] wcaps 0x200101: Stereo Connection: 2 0x1d 0x20 Node 0x2a [Audio Mixer] wcaps 0x200101: Stereo Connection: 3 0x1f 0x1d 0x20 Node 0x2b [Audio Mixer] wcaps 0x200100: Mono Connection: 1 0x0f more /proc/asound/card0/codec#1 Codec: Generic 11c1 ID 1040 Address: 1 Vendor Id: 0x11c11040 Subsystem Id: 0x11c10001 Revision Id: 0x100200 more /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: AD198x Analog name: AD198x Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 more /proc/asound/card0/pcm0p/info card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: AD198x Analog name: AD198x Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 amixer scontents Simple mixer control 'Master',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 12 [39%] [on] Front Right: Playback 12 [39%] [on] Simple mixer control 'PCM',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 29 [94%] [on] Front Right: Playback 29 [94%] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Mono Limits: Playback 0 - 31 Mono: Capture [on] Front Left: Playback 29 [94%] [on] Front Right: Playback 29 [94%] [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 15 Front Left: Capture 15 [100%] [on] Front Right: Capture 15 [100%] [on] Simple mixer control 'Mix',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Mono Mono: Capture [off] Simple mixer control 'External Amplifier',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Internal Mic',0 Capabilities: pvolume pswitch cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Mono Limits: Playback 0 - 31 Mono: Capture [off] Front Left: Playback 15 [48%] [on] Front Right: Playback 15 [48%] [on] ======================================================================================= Peter Skensved Email : peter at SNO dot Phy dot QueensU dot CA Dept. of Physics, Queen's University, Kingston, Ontario, Canada

2 1