Skip to content
Snippets Groups Projects
  1. Jul 24, 2013
    • 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
      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: <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>
      eca3aeb3
  2. Jul 23, 2013
  3. Jul 12, 2013
  4. Jul 03, 2013
  5. Jun 28, 2013
  6. Jun 26, 2013
    • 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>
      19c402af
    • 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>
      6c887b2a
  7. Jun 21, 2013
  8. Jun 14, 2013
  9. Jun 03, 2013
  10. May 28, 2013
  11. May 06, 2013
    • Marek Vasut's avatar
      arm: mxs: Preprocess u-boot.bd so they contain full path · 714dc001
      Marek Vasut authored
      
      The u-boot-imx23.bd and u-boot-imx28.bd need to be preprocessed, otherwise
      they have issues with out-of-tree build where elftosb tool couldn't sometimes
      find the u-boot.bin and spl/u-boot-spl.bin .
      
      Preprocess these .bd files with sed and insert full path to u-boot.bin and
      spl/u-boot-spl.bin to prevent this issue. Moreover, to avoid adding more
      churn into main Makefile, move all this preprocessing and u-boot.sb generation
      into CPU directory instead.
      
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Acked-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      714dc001
  12. May 01, 2013
    • Simon Glass's avatar
      Trigger generic board error only when building · fada9e20
      Simon Glass authored
      
      At present the generic board error can occur when configuring U-Boot, or
      during distclean, but this is incorrect. The existing autoconf.mk may come
      from an earlier U-Boot configuration which is about to be overwritten.
      
      Make the error conditional so that it will only be triggered when we are
      actually building U-Boot.
      
      This avoids a problem where the system is being reconfigured to remove
      CONFIG_SYS_GENERIC_BOARD on an architecture that does not support it.
      Currently this will print an error and require the manual removal of
      include/autoconf.mk.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      fada9e20
  13. Apr 22, 2013
    • Stefan Roese's avatar
      imx: Move some i.MX common functions into the imx-common directory · 8870e459
      Stefan Roese authored
      
      This patch moves the following functions into the imx-common
      directory:
      
      - mxs_wait_mask_set()
      - mxs_wait_mask_clr()
      - mxs_reset_block()
      
      These are currently used by i.MX28. But the upcoming GPMI NAND port
      for i.MX6 will also use these functions. So lets move them to a
      common location to re-use them.
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      8870e459
    • Stefan Roese's avatar
      Makefile: Add target for combined u-boot.img & spl/u-boot.bin · ecddccd0
      Stefan Roese authored
      
      This new make target "u-boot-img-spl-at-end.bin" consists of the
      the real, full-blown U-Boot image and the U-Boot SPL binary
      directly attached to it. The full-blown U-Boot image has the
      mkimage header included, with its load-address and entry-point.
      
      This will be used by the upcoming lwmon5 PPC440EPx derivate board
      port.
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      ecddccd0
  14. Apr 19, 2013
  15. Apr 15, 2013
  16. Apr 12, 2013
  17. Apr 03, 2013
  18. Apr 02, 2013
    • Vadim Bendebury's avatar
      build: Fix make errors generated when building 'distclean' · b343bbb5
      Vadim Bendebury authored
      
      It was noticed that when `make distclean' is run, the make process
      terminates with error reporting something like:
      
      rm: cannot remove '/tmp/foobar/': Is a directory
      make: *** [clobber] Error 1
      
      The problem is that the list of files targeted for removal includes a
      directory in case CONFIG_SPL_TARGET is not set.
      
      The fix has been tested as follows:
      
       Ran several times the following sequence of commands:
      
           CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- make O=/tmp/foobar smdk5250_config
           CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- make O=/tmp/foobar distclean
      
       it did not cause an error, it used to before this change.
      
      Signed-off-by: default avatarVadim Bendebury <vbendeb@chromium.org>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      b343bbb5
  19. Mar 29, 2013
  20. Mar 24, 2013
  21. Mar 12, 2013
    • Albert ARIBAUD's avatar
      Refactor linker-generated arrays · ef123c52
      Albert ARIBAUD authored
      
      Refactor linker-generated array code so that symbols
      which were previously linker-generated are now compiler-
      generated. This causes relocation records of type
      R_ARM_ABS32 to become R_ARM_RELATIVE, which makes
      code which uses LGA able to run before relocation as
      well as after.
      
      Note: this affects more than ARM targets, as linker-
      lists span possibly all target architectures, notably
      PowerPC.
      
      Conflicts:
      	arch/arm/cpu/arm926ejs/mxs/u-boot-spl.lds
      	arch/arm/cpu/arm926ejs/spear/u-boot-spl.lds
      	arch/arm/cpu/armv7/omap-common/u-boot-spl.lds
      	board/ait/cam_enc_4xx/u-boot-spl.lds
      	board/davinci/da8xxevm/u-boot-spl-da850evm.lds
      	board/davinci/da8xxevm/u-boot-spl-hawk.lds
      	board/vpac270/u-boot-spl.lds
      
      Signed-off-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
      ef123c52
  22. Mar 04, 2013
  23. Feb 15, 2013
  24. Feb 12, 2013
  25. Jan 22, 2013
  26. Jan 21, 2013
  27. Jan 16, 2013
  28. Jan 15, 2013
  29. Jan 10, 2013
  30. Dec 19, 2012
  31. Dec 14, 2012
Loading