18 Aug, 2018

1 commit


21 Jul, 2018

1 commit

  • The test for (CONFIG_BOOTDELAY >= 0) has been in U-Boot since the
    beginning, but the meaning of it has changed over time. Allow the
    default to be set for any value, including -ve ones. This allows
    (for example) CONFIG_ENV_IS_NOWHERE to have values for bootdelay in
    its compiled in environment.

    The only thing this changes is where the default for bootdelay can be
    fetched from; before this change you get a compiled in default, after
    you'll pull it from the default value in the environment, but both values
    will be the same. Also if there's a value set in the environment then
    that will take precedence (as before).

    Signed-off-by: Alex Kiernan

    Alex Kiernan
     

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
     

09 Apr, 2018

1 commit


07 Apr, 2018

2 commits

  • Modifying the default environment via CONFIG_EXTRA_ENV_SETTINGS is
    somewhat inflexible, partly because the cpp language does not allow
    appending to an existing macro. This prevents reuse of "environment
    fragments" for different boards, which in turn makes maintaining that
    environment consistently tedious and error-prone.

    This implements a Kconfig option for allowing one to define the entire
    default environment in an external file, which can then, for example, be
    generated programmatically as part of a Yocto recipe, or simply be kept
    in version control separately from the U-boot repository.

    Tested-by: Sean Nyekjaer
    Signed-off-by: Rasmus Villemoes
    Reviewed-by: Lukasz Majewski

    Rasmus Villemoes
     
  • Commit 7653942b10e9e ("common/env_embedded.c: drop support for
    CONFIG_SYS_USE_PPCENV") dropped the .ppcenv section which was
    used in linking scripts to allow fine placement of embedded
    environment sections.

    This implies that GCC randomly places objects from env/embedded.o
    and environment is not guaranteed to be located at the correct address:

    04003df8 g F .text 00000038 mii_init
    04004000 g O .text 00000004 env_size
    04004004 g O .text 00002000 environment
    04006004 g F .text 00000040 .hidden __lshrdi3

    This patch restores this capability by allocating each object marked
    with __UBOOT_ENV_SECTION__ into a different section. Hence
    'environment' will be alone in .text.environment, allowing a
    fine placement in u-boot.lds with:

    . = DEFINED(env_offset) ? env_offset : .;
    env/embedded.o (.text.environment)

    Fixes: 7653942b10e9e ("common/env_embedded.c: drop support for CONFIG_SYS_USE_PPCENV")
    Cc: Thomas Petazzoni
    Signed-off-by: Christophe Leroy

    Christophe Leroy
     

15 Aug, 2017

1 commit


05 Aug, 2017

1 commit

  • The environment has pretty much nothing to do with just "PPC", so
    rename the macros to just __UBOOT_ENV_SECTION__ which is more
    readable.

    In addition, only a single macro is needed: the environment now goes
    either to the default section (USE_HOSTCC is defined) or in the .text
    section.

    Signed-off-by: Thomas Petazzoni

    Thomas Petazzoni
     

25 Jun, 2016

1 commit


20 May, 2015

1 commit


15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


14 Dec, 2012

2 commits


03 Nov, 2012

1 commit

  • CONFIG_ENV_VARS_UBOOT_CONFIG creates environment variables indicating
    which configuration U-Boot was built for. Some U-Boot binaries run on
    multiple boards, and hence this information may not uniquley describe
    the HW that U-Boot is actually running on. Another patch introduces
    environment variable board_name to represent that. In order to avoid
    scripts having to check $board_name, use it if set, and then fall back
    to using $board, make CONFIG_ENV_VARS_UBOOT_CONFIG also set a default
    value for board_name, so that variable is always available.

    Signed-off-by: Stephen Warren
    Acked-by: Joe Hershberger

    Stephen Warren
     

20 Oct, 2012

1 commit