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 18:04:17 -0700 [thread overview]
Message-ID: <3B4E4911.25616E3@mvista.com> (raw)
In-Reply-To: 20010713024108.A26493@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Thu, Jul 12, 2001 at 04:55:27PM -0700, Jun Sun wrote:
>
> > 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?
>
> Well, do you actually build kernels for multiple boards that need this?
The answer is actually yes.
What is happening in embedded world is people often derive their boards from
another board (probably reference board). Sometimes the difference between
those two boards are very small (but still have difference such as in
interrupt routing). It will then become interesting to share most of the code
and leave some other code hookable.
Another scenario is sometimes vendors builds a base board which can plug in
multiple different daughter boards. In many cases it is desirable to build
one kernel for the same "base board".
That is the need I have seen so far.
Jun
prev parent reply other threads:[~2001-07-13 1:07 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
2001-07-13 0:41 ` Ralf Baechle
2001-07-13 1:04 ` Jun Sun [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=3B4E4911.25616E3@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