[PATCH v2] cmd: bootefi: restore ability to boot arbitrary blob

From: Kyle Evans Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we could boot an arbitrary blob with bootefi. Indeed, efi_run_image() even has a special case for missing device paths indicating a payload that was directly loaded via JTAG, for example. Restore the ability to

[PATCH] cmd: bootefi: restore ability to boot arbitrary blob

From: Kyle Evans Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we could boot an arbitrary blob with bootefi. Indeed, efi_run_image() even has a special case for missing device paths indicating a payload that was directly loaded via JTAG, for example. Restore the ability to

[PATCH 2/2] rpi: use the newly-added RPI_EFI_NR_SPIN_PAGES

From: Kyle Evans Some systems may use a slightly larger stub to do PSCI for booting the RPi family. The number of pages has been made configurable so that operating systems building U-Boot for use in these kinds of environments can reserve more memory in the EFI memory map. Signed-off-by: Kyle

[PATCH 1/2] rpi: Kconfig option for initial page reservation

From: Kyle Evans While the nearly-universal default for the Raspberry Pi family is to use spin tables and the spin table implementation provided by the Raspberry Pi Foundation, FreeBSD and others may use a PSCI implementation instead. Accommodate these setups by allowing them to configure for

[PATCH 1/2] rpi: add an RPi Kconfig to configure size of initial page reservation

From: Kyle Evans While the nearly-universal default for the Raspberry Pi family is to use spin tables and the spin table implementation provided by the Raspberry Pi Foundation, FreeBSD and others may use a PSCI implementation instead. Accommodate these setups by allowing them to configure for

[PATCH] raspberrypi: reserve first two pages in efi memory map

From: Kyle Evans The psci stub provided by Raspberry Pi is around 5k in size, thus residing in the first two pages of memory. Without this reservation, the next stage or OS assume they're free to use the second page and may get catastrophic results from clobbering it. Signed-off-by: Kyle Evans

[U-Boot] [PATCH 1/2] net: phy: Add PHY_RTL8211E_PINE64_GIGABIT_FIX for realtek phys

Setting PHY_RTL8211E_PINE64_GIGABIT_FIX forces internal rx/tx delays off on the PHY, as well as flipping some magical undocumented bits. The magic number comes from the Pine64 engineering team, presumably as a proxy from Realtek. This configuration fixes the throughput on some Pine64 models.

[U-Boot] [PATCH 0/2] Add fix for Pine64 gigabit throughput issues

The Pine64 has a known issue on gigabit links (see [1]); some boards suffer significant packet loss on Gigabit links. This patch sets the magical bits in CONFREG on the RTL8211E PHY to turn off the internal delay and do some other undocumented stuff. [1]

[U-Boot] [PATCH 2/2] Configs: Use the newly added PHY_RTL8211E_PINE64_GIGABIT_FIX

The Pine64+ uses a generic PHY driver, so flip it over to using the Realtek PHY driver to actually apply the RTL8211e fix. Signed-off-by: Kyle Evans --- configs/pine64_plus_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/configs/pine64_plus_defconfig