This project is mirrored from git://git.denx.de/u-boot.git. The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 30 Nov, 2017 1 commit
  2. 17 Nov, 2017 1 commit
    • Masahiro Yamada's avatar
      pylibfdt: compile pylibfdt only when dtoc/binman is necessary · d6a0c78a
      Masahiro Yamada authored
      Currently, pylibfdt is always compiled if swig is installed on your
      machine.  It is really annoying because most of targets (excepts
      x86, sunxi, rockchip) do not use dtoc or binman.
      
      "checkbinman" and "checkdtoc" are wrong.  It is odd that the final
      build stage checks if we have built necessary tools.  If your platform
      depends on dtoc/binman, you must be able to build pylibfdt.  If swig
      is not installed, it should fail immediately.
      
      I added PYLIBFDT, DTOC, BINMAN entries to Kconfig.  They should be
      property select:ed by platforms that need them.  Kbuild will descend
      into scripts/dtc/pylibfdt/ only when CONFIG_PYLIBFDT is enabled.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      d6a0c78a
  3. 06 Oct, 2017 2 commits
  4. 24 Sep, 2017 2 commits
  5. 13 Aug, 2017 1 commit
  6. 10 Jul, 2017 1 commit
  7. 01 Jun, 2017 1 commit
  8. 10 May, 2017 1 commit
    • Alex Deymo's avatar
      Allow boards to initialize the DT at runtime. · 82f766d1
      Alex Deymo authored
      In some boards like the Raspberry Pi the initial bootloader will pass
      a DT to the kernel. When using U-Boot as such kernel, the board code in
      U-Boot should be able to provide U-Boot with this, already assembled
      device tree blob.
      
      This patch introduces a new config option CONFIG_OF_BOARD to use instead
      of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT
      from a board-specific funtion instead of bundling one with U-Boot or as
      a separated file. This allows boards like the Raspberry Pi to reuse the
      device tree passed from the bootcode.bin and start.elf firmware
      files, including the run-time selected device tree overlays.
      Signed-off-by: Alex Deymo's avatarAlex Deymo <deymo@google.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      82f766d1
  9. 05 Apr, 2017 1 commit
  10. 29 Mar, 2017 1 commit
    • mario.six@gdsys.cc's avatar
      dm: Add callback to modify the device tree · 0db4cd25
      mario.six@gdsys.cc authored
      Certain boards come in different variations by way of utilizing daughter
      boards, for example. These boards might contain additional chips, which
      are added to the main board's busses, e.g. I2C.
      
      The device tree support for such boards would either, quite naturally,
      employ the overlay mechanism to add such chips to the tree, or would use
      one large default device tree, and delete the devices that are actually
      not present.
      
      Regardless of approach, even on the U-Boot level, a modification of the
      device tree is a prerequisite to have such modular families of boards
      supported properly.
      
      Therefore, we add an option to make the U-Boot device tree (the actual
      copy later used by the driver model) writeable, and add a callback
      method that allows boards to modify the device tree at an early stage,
      at which, hopefully, also the application of device tree overlays will
      be possible.
      Signed-off-by: default avatarMario Six <mario.six@gdsys.cc>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      0db4cd25
  11. 26 Mar, 2017 1 commit
  12. 23 Mar, 2017 1 commit
    • mario.six@gdsys.cc's avatar
      dm: Add callback to modify the device tree · 2a792753
      mario.six@gdsys.cc authored
      Certain boards come in different variations by way of utilizing daughter
      boards, for example. These boards might contain additional chips, which
      are added to the main board's busses, e.g. I2C.
      
      The device tree support for such boards would either, quite naturally,
      employ the overlay mechanism to add such chips to the tree, or would use
      one large default device tree, and delete the devices that are actually
      not present.
      
      Regardless of approach, even on the U-Boot level, a modification of the
      device tree is a prerequisite to have such modular families of boards
      supported properly.
      
      Therefore, we add an option to make the U-Boot device tree (the actual
      copy later used by the driver model) writeable, and add a callback
      method that allows boards to modify the device tree at an early stage,
      at which, hopefully, also the application of device tree overlays will
      be possible.
      Signed-off-by: default avatarMario Six <mario.six@gdsys.cc>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      2a792753
  13. 15 Jul, 2016 1 commit
  14. 23 May, 2016 1 commit
    • Michal Simek's avatar
      spl: Setup default value for OF_LIST · c409bd01
      Michal Simek authored
      OF_LIST can't remain empty that's why setup it up to default DTB.
      
      If it is empty u-boot.img is created without FDT partition:
      For example:
        ./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a
      0x8000000 -e 0 -n "U-Boot 2016.05-rc3 ..." -E -b  -d u-boot-nodtb.bin u-boot.img
      Can't set 'timestamp' property for '' node (FDT_ERR_NOSPACE)
      FIT description: Firmware image with one or more FDT blobs
      Created:         Wed May  4 15:02:52 2016
       Image 0 (firmware@1)
        Description:  U-Boot 2016.05-rc3-00080-gff2e12ae22a8-dirty for zynqmp
      board
        Created:      Wed May  4 15:02:52 2016
        Type:         Firmware
        Compression:  uncompressed
        Data Size:    unavailable
        Architecture: ARM
        Load Address: 0x08000000
       Default Configuration: 'conf@1'
       Configuration 0 (conf@1)
        Description:  unavailable
        Kernel:       unavailable
      
      And then image like this doesn't contain description and link to FDT and
      can't boot.
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      c409bd01
  15. 14 Mar, 2016 2 commits
  16. 25 Feb, 2016 1 commit
  17. 25 Jan, 2016 1 commit
    • Masahiro Yamada's avatar
      Revert "devicetree: use wildcard to clean arch subdir" · be6b2b31
      Masahiro Yamada authored
      This reverts commit 67871a59.
      
      Since that commit, out-of-tree cleaning emits lots of warnings.
      
      $ make O=foo clean
      make[1]: Entering directory `/home/masahiro/workspace/u-boot/foo'
      ../dts/../arch/arm/dts/Makefile:209: warning: overriding commands for target `dtbs'
      ../dts/../arch/arc/dts/Makefile:15: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/microblaze/dts/Makefile:13: warning: overriding commands for target `dtbs'
      ../dts/../arch/arm/dts/Makefile:209: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/mips/dts/Makefile:14: warning: overriding commands for target `dtbs'
      ../dts/../arch/microblaze/dts/Makefile:13: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/nios2/dts/Makefile:13: warning: overriding commands for target `dtbs'
      ../dts/../arch/mips/dts/Makefile:14: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/powerpc/dts/Makefile:13: warning: overriding commands for target `dtbs'
      ../dts/../arch/nios2/dts/Makefile:13: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/sandbox/dts/Makefile:14: warning: overriding commands for target `dtbs'
      ../dts/../arch/powerpc/dts/Makefile:13: warning: ignoring old commands for target `dtbs'
      ../dts/../arch/x86/dts/Makefile:22: warning: overriding commands for target `dtbs'
      ../dts/../arch/sandbox/dts/Makefile:14: warning: ignoring old commands for target `dtbs'
      make[1]: Leaving directory `/home/masahiro/workspace/u-boot/foo'
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      be6b2b31
  18. 22 Jan, 2016 1 commit
  19. 16 Jan, 2016 1 commit
  20. 03 Oct, 2015 1 commit
  21. 17 Sep, 2015 1 commit
  22. 31 Aug, 2015 1 commit
  23. 18 Aug, 2015 1 commit
  24. 21 Jul, 2015 1 commit
    • Simon Glass's avatar
      dm: Reduce SPL device tree size · fa78e0a3
      Simon Glass authored
      The SPL device tree size must be minimised to save memory. Only include
      properties that are needed by SPL - this is determined by the presence
      of the "u-boot,dm-pre-reloc" property. Also remove a predefined list of
      unused properties from the nodes that remain.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      fa78e0a3
  25. 23 Apr, 2015 1 commit
  26. 24 Feb, 2015 1 commit
  27. 27 Oct, 2014 1 commit
  28. 25 Sep, 2014 2 commits
  29. 19 Jun, 2014 1 commit
  30. 11 Jun, 2014 1 commit
  31. 05 Jun, 2014 1 commit
  32. 28 Mar, 2014 1 commit
  33. 19 Feb, 2014 4 commits
    • Masahiro Yamada's avatar
      dts: generate multiple device tree blobs · 3284c8b8
      Masahiro Yamada authored
      It is convenient to have all device trees on the same SoC compiled.
      It allows for later easy repackaging without the need to re-run
      the make file.
      
        - Build device trees with the same SoC under arch/$(ARCH)/dts
      
        - Copy the one specified by CONFIG_DEFAULT_DEVICE_TREE or
          DEVICE_TREE=... to dts/dt.dtb
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      3284c8b8
    • Masahiro Yamada's avatar
      dts: move device tree sources to arch/$(ARCH)/dts/ · 5ab502cb
      Masahiro Yamada authored
      Unlike Linux Kernel, U-Boot historically had *.dts files under
      board/$(VENDOR)/dts/ and *.dtsi files under arch/$(ARCH)/dts/.
      
      I think arch/$(ARCH)/dts dicretory is a better location
      to store both *.dts and *.dtsi files.
      
      For example, before this commit, board/xilinx/dts directory
      had both Microblaze dts (microblaze-generic.dts) and
      ARM dts (zynq-*.dts), which are totally unrelated.
      
      This commit moves *.dts to arch/$(ARCH)/dts/ directories,
      allowing us to describe nicely mutiple DTBs generation in the next commit.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      5ab502cb
    • Masahiro Yamada's avatar
      dts: re-write dts/Makefile more simply with Kbuild · 6ab6b2af
      Masahiro Yamada authored
      Useful rules in scripts/Makefile.lib allows us to easily
      generate a device tree blob and wrap it in assembly code.
      
      We do not need to parse a linker script to get output format and arch.
      
      This commit deletes ./u-boot.dtb since it is a copy of dts/dt.dtb.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      6ab6b2af
    • Masahiro Yamada's avatar
      kbuild: use scripts/Makefile.clean · efcf8619
      Masahiro Yamada authored
      This commit refactors cleaning targets such as
      clean, clobber, mrpropper, distclean
      with scripts/Makefile.clean.
      
      By using scripts/Makefile.clean, we can recursively descend
      into subdirectories and delete generated files there.
      
      We do not need add a big list of generated files
      to the "clean" target.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      efcf8619