[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47EE317E.9030807@keyaccess.nl>
Date: Sat, 29 Mar 2008 13:09:34 +0100
From: Rene Herman <rene.herman@...access.nl>
To: Bob Tracy <rct@...s.com>
CC: Tyson Whitehead <twhitehe@....ca>, Takashi Iwai <tiwai@...e.de>,
ALSA devel <alsa-devel@...a-project.org>,
Michael Cree <mcree@...on.net.nz>,
Krzysztof Helt <krzysztof.h1@...pl>,
linux-kernel@...r.kernel.org,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
linux-alpha@...r.kernel.org
Subject: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
On 29-03-08 07:42, Bob Tracy wrote:
>>> +#ifdef CONFIG_ALPHA
>>> + if (!(status & (AUDIO1_IRQ | AUDIO2_IRQ))) {
>>> + /* status = 0; */
> Unfortunately, this does nothing to fix the ES1888 on my system. Same
> broken behavior as described previously. I'll try something else in
> the queue later today after I get some sleep...
Okay. The thing that "fixed" Tyson was disabling mmap from the driver:
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-March/006911.html
It landed him in the same situation as you though, where that "asskickd.wav"
mono, 8-bit 11025 file you sent me shows the same behaviour you reported.
This might imply you weren't using mmap to begin with. You have no horribly
obsolete alsa userland, nor an /etc/asound.conf or ~/.asoundrc?
No change with "aplay -M"? If there is a change, you'd expect it to be
Tyson's old behaviour which means blowing up the machine on subsequent
plays, so be a bit careful...
This one needs answer so as to possibly pin things down to format:
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-March/006914.html
Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists