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
     

31 Aug, 2014

1 commit


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
     

11 Apr, 2014

1 commit

  • Commit 890880583d84607e36b52a785a96b167728bbf73 introduced EEPROM parsing and
    board detection but faild to return a valid tricorder_eeprom struct for backup
    case. When pressing S200 while reading EEPROM we ignore the value. We
    returned falsely a tricorder_eeprom struct with uninitialized data which is
    just garbage.
    Initialize it by zeroing the whole structure.

    Signed-off-by: Andreas Bießmann
    Cc: Thomas Weber
    Signed-off-by: Andreas Bießmann

    Andreas Bießmann
     

10 Nov, 2013

1 commit

  • Conflicts:
    arch/arm/cpu/arm926ejs/mxs/Makefile
    board/compulab/cm_t35/Makefile
    board/corscience/tricorder/Makefile
    board/ppcag/bg0900/Makefile
    drivers/bootcount/Makefile
    include/configs/omap4_common.h
    include/configs/pdnb3.h

    Makefile conflicts are due to additions/removals of
    object files on the ARM branch vs KBuild introduction
    on the main branch. Resolution consists in adjusting
    the list of object files in the main branch version.
    This also applies to two files which are not listed
    as conflicting but had to be modified:

    board/compulab/common/Makefile
    board/udoo/Makefile

    include/configs/omap4_common.h conflicts are due to
    the OMAP4 conversion to ti_armv7_common.h on the ARM
    side, and CONFIG_SYS_HZ removal on the main side.
    Resolution is to convert as this icludes removal of
    CONFIG_SYS_HZ.

    include/configs/pdnb3.h is due to a removal on ARM side.
    Trivial resolution is to remove the file.

    Note: 'git show' will also list two files just because
    they are new:

    include/configs/am335x_igep0033.h
    include/configs/omap3_igep00x0.h

    Albert ARIBAUD
     

02 Nov, 2013

4 commits


01 Nov, 2013

1 commit


24 Jul, 2013

1 commit


09 Mar, 2013

2 commits


10 Dec, 2012

1 commit


15 May, 2012

1 commit

  • Add parameters to the OMAP MMC initialization function so the board can
    mask host capabilities and set the maximum clock frequency. While the
    OMAP supports a certain set of MMC host capabilities, individual boards
    may be more restricted and the OMAP may need to be configured to match
    the board. The PRG_SDMMC1_SPEEDCTRL bit in the OMAP3 is an example.

    Signed-off-by: Jonathan Solnit

    Jonathan Solnit
     

12 Feb, 2012

1 commit

  • Tricorder is a board which is very similar to the Devkit8000. It
    is designed as a base platform for further medical devices.

    www.corscience.de/en/medical-engineering/products/multiparameter/mp10-board.html

    Signed-off-by: Thomas Weber

    Thomas Weber