U-Boot for ARM Integrator Development Platforms			Peter Pearse, ARM Ltd.			peter.pearse@arm.com			     www.arm.comManuals available from :-http://www.arm.com/products/DevTools/Hardware_Platforms.htmlOverview :--------There are two Integrator variants - Integrator/AP and Integrator/CP.Each may be fitted with a variety of core modules (CMs).Each CM consists of a ARM processor core and associated hardware e.g	FPGA implementing various controllers and/or register	SSRAM	SDRAM	RAM controllers	clock generators etc.CMs may be fitted with varying amounts of SDRAM using a DIMM socket.Boot Methods :------------Integrator platforms can be configured to use U-Boot in at least three ways :-a) Run ARM boot monitor, manually run U-Boot image from flashb) Run ARM boot monitor, automatically run U-Boot image from flashc) Run U-Boot image direct from flash.In cases a) and b) the ARM boot monitor will have configured the CM and mappedwriteable memory to 0x00000000 in the Integrator address space.U-Boot has to carry out minimal configration before standard code is run.In case c) it may be necessary for U-Boot to perform CM dependent initialization.Configuring U-Boot :------------------	The makefile contains targets for Integrator platforms of both typesfitted with all current variants of CM. If these targets are to be used withboot process c) above then CONFIG_INIT_CRITICAL may need to be defined to ensurethat the CM is correctly configured.	There are also targets independent of CM. These may not be suitable forboot process c) above. They have been preserved for backward compatibility withexisting build processes.Code Hierarchy Applied :----------------------Code specific to initialization of a particular ARM processor has been placed incpu/arm<>/start.S so that it may be used by other boards.However, to avoid duplicating code through all processor files, a generic corefor ARM Integrator CMs has been added	cpu/arm_intcmOtherwise. for example,  the standard CM reset via the CM control register wouldneed placing in each CM processor file......Code specific to the initialization of the CM, rather than the cpu, and initializationof the Integrator board itself, has been placed in	board/integrator<>/platform.S	board/integrator<>/integrator<>.cTargets=======The U-Boot make targets map to the available core modules as below.Integrator/AP is no longer available from ARM.Core modules marked ** are also no longer available.ap720t_config		** CM720Tap920t_config		** CM920Tap926ejs_config	Integrator Core Module for ARM926EJ-STMap946es_config		Integrator Core Module for ARM946E-STMcp920t_config		** CM920Tcp926ejs_config	Integrator Core Module for ARM926EJ-STMcp946es_config		Integrator Core Module for ARM946E-STMcp1136_config		Integrator Core Module ARM1136JF-S  TMThe final groups of targets are for core modules where no explicit cpucode has yet been added to U-Boot i.e. they all use the same U-Boot binaryusing the generic "arm_intcm" core:ap966_config			Integrator Core Module for ARM966E-S TMap922_config			Integrator Core Module for ARM922T TM with ETMap922_XA10_config		Integrator Core Module for ARM922T using Altera Excaliburap7_config	       		** CM7TDMIintegratorap_configap_configcp966_config  			Integrator Core Module for ARM966E-S TMcp922_config			Integrator Core Module for ARM922T TM with ETMcp922_XA10_config		Integrator Core Module for ARM922T using Altera Excaliburcp1026_config			Integrator Core Module ARM1026EJ-S TMintegratorcp_configcp_configThe Makefile targets call board/integrator<>/split_by_variant.shto configure various defines in include/configs/integrator<>.hto indicate the core module & core configuration and ensure thatboard/integrator<>/u-boot.lds loads the cpu object first in the U-Boot image.*********************************Because of this mechanism> make cleanmust be run before each change in configuration*********************************