26 Jul, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

01 May, 2017

1 commit


16 Apr, 2017

1 commit


05 Apr, 2017

1 commit


17 Mar, 2017

1 commit

  • We are using wrong mmc instance as boot target device now. below Jaehoon Chung's
    patch use mmc alias which correct it. That make tinker board can not find mmc
    device. So give it correct mmc device instance.

    commit 02ad33aa3a84821c8d9a6c4f167f143f6248b084
    Author: Jaehoon Chung
    Date: Thu Feb 2 13:41:14 2017 +0900

    mmc: mmc-uclass: use the fixed devnum with alias node

    Signed-off-by: Eddie Cai
    Acked-by: Simon Glass

    Eddie Cai
     

10 Feb, 2017

1 commit