mirror of
https://github.com/Fishwaldo/u-boot.git
synced 2025-03-18 21:21:37 +00:00
bootstage: Remove unused entries related to kernel/ramdisk/fdt load
Now that the code for loading these three images from a FIT is common, we don't need individual boostage IDs for each of them. Note: there are some minor changes in the bootstage numbering, particuarly for kernel loading. I don't believe this matters. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
parent
c6ac13bdea
commit
13167dac19
1 changed files with 2 additions and 25 deletions
|
@ -161,20 +161,10 @@ enum bootstage_id {
|
|||
* bit wonky.
|
||||
*/
|
||||
BOOTSTAGE_ID_FIT_KERNEL_START = 100,
|
||||
BOOTSTAGE_ID_FIT_FORMAT = 100,
|
||||
BOOTSTAGE_ID_FIT_NO_UNIT_NAME,
|
||||
BOOTSTAGE_ID_FIT_UNIT_NAME,
|
||||
BOOTSTAGE_ID_FIT_CONFIG,
|
||||
BOOTSTAGE_ID_FIT_CHECK_SUBIMAGE,
|
||||
BOOTSTAGE_ID_FIT_CHECK_HASH = 104,
|
||||
|
||||
BOOTSTAGE_ID_FIT_CHECK_ARCH,
|
||||
BOOTSTAGE_ID_FIT_CHECK_KERNEL,
|
||||
BOOTSTAGE_ID_FIT_CHECKED,
|
||||
|
||||
BOOTSTAGE_ID_FIT_KERNEL_INFO_ERR = 107,
|
||||
BOOTSTAGE_ID_FIT_KERNEL_INFO,
|
||||
BOOTSTAGE_ID_FIT_CONFIG = 110,
|
||||
BOOTSTAGE_ID_FIT_TYPE,
|
||||
BOOTSTAGE_ID_FIT_KERNEL_INFO,
|
||||
|
||||
BOOTSTAGE_ID_FIT_COMPRESSION,
|
||||
BOOTSTAGE_ID_FIT_OS,
|
||||
|
@ -183,19 +173,6 @@ enum bootstage_id {
|
|||
|
||||
/* 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,
|
||||
BOOTSTAGE_ID_FIT_RD_UNIT_NAME,
|
||||
BOOTSTAGE_ID_FIT_RD_SUBNODE,
|
||||
|
||||
BOOTSTAGE_ID_FIT_RD_CHECK,
|
||||
BOOTSTAGE_ID_FIT_RD_HASH = 125,
|
||||
BOOTSTAGE_ID_FIT_RD_CHECK_ALL,
|
||||
BOOTSTAGE_ID_FIT_RD_GET_DATA,
|
||||
BOOTSTAGE_ID_FIT_RD_CHECK_ALL_OK = 127,
|
||||
BOOTSTAGE_ID_FIT_RD_GET_DATA_OK,
|
||||
BOOTSTAGE_ID_FIT_RD_LOAD,
|
||||
|
||||
BOOTSTAGE_ID_IDE_FIT_READ = 140,
|
||||
BOOTSTAGE_ID_IDE_FIT_READ_OK,
|
||||
|
|
Loading…
Add table
Reference in a new issue