Eric Lee / smarc-uboot

19 Jul, 2019

1 commit

  • accb5349b   MLK-22287 imx8mn: enable CONFIG_ENV_DEFAULT_NOWHERE at default ... Browse Code »

    This CONFIG_ENV_DEFAULT_NOWHERE config must be enabled for USB download
    when we implemented the override function to select env storage medium.
    To avoid adding it to every imx8mn defconfig, enable the config as default
    on imx8mn.

    Signed-off-by: Ye Li
    (cherry picked from commit 3f94cf98113af6c31e146afcf394f34ff4d2bc00)

    Ye Li
     

17 Jul, 2019

1 commit

  • 606469c94   MLK-22279-2 env: Add a config to enable nowhere as default location ... Browse Code »

    When booting from USB there is no place to store the environment and
    should use default env. However CONFIG_ENV_IS_NOWHERE has dependence
    with other env storage config. If we enable multiple storages, NOWHERE
    can't be enabled. And saveenv won't be built if NOWHERE is set.

    This patch introduces a new CONFIG_ENV_DEFAULT_NOWHERE, that can enable
    NOWHERE as a default env location when other storage are not avaliable.
    And allow to build saveenv.

    Signed-off-by: Ye Li
    (cherry picked from commit 64c02d26555491eb7cb758f58511620c1590c378)

    Ye Li
     

24 May, 2019

1 commit

26 Mar, 2019

1 commit

  • abe66b1b5   Convert CONFIG_ENV_SPI_* to Kconfig ... Browse Code »
    24

    This converts the following to Kconfig:
    CONFIG_ENV_SPI_BUS
    CONFIG_ENV_SPI_CS
    CONFIG_ENV_SPI_MAX_HZ
    CONFIG_ENV_SPI_MODE

    Most of time these value are not needed, CONFIG_SF_DEFAULT
    with same value is used, so I introduced CONFIG_USE_ENV_SPI_*
    to force the associated value for the environment.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

25 Jan, 2019

1 commit

16 Oct, 2018

1 commit

  • ec48b6c99   arm64: versal: Add support for new Xilinx Versal ACAPs ... Browse Code »
    1

    Xilinx is introducing Versal, an adaptive compute acceleration platform
    (ACAP), built on 7nm FinFET process technology. Versal ACAPs combine
    Scalar Processing Engines, Adaptable Hardware Engines, and Intelligent
    Engines with leading-edge memory and interfacing technologies to deliver
    powerful heterogeneous acceleration for any application. The Versal AI
    Core series has five devices, offering 128 to 400 AI Engines. The series
    includes dual-core Arm Cortex™-A72 application processors, dual-core Arm
    Cortex-R5 real-time processors, 256KB of on-chip memory with ECC, more
    than 1,900 DSP engines optimized for high-precision floating point with
    low latency.

    The patch is adding necessary infrastructure in place without enabling
    platform which is done in separate patch.

    Signed-off-by: Michal Simek

    Michal Simek
     

20 Aug, 2018

1 commit

  • 4aee624c9   env: Merge Rockchip, Sunxi, Zynq and ZynqMP ... Browse Code »

    There is no reason to have the same Kconfig options for different SoCs
    separately. The patch is merging them together.

    Signed-off-by: Michal Simek
    Acked-by: Maxime Ripard
    [trini: Fix ENV_SIZE around ENV_IS_NOWHERE]
    Signed-off-by: Tom Rini

    Signed-off-by: Tom Rini

    Michal Simek
     

22 Jul, 2018

2 commits

19 Jul, 2018

1 commit

13 Jun, 2018

2 commits

09 Apr, 2018

1 commit

07 Apr, 2018

1 commit

  • f3d8f7dd7   Allow providing default environment from file ... Browse Code »
    12

    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
     

05 Apr, 2018

1 commit

04 Apr, 2018

1 commit

  • 901fb09d0   sunxi: disable direct MMC environment ... Browse Code »

    Since the dawn of time for the Allwinner support in mainline U-Boot
    we store the environment to the SD card and write directly at
    544KB from the beginning of the device. This leads to problems when
    the U-Boot proper image grows beyond 504KB and eventually overlaps.
    With one release of having the environment preferably in a FAT
    partition, let's now turn off the MMC variant fallback, so we get back
    all the space we need to implement features.

    Signed-off-by: Andre Przywara
    Reviewed-by: Jagan Teki
    Acked-by: Maxime Ripard

    Andre Przywara
     

24 Mar, 2018

2 commits

  • c0ce4ceab   Convert CONFIG_UBI_SILENCE_MSG to Kconfig ... Browse Code »

    Signed-off-by: Petr Vorel

    Petr Vorel
     
  • afb6fda2a   Convert CONFIG_UBIFS_SILENCE_MSG to Kconfig ... Browse Code »

    Introduce another difference from upstream (kernel) source in
    fs/ubifs/super.c: adding preprocessor condition as y variable in
    mount_ubifs() depends on CONFIG_UBIFS_SILENCE_MSG:
    fs/ubifs/super.c:1337:15: error: variable ?y? set but not used [-Werror=unused-but-set-variable]
    long long x, y;

    Not setting CONFIG_UBIFS_SILENCE_MSG in am335x_igep003x_defconfig and
    igep0032_defconfig. Although it was defined in their config headers, it
    depends on CMD_UBIFS which is not set for them.

    Signed-off-by: Petr Vorel
    Cc: Joe Hershberger
    Cc: Heiko Schocher

    Petr Vorel
     

27 Jan, 2018

3 commits

23 Jan, 2018

1 commit

  • 3cd084d36   env: ENV_IS_IN_FAT improvements ... Browse Code »

    Make it select FS_FAT as well, because if it's not selected, enabling
    ENV_IS_IN_FAT causes a Kconfig warning:

    warning: (ENV_IS_IN_FAT) selects FAT_WRITE which has unmet direct dependencies (FS_FAT)

    This also allows dropping some code from config_fallbacks.

    Also drop the unnecessary help text about having to enable
    CONFIG_FAT_WRITE - Kconfig automatically handles that.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

16 Jan, 2018

1 commit

  • 1087a7942   env: enable accessing the environment in an EXT4 partition ... Browse Code »

    For example to store the environment in a file named "/uboot.env" in MMC
    "0", where partition "1" contains the EXT4 filesystem, the following
    configs should be added to the board's default config:

    CONFIG_ENV_IS_IN_EXT4=y
    CONFIG_ENV_EXT4_DEVICE_AND_PART="0:1"
    CONFIG_ENV_EXT4_FILE="/uboot.env"
    CONFIG_ENV_EXT4_INTERFACE="mmc"

    Signed-off-by: Jorge Ramirez-Ortiz
    [trini: Fix some line over 80 chars issues]
    Signed-off-by: Tom Rini

    Jorge Ramirez-Ortiz
     

18 Dec, 2017

1 commit

  • 81f53b0da   rockchip: move CONFIG_ENV_SIZE and CONFIG_ENV_OFFSET to Kconfig ... Browse Code »

    This commit adds ENV_SIZE and ENV_OFFSET configuration items for
    ARCH_ROCKCHIP, but keeps these non-visible (i.e. not prompt is given).
    With these new items present, the configuration from the header files
    is moved to Kconfig.

    Keeping these non-visible is necessary to have the possibility to
    select new default values if CONFIG_IS_IN_* is changed (interactively
    or with oldconfig). Otherwise it will always be set to a previous
    value if used with a prompt. As an example if we do a defconfig with
    CONFIG_IS_IN_MMC and change it to CONFIG_IS_IN_SPI_FLASH via
    menuconfig, ENV_SIZE and ENV_OFFSET will not be changed to the correct
    values as defconfig will already have set them to the default values
    of CONFIG_IS_IN_MMC in .config.

    Signed-off-by: Klaus Goger
    Reviewed-by: Philipp Tomsich

    Klaus Goger
     

21 Nov, 2017

1 commit

27 Oct, 2017

1 commit

16 Oct, 2017

1 commit

15 Oct, 2017

1 commit

09 Sep, 2017

1 commit

  • 5eb35220b   env: Migrate CONFIG_ENV_AES to Kconfig and deprecate ... Browse Code »

    The underlying implementation for ENV_AES has security complications and
    is not recommended for use. Please see CVE-2017-3225 and CVE-2017-3226
    for more details. Mark this as deprecated now and delete this in the
    medium term if no one comes forward to re-work the support.

    Signed-off-by: Tom Rini

    Tom Rini
     

03 Sep, 2017

1 commit

  • e3f24d4f2   Kconfig: Add EEPROM options to Kconfig when I2C_EEPROM is set ... Browse Code »

    Add the following options to drivers/misc/Kconfig:
    SYS_I2C_EEPROM_ADDR
    SYS_I2C_EEPROM_BUS
    SYS_EEPROM_SIZE
    SYS_EEPROM_PAGE_WRITE_BITS
    SYS_EEPROM_PAGE_WRITE_DELAY_MS
    SYS_I2C_EEPROM_ADDR_LEN
    SYS_I2C_EEPROM_ADDR_OVERFLOW

    This does not migrate any boards, but provides a foundations for
    those who want/need these options

    Signed-off-by: Adam Ford
    [trini: Migrate uniphier]
    Signed-off-by: Tom Rini

    Adam Ford
     

20 Aug, 2017

1 commit

16 Aug, 2017

1 commit

  • c1c3fe230   env: Convert CONFIG_ENV_IS_IN... to a choice ... Browse Code »

    At present we support multiple environment drivers but there is not way to
    select between them at run time. Also settings related to the position and
    size of the environment area are global (i.e. apply to all locations).

    Until these limitations are removed we cannot really support more than one
    environment location. Adjust the location to be a choice so that only one
    can be selected. By default the environment is 'nowhere', meaning that the
    environment exists only in memory and cannot be saved.

    Also expand the help for the 'nowhere' option and move it to the top since
    it is the default.

    Signed-off-by: Simon Glass
    [trini: Move all of the imply logic to default X if Y so it works again]
    Signed-off-by: Tom Rini

    Simon Glass
     

15 Aug, 2017

2 commits