Skip to content
Snippets Groups Projects
  1. Aug 09, 2013
    • York Sun's avatar
      mpc85xx: Base emulator support · cb93071b
      York Sun authored
      
      Prepare for emulator support for mpc85xx parts.
      Disable DDR training and skip wrlvl_cntl_2 and wrlvl_cntl_3 registers.
      These two registers improve stability but not supported by emulator.
      Add CONFIG_FSL_TBCLK_EXTRA_DIV for possible adjustment to time base.
      
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      cb93071b
  2. 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
  3. Jul 23, 2013
  4. Jul 16, 2013
  5. Jul 01, 2013
  6. Jun 30, 2013
    • Heiko Schocher's avatar
      dfu: make data buffer size configurable · e7e75c70
      Heiko Schocher authored
      
      Dfu transfer uses a buffer before writing data to the
      raw storage device. Make the size (in bytes) of this buffer
      configurable through environment variable "dfu_bufsiz".
      Defaut value is configurable through CONFIG_SYS_DFU_DATA_BUF_SIZE
      
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
      Cc: Tom Rini <trini@ti.com>
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
      Acked-by: default avatarTom Rini <trini@ti.com>
      e7e75c70
  7. Jun 26, 2013
  8. Jun 23, 2013
  9. Jun 20, 2013
  10. Jun 13, 2013
  11. Jun 12, 2013
  12. Jun 07, 2013
    • Gabor Juhos's avatar
      pci: introduce CONFIG_PCI_INDIRECT_BRIDGE option · 842033e6
      Gabor Juhos authored
      
      The pci_indirect.c file is always compiled when
      CONFIG_PCI is defined although the indirect PCI
      bridge support is not needed by every board.
      
      Introduce a new CONFIG_PCI_INDIRECT_BRIDGE
      config option and only compile indirect PCI
      bridge support if this options is enabled.
      
      Also add the new option into the configuration
      files of the boards which needs that.
      
      Compile tested for powerpc, x86, arm and nds32.
      MAKEALL results:
      
      powerpc:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 641
        Boards with warnings but no errors: 2 ( ELPPC MPC8323ERDB )
        ----------------------------------------------------------
        Note: the warnings for ELPPC and MPC8323ERDB are present even
        without the actual patch.
      
      x86:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 1
        ----------------------------------------------------------
      
      arm:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 311
        ----------------------------------------------------------
      
      nds32:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 3
        ----------------------------------------------------------
      
      Cc: Tom Rini <trini@ti.com>
      Cc: Daniel Schwierzeck <daniel.schwierzeck@googlemail.com>
      Signed-off-by: default avatarGabor Juhos <juhosg@openwrt.org>
      842033e6
    • Peter Korsgaard's avatar
      spl_mmc: add Falcon mode support for raw variant · 2b75b0ad
      Peter Korsgaard authored
      
      If Falcon mode support is enabled (and the system isn't directed into
      booting u-boot), it will instead try to load kernel from sector
      CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR and
      CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS of kernel argument parameters
      starting from sector CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR.
      
      Signed-off-by: default avatarPeter Korsgaard <peter.korsgaard@barco.com>
      2b75b0ad
    • Peter Korsgaard's avatar
      spl_mmc: add Falcon mode support for FAT variant · 7ad2cc79
      Peter Korsgaard authored
      
      If Falcon mode support is enabled (and the system isn't directed into
      booting u-boot), it will instead try to load kernel from
      CONFIG_SPL_FAT_LOAD_KERNEL_NAME file and kernel argument parameters from
      CONFIG_SPL_FAT_LOAD_ARGS_NAME, both from the same partition as u-boot.
      
      Signed-off-by: default avatarPeter Korsgaard <peter.korsgaard@barco.com>
      7ad2cc79
  13. Jun 03, 2013
  14. May 16, 2013
  15. May 15, 2013
  16. May 14, 2013
  17. May 13, 2013
  18. May 10, 2013
    • Lokesh Vutla's avatar
      ARM: OMAP5: Fix warm reset with USB cable connected · 0b1b60c7
      Lokesh Vutla authored
      
      Warm reset on OMAP5 freezes when USB cable is connected.
      Fix requires PRM_RSTTIME.RSTTIME1 to be programmed
      with the time for which reset should be held low for the
      voltages and the oscillator to reach stable state.
      
      There are 3 parameters to be considered for calculating
      the time, which are mostly board and PMIC dependent.
      -1- Time taken by the Oscillator to shut + restart
      -2- PMIC OTP times
      -3- Voltage rail ramp times, which inturn depends on the
      PMIC slew rate and value of the voltage ramp needed.
      
      In order to keep the code in u-boot simple, have a way
      for boards to specify a pre computed time directly using
      the 'CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC'
      option. If boards fail to specify the time, use a default
      as specified by 'CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC' instead.
      Using the default value translates into some ~22ms and should work in
      all cases.
      However in order to avoid this large delay hiding other bugs,
      its recommended that all boards look at their respective data
      sheets and specify a pre computed and optimal value using
      'CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC'
      
      In order to help future board additions to compute this
      config option value, add a README at doc/README.omap-reset-time
      which explains how to compute the value. Also update the toplevel
      README with the additional option and pointers to
      doc/README.omap-reset-time.
      
      Signed-off-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
      [rnayak@ti.com: Updated changelog and added the README]
      Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
      0b1b60c7
  19. May 01, 2013
    • Wolfgang Denk's avatar
      Add SLRE - Super Light Regular Expression library · a5ecbe62
      Wolfgang Denk authored
      Downloaded from http://slre.sourceforge.net/
      and adapted for U-Boot environment.
      
      Used to implement regex operations on environment variables.
      Code size is ~ 3.5 KiB on PPC.
      
      To enable this code, define the  CONFIG_REGEX  option in your board
      config file.
      
      Note:  There are more recent versions of the SLRE library available at
      http://slre.googlecode.com
      
       ; unfortunately, the new code has a heavily
      reorked API which makes it less usable for our purposes:
      - the return code is strings, which are more difficult to process
      - we don't get any information any more which sub-string of the data
        was matched by the given regex
      - it is much more cumbersome to work with arbitrary expressions, where
        for example the number of substrings for capturing are not known at
        compile time
      Also, there does not seem to be any real changes or improvements of
      the functionality.
      
      Because of this, we deliberately stick with the older code.
      
      Note 2: the test code (built when SLRE_TEST is defined) was modified
      to allow for more extensive testing; now we can test the regexp
      matching on all lines on a text file (instead of the whole data in the
      file as a single block).
      
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      a5ecbe62
  20. Apr 28, 2013
  21. Apr 22, 2013
    • Stefan Roese's avatar
      flash: Add optional verify-after-write feature · 352ef3f1
      Stefan Roese authored
      
      Sometimes it might make sense to verify the written data to NOR flash.
      This patch adds this feature. To enable this verify-after-write, you
      need to define CONFIG_FLASH_VERIFY in your board config header.
      
      Please note that this option is useless in nearly all cases,
      since such flash programming errors usually are detected earlier
      while unprotecting/erasing/programming. Please only enable
      this option if you really know what you are doing.
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      352ef3f1
  22. Apr 14, 2013
Loading