summaryrefslogtreecommitdiffstats
path: root/lib/libthr/thread/thr_init.c
diff options
context:
space:
mode:
authormjacob <mjacob@FreeBSD.org>2006-07-25 00:59:54 +0000
committermjacob <mjacob@FreeBSD.org>2006-07-25 00:59:54 +0000
commitdd7156e6854b14431bf8613e75c524688d25e058 (patch)
tree24a0b7419686392b7d5cb4ac839ffbd3d743e506 /lib/libthr/thread/thr_init.c
parent35c8368f4e46783fcce1459c7ddd38addbb600f2 (diff)
downloadFreeBSD-src-dd7156e6854b14431bf8613e75c524688d25e058.zip
FreeBSD-src-dd7156e6854b14431bf8613e75c524688d25e058.tar.gz
When probing to attach the CAM functionality, check against
desired role configuration instead of existing role. This gets us out of the mess where we configured a role of NONE (or were LAN only, for example), but didn't continue to attach the CAM module (because we had neither initiator nor target role set). Unfortunately, the code that rewrites NVRAM to match actual to desired role only works if the CAM module attaches. MFC after: 2 weeks
Diffstat (limited to 'lib/libthr/thread/thr_init.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud