06 Feb, 2020

1 commit


18 Jan, 2020

1 commit


03 Dec, 2019

1 commit


12 Aug, 2019

1 commit


27 Apr, 2019

1 commit


26 Jan, 2019

1 commit

  • CLI support with the HUSH parser is not currently SPL safe due to it's
    use of realloc. That function is not defined for SPLs that use
    SYS_MALLOC_SIMPLE. CLI support can be built in to SPL and some functions
    do work, but use of some like run_command() will cause build to fail.
    When no SPL code calls this function build works as the compiler removes
    this unreachable code so the unresolved symbols are ignored.

    If DFU support is enabled in SPL then MMU DFU support may get brought in
    also, this code does make a call to run_command() causing build to fail
    if the HUSH parser is not built-in. To break this odd and unneeded
    dependency chain we use CONFIG_IS_ENABLED where appropriate to prevent
    calls into HUSH code from SPL. This also removes our need to pull in the
    rather unrelated source file when SPL_DFU is defined.

    Signed-off-by: Andrew F. Davis
    Reviewed-by: Tom Rini

    Andrew F. Davis
     

07 May, 2018

1 commit

  • 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

    Tom Rini
     

16 Aug, 2017

1 commit

  • We are now using an env_ prefix for environment functions. Rename these
    two functions for consistency. Also add function comments in common.h.

    Quite a few places use getenv() in a condition context, provoking a
    warning from checkpatch. These are fixed up in this patch also.

    Suggested-by: Wolfgang Denk
    Signed-off-by: Simon Glass

    Simon Glass
     

25 Jun, 2016

1 commit


05 Apr, 2016

1 commit


02 Apr, 2016

1 commit


05 Jan, 2016

1 commit


20 Nov, 2015

1 commit


19 Aug, 2015

1 commit

  • We have flipped CONFIG_SPL_DISABLE_OF_CONTROL. We have cleansing
    devices, $(SPL_) and CONFIG_IS_ENABLED(), so we are ready to clear
    away the ugly logic in include/fdtdec.h:

    #ifdef CONFIG_OF_CONTROL
    # if defined(CONFIG_SPL_BUILD) && !defined(SPL_OF_CONTROL)
    # define OF_CONTROL 0
    # else
    # define OF_CONTROL 1
    # endif
    #else
    # define OF_CONTROL 0
    #endif

    Now CONFIG_IS_ENABLED(OF_CONTROL) is the substitute. It refers to
    CONFIG_OF_CONTROL for U-boot proper and CONFIG_SPL_OF_CONTROL for
    SPL.

    Also, we no longer have to cancel CONFIG_OF_CONTROL in
    include/config_uncmd_spl.h and scripts/Makefile.spl.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass
    Acked-by: Linus Walleij

    Masahiro Yamada
     

27 Oct, 2014

1 commit

  • 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
    Signed-off-by: Simon Glass

    Simon Glass
     

12 Jun, 2014

1 commit

  • run_command() returns 0 on success and 1 on error. However, there are some
    invocations which expect 0 or 1 for success (not repeatable or repeatable)
    and -1 for error; add run_command_repeatable() for this purpose.

    Signed-off-by: Thomas Betker
    Acked-by: Simon Glass
    Tested-by: Simon Glass

    Thomas Betker
     

30 May, 2014

3 commits