commit 0dbb41f28deadca906d09a2d6e7d11bc8381410f
author David Brazdil <dbrazdil@google.com> Mon Sep 09 18:03:35 2019 +0100
committer David Brazdil <dbrazdil@google.com> Wed Sep 11 13:24:43 2019 +0100
tree 446d695110e6ce0ca31c2b87a71454348a75e1b6
parent c76466d3dba6e41e1fa82090fa31ca6620f901dc

Merge manifest into the board DT, add boot flow drivers

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