diff options
author | brooks <brooks@FreeBSD.org> | 2001-09-26 01:11:33 +0000 |
---|---|---|
committer | brooks <brooks@FreeBSD.org> | 2001-09-26 01:11:33 +0000 |
commit | ed782e909096e9685fb66fc6beb5b587b7b29f11 (patch) | |
tree | ce220d0907d4fc1ffecb54eb2dd31abc721fda80 /sys/dev/pci | |
parent | cd2a2dcb2388797636bff81d59edd30b6d99011e (diff) | |
download | FreeBSD-src-ed782e909096e9685fb66fc6beb5b587b7b29f11.zip FreeBSD-src-ed782e909096e9685fb66fc6beb5b587b7b29f11.tar.gz |
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
Diffstat (limited to 'sys/dev/pci')
-rw-r--r-- | sys/dev/pci/pci_pci.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sys/dev/pci/pci_pci.c b/sys/dev/pci/pci_pci.c index 3980158..9587622 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", |