summaryrefslogtreecommitdiff
path: root/src/arch/armv7/coreboot_ram.ld
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2013-04-24 15:14:01 -0500
committerRonald G. Minnich <rminnich@gmail.com>2013-05-01 07:04:47 +0200
commit7e35efa83cdd6240e4f9282cc4d2703c40d472d5 (patch)
tree09091124f6b118ca5c9e5ac1c675d138174564bf /src/arch/armv7/coreboot_ram.ld
parente1be5ae2f485989f88ae9af92a97e0577b033155 (diff)
ramstage: introduce boot state machine
The boot flow currently has a fixed ordering. The ordering is dictated by the device tree and on x86 the PCI device ordering for when actions are performed. Many of the new machines and configurations have dependencies that do not follow the device ordering. In order to be more flexible the concept of a boot state machine is introduced. At the boundaries (entry and exit) of each state there is opportunity to run callbacks. This ability allows one to schedule actions to be performed without adding board-specific code to the shared boot flow. Change-Id: I757f406c97445f6d9b69c003bb9610b16b132aa6 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/3132 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Diffstat (limited to 'src/arch/armv7/coreboot_ram.ld')
0 files changed, 0 insertions, 0 deletions