Skip to content
Snippets Groups Projects
  1. Nov 27, 2010
  2. Nov 14, 2010
  3. Oct 27, 2010
    • Wolfgang Denk's avatar
      make-asm-offsets: fix sed script · e4691f5e
      Wolfgang Denk authored
      
      When copying the "sed" script to generate the asm-offsets.h file from
      the Linux Kbuild script into the make-asm-offsets file I missed the
      fact that the former runs in a "make" context and thus uses double
      "$$" to escape a single "$", while the latter is a shell script, where
      this must not be done.  Unfortunately the problem did not show up
      during the initial tests on Power Architecture systems, but on ARM the
      generated asm-offsets.h was not correct.
      
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Tested-by: default avatarHeiko Schocher <hs@denx.de>
      Tested-by: default avatarBen Gardiner <bengardiner@nanometrics.ca>
      e4691f5e
  4. Oct 26, 2010
    • Wolfgang Denk's avatar
      include/asm-offsets.h: automatically generate assembler constants · 16a354f9
      Wolfgang Denk authored
      
      A recurrent issue is that certain C level constructs like sizeof() or
      offsetof() cannot be used in assembler files, which is inconvenient
      when such constructs are used in the definition of macro names etc.
      
      To avoid duplication of such definitions (and thus another cause of
      problems), we adapt the Linux way to automatically generate the
      respective definitions from the respective C header files.
      
      In Linux, this is implemented in include/linux/kbuild.h, Kbuild, and
      arch/*/kernel/asm-offsets.c; we adapt the code from the Linux v2.6.36
      kernel tree.
      
      We also copy the concept of the include/generated/ directory which can
      be used to hold other automatically generated files as well.
      
      We start with an architecture-independent lib/asm-offsets.c which
      generates include/generated/generic-asm-offsets.h (included by
      include/asm-offsets.h, which is what will be referred to in the actual
      source code).  Later this may be extended by architecture-specific
      arch/*/lib/asm-offsets.c files that will generate a
      include/generated/asm-offsets.h.
      
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Acked-by: default avatarKumar Gala <galak@kernel.crashing.org>
      16a354f9
  5. Oct 18, 2010
  6. Oct 12, 2010
  7. Sep 21, 2010
  8. Sep 19, 2010
  9. Sep 18, 2010
  10. Aug 10, 2010
  11. Aug 08, 2010
  12. Jul 25, 2010
  13. Jul 24, 2010
  14. Jun 29, 2010
  15. Apr 30, 2010
  16. Apr 24, 2010
  17. Apr 13, 2010
  18. 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
  19. Mar 27, 2010
  20. 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
  21. Feb 23, 2010
  22. Feb 12, 2010
  23. Jan 31, 2010
  24. Jan 27, 2010
  25. Jan 25, 2010
  26. Jan 21, 2010
  27. Jan 17, 2010
  28. Dec 07, 2009
  29. 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
Loading