From owner-freebsd-current Thu Aug 13 10:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08953 for freebsd-current-outgoing; Thu, 13 Aug 1998 10:57:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08946 for ; Thu, 13 Aug 1998 10:57:57 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z71ct-0001om-00; Thu, 13 Aug 1998 10:57:27 -0700 Date: Thu, 13 Aug 1998 10:57:25 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: More PCI Slots... (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 Aug 1998, The Hermit Hacker wrote: > On Thu, 13 Aug 1998, Tom wrote: > > > > > On Thu, 13 Aug 1998, The Hermit Hacker wrote: > > > > > Sorry, I couldn't think of anywhere else more appropriate...but, is this > > > restricted to only Sun's, or has anyone looked at similar under an > > > Intel/PCI environment? > > > > PCI extender boxes have been available for a long time. Not long ago > > there was a mention of someone who hooked several of these up to a FreeBSD > > system. > > The OS doesn't need to do anything special to recognize them? Are > there any limitations? It is part of the PCI standard. PCI-PCI bridging. > At work, we are looking at a Sparc Enterprise 450, which has 10PCI > slots spread over something like 3-4 PCI busses...do the extende do > something like that, or is it all one big bus? I belive each extender is considered a separate bus, but of course is linked back to whatever bus it is plugged into. However, some x86 motherboards have their PCI slots slit over two buses too. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message