1. 20 Apr, 2014 2 commits
  2. 19 Feb, 2014 2 commits
    • Masahiro Yamada's avatar
      Makefile: remove a cleaning target "tidy" · 7390643f
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
    • Masahiro Yamada's avatar
      kbuild: change out-of-tree build · 9e414032
      Masahiro Yamada authored
      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 <sub-dir>" syntax when descending into the
      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=<sub-dir>"
      syntax for descending into sub-directories.
      (We can write it like "make $(obj)=<sub-dir>" with a shorthand.)
      This means the current working directory is always the top
      of the output directory.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
  3. 07 Feb, 2014 1 commit
  4. 06 Feb, 2014 1 commit
  5. 09 Jan, 2014 1 commit
  6. 25 Nov, 2013 1 commit
    • Masahiro Yamada's avatar
      MAKEALL: add -b (--board) option · 4d1584bd
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
  7. 08 Nov, 2013 4 commits
  8. 14 Oct, 2013 1 commit
  9. 07 Oct, 2013 1 commit
  10. 12 Sep, 2013 1 commit
  11. 24 Jul, 2013 1 commit
    • Wolfgang Denk's avatar
      Licenses: introduce SPDX Unique Lincense Identifiers · eca3aeb3
      Wolfgang Denk authored
      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
          - 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: <4ADF8CAA.5030808@softwarefreedom.org>
      | Date: Wed, 21 Oct 2009 18:35:22 -0400
      | From: "Daniel B. Ravicher" <ravicher@softwarefreedom.org>
      | To: Wolfgang Denk <wd@denx.de>
      | 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: default avatarWolfgang Denk <wd@denx.de>
  12. 15 Jul, 2013 1 commit
    • Tom Rini's avatar
      Revert "MIPS: Jz4740: Add qi_lb60 board support" · 54e458de
      Tom Rini authored
      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: default avatarTom Rini <trini@ti.com>
  13. 15 May, 2013 1 commit
  14. 02 Apr, 2013 1 commit
  15. 27 Mar, 2013 1 commit
  16. 11 Mar, 2013 1 commit
    • Andreas Bießmann's avatar
      MAKEALL: fix kill_children for BSD hosts · 6bdd9f89
      Andreas Bießmann authored
      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: default avatarAndreas Bießmann <andreas.devel@googlemail.com>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Acked-by: default avatarJoe Hershberger <joe.hershberger@ni.com>
  17. 20 Feb, 2013 1 commit
  18. 06 Dec, 2012 2 commits
  19. 07 Nov, 2012 1 commit
  20. 29 Oct, 2012 1 commit
    • Tom Rini's avatar
      MAKEALL: Add -s to '${MAKE} tidy' section · ed296d20
      Tom Rini authored
      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: default avatarTom Rini <trini@ti.com>
  21. 15 Oct, 2012 2 commits
  22. 25 Sep, 2012 1 commit
    • Allen Martin's avatar
      MAKEALL: fix per arch board lists · cce5d210
      Allen Martin authored
      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: default avatarAllen Martin <amartin@nvidia.com>
      Acked-by: default avatarTom Rini <trini@ti.com>
  23. 01 Sep, 2012 1 commit
  24. 09 Aug, 2012 1 commit
  25. 22 May, 2012 2 commits
  26. 18 May, 2012 2 commits
  27. 30 Apr, 2012 1 commit
    • Andy Fleming's avatar
      Allow for parallel builds and saved output · f588bb03
      Andy Fleming authored
      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: default avatarAndy Fleming <afleming@freescale.com>
  28. 30 Mar, 2012 1 commit
    • Marek Vasut's avatar
      MAKEALL: Add -m/-M option to determine maintainers · 9b96c6b1
      Marek Vasut authored
      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/<boardname> with git log and use three most recent emails
      2) Check board/<boardname> 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: default avatarMarek Vasut <marex@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
  29. 26 Mar, 2012 1 commit
  30. 13 Jan, 2012 1 commit
  31. 10 Dec, 2011 1 commit