1. 24 Jul, 2013 2 commits
    • Wolfgang Denk's avatar
      Add GPL-2.0+ SPDX-License-Identifier to source files · 1a459660
      Wolfgang Denk authored
      Signed-off-by: 's avatarWolfgang Denk <wd@denx.de>
      [trini: Fixup common/cmd_io.c]
      Signed-off-by: 's avatarTom Rini <trini@ti.com>
      1a459660
    • 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: 's avatarWolfgang Denk <wd@denx.de>
      eca3aeb3
  2. 23 Jul, 2013 1 commit
  3. 22 Jul, 2013 3 commits
  4. 20 Jul, 2013 1 commit
  5. 19 Jul, 2013 4 commits
  6. 17 Jul, 2013 3 commits
  7. 16 Jul, 2013 11 commits
  8. 15 Jul, 2013 7 commits
    • Wolfgang Denk's avatar
      PPC MPC83xx: Fix MPC8323ERDB build warning · f4ea9f86
      Wolfgang Denk authored
      Fix:
      
      mpc8323erdb.c: In function 'mac_read_from_eeprom':
      mpc8323erdb.c:198:3: warning: dereferencing type-punned pointer will
      break strict-aliasing rules [-Wstrict-aliasing]
      Signed-off-by: 's avatarWolfgang Denk <wd@denx.de>
      cc: Timur Tabi <timur@tabi.org>
      cc: Kim Phillips <kim.phillips@freescale.com>
      f4ea9f86
    • Frederic Leroy's avatar
      Fix ext2/ext4 filesystem accesses beyond 2TiB · 04735e9c
      Frederic Leroy authored
      With CONFIG_SYS_64BIT_LBA, lbaint_t gets defined as a 64-bit type,
      which is required to represent block numbers for storage devices that
      exceed 2TiB (the block size usually is 512B), e.g. recent hard drives
      
      We now use lbaint_t for partition offset to reflect the lbaint_t change,
      and access partitions beyond or crossing the 2.1TiB limit.
      This required changes to signature of ext4fs_devread(), and type of all
      variables relatives to block sector.
      
      ext2/ext4 fs uses logical block represented by a 32 bit value. Logical
      block is a multiple of device block sector. To avoid overflow problem
      when calling ext4fs_devread(), we need to cast the sector parameter.
      Signed-off-by: 's avatarFrédéric Leroy <fredo@starox.org>
      04735e9c
    • Lan Yixun (dlan)'s avatar
      common: remove unaligned access error in bootmenu_getoption() · 0eb33ad2
      Lan Yixun (dlan) authored
      Some ARM compilers may emit code that makes unaligned accesses when
      faced with constructs such as:
      
          char name[12] = "bootmenu_";
      
      same fix as commit: 064d55f8
      
      =========================================================
      data abort
      
          MAYBE you should read doc/README.arm-unaligned-accesses
      
      pc : [<3ff4b60c>]          lr : [<3ff4b7b0>]
      sp : 3f346a58  ip : 3ff9c8e6     fp : 02000060
      r10: 00000000  r9 : 3df47fc0     r8 : 3f347f40
      r7 : 00000000  r6 : 00000000     r5 : 00000003  r4 : 3f759140
      r3 : 000003f0  r2 : 00000000     r1 : 000003f1  r0 : 00000000
      Flags: nzCv  IRQs on  FIQs off  Mode SVC_32
      Resetting CPU ...
      ======================================================
      Signed-off-by: 's avatarLan Yixun (dlan) <dennis.yxun@gmail.com>
      0eb33ad2
    • Holger Brunck's avatar
      cramfs: fix bug for wrong filename comparison · 457dd025
      Holger Brunck authored
      "cramfsload uImage_1" succeeds even though the actual file is named
      "uImage".
      
      Fix file name comparison when one name is the prefix of the other.
      Signed-off-by: 's avatarHolger Brunck <holger.brunck@keymile.com>
      cc: Wolfgang Denk <wd@denx.de>
      cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
      457dd025
    • Gerhard Sittig's avatar
      patman: README documentation nits (unit test) · c8605bb4
      Gerhard Sittig authored
      adjust instructions for the invocation of Patman's self test: the -t
      flag appears to have a different meaning now, refer to the --test option
      for the builtin unit test; adjust a directory location and make sure to
      run the file which resides in the source directory
      Signed-off-by: 's avatarGerhard Sittig <gsi@denx.de>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>
      c8605bb4
    • Simon Glass's avatar
      scsi: Correct types of scsi_read/write() · 4f6aa346
      Simon Glass authored
      The block device expects to see lbaint_t for the blknr parameter. Change
      the SCSI read/write functions to suit.
      
      This fixes the following build warnings for coreboot:
      
      cmd_scsi.c: In function ‘scsi_scan’:
      cmd_scsi.c:119:30: error: assignment from incompatible pointer type [-Werror]
      cmd_scsi.c:120:32: error: assignment from incompatible pointer type [-Werror]
      Signed-off-by: 's avatarSimon Glass <sjg@chromium.org>
      4f6aa346
    • 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: 's avatarTom Rini <trini@ti.com>
      54e458de
  9. 12 Jul, 2013 8 commits