From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Import updates from i386's i8259.c
Date: Wed, 6 Dec 2006 12:07:17 +0000 [thread overview]
Message-ID: <20061206120717.GA13744@linux-mips.org> (raw)
In-Reply-To: <20061206.115602.63741871.nemoto@toshiba-tops.co.jp>
On Wed, Dec 06, 2006 at 11:56:02AM +0900, Atsushi Nemoto wrote:
> Date: Wed, 06 Dec 2006 11:56:02 +0900 (JST)
> To: ralf@linux-mips.org
> Cc: linux-mips@linux-mips.org
> Subject: Re: [PATCH] Import updates from i386's i8259.c
> From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> Content-Type: Text/Plain; charset=us-ascii
>
> On Wed, 6 Dec 2006 01:58:18 +0000, Ralf Baechle <ralf@linux-mips.org> wrote:
> > There are some other issues with the legacy IDE on the Intel PIIX which
> > likely affect other systems such as Alpha as well. I think I solved that
> > so it's now time to tackle the IRQ stuff. Even without your i8259 stuff
> > there are some strange things going on currently:
> >
> > [...]
> > irq 7, desc: 803db360, depth: 1, count: 0, unhandled: 0
> > ->handle_irq(): 8014ff28, handle_bad_irq+0x0/0x318
> > ->chip(): 803a3d4c, 0x803a3d4c
> > ->action(): 00000000
> > IRQ_DISABLED set
> > unexpected IRQ # 7
>
> Hmm ... malta_int.c:get_int() returned 7? I have no idea, but it
> seems mips_irq_lock in malta_int.c can be replaced by i8259A_lock...
Your new patch works and also resolves this issue.
Ralf
next prev parent reply other threads:[~2006-12-06 13:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 16:23 [PATCH] Import updates from i386's i8259.c Atsushi Nemoto
2006-12-05 16:50 ` Franck Bui-Huu
2006-12-05 16:52 ` Ralf Baechle
2006-12-05 17:10 ` Franck Bui-Huu
2006-12-06 1:28 ` Atsushi Nemoto
2006-12-06 1:45 ` Ralf Baechle
2006-12-05 19:49 ` Ralf Baechle
2006-12-05 19:57 ` Ralf Baechle
2006-12-06 1:39 ` Atsushi Nemoto
2006-12-06 1:58 ` Ralf Baechle
2006-12-06 2:56 ` Atsushi Nemoto
2006-12-06 4:38 ` anemo
2006-12-06 13:17 ` Sergei Shtylyov
2006-12-06 13:48 ` Maciej W. Rozycki
2006-12-06 13:53 ` Sergei Shtylyov
2006-12-06 14:41 ` Maciej W. Rozycki
2006-12-06 15:12 ` Sergei Shtylyov
2006-12-06 15:43 ` Maciej W. Rozycki
2006-12-06 15:48 ` Sergei Shtylyov
2006-12-06 19:00 ` Maciej W. Rozycki
2006-12-06 17:03 ` Atsushi Nemoto
2006-12-06 20:32 ` Ralf Baechle
2006-12-06 12:07 ` Ralf Baechle [this message]
2006-12-06 8:40 ` Franck Bui-Huu
2006-12-07 3:17 ` Atsushi Nemoto
2006-12-07 7:34 ` Franck Bui-Huu
2006-12-07 11:50 ` Ralf Baechle
2006-12-07 13:32 ` Maciej W. Rozycki
2006-12-07 13:37 ` Ralf Baechle
2006-12-07 13:51 ` Sergei Shtylyov
2006-12-07 15:03 ` Maciej W. Rozycki
2006-12-07 15:09 ` Ralf Baechle
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=20061206120717.GA13744@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
/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