26 Apr, 2018

1 commit


27 Jan, 2018

3 commits


23 Jan, 2018

1 commit

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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