Andre Przywara 448fb352f9 rpi4: Determine BL33 entry point at runtime ... Now that we have the armstub magic value in place, the GPU firmware will write the kernel load address (and DTB address) into our special page, so we can always easily access the actual location without hardcoding any addresses into the BL31 image. Make the compile-time defined PRELOADED_BL33_BASE macro optional, and read the BL33 entry point from the magic location, if the macro was not defined. We do the same for the DTB address. This also splits the currently "common" definition of plat_get_ns_image_entrypoint() to be separate between RPi3 and RPi4. Change-Id: I6f26c0adc6fce2df47786b271c490928b4529abb Signed-off-by: Andre Przywara <andre.przywara@arm.com>		2019-09-25 11:45:35 +01:00
..
aarch64	rpi3: Do prescaler and control setup in C	2019-09-13 16:54:21 +01:00
include	rpi3: Rename RPI3_IO_BASE to RPI_IO_BASE	2019-09-13 16:54:21 +01:00
platform.mk	rpi3: Move shared rpi3 files into common directory	2019-09-13 16:54:21 +01:00
rpi3_bl1_setup.c	rpi3: Allow runtime determination of UART base clock rate	2019-09-25 11:45:35 +01:00
rpi3_bl2_setup.c	rpi3: Allow runtime determination of UART base clock rate	2019-09-25 11:45:35 +01:00
rpi3_bl31_setup.c	rpi4: Determine BL33 entry point at runtime	2019-09-25 11:45:35 +01:00
rpi_mbox_board.c	rpi3: Move VC mailbox driver into generic drivers directory	2019-09-13 16:54:21 +01:00