1. 21 Mar, 2014 1 commit
  2. 24 Jul, 2013 1 commit
  3. 14 May, 2013 1 commit
    • Simon Glass's avatar
      image: Add device tree setup to image library · 13d06981
      Simon Glass authored
      This seems to be a common function for several architectures, so create
      a common function rather than duplicating the code in each arch.
      
      Also make an attempt to avoid introducing #ifdefs in the new code, partly
      by removing useless #ifdefs around function declarations in the image.h
      header.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      13d06981
  4. 09 Feb, 2013 1 commit
  5. 08 Feb, 2013 2 commits
    • Kim Phillips's avatar
      common/fdt_support.c: sparse fixes · 8aa5ec6e
      Kim Phillips authored
      trivial:
      
      fdt_support.c:89:64: warning: Using plain integer as NULL pointer
      fdt_support.c:325:65: warning: Using plain integer as NULL pointer
      fdt_support.c:352:65: warning: Using plain integer as NULL pointer
      
      For the following bad constant expression, We hardcode the max. number of
      memory banks to four for the foreseeable future, and add an error with
      instructions on what to do once it's exceeded:
      
      fdt_support.c:397:22: error: bad constant expression
      
      For the rest below, sparse found a couple of wrong endian conversions
      in of_bus_default_translate() and fdt_get_base_address(), but
      otherwise the rest is mostly annotation fixes:
      
      fdt_support.c:64:24: warning: cast to restricted __be32
      fdt_support.c:192:21: warning: incorrect type in assignment (different base types)
      fdt_support.c:192:21:    expected unsigned int [unsigned] [usertype] tmp
      fdt_support.c:192:21:    got restricted __be32 [usertype] <noident>
      fdt_support.c:201:21: warning: incorrect type in assignment (different base types)
      fdt_support.c:201:21:    expected unsigned int [unsigned] [addressable] [usertype] tmp
      fdt_support.c:201:21:    got restricted __be32 [usertype] <noident>
      fdt_support.c:304:13: warning: incorrect type in assignment (different base types)
      fdt_support.c:304:13:    expected unsigned int [unsigned] [usertype] val
      fdt_support.c:304:13:    got restricted __be32 [usertype] <noident>
      fdt_support.c:333:13: warning: incorrect type in assignment (different base types)
      fdt_support.c:333:13:    expected unsigned int [unsigned] [usertype] val
      fdt_support.c:333:13:    got restricted __be32 [usertype] <noident>
      fdt_support.c:359:13: warning: incorrect type in assignment (different base types)
      fdt_support.c:359:13:    expected unsigned int [unsigned] [usertype] val
      fdt_support.c:359:13:    got restricted __be32 [usertype] <noident>
      fdt_support.c:373:21: warning: cast to restricted __be32
      fdt_support.c:963:48: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:963:48:    expected restricted __be32 const [usertype] *p
      fdt_support.c:963:48:    got unsigned int [usertype] *<noident>
      fdt_support.c:971:48: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:971:48:    expected restricted __be32 const [usertype] *p
      fdt_support.c:971:48:    got unsigned int [usertype] *<noident>
      fdt_support.c:984:29: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:984:29:    expected restricted __be32 const [usertype] *cell
      fdt_support.c:984:29:    got unsigned int [usertype] *addr
      fdt_support.c:996:32: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:996:32:    expected restricted __be32 const [usertype] *cell
      fdt_support.c:996:32:    got unsigned int [usertype] *addr
      fdt_support.c:1041:41: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:1041:41:    expected restricted __be32 const [usertype] *cell
      fdt_support.c:1041:41:    got unsigned int [usertype] *addr
      fdt_support.c:1053:41: warning: incorrect type in argument 2 (different base types)
      fdt_support.c:1053:41:    expected restricted __be32 const [usertype] *range
      fdt_support.c:1053:41:    got unsigned int const [usertype] *[assigned] ranges
      fdt_support.c:1064:53: warning: incorrect type in argument 2 (different base types)
      fdt_support.c:1064:53:    expected restricted __be32 const [usertype] *addr
      fdt_support.c:1064:53:    got unsigned int [usertype] *addr
      fdt_support.c:1110:50: warning: incorrect type in argument 2 (different base types)
      fdt_support.c:1110:50:    expected restricted __be32 const [usertype] *addr
      fdt_support.c:1110:50:    got unsigned int *<noident>
      fdt_support.c:1121:49: warning: incorrect type in argument 1 (different base types)
      fdt_support.c:1121:49:    expected restricted __be32 const [usertype] *cell
      fdt_support.c:1121:49:    got unsigned int *<noident>
      fdt_support.c:1147:60: warning: incorrect type in argument 2 (different base types)
      fdt_support.c:1147:60:    expected restricted __be32 const [usertype] *addr
      fdt_support.c:1147:60:    got unsigned int *<noident>
      fdt_support.c:1081:5: warning: symbol '__of_translate_address' was not declared. Should it be static?
      fdt_support.c:1154:5: error: symbol 'fdt_translate_address' redeclared with different type (originally declared at include/fdt_support.h:95) - incompatible argument 3 (different base types)
      fdt_support.c: In function 'fdt_node_offset_by_compat_reg':
      fdt_support.c:1173:17: warning: initialization discards 'const' qualifier from pointer target type [enabled by default]
      
      See also linux kernel commit 0131d897 "of/address: use proper
      endianess in get_flags".
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Cc: Jerry Van Baren <gvb.uboot@gmail.com>
      8aa5ec6e
    • Kim Phillips's avatar
      treewide: include libfdt_env.h before fdt.h · 12e06fe0
      Kim Phillips authored
      and, if including libfdt.h which includes libfdt_env.h in
      the correct order, don't include fdt.h before libfdt.h.
      
      this is needed to get the fdt type definitions set from
      the project environment before fdt.h uses them.
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Cc: Jerry Van Baren <gvb.uboot@gmail.com>
      12e06fe0
  6. 15 Feb, 2012 1 commit
  7. 13 Nov, 2011 1 commit
  8. 18 Oct, 2011 1 commit
  9. 15 Oct, 2011 2 commits
  10. 30 Sep, 2011 2 commits
  11. 15 Jul, 2011 3 commits
  12. 18 Oct, 2010 1 commit
  13. 12 Oct, 2010 1 commit
    • Anatolij Gustschin's avatar
      fdt_support: support adding EDID property to FDT display nodes · beca5a5f
      Anatolij Gustschin authored
      Boards can pass display timing info for drivers using EDID
      block. Provide common function to add board specific EDID
      data to the device tree. Subsequent patch makes use of this
      functionality.
      
      Detailed timing descriptor data from EDID is used for
      programming the display controller. This is currently
      implemented on the Linux side by the fsl-diu-fb frame
      buffer driver and it is documented there in
      Documentation/powerpc/dts-bindings/fsl/diu.txt.
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      Cc: Gerald Van Baren <vanbaren@cideas.com>
      beca5a5f
  14. 23 Sep, 2010 1 commit
    • Stefan Roese's avatar
      ppc4xx/fdt/flash: Change fdt_fixup_nor_flash_node() to not rely on cs size · 8a805df1
      Stefan Roese authored
      This patch changes the behaviour of the fdt_fixup_nor_flash_node()
      function. Now it doesn't patch the size of the "reg" property with the
      chip-select size, but with the size returned from the new function
      flash_get_bank_size(). This function will return per weak default the
      flash size of the bank (bank = chip-select numer) detected by the flash
      driver. If this does not fit your needs, this function may be overridden
      by a board specific one.
      
      For this the parameters needed to be changed. So I intentionally squashed
      the PPC4xx stuff using this routine into this patch. Otherwise it would
      not be git-bisectable anymore.
      
      The board specific function for the AMCC/APM Ebony eval board is now
      included in this patch version.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Tested-by: default avatarDetlev Zundel <dzu@denx.de>
      Cc: Gerald Van Baren <vanbaren@cideas.com>
      Cc: Wolfgang Denk <wd@denx.de>
      8a805df1
  15. 26 Jul, 2010 1 commit
  16. 20 Jul, 2010 2 commits
  17. 16 Jul, 2010 1 commit
  18. 07 Apr, 2010 1 commit
  19. 21 Mar, 2010 1 commit
  20. 23 Oct, 2009 1 commit
  21. 12 Jun, 2009 1 commit
  22. 24 Oct, 2008 2 commits
  23. 13 Sep, 2008 1 commit
  24. 26 Aug, 2008 3 commits
  25. 21 Aug, 2008 1 commit
  26. 14 Jul, 2008 1 commit
  27. 26 Mar, 2008 1 commit
  28. 25 Mar, 2008 1 commit
  29. 09 Jan, 2008 1 commit
    • Timur Tabi's avatar
      85xx: add ability to upload QE firmware · b8ec2385
      Timur Tabi authored
      Define the layout of a binary blob that contains a QE firmware and instructions
      on how to upload it.  Add function qe_upload_firmware() to parse the blob and
      perform the actual upload.  Add command-line command "qe fw" to take a firmware
      blob in memory and upload it.  Update ft_cpu_setup() on 85xx to create the
      'firmware' device tree node if U-Boot has uploaded a firmware.  Fully define
      'struct rsp' in immap_qe.h to include the actual RISC Special Registers.
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
      b8ec2385
  30. 08 Jan, 2008 1 commit
  31. 08 Dec, 2007 1 commit