20 Feb, 2014

3 commits

  • Conflicts:
    Makefile
    drivers/net/npe/Makefile

    These two conflicts arise from commit 0b2d3f20
    ("ARM: NET: Remove the IXP NPE ethernet driver") and are
    resolved by deleting the drivers/net/npe/Makefile file
    and removing the CONFIG_IXP4XX_NPE line from Makefile.

    Albert ARIBAUD
     
  • Before this commit, "make tidy" did
    "make clean" + delete "*.depend*" files.

    But, we do not have "*.depend*" files any more,
    which means "make tidy" is the same as "make clean".

    This commit removes the redandant target "tidy".

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • This commit changes the working directory
    where the build process occurs.

    Before this commit, build process occurred under the source
    tree for both in-tree and out-of-tree build.

    That's why we needed to add $(obj) prefix to all generated
    files in makefiles like follows:
    $(obj)u-boot.bin: $(obj)u-boot

    Here, $(obj) is empty for in-tree build, whereas it points
    to the output directory for out-of-tree build.

    And our old build system changes the current working directory
    with "make -C " syntax when descending into the
    sub-directories.

    On the other hand, Kbuild uses a different idea
    to handle out-of-tree build and directory descending.

    The build process of Kbuild always occurs under the output tree.
    When "O=dir/to/store/output/files" is given, the build system
    changes the current working directory to that directory and
    restarts the make.

    Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj="
    syntax for descending into sub-directories.
    (We can write it like "make $(obj)=" with a shorthand.)
    This means the current working directory is always the top
    of the output directory.

    Signed-off-by: Masahiro Yamada
    Tested-by: Gerhard Sittig

    Masahiro Yamada
     

19 Feb, 2014

1 commit


07 Feb, 2014

1 commit


06 Feb, 2014

1 commit


09 Jan, 2014

1 commit


25 Nov, 2013

1 commit

  • Some board have multiple configurations.
    For example, the board "m54455evb" has many configurations:
    M54455EVB, M54455EVB_a66, M54455EVB_i66, M54455EVB_intel, ...

    When we modify board-related files, we need to test
    all configurations based on such a board.

    In such a case, the new option -b is useful.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

08 Nov, 2013

4 commits


15 Oct, 2013

1 commit


08 Oct, 2013

1 commit


12 Sep, 2013

1 commit


24 Jul, 2013

1 commit

  • Like many other projects, U-Boot has a tradition of including big
    blocks of License headers in all files. This not only blows up the
    source code with mostly redundant information, but also makes it very
    difficult to generate License Clearing Reports. An additional problem
    is that even the same lincenses are referred to by a number of
    slightly varying text blocks (full, abbreviated, different
    indentation, line wrapping and/or white space, with obsolete address
    information, ...) which makes automatic processing a nightmare.

    To make this easier, such license headers in the source files will be
    replaced with a single line reference to Unique Lincense Identifiers
    as defined by the Linux Foundation's SPDX project [1]. For example,
    in a source file the full "GPL v2.0 or later" header text will be
    replaced by a single line:

    SPDX-License-Identifier: GPL-2.0+

    We use the SPDX Unique Lincense Identifiers here; these are available
    at [2].

    Note: From the legal point of view, this patch is supposed to be only
    a change to the textual representation of the license information,
    but in no way any change to the actual license terms. With this patch
    applied, all files will still be licensed under the same terms they
    were before.

    Note 2: The apparent difference between the old "COPYING" and the new
    "Licenses/gpl-2.0.txt" only results from switching to the upstream
    version of the license which is differently formatted; there are not
    any actual changes to the content.

    Note 3: There are some recurring questions about linense issues, such
    as:
    - Is a "All Rights Reserved" clause a problem in GPL code?
    - Are files without any license header a problem?
    - Do we need license headers at all?

    The following excerpt from an e-mail by Daniel B. Ravicher should help
    with these:

    | Message-ID:
    | Date: Wed, 21 Oct 2009 18:35:22 -0400
    | From: "Daniel B. Ravicher"
    | To: Wolfgang Denk
    | Subject: Re: GPL and license cleanup questions
    |
    | Mr. Denk,
    |
    | Wolfgang Denk wrote:
    | > - There are a number of files which do not include any specific
    | > license information at all. Is it correct to assume that these files
    | > are automatically covered by the "GPL v2 or later" clause as
    | > specified by the COPYING file in the top level directory of the
    | > U-Boot source tree?
    |
    | That is a very fact specific analysis and could be different across the
    | various files. However, if the contributor could reasonably be expected
    | to have known that the project was licensed GPLv2 or later at the time
    | she made her contribution, then a reasonably implication is that she
    | consented to her contributions being distributed under those terms.
    |
    | > - Do such files need any clean up, for example should we add GPL
    | > headers to them, or is this not needed?
    |
    | If the project as a whole is licensed under clear terms, you need not
    | identify those same terms in each file, although there is no harm in
    | doing so.
    |
    | > - There are other files, which include both a GPL license header
    | > _plus_ some copyright note with an "All Rights Reserved" clause. It
    | > has been my understanding that this is a conflict, and me must ask
    | > the copyright holders to remove such "All Rights Reserved" clauses.
    | > But then, some people claim that "All Rights Reserved" is a no-op
    | > nowadays. License checking tools (like OSLC) seem to indicate this is
    | > a problem, but then we see quite a lot of "All rights reserved" in
    | > BSD-licensed files in gcc and glibc. So what is the correct way to
    | > deal with such files?
    |
    | It is not a conflict to grant a license and also reserve all rights, as
    | implicit in that language is that you are reserving all "other" rights
    | not granted in the license. Thus, a file with "Licensed under GPL, All
    | Rights Reserved" would mean that it is licensed under the GPL, but no
    | other rights are given to copy, modify or redistribute it.
    |
    | Warm regards,
    | --Dan
    |
    | Daniel B. Ravicher, Legal Director
    | Software Freedom Law Center (SFLC) and Moglen Ravicher LLC
    | 1995 Broadway, 17th Fl., New York, NY 10023
    | (212) 461-1902 direct (212) 580-0800 main (212) 580-0898 fax
    | ravicher@softwarefreedom.org www.softwarefreedom.org

    [1] http://spdx.org/
    [2] http://spdx.org/licenses/

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

15 Jul, 2013

1 commit

  • The files board/qi/qi_lb60/qi_lb60.c and include/configs/qi_lb60.h were
    licensed under the GPL v3 or later, and not v2 or later. As this is
    incompatible with the project, revert this board support until the
    responsible parties are available to re-license (if so desired) under
    GPL v2.

    Signed-off-by: Tom Rini

    Tom Rini
     

15 May, 2013

1 commit


03 Apr, 2013

1 commit


28 Mar, 2013

1 commit


12 Mar, 2013

1 commit

  • ps on BSD hosts (like OS X) do not provide the --no-headers switch nor
    understand the AIX format descriptions. Unfortunately there seems no solution to
    get the PIDs of children in a platfrom independent manner.
    Therefore detect the OS and decide upon that which way to go.

    This patch makes the MAKEALL script cleanly stoppable on bare OS X when using
    the parallel builds of targets.

    Additionally this patch removes double call to grep by a single call to sed for
    GNU style child PID detection.

    Signed-off-by: Andreas Bießmann
    Cc: Joe Hershberger
    Acked-by: Joe Hershberger

    Andreas Bießmann
     

20 Feb, 2013

1 commit

  • Add support for per architecture CROSS_COMPILE toolchain definitions
    via CROSS_COMPILE_ARCH where "ARCH" is any of the supported u-boot
    architectures. This allows building every supported u-boot board in a
    single pass of MAKEALL.

    Signed-off-by: Allen Martin
    Acked-by: Simon Glass
    Reviewed-by: Stephen Warren

    Allen Martin
     

07 Dec, 2012

2 commits

  • --continue will allow you to the MAKEALL and pick up where
    you left off.

    --rebuild-errors will allow you to rebuild only those boards which
    had trouble on the last run of MAKEALL, allowing you to quickly test
    a simple fix on just those boards.

    Signed-off-by: Joe Hershberger
    Acked-by: Simon Glass
    Tested-by: Simon Glass

    Joe Hershberger
     
  • When building in parallel, make sure that we look up the children
    based on the the actual process group id instead of just assuming
    that the MAKEALL pid is the process group id.

    Also ensure that logs from incomplete builds are deleted in the
    process.

    Signed-off-by: Joe Hershberger
    Acked-by: Simon Glass
    Tested-by: Simon Glass

    Joe Hershberger
     

07 Nov, 2012

1 commit


30 Oct, 2012

1 commit

  • When BUILD_NBUILDS is > 1 we run the tidy command. With the addition of
    DocBook this now includes a -C doc/DocBook and a 'entering/leaving' pair
    of messages happen. Since we don't want to see what's being cleaned
    here, we can just invoke make -s like we do when building.

    Signed-off-by: Tom Rini

    Tom Rini
     

16 Oct, 2012

2 commits


26 Sep, 2012

1 commit

  • The LIST_arm rule included the Atmel boards twice (by virtue of
    including both LIST_at91 and LIST_ARM9) and was missing all the
    arm720t, arm946es, and arm1176 boards. Change this list to use
    boards_by_arch() which is less error prone. After this change
    "./MAKEALL arm" and "./MAKEALL -a arm" build the same boards.

    Also fix up some missing and duplicate boards to arm, mips, and m68k.

    Signed-off-by: Allen Martin
    Acked-by: Tom Rini

    Allen Martin
     

01 Sep, 2012

1 commit

  • Update MAKEALL to handle the optional SPL CPU field that was added to
    boards.cfg. This impacts the cases in MAKEALL that have to match
    against CPU type (field 3). In these cases use ':' as a field
    separator to split the u-boot CPU from the SPL CPU.

    Signed-off-by: Allen Martin
    Signed-off-by: Tom Warren

    Allen Martin
     

10 Aug, 2012

1 commit

  • If we build everything correctly with multiple builds, and an
    ERR directory had been previously created, we failed to report
    that everything was fine because grep failed to find anything
    in the ERR directory. Use grep -r, which doesn't complain if
    there are no input files.

    Signed-off-by: Andy Fleming
    Tested-by: Tom Rini

    Andy Fleming
     

22 May, 2012

2 commits


18 May, 2012

2 commits

  • The patch that added parallel builds broke MAKEALL -l, so this
    fixes that. At the same time, it improves the termination so
    that it shuts down the build threads if you cancel the build.
    Lastly, it removes a bunch of debug code.

    Signed-off-by: Andy Fleming
    Tested-by: Wolfgang Denk

    Andy Fleming
     
  • pdnb3 and scpu are explicitly on LIST_ixp, even though they are
    also specified in boards.cfg as having cpu ixp. This means that
    they will be built twice when doing ./MAKEALL ixp, or ./MAKEALL arm.

    This was pointless before, but actually breaks things if you launch
    both builds at the same time, as they overwrite each other.

    Signed-off-by: Andy Fleming

    Andy Fleming
     

30 Apr, 2012

1 commit

  • The MAKEALL script cleverly runs make with the appropriate options
    to use all of the cores on the system, but your average U-Boot build
    can't make much use of more than a few cores. If you happen to have
    a many-core server, your builds will leave most of the system idle.

    In order to make full use of such a system, we need to build multiple
    targets in parallel, and this requires directing make output into
    multiple directories. We add a BUILD_NBUILDS variable, which allows
    users to specify how many builds to run in parallel.
    When BUILD_NBUILDS is set greater than 1, we redefine BUILD_DIR for
    each build to be ${BUILD_DIR}/${target}. Also, we make "./build" the
    default BUILD_DIR when BUILD_NBUILDS is greater than 1.

    MAKEALL now tracks which builds are still running, and when one
    finishes, it starts a new build.

    Once each build finishes, we run "make tidy" on its directory, to reduce
    the footprint.

    As a result, we are left with a build directory with all of the built
    targets still there for use, which means anyone who wanted to use
    MAKEALL as part of a test harness can now do so.

    Signed-off-by: Andy Fleming

    Andy Fleming
     

31 Mar, 2012

1 commit

  • The -m option tries to find the board in MAINTAINERS file and figure out the
    email. The -M option lists boards including their maintainers emails and all
    affiliated emails. There are multiple strategies used to retrieve these emails:

    1) Check board/ with git log and use three most recent emails
    2) Check board/ with git log and use three most used emails
    3) Try finding board in MAINTAINERS file and retrieve all emails from there

    The result is then sorted and unique results are retrieved and reported.

    For -m option, only strategy 3) is used.

    Signed-off-by: Marek Vasut
    Cc: Wolfgang Denk

    Marek Vasut
     

26 Mar, 2012

1 commit


14 Jan, 2012

1 commit


11 Dec, 2011

1 commit