leandrof/u-boot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

bootstage: Introduce sub-IDs for use with image loading

Browse Source 
Loading a ramdisk, kernel or FDT goes through similar stages. Create
a block of IDs for each task, and define a consistent numbering within
the block. This will allow use of common code for image loading.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass 2013-05-16 13:53:19 +00:00 committed by Tom Rini
parent d34d186ef9
commit a2cc9bf4c1
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
include/bootstage.h
View File

@ -37,6 +37,24 @@ enum bootstage_flags {
BOOTSTAGEF_ALLOC = 1 << 1, /* Allocate an id */
};
/* bootstate sub-IDs used for kernel and ramdisk ranges */
enum {
BOOTSTAGE_SUB_FORMAT,
BOOTSTAGE_SUB_FORMAT_OK,
BOOTSTAGE_SUB_NO_UNIT_NAME,
BOOTSTAGE_SUB_UNIT_NAME,
BOOTSTAGE_SUB_SUBNODE,
BOOTSTAGE_SUB_CHECK,
BOOTSTAGE_SUB_HASH = 5,
BOOTSTAGE_SUB_CHECK_ARCH = 5,
BOOTSTAGE_SUB_CHECK_ALL,
BOOTSTAGE_SUB_GET_DATA,
BOOTSTAGE_SUB_CHECK_ALL_OK = 7,
BOOTSTAGE_SUB_GET_DATA_OK,
BOOTSTAGE_SUB_LOAD,
};
/*
* A list of boot stages that we know about. Each of these indicates the
* state that we are at, and the action that we are about to perform. For
@ -137,10 +155,12 @@ enum bootstage_id {
BOOTSTAGE_ID_NET_DONE_ERR,
BOOTSTAGE_ID_NET_DONE,
BOOTSTAGE_ID_FIT_FDT_START = 90,
/*
* Boot stages related to loading a FIT image. Some of these are a
* bit wonky.
*/
BOOTSTAGE_ID_FIT_KERNEL_START = 100,
BOOTSTAGE_ID_FIT_FORMAT = 100,
BOOTSTAGE_ID_FIT_NO_UNIT_NAME,
BOOTSTAGE_ID_FIT_UNIT_NAME,
@ -161,6 +181,8 @@ enum bootstage_id {
BOOTSTAGE_ID_FIT_LOADADDR,
BOOTSTAGE_ID_OVERWRITTEN,
/* Next 10 IDs used by BOOTSTAGE_SUB_... */
BOOTSTAGE_ID_FIT_RD_START = 120, /* Ramdisk stages */
BOOTSTAGE_ID_FIT_RD_FORMAT = 120,
BOOTSTAGE_ID_FIT_RD_FORMAT_OK,
BOOTSTAGE_ID_FIT_RD_NO_UNIT_NAME,