47aedc29dc
At present we set up the bootdev order at the start, then scan the bootdevs one by one. However this approach cannot be used with hunters, since the bootdevs may not exist until the hunter is used. Nor can we just run all the hunters at the start, since that violate's U-Boot's 'lazy init' requirement. It also increases boot time. So we need to adjust the algorithm to scan by labels instead. As a first step, drop the dev_order[] array in favour of a list of labels. Update the name of bootdev_setup_iter_order() to better reflect what it does. Update some related comments and log messages. Also disable a few tests until a later commit where we can use them. Signed-off-by: Simon Glass <sjg@chromium.org> |
||
|---|---|---|
| .. | ||
| bootdev.c | ||
| bootflow.c | ||
| bootmeth.c | ||
| bootstd_common.c | ||
| bootstd_common.h | ||
| expo.c | ||
| image.c | ||
| Makefile | ||
| vbe_fixup.c | ||
| vbe_simple.c | ||