26 Mar, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

07 Feb, 2019

1 commit


01 Feb, 2019

1 commit


08 Jan, 2019

1 commit


04 Sep, 2018

1 commit


17 Aug, 2018

1 commit

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

21 Jul, 2018

1 commit

  • Currently the fdtfile environment variable is set to
    CONFIG_DEFAULT_DEVICE_TREE which is іnternally used as U-Boot devicetree
    source. The OS can use a different filename and Kconfig gives us the
    ability to select a default devicetree via CONFIG_DEFAULT_FDT_FILE.
    This also gives user configuring U-Boot via menuconfig the behaviour
    someone would expect.

    Signed-off-by: Klaus Goger
    Tested-By: Vagrant Cascadian
    Reviewed-by: Philipp Tomsich
    Acked-by: Philipp Tomsich

    Klaus Goger
     

04 Jun, 2018

1 commit


30 May, 2018

1 commit


26 Apr, 2018

1 commit


17 Apr, 2018

1 commit

  • We enabled CONFIG_ISO_PARTITION by default for distro boot, so that U-Boot
    could load distro images that usually get shipped as iso images. These images
    usually come with a board agnostic boot environment.

    However, there is very little point in having ISO support enabled (for anyone
    really) in SPL, as the whole idea of SPL is to load U-Boot proper which again
    is board specific. So the fact that we enable ISO support in U-Boot proper does
    not mean at all that we want ISO support in U-Boot SPL.

    Hence, let's remove the Kconfig dependency. Along the way, let's also clean up
    all those default configs that disabled SPL ISO support.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

09 Apr, 2018

1 commit


11 Feb, 2018

2 commits


02 Feb, 2018

2 commits


23 Jan, 2018

1 commit


10 Jan, 2018

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

2 commits

  • Fastboot need a bunch of options to be operating properly, such as the
    g_dnl gadget, the fastboot command, and some options that make sense. Since
    fastboot is now part of Kconfig, make sure we have them right.

    That will also reduce the boilerplate in the defconfigs.

    Reviewed-by: Łukasz Majewski
    Reviewed-by: Simon Glass
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     
  • The g_dnl USB settings for the vendor ID, product ID and manufacturer are
    actually common settings that can and should be shared by all the gadgets.

    Make them common by renaming them, and convert all the users.

    Reviewed-by: Simon Glass
    Reviewed-by: Lukasz Majewski
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     

08 Sep, 2017

2 commits


05 Sep, 2017

1 commit


02 Sep, 2017

2 commits

  • - Move ANDROID_IMAGE_SUPPORT to top level Kconfig under images as it's
    not strictly part of fastboot.
    - Add some defaults for the fastboot buffer location and size
    - Migrate all options listed in cmd/fastboot/Kconfig
    - Cleanup the README

    Signed-off-by: Tom Rini

    Tom Rini
     
  • This syncs all of the currently Kconfig'd symbols out of the headers and
    into the defconfig files. This has two exceptions, first am335x_evm
    needs to be converted to DM in SPL and then it can stop undef'ing
    CONFIG_DM_USB. Leaving this as-is results in a build failure, and
    without work, run time failure. The other case is am43xx_evm.h and in
    turn am43xx_evm_usbhost_boot. The problem here is that we need DWC3 USB
    host mode in SPL, but still desire to have gadget mode in U-Boot proper.

    Signed-off-by: Tom Rini

    Tom Rini
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


13 Aug, 2017

1 commit

  • The back-to-bootrom option is rather unfortunately named
    CONFIG_ROCKCHIP_SPL_BACK_TO_BOOTROM
    instead of
    CONFIG_SPL_ROCKCHIP_BACK_TO_BOOTROM

    To make is selectable through CONFIG_IS_ENABLED(ROCKCHIP_BACK_TO_BOOTROM),
    we need to rename it. At the same time, we introduce a TPL_ variant of
    the option to give us finer-grained control over when it should be used.

    This change is motivated by our RK3368 boot process, which returns to
    the boot ROM only from the TPL stage, but not from the SPL stage.

    Signed-off-by: Philipp Tomsich
    [added fix-up for evb-rk3229_defconfig and phycore-rk3288_defconfig:]
    [fixed inverted CONFIG_IS_ENABLED test for rk3288:]
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass
    Reviewed-by: Tom Rini

    include/configs/rock.h: undef

    Philipp Tomsich
     

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
     

11 Jul, 2017

1 commit

  • The phyCORE-RK3288 is a SoM (System on Module) containing a RK3288 SoC.
    The module can be connected to different carrier boards.
    It can be also equipped with different RAM, SPI flash and eMMC variants.
    The Rapid Development Kit option is using the following setup:

    - 1 GB DDR3 RAM (2 Banks)
    - 1x 4 KB EEPROM
    - DP83867 Gigabit Ethernet PHY
    - 16 MB SPI Flash
    - 4 GB eMMC Flash

    Add basic support for the PCM-947 carrier board, a RK3288 based development
    board made by PHYTEC. This board works in a combination with
    the phyCORE-RK3288 System on Module.

    Signed-off-by: Wadim Egorov
    Reviewed-by: Simon Glass
    Acked-by: Philipp Tomsich

    Wadim Egorov