From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 25 Sep 2001 17:34:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 25 Sep 2001 17:34:26 -0400 Received: from s2.relay.oleane.net ([195.25.12.49]:12818 "HELO s2.relay.oleane.net") by vger.kernel.org with SMTP id ; Tue, 25 Sep 2001 17:34:08 -0400 From: Benjamin Herrenschmidt To: Jim Potter Cc: Subject: Re: question from linuxppc group Date: Tue, 25 Sep 2001 23:35:57 +0200 Message-Id: <20010925213557.7782@smtp.adsl.oleane.com> In-Reply-To: <3BB0E2F2.CD668D18@wvi.com> In-Reply-To: <3BB0E2F2.CD668D18@wvi.com> X-Mailer: CTM PowerMail 3.0.8 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >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 me and Paulus 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.