[PATCH v5 5/8] rockchip: Use the same boot_targets for all boards

Simon Glass sjg at chromium.org
Thu Mar 30 23:25:58 CEST 2023

It doesn't really matter if we mention things which are not present. For
example, if 'nvme' is included but the board does not support it, we get
a message like:

   Unknown uclass 'nvme' in label

This seems tolerable. If it creates confusion we could perhaps find a way
to avoid the message, e.g. by maintaining a list of uclasses which may
be missing from the build and supressing warnings about them.

It is simpler to use the same target list for all boards, so drop the
different one for rk3399.

Signed-off-by: Simon Glass <sjg at chromium.org>

Changes in v5:
- Drop patch to relax the argument requirements for bootflow scan

Changes in v4:
- Rebase to -next
- Add new patch to use the same boot_targets for all boards

 include/configs/rockchip-common.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/include/configs/rockchip-common.h b/include/configs/rockchip-common.h
index e9f4072b7e78..9121bba37384 100644
--- a/include/configs/rockchip-common.h
+++ b/include/configs/rockchip-common.h
@@ -13,11 +13,7 @@
 #define BOOT_TARGETS	"mmc1 mmc0 nvme scsi usb pxe dhcp spi"
-#define BOOT_TARGETS	"mmc1 mmc0 usb pxe dhcp"
 #ifdef CONFIG_ARM64
 #define ROOT_UUID "B921B045-1DF0-41C3-AF44-4C6F280D3FAE;\0"

More information about the U-Boot mailing list