u-boot/include/cli_hush.h

/* SPDX-License-Identifier: GPL-2.0+ */
/*
 * (C) Copyright 2001
 * Wolfgang Denk, DENX Software Engineering, wd@denx.de.
 */

#ifndef _CLI_HUSH_H_
#define _CLI_HUSH_H_

#define FLAG_EXIT_FROM_LOOP 1
#define FLAG_PARSE_SEMICOLON (1 << 1)	  /* symbol ';' is special for parser */
#define FLAG_REPARSING       (1 << 2)	  /* >=2nd pass */
#define FLAG_CONT_ON_NEWLINE (1 << 3)	  /* continue when we see \n */

extern int u_boot_hush_start(void);
extern int parse_string_outer(const char *, int);
extern int parse_file_outer(void);

int set_local_var(const char *s, int flg_export);
void unset_local_var(const char *name);
char *get_local_var(const char *s);

#if defined(CONFIG_HUSH_INIT_VAR)
extern int hush_init_var (void);
#endif
#endif
SPDX: Convert all of our single license tags to Linux Kernel style When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: Tom Rini <trini@konsulko.com> 2018-05-07 05:58:06 +08:00			`/* SPDX-License-Identifier: GPL-2.0+ */`
Initial revision 2002-11-03 08:07:02 +08:00			`/*`
			`* (C) Copyright 2001`
			`* Wolfgang Denk, DENX Software Engineering, wd@denx.de.`
			`*/`

Rename hush to cli_hush Hush is a command-line interpreter, so rename it to make that clearer. Signed-off-by: Simon Glass <sjg@chromium.org> 2014-04-11 10:01:24 +08:00			`#ifndef _CLI_HUSH_H_`
			`#define _CLI_HUSH_H_`
Initial revision 2002-11-03 08:07:02 +08:00
			`#define FLAG_EXIT_FROM_LOOP 1`
			`#define FLAG_PARSE_SEMICOLON (1 << 1) /* symbol ';' is special for parser */`
			`#define FLAG_REPARSING (1 << 2) /* >=2nd pass */`
cli: hush: Adjust 'run' command to run each line of the env var The run command treats each argument an an environment variable. It gets the value of each variable and executes it as a command. If an environment variable contains a newline and the hush cli is used, it is supposed to execute each line one after the other. Normally a newline signals to hush to exit - this is used in normal command line entry - after a command is entered we want to return to allow the user to enter the next one. But environment variables obviously need to execute to completion. Add a special case for the execution of environment variables which continues when a newline is seen, and add a few tests to check this behaviour. Note: it's not impossible that this may cause regressions in other areas. I can't think of a case but with any change of behaviour with limited test coverage there is always a risk. From what I can tell this behaviour has been around since at least U-Boot 2011.03, although this pre-dates sandbox and I have not tested it on real hardware. Reported-by: Wolfgang Denk <wd@denx.de> Signed-off-by: Simon Glass <sjg@chromium.org> 2014-10-08 03:59:43 +08:00			`#define FLAG_CONT_ON_NEWLINE (1 << 3) /* continue when we see \n */`
Initial revision 2002-11-03 08:07:02 +08:00
			`extern int u_boot_hush_start(void);`
common: add run_command2 for running simple or hush commands Signed-off-by: Jason Hobbs <jason.hobbs@calxeda.com> Cc: Mike Frysinger <vapier@gentoo.org> Acked-by: Mike Frysinger <vapier@gentoo.org> 2011-08-31 13:37:24 +08:00			`extern int parse_string_outer(const char *, int);`
Initial revision 2002-11-03 08:07:02 +08:00			`extern int parse_file_outer(void);`

hush: add showvar command for hush shell. This new command shows the local variables defined in the hush shell: => help showvar showvar - print values of all hushshell variables showvar name ... - print value of hushshell variable 'name' Also make the set_local_var() and unset_local_var () no longer static, so it is possible to define local hush shell variables at boot time. If CONFIG_HUSH_INIT_VAR is defined, u-boot calls hush_init_var (), where boardspecific code can define local hush shell variables at boottime. Signed-off-by: Heiko Schocher <hs@denx.de> 2008-10-15 15:40:28 +08:00			`int set_local_var(const char *s, int flg_export);`
			`void unset_local_var(const char *name);`
common/hush: make get_local_var visible for other users Signed-off-by: Holger Brunck <holger.brunck@keymile.com> Acked-by: Heiko Schocher <hs@denx.de> cc: Wolfgang Denk <wd@denx.de> cc: Detlev Zundel <dzu@denx.de> cc: Valentin Longchamp <valentin.longchamp@keymile.com> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com> 2011-04-08 10:47:42 +08:00			`char get_local_var(const char s);`
hush: add showvar command for hush shell. This new command shows the local variables defined in the hush shell: => help showvar showvar - print values of all hushshell variables showvar name ... - print value of hushshell variable 'name' Also make the set_local_var() and unset_local_var () no longer static, so it is possible to define local hush shell variables at boot time. If CONFIG_HUSH_INIT_VAR is defined, u-boot calls hush_init_var (), where boardspecific code can define local hush shell variables at boottime. Signed-off-by: Heiko Schocher <hs@denx.de> 2008-10-15 15:40:28 +08:00
			`#if defined(CONFIG_HUSH_INIT_VAR)`
			`extern int hush_init_var (void);`
			`#endif`
Initial revision 2002-11-03 08:07:02 +08:00			`#endif`