Eric Lee / smarc-uboot

14 Sep, 2014

1 commit

  • 461be2f96   kconfig: remove redundant "string" type in arch and board Kconfigs ... Browse Code »
    44

    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

  • 93d4334f7   Add board MAINTAINERS files ... Browse Code »

    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
     
  • dd84058d2   kconfig: add board Kconfig and defconfig files ... Browse Code »

    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
     

13 Mar, 2014

1 commit

  • 01286329b   kbuild: rename SRCTREE to srctree ... Browse Code »

    Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
    pointing to the top of source directory.
    (No difference between the two.)

    In Kbuild style, $(srctree) is used for instead.
    This commit renames SRCTREE to srctree and deletes the
    defition of SRCTREE.

    Note that SRCTREE in scripts/kernel-doc, scripts/docproc.c,
    doc/DocBook/Makefile should be keep.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

07 Mar, 2014

1 commit

01 Nov, 2013

1 commit

24 Jul, 2013

1 commit

13 May, 2011

1 commit

  • f0c0b3a9e   Fix incorrect use of getenv() before relocation ... Browse Code »

    A large number of boards incorrectly used getenv() in their board init
    code running before relocation. In some cases this caused U-Boot to
    hang when certain environment variables grew too long.
    Fix the code to use getenv_r().

    Signed-off-by: Wolfgang Denk
    Cc: Stefan Roese
    Cc: The LEOX team
    Cc: Michael Schwingen
    Cc: Georg Schardt
    Cc: Werner Pfister
    Cc: Dirk Eibach
    Cc: Peter De Schrijver
    Cc: John Zhan
    Cc: Rishi Bhattacharya
    Cc: Peter Tyser

    Wolfgang Denk
     

30 Apr, 2011

1 commit

  • 83b7e2a7f   Handle most LDSCRIPT setting centrally ... Browse Code »

    Currently, some linker scripts are found by common code in config.mk.
    Some are found using CONFIG_SYS_LDSCRIPT, but the code for that is
    sometimes in arch config.mk and sometimes in board config.mk. Some
    are found using an arch-specific rule for looking in CPUDIR, etc.

    Further, the powerpc config.mk rule relied on CONFIG_NAND_SPL
    when it really wanted CONFIG_NAND_U_BOOT -- which covered up the fact
    that not all NAND_U_BOOT builds actually wanted CPUDIR/u-boot-nand.lds.

    Replace all of this -- except for a handful of boards that are actually
    selecting a linker script in a unique way -- with centralized ldscript
    finding.

    If board code specifies LDSCRIPT, that will be used.
    Otherwise, if CONFIG_SYS_LDSCRIPT is specified, that will be used.

    If neither of these are specified, then the central config.mk will
    check for the existence of the following, in order:

    $(TOPDIR)/board/$(BOARDDIR)/u-boot-nand.lds (only if CONFIG_NAND_U_BOOT)
    $(TOPDIR)/$(CPUDIR)/u-boot-nand.lds (only if CONFIG_NAND_U_BOOT)
    $(TOPDIR)/board/$(BOARDDIR)/u-boot.lds
    $(TOPDIR)/$(CPUDIR)/u-boot.lds

    Some boards (sc3, cm5200, munices) provided their own u-boot.lds that
    were dead code, because they were overridden by a CPUDIR u-boot.lds under
    the old powerpc rules. These boards' own u-boot.lds have bitrotted and
    no longer work -- these lds files have been removed.

    Signed-off-by: Scott Wood
    Tested-by: Graeme Russ

    Scott Wood
     

19 Oct, 2010

1 commit

04 Aug, 2010

1 commit

  • cdb749778   Rename getenv_r() into getenv_f() ... Browse Code »

    While running from flash, i. e. before relocation, we have only a
    limited C runtime environment without writable data segment. In this
    phase, some configurations (for example with environment in EEPROM)
    must not use the normal getenv(), but a special function. This
    function had been called getenv_r(), with the idea that the "_r"
    suffix would mean the same as in the _r_eentrant versions of some of
    the C library functions (for example getdate vs. getdate_r, getgrent
    vs. getgrent_r, etc.).

    Unfortunately this was a misleading name, as in U-Boot the "_r"
    generally means "running from RAM", i. e. _after_ relocation.

    To avoid confusion, rename into getenv_f() [as "running from flash"]

    Signed-off-by: Wolfgang Denk
    Acked-by: Detlev Zundel

    Wolfgang Denk
     

31 Oct, 2008

1 commit

24 Oct, 2008

1 commit

12 Sep, 2008

1 commit

09 Sep, 2008

1 commit

05 Sep, 2008

1 commit

  • e07f4a803   ppc44x: Unification of virtex5 pp440 boards ... Browse Code »

    This patch provides an unificated way of handling xilinx v5 ppc440 boards.

    It unificates 3 different things:

    1) Source code
    A new board called ppc440-generic has been created. This board includes
    a generic tlb initialization (Maps the whole memory into virtual) and
    defines board_pre_init, checkboard, initdram and get_sys_info weakly,
    so, they can be replaced by specific functions.

    If a new board needs to redefine any of the previous functions
    (specific initialization) it can create a new directory with the
    specific initializations needed. (see the example ml507 board).

    2) Configuration file
    Common configurations are located under configs/xilinx-ppc440.h, this
    header file interpretes the xparameters file generated by EDK and
    configurates u-boot in correspondence. Example: if there is a Temac,
    allows CMD_CONFIG_NET
    Specific configuration are located under specific configuration file.
    (see the example ml507 board)

    3) Makefile
    Some work has been done in order to not duplicate work in the Main
    Makefile. Please see the attached code.

    In order to support new boards they can be implemented in the next way:

    a) Simple Generic Board (90% of the time)
    Using EDK generates a new xparameters.h file, replace
    ppc440-generic/xparameters.h and run make xilinx-ppc440-generic_config
    && make

    b) Simple Boards with special u-boot parameters (9 % of the time)
    Create a new file under configs for it (use ml507.h as example) and
    change your paramaters. Create a new Makefile paragraph and compile

    c) Complex boards (1% of the time)
    Create a new folder for the board, like the ml507

    Finally, it adds support for the Avnet FX30T Evaluation board, following
    the new generic structure:

    Cheap board by Avnet for evaluating the Virtex5 FX technology.

    This patch adds support for:
    - UartLite
    - 16MB Flash
    - 64MB RAM

    Prior using U-boot in this board, read carefully the ERRATA by Avnet
    to solve some memory initialization issues.

    Signed-off-by: Ricardo Ribalda Delgado
    Signed-off-by: Stefan Roese

    Ricardo Ribalda Delgado