1. 09 Dec, 2015 1 commit
  2. 26 Oct, 2015 1 commit
    • Scott Wood's avatar
      fdt_support: Don't panic if stdout alias is missing · da77c819
      Scott Wood authored
      Currently, using fdt_fixup_stdout() on a device tree that is missing
      the relevant alias results in this:
      
      WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
      ERROR: /chosen node create failed
       - must RESET the board to recover.
      
      FDT creation failed! hanging...### ERROR ### Please RESET the board ###
      
      There is no reason for this to be a fatal error rather than a warning,
      and removing this allows for a smooth transition on a platform where
      the device tree currently lacks the correct aliases but will have them
      in the future.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      Cc: Kumar Gala <galak@kernel.crashing.org>
      Cc: Simon Glass <sjg@chromium.org>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarYork Sun <yorksun@freescale.com>
      da77c819
  3. 20 Jul, 2015 1 commit
    • Andre Przywara's avatar
      fdt: prevent clearing memory node if there are no banks · 5c1cf89f
      Andre Przywara authored
      Avoid clearing the reg property in the memory DT node if no memory
      banks have been specified for a board (CONFIG_NR_DRAM_BANKS == 0).
      This allows boards to let U-Boot skip the DT memory tinkering in case
      other firmware has already setup the node properly before.
      This should be safe as all callers of fdt_fixup_memory_banks that use
      a computed <banks> value put at least 1 in there.
      Add some documentation comments to the header file.
      Signed-off-by: default avatarAndre Przywara <osp@andrep.de>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      5c1cf89f
  4. 05 Jun, 2015 1 commit
    • Paul Kocialkowski's avatar
      fdt: Pass the device serial number through devicetree · 10be5b5d
      Paul Kocialkowski authored
      Before device-tree, the device serial number used to be passed to the kernel
      using ATAGs (on ARM). This is now deprecated and all the handover to the kernel
      should now be done using device-tree. Thus, this passes the serial-number
      property to the kernel using the serial-number property of the root node, as
      expected by the kernel.
      
      The serial number is a string that somewhat represents the device's serial
      number. It might come from some form of storage (e.g. an eeprom) and be
      programmed at factory-time by the manufacturer or come from identification
      bits available in e.g. the SoC.
      Signed-off-by: default avatarPaul Kocialkowski <contact@paulk.fr>
      Reviewed-by: default avatarSimon Glass <sgj@chromium.org>
      10be5b5d
  5. 06 May, 2015 1 commit
  6. 22 Apr, 2015 1 commit
  7. 01 Dec, 2014 1 commit
  8. 27 Nov, 2014 1 commit
  9. 25 Nov, 2014 1 commit
  10. 23 Nov, 2014 1 commit
  11. 21 Nov, 2014 3 commits
  12. 25 Sep, 2014 2 commits
  13. 09 Aug, 2014 1 commit
  14. 19 Jun, 2014 10 commits
  15. 23 Apr, 2014 2 commits
  16. 20 Jan, 2014 1 commit
  17. 09 Jan, 2014 1 commit
  18. 16 Dec, 2013 1 commit
  19. 16 Oct, 2013 1 commit
  20. 24 Jul, 2013 1 commit
  21. 07 Jun, 2013 1 commit
    • Stephen Warren's avatar
      fdt: remove unaligned access in fdt_fixup_ethernet() · 064d55f8
      Stephen Warren authored
      Some ARM compilers may emit code that makes unaligned accesses when
      faced with constructs such as:
      
      char mac[16] = "ethaddr";
      
      Replace this with a strcpy() call instead to avoid this. strcpy() is
      used here, rather than replacing all usage of the mac variable with the
      string itself, since the loop itself sprintf()s to the variable each
      iteration, so strcpy() is doing basically the same thing.
      
      Reported-by: Florian Meier
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      064d55f8
  22. 17 May, 2013 1 commit
  23. 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
  24. 11 Dec, 2012 1 commit
  25. 15 Oct, 2012 1 commit
  26. 13 Nov, 2011 1 commit