28 Jun, 2016

3 commits

  • - update fastboot_okay() and fastboot_fail()

    This file originally came from upstream code.

    While retaining the storage abstraction feature, this is the second
    set of the changes required to resync with the
    cmd_flash_mmc_sparse_img()
    in the file
    aboot.c
    from
    https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1

    Signed-off-by: Steve Rae

    Steve Rae
     
  • This file originally came from upstream code.

    While retaining the storage abstraction feature, this is the first
    set of the changes required to resync with the
    cmd_flash_mmc_sparse_img()
    in the file
    aboot.c
    from
    https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1

    Signed-off-by: Steve Rae

    Steve Rae
     
  • This "session-id" alogrithm is not required, and currently corrupts
    the stored image whenever more the one "session" is required.

    Signed-off-by: Steve Rae

    Steve Rae
     

27 Jun, 2016

9 commits


25 Jun, 2016

26 commits


22 Jun, 2016

2 commits

  • Tom Rini
     
  • There are some cases where config options are moved, but they are
    ripped off at the final savedefconfig stage:

    - The moved option is not user-configurable, for example, due to
    a missing prompt in the Kconfig entry

    - The config was not defined in the original config header despite
    the Kconfig specifies it as non-bool type

    - The config define in the header contains reference to another
    macro, for example:
    #define CONFIG_CONS_INDEX (CONFIG_SYS_LPC32XX_UART - 2)
    The current moveconfig does not support recursive macro expansion.

    In these cases, the conversion is very likely to be an unexpected
    result. That is why I decided to display the log in yellow color
    in commit 5da4f857beac ("tools: moveconfig: report when CONFIGs are
    removed by savedefconfig").

    It would be nice to display the list of suspicious boards when the
    tool finishes processing. It is highly recommended to check the
    defconfigs once again when this message is displayed.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Joe Hershberger

    Masahiro Yamada