Lines Matching refs:command
9 Commands are added to U-Boot by creating a new command structure.
10 This is done by first including command.h, then using the U_BOOT_CMD() or the
15 U_BOOT_CMD(name, maxargs, repeatable, command, "usage", "help")
16 U_BOOT_CMD_COMPLETE(name, maxargs, repeatable, command, "usage, "help", comp)
19 The name of the command. This is **not** a string.
23 the command itself.
28 command
29 Pointer to the command function. This is the function that is
30 called when the command is issued.
42 entering the command arguments to complete the entry. Command
45 Sub-command definition
53 U_BOOT_CMD_MKENT(name, maxargs, repeatable, command, "usage", "help")
54 U_BOOT_CMD_MKENTCOMPLETE(name, maxargs, repeatable, command, "usage, "help", comp)
56 This table has to be evaluated in the command function of the main command, e.g.
72 /* drop sub-command argument */
87 The command function pointer has to be of type
94 Table entry describing the command (see above).
99 * CMD_FLAG_REPEAT - The last command is repeated.
100 * CMD_FLAG_BOOTD - The command is called by the bootd command.
101 * CMD_FLAG_ENV - The command is called by the run command.
104 Number of arguments including the command.
112 The command was successfully executed.
115 The command failed.
118 The command was called with invalid parameters. This value
132 Number of arguments including the command.
138 The last character in the command line buffer.
160 command array can be iterated over using the linker lists macros.
166 If a new board is defined do not forget to define the command section
182 It is fairly easy to write a test for a command. Enable it in sandbox, and
183 then add code that runs the command and checks the output.
189 /* Test 'acpi items' command */