1. 04 Oct, 2017 2 commits
  2. 02 Aug, 2017 1 commit
  3. 25 Jul, 2017 1 commit
  4. 24 Jul, 2017 3 commits
  5. 17 Jul, 2017 1 commit
  6. 12 Jul, 2017 2 commits
  7. 06 Jul, 2017 1 commit
  8. 04 Jul, 2017 3 commits
  9. 02 Jul, 2017 2 commits
  10. 26 Jun, 2017 1 commit
  11. 11 Jun, 2017 1 commit
  12. 19 Apr, 2017 1 commit
  13. 17 Apr, 2017 1 commit
  14. 14 Apr, 2017 1 commit
  15. 10 Apr, 2017 1 commit
  16. 22 Mar, 2017 1 commit
  17. 18 Mar, 2017 1 commit
  18. 17 Mar, 2017 1 commit
  19. 16 Mar, 2017 1 commit
  20. 13 Mar, 2017 2 commits
  21. 18 Jan, 2017 1 commit
  22. 15 Jan, 2017 1 commit
  23. 11 Jan, 2017 1 commit
  24. 02 Jan, 2017 3 commits
  25. 23 Dec, 2016 1 commit
    • Martin Michlmayr's avatar
      Only create DTB boot file on kernels that require DTB · 0dbe0d6e
      Martin Michlmayr authored
      Boot-DTB-Path can be specified to install the DTB to a file.  Some
      machines, such as the SheevaPlug, contain both a DTB-Append-From and
      a Boot-DTB-Path.
      
      If DTB-Append-From is set, a verson check is performed to see if the
      DTB is required and dtb_append is set to "yes" or "no" accordingly.
      However, there is no version check for Boot-DTB-Path.  This can lead
      to errors that the DTB couldn't be found on older kernels (i.e. older
      than the version specified in DTB-Append-From).
      
      Arguably, DTB-Append-From and Boot-DTB-Path together don't make sense
      (why would you append the DTB _and_ install it to /boot), but it's
      possible that users rely on this behaviour.
      
      Therefore, only honour Boot-DTB-Path if $dtb_append is not "no".  If
      it's "yes" or empty, we want to install the DTB to Boot-DTB-Path.
      But if $dtb_append is "no", it means we're on an old kernel without
      DTBs.
      
      Debian bug #789886
      0dbe0d6e
  26. 21 Dec, 2016 2 commits
  27. 20 Dec, 2016 1 commit
  28. 18 Dec, 2016 1 commit
  29. 17 Dec, 2016 1 commit
    • Martin Michlmayr's avatar
      Fix support for DTBs with absolute paths · 43c70b7c
      Martin Michlmayr authored
      It seems DTBs with absolute paths were broken even before I broke
      them with arm64 support.  We have to take the basename of the DTB
      with absolute path before installing it, otherwise we try to create
      subdirectories under /boot/dtbs/$kvers and this will fail:
      
      Installing /usr/lib/linux-image-4.9.0-rc8-armmp/armada-370-seagate-personal-cloud.dtb into /boot/dtbs/4.9.0-rc8-armmp//usr/lib/linux-image-4.9.0-rc8-armmp/armada-370-seagate-personal-cloud.dtb
      cp: cannot create regular file '/boot/dtbs/4.9.0-rc8-armmp//usr/lib/linux-image-4.9.0-rc8-armmp/armada-370-seagate-personal-cloud.dtb.new': No such file or directory
      43c70b7c