6755970bcf
funk when they misbehave and give us unexpected results. Specifically: - Don't assume that the first free slot is at the top of the table if we can't find one. - Don't increment ADBNumDevices when backfilling "holes" left by devices that didn't respond to a TALK R3 during the initial device scan. - Don't assume that an address reassignment worked; make sure something responds on the new address before plowing forward. - If after device reassignment there are no free slots, make sure to indicate this fact. - Failing all else, handle the situation where we run out of slots in the device table -- which now should "never" happen -- gracefully. While the Power Manager driver still sometimes misbehaves, it shouldn't cause the system to crash/hang due to us walking off the end of the device table.