Handle deconfigured proc0 on FSPB boot
Handle deconfigured proc0 on FSPB boot

The basic issue is that we always boot from the memory range owned
by topology id 0.  Typically this is owned by proc0.  In this
case, proc0 is deconfigured though so we can't use it.  Hostboot
has logic to swap topoology ids if we have no functional memory
behind proc0, but the code wasn't correctly handling the case
where the processor itself is deconfigured.

Change-Id: I5304ddef32e52221d93533b439cec74ed04dabec
CQ: SW516583
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/111179
Reviewed-by: Michael Baiocchi <a81f28e8886c5e2bd4bbd867228778c3b7b19dea@us.ibm.com>
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Tested-by: Jenkins OP HW <0eb0fff262f74a65a832afbcc7b153e391c9a3fd@us.ibm.com>
Reviewed-by: Ilya Smirnov <2c7a6ec38cfb553b896499595cca9c656159f2a4@us.ibm.com>
Tested-by: Jenkins Combined Simics CI <8312af3886dfc9bb930f549023677220805b137e@us.ibm.com>
Reviewed-by: Christian R Geddes <f397583a9caa8163a06ad1128784fb67413f2fe6@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Tested-by: Hostboot CI <52521565bd8ea18a2b112942dce4f4220a97c2c8@us.ibm.com>

open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot