From owner-freebsd-current Fri Jun 18 22:15:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 743D314CE5 for ; Fri, 18 Jun 1999 22:15:50 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id GAA94989; Sat, 19 Jun 1999 06:16:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 19 Jun 1999 06:16:52 +0100 (BST) From: Doug Rabson To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: New-bus questions In-Reply-To: <19990618120110.30286@right.PCS> 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 Fri, 18 Jun 1999, Jonathan Lemon wrote: > > First, a request: > > I'm running into a problem with the new-bus PCI bus probing code, > and am not sure where to look. If someone could give me an overview > of how new-bus works, I would appreciate it. > > Now to the problem: > > I have a Compaq 3000 which I'm trying to get working. Under > -STABLE, it detects 4 PCI buses, and probes the devices on > the buses correctly. Under -current, it only detects 2 PCI > buses. Unfortunatly, my boot device is on one of the non- > detected buses, making debugging slightly difficult. > > FWIW, I can't get SMP working on this machine either, since > only two PCI buses are listed in the MP table; and I can't see > any "set Full MPTable" in Compaq's blasted Ctrl-A config utility. > > > 1. Why does -stable work and not -current? > 2. Does new-bus require an MP table (or equivalent) to detect the buses? I think this is a machine with multiple host-pci bridges. Could you send me a dmesg so that I can see what chipset is being used. I think we can support this by pretending the second bridge is a pci-pci bridge. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message