From: Ralf Baechle <ralf@oss.sgi.com>
To: Pete Popov <ppopov@mvista.com>
Cc: carlson@sibyte.com, "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: irq.c
Date: Mon, 12 Feb 2001 22:18:25 -0800 [thread overview]
Message-ID: <20010212221825.B2239@bacchus.dhis.org> (raw)
In-Reply-To: <3A84400E.82CEA4B@mvista.com>; from ppopov@mvista.com on Fri, Feb 09, 2001 at 11:07:58AM -0800
On Fri, Feb 09, 2001 at 11:07:58AM -0800, Pete Popov wrote:
> Thanks for pointing that out. If all architectures will move to
> kernel/irq.c, then it probably makes sense to wait. At first glance,
> mips/kernel/irq.c seems pretty close to i386/kernel/irq.c -- certainly a
> lot closer than many of the other copies.
It was derived from a fairly recent copy of the x86 irq.c; running out of
time I never completed the rewrite. The idea is to implement some kind
of modular interrupt mechanism which allows us to have a single piece of
code in the MIPS kernel that knows how to handle i8259 interrupt, a single
piece of code to handle GT64120 interrupts etc. Not like the current mess
which duplicates code ad infinitum.
Aside it's also going to make the RTLinux fraction happy.
Ralf
prev parent reply other threads:[~2001-02-14 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 18:51 irq.c Pete Popov
2001-02-09 18:56 ` irq.c Justin Carlson
2001-02-09 19:07 ` irq.c Pete Popov
2001-02-13 6:18 ` Ralf Baechle [this message]
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=20010212221825.B2239@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox