From: Tyson Whitehead <twhitehe@uwo.ca>
To: rene.herman@gmail.com, Michael Cree <mcree@orcon.net.nz>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-kernel@vger.kernel.org,
ALSA devel <alsa-devel@alsa-project.org>
Subject: [Fwd: Re: [regression] 2.6.25-rc4 snd-es18xx broken on Alpha]
Date: Tue, 01 Apr 2008 17:21:33 -0400 [thread overview]
Message-ID: <47F2A75D.9060809@uwo.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 147 bytes --]
Sorry. Bob was just saying this could be an important observation, but
it didn't get to everyone as the CC list got shortened. Cheers! -Tyson
[-- Attachment #2: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha.eml --]
[-- Type: message/rfc822, Size: 2403 bytes --]
From: Tyson Whitehead <twhitehe@uwo.ca>
To: Bob Tracy <rct@frus.com>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Tue, 01 Apr 2008 15:23:58 -0400
Message-ID: <47F28BCE.9090108@uwo.ca>
Bob Tracy wrote:
> Takashi Iwai wrote:
>> I vaguely remember about the patch... The patch below was on my local
>> tree but never pushed because of lack of testing. Does it work for
>> you?
>>
>> ---
>>
>> diff -r 82e6201fc907 sound/isa/es18xx.c
>> --- a/sound/isa/es18xx.c Mon Mar 17 14:36:24 2008 +0100
>> +++ b/sound/isa/es18xx.c Mon Mar 17 17:32:59 2008 +0100
>> @@ -765,9 +765,10 @@ static irqreturn_t snd_es18xx_interrupt(
>> /* Read Interrupt status */
>> status = snd_es18xx_mixer_read(chip, 0x7f) >> 4;
>> }
>> -#if 0
>> - else {
>> - status = 0;
>> +
>> +#ifdef CONFIG_ALPHA
>> + if (!(status & (AUDIO1_IRQ | AUDIO2_IRQ))) {
>> + /* status = 0; */
>> if (inb(chip->port + 0x0C) & 0x01)
>> status |= AUDIO1_IRQ;
>> if (snd_es18xx_mixer_read(chip, 0x7A) & 0x80)
>> @@ -777,7 +778,6 @@ static irqreturn_t snd_es18xx_interrupt(
>> status |= HWV_IRQ;
>> }
>> #endif
>> -
>> /* Audio 1 & Audio 2 */
>> if (status & AUDIO2_IRQ) {
>> if (chip->active & DAC2)
>> --
>
> The above patch doesn't make any difference for me as far as how the
> ES1888 works. I get the same broken behavior as previously described.
I wonder if the difference between Bob and I (i.e., that I can get sound
working with patching while he cannot) might be that all along I've been
using CONFIG_ALPHA_GENERIC, while he has (possibly -- he will have to
confirm this) been using CONFIG_ALPHA_MIATA.
As I mentioned in the email I just sent out, I just finished discovering
that if I compile with CONFIG_ALPHA_MIATA, I can't get sound to work no
matter what I do (patched or unpatched es18xx or sb8).
When I compile with CONFIG_ALPHA_GENERIC I can get sound working (modulo
this new "Bad page state in process 'mpg321'" thing that started
sometime after 2.6.14) with either the patched es18xx or standard sb8.
Cheers! -Tyson
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Tyson Whitehead <twhitehe@uwo.ca>
To: rene.herman@gmail.com, Michael Cree <mcree@orcon.net.nz>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-kernel@vger.kernel.org,
ALSA devel <alsa-devel@alsa-project.org>
Subject: [Fwd: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha]
Date: Tue, 01 Apr 2008 17:21:33 -0400 [thread overview]
Message-ID: <47F2A75D.9060809@uwo.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 147 bytes --]
Sorry. Bob was just saying this could be an important observation, but
it didn't get to everyone as the CC list got shortened. Cheers! -Tyson
[-- Attachment #2: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha.eml --]
[-- Type: message/rfc822, Size: 2403 bytes --]
From: Tyson Whitehead <twhitehe@uwo.ca>
To: Bob Tracy <rct@frus.com>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Tue, 01 Apr 2008 15:23:58 -0400
Message-ID: <47F28BCE.9090108@uwo.ca>
Bob Tracy wrote:
> Takashi Iwai wrote:
>> I vaguely remember about the patch... The patch below was on my local
>> tree but never pushed because of lack of testing. Does it work for
>> you?
>>
>> ---
>>
>> diff -r 82e6201fc907 sound/isa/es18xx.c
>> --- a/sound/isa/es18xx.c Mon Mar 17 14:36:24 2008 +0100
>> +++ b/sound/isa/es18xx.c Mon Mar 17 17:32:59 2008 +0100
>> @@ -765,9 +765,10 @@ static irqreturn_t snd_es18xx_interrupt(
>> /* Read Interrupt status */
>> status = snd_es18xx_mixer_read(chip, 0x7f) >> 4;
>> }
>> -#if 0
>> - else {
>> - status = 0;
>> +
>> +#ifdef CONFIG_ALPHA
>> + if (!(status & (AUDIO1_IRQ | AUDIO2_IRQ))) {
>> + /* status = 0; */
>> if (inb(chip->port + 0x0C) & 0x01)
>> status |= AUDIO1_IRQ;
>> if (snd_es18xx_mixer_read(chip, 0x7A) & 0x80)
>> @@ -777,7 +778,6 @@ static irqreturn_t snd_es18xx_interrupt(
>> status |= HWV_IRQ;
>> }
>> #endif
>> -
>> /* Audio 1 & Audio 2 */
>> if (status & AUDIO2_IRQ) {
>> if (chip->active & DAC2)
>> --
>
> The above patch doesn't make any difference for me as far as how the
> ES1888 works. I get the same broken behavior as previously described.
I wonder if the difference between Bob and I (i.e., that I can get sound
working with patching while he cannot) might be that all along I've been
using CONFIG_ALPHA_GENERIC, while he has (possibly -- he will have to
confirm this) been using CONFIG_ALPHA_MIATA.
As I mentioned in the email I just sent out, I just finished discovering
that if I compile with CONFIG_ALPHA_MIATA, I can't get sound to work no
matter what I do (patched or unpatched es18xx or sb8).
When I compile with CONFIG_ALPHA_GENERIC I can get sound working (modulo
this new "Bad page state in process 'mpg321'" thing that started
sometime after 2.6.14) with either the patched es18xx or standard sb8.
Cheers! -Tyson
next reply other threads:[~2008-04-01 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 21:21 Tyson Whitehead [this message]
2008-04-01 21:21 ` [Fwd: Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha] Tyson Whitehead
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=47F2A75D.9060809@uwo.ca \
--to=twhitehe@uwo.ca \
--cc=alsa-devel@alsa-project.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=rene.herman@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.