Sandrine Bailleux 2102ef2275 TSP: Let the platform decide which secure memory to use ... The TSP's linker script used to assume that the TSP would execute from secure DRAM. Although it is currently the case on FVPs, platforms are free to use any secure memory they wish. This patch introduces the flexibility to load the TSP into any secure memory. The platform code gets to specify the extents of this memory in the platform header file, as well as the BL3-2 image limit address. The latter definition allows to check in a generic way that the BL3-2 image fits in its bounds. Change-Id: I9450f2d8b32d74bd00b6ce57a0a1542716ab449c		2014-05-21 11:01:29 +01:00
..
aarch64	Rework memory information passing to BL3-x images	2014-05-20 16:36:31 +01:00
tsp-fvp.mk	fvp: Use the right implem. of plat_report_exception() in BL3-2	2014-05-13 17:33:01 +01:00
tsp.ld.S	TSP: Let the platform decide which secure memory to use	2014-05-21 11:01:29 +01:00
tsp.mk	Remove vpath usage in makefiles	2014-05-06 12:35:02 +01:00
tsp_main.c	Rework memory information passing to BL3-x images	2014-05-20 16:36:31 +01:00