summaryrefslogtreecommitdiff
path: root/arch/microblaze/config.mk
diff options
context:
space:
mode:
authorLiu Gang <Gang.Liu@freescale.com>2012-03-08 00:33:17 +0000
committerAndy Fleming <afleming@freescale.com>2012-04-24 23:58:32 -0500
commit5ffa88eca78b7260788b898b69b7d17d9508268f (patch)
tree90599d2e979845f696ffd2fce82ef44c10ad2540 /arch/microblaze/config.mk
parent006f37f698853ca412022f80c755829f7cfa7cf2 (diff)
downloadu-boot-imx-5ffa88eca78b7260788b898b69b7d17d9508268f.zip
u-boot-imx-5ffa88eca78b7260788b898b69b7d17d9508268f.tar.gz
u-boot-imx-5ffa88eca78b7260788b898b69b7d17d9508268f.tar.bz2
powerpc/corenet_ds: Master module for boot from SRIO
For the powerpc processors with SRIO interface, boot location can be configured from SRIO1 or SRIO2 by RCW. The processor booting from SRIO can do without flash for u-boot image. The image can be fetched from another processor's memory space by SRIO link connected between them. The processor boots from SRIO is slave, the processor boots from normal flash memory space and can help slave to boot from its memory space is master. They are different environments and requirements: master: 1. NOR flash for its own u-boot image, ucode and ENV space. 2. Slave's u-boot image in master NOR flash. 3. Normally boot from local NOR flash. 4. Configure SRIO switch system if needed. slave: 1. Just has EEPROM for RCW. No flash for u-boot image, ucode and ENV. 2. Boot location should be set to SRIO1 or SRIO2 by RCW. 3. RCW should configure the SerDes, SRIO interfaces correctly. 4. Slave must be powered on after master's boot. For the master module, need to finish these processes: 1. Initialize the SRIO port and address space. 2. Set inbound SRIO windows covered slave's u-boot image stored in master's NOR flash. 3. Master's u-boot image should be generated specifically by make xxxx_SRIOBOOT_MASTER_config 4. Master must boot first, and then slave can be powered on. Signed-off-by: Liu Gang <Gang.Liu@freescale.com> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
Diffstat (limited to 'arch/microblaze/config.mk')
0 files changed, 0 insertions, 0 deletions