summaryrefslogtreecommitdiffstats
path: root/sys/dev/pccbb
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2003-07-03 14:00:57 +0000
committerimp <imp@FreeBSD.org>2003-07-03 14:00:57 +0000
commite9df6b7a142eb6576de449a7025b728f30224161 (patch)
tree584c5d95c565a7220199ac4f80f117d25995ead7 /sys/dev/pccbb
parent2d545c0325ebd6225a22298a5cffc0570a56fb16 (diff)
downloadFreeBSD-src-e9df6b7a142eb6576de449a7025b728f30224161.zip
FreeBSD-src-e9df6b7a142eb6576de449a7025b728f30224161.tar.gz
All current uses of pci_set_powerstate are bogus, at least in theory.
However, they are presently necessary due to bigger bogusness in the pci bus layer not doing the right thing on suspend/resume or on initial device probe. This is exactly the sort of thing that the BURN_BRIDGES option was invented for. Mark all of them as BURN_BRIDGES. As soon as I have the powerstate stuff properly integrated into the pci bus code, I intend to remove all these workarounds.
Diffstat (limited to 'sys/dev/pccbb')
-rw-r--r--sys/dev/pccbb/pccbb.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/sys/dev/pccbb/pccbb.c b/sys/dev/pccbb/pccbb.c
index b3e655c..fe4c445 100644
--- a/sys/dev/pccbb/pccbb.c
+++ b/sys/dev/pccbb/pccbb.c
@@ -585,6 +585,7 @@ cbb_chipinit(struct cbb_softc *sc)
pci_write_config(sc->dev, CBBR_IOLIMIT1, 0, 4);
}
+#ifndef BURN_BRIDGES
static void
cbb_powerstate_d0(device_t dev)
{
@@ -606,6 +607,7 @@ cbb_powerstate_d0(device_t dev)
pci_write_config(dev, PCIR_INTLINE, irq, 4);
}
}
+#endif
/*
* Print out the config space
@@ -640,10 +642,9 @@ cbb_attach(device_t brdev)
sc->subbus = pci_read_config(brdev, PCIR_SUBBUS_2, 1);
SLIST_INIT(&sc->rl);
STAILQ_INIT(&sc->intr_handlers);
-
+#ifndef BURN_BRIDGES
cbb_powerstate_d0(brdev);
-#ifndef BURN_BRIDGES
/*
* The PCI bus code should assign us memory in the absense
* of the BIOS doing so. However, 'should' isn't 'is,' so we kludge
OpenPOWER on IntegriCloud