summaryrefslogtreecommitdiff
path: root/configs/M5275EVB_defconfig
diff options
context:
space:
mode:
authorMarek Vasut <marek.vasut+renesas@mailbox.org>2023-03-23 03:21:28 +0300
committerAngelo Dureghello <angelo@kernel-space.org>2023-04-16 22:43:28 +0300
commitea82cd1cbdc9d2bf8ff94d2f993edce9fec16d1e (patch)
tree6b83a1abc27955ef9292142c92c7518b1f25c08c /configs/M5275EVB_defconfig
parentf04ef0a7a0166e91729b45b1db22f5cc3b3b2f99 (diff)
downloadu-boot-ea82cd1cbdc9d2bf8ff94d2f993edce9fec16d1e.tar.xz
configs: m68k: Use default shell prompt
The current shell prompt '->' interferes with CI matching on 'bdinfo' output. When CI test.py attempts to locate memory information in the 'bdinfo' output, it matches on '->' prefix which is identical to the shell prefix. Switch the prompt to default '=>' one to avoid this interference. Suggested-by: Tom Rini <trini@konsulko.com> # found the CI oddity Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Diffstat (limited to 'configs/M5275EVB_defconfig')
-rw-r--r--configs/M5275EVB_defconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/configs/M5275EVB_defconfig b/configs/M5275EVB_defconfig
index 5ce9b74f06..557e6940b5 100644
--- a/configs/M5275EVB_defconfig
+++ b/configs/M5275EVB_defconfig
@@ -4,7 +4,6 @@ CONFIG_SYS_MALLOC_LEN=0x40000
CONFIG_ENV_SIZE=0x2000
CONFIG_ENV_SECT_SIZE=0x2000
CONFIG_DEFAULT_DEVICE_TREE="M5275EVB"
-CONFIG_SYS_PROMPT="-> "
CONFIG_SYS_LOAD_ADDR=0x800000
CONFIG_ENV_ADDR=0xFFE04000
CONFIG_TARGET_M5275EVB=y