From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jim Potter <jrp@wvi.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: question from linuxppc group
Date: Tue, 25 Sep 2001 23:36:19 +0200 [thread overview]
Message-ID: <20010925213619.29454@smtp.adsl.oleane.com> (raw)
>We have a host bridge (plus PIC, mem ctlr, etc.) that is essentially
>identical
>for ppc and mips. Where is the best place to put the code since we
>don't want to
>duplicate it for both architectures?
Well, most of the PCI & interrupt frameworks are mostly arch specific.
I can't tell for MIPS, but the way you setup a PCI host bridge on PPC
was written by Paulus and me without looking at MIPS.
I don't think there is real need to have common code here. Maybe some
common definitions (register defs for example) could go into a linux/*.h
file.
Ben.
next reply other threads:[~2001-09-25 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 21:36 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 20:02 question from linuxppc group Jim Potter
2001-09-25 21:35 ` Benjamin Herrenschmidt
2001-09-25 21:42 ` James Simmons
2001-09-25 21:54 ` Tom Rini
2001-09-25 23:39 ` Eyal Lebedinsky
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=20010925213619.29454@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=jrp@wvi.com \
--cc=linux-kernel@vger.kernel.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