When the firmware tells us a loop id is already in use, add the device
authorjmatthew <jmatthew@openbsd.org>
Wed, 21 May 2014 22:59:26 +0000 (22:59 +0000)
committerjmatthew <jmatthew@openbsd.org>
Wed, 21 May 2014 22:59:26 +0000 (22:59 +0000)
commit0d6eccfa11e91701f347243252a2196270c33205
treeaa1884e9b1fc8d8782be5714b536af9f34f9fb3d
parent1c0d75a10f832a9d000d8dee9a82751c2c0f54c7
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.
sys/dev/pci/qle.c