Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@mvista.com>
To: carlson@sibyte.com
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: irq.c
Date: Fri, 09 Feb 2001 11:07:58 -0800	[thread overview]
Message-ID: <3A84400E.82CEA4B@mvista.com> (raw)
In-Reply-To: 0102091101190P.01909@plugh.sibyte.com

Justin Carlson wrote:
> 
> On Fri, 09 Feb 2001, Pete Popov wrote:
> > There's a dozen copies of "irq.c", and a few more files that do the same
> > thing but are named differently. The irq.c in arch/mips/kernel doesn't
> > seem to be used by any system.  The PowerPC also has lots of variants
> > also, but I believe they have a single irq.c file that all systems use.
> > So I guess my question is, is anyone using arch/mips/kernel/irq.c, and
> > does everyone plan on moving to that file (which seems like the right
> > thing to do).
> >
> 
> I've noticed that arch/i386/kernel/irq.c has this note on it:
> 
> /*
>  * (mostly architecture independent, will move to kernel/irq.c in 2.5.)
>  *
>  * IRQs are in fact implemented a bit like signal handlers for the kernel.
>  * Naturally it's not a 1:1 relation, but there are similarities.
>  */
> 
> My internal code uses this as a template, in anticipation of this move;
> assuming this will happen in 2.5, does it make sense to do an intermediate move
> to a common mips/kernel/irq.c?
> 
> If it does, I'd like to see mips/kernel/irq.c updated to more closely match the
> i386 version, but I'm curious what other people think.

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.  

Pete

  reply	other threads:[~2001-02-09 19:08 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   ` Pete Popov [this message]
2001-02-13  6:18     ` irq.c 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=3A84400E.82CEA4B@mvista.com \
    --to=ppopov@mvista.com \
    --cc=carlson@sibyte.com \
    --cc=linux-mips@oss.sgi.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