On Fri, Jan 26, 2001 at 08:25:40PM -0500, Allen Briggs wrote:

 > Right now, it's an option (PCI_NETBSD_CONFIGURE) that causes
 > dev/pci/pciconf.c to be included.  This includes a function
 > 
 > int     pci_configure_bus(pci_chipset_tag_t pc, int bus, int maxdevs);
 > 
 > If PCI_NETBSD_CONFIGURE is defined, this function is called just before
 > the device loop in pci.c:pci_probe_bus().  This is slightly suboptimal
 > because when assigning memory and I/O ranges, we could do a better job
 > if we have all of the information for all busses.  I'm tempted to say
 > that this isn't a problem until someone runs into an actual case where
 > it is a problem.  :-)
 > 
 > I haven't defined a way for a port to declare its free memory and I/O
 > spaces.  That's one of the things that's currently hardcoded.  Does
 > anyone have any suggestions on the best way to do this?

Err, a simple call into machdep PCI code, that fills in a linked
list of available spaces?

-- 
        -- Jason R. Thorpe <thorpej@zembu.com>