Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Dec 1998 09:30:00 -0800 (PST)
From:      Kevin Van Maren <vanmaren@fast.cs.utah.edu>
To:        freebsd-bugs@FreeBSD.ORG
Subject:   Re: kern/8928: 450NX-based computers only probe the first PCI bus
Message-ID:  <199812041730.JAA16056@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/8928; it has been noted by GNATS.

From: Kevin Van Maren <vanmaren@fast.cs.utah.edu>
To: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Cc:  Subject: Re: kern/8928: 450NX-based computers only probe the first PCI bus
Date: Fri, 4 Dec 1998 10:21:00 -0700 (MST)

 Just a couple of things:  The 2.2-STABLE patches have been tested
 (on an IBM 7000 M10), and they do work.
 
 The IBM allocates a PCI bus for every expansion slot in
 the system, in addition to the 3 busses (0-16 are "used").
 
 The Dell PowerEdge 6300 also sets up the MIOC registers "wrong".
 However, the Dell just programs the "highest used bus number" to
 255 on the last PXB.  So the PCI code probes all 256 possible
 busses...
 
 So if (subordinatebus == 255), it should probably be set to (NBUS-2)
 for SMP, and presumably something "reasonable" otherwise.  I can't
 tell how many "primary" PCI busses there are in the computer, but
 (because of the IBM 7000) that doesn't help much.  I can read the
 lowest PCI bus number per PXB, but there is no easy way to infer
 the highest buds number.
 
 Perhaps we should just read the device id for every device on every
 PCI bus and program the subordinatebus to the highest bus number
 on which we found something.  Yuck.
 
 Why is the BIOS on every 450NX-based Xeon screwed up?  The intel
 bios didn't even bother to config the bus if it thought it was empty.
 
 Kevin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812041730.JAA16056>