Re: [U-Boot] [PATCH] rockchip: reserve memory for rk3399 ATF data

Kever, Thanks for clarifying regarding what versions of ATF are out in production. I still feel a bit uneasy, as the size of the Cortex-M0 firmware could grow in the future (but then again, if that happens an alternative solution can be used). Given that this is needed for backward compatiblity,

Re: [U-Boot] [PATCH] rockchip: reserve memory for rk3399 ATF data

Hi Philipp, On 04/14/2017 06:51 PM, Dr. Philipp Tomsich wrote: Kever, Do we really need to change the SPL layout (i.e. BL2) for this? The SPL code should remain independent of later stages. This change would tie the U-Boot SPL (BL2) to a specific implementation/memory layout of the later BL3

Re: [U-Boot] [PATCH] rockchip: reserve memory for rk3399 ATF data

Hi Philipp, On 14 April 2017 at 04:51, Dr. Philipp Tomsich wrote: > Kever, > > Do we really need to change the SPL layout (i.e. BL2) for this? > > The SPL code should remain independent of later stages. This change would tie > the > U-Boot SPL (BL2) to a specific implementation/memory layout of

Re: [U-Boot] [PATCH] rockchip: reserve memory for rk3399 ATF data

Kever, Do we really need to change the SPL layout (i.e. BL2) for this? The SPL code should remain independent of later stages. This change would tie the U-Boot SPL (BL2) to a specific implementation/memory layout of the later BL31 stage. It should rather remain the responsibility of the BL31 st

[U-Boot] [PATCH] rockchip: reserve memory for rk3399 ATF data

There are 3 region used by rk3399 ATF: - bl31 code, locate at 0x1; - cortex-m0 code and data, locate at 0xff8c; - bl31 data, locate at 0xff8c1000 ~ 0xff8c4000; SPL_TEXT_BASE starts from 0xff8c2000, we need to reserve memory for ATF data, or else there will have memory corrupt after SPL loa