Skip to content
Snippets Groups Projects
  1. Oct 20, 2016
  2. Oct 03, 2016
  3. Sep 23, 2016
  4. Sep 22, 2016
  5. Sep 19, 2016
  6. Sep 12, 2016
  7. Sep 06, 2016
  8. Sep 05, 2016
  9. Aug 29, 2016
  10. Aug 25, 2016
    • Gatis Paeglis's avatar
      Disable use of O_TMPFILE by default · 38f88390
      Gatis Paeglis authored
      
      It is not uncommon for embedded devices to use
      relatively older versions of the Linux kernel,
      where file systems do not support O_TMPFILE
      (since Linux 3.11) or implementations contain
      bugs (with fixes available in some > 3.11 version).
      
      Change-Id: Ic204bf6dcbdbcece87d42eea8eed9e114bd757ad
      Reviewed-by: default avatarTeemu Holappa <teemu.holappa@theqtcompany.com>
      38f88390
    • Gatis Paeglis's avatar
      ostree: Update revison · 96e38aae
      Gatis Paeglis authored
      
      - Dependency to libgsystem has been removed by the
        upstream project.
      - Booting without initramfs does not require patching
        kernel anymore. Now ostree-prepare-root can be used
        as the init process to prepare rootfs for ostree.
      
      For more info refer to the ostree's change log.
      
      Change-Id: I7de61ffc2f9957055402f7733f16566e635a8e99
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@qt.io>
      96e38aae
  11. Aug 24, 2016
  12. Jun 22, 2016
  13. Jun 07, 2016
  14. Jun 02, 2016
  15. May 18, 2016
  16. Apr 28, 2016
  17. Apr 12, 2016
  18. Apr 11, 2016
  19. Apr 08, 2016
  20. Mar 16, 2016
  21. Mar 15, 2016
  22. Mar 14, 2016
  23. Mar 08, 2016
    • Gatis Paeglis's avatar
      ostree: Mount boot partition from user space · 2bd71505
      Gatis Paeglis authored
      
      In the current approach we assumed that boot/
      
      - is on a separate boot partition
      - boot partition is right before rootfs partition
      - rootfs parition is provided as a *device node*
      - has "ext2" filesystem (mount shell cmd tries to
        auto detect FS type, mount system call does not.)
      
      The new approch does not assume any of the above, and
      moves this logic from early user space (initramfs) to
      user space. Initramfs by design should be used only to
      prepare the rootfs, other tasks should be done later.
      
      Change-Id: Idc429c8061c1fd486658e4b4d170ee487682cc91
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@theqtcompany.com>
      2bd71505
    • Gatis Paeglis's avatar
      ostree: Do not use grub2-mkconfig. · 91b76a3a
      Gatis Paeglis authored
      For more details see:
      https://bugzilla.gnome.org/show_bug.cgi?id=762220
      
      To summarize:
      
      1) The current approach is less flexible than using a
         custom 'ostree-grub-generator' script. Each device can
         adjust this script for its needs, instead of hardcoding
         some values in ostree-bootloader-grub2.c.
      
      2) Too much overhead on embedded to generate grub.cfg
         via /etc/grub.d/ configuration files. It is still
         possible to do so, even with this patch applied.
      
      3) The grub2-mkconfig code path has other issues:
         https://bugzilla.gnome.org/show_bug.cgi?id=761180
      
      
      
      Change-Id: I077838fdf16fbbb42f98df6fa6720bfbaf7c6f8b
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@theqtcompany.com>
      91b76a3a
  24. Feb 23, 2016
    • Gatis Paeglis's avatar
      NUC: Use custom image layout · 769ae557
      Gatis Paeglis authored
      
      This patch adds a new image class 'image_dd', by default
      it has an empty boot partition. image_dd_efi extends this
      class to support Intel NUC board. The layout of a generated
      image is a prerequisite for OSTree integarion.
      
      Image generated by 'hddimg' produces rootfs.img (ext3
      filesystem file) and then "live" boots it from initramfs
      by mounting rootfs.img via loop device. For OTA integration
      we need to access contents of rootfs.img already from
      boot loader.
      
      The custom 'image_nuc_efi' layout allow for fully atomic
      updates on EFI based system, by keeping GRUB-EFI binary
      on a dedicated EFI system partition (ESP). OSTree currently
      is not fully atomic on EFI systems, but with this setup
      we use GRUB-BIOS code path in OSTree, which is atomic.
      After EFI firmware has loaded the GRUB-EFI binary, everything
      else is done on rootfs parition.
      
      One limitation from the above scenario is that you would
      need to update /EFI/BOOT/bootx64.efi (GRUB-EFI) binary
      manually. Not sure how common it is to update a boot loader
      binary on a deployed system, but its not impossible.
      
      Change-Id: Ibf2840aecd548000372131c4ded5cffa11ff1b0f
      Reviewed-by: default avatarTeemu Holappa <teemu.holappa@theqtcompany.com>
      769ae557
    • Gatis Paeglis's avatar
      Format os-release file as specified in standard · 4fc10054
      Gatis Paeglis authored
      os-release spec:
      https://www.freedesktop.org/software/systemd/man/os-release.html
      
      
      
      "Variable assignment values must be enclosed in double or single
      quotes if they include spaces, semicolons or other special
      characters outside of A–Z, a–z, 0–9."
      
      Some tools might fail to read the file properly. Dracut for
      example prints warnings when parsing os-release file.
      
      Change-Id: I678a59aa8f33aa0c0398afb8ac87384f7ed52bc8
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@theqtcompany.com>
      4fc10054
Loading