From: Rene Herman <rene.herman@keyaccess.nl>
To: Bob Tracy <rct@frus.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
Michael Cree <mcree@orcon.net.nz>,
Krzysztof Helt <krzysztof.h1@wp.pl>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha@vger.kernel.org
Subject: Re: [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Wed, 12 Mar 2008 20:34:36 +0100 [thread overview]
Message-ID: <47D8304C.3090005@keyaccess.nl> (raw)
In-Reply-To: <20080312144021.3FE57DBA2@gherkin.frus.com>
On 12-03-08 15:40, Bob Tracy wrote:
> Well, I built a 2.6.22 kernel last night, and in tests this morning
> there's no difference relative to the ALSA behavior seen in 2.6.25-rc4.
Okay. If someone is tracking this as a 2.6.25 regresion, it can be stricken
of that list.
> Since the question came up (or was strongly implied), I took the time to
> check the status of IRQ 5 in /proc/interrupts, and while it shows up as
> assigned to the sound card, no interrupts are being seen/processed by
> the es18xx driver.
That is indeed what it soundeed like, or the first bit at least.
> When I remove the snd-es18xx module and install the snd-sb8 module with
> the same parameters (other than there's no second DMA channel), the
> /proc/interrupts counter for IRQ 5 increments as expected when playing
> sound files.
What does cat /proc/config.gz | grep CONFIG_ALPHA_ say? Miuchael, and for
you? For some Alpha configs, arch/alpha/kernel/es1888.c is compiled and for
some not. I expect for you (Bob) it's compiled in? And Michael?
Rene.
next prev parent reply other threads:[~2008-03-12 19:34 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 3:58 [regression] 2.6.25-rc4 snd-es18xx broken on Alpha Bob Tracy
2008-03-09 15:34 ` Ivan Kokshaysky
2008-03-09 23:57 ` Bob Tracy
2008-03-10 7:34 ` Michael Cree
2008-03-10 15:17 ` Rene Herman
2008-03-10 15:21 ` Rene Herman
2008-03-10 16:21 ` Bob Tracy
2008-03-10 16:56 ` Rene Herman
2008-03-10 17:14 ` Takashi Iwai
2008-03-10 19:29 ` [alsa-devel] " Rene Herman
2008-03-10 22:22 ` Bob Tracy
2008-03-10 22:33 ` Rene Herman
2008-03-11 14:07 ` [alsa-devel] " Bob Tracy
2008-03-11 15:17 ` Rene Herman
2008-03-11 18:08 ` Bob Tracy
2008-03-11 20:00 ` [alsa-devel] " Michael Cree
2008-03-11 20:34 ` Bob Tracy
2008-03-12 14:40 ` Bob Tracy
2008-03-12 19:34 ` Rene Herman [this message]
2008-03-12 20:31 ` [alsa-devel] " Bob Tracy
2008-03-12 21:12 ` Rene Herman
2008-03-13 4:24 ` Bob Tracy
2008-03-17 22:00 ` Rene Herman
2008-03-18 3:24 ` [alsa-devel] " Bob Tracy
2008-03-18 3:54 ` Michael Cree
2008-03-23 10:40 ` Michael Cree
2008-03-24 18:15 ` Rene Herman
2008-03-24 23:56 ` Michael Cree
2008-03-25 0:29 ` [alsa-devel] " Rene Herman
2008-03-25 1:22 ` Michael Cree
2008-03-25 2:22 ` Rene Herman
2008-03-30 5:18 ` Bob Tracy
2008-03-30 10:02 ` Michael Cree
2008-03-30 9:13 ` [alsa-devel] " Michael Cree
2008-03-25 2:46 ` Rene Herman
2008-03-30 21:07 ` Bob Tracy
2008-03-30 21:11 ` Michael Cree
2008-03-30 21:18 ` Bob Tracy
2008-03-30 4:24 ` Bob Tracy
2008-03-30 22:09 ` [alsa-devel] " Bob Tracy
2008-03-14 13:13 ` Bob Tracy
2008-03-15 1:18 ` Tyson Whitehead
2008-03-17 22:04 ` Rene Herman
2008-03-18 13:55 ` Tyson Whitehead
2008-03-18 22:57 ` Rene Herman
[not found] ` <s5hskypnwp8.wl%tiwai@suse.de>
2008-03-18 14:16 ` Tyson Whitehead
2008-03-29 6:42 ` Bob Tracy
2008-03-29 12:09 ` [alsa-devel] " Rene Herman
2008-03-30 16:14 ` Ivan Kokshaysky
2008-03-30 21:17 ` Michael Cree
2008-03-30 20:24 ` [alsa-devel] " Bob Tracy
2008-03-12 22:48 ` Rafael J. Wysocki
2008-03-23 9:48 ` Michael Cree
2008-03-11 5:36 ` Bob Tracy
2008-03-10 15:08 ` Rene Herman
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 23:33 Bob Tracy
2008-04-01 19:07 [alsa-devel] " Rene Herman
2008-04-01 20:32 ` Bob Tracy
2008-04-01 20:26 [alsa-devel] " Bob Tracy
2008-04-01 21:02 ` Michael Cree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47D8304C.3090005@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=ink@jurassic.park.msu.ru \
--cc=krzysztof.h1@wp.pl \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=rct@frus.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).