Skip to content
Snippets Groups Projects
  1. Apr 13, 2010
  2. Apr 09, 2010
    • Peter Tyser's avatar
      mkimage: Fix strict-aliasing compiler warning · a2513e27
      Peter Tyser authored
      
      Version 4.2.4 of gcc produces the following warnings without this change:
        mkimage.c: In function ‘main’:
        mkimage.c:204: warning: dereferencing type-punned pointer will break strict-aliasing rules
        mkimage.c:222: warning: dereferencing type-punned pointer will break strict-aliasing rules
      
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      a2513e27
  3. Mar 27, 2010
  4. Mar 11, 2010
    • Mike Frysinger's avatar
      mkimage: dont force entry point with xip · 1b691bb0
      Mike Frysinger authored
      
      Some people boot images with the entry point in the middle of the blob
      (like Linux with the head code in discardable .init.text), and there is no
      no real requirement that the entry point be right after the mkimage header
      when doing XIP, so let people specify whatever they want.  If they do need
      an entry right after the header, then they still can do that with normal
      -e behavior.
      
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      1b691bb0
  5. Feb 23, 2010
  6. Feb 12, 2010
  7. Jan 27, 2010
  8. Jan 25, 2010
  9. Jan 21, 2010
  10. Jan 17, 2010
  11. Dec 07, 2009
  12. Dec 05, 2009
    • Peter Tyser's avatar
      tools/mkimage: Print FIT image contents after creation · c81296c1
      Peter Tyser authored
      
      Previously, there was no indication to the user that a FIT image was
      successfully created after executing mkimage.  For example:
      
        $ mkimage -f uImage.its uImage.itb
        DTC: dts->dtb  on file "uImage.its"
      
      Adding some additional output after creating a FIT image lets the user
      know exactly what is contained in their image, eg:
      
        $ mkimage -f uImage.its uImage.itb
        DTC: dts->dtb  on file "uImage.its"
        FIT description: Linux kernel 2.6.32-rc7-00201-g7550d6f-dirty
        Created:         Tue Nov 24 15:43:01 2009
         Image 0 (kernel@1)
          Description:  Linux Kernel 2.6.32-rc7-00201-g7550d6f-dirty
          Type:         Kernel Image
          Compression:  gzip compressed
          Data Size:    2707311 Bytes = 2643.86 kB = 2.58 MB
          Architecture: PowerPC
          OS:           Linux
          Load Address: 0x00000000
          Entry Point:  0x00000000
          Hash algo:    crc32
          Hash value:   efe0798b
          Hash algo:    sha1
          Hash value:   ecafba8c95684f2c8fec67e33c41ec88df1534d7
         Image 1 (fdt@1)
          Description:  Flattened Device Tree blob
          Type:         Flat Device Tree
          Compression:  uncompressed
          Data Size:    12288 Bytes = 12.00 kB = 0.01 MB
          Architecture: PowerPC
          Hash algo:    crc32
          Hash value:   a5cab676
          Hash algo:    sha1
          Hash value:   168722b13e305283cfd6603dfe8248cc329adea6
         Default Configuration: 'config@1'
         Configuration 0 (config@1)
          Description:  Default Linux kernel
          Kernel:       kernel@1
          FDT:          fdt@1
      
      This brings the behavior of creating a FIT image in line with creating a
      standard uImage, which also prints out the uImage contents after
      creation.
      
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      c81296c1
    • Peter Tyser's avatar
      tools/fit_image.c: Remove unused fit_set_header() · 8e1c8966
      Peter Tyser authored
      
      The FIT fit_set_header() function was copied from the standard uImage's
      image_set_header() function during mkimage reorganization.  However, the
      fit_set_header() function is not used since FIT images use a standard
      device tree blob header.
      
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      8e1c8966
    • Peter Tyser's avatar
      tools/mkimage: Assume FDT image type for FIT images · 1a99de2c
      Peter Tyser authored
      
      When building a Flattened Image Tree (FIT) the image type needs to be
      "flat_dt".  Commit 89a4d6b1 introduced a
      regression which caused the user to need to specify the "-T flat_dt"
      parameter on the command line when building a FIT image.  The "-T
      flat_dt" parameter should not be needed and is at odds with the current
      FIT image documentation.
      
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      1a99de2c
  13. Dec 02, 2009
    • Scott Wood's avatar
      makefiles: fixes for building build tools · d984fed0
      Scott Wood authored
      
      Currently, some of the tools instead set CC to be HOSTCC in order to re-use
      some pattern rules -- but this fails when the user overrides CC on the make
      command line.  Also, the HOSTCFLAGS in tools/Makefile are currently not
      being used because config.mk overwrites them.
      
      This patch adds static pattern rules for files that have been requested to
      be built with the native compiler using $(HOSTSRCS) and $(HOSTOBJS), and
      converts the tools to use them.
      
      It restores easylogo to using the host compiler, which was broken by commit
      38d299c2 (if this was an intentional change,
      please let me know -- but it seems to be a build tool).
      
      It restores -pedantic and the special flags for darwin and cygwin that were
      requested in tools/makefile (but keeps the flags added by config.mk) --
      hopefully someone can test this on those platforms.  It no longer
      conditionalizes -pedantic on not being darwin; it wasn't clear that that was
      intentional, and unless there's a real problem it's just inviting people to
      contribute non-pedantic patches to those files (I'm not a fan of -pedantic
      personally, but if it's on for one platform it should be on for all).
      
      HOST_LDFLAGS is renamed HOSTLDFLAGS for consistency with the previous
      HOST_CFLAGS to HOSTCFLAGS rename.  A new HOSTCFLAGS_NOPED is made available
      for those files which currently cannot be built with -pedantic, and replaces
      the old FIT_CFLAGS.
      
      imls now uses the cross compiler properly, rather than by trying to
      reconstruct CC using the typoed $(CROSS_COMPILER).
      
      envcrc.c is now dependency-processed unconditionally -- previously it would
      be built without being on (HOST)SRCS if CONFIG_ENV_IS_EMBEDDED was not
      selected.
      
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      d984fed0
  14. Nov 24, 2009
  15. Nov 23, 2009
  16. Oct 27, 2009
  17. Oct 19, 2009
  18. Oct 18, 2009
    • Mike Frysinger's avatar
      env: only build env_embedded and envcrc when needed · 6dab6add
      Mike Frysinger authored
      
      The env code is protected by the ENV_IS_EMBEDDED define, so attempting to
      compile the code when this isn't defined is pointless.  Now that the env
      headers have unified around CONFIG_ENV_IS_EMBEDDED, convert the build
      system to only build the env objects when this is enabled.  And now that
      the env code is conditionally compiled, we can drop the source code checks.
      
      For people who want to extract the environment manually, add a new option
      CONFIG_BUILD_ENVCRC that only enables the envcrc utility.
      
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      6dab6add
  19. Sep 15, 2009
  20. Sep 11, 2009
  21. Sep 10, 2009
  22. Sep 04, 2009
  23. Jul 23, 2009
Loading