Home
last modified time | relevance | path

Searched hist:"448 fb352f9be697e40b1224df3e33bca863326c6" (Results 1 – 3 of 3) sorted by relevance

/rk3399_ARM-atf/plat/rpi/rpi3/
H A Drpi3_bl31_setup.c448fb352f9be697e40b1224df3e33bca863326c6 Thu Jul 11 00:42:12 UTC 2019 Andre Przywara <andre.przywara@arm.com> 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>
/rk3399_ARM-atf/plat/rpi/common/
H A Drpi3_common.c448fb352f9be697e40b1224df3e33bca863326c6 Thu Jul 11 00:42:12 UTC 2019 Andre Przywara <andre.przywara@arm.com> 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>
/rk3399_ARM-atf/plat/rpi/rpi4/
H A Dplatform.mk448fb352f9be697e40b1224df3e33bca863326c6 Thu Jul 11 00:42:12 UTC 2019 Andre Przywara <andre.przywara@arm.com> 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>