summaryrefslogtreecommitdiffstats
path: root/sys/dev/txp
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/txp
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/txp')
-rw-r--r--sys/dev/txp/if_txp.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/dev/txp/if_txp.c b/sys/dev/txp/if_txp.c
index 542f692..866a120 100644
--- a/sys/dev/txp/if_txp.c
+++ b/sys/dev/txp/if_txp.c
@@ -223,7 +223,7 @@ txp_attach(dev)
mtx_init(&sc->sc_mtx, device_get_nameunit(dev), MTX_NETWORK_LOCK,
MTX_DEF | MTX_RECURSE);
-
+#ifndef BURN_BRIDGES
/*
* Handle power management nonsense.
*/
@@ -245,7 +245,7 @@ txp_attach(dev)
pci_write_config(dev, TXP_PCI_LOMEM, membase, 4);
pci_write_config(dev, TXP_PCI_INTLINE, irq, 4);
}
-
+#endif
/*
* Map control/status registers.
*/
OpenPOWER on IntegriCloud