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
     

20 Jan, 2018

1 commit

  • The following config symbols are only defined once and never referenced
    anywhere else:

    CONFIG_CYRUS
    CONFIG_IDS8313
    CONFIG_MPC8308_P1M
    CONFIG_MPC8308RDB
    CONFIG_MPC8349EMDS
    CONFIG_MPC8349ITXGP
    CONFIG_SBC8349
    CONFIG_SBC8548
    CONFIG_SBC8641D
    CONFIG_TQM834X
    CONFIG_VE8313
    CONFIG_XPEDITE5140
    CONFIG_XPEDITE5200
    CONFIG_XPEDITE550X

    Most of them are config symbols named after the respective boards which
    seems to have been a standard practice at some point.

    Signed-off-by: Tuomas Tynkkynen
    Acked-by: Mario Six

    Tuomas Tynkkynen
     

13 Dec, 2017

1 commit


04 Sep, 2017

4 commits

  • This commit removes definitions of CONFIG_SYS_BARGSIZE defined to be
    equal to CONFIG_SYS_CBSIZE in numerous configuration files.

    We remove such definitions in two situations:

    - CONFIG_SYS_CBSIZE is otherwise not defined in the board
    configuration file, which means the default value of
    CONFIG_SYS_CBSIZE == 256 applies. In this case, the default value
    of CONFIG_SYS_BARGSIZE == 512 (common/image.c) is suitable, as it is
    larger.

    - CONFIG_SYS_CBSIZE is defined in the board configuration file, but
    to a value equal or less than 512. In this case, the default value
    of CONFIG_SYS_BARGSIZE == 512 (common.image.c) is suitable, as it
    is equal or larger.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini

    Thomas Petazzoni
     
  • Now that include/config_fallbacks.h define a sane fallback for
    CONFIG_SYS_MAXARGS, we can drop the definition of this constant in all
    configurations that were using the default value.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini

    Thomas Petazzoni
     
  • Now that the fallback value of CONFIG_SYS_PBSIZE in
    include/config_fallbacks.h has been adjusted, remove its definition
    from a large number of board configuration files.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini

    Thomas Petazzoni
     
  • Now that include/config_fallbacks.h define a sane fallback for
    CONFIG_SYS_CBSIZE, we can drop the definition of this constant in all
    configurations that were using the default value.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini
    [trini: Drop from stih410-b2260.h]
    Signed-off-by: Tom Rini

    Thomas Petazzoni
     

15 Aug, 2017

1 commit


12 Aug, 2017

2 commits


26 Jul, 2017

1 commit


20 Mar, 2017

1 commit


28 Jan, 2017

1 commit


26 Jan, 2017

1 commit


05 Jan, 2017

1 commit


03 Dec, 2016

2 commits


24 Nov, 2016

1 commit


28 Oct, 2016

2 commits


10 Jun, 2016

1 commit


17 May, 2016

1 commit


04 May, 2016

1 commit


26 Apr, 2016

3 commits


15 Mar, 2016

2 commits

  • There are already two FIT options in Kconfig but the CONFIG options are
    still in the header files. We need to do a proper move to fix this.

    Move these options to Kconfig and tidy up board configuration:

    CONFIG_FIT
    CONFIG_OF_BOARD_SETUP
    CONFIG_OF_SYSTEM_SETUP
    CONFIG_FIT_SIGNATURE
    CONFIG_FIT_BEST_MATCH
    CONFIG_FIT_VERBOSE
    CONFIG_OF_STDOUT_VIA_ALIAS
    CONFIG_RSA

    Unfortunately the first one is a little complicated. We need to make sure
    this option is not enabled in SPL by this change. Also this option is
    enabled automatically in the host builds by defining CONFIG_FIT in the
    image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
    be used in files that are built on the host but must also build for U-Boot
    and SPL.

    Note: Masahiro's moveconfig.py script is amazing.

    Signed-off-by: Simon Glass
    [trini: Add microblaze change, various configs/ re-applies]
    Signed-off-by: Tom Rini

    Simon Glass
     
  • Move this option to Kconfig and tidy up existing boards.

    Signed-off-by: Simon Glass

    Simon Glass
     

22 Nov, 2015

1 commit


25 Oct, 2015

1 commit

  • We have finished Generic Board conversion for ARM and PowerPC, i.e.
    all the boards have been converted except OpenRISC, SuperH, SPARC,
    which have not supported Generic Board framework yet.

    Select SYS_GENERIC_BOARD in arch/Kconfig and delete all the macro
    defines in include/configs/*.h.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

20 Oct, 2015

5 commits

  • Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     
  • Between v2015.07-rc1 and v2015.07-rc2 this board started
    silent boot failure. A bisect led to commit 6eed3786c68c8a49d
    ("net: Move the CMD_NET config to defconfigs"). This commit
    looks harmless in itself, but it did implicitly add a feature
    to the image which led to this:

    u-boot$git describe 6eed3786c68c8a49d
    v2015.07-rc1-412-g6eed3786c68c
    ^^^

    u-boot$ls -l ../41*/u-boot.bin
    -rwxrwxr-x 1 paul paul 261476 Oct 16 16:47 ../411/u-boot.bin
    -rwxrwxr-x 1 paul paul 266392 Oct 16 16:43 ../412/u-boot.bin
    u-boot$bc
    bc 1.06.95
    Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
    This is free software with ABSOLUTELY NO WARRANTY.
    For details type `warranty'.
    256*1024
    262144

    i.e. we finally broke through the 256k monitor size. Jump it
    up to 384k and fix the hard coded value used in the env offset
    at the same time.

    We were probably flirting with the 256k size issue without
    knowing it when testing on different baselines in earlier
    commits, but since this is all board specific, a rebase or
    reorder to put this commit 1st is of little value.

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     
  • When debugging an env fail due to too small a malloc pool, it
    was noted that the env write was 256k. But the device sector
    size is 1/2 that, as can be seen from "fli" output:

    Bank # 1: CFI conformant flash (16 x 16) Size: 16 MB in 131 Sectors
    Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x1888
    Erase timeout: 4096 ms, write timeout: 1 ms
    Buffer write timeout: 2 ms, buffer size: 64 bytes

    Sector Start Addresses:
    FF000000 E RO FF020000 E RO FF040000 E RO FF060000 E RO FF080000 E RO
    FF0A0000 E RO FF0C0000 E RO FF0E0000 E RO FF100000 E RO FF120000 E RO
    [...]
    FFF00000 RO FFF20000 RO FFF40000 RO FFF60000 RO FFF80000 RO
    FFFA0000 RO FFFC0000 RO FFFE0000 E RO FFFE8000 RO FFFF0000 E RO
    FFFF8000 RO
    =>

    The desired env sector is FFF40000->FFF60000, or 0x20000 in length,
    just after the 256k u-boot image which starts @ FFF00000.

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     
  • Currently the board fails to save its env, since the env size
    is much smaller than the sector size, and the malloc fails for
    the pad buffer, giving the user visible symptom of:

    Unable to save the rest of sector (253952)

    Allow for 1M malloc pool, the same as used on the sbc8548 board.

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     
  • It is just too painful to use interactively without it.

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     

26 Jun, 2015

1 commit


20 May, 2015

1 commit


25 Jan, 2014

1 commit


13 Dec, 2013

1 commit