The README file states that the macros beginning with "CONFIG_SYS_" depend on the hardware etc. and should not be meddled with if you do not what you're doing. We have already screwed up with this policy; we have given the prefix "CONFIG_SYS_" to many user-selectable configurations. Here, "CONFIG_SYS_HUSH_PARSER" is one of them. Users can enable it if they want to use a more powerful command line parser, or disable it if they only need a simple one. This commit attempts to rename CONFIG_SYS_HUSH_PARSER to CONFIG_HUSH_PARSER and move it to Kconfig. Every board maintainer is expected to enable CONFIG_HUSH_PARSER (= add "CONFIG_HUSH_PARSER=y" to his defconfig file) and remove "#define CONFIG_SYS_HUSH_PARSER" from his header file. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
52 lines
1011 B
Plaintext
52 lines
1011 B
Plaintext
menu "Command line interface"
|
|
depends on !SPL_BUILD
|
|
|
|
config HUSH_PARSER
|
|
bool "Use hush shell"
|
|
select SYS_HUSH_PARSER
|
|
help
|
|
This option enables the "hush" shell (from Busybox) as command line
|
|
interpreter, thus enabling powerful command line syntax like
|
|
if...then...else...fi conditionals or `&&' and '||'
|
|
constructs ("shell scripts").
|
|
|
|
If disabled, you get the old, much simpler behaviour with a somewhat
|
|
smaller memory footprint.
|
|
|
|
config SYS_HUSH_PARSER
|
|
bool
|
|
help
|
|
Backward compatibility.
|
|
|
|
config CMD_BOOTM
|
|
bool "Enable bootm command"
|
|
default y
|
|
help
|
|
Boot an application image from the memory.
|
|
|
|
config CMD_CRC32
|
|
bool "Enable crc32 command"
|
|
default y
|
|
help
|
|
Compute CRC32.
|
|
|
|
config CMD_EXPORTENV
|
|
bool "Enable env export command"
|
|
default y
|
|
help
|
|
Export environments.
|
|
|
|
config CMD_IMPORTENV
|
|
bool "Enable env import command"
|
|
default y
|
|
help
|
|
Import environments.
|
|
|
|
config CMD_GO
|
|
bool "Enable go command"
|
|
default y
|
|
help
|
|
Start an application at a given address.
|
|
|
|
endmenu
|