Re: [edk2-devel] [edk2-non-osi][PATCH 2/2] Platforms/RPi4: Add Trusted Firmware binaries

2019-12-11 Thread Pete Batard
Hi Leif, On 2019.12.11 14:14, Leif Lindholm wrote: On Wed, Dec 11, 2019 at 11:24:00 +, Pete Batard wrote: Similar to what is the case with the Raspberry Pi 3, the Raspberry Pi 4 UEFI firmware requires the provision of a Trusted Firmware binary (TF-A). The binary is built for a dtb base add

Re: [edk2-devel] [edk2-non-osi][PATCH 2/2] Platforms/RPi4: Add Trusted Firmware binaries

2019-12-11 Thread Leif Lindholm
On Wed, Dec 11, 2019 at 11:24:00 +, Pete Batard wrote: > Similar to what is the case with the Raspberry Pi 3, the Raspberry Pi > 4 UEFI firmware requires the provision of a Trusted Firmware binary > (TF-A). > > The binary is built for a dtb base address of 0x0002 and a UEFI > payload base

[edk2-devel] [edk2-non-osi][PATCH 2/2] Platforms/RPi4: Add Trusted Firmware binaries

2019-12-11 Thread Pete Batard
Similar to what is the case with the Raspberry Pi 3, the Raspberry Pi 4 UEFI firmware requires the provision of a Trusted Firmware binary (TF-A). The binary is built for a dtb base address of 0x0002 and a UEFI payload base address of 0x0003. Binaries are built using a custom version of TF