| Age | Commit message (Collapse) | Author |
|---|
|
For nearly all commands in U-Boot the '?' variable is handled the same
way with 0 meaning success, 1 meaning any failure. Explain this in the
general rules section of the cmdline documentation (with a link to a
counter example) and then remove the redundant wording from most
commands. We retain a section about the return value in a number of
places where we are doing something such as always returning a specific
value or we have useful additional information to go along with the
normal return codes.
Signed-off-by: Tom Rini <[email protected]>
Reviewed-by: Heinrich Schuchardt <[email protected]>
|
|
%s/Synopis/Synopsis/g
Signed-off-by: Heinrich Schuchardt <[email protected]>
|
|
Add the description of CLI commands to the generated index.
Signed-off-by: Heinrich Schuchardt <[email protected]>
|
|
The working FDT is the one which comes from the OS and is fixed up by
U-Boot. When the bootm command runs, it sets up the working FDT to be the
one it is about to pass to the OS, so that fixups can happen.
This seems like an important step, so add a message indicating that the
working FDT has changed. This is shown during the running of the bootm
command.
Signed-off-by: Simon Glass <[email protected]>
|
|
Add some information about the 'fdt addr' subcommand, to get things
started.
Signed-off-by: Simon Glass <[email protected]>
|
