summaryrefslogtreecommitdiffstats
path: root/release/doc
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2001-05-14 04:53:02 +0000
committerimp <imp@FreeBSD.org>2001-05-14 04:53:02 +0000
commit9350da3f9847bf5ef63748000a29fd5685788a32 (patch)
treed899f603003387298a4da935fa155169db9b8a26 /release/doc
parent6cfabf52542f075d198dc1ed4b488571becbb977 (diff)
downloadFreeBSD-src-9350da3f9847bf5ef63748000a29fd5685788a32.zip
FreeBSD-src-9350da3f9847bf5ef63748000a29fd5685788a32.tar.gz
When activating or deactivating a resource, only attempt to deal with
the resource activation if we're dealing with our grandchild. Otherwise, we run into two problems. One, if the pccard layer wanted to allocate and activate something, we'd wind up trying to do the wrong thing twice: the ivars are wrong and we don't want the bridge to map the resource to the slot. If we're more than a grandchild, then who knows what kind of ivar is present. In either of these cases, we just pass it up the food chain.
Diffstat (limited to 'release/doc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud