Eric Lee / smarc-uboot

11 Feb, 2018

2 commits

16 Jan, 2018

3 commits

19 Dec, 2017

1 commit

17 Nov, 2017

1 commit

17 Oct, 2017

1 commit

11 Oct, 2017

1 commit

  • ad12dc184   cmd: Toggle the default value of CONFIG_CMD_IMLS ... Browse Code »

    Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

08 Sep, 2017

2 commits

28 Aug, 2017

1 commit

15 Aug, 2017

2 commits

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    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
     

10 Jul, 2017

1 commit

07 Jul, 2017

1 commit

01 May, 2017

1 commit

18 Mar, 2017

1 commit

  • 2cfe31225   configs: move CMD_MD5SUM definition to defconfigs ... Browse Code »

    Boards with an apparent need for the md5sum command had the connected
    config symbol defined in their board header file.
    Move this over to the respective defconfig files now that md5sum is
    configured via Kconfig.
    (This is a manual effort, which differs from moveconfig.py, not sure
    who is right here. Boards except sandbox loose the md5sum command with
    moveconfig.py, though it was explicitly mentioned in their config.h's)

    Signed-off-by: Andre Przywara
    Reviewed-by: Simon Glass
    [trini: migrate stih410-b2260]
    Signed-off-by: Tom Rini

    Andre Przywara
     

14 Mar, 2017

1 commit

09 Feb, 2017

1 commit

  • e9d33e732   cmd: move CONFIG_CMD_UNZIP and CONFIG_CMD_ZIP to Kconfig ... Browse Code »

    CONFIG_CMD_ZIP is not defined by any board. I am moving
    CONFIG_CMD_UNZIP to defconfig files except UniPhier SoC family.

    I am the maintainer of UniPhier platform, so I know "select CMD_UNZIP"
    is better for this platform.

    Signed-off-by: Masahiro Yamada
    Acked-by: Michal Simek
    Acked-by: Stefan Roese
    Acked-by: Ryan Harkin
    Tested-by: Ryan Harkin

    Masahiro Yamada
     

31 Jan, 2017

1 commit

28 Jan, 2017

1 commit

30 Dec, 2016

1 commit

  • e1ce61fbb   mmc: move CONFIG_SDHCI to Kconfig, renaming to CONFIG_MMC_SDHCI ... Browse Code »

    Move CONFIG_SDHCI to Kconfig and rename it to CONFIG_MMC_SDHCI.
    My motivation for the rename is, ultimately, to make all the MMC
    options prefixed with MMC_ and SDHCI options with MMC_SDHCI_,
    like Linux.

    This commit was created as follows:

    [1] Rename the config option with the following command:
    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e 's/CONFIG_SDHCI/CONFIG_MMC_SDHCI/g'

    [2] create the entry for MMC_SDHCI in drivers/mmc/Kconfig

    [3] run "tools/moveconfig.py -y MMC_SDHCI"

    [4] add "depends on MMC_SDHCI" to existing SDHCI driver entries

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Tom Rini
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

04 Dec, 2016

1 commit

  • 3337e3af5   Enable DISTRO_DEFAULT on platforms that missed it before ... Browse Code »
    20

    A number of platforms had been using the distro default feature before
    it was moved to Kconfig but did not enable the new Kconfig option when
    it was enabled. This caused a regression in terms of features and this
    introduces breakage when more things move to Kconfig.

    Signed-off-by: Tom Rini

    Tom Rini
     

24 Oct, 2016

1 commit

12 Oct, 2016

2 commits

20 Sep, 2016

1 commit

09 Sep, 2016

1 commit

12 Jul, 2016

1 commit

27 May, 2016

1 commit

  • 116362589   Rename reset to sysreset ... Browse Code »
    29

    The current reset API implements a method to reset the entire system.
    In the near future, I'd like to introduce code that implements the device
    tree reset bindings; i.e. the equivalent of the Linux kernel's reset API.
    This controls resets to individual HW blocks or external chips with reset
    signals. It doesn't make sense to merge the two APIs into one since they
    have different semantic purposes. Resolve the naming conflict by renaming
    the existing reset API to sysreset instead, so the new reset API can be
    called just reset.

    Signed-off-by: Stephen Warren
    Acked-by: Simon Glass

    Stephen Warren
     

26 Apr, 2016

3 commits

02 Apr, 2016

1 commit

  • 626f048bb   board: Add Qualcomm Dragonboard 410C support ... Browse Code »
    1

    This commit add support for 96Boards Dragonboard410C.
    It is board based on APQ8016 Qualcomm SoC, complying with
    96boards specification.
    Features (present out of the box):
    - 4x Cortex A53 (ARMv8)
    - 2x USB Host port
    - 1x USB Device port
    - 4x LEDs
    - 1x HDMI connector
    - 1x uSD connector
    - 3x buttons (Power, Vol+, Vol-/Reset)
    - WIFI, Bluetooth with integrated antenna
    - 8GiB eMMC

    U-Boot boots chained with fastboot in 64-bit mode.
    For detailed build instructions see readme.txt in board directory.

    Signed-off-by: Mateusz Kulikowski
    Tested-by: Simon Glass

    Mateusz Kulikowski