Tianocore/edk2-platforms.git/Platform/RaspberryPi/RPi4/RPi4.fdf, branch CodeCleanup

Platform/RPi4: Add EFI_MP_SERVICES_PROTOCOL support

2023-02-03T12:43:19+00:00

Fix the ARM_MPCORE_INFO table and incorporate the DXE driver and test app to the build so that EFI_MP_SERVICES_PROTOCOL can be used and tested on Raspberry Pi 4. Note that the test app is not added to the image - it can be taken from the build directory and executed from the UEFI shell. Signed-off-by: Ard Biesheuvel Acked-by: Laszlo Ersek Reviewed-by: Rebecca Cran

Platform/RaspberryPi: Enable NVMe boot on CM4

2021-08-22T13:55:26+00:00

The CM4 has a number of carrier boards with PCIe slots. With the PCIe changes in place its quite possible to utilize a NVMe root device. Lets allow people to boot from it. Reviewed-by: Andrei Warkentin Signed-off-by: Jeremy Linton Reviewed-By: Samer El-Haj-Mahmoud

Platform/RaspberryPi: Enable default Secure Boot variables initialization

2021-08-04T12:32:33+00:00

This commit allows to initialize Secure Boot default key and databases from data embedded in firmware binary. Signed-off-by: Grzegorz Bernacki Reviewed-by: Sunny Wang Reviewed-by: Pete Batard Tested-by: Pete Batard # on Raspberry Pi 4

Platform/RaspberryPi: Enable Boot Discovery Policy.

2021-08-03T16:05:18+00:00

Modify platform boot to check the value of BootDiscoveryPolicy variable and use BootPolicyManager Protocol to connect devices specified by the variable. Signed-off-by: Grzegorz Bernacki Reviewed-by: Sunny Wang Reviewed-by: Pete Batard Tested-by: Pete Batard

Platform/RaspberryPi4: remove ASIX 88772b driver

2020-05-12T17:19:35+00:00

The Raspberry Pi4 has gigabit ethernet builtin, for which we now have a UEFI driver. So no need for the ASIX 88772b driver. Signed-off-by: Ard Biesheuvel Reviewed-by: Andrei Warkentin Reviewed-by: Samer El-Haj-Mahmoud Reviewed-by: Leif Lindholm

Platform/RaspberryPi: Rip out FdtDxe logic to use internal DTB

2020-05-01T17:07:15+00:00

Initially, FdtDxe used an internal (embedded in UEFI) FDT, because it was neither understood how to consume the one loaded by the VideoCore firmware, nor understood just how important it is to use the DTB provided by config.txt. Embedding the DT was a bad idea, because: - Permanently stale - No overlays Also, on devices like the Pi 4 you _have_ to have a DT around for the start4 VPU firmware to pick up, otherwise the board is left in an inconsistent state. So we're being prescriptive now about DT use with config.txt, which means this internal DT logic is dead code. Further FdtDxe cleanups are possible and will be handled separately, specifically: - probably no need to use a separate allocation for patched DT (optimize memory used) - suspicious use of EfiBootServicesData (I filed [0] to sort out the real requirements) Testing: Booted Ubuntu 18.04 on Pi 2B (1.2). [0] https://github.com/ARM-software/ebbr/issues/45 Signed-off-by: Andrei Warkentin Reviewed-by: Pete Batard

RPi3/RPi4: fix RPi 3 VPU-passed FDT handling by unifying with RPi4 implementation

2020-05-01T10:22:39+00:00

A rev-up of start.elf VPU firmware meant that the previous scheme of loading the DTB over top of RPI_EFI.FD no longer works - the DT is now loaded way before the armstub, so any overlap means the DT is overridden. This change re-arranges a few items in the FD, allowing the DTB to loaded directly after the FD in physical memory. Unlike the Pi 4 implementation, we can't move the UEFI image down in memory, as that needs a TF-A changem so it just reduces the size by 0x10000. The same base address (0x1f0000) is used as on the Pi 4. The Pi 3 FDF can be further unified with Pi 4 after work on TF-A to move to a single BL32-based Pi 3 TF-A implementation. Tested: Pi 3A+, Pi 2B v1.2, Pi 4B (4GB). Signed-off-by: Andrei Warkentin Reviewed-by: Pete Batard

Platform/RaspberryPi/RPi4: Switch to common GraphicsConsoleDxe

2020-04-14T16:46:28+00:00

Switch from the PI specific GraphicsConsoleDxe driver to the common driver in MdeModulePkg. There is no need to carry RPi specific version. Signed-off-by: Samer El-Haj-Mahmoud Reviewed-by: Andrei Warkentin

Platform/RaspberryPi: fix FDT handling for RPi4

2020-03-06T16:47:05+00:00

A rev-up of start4.elf VPU firmware meant that the previous scheme of loading the DTB over top of RPI_EFI.FD no longer works - the DT is now loaded way before the armstub, so any overlap means the DT is overridden. This change re-arranges a few items in the FD, allowing the DTB to loaded directly after the FD in physical memory. This moves UEFI image down by 0x10000, and reduces the FD image size by 0x10000, leaving space for a DTB to be loaded by config.txt at 0x1f0000. You need a matching "rev RPi4 TF-A for DTB fix" patch to edk2-non-osi, as it requires a TF-A build with these options: PRELOADED_BL33_BASE=0x20000 RPI3_PRELOADED_DTB_BASE=0x1f0000 Note: the same problem still affects the Pi 3, and will be fixed in a separate change. Signed-off-by: Andrei Warkentin Reviewed-by: Pete Batard Tested-by: Pete Batard

Platform/RPi: Make Device Tree provision a runtime (BIOS setup) choice

2020-03-03T14:06:46+00:00

With this and the previous commit, ACPI_BASIC_MODE_ENABLE becomes superfluous so remove it. New option defaults to enabled on Pi 3, disabled on Pi 4. Signed-off-by: Pete Batard Reviewed-by: Ard Biesheuvel