From owner-freebsd-stable Mon Jun 5 14:12:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id BC12137BE02; Mon, 5 Jun 2000 14:12:43 -0700 (PDT) (envelope-from fred@veriohosting.com) Received: by gatekeeper.veriohosting.com; Mon, 5 Jun 2000 15:12:39 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma011355; Mon, 5 Jun 00 15:12:35 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id PAA34105; Mon, 5 Jun 2000 15:12:35 -0600 (MDT) Date: Mon, 5 Jun 2000 15:17:34 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Jason Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: changed pci bus probe order from 3.2 to 4.0 -- ideas? In-Reply-To: <00aa01bfcf2f$0478c760$0dcb1f40@mom> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The PCI spec basicly states that buses are to be probed depth first. As a > PCI bridge is found, it is assigned the next sequential bus number and > probed for additional bridges beyond it. As a new bridge is found, all the > parent bridges' subordinat bus number register is updated to the highest > numbered bus that exists beyond it. When no more PCI bridges are found on > the current bus, the routine should return to the parent bus and continue > probing for more PCI bridges, and so on. > Hm so does that mean that non-bridge devices on those busses should also be done depth first? I understand wanting to find all the busses first, but devices too? All the bioses I've seen seem to find all the busses, then assign resources to devices starting with those on bus 0 then bus 1 etc. This is also how FreeBSD <=3.4 work. Am I just missing something? Fred -- Fred Clift - fred@veriohosting.com -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message