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
     

07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

16 Mar, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_CONS_INDEX

    We have existing entries for this option in a number of places, with
    different guards on them. They're also sometimes used for things not
    directly inside of the serial driver. First, introduce a new symbol to
    guard the use of CONFIG_CONS_INDEX, so that in the case where we don't
    need this for the serial driver, but for some other use, we can still do
    it. Next, consolidate all of these into the single entry in
    drivers/serial/Kconfig. Finally, introduce CONS_INDEX_[023456] so that
    we can imply a correct value here to make the defconfig side of this
    smaller.

    Signed-off-by: Adam Ford
    [trini: Rework a lot of the logic here, such that I took authorship from
    Adam, but kept his S-o-B line]
    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

09 Feb, 2018

1 commit

  • config_fallbacks.h had some logic to automatically select
    LIB_RAND if RANDOM_UUID or CMD_UUID were set if LIB_HW_RAND wasn't
    already selected. By migrating LIB_HW_RAND to Kconfig, we can
    remove this check from config_fallbacks.h and put it into Kconfig

    Signed-off-by: Adam Ford
    Reviewed-by: Lukasz Majewski
    [trini: Turn into a choice, add NET_RANDOM_ETHADDR]
    Signed-off-by: Tom Rini

    Adam Ford
     

29 Jan, 2018

1 commit


04 Sep, 2017

2 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 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
     

15 Aug, 2017

1 commit


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
     

20 Mar, 2017

1 commit


13 Feb, 2017

1 commit

  • We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
    not completed. Finish this work by the tool.

    During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
    Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
    than those of "#ifdef CONFIG_SYS_NO_FLASH". Flipping the logic will
    make the code more readable. Besides, negative meaning symbols do
    not fit in obj-$(CONFIG_...) style Makefiles.

    This commit was created as follows:

    [1] Edit "default n" to "default y" in the config entry in
    common/Kconfig.

    [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"

    [3] Rename the instances in defconfigs by the following:
    find . -path './configs/*_defconfig' | xargs sed -i \
    -e '/CONFIG_SYS_NO_FLASH=y/d' \
    -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'

    [4] Change the conditionals by the following:
    find . -name '*.[ch]' | xargs sed -i \
    -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
    -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
    -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
    -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'

    [5] Modify the following manually
    - Rename the rest of instances
    - Remove the description from README
    - Create the new Kconfig entry in drivers/mtd/Kconfig
    - Remove the old Kconfig entry from common/Kconfig
    - Remove the garbage comments from include/configs/*.h

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

04 Dec, 2016

1 commit


20 Sep, 2016

1 commit


10 Jun, 2016

1 commit


27 May, 2016

1 commit

  • We have a bunch of boards that define their vendor class identifier and
    client archs in the board files or in the distro config. Move everything
    to the generic Kconfig options.

    We're missing the distinction between i386 and x86_64, as I couldn't find
    any config variable that would tell us the difference. Is that really important
    to people? I guess not, so I left it out.

    Signed-off-by: Alexander Graf
    Reviewed-by: Tom Rini

    Alexander Graf
     

26 Apr, 2016

2 commits


16 Mar, 2016

4 commits

  • By now the code to only have a single page table level with 64k page
    size and 42 bit address space is no longer used by any board in tree,
    so we can safely remove it.

    To clean up code, move the layerscape mmu code to the new defines,
    removing redundant field definitions.

    Signed-off-by: Alexander Graf

    Alexander Graf
     
  • The MMU range table can vary depending on things we may only find
    out at runtime. While the very simple ThunderX variant does not
    change, other boards will, so move the definition from a static
    entry in a header file to the board file.

    Signed-off-by: Alexander Graf

    Alexander Graf
     
  • The idea to generate our pages tables from an array of memory ranges
    is very sound. However, instead of hard coding the code to create up
    to 2 levels of 64k granule page tables, we really should just create
    normal 4k page tables that allow us to set caching attributes on 2M
    or 4k level later on.

    So this patch moves the full_va mapping code to 4k page size and
    makes it fully flexible to dynamically create as many levels as
    necessary for a map (including dynamic 1G/2M pages). It also adds
    support to dynamically split a large map into smaller ones when
    some code wants to set dcache attributes.

    With all this in place, there is very little reason to create your
    own page tables in board specific files.

    Signed-off-by: Alexander Graf

    Alexander Graf
     
  • Based on the memory map we can determine a lot of hard coded fields of
    TCR, like the maximum VA and max PA we want to support. Calculate those
    dynamically to reduce the chance for pit falls.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

15 Mar, 2016

1 commit


20 Jan, 2016

2 commits