Changes from v1:
* Added commit message to patches
* Moved 2nd patch from platforms.config to edk2-platforms.config
* Added 3rd patch to allow use of UART5 in OP-TEE for hikey960
---
v1 cover letter:
Previously, we were using a 'headless' version of optee_os binary for
hikey and hikey960. With BL32_EXTRA1 and BL32_EXTRA2, we now enable
optee_os header parsing to allow dynamic runtime support of either a
64- or 32-bit optee_os build, and also the pager feature.
Victor Chong (3):
atf, opteed: Support BL32_EXTRA1 and BL32_EXTRA2
edk2-platforms.config: hikey*: Set TOS_BIN_EXTRA{1,2}
edk2-platforms.config: hikey960: Add UART5 option
atf-build.sh | 14 ++++++++++++--
edk2-platforms.config | 12 ++++++++++--
opteed-build.sh | 4 ++++
3 files changed, 26 insertions(+), 4 deletions(-)
--
2.15.1
Hi all,
I posted an issue on macchiato(a)lists.einval.com which is specific to my m
acchiato board setup. I just have a more generic question I would like to
ask here:
It appears that in my Marvell environment the DT data received through the
EFI mechanism may be partially corrupted (to be proven). The uboot boot
sequence works perfectly, but the EDKII boot fails in the kernel with
stalled CPUs due to PCIe failures and other interrupt handling problems.
Are there known issue receiving an FDT blob from EDKII using EFI?
If no, could you perhaps share the test setup at a high level?
Kind Regards,
Fred
Previously, we were using a 'headless' version of optee_os binary for
hikey and hikey960. With BL32_EXTRA1 and BL32_EXTRA2, we now enable
optee_os header parsing to allow dynamic runtime support of either a
64- or 32-bit optee_os builds, and also the pager feature.
Victor Chong (2):
atf, opteed: Support BL32_EXTRA1 and BL32_EXTRA2
platforms.config: hikey*: Set TOS_BIN_EXTRA{1,2}
atf-build.sh | 14 ++++++++++++--
opteed-build.sh | 4 ++++
platforms.config | 10 ++++++++--
3 files changed, 24 insertions(+), 4 deletions(-)
--
2.15.1
