summaryrefslogtreecommitdiff
path: root/board/friendlyarm
diff options
context:
space:
mode:
authorLiu Gang <Gang.Liu@freescale.com>2013-05-07 16:30:50 +0800
committerAndy Fleming <afleming@freescale.com>2013-06-20 17:08:49 -0500
commit69fdf900105d9f730b526c760c082d1f6641a489 (patch)
tree9d6c51856acdfe121c61b5de82028c797e346b55 /board/friendlyarm
parent3e531b0ba96590ab3e86ee3b5c9fa8a2e91b6849 (diff)
downloadu-boot-imx-69fdf900105d9f730b526c760c082d1f6641a489.zip
u-boot-imx-69fdf900105d9f730b526c760c082d1f6641a489.tar.gz
u-boot-imx-69fdf900105d9f730b526c760c082d1f6641a489.tar.bz2
powerpc/t4qds: Slave module for boot from SRIO and PCIE
When a T4 board boots from SRIO or PCIE, it needs to finish these processes: 1. Set all the cores in holdoff status. 2. Set the boot location to one PCIE or SRIO interface by RCW. 3. Set a specific TLB entry for the boot process. 4. Set a LAW entry with the TargetID of one PCIE or SRIO for the boot. 5. Set a specific TLB entry in order to fetch ucode and ENV from master. 6. Set a LAW entry with the TargetID one of the PCIE ports for ucode and ENV. 7. Slave's u-boot image should be generated specifically by make xxxx_SRIO_PCIE_BOOT_config. This will set SYS_TEXT_BASE=0xFFF80000 and other configurations. For more information about the feature of Boot from SRIO/PCIE, please refer to the document doc/README.srio-pcie-boot-corenet. Signed-off-by: Liu Gang <Gang.Liu@freescale.com> Signed-off-by: Andy Fleming <afleming@freescale.com>
Diffstat (limited to 'board/friendlyarm')
0 files changed, 0 insertions, 0 deletions