11 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

12 Jan, 2018

1 commit


13 Dec, 2017

1 commit


28 Nov, 2017

1 commit


06 Nov, 2017

1 commit


11 Oct, 2017

1 commit

  • 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
     

04 Oct, 2017

1 commit

  • When we import code from Linux, with regular re-sync planned, we want
    to use printk() and pr_*(). U-Boot does not support them in a clean
    way. So, people end up with local macros, or compat headers here and
    there, then we occasionally see build errors of definition conflicts.

    We have include/linux/compat.h, but putting all sorts of unrelated
    things into a single header is just a temporal workaround. Hence this
    patch, to find the best home for all printk variants. If you want to
    use printk() and friends, please include . This header
    is self-contained, and pulls in only a few headers.

    When I was testing this clean-up, I noticed the image size exceeded
    its platform limit on some boards. This is because all pr_*() that
    were previously defined as no-op in include/linux/mtd/mtd.h (unless
    CONFIG_MTD_DEBUG is set), are now enabled.

    To make such boards happy, this commit also implements CONFIG_LOGLEVEL.
    The concept is similar to the kernel parameter "loglevel". (Actually,
    the Kconfig help message was taken from kernel-paremeter.txt of Linux)
    Messages with a loglevel smaller than console loglevel will be printed.

    The difference is the loglevel is build-time determined. To save the
    image size, lower priority pr_*() are compiled out. I set the default
    of CONFIG_LOGLEVEL to 6, i.e. pr_notice and higher priority messages
    are compiled in.

    I adjusted CONFIG_LOGLEVEL to avoid build error for some boards.

    Signed-off-by: Masahiro Yamada
    [trini: Add in SPL_LOGLEVEL that is the same as LOGLEVEL]
    Signed-off-by: Tom Rini

    Masahiro Yamada
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


01 Aug, 2017

1 commit

  • Migrate all remaining instances of CMD_NAND, CMD_NAND_TRIMFFS
    CMD_NAND_LOCK_UNLOCK and CMD_NAND_TORTURE from the headers into the
    defconfig files.

    Tested-by: Adam Ford
    Signed-off-by: Tom Rini
    Reviewed-by: Bin Meng

    Tom Rini
     

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
     

23 May, 2017

2 commits


16 May, 2017

1 commit


19 Mar, 2017

1 commit

  • Today, we have cases where we wish to build all of U-Boot in Thumb2 mode for
    various reasons. We also have cases where we only build SPL in Thumb2 mode due
    to size constraints and wish to build the rest of the system in ARM mode. So
    in this migration we introduce a new symbol as well, SPL_SYS_THUMB_BUILD to
    control if we build everything or just SPL (or in theory, just U-Boot) in
    Thumb2 mode.

    Signed-off-by: Tom Rini
    Acked-by: Siarhei Siamashka

    Tom Rini
     

28 Jan, 2017

1 commit


12 Oct, 2016

1 commit


27 Sep, 2016

1 commit


20 Sep, 2016

1 commit


10 Sep, 2016

1 commit


10 Jun, 2016

1 commit


26 Apr, 2016

2 commits


15 Mar, 2016

1 commit


22 Nov, 2015

1 commit


10 Nov, 2015

1 commit

  • Revert commit 7a2c1b13 which dropped OpenRD boards.
    Assume maintainership of OpenRD.
    Remove OpenRD from scrapyard.
    Switch OpenRD to generic board.
    Switch to Thumb build.

    Signed-off-by: Albert ARIBAUD

    Albert ARIBAUD
     

12 Sep, 2015

1 commit


26 Jun, 2015

1 commit


01 Jun, 2015

1 commit


13 May, 2015

1 commit

  • In order to reduce merge conflicts and to maintain the simplest possible
    defconfig files, we should be using the savedefconfig feature of Kconfig
    every time a new feature is added. This keeps the defconfig settings to
    a minimum (only those things not default) and keeps them in the same
    order as the Kconfig options.

    Signed-off-by: Joe Hershberger
    Cc: Masahiro Yamada
    Acked-by: Stephen Warren
    Cc: Tom Rini

    Joe Hershberger
     

31 Aug, 2014

1 commit


30 Jul, 2014

1 commit

  • This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada