2.2 BSP Rel. 1.0 for PPMC-275 Programmer's Guide

List of APIs API Call Reference
Driver Initialization
PCI0/1 Scanning
PCI number (0 or 1)
The driver flow of execution is divided into four phases:
Driver initialization
PCI0/1 scanning
PCI0/1 MEM1 address spacing remap
PCI devices configuration
In this phase, the driver:
initializes the pciConfigLib with PCI read/write routines.
scans for Monarch or Non-Monarch Mode and performs
initialization accordingly.
cleans both GalNetMappingArray and pciDeviceArray
data structures.
If the Monarch pin is asserted then the driver waits till EREADY
Signal goes to HIGH and then does PCI Scan by the pciGoScan()
routine. The EREADY signal assures all other PCI devices are ready
for initialization. In case of Monarch the pciGoScan routine fills
up the GalNet device table's GalNetMappingArray, with information
on the GalNet devices in PCI0/1 and the pciDeviceArray
table with information on any other PCI devices located in PCI0/1
(NIC).
In Non-Monarch mode it pulls down the EREADYOUT signal of the
MV-64360, which in turn causes the EREADY signal to be pulled
high so that an external monarch can initiate PCI Bus enumeration.
PCI0/1 MEM1 Address Spacing Remap
This stage is required only if there are GalNet devices in the system.
The GalNet devices use the GalNet region 0x08000000, which is
not a PCI address space by default. This routine changes the
PCI0/1 MEM1 address decoders according to the GalNet devices
found on PCI0/1:
If there is no GalNet device on both PCI0 and PCI1, the address
space 0x08000000 to 0x10000000 stays as the default.
– The PCI0_MEM1 default address space is 0xF2000000 to
0xF3FFFFFF (32 Mbyte).
5 - 18 VxWorks 5.5/Tornado 2.2 BSP Rel. 1.0 for PPMC-275