From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@frus.com>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
Takashi Iwai <tiwai@suse.de>,
ALSA devel <alsa-devel@alsa-project.org>,
linux-kernel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha@vger.kernel.org, Krzysztof Helt <krzysztof.h1@wp.pl>
Subject: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Sun, 23 Mar 2008 22:48:38 +1300 [thread overview]
Message-ID: <47E62776.9000107@orcon.net.nz> (raw)
In-Reply-To: <ED0F0070-B876-4D8B-8F88-879E01AB4326@orcon.net.nz>
Michael Cree wrote:
>> I can't tell you exactly *when* it used to work, or even *if* it did
>> with 2.6 kernels. I'll try to explain...
>>
>> Sometime back in the 2.6.14 to 2.6.16 timeframe there was an issue with
>> the ALSA driver not recognizing interrupts (causing looping)
>
> Yes, the ESS1888 driver failed to work on Alpha about the 2.6.14 to
> 2.6.16 kernel. It came right with alsa release 1.0.13 (IIRC) and I
> have been running the ESS1888 driver on an Alpha XP1000 without problems
> for about a year.
After thinking about this more, I am wondering if the appearance of the
ESS1888 not working then coming right at about the 1.0.13 alsa release
is an artefact of when I shifted from mainly using the PWS600au to
mainly using the XP1000, and then trying out the es18xx driver at some
stage, finding it works on the XP1000, but forgetting that it was on the
PWS600au that it didn't work. It's in the distant past now and memory
is getting hazy...
Michael.
next prev parent reply other threads:[~2008-03-23 9:48 UTC|newest]
Thread overview: 61+ 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
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 [this message]
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 18:07 ` [alsa-devel] " Tyson Whitehead
2008-04-01 18:29 ` Rene Herman
2008-04-01 18:31 ` Rene Herman
2008-04-01 18:34 ` Rene Herman
2008-04-01 19:07 ` Rene Herman
2008-04-01 20:26 ` Bob Tracy
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=47E62776.9000107@orcon.net.nz \
--to=mcree@orcon.net.nz \
--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=rct@frus.com \
--cc=rene.herman@keyaccess.nl \
--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).