aboutsummaryrefslogtreecommitdiff
path: root/src/arch/aarch64/boot_flow/linux.S
AgeCommit message (Collapse)Author
2020-06-26Relicense Hafnium under the BSD 3 clause license.Andrew Walbran
Updates to the rest of the links in the documentation will follow in a separate patch. Change-Id: I52e35dad8fa12be48df5459a5fc8521adc53d55b Signed-off-by: Andrew Walbran <qwandor@google.com>
2019-09-20Move boot params update to the boot_flow module.Andrew Scull
Not all boot flows want to be doing updates so leave that decision to the module responsible for coordinating the boot details. Change-Id: Ia769f99e2221f12c79a364c3ad323c31d39c98f3
2019-09-11Merge manifest into the board DT, add boot flow driversDavid Brazdil
Hafnium currently supports two kinds of boot flow: (a) Linux-like, where the board FDT is passed by the boot loader to the OS kernel in first kernel arg (this is used by QEMU, FVP, RPi, ...), (b) Android-like, where the FDT used by Hafnium is compiled into it and the VMs have their own. This used to be implemented using weak symbols and each board spec overriding it with its own implementation. This patch introduces the concept of boot-flow drivers in the main tree, and the corresponding driver selected using a config option in board spec. Drivers for the two boot-flows described above are implemented. Simultaneously, the manifest is now read from the FDT available at Hafnium init time. This required two notable changes: (1) all values are copied into the manifest struct because FDT is unmapped, modified and passed to the primary VM, (2) manifest is now written as an overlay; QEMU and FVP test drivers overlay it automatically. Bug: 117551352 Change-Id: Ieae7fe4ef5b3047174ec0ad057e487660ccd5a03