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

[alsa-devel] Input/output error - Confusion regarding period size and interrupts
by Pharaoh . 16 Jul '07

16 Jul '07

Hi The hardware I am working on expects 8K bytes to be DMAed before giving an interrupt. Only after a block of 8K bytes is DMAed, I get an end of the block interrupt and I enqueue next 8K bytes for processing. The params look like these: static snd_pcm_hardware_t snd_omap_alsa_playback = { .info = (SNDRV_PCM_INFO_INTERLEAVED | SNDRV_PCM_INFO_PAUSE | SNDRV_PCM_INFO_RESUME | SNDRV_PCM_INFO_MMAP_VALID | SNDRV_PCM_INFO_MMAP), .formats = (SNDRV_PCM_FMTBIT_S16_LE), .rates = (SNDRV_PCM_RATE_44100 | SNDRV_PCM_RATE_48000 ), .rate_min = 44100, .rate_max = 48000, .channels_min = 2, .channels_max = 2, .buffer_bytes_max = 8192*8, .period_bytes_min = 32, .period_bytes_max = 8 * 1024, .periods_min = 2, //ping pong buffer .periods_max = 128, .fifo_size = 0, }; I just copied it from another driver ;-). But now I am getting an input/output error after first block of data i.e. 8K bytes are DMAed. Does it have anything to do with the above struct? I have discussed this earlier too, but now attacking it once again after long gap. -pharaoh.

1 1

[alsa-devel] [Alsa-devel] xrun problem
by Gao, Jonathan 16 Jul '07

16 Jul '07

Hi, I am writing a PCM driver on a Soc for 2.6.10 kernel. The test code I'm using is from alsa-lib-1.0.6rc1/test/pcm.c. The runtime log gives me like this... ----------------------------------------------------------------- open callback: hw params callback: alloc result = 1, buffer bytes = 4608 /* --------- HW params ------------- */ format = 2, rate = 44100, channels= 2, period_size = 288, periods = 4, buffer_size = 1152 prepare callback /* --------- Runtime Info ---------- */ state = 1 (SNDRV_PCM_STATE_SETUP), hw_ptr = 0, appl_ptr = 0, avail_min = 288 avail_max = 0, hw_ptr_base = 0, hw_ptr_interrupt = 0 trigger callback: START Codec Do Copy: /* --------- Runtime Info ---------- */ state = 3 (SNDRV_PCM_STATE_RUNNING), hw_ptr = 0, appl_ptr = 1152, avail_min = 288 avail_max = 0, hw_ptr_base = 0, hw_ptr_interrupt = 0 pointer callback: hw pointer: 288 (return value of pointer callback) Codec Do Copy: /* --------- Runtime Info ---------- */ state = 3 (SNDRV_PCM_STATE_RUNNING), hw_ptr = 288, appl_ptr = 1152, avail_min = 288 avail_max = 288, hw_ptr_base = 0, hw_ptr_interrupt = 288 pointer callback: hw pointer: 576 (return value of pointer callback) Codec Do Copy: /* --------- Runtime Info ---------- */ state = 3 (SNDRV_PCM_STATE_RUNNING), hw_ptr = 576, appl_ptr = 1152, avail_min = 288 avail_max = 576, hw_ptr_base = 0, hw_ptr_interrupt = 576 pointer callback: hw pointer: 864 (return value of pointer callback) Codec Do Copy: /* --------- Runtime Info ---------- */ state = 3 (SNDRV_PCM_STATE_RUNNING), hw_ptr = 864, appl_ptr = 1152, avail_min = 288 avail_max = 864, hw_ptr_base = 0, hw_ptr_interrupt = 864 pointer callback: hw pointer: 0 (return value of pointer callback) trigger callback: STOP prepare callback /* --------- Runtime Info ---------- */ state = 4 (SNDRV_PCM_STATE_XRUN), hw_ptr = 1152, appl_ptr = 1152, avail_min = 288 avail_max = 1152, hw_ptr_base = 1152, hw_ptr_interrupt = 1152 ----------------------------------------------------------------- The kernel hangs after prepare callback, from strace, I can see a endless ioctl(4, ..., ...) repeated. Does anyone have a few pointers on what is going wrong? Best Regards, Jonathan

2 1

Re: [alsa-devel] [PATCH] Fix request_irq error handling
by Ash Willis 16 Jul '07

16 Jul '07

Hah, um, ignore me. It seems that my c needs some work ;) In if(some_expression), I always though it is true if the expression is > 0, not != 0. If anything, that was a CodingStyle patch because it lets us see exactly what we're getting from request_irq but I can see that it is totally unnecessary :) > ----- Original Message ----- > From: "Ash Willis" <ashwillis(a)programmer.net> > To: alsa-devel(a)alsa-project.org > Subject: [alsa-devel] [PATCH] Fix request_irq error handling > Date: Sat, 14 Jul 2007 02:29:19 -0500 > > > request_irq returns 0 on success and a negative code on failure. > Many ALSA drivers incorrectly check for failure by testing for a > positive code instead of a negative one. > > Signed-Off-By: Ash Willis <ashwillis(a)programmer.net> > > > -- > We've Got Your Name at http://www.mail.com! > Get a FREE E-mail Account Today - Choose From 100+ Domains > << request_irq_error_handling.patch >> > > _______________________________________________ > 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

2 1

Re: [alsa-devel] No sound on Medion laptop (intel 82801G)
by albox＠free.fr 16 Jul '07

16 Jul '07

I have added a note for this bug on : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3160 I'm not really sure but it seems that the file /etc/modprobe.d/alsa-base is not loaded. http://ubuntuforums.org/showthread.php?p=3026300#post3026300 Any idea ? Thanks

1 0

[alsa-devel] Install of alsa 1.0.14.final on Fedora 7
by stan 15 Jul '07

15 Jul '07

On Fri, 13 Jul 2007 08:53:47 -0700 tdavis(a)dsl-only.net wrote: > For RPM based systems, I have a build environment for the drivers, > libs, and utils packages at > http://members.dsl-only.net/~tdavis/my-build.tar.bz2. You need to > be root to build them, but they won't interfere with your rpm > distribution. THe driver rpm will also make a backup of your > current drivers prior to installation. > > Tobin > Hi Tobin, I unpacked the archive and typed make. It created 4 RPMs. Two of them installed, alsa-lib and alsa-lib-devel. When I run a test on the drivers rpm, there are conflicts with the kernel headers already on the box. And I have no sound now, except in the audio configuration screen which is using the 14.rc3 packages. The packages are named with rh7 instead of fc7 as well. Do I have to run make install to get everything working, or is the header incompatability in the drivers a show stopper? Thanks.

2 5

[alsa-devel] MOTU PCI-424
by Per Eriksson 14 Jul '07

14 Jul '07

Hello, After talking to Jonathan Woithe about the development done to support MOTUs product families, Jonathan and I have reached the conclusion that ALSA support for the PCI-424 series of cards would mean a great benefit for Linux users to get high quality audio at a fair price. The PCI-424 card is used to drive the following products: MOTU 2408mk3 MOTU HD192 MOTU 24I/O The work will start this autumn, as soon as I get everything set-up, and the progress will be published on https://erinet.se/alsa/motu_pci_424/pci-424 specification.pdf The actual driver will for me be a later issue to solve, I hope to gather some understanding by reading the list and look through the releases. However, I would like some more information on how the Matrix is supposed to be used in the wiki system. Are the vendor pages only for supported devices, or also for devices concidered for being supported? Thanks, Per

1 0

[alsa-devel] [PATCH] Fix request_irq error handling
by Ash Willis 14 Jul '07

14 Jul '07

request_irq returns 0 on success and a negative code on failure. Many ALSA drivers incorrectly check for failure by testing for a positive code instead of a negative one. Signed-Off-By: Ash Willis <ashwillis(a)programmer.net> -- We've Got Your Name at http://www.mail.com! Get a FREE E-mail Account Today - Choose From 100+ Domains

1 0

[alsa-devel] [PATCH] Add quirks for HP dx2200 and dx2250
by Claudio Matsuoka 14 Jul '07

14 Jul '07

This patch adds quirks for HP dx2200 and dx2250. They use the standard configuration for 3-stack ALC862.

1 0

[alsa-devel] Setting audio channels on ICH5 with SALSA
by Fausto Carvalho Marques SIlva 13 Jul '07

13 Jul '07

Setting audio channels on ICH5 with SALSA generates and: EINVAL Numbers of channels is 1. Does anyone have some ideias?? ( on ICH6 and ICH7 works well) thanks... Fausto Carvalho Marques Silva

3 6

[alsa-devel] [PATCH] Add quirk for HP Samba (ALC888)
by Claudio Matsuoka 13 Jul '07

13 Jul '07

Hi, This patch fixes 5.1 surround output for the HP Samba using the same quirk as the HP Lucknow. If HP machines are uniform in their wiring, I think we should rename ALC888_HP_NETTLE to ALC888_6ST_HP and ALC888_HP_LUCKNOW to ALC888_3ST_HP for generic HP 6stack and 3stack configurations. I'll probably receive more HP machines soon, so I'll see if this is the case. Best regards, Claudio

2 3