24 Feb, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

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
     

19 Oct, 2017

1 commit

  • Up to now we depended on an exported variable to build u-boot.rom.
    We should be able to specify it in the configuration file, too.

    With this patch this becomes possible using the new Kconfig option
    CONFIG_BUILD_ROM.

    This option depends on CONFIG_X86 and is selected in
    qemu-x86_defconfig and qemu-x86_64_defconfig.

    Cc: Simon Glass
    Cc: Bin Meng
    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Bin Meng

    Heinrich Schuchardt
     

17 Oct, 2017

1 commit


13 Oct, 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
     

05 Oct, 2017

1 commit

  • The EFI selftest has been broken by a patch on efi-next.
    We should enable CONFIG_CMD_BOOTEFI_SELFTEST on
    qemu-x86_defconfig and qemu-x86_64_defconfig by default
    to catch this type of problem in the Travis CI tests.

    These systems typically have abundant memory so that
    enabling this option should not pose a problem.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt
     

24 Aug, 2017

1 commit


15 Aug, 2017

2 commits


14 Aug, 2017

1 commit


12 Aug, 2017

1 commit


01 Aug, 2017

8 commits

  • QEMU does not support ICH SPI controller yet. It's meaningless to
    include SPI flash support.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Imply Qemu-specific drivers in the platform Kconfig.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Now that all x86 boards have been converted to use DM, we can imply
    these uclass drivers (DM_ETH, DM_RTC, DM_USB, DM_VIDEO) from the
    top level.

    Previously DM_GPIO, DM_KEYBOARD, DM_SERIAL, DM_SPI, DM_SPI_FLASH
    are selected. Change to use 'imply' to allow them to be removed.

    Note with this change, chromebook_link64 build fails:

    common/built-in.o:(.data.env_htab+0xc): undefined reference to 'env_flags_validate'
    lib/built-in.o: In function `hsearch_r':
    lib/hashtable.c:380: undefined reference to 'env_callback_init'
    lib/hashtable.c:382: undefined reference to 'env_flags_init'
    make[1]: *** [spl/u-boot-spl] Error 1

    CONFIG_SPL_ENV_SUPPORT is required for chromebook_link64 to build
    again. This is just a workaround as it is not needed at all. See
    commit bda40d5 "x86: qemu: Add a config for 64-bit U-Boot" for
    the same issue seen on QEMU 64-bit target.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • This is a must have for all x86 boards.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • CONFIG_BOARD_EARLY_INIT_F literally indicates board-specific codes
    and should be not 'default y' for all x86 boards.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • PCI is the de facto interconnect bus in an x86 system.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • x86 is using the built-in libgcc implementation and this cannot be
    turned off.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Without a timer, U-Boot just doesn't boot. This is not something
    we can turn off.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     

30 Jul, 2017

1 commit

  • Kbuild complains if USB is not selected before any of host driver.

    warning: (X86) selects USB_EHCI_HCD which has unmet direct dependencies (USB)
    warning: (X86) selects USB_EHCI_HCD which has unmet direct dependencies (USB)

    Select it for X86.

    Fixes: 64d6ac5bc4a9 ("Kconfig: USB: Migrate CONFIG_USB_EHCI_HCD users to Kconfig")
    Signed-off-by: Andy Shevchenko
    [bmeng: Update all x86 boards' defconfig files to remove CONFIG_USB]
    Signed-off-by: Bin Meng

    Andy Shevchenko
     

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

1 commit


28 Jan, 2017

4 commits


26 Jan, 2017

1 commit


30 Dec, 2016

1 commit


24 Oct, 2016

6 commits


12 Oct, 2016

1 commit


10 Sep, 2016

1 commit


12 Jun, 2016

1 commit


23 May, 2016

2 commits