1. 17 Nov, 2013 4 commits
  2. 06 Nov, 2013 1 commit
  3. 01 Nov, 2013 2 commits
  4. 31 Oct, 2013 7 commits
  5. 16 Oct, 2013 2 commits
  6. 02 Oct, 2013 1 commit
  7. 25 Sep, 2013 1 commit
  8. 20 Sep, 2013 2 commits
  9. 17 Sep, 2013 1 commit
  10. 12 Sep, 2013 1 commit
  11. 06 Sep, 2013 1 commit
  12. 02 Sep, 2013 1 commit
  13. 27 Aug, 2013 1 commit
  14. 21 Aug, 2013 1 commit
  15. 20 Aug, 2013 1 commit
    • Ying Zhang's avatar
      TPL : introduce the TPL based on the SPL · 3aa29de0
      Ying Zhang authored
      Due to the nand SPL on some board(e.g. P1022DS)has a size limit, it can
      not be more than 4K. So, the SPL cannot initialize the DDR with the SPD
      code. This patch introduces TPL to enable a loader stub that is loaded
      by the code from the SPL. It initializes the DDR with the SPD or other
      The TPL's size is sizeable, the maximum size is decided by the memory's
      size that TPL runs. It initializes the DDR through SPD code, and copys
      final uboot image to DDR. So there are three stage uboot images:
      	* spl_boot, * tpl_boot, * final uboot image
      Signed-off-by: default avatarYing Zhang <b40530@freescale.com>
      Acked-by: default avatarYork Sun <yorksun@freescale.com>
  16. 19 Aug, 2013 2 commits
    • Joel Fernandes's avatar
      SPL: Makefile: Build a separate autoconf.mk for SPL · 39bc12dd
      Joel Fernandes authored
      SPL defines CONFIG_SPL_BUILD but this does not percolate to the
      autoconf.mk Makefile.  As a result the build breaks when
      CONFIG_SPL_BUILD is used in the board-specific include header file. With
      this, there is a possibility of having a CONFIG option defined in the
      header file but not defined in the Makefile causing all kinds of build
      failure and problems.
      It also messes things for up, for example, when one might want to
      undefine options to keep the SPL small and doesn't want to be stuck with
      the CONFIG options used for U-boot.  Lastly, this also avoids defining
      special CONFIG_SPL_ variables for cases where some options are required
      in U-boot but not in SPL.
      We add a spl-autoconf.mk rule that is generated for SPL with the
      CONFIG_SPL_BUILD flag and conditionally include it for SPL builds.
      Signed-off-by: default avatarJoel Fernandes <joelf@ti.com>
      Signed-off-by: default avatarYing Zhang <b40530@freescale.com>
    • Tom Rini's avatar
      Prepare v2013.10-rc1 · 40a60c6e
      Tom Rini authored
      Signed-off-by: default avatarTom Rini <trini@ti.com>
  17. 15 Aug, 2013 1 commit
  18. 02 Aug, 2013 1 commit
  19. 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>
  20. 23 Jul, 2013 1 commit
  21. 12 Jul, 2013 1 commit
  22. 03 Jul, 2013 1 commit
  23. 28 Jun, 2013 1 commit
  24. 26 Jun, 2013 2 commits
    • Simon Glass's avatar
      image: Add RSA support for image signing · 19c402af
      Simon Glass authored
      RSA provides a public key encryption facility which is ideal for image
      signing and verification.
      Images are signed using a private key by mkimage. Then at run-time, the
      images are verified using a private key.
      This implementation uses openssl for the host part (mkimage). To avoid
      bringing large libraries into the U-Boot binary, the RSA public key
      is encoded using a simple numeric representation in the device tree.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Add proftool to decode profile data · 6c887b2a
      Simon Glass authored
      This tool provides the facility to decode U-Boot trace data and write out
      a text file in Linux ftrace format for use with pytimechart.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  25. 21 Jun, 2013 1 commit
  26. 14 Jun, 2013 1 commit