05 Mar, 2018

1 commit

  • Thomas reported U-Boot failed to build host tools if libfdt-devel
    package is installed because tools include libfdt headers from
    /usr/include/ instead of using internal ones.

    This commit moves the header code:
    include/libfdt.h -> include/linux/libfdt.h
    include/libfdt_env.h -> include/linux/libfdt_env.h

    and replaces include directives:
    #include -> #include
    #include -> #include

    Reported-by: Thomas Petazzoni
    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

12 Jan, 2015

1 commit


21 Nov, 2014

1 commit

  • This function can fail if the device tree runs out of space. Rather than
    silently booting with an incomplete device tree, allow the failure to be
    detected.

    Unfortunately this involves changing a lot of places in the code. I have
    not changed behvaiour to return an error where one is not currently
    returned, to avoid unexpected breakage.

    Eventually it would be nice to allow boards to register functions to be
    called to update the device tree. This would avoid all the many functions
    to do this. However it's not clear yet if this should be done using driver
    model or with a linker list. This work is left for later.

    Signed-off-by: Simon Glass
    Acked-by: Anatolij Gustschin

    Simon Glass
     

25 Sep, 2014

1 commit

  • Since commit ddaf5c8f3030050fcd356a1e49e3ee8f8f52c6d4
    (patman: RunPipe() should not pipe stdout/stderr unless asked),
    Patman spits lots of "Invalid MAINTAINERS address: '-'"
    error messages for patches with global changes.
    It takes too long for Patman to process them.

    Anyway, "M: -" does not carry any important information.
    Rather, it is just like a place holder in case of assigning
    a new board maintainer. Let's comment out.

    This commit can be reproduced by the following command:

    find . -name MAINTAINERS | xargs sed -i -e '/^M:[[:blank:]]*-$/s/^/#/'

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

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
     

26 Nov, 2013

1 commit


01 Nov, 2013

1 commit


17 Oct, 2013

1 commit

  • Some DDR related structures present in fsl_ddr_dimm_params.h, fsl_ddr_sdram.h, ddr_spd.h
    has various parameters with embedded acronyms capitalized that trigger the CamelCase
    warning in checkpatch.pl

    Convert those variable names to smallcase naming convention and modify all files
    which are using these structures with modified structures.

    Signed-off-by: Priyanka Jain

    Priyanka Jain
     

15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


16 Oct, 2011

1 commit

  • The top level Makefile does not do any recursion into subdirs when
    cleaning, so these clean/distclean targets in random arch/board dirs
    never get used. Punt them all.

    MAKEALL didn't report any errors related to this that I could see.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

12 Jul, 2011

1 commit


04 Apr, 2011

3 commits

  • Move fsl_ddr_get_spd into common mpc8xxx/ddr/main.c as most boards
    pretty much do the same thing. The only variations are in how many
    controllers or DIMMs per controller exist. To make this work we
    standardize on the names of the SPD_EEPROM_ADDRESS defines based on the
    use case of the board.

    We allow boards to override get_spd to either do board specific fixups
    to the SPD data or deal with any unique behavior of how the SPD eeproms
    are wired up.

    Signed-off-by: Kumar Gala

    Kumar Gala
     
  • Every 85xx board implements fsl_ddr_get_mem_data_rate via get_ddr_freq()
    and every 86xx board uses get_bus_freq(). If implement get_ddr_freq()
    as a static inline to call get_bus_freq() we can remove
    fsl_ddr_get_mem_data_rate altogether and just call get_ddr_freq()
    directly.

    Signed-off-by: Kumar Gala

    Kumar Gala
     
  • We've been utilizing board_lmb_reserve to reserve the boot page for MP
    systems. We can just move this into arch_lmb_reserve for 85xx & 86xx
    systems rather than duplicating in each board port.

    Signed-off-by: Kumar Gala

    Kumar Gala
     

19 Jan, 2011

1 commit


14 Jan, 2011

1 commit


18 Nov, 2010

1 commit

  • Before this commit, weak symbols were not overridden by non-weak symbols
    found in archive libraries when linking with recent versions of
    binutils. As stated in the System V ABI, "the link editor does not
    extract archive members to resolve undefined weak symbols".

    This commit changes all Makefiles to use partial linking (ld -r) instead
    of creating library archives, which forces all symbols to participate in
    linking, allowing non-weak symbols to override weak symbols as intended.
    This approach is also used by Linux, from which the gmake function
    cmd_link_o_target (defined in config.mk and used in all Makefiles) is
    inspired.

    The name of each former library archive is preserved except for
    extensions which change from ".a" to ".o". This commit updates
    references accordingly where needed, in particular in some linker
    scripts.

    This commit reveals board configurations that exclude some features but
    include source files that depend these disabled features in the build,
    resulting in undefined symbols. Known such cases include:
    - disabling CMD_NET but not CMD_NFS;
    - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.

    Signed-off-by: Sebastien Carlier

    Sebastien Carlier
     

28 Oct, 2010

1 commit


22 Oct, 2010

1 commit

  • Initial support for Extreme Engineering Solutions XPedite5500 -
    a P2020-based PMC/XMC single board computer.

    Signed-off-by: John Schmoller
    Signed-off-by: Peter Tyser
    Signed-off-by: Kumar Gala

    John Schmoller