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

[alsa-devel] Effect of CONFIG_SND_PCM_OSS_PLUGINS
by Adrian McMenamin 27 Jul '07

27 Jul '07

Unless CONFIG_SND_PCM_OSS_PLUGINS is set then with my driver the userspace (and OSS) app mpg123 doesn't work properly - not outputting any sound. Is this likely to be a problem with my driver or with the app? Adrian

3 7

[alsa-devel] VT1618 driver
by Niels Gram Jeppesen 27 Jul '07

27 Jul '07

Hi, I have a VIA CN1000G mini-ITX board with a VT1618 that I would like to have up and running with sound next week. I see (https://bugtrack.alsa-project.org/wiki/wikka.php?wakka=VT1618&show_comments…) that there exist a still unreleased driver for the chip. If possible, I would like to play arround with that driver next week. Best regards and thanks in advance, Niels Gram Jeppesen

1 0

[alsa-devel] Intel HDA Driver - Bug
by Steven King 26 Jul '07

26 Jul '07

Hi, I have been trying to get the sound on my Dell Inspiron 1720 laptop running under Debian Etch (STAC 9205). Originally, I could only get sound through the main speakers, there was no headphone sound or mic. I downloaded the latest alsa-drivers package (1.0.14), compiled it and installed it. I received the following messages (and the device would not register itself): hda_intel: azx_get_response timeout, switching to polling mode... hda_intel: azx_get_response timeout, switching to single_cmd mode... I started digging into the driver code and found an issue with one of the routines going outside an array. The offending code is (all in patch_sigmatel): static void stac92xx_set_config_regs(struct hda_codec *codec) { // ... for (i = 0; i < spec->num_pins; i++) { // ... } And in: static int patch_stac9205(struct hda_codec *codec) { // .. spec->num_pins = 14 ; //ERROR // .. } However, there are only 12 pins with 12 corresponding NIDs and default configuration so in stac92xx_set_config_regs it accesses spec->pin_configs[i] and spec->pin_nids[i] outside of bounds. Fix: Add a define (STAC_9205_MAX_PINS = 12) and use for array defines and num_pins. The driver loads now, but I still only have sound out the main speaker. If I get rid of the configuration sent to the chipset altogether. I get sound through Headphone and Speakers (with detect working on HP), but still no MIC. How can I add support for my Dell as I don't know the configuration to use or am I missing something here? Thanks, Steve

1 0

[alsa-devel] [patch] asihpi: mmap and link streams
by Eliot Blennerhassett 26 Jul '07

26 Jul '07

Greetings, asihpi version 3.07.13 : Enable MMAP dma capable cards. Enable linked streams for cards that have hardware support for this. Add TLV for level and volume controls. Register asihpi class for HPI part of driver Add documentation, remove unused code. Signed-off-by: Eliot Blennerhassett <eblennerhassett(a)audioscience.com> ---- Patch (4798 lines) is here: http://audioscience.com/internet/download/beta/alsa_driver3349_asihpi30713.… Matching firmware is here: http://audioscience.com/internet/download/firmware/dspbins30713.zip FYI: Original source package here: http://audioscience.com/internet/download/hpklinux-3.07.13.tar.bz2 asihpi.c | 1517 ++++++++++++++++++++++++++------------------------- Implement MMAP and linked streams. Merge some capture and playback functions Add dB TLV for level and volume controls hpi6000.c | 7 Clean hpi6205.c | 498 +++++++++------- Changes to allow attaching external DMA buffer (for ALSA) hpidebug.c | 67 +- hpidebug.h | 349 +++++------ Changes to support unicode hpimod.c | 283 ++------- Cleanup, add class registration hpimsgx.c | 50 + Add 2 new subsys functions hpios_linux_kernel.c | 36 - hpios_linux_kernel.h | 15 Minor debug changes. Add pci dev ptr to allow alsa to allocate dma buffer hpi.h | 54 - hpi56301.c | 1 hpidspcd.c | 2 hpifunc.c | 121 ++-- Documentation updates 13 files changed, 1506 insertions(+), 1494 deletions(-)

2 1

[alsa-devel] ALC262 - HDA-Intel
by Andy 26 Jul '07

26 Jul '07

I have a ALC262 hda-intel card which doesn't function quite correctly. Details can be found at https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/110145 I got bored of waiting for it to be fixed, and had a go myself. My knowledge of ALSA is very limited, but nevertheless it was really simple to add my device ids to the quirks list in the patch_realtek.c file - eg: ... SND_PCI_QUIRK(0x104d, 0x900e, "Sony ASSAMD", ALC262_SONY_ASSAMD), SND_PCI_QUIRK(0x104d, 0x1f00, "Sony ASSAMD", ALC262_SONY_ASSAMD), /* My card... */ SND_PCI_QUIRK(0x104d, 0x820f, "Sony ASSAMD", ALC262_SONY_ASSAMD), ... I found by trial and error that ALC262_SONY_ASSAMD almost works. Connecting headphones disables built-in speakers and unplugging them re-enables them. However, something does not get initialised until this is done. That is, every bootup using ALC262_SONY_ASSAMD, I must plug in and remove my headphones before the device is initialised properly. Until this is done, I get no sound and the little GUI mixer in XFCE doesn't show the list of supported outputs on the device. I'm posting this to the devel list as I'm more interested the code side of things rather than actually having working sound :) Thanks Andy. ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.ht…

2 7

[alsa-devel] [PATCH 1/2] Add SPI devices to ALSA Kconfig and Makefile
by Hans-Christian Egtvedt 26 Jul '07

26 Jul '07

This patch adds SPI devices in the ALSA diretory, including the Kconfig and Makefile. Signed-off-by: Hans-Christian Egtvedt <hcegtvedt(a)atmel.com> --- sound/Kconfig | 6 +++++- sound/Makefile | 3 ++- sound/spi/Kconfig | 6 ++++++ sound/spi/Makefile | 2 ++ 4 files changed, 15 insertions(+), 2 deletions(-) create mode 100644 sound/spi/Kconfig create mode 100644 sound/spi/Makefile diff --git a/sound/Kconfig b/sound/Kconfig index 9ea4738..9217739 100644 --- a/sound/Kconfig +++ b/sound/Kconfig @@ -63,9 +63,13 @@ source "sound/aoa/Kconfig" source "sound/arm/Kconfig" +if SPI +source "sound/spi/Kconfig" +endif + source "sound/mips/Kconfig" -# the following will depend on the order of config. +# tee following will depend on the order of config. # here assuming USB is defined before ALSA source "sound/usb/Kconfig" diff --git a/sound/Makefile b/sound/Makefile index b7c7fb7..581ea5e 100644 --- a/sound/Makefile +++ b/sound/Makefile @@ -5,7 +5,8 @@ obj-$(CONFIG_SOUND) += soundcore.o obj-$(CONFIG_SOUND_PRIME) += sound_firmware.o obj-$(CONFIG_SOUND_PRIME) += oss/ obj-$(CONFIG_DMASOUND) += oss/ -obj-$(CONFIG_SND) += core/ i2c/ drivers/ isa/ pci/ ppc/ arm/ synth/ usb/ sparc/ parisc/ pcmcia/ mips/ soc/ +obj-$(CONFIG_SND) += core/ i2c/ drivers/ isa/ pci/ ppc/ arm/ synth/ usb/ \ + sparc/ spi/ parisc/ pcmcia/ mips/ soc/ obj-$(CONFIG_SND_AOA) += aoa/ # This one must be compilable even if sound is configured out diff --git a/sound/spi/Kconfig b/sound/spi/Kconfig new file mode 100644 index 0000000..60fbb2a --- /dev/null +++ b/sound/spi/Kconfig @@ -0,0 +1,6 @@ +#SPI drivers + +menu "SPI devices" + depends on SND != n + +endmenu diff --git a/sound/spi/Makefile b/sound/spi/Makefile new file mode 100644 index 0000000..30d8ec9 --- /dev/null +++ b/sound/spi/Makefile @@ -0,0 +1,2 @@ +# Makefile for SPI drivers + -- 1.5.2.3

3 20

[alsa-devel] How to get correct midi timings from ALSA using the library only
by Carlo Florendo 26 Jul '07

26 Jul '07

Hi, (1) I've written a command line MIDI sequencer for lightweight systems and am successful in making it work using the ALSA queue API. However, one drawback of the API is its lack of callback functions. I wish to be able to track events as they are drained by the queue. (2) I know and have successfully worked on a work around whereby the application itself subscribes to the output port so as to see events as they are played. However, I wish to be able to make the sequencer or player work without the use of the ALSA queue nor the workaround in (2). Here's the pseudo-code of the relevant MIDI player routine: for (i = 0; i < number_of_events; i++) { usleep(event[i].delta_time_in_microseconds); output_and_drain_event(event[i]); } This routine gives a non-bearable latency on 2.4 kernels but not so much on 2.6 kernels. How could I get the app to <u|nano>sleep() in the most accurate way in userspace without using the ALSA queue nor the extra subscription to an output port? Or, is there a drain or output routine that supports callbacks? If so, I will be grateful if you could point them out. I seem not to find any output callback routine under the docs. Thank you very much. Best Regards, Carlo -- Carlo Florendo Softare Engineer/Network Co-Administrator Astra Philippines Inc. UP-Ayala Technopark, Diliman 1101, Quezon City Philippines http://www.astra.ph -- The Astra Group of Companies 5-3-11 Sekido, Tama City Tokyo 206-0011, Japan http://www.astra.co.jp

3 9

[alsa-devel] dmix and sounds less than 64kb
by Aaron "Caustik" Robinson 25 Jul '07

25 Jul '07

We have been having one heck of a time tracking down the cause of some ALSA audio playback issues. It appears that any time we play a very short sound (<64kb), either the sound doesn't play at all, or only a fragment of it plays. We haven't had much luck finding a solution to this issue, then I found this thread on the history of this email group: http://mailman.alsa-project.org/pipermail/alsa-devel/2007-April/000526.html Our problem is pretty much exactly like his issues relating to <64k sounds. My question is - has anybody else run into this problem? To the OP of the above thread, if you're still listening - did you ever find a solution to your problem? I'd be very interested to hear any help you can provide. Thanks much, caustik

3 9

[alsa-devel] Testing play and record simultaneously.
by Pharaoh . 25 Jul '07

25 Jul '07

Very naive questions. 1. I want to test the recording using arecord, but how will I make sure that the data is actually being recorded? I mean is there any way of storing the data recorded, say in a file? Off course there must be some way, its just that I dont know it. Can some one throw some light on this? 2. Also, I want to test my card in full duplex mode as well, i.e. playing and recording simultaneously. How can test this using aplay and arecord? -Pharaoh.

2 1

[alsa-devel] [PATCH] CA0106 SPI DAC powerdown
by Trent Piepho 25 Jul '07

25 Jul '07

Here are three patches for the CA0106 SPI DAC. The first patch powers down the DACs (other than the front dac) when they are not in use. The front dac serves as the output for the line-in pass-through / capture feedback, so it's not powered down. The second patch adds a bunch of symbol names for SPI registers, and converts the existing init sequence from magic numbers to these names. The sequence doesn't change at all. The third patch cleans up some unnecessary repeated sets to the same registers in the SPI init sequence. Of course, I have tested all these patches and they work.

2 1