From owner-freebsd-stable Mon Jun 26 9:19: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 616E737BA47 for ; Mon, 26 Jun 2000 09:18:49 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e5QGIcR90613; Mon, 26 Jun 2000 09:18:38 -0700 (PDT) Date: Mon, 26 Jun 2000 09:18:38 -0700 (PDT) From: Doug White To: Remy Nonnenmacher Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Fixing PCI device locations In-Reply-To: <200006261436.QAA10618@luxren2.boostworks.com> 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 On Mon, 26 Jun 2000, Remy Nonnenmacher wrote: > > I recently upgraded a server from 3.4 to 4-stable and was hurted by the > PCI device scanning not done in the same order on the two versions. > > Mainly, the server have 6 SCSI busses over 3 devices and two PCI > busses. (da0 on 3.4 ended up on da52 under 4-stable) > > While provisions are made for fixing SCSI controlers to busses (ieg: ahc > to scbus) and disks to scbuses, is there a way to fix SCSI controlers > to PCI locations ? > > (something like "device ahc0 on pci0.11.1") Not at this time, but it may appear at some time in the future, given an enterprising individual. A great many people, including embedded systems builders, would be thankful for such a feature. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message