16 Aug, 2017

2 commits


15 May, 2017

1 commit


20 Mar, 2017

1 commit

  • To keep a consistent MMC device mapping in SPL and in u-boot, let's
    register the MMC controllers the same way in u-boot and in the SPL.
    In terms of boot time, it doesn't hurt to register more controllers than
    needed because the MMC device is initialized only prior being accessed for
    the first time.
    Having the same device mapping in SPL and u-boot allows us to use the
    environment in SPL whatever the MMC boot device.

    Signed-off-by: Jean-Jacques Hiblot

    Jean-Jacques Hiblot
     

16 Sep, 2015

1 commit


19 Apr, 2015

1 commit


29 Oct, 2014

1 commit

  • This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     

14 Sep, 2014

1 commit

  • Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
    are specified in arch/Kconfig.

    We can delete the ones in arch and board Kconfig files.

    This commit can be easily reproduced by the following command:

    find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
    /config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
    }
    '

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

30 Jul, 2014

2 commits

  • We have switched to Kconfig and the boards.cfg file is going to
    be removed. We have to retrieve the board status and maintainers
    information from it.

    The MAINTAINERS format as in Linux Kernel would be nice
    because we can crib the scripts/get_maintainer.pl script.

    After some discussion, we chose to put a MAINTAINERS file under each
    board directory, not the top-level one because we want to collect
    relevant information for a board into a single place.

    TODO:
    Modify get_maintainer.pl to scan multiple MAINTAINERS files.

    Signed-off-by: Masahiro Yamada
    Suggested-by: Tom Rini
    Acked-by: Simon Glass

    Masahiro Yamada
     
  • This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

04 Mar, 2014

1 commit


19 Dec, 2013

1 commit

  • Currently same value is programmed for all ioregs. This is not
    the case for all SoC's like AM4372. So adding a structure for ioregs
    and updating in all board files. And also return from config_cmd_ctrl()
    and config_ddr_data() functions if data is not passed.

    Signed-off-by: Lokesh Vutla
    [trini: Fixup dxr2, cm_t335, adapt pcm051 rev3]
    Signed-off-by: Tom Rini

    Lokesh Vutla
     

04 Dec, 2013

1 commit

  • Based on the definitive guide to EMIF configuration[1] certain registers
    that we have been modifying (and are documented registers) should be
    left in their reset values rather than modified. This has been tested
    on AM335x GP EVM and Beaglebone White.

    [1]: http://processors.wiki.ti.com/index.php/AM335x_EMIF_Configuration_tips
    Cc: Enric Balletbo i Serra
    Cc: Javier Martinez Canillas
    Cc: Heiko Schocher
    Cc: Lars Poeschel
    Signed-off-by: Tom Rini
    Tested-by: Matt Porter

    Tom Rini
     

01 Nov, 2013

1 commit


16 Aug, 2013

1 commit

  • We defined PHYS_DRAM_1 to 0x80000000 (start of DRAM) and then used this
    for CONFIG_SYS_SDRAM_BASE. But then we kept on referencing PHYS_DRAM_1
    in other places. Change to directly setting CONFIG_SYS_DRAM_BASE and
    then using that name in code.

    Signed-off-by: Tom Rini

    Tom Rini
     

15 Aug, 2013

2 commits


27 Jul, 2013

1 commit


24 Jul, 2013

1 commit


18 Jun, 2013

2 commits


05 Jun, 2013

1 commit

  • We need to call the save_omap_boot_params function on am33xx/ti81xx and
    other newer TI SoCs, so move the function to boot-common. Only OMAP4+
    has the omap_hw_init_context function so add ifdefs to not call it on
    am33xx/ti81xx. Call save_omap_boot_params from s_init on am33xx/ti81xx
    boards.

    Reviewed-by: R Sricharan
    Signed-off-by: Tom Rini

    Tom Rini
     

10 May, 2013

2 commits


25 Mar, 2013

1 commit