From 9efaa0ae62faa8f627d135f1de1c99c659753281 Mon Sep 17 00:00:00 2001 From: Brooks Davis Date: Wed, 26 Sep 2001 01:11:33 +0000 Subject: Add a standard hack in the spirit of PCI_ENABLE_IO_MODES to allow systems with weird PCI-PCI bridge configurations to work. Defining PCI_ALLOW_UNSUPPORTED_IO_RANGE causes the sanity checks to pass even with out of range values. Reviewed by: msmith --- sys/dev/pci/pci_pci.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'sys/dev') diff --git a/sys/dev/pci/pci_pci.c b/sys/dev/pci/pci_pci.c index 3980158f40e3..9587622cf923 100644 --- a/sys/dev/pci/pci_pci.c +++ b/sys/dev/pci/pci_pci.c @@ -286,7 +286,9 @@ pcib_alloc_resource(device_t dev, device_t child, int type, int *rid, " (decoding 0x%x-0x%x)\n", device_get_name(child), device_get_unit(child), start, end, sc->iobase, sc->iolimit); +#ifndef PCI_ALLOW_UNSUPPORTED_IO_RANGE return(NULL); +#endif } if (bootverbose) device_printf(sc->dev, "device %s%d requested decoded I/O range 0x%lx-0x%lx\n", @@ -306,7 +308,9 @@ pcib_alloc_resource(device_t dev, device_t child, int type, int *rid, " (decoding 0x%x-0x%x, 0x%x-0x%x)\n", device_get_name(child), device_get_unit(child), start, end, sc->membase, sc->memlimit, sc->pmembase, sc->pmemlimit); +#ifndef PCI_ALLOW_UNSUPPORTED_IO_RANGE return(NULL); +#endif } if (bootverbose) device_printf(sc->dev, "device %s%d requested decoded memory range 0x%lx-0x%lx\n", -- cgit v1.3