Le support aux utilisateurs et les demandes de création de comptes externes doivent être faites depuis les issues du projet GitLab HEFR (https://gitlab.forge.hefr.ch/forge-hefr/gitlab-hefr)

  1. 20 Sep, 2013 2 commits
  2. 12 Sep, 2013 1 commit
  3. 03 Sep, 2013 1 commit
  4. 20 Aug, 2013 3 commits
  5. 16 Aug, 2013 1 commit
    • Simon Glass's avatar
      RFC: bootm: Add silent_linux environment variable · 8d51aacd
      Simon Glass authored
      
      
      At present the console for linux is silent if the U-Boot console is silent,
      unless CONFIG_SILENT_U_BOOT_ONLY is set. I wonder if a better way would be
      to have an environment variable to control this? Then we can control the
      verbosity from scripts, and set the variable to 'no' for those boards that
      want Linux to boot with console output.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      8d51aacd
  6. 09 Aug, 2013 2 commits
  7. 27 Jul, 2013 1 commit
  8. 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
      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
  9. 23 Jul, 2013 6 commits
  10. 16 Jul, 2013 2 commits
  11. 01 Jul, 2013 1 commit
  12. 30 Jun, 2013 1 commit
    • 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
  13. 26 Jun, 2013 4 commits
  14. 23 Jun, 2013 1 commit
  15. 20 Jun, 2013 5 commits
  16. 13 Jun, 2013 2 commits
  17. 12 Jun, 2013 1 commit
  18. 07 Jun, 2013 3 commits
    • 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
  19. 03 Jun, 2013 2 commits