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

[alsa-devel] how to subscribe to new maillist?
by Songmao Tian 28 Mar '07

28 Mar '07

Hello, I have tried several times on the web page http://mailman.alsa-project.org/mailman/listinfo/alsa-devel, but i can't receive the confirm mail, so how to subscribe? Tian

4 3

[alsa-devel] New code for conexant chipsets in -mm tree
by Rodrigo Luiz 28 Mar '07

28 Mar '07

Hi. I have a HDA NVidia, with a Conexant chipset CX20549 Venice (CXT5045) I tried to test the last alsa-kernel in -mm tree to support my mic. (2.6.21-rc4-mm1 and 2.6.21-rc5-mm2) When I try to load the hda-intel, I receive this message: Mar 27 11:29:08 dig kernel: hda_intel: azx_get_response timeout, switching to polling mode Mar 27 11:29:09 dig kernel: hda_intel: azx_get_response timeout, switching to single_cmd mode After loaded, the speakers doesn't work. Headphone works ok. Mic too. Look in code, I apply this comment and now the speakers works for me: --- patch_conexant.c.orig 2007-03-27 11:37:43.000000000 -0300 +++ patch_conexant.c 2007-03-27 11:38:02.000000000 -0300 @@ -822,7 +822,7 @@ case CXT5045_FUJITSU: spec->input_mux = &cxt5045_capture_source; spec->num_init_verbs = 2; - spec->init_verbs[1] = cxt5045_mic_sense_init_verbs; +// spec->init_verbs[1] = cxt5045_mic_sense_init_verbs; spec->mixers[0] = cxt5045_mixers; codec->patch_ops.init = cxt5045_init; break; But, I don't understand why, because this code is not executed for my chipset. Thanks, Rodrigo Luiz

3 8

[alsa-devel] snd-es1968 capture broken
by Rene Herman 28 Mar '07

28 Mar '07

Good day. Capture is broken on snd-es1968, at least if it is driving a ES1970MS-3D (ESS Canyon 3D). The captured stream is "stuttering" like mad. Kernel 2.6.20 (ALSA 1.0.14-rc1) with alsa-lib 1.0.11 (my distribution's version). Does not happen with a CS4236 in the same machine and same software version(s). Don't know if this driver has a specific maintainer. If needed I guess I can try to pin it down to some change. I hardly use capture on this card but it wasn't always broken... Rene.

2 15

Re: [alsa-devel] Basic DMA question
by Sven Johnsson 28 Mar '07

28 Mar '07

Rene, I have already read the ALSA driver document. What I really like to understand is when DMA transfers are invoked, and what the source and destination for the transfer is. Regards, Sven 2007/3/26, Rene Herman <rene.herman(a)gmail.com>: > On 03/26/2007 03:13 AM, Sven Johnsson wrote: > > > I'm new to writing ALSA drivers, and I could use some help on > > clarifying how DMA is used in ALSA. > > "Writing an ALSA Driver" is a useful document. Google will find it... > > By the way, the alsa-devel mailinglist recently moved from > sourceforge.net to alsa-project.org directly and the new list is > moderated for non-subscribers. I just approved your message from the > moderation queue manually, but please consider subscribing, at: > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > Thanks, > Rene > > > > > > > > Regards, > > Sven > > _______________________________________________ > > Alsa-devel mailing list > > Alsa-devel(a)alsa-project.org > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > >

3 2

Re: [alsa-devel] Status of CMI9738 and SiS7012
by Takashi Iwai 28 Mar '07

28 Mar '07

At Tue, 27 Mar 2007 10:44:23 -0600, Rob Franklin wrote: > > On 3/27/07, Takashi Iwai <tiwai(a)suse.de> wrote: > > At Tue, 27 Mar 2007 08:49:05 -0600, > > Rob Franklin wrote: > > > > > > Hi All, > > > > > > I posted a question a couple of weeks ago to the alsa-users list > > > (Can't get spdif working with ALSA and FC6 on ECS L4S5MG/651+ > > > motherboard), but never got a response. > > > > > > I have been looking at the ALSA source code for the AC'97 codec on my > > > board (CMI9738) and the source code for the intel8x0 driver (for my > > > SiS 7012). However, as far as I can tell from looking at the source, > > > S/PDIF is not enabled/supported for this combination of devices. > > > Additionally, Googling around I haven't found any mention of people > > > getting spdif working with ALSA and a CM9738 / SiS7012 combo. > > > > > > I am wondering whether anyone on the developer list can confirm that > > > this is the case. Also, if this is the case can someone give me an > > > idea of what would be required to get this working. The system is > > > setup with dual boot and so I could grab some of the values from > > > windows using a PCI sniffer, and I might be able to do some hacking on > > > the source code and submit a patch if someone could help guide me in > > > the right direction. > > > > Are you sure it's CM9738? AFAIK, CM9738 doesn't support SPDIF at > > all, but CM9739 does... > > > That was my first thought too, but I pulled open the case last night > and verified that it was indeed a 9738. The download page from the > motherboard manufacturer has a driver for CMI9738 and a CMI9738/9739 > driver (http://www.ecsusa.com/downloads/drivers_sound.html). I am > wondering if there are two different versions of this chip. > > Here is the output from lspci -vv for the sound device: > > 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] > AC'97 Sound Controller (rev a0) > Subsystem: Elitegroup Computer Systems Unknown device 0a44 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- > Latency: 32 (13000ns min, 2750ns max) > Interrupt: pin C routed to IRQ 22 > Region 0: I/O ports at d000 [size=256] > Region 1: I/O ports at d400 [size=128] > Capabilities: <access denied> > > One thought that I had was to force the AC'97 driver to detect the > chip as a 9739 instead of a 9738 to see whether my 9738 can work as a > 9739. But I'm not sure how to do that short of modifying the source > code and recompiling the kernel module. First check whether its codec id is CMI9738, see /proc/asound/card0/codec97#0/* files. If it's really CM9738, you can hack pci/ac97/ac97_codec.c to replace patch_cm9738 with patch_cm9739 in snd_ac97_codec_ids[]. Takashi

1 0

[alsa-devel] Status of CMI9738 and SiS7012
by Rob Franklin 27 Mar '07

27 Mar '07

Hi All, I posted a question a couple of weeks ago to the alsa-users list (Can't get spdif working with ALSA and FC6 on ECS L4S5MG/651+ motherboard), but never got a response. I have been looking at the ALSA source code for the AC'97 codec on my board (CMI9738) and the source code for the intel8x0 driver (for my SiS 7012). However, as far as I can tell from looking at the source, S/PDIF is not enabled/supported for this combination of devices. Additionally, Googling around I haven't found any mention of people getting spdif working with ALSA and a CM9738 / SiS7012 combo. I am wondering whether anyone on the developer list can confirm that this is the case. Also, if this is the case can someone give me an idea of what would be required to get this working. The system is setup with dual boot and so I could grab some of the values from windows using a PCI sniffer, and I might be able to do some hacking on the source code and submit a patch if someone could help guide me in the right direction. Thanks, Rob

2 1

[alsa-devel] Correct value for AK4114_DIF2 constant?
by dustin＠seznam.cz 27 Mar '07

27 Mar '07

Hello, While going through AK4114 support I have hit the constant AK4114_DIF2 in ak4114.h . I would say its value should be (1<<6) according to AK4114 datasheet. This is current situation: #define AK4114_DIF2 (1<<5) /* Audio Data Control */ #define AK4114_DIF1 (1<<5) /* Audio Data Control */ #define AK4114_DIF0 (1<<4) /* Audio Data Control */ I think cards using this code should experience related problems. E.g. in juli.c and revo.c the constant #define AK4114_DIF_I24I2S (AK4114_DIF2|AK4114_DIF1|AK4114_DIF0) /* STDO: I2S; LRCLK, BICK = Input */ is used, intended to set output serial data mode to I2S/slave perhaps compatible with ICE1712/24. This may be causing problems mentioned in revo.c: #if 0 /* FIXME: ak4114 makes the sound much lower due to some confliction, * so let's disable it right now... */ #define BUILD_AK4114_AP192 #endif I am trying to add support for SPDIF-IN of AudioTrak MI/ODI/O addon card (ice1724 + ak4114), hopefully this will be a little step forward. Thanks for any reaction. Best regards, Pavel.

2 1

[alsa-devel] capture line-out
by Tomas Carnecky 27 Mar '07

27 Mar '07

Is it possible to capture/record line-out (or simply 'what the user hears')? I'm writing 'fraps for linux' and so far I have video capturing implemented and that works great, but users are also requesting sound-capturing and I'm looking into how that could be done. thanks tom

2 10

[alsa-devel] [3/5] 2.6.21-rc5: known regressions
by Adrian Bunk 27 Mar '07

27 Mar '07

This email lists some known regressions in Linus' tree compared to 2.6.20. If you find your name in the Cc header, you are either submitter of one of the bugs, maintainer of an affectected subsystem or driver, a patch of you caused a breakage or I'm considering you in any other way possibly involved with one or more of these issues. Due to the huge amount of recipients, please trim the Cc when answering. Subject : Oops when changing DVB-T adapter References : http://lkml.org/lkml/2007/3/9/212 Submitter : CIJOML <cijoml(a)volny.cz> Status : unknown Subject : snd_intel8x0: divide error: 0000 References : http://lkml.org/lkml/2007/3/5/252 Submitter : Michal Piotrowski <michal.k.k.piotrowski(a)gmail.com> Status : unknown Subject : USB: iPod doesn't work (CONFIG_USB_SUSPEND) References : http://lkml.org/lkml/2007/3/21/320 Submitter : Tino Keitel <tino.keitel(a)gmx.de> Caused-By : Marcelo Tosatti <marcelo(a)kvack.org> commit 1d619f128ba911cd3e6d6ad3475f146eb92f5c27 Handled-By : Oliver Neukum <oneukum(a)suse.de> Status : problem is being debuggged

1 0

Re: [alsa-devel] [Alsa-devel] [RFC][RFT] Adding support for Jazz16 based sound cards
by Rask Ingemann Lambertsen 27 Mar '07

27 Mar '07

On Mon, Mar 12, 2007 at 12:28:00PM +0100, Takashi Iwai wrote: > At Mon, 12 Mar 2007 00:24:36 +0100, > Rask Ingemann Lambertsen wrote: > > > I tried to include u-law support, but it doesn't sound right and playback > > speed is about one third of what it should be. I could really use some > > documentation here. I'll remove it before submitting a final patch if I > > don't get it to work. > > OK. I never got u-law or a-law to work. I tried various ADPCM formats which gave correct playback speed, but much noise. There seems to be a Media Vision ADPCM format, which is probably what the Jazz16 wants, but I have no information about that format. FWIW, the playback_format/capture_format values I've tried are: #define SB_DSP_ALAW_OUTPUT_AUTO 0x1F #define SB_DSP_ALAW_INPUT_AUTO 0x2F #define SB_DSP_ULAW_OUTPUT_AUTO 0x7f #define SB_DSP_ULAW_INPUT_AUTO 0x8f #define SB_DSP_ADPCM_OUTPUT_AUTO 0x7C+1 #define SB_DSP_ADPCM_INPUT_AUTO 0x8C+1 > > Setting the irq of the MPU-401 port requires the SB part to be active and > > even worse, DSP commands need to be sent. Would it be better to just use the > > MPU-401 port without an irq and avoid the complexity? > > Isn't SB part already active? It's fine with non-irq version (which > uses timer) if the code gets too complicated, of course. It turned out that I can't disable just the MPU port. -- Rask Ingemann Lambertsen

1 0