From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 6 Jan 2004 15:45:45 +0100 To: Geert Uytterhoeven Cc: Sven Luther , Benjamin Herrenschmidt , linuxppc-dev list , Rob Baxter Subject: Re: multiple separate pci bridges ... Message-ID: <20040106144545.GA7261@iliana> References: <1073252724.780.5.camel@gaston> <20040104220608.GA1667@iliana> <20040105164038.GA16158@iliana> <1073338095.9497.70.camel@gaston> <20040105214239.GA20252@iliana> <1073340725.9497.105.camel@gaston> <20040106073955.GF735@iliana> <1073376024.26508.220.camel@gaston> <20040106081143.GA1644@iliana> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: From: Sven Luther Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: On Tue, Jan 06, 2004 at 03:40:30PM +0100, Geert Uytterhoeven wrote: > On Tue, 6 Jan 2004, Sven Luther wrote: > > On Tue, Jan 06, 2004 at 07:00:24PM +1100, Benjamin Herrenschmidt wrote: > > > Type 0 is an access to the primary segment (doesn't contain a bus > > > number), type 1 is to be forwarded to another bus segment by a P2P > > > bridge. So for anything directly attached to the host bridge, it's a > > > type 0 access. Anything else is type 1. Typically, if the bus number of > > > your "target" == hose->first_busno, it's type 0, else type 1 > > > > Yep, except we have two pci controllers, and it should be type 0 for > > both of them. > > Yep, two hoses, with different hose->first_busno. A, yes, right. > > > They could have appeared as on-chip PCI devices on a "pseudo-bus", but > > > we can eventually just match with the host's PCI device. > > > > Ok. but this can also be faked or something ? But, how can we match with > > the host PCI device, if we are going to hide it ? > > Hide the memory BAR only, not the full PCI device. Ok, will try that. BTW, is there any reason the L2 cache is disabled by default in the 2.4.x kernels ? Friendly, Sven Luther ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/