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

Re: [alsa-devel] Ответы для Linux Format
by Serge A. Suchkov 21 Feb '08

21 Feb '08

В сообщении от Thursday 21 February 2008 12:33:26 Andrei Borovsky написал(а): > > Хмм... а можно урезать эту информацию до минимума ? > > Это ведь всего лишь хобби и я не склонен его афишировать настолько > > публично :) > > >Тем более мой вклад в GSPCA весьма скромен на общем фоне. > > Как скажете. В принципе, все это, конечно, необязательно. Даже фотографию > поместить не хотите? :) Нет, спасибо :) > > > С уважением, > Андрей Боровский. -- Regards, Serge A. Suchkov -- A baby is an alimentary canal with a loud voice at one end and no responsibility at the other.

1 1

Re: [alsa-devel] [PATCH] Fix a compile warning under gcc-4.2.3.
by Clemens Ladisch 21 Feb '08

21 Feb '08

Joshua Roys wrote: > sound/core/init.c: In function ‘snd_card_disconnect’: > sound/core/init.c:307: warning: the address of ‘snd_shutdown_f_ops’ will always evaluate as ‘true’ > > Signed-off-by: Joshua Roys <roysjosh(a)gmail.com> > --- > sound/core/init.c | 1 - > 1 files changed, 0 insertions(+), 1 deletions(-) > > diff --git a/sound/core/init.c b/sound/core/init.c > index 2cb7099..1afc58b 100644 > --- a/sound/core/init.c > +++ b/sound/core/init.c > @@ -304,7 +304,6 @@ int snd_card_disconnect(struct snd_card *card) > list_add(&mfile->shutdown_list, &shutdown_files); > spin_unlock(&shutdown_lock); > > - fops_get(&snd_shutdown_f_ops); > mfile->file->f_op = &snd_shutdown_f_ops; > > mfile = mfile->next; This change may get rid of the warning, but is has the slight disadvantage that the kernel will blow up if you try to unload the sound modules before all device files have been closed. If you want to get rid of this warning, tell the compiler that fops_get knows what it does; or try making fops_get an inline function instead of a macro. Regards, Clemens

2 1

[alsa-devel] [PATCH] hda: 92HDxxxx PCI Quirks
by Matthew Ranostay 21 Feb '08

21 Feb '08

Added PCI_QUIRKS for laptop that have the 92HDxxx family of codecs. Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> --- diff -r 6b53fa114faa pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Tue Feb 19 15:03:57 2008 +0100 +++ b/pci/hda/patch_sigmatel.c Wed Feb 20 17:18:15 2008 -0500 @@ -64,11 +64,14 @@ enum { enum { STAC_92HD73XX_REF, + STAC_DELL_M6_5ST, STAC_92HD73XX_MODELS }; enum { STAC_92HD71BXX_REF, + STAC_DELL_M4_5ST, + STAC_DELL_M4_6ST, STAC_92HD71BXX_MODELS }; @@ -334,10 +337,10 @@ static hda_nid_t stac922x_pin_nids[10] = 0x0f, 0x10, 0x11, 0x15, 0x1b, }; -static hda_nid_t stac92hd73xx_pin_nids[12] = { +static hda_nid_t stac92hd73xx_pin_nids[13] = { 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, 0x10, 0x11, 0x12, 0x13, - 0x14, 0x22 + 0x14, 0x1e, 0x22 }; static hda_nid_t stac92hd71bxx_pin_nids[10] = { @@ -1220,24 +1223,48 @@ static struct snd_pci_quirk stac925x_cfg {} /* terminator */ }; -static unsigned int ref92hd73xx_pin_configs[12] = { +static unsigned int ref92hd73xx_pin_configs[13] = { 0x02214030, 0x02a19040, 0x01a19020, 0x02214030, 0x0181302e, 0x01014010, 0x01014020, 0x01014030, 0x02319040, 0x90a000f0, 0x90a000f0, 0x01452050, + 0x01452050, +}; + +static unsigned int dell_m6_5st_pin_configs[13] = { + 0x0321101f, 0x4f00000f, 0x4f0000f0, 0x90170110, + 0x03a11020, 0x03011050, 0x4f0000f0, 0x4f0000f0, + 0x4f0000f0, 0x90a60160, 0x4f0000f0, 0x4f0000f0, + 0x4f0000f0, }; static unsigned int *stac92hd73xx_brd_tbl[STAC_92HD73XX_MODELS] = { - [STAC_92HD73XX_REF] = ref92hd73xx_pin_configs, + [STAC_92HD73XX_REF] = ref92hd73xx_pin_configs, + [STAC_DELL_M6_5ST] = dell_m6_5st_pin_configs, }; static const char *stac92hd73xx_models[STAC_92HD73XX_MODELS] = { [STAC_92HD73XX_REF] = "ref", + [STAC_DELL_M6_5ST] = "dell-m6-5stack", }; static struct snd_pci_quirk stac92hd73xx_cfg_tbl[] = { /* SigmaTel reference board */ SND_PCI_QUIRK(PCI_VENDOR_ID_INTEL, 0x2668, - "DFI LanParty", STAC_92HD73XX_REF), + "DFI LanParty", STAC_92HD73XX_REF), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0254, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0255, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0256, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0257, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x025e, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x025f, + "unknown Dell", STAC_DELL_M6_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0271, + "unknown Dell", STAC_DELL_M6_5ST), {} /* terminator */ }; @@ -1247,18 +1274,56 @@ static unsigned int ref92hd71bxx_pin_con 0x90a000f0, 0x01452050, }; +static unsigned int dell_m4_5st_pin_configs[13] = { + 0x0421101f, 0x04a11221, 0x40f000f0, 0x90170110, + 0x23a1902e, 0x23014250, 0x40f000f0, 0x4f0000f0, + 0x40f000f0, 0x4f0000f0, +}; + +static unsigned int dell_m4_6st_pin_configs[13] = { + 0x0421101f, 0x04a11221, 0x90a70330, 0x90170110, + 0x23a1902e, 0x23014250, 0x40f000f0, 0x40f000f0, + 0x40f000f0, 0x044413b0, +}; + static unsigned int *stac92hd71bxx_brd_tbl[STAC_92HD71BXX_MODELS] = { [STAC_92HD71BXX_REF] = ref92hd71bxx_pin_configs, + [STAC_DELL_M4_5ST] = dell_m4_5st_pin_configs, + [STAC_DELL_M4_6ST] = dell_m4_6st_pin_configs, }; static const char *stac92hd71bxx_models[STAC_92HD71BXX_MODELS] = { [STAC_92HD71BXX_REF] = "ref", + [STAC_DELL_M4_5ST] = "dell-m4-5stack", + [STAC_DELL_M4_6ST] = "dell-m4-6stack", }; static struct snd_pci_quirk stac92hd71bxx_cfg_tbl[] = { /* SigmaTel reference board */ SND_PCI_QUIRK(PCI_VENDOR_ID_INTEL, 0x2668, "DFI LanParty", STAC_92HD71BXX_REF), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0233, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0234, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0250, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x024f, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x024d, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0251, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0277, + "unknown Dell", STAC_DELL_M4_5ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0263, + "unknown Dell", STAC_DELL_M4_6ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0265, + "unknown Dell", STAC_DELL_M4_6ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0262, + "unknown Dell", STAC_DELL_M4_6ST), + SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0264, + "unknown Dell", STAC_DELL_M4_6ST), {} /* terminator */ }; @@ -3355,12 +3420,38 @@ again: spec->num_muxes = ARRAY_SIZE(stac92hd73xx_mux_nids); spec->num_adcs = ARRAY_SIZE(stac92hd73xx_adc_nids); - spec->num_dmics = STAC92HD73XX_NUM_DMICS; spec->num_dmuxes = ARRAY_SIZE(stac92hd73xx_dmux_nids); spec->dinput_mux = &stac92hd73xx_dmux; /* GPIO0 High = Enable EAPD */ spec->gpio_mask = spec->gpio_dir = 0x1; spec->gpio_data = 0x01; + + switch (spec->board_config) { + case STAC_DELL_M6_5ST: + switch (codec->subsystem_id) { + case 0x1028025e: /* Analog Mics */ + case 0x1028025f: + stac92xx_set_config_reg(codec, 0x0b, 0x90A70170); + spec->num_dmics = 0; + break; + case 0x10280254: /* Digital Mics */ + case 0x10280255: + case 0x10280271: + case 0x10280272: + stac92xx_set_config_reg(codec, 0x13, 0x90A60160); + spec->num_dmics = 1; + break; + case 0x10280256: /* Both */ + case 0x10280057: + stac92xx_set_config_reg(codec, 0x0b, 0x90A70170); + stac92xx_set_config_reg(codec, 0x13, 0x90A60160); + spec->num_dmics = 1; + break; + } + break; + default: + spec->num_dmics = STAC92HD73XX_NUM_DMICS; + } spec->num_pwrs = ARRAY_SIZE(stac92hd73xx_pwr_nids); spec->pwr_nids = stac92hd73xx_pwr_nids;

2 2

[alsa-devel] [PATCH] hda: STAC927x power management
by Matthew Ranostay 21 Feb '08

21 Feb '08

Fix issue on STAC927x codecs that first DAC was getting powered down even if was being used. Signed-off-by: Matthew Ranostay <mranostay(a)embeddedalley.com> --- diff -r 30701aaf404c pci/hda/patch_sigmatel.c --- a/pci/hda/patch_sigmatel.c Wed Feb 20 12:13:29 2008 +0100 +++ b/pci/hda/patch_sigmatel.c Wed Feb 20 14:16:59 2008 -0700 @@ -2893,7 +2893,8 @@ static void stac92xx_power_down(struct h /* power down inactive DACs */ hda_nid_t *dac; for (dac = spec->dac_list; *dac; dac++) - if (!is_in_dac_nids(spec, *dac)) + if (!is_in_dac_nids(spec, *dac) && + spec->multiout.hp_nid != *dac) snd_hda_codec_write_cache(codec, *dac, 0, AC_VERB_SET_POWER_STATE, AC_PWRST_D3); }

2 1

Re: [alsa-devel] Alsa-devel Digest, Vol 12, Issue 70
by Anders Rønningen 21 Feb '08

21 Feb '08

I'll do the tests when I get home from work. Just wanted to check that I understood the instructions. The problem is like you said. The left HP and the internal speakers never give any sound, regardless of whether the right HP is connected. You want me to: 1. remove the mentioned line from alsa-kernel/pci/hda/patch_sigmatel.c. 2. configure and build the driver with full debug 3. reboot, run alsa-info.sh and upload the output Is that right? > No difference in the output but there must be a difference in the codec setting. You mean before and after I remove the line from patch_sigmatel.c? >What is the original configuration of pin 0xf? How can I know/find out this? - Anders On Feb 20, 2008 12:00 PM, <alsa-devel-request(a)alsa-project.org> wrote: > Send Alsa-devel mailing list submissions to > alsa-devel(a)alsa-project.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > or, via email, send a message with subject or body 'help' to > alsa-devel-request(a)alsa-project.org > > You can reach the person managing the list at > alsa-devel-owner(a)alsa-project.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Alsa-devel digest..." > > > Today's Topics: > > 1. Re: Problem with DELL XPS M1530 (Jiang zhe) > 2. Re: Problem with DELL XPS M1530 (Takashi Iwai) > 3. Re: Problem with DELL XPS M1530 (Takashi Iwai) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Feb 2008 17:49:00 +0800 > From: Jiang zhe <zhe.jiang(a)intel.com> > Subject: Re: [alsa-devel] Problem with DELL XPS M1530 > To: Anders R?nningen <andersronningen(a)gmail.com> > Cc: Takashi Iwai <tiwai(a)suse.de>, alsa-devel(a)alsa-project.org > Message-ID: <1203500940.3006.4.camel(a)localhost.localdomain> > Content-Type: text/plain; charset=utf-8 > > On Wed, 2008-02-20 at 02:25 +0800, Anders R?nningen wrote: > > Hi Takashi. > > > > Some dmesg output: > > > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: > > autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: > > speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: > > hp_outs=1 (0xa/0xf/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: > > mono: mono_out=0x0 > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: > > inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 > > [ 14.196000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: > > dac_nids=2 (0x5/0x4/0x0/0x0/0x0) > > > > Unmuted and adjusted Surround volume, but it made no difference. > > > > - Anders > > > It's weird that 0xf is in both the line_outs and hp_outs. > And the hp_outs=1 when there are two items. > > What is the original configuration of pin 0xf? > Please try to get rid of this line from the > alsa-kernel/pci/hda/patch_sigmatel.c. > > SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x022e, "Dell ", STAC_DELL_BIOS), > > Rebuild and install the driver. > Please give the output of "cat /proc/asound/card0/codec#0". > > Thanks! > > > Takashi Iwai wrote: > > > At Tue, 19 Feb 2008 17:24:04 +0100, > > > Anders R?nningen wrote: > > > > > >> Hi. I am the mentioned user with this problem. Just thought I'd > > give you > > >> a little more info on this problem. > > >> > > >> What wishie described was correct, except it's the internal > > speakers and > > >> the /left/ hp-jack that stopped working, while the right one is > > still > > >> ok. Like he wrote, the reason we started this debugging was to get > > mic > > >> sound on my system. The thing I think is worth mentioning is that > > with > > >> alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and > > the > > >> internal speakers worked for me. People in #alsa told me that the > > module > > >> was not loaded correctly, but whatever was loaded _almost_ worked > > well :-) > > >> > > > > > > OK, please build the driver with --with-debug=full option and show > > the > > > kernel messages such as "autoconfig: ..." and "dac_nids...", etc. > > > This contains the information that the pin configuration parser > > uses. > > > > > > Also, unmute and adjust "Surround" volume. > > > > > > > > > Takashi > > > > > _______________________________________________ > > Alsa-devel mailing list > > Alsa-devel(a)alsa-project.org > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 20 Feb 2008 11:50:44 +0100 > From: Takashi Iwai <tiwai(a)suse.de> > Subject: Re: [alsa-devel] Problem with DELL XPS M1530 > To: Jiang zhe <zhe.jiang(a)intel.com> > Cc: alsa-devel(a)alsa-project.org, Anders R?nningen > <andersronningen(a)gmail.com> > Message-ID: <s5hy79fsxyz.wl%tiwai(a)suse.de> > Content-Type: text/plain; charset=ISO-8859-1 > > At Wed, 20 Feb 2008 17:49:00 +0800, > Jiang zhe wrote: > > > > On Wed, 2008-02-20 at 02:25 +0800, Anders R?nningen wrote: > > > Hi Takashi. > > > > > > Some dmesg output: > > > > > > [ 14.192000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: > > > autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) > > > [ 14.192000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: > > > speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) > > > [ 14.192000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: > > > hp_outs=1 (0xa/0xf/0x0/0x0/0x0) > > > [ 14.192000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: > > > mono: mono_out=0x0 > > > [ 14.192000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: > > > inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 > > > [ 14.196000] ALSA > > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: > > > dac_nids=2 (0x5/0x4/0x0/0x0/0x0) > > > > > > Unmuted and adjusted Surround volume, but it made no difference. > > > > > > - Anders > > > > > It's weird that 0xf is in both the line_outs and hp_outs. > > And the hp_outs=1 when there are two items. > > It's due to a fix for an ALC268 laptop that has also two HPs but one > is actually a line-out. Note that hp_outs=1 in the print above. The > 0x0f in hp_outs is simply a garbage. Maybe that patch broke the > double HPs with STAC9228... > > > Takashi > > > ------------------------------ > > Message: 3 > Date: Wed, 20 Feb 2008 11:52:43 +0100 > From: Takashi Iwai <tiwai(a)suse.de> > Subject: Re: [alsa-devel] Problem with DELL XPS M1530 > To: Anders R?nningen <andersronningen(a)gmail.com> > Cc: alsa-devel(a)alsa-project.org > Message-ID: <s5hwsozsxvo.wl%tiwai(a)suse.de> > Content-Type: text/plain; charset=ISO-8859-1 > > At Tue, 19 Feb 2008 19:25:24 +0100, > Anders R?nningen wrote: > > > > Hi Takashi. > > > > Some dmesg output: > > > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: > > autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: > > speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: > > hp_outs=1 (0xa/0xf/0x0/0x0/0x0) > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: > > mono: mono_out=0x0 > > [ 14.192000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: > > inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 > > [ 14.196000] ALSA > > > /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: > > dac_nids=2 (0x5/0x4/0x0/0x0/0x0) > > > > Unmuted and adjusted Surround volume, but it made no difference. > > Please upload the alsa-info.sh output again. No difference in the > output but there must be a difference in the codec setting. > > Also, just to make the situation clear: > the problem is that the speaker and the rear HP don't give sound > output even if you *don't* plug in the front HP, right? > > > Takashi > > > ------------------------------ > > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > End of Alsa-devel Digest, Vol 12, Issue 70 > ****************************************** > -- Mvh, Anders

3 5

Re: [alsa-devel] Problem with DELL XPS M1530
by Anders Rønningen 21 Feb '08

21 Feb '08

Hi. I am the mentioned user with this problem. Just thought I'd give you a little more info on this problem. What wishie described was correct, except it's the internal speakers and the /left/ hp-jack that stopped working, while the right one is still ok. Like he wrote, the reason we started this debugging was to get mic sound on my system. The thing I think is worth mentioning is that with alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and the internal speakers worked for me. People in #alsa told me that the module was not loaded correctly, but whatever was loaded _almost_ worked well :-) - Anders

3 7

[alsa-devel] snd-hda-intel AD1981 - the microphone doesn't work
by Robert Gonciarz 20 Feb '08

20 Feb '08

Hi, I'm trying to activate a microphone (I have just external one) in my HP NX7300 (RU374ES) notebook (it has two jacks without internal mic) for six months. Alsamixer says that it's AD1981 chipset. The sound works great execept two things: - it's too silent when I set almost the maximum level (if you compare it with Windows XP driver) - but it's not so bad. It is said that a tothem can change some hidden settings to make it louder. - the microphone doesn't work even though I setted it in alsamiser (the settings: <capture tab> the "Mic" is red, "Mic boss" is setted with 67/67, "Capture" 80/80, Mix is blue and "-----", "Digital" 62/62, "Docking-" is blue and "----", "Internal" 67/67. The mic doesn't capture any voice at all. I was trying to load the module with different names: default, hp and toshiba works but the mic still doesn't work. lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) lspci -nv 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 103c:30a2 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f4580000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel It was tested with snd-hda-intel module from the lastest sources from your website: alsa-driver-1.0.16rc2. I'm using 2.6.24.1 kernel. At the begining I tried to compile the kernel with a module which was included to it (it was working without a mic) and then I compiled the external module from your web. It was tested with many other kernels. Can you check it please? If you need more information just email me back. Robert

4 12

[alsa-devel] Regarding pointer callback
by Pharaoh . 20 Feb '08

20 Feb '08

Hi, In Writing an ALSA driver, it is written that pointer callback is called usually from the buffer-update routine in the pcm middle layer, which is invoked when snd_pcm_period_elapsed() is called in the interrupt routine. Then the pcm middle layer updates the position and calculates the available space, and wakes up the sleeping poll threads, etc. I know from a kernel space ALSA driver, the pointer callback is called after the driver calls snd_pcm_period_elapsed() from the interrupt handler or after a period is consumed. How pointer function of a user space plugin is called? I have a user space pcm external plugin which updates the buffer counter after every period is consumed, but when will it be called? How does the ALSA lib know when to call it since there is no snd_pcm_period_elapsed() in user space. -Phraoh.

1 0

[alsa-devel] Capture and playabck together
by Emmanuel Milou 20 Feb '08

20 Feb '08

Hi all, I am developping an open-source C++ softphone based on Alsa. We used to use Portaudio but we recently decided to switch to Alsa. I am quite unexperimented in Alsa dev and I got some difficulties to make it work fine. My capture and playback devices are plughw:0,0. I am using read/write transfers. When I disable the capture, playback works fine; when I disable the playback, capture works fine. The problems occurs when I used them together. If I set hardware parameters for both, the playback sound is awful and there is no capture, and finally core dumped. If I set hardware parameters for the playback stream only, the playback works fine, but no capture, I just get an echo with an input/ouput error. Where do you think the problem comes from? Isn't it possible to set hardware configuration for playback and capture? Is there a hardware ring buffer for each stream ? Thanks for your help Manu

1 0

[alsa-devel] [PATCH 0/2] TLV320AIC3X MCLK and rate updates
by Jarkko Nikula 20 Feb '08

20 Feb '08

Hi Two patches to TLV320AIC3X SoC codec driver. First one fixes typo (?) for 64 kHz sample rate and second one adds support to 12 MHz MCLK used e.g. in Nokia N810 Internet Tablet. Patches are generated from 2.6.25-rc2-omap1 tree but they apply to alsa git and alsa-kernel hg trees as well. -- Jarkko

2 3