When the firmware tells us a loop id is already in use, add the device
authorjmatthew <jmatthew@openbsd.org>
Sat, 17 May 2014 11:51:21 +0000 (11:51 +0000)
committerjmatthew <jmatthew@openbsd.org>
Sat, 17 May 2014 11:51:21 +0000 (11:51 +0000)
commit74521a28a19397a865f1801263523f6580e44ae7
treef2fdd197ce3207405c84eddffa2012069678f08b
parentace552a014149de7417db98e4a349653d4ff4329
When the firmware tells us a loop id is already in use, add the device
there to our port lists, then find the next available loop id and carry on
rather than restarting.  This way, we're less likely to get stuck looping
when the firmware behaves inconsistently.  We also don't need to treat domain
controller logins specially.

additional complications discovered by deraadt@
sys/dev/ic/qla.c
sys/dev/ic/qlavar.h