"...0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png" did not exist on "89a09a8bd45be1fef0cad4d00ad9d28081d7ff8d"
-
Adam Johnston authored
Previously, the order in which secure partitions were initialized relied on the order in which they were loaded - however that is undocumented behavior. Add boot order property into SP manifests to ensure each partition is initialized in the correct order i.e before any other partition which uses it - block storage before protected storage - protected storage before crypto Signed-off-by:
Adam Johnston <adam.johnston@arm.com>6b5058c4
Loading