1. 12 Mar, 2014 2 commits
    • Masahiro Yamada's avatar
      kbuild: rename SRCTREE to srctree · 01286329
      Masahiro Yamada authored
      Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
      pointing to the top of source directory.
      (No difference between the two.)
      
      In Kbuild style, $(srctree) is used for instead.
      This commit renames SRCTREE to srctree and deletes the
      defition of SRCTREE.
      
      Note that SRCTREE in scripts/kernel-doc, scripts/docproc.c,
      doc/DocBook/Makefile should be keep.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      01286329
    • Masahiro Yamada's avatar
      kbuild: rename TOPDIR to stctree · 4379ac61
      Masahiro Yamada authored
      Prior to Kbuild, $(TOPDIR) or $(SRCTREE) was used for
      pointing to the top of source directory.
      (No difference between the two.)
      
      In Kbuild style, $(srctree) is used instead.
      This commit renames TOPDIR to srctree and delete the
      defition of TOPDIR.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      4379ac61
  2. 07 Mar, 2014 1 commit
    • Masahiro Yamada's avatar
      kbuild: improve Kbuild speed · 026f9cf2
      Masahiro Yamada authored
      Kbuild brought about many advantages for us but a significant
      performance regression was reported by Simon Glass.
      
      After some discussions and analysis, it turned out
      its main cause is in $(call cc-option,...).
      
      Historically, U-Boot parses all config.mk
      (arch/*/config.mk and board/*/config.mk)
      every time descending into subdirectories.
      That means cc-options are evaluated over and over again.
      
      $(call cc-option,...) is useful but costly.
      So we want to evaluate them only in ./Makefile
      and spl/Makefile and export compiler flags.
      
      This commit changes the build system as follows:
      
        - Modify scripts/Makefile.build to not include config.mk
          Instead, add $(PLATFORM_CPPFLAGS) to asflags-y, ccflags-y,
          cppflags-y.
      
        - Export many variables
          Going forward, Kbuild will not parse config.mk files
          when it descends into subdirectories.
          If we want to set variables in config.mk and use them
          in subdirectories, they must be exported.
      
          This is the list of variables to get exported:
            PLATFORM_CPPFLAGS
            CPUDIR
            BOARDDIR
            OBJCOPYFLAGS
            LDFLAGS
            LDFLAGS_FINAL
              (used in nand_spl/board/*/*/Makefile)
            CONFIG_STANDALONE_LOAD_ADDR
              (used in examples/standalone/Makefile)
            SYM_PREFIX
              (used in examples/standalone/Makefile)
            RELFLAGS
              (used in examples/standalone/Makefile)
      
        - Delete CPPFLAGS
          This variable has been replaced with PLATFORM_CPPFLAGS
      
        - Copy gcclibdir from example/standalone/Makefile
          to arch/sparc/config.mk
          The reference in CONFIG_STANDALONE_LOAD_ADDR must be
          resolved before it is exported.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Reported-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Tested-by: Simon Glass <sjg@chromium.org> [on Sandbox]
      Tested-by: Stephen Warren <swarren@nvidia.com> [on Tegra]
      026f9cf2
  3. 04 Mar, 2014 2 commits
  4. 25 Feb, 2014 1 commit
  5. 19 Feb, 2014 13 commits
    • Masahiro Yamada's avatar
      kbuild: move include directives of board configuration files · 01072b44
      Masahiro Yamada authored
      This commit changes the location of include directives
      of board configuration files.
      
      The purpose of this change is:
       - Slim down $(TOPDIR)/config.mk
       - Prevent $(TOPDIR)/Makefile from including the same
          configuration file twice
       - Do not include include/config.mk multiple times
          because ARCH, CPU, BOARD, VENDOR, SOC are exported
      
      Before this commit:
      
       - include/autoconf.mk was included from $(TOPDIR)/Makefile
         and $(TOPDIR)/config.mk
         (This means $(TOPDIR)/Makefile included include/autoconf.mk twice)
      
       - include/{spl,tpl}-autoconf.mk was included from $(TOPDIR)/config.mk
      
       - include/config.mk was included from $(TOPDIR)/Makefile
         and $(TOPDIR)/config.mk
         (This means $(TOPDIR)/Makefile included include/config.mk twice)
      
      After this commit:
      
       - include/autoconf.mk is included from $(TOPDIR)/Makefile
         and $(TOPDIR)/scripts/Makefile.build
      
       - include/{spl,tpl}-autoconf.mk is included from $(TOPDIR)/spl/Makefile
         and $(TOPDIR)/scripts/Makefile.build
      
       - include/config.mk is included from $(TOPDIR)/config.mk and
         $(TOPDIR)/spl/Makefile
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      01072b44
    • Masahiro Yamada's avatar
      kbuild: use Linux Kernel build scripts · 6825a95b
      Masahiro Yamada authored
      Now we are ready to switch over to real Kbuild.
      
      This commit disables temporary scripts:
        scripts/{Makefile.build.tmp, Makefile.host.tmp}
      and enables real Kbuild scripts:
        scripts/{Makefile.build,Makefile.host,Makefile.lib}.
      
      This switch is triggered by the line in scripts/Kbuild.include
        -build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build.tmp obj
        +build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build obj
      
      We need to adjust some build scripts for U-Boot.
      But smaller amount of modification is preferable.
      
      Additionally, we need to fix compiler flags which are
      locally added or removed.
      
      In Kbuild, it is not allowed to change CFLAGS locally.
      Instead, ccflags-y, asflags-y, cppflags-y,
      CFLAGS_$(basetarget).o, CFLAGS_REMOVE_$(basetarget).o
      are prepared for that purpose.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
      6825a95b
    • Masahiro Yamada's avatar
      kbuild: change out-of-tree build · 9e414032
      Masahiro Yamada authored
      This commit changes the working directory
      where the build process occurs.
      
      Before this commit, build process occurred under the source
      tree for both in-tree and out-of-tree build.
      
      That's why we needed to add $(obj) prefix to all generated
      files in makefiles like follows:
        $(obj)u-boot.bin:  $(obj)u-boot
      
      Here, $(obj) is empty for in-tree build, whereas it points
      to the output directory for out-of-tree build.
      
      And our old build system changes the current working directory
      with "make -C <sub-dir>" syntax when descending into the
      sub-directories.
      
      On the other hand, Kbuild uses a different idea
      to handle out-of-tree build and directory descending.
      
      The build process of Kbuild always occurs under the output tree.
      When "O=dir/to/store/output/files" is given, the build system
      changes the current working directory to that directory and
      restarts the make.
      
      Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>"
      syntax for descending into sub-directories.
      (We can write it like "make $(obj)=<sub-dir>" with a shorthand.)
      This means the current working directory is always the top
      of the output directory.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
      9e414032
    • Masahiro Yamada's avatar
      Makefile: move some flags to examples makefiles · d9580025
      Masahiro Yamada authored
      This commit moves some flags which are used
      under examples/ directory only.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      d9580025
    • Masahiro Yamada's avatar
      Makefile: move some flags to spl/Makefile · e0d5d9f8
      Masahiro Yamada authored
      Some flags are used for SPL (and TPL) build only.
      This commit moves them from config.mk to spl/Makefile.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      e0d5d9f8
    • Masahiro Yamada's avatar
      ced0715d
    • Masahiro Yamada's avatar
      Makefile: refactor include path settings · fea1ca8e
      Masahiro Yamada authored
      This commit merges commonly-used header include paths
      to UBOOTINCLUDE and NOSTDINC_FLAGS variables, which are placed
      at the top Makefile.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      fea1ca8e
    • Masahiro Yamada's avatar
      Makefile: move more flags to the top Makefile · 2b3c9d3d
      Masahiro Yamada authored
      Before this commit, most of compiler flags were defined in config.mk.
      But it is redundant because config.mk is included from all recursive make.
      
      This commit moves many complier flags to the top Makefile
      and export them.
      And we use new vaiarables to store them:
      KBUILD_CPPFLAGS, KBUILD_CFLAGS, KBUILD_AFLAGS.
      This will allow us to switch more smoothly to Kbuild.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      2b3c9d3d
    • Masahiro Yamada's avatar
      kbuild: Use Kbuild.include · bf4b3de1
      Masahiro Yamada authored
      This commit adjusts some files to use Kbuild.include.
      
       - Use cc-option defined in Kbuild.include
          (Delete cc-option in config.mk)
       - Use cc-version defined in
          (Delete cc-version in config.mk)
       - Move binutils-version and dtc-version to Kbuild.include
           by analogy to cc-version
      
      This commit also adds srctree (same as SRCTREE)
      to use Kbuild scripts.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      bf4b3de1
    • Masahiro Yamada's avatar
      Makefile: move BFD_ROOT_DIR to tools/gdb/Makefile · 34bd0507
      Masahiro Yamada authored
      BFD_ROOT_DIR is used only in tools/gdb/Makefile
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      34bd0507
    • Masahiro Yamada's avatar
      Makefile: move some variable definitions to the top Makefile · f6322eb7
      Masahiro Yamada authored
      This commit moves some variable definitions from config.mk
      to the top Makefile:
      
        - HOSTCC, HOSTCFLAGS, HOSTLDFLAGS
        - AS, LD, CC, CPP, etc.
        - SHELL (renamed to CONFIG_SHELL)
      
      I'd like to slim down config.mk file
      because it is included from all recursive make.
      It is redundant to re-define the variables
      every time descending into sub directories.
      We should rather define them at the top Makefile
      and export them.
      
      U-Boot makefiles has been used "SHELL" variable to store shell
      chosen for the user, whereas Linux Kernel uses "CONFIG_SHELL".
      
      We should never use "SHELL" variable because it is
      a special variable for GNU Make.
      Changing SHELL may cause unpredictable side effects
      whose root cause is usually difficult to find.
      We should use a generic variable name "CONFIG_SHELL".
      
      We should not use the syntax as follows either:
      
          rm -f $(obj)tools/env/{fw_printenv,fw_setenv}
      
      This depends on "bash" although GNU Make generally
      invokes "sh" to run the each rule.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      f6322eb7
    • Masahiro Yamada's avatar
      Makfile: move suffix rules to Makefile.build · 5651ccff
      Masahiro Yamada authored
      This commit moves suffix rules from config.mk
      to scripts/Makefile.build, which will allow us
      to switch smoothly to real Kbuild.
      
      Note1:
      post/lib_powerpc/fpu/Makefile has
      its own rule to compile C sources.
      We need to tweak it to keep the same behavior.
      
      Note2:
      There are two file2 with the same name:
      arch/arm/lib/crt0.S and eamples/api/crt0.S.
      To keep the same build behavior,
      examples/api/Makefile also has to be treaked.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      5651ccff
    • Masahiro Yamada's avatar
      tools: convert makefiles to kbuild style · 940db16d
      Masahiro Yamada authored
      Before this commit, makefiles under tools/ directory
      were implemented with their own way.
      
      This commit refactors them by using "hostprogs-y" variable.
      
      Several C sources have been added to wrap other C sources
      to simplify Makefile.
      For example, tools/crc32.c includes lib/crc32.c
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      940db16d
  6. 29 Jan, 2014 1 commit
  7. 13 Dec, 2013 1 commit
    • Masahiro Yamada's avatar
      Makefile: Move some scripts imported from Linux · dd88ab32
      Masahiro Yamada authored
      We have some scripts imported from Linux Kernel:
      setlocalversion, checkstack.pl, checkpatch.pl, cleanpatch
      
      They are located under tools/ directory in U-Boot now.
      But they were originally located under scripts/ directory
      in Linux Kernel.
      
      This commit moves them to the original location.
      
      It is true that binutils-version.sh and dtc-version.sh
      do not originate in Linux Kernel, but they should
      be moved by analogy to gcc-version.sh.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      dd88ab32
  8. 21 Nov, 2013 1 commit
    • Simon Glass's avatar
      sandbox: Use system headers first for sandbox's os.c · cbe5cdfc
      Simon Glass authored
      This file must be compiled with system headers, even if U-Boot has headers
      of the same name. The existing solution for this is good enough for libfdt,
      but fails when we have headers like stdint.h in U-Boot.
      
      Use -idirafter instead of -I, and remove the -nostdinc and other things
      that we don't want for this file. The best way to do this is to keep a
      copy of the original flags, rather than trying to filter them later.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      cbe5cdfc
  9. 17 Nov, 2013 1 commit
  10. 08 Nov, 2013 1 commit
  11. 14 Oct, 2013 1 commit
  12. 06 Sep, 2013 2 commits
    • Masahiro Yamada's avatar
      cam_enc_4xx: Move CONFIG_SPL_PAD_TO to a config header · 1affd4d4
      Masahiro Yamada authored
      For most boards which define CONFIG_SPL_PAD_TO,
      it is defined in config header files.
      Currently, there exists only one exception, cam_enc_4xx board.
      
      This patch moves CONFIG_SPL_PAD_TO definition
      from board/ait/cam_enc_4xx/config.mk
      to include/configs/cam_enc_4xx.h.
      
      With this modification, we can delete a glue code
      in the top level config.mk:
      
      ifneq ($(CONFIG_SPL_PAD_TO),)
      CPPFLAGS += -DCONFIG_SPL_PAD_TO=$(CONFIG_SPL_PAD_TO)
      endif
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Heiko Schocher <hs@denx.de>
      1affd4d4
    • Masahiro Yamada's avatar
      config.mk: Delete unnecessary code · cb4ef5ba
      Masahiro Yamada authored
      Currently no makefiles (board-specific config.mk)
      set the following variables:
      
      CONFIG_SPL_TEXT_BASE
      CONFIG_UBOOT_PAD_TO
      CONFIG_RESET_VECTOR_ADDRESS
      CONFIG_TPL_PAD_TO
      
      For all target boards using above macros
      they are set in header files (include/configs/*.h),
      so we do not need to set them as CPPFLAGS.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      cb4ef5ba
  13. 31 Aug, 2013 1 commit
    • Marek Vasut's avatar
      ARM: mxs: tools: Add mkimage support for MXS bootstream · bce88370
      Marek Vasut authored
      Add mkimage support for generating and verifying MXS bootstream.
      The implementation here is mostly a glue code between MXSSB v0.4
      and mkimage, but the long-term goal is to rectify this and merge
      MXSSB with mkimage more tightly. Once this code is properly in
      U-Boot, MXSSB shall be deprecated in favor of mkimage-mxsimage
      support.
      
      Note that the mxsimage generator needs libcrypto from OpenSSL, I
      therefore enabled the libcrypto/libssl unconditionally.
      
      MXSSB: http://git.denx.de/?p=mxssb.git;a=summary
      
      The code is based on research presented at:
      http://www.rockbox.org/wiki/SbFileFormatSigned-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Tom Rini <trini@ti.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Otavio Salvador <otavio@ossystems.com.br>
      bce88370
  14. 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
      operations.
      
      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>
      3aa29de0
  15. 19 Aug, 2013 1 commit
    • 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>
      39bc12dd
  16. 02 Aug, 2013 1 commit
  17. 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
  18. 19 Jul, 2013 1 commit
  19. 28 Jun, 2013 1 commit
    • Simon Glass's avatar
      mkimage: Build signing only if board has CONFIG_FIT_SIGNATURE · 29ce737d
      Simon Glass authored
      At present mkimage is set up to always build with image signing support.
      This means that the SSL libraries (e.g. libssl-dev) are always required.
      
      Adjust things so that mkimage can be built with and without image signing,
      controlled by the presence of CONFIG_FIT_SIGNATURE in the board config file.
      
      If CONFIG_FIT_SIGNATURE is not enabled, then mkimage will report a warning
      that signing is not supported. If the option is enabled, but libraries are
      not available, then a build error similar to this will be shown:
      
      lib/rsa/rsa-sign.c:26:25: fatal error: openssl/rsa.h: No such file or directory
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      29ce737d
  20. 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>
      19c402af
    • Simon Glass's avatar
      Support tracing in config.mk when enabled · 5c2aeac5
      Simon Glass authored
      Use -finstrument-functions when tracing is enabled (make FTRACE=1).
      Tracing is not currently supported by SPL even if sufficient memory is
      available.
      
      When tracing is enabled, we #define FTRACE. This can be used by
      board config files to conditionally enable the tracing options.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      5c2aeac5
  21. 09 May, 2013 1 commit
  22. 01 May, 2013 1 commit
    • 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
  23. 22 Apr, 2013 1 commit
    • 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
  24. 12 Apr, 2013 1 commit
    • Benoît Thébaudeau's avatar
      Makefile: Move SHELL setup to config.mk · 120ae609
      Benoît Thébaudeau authored
      make never uses the SHELL variable from the environment. Instead, it
      uses /bin/sh, or the value assigned to the SHELL variable by the Makefile. This
      makes the export of the SHELL variable useless for sub-makes (but still useful
      for the environment of recipes). However, we want all makes to use the same
      shell.
      
      This patch fixes this issue by moving the SHELL variable setup and export to the
      top config.mk, so that all Makefile-s including it use the same shell.
      
      Since BASH is used by default, this makes it possible to use things
      like 'echo -e ...' in sub-makes, which would otherwise fail e.g. with /bin/sh
      symlinked to /bin/dash on Ubuntu.
      Signed-off-by: default avatarBenoît Thébaudeau <benoit.thebaudeau@advansee.com>
      Reviewed-by: default avatarTom Rini <trini@ti.com>
      120ae609