From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Phil Thompson <Phil.Thompson@pace.co.uk>,
"'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: Moving from old-irq.c
Date: Thu, 12 Jul 2001 16:55:27 -0700 [thread overview]
Message-ID: <3B4E38EF.3D3FF73E@mvista.com> (raw)
In-Reply-To: 20010713013054.A24695@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Wed, Jul 11, 2001 at 01:16:56PM +0100, Phil Thompson wrote:
>
> > Is there any documentation around that describes how to move from interrupt
> > code based on old-irq.c to the new code? Or any other hints or suggestions.
>
> Take a look at arch/mips/sgi/indy_int.c but there are more examples.
>
Under ddb5xxx/ directory there is an example of doing cascading portable IRQ
controllers. The irq_cpu.c file really should be shared by all common r4k
style CPUs.
> You'll have to provide
> an init_IRQ()
Ralf, I think we should have a common init_IRQ() in arch/mips/kernel, which
will then call (*setup_irq)(). This way it is easier to build a kernel for
multiple boards. It is also more compatible with the current arrangment.
What do you think?
Jun
next prev parent reply other threads:[~2001-07-12 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 12:16 Moving from old-irq.c Phil Thompson
2001-07-12 23:30 ` Ralf Baechle
2001-07-12 23:55 ` Jun Sun [this message]
2001-07-13 0:41 ` Ralf Baechle
2001-07-13 1:04 ` Jun Sun
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=3B4E38EF.3D3FF73E@mvista.com \
--to=jsun@mvista.com \
--cc=Phil.Thompson@pace.co.uk \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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