Skip to content
Snippets Groups Projects
  1. Jun 23, 2024
  2. Apr 20, 2024
  3. Mar 23, 2024
  4. Jan 22, 2024
  5. Dec 07, 2023
  6. Oct 31, 2023
    • Casey's avatar
      devicepkg-dev: add pmtest helper (MR 4420) · ac1d78a2
      Casey authored
      Add a helper to generate a post-install script for device pmtest
      subpackages. This script configures the console and enables logging in
      the initramfs for images running in CI.
      
      [ci:ignore-count]
      Unverified
      ac1d78a2
  7. Sep 25, 2023
  8. Aug 04, 2023
  9. Jul 31, 2023
  10. Jul 10, 2023
  11. Jun 03, 2023
  12. Mar 14, 2023
  13. Mar 09, 2023
  14. Feb 18, 2023
  15. Oct 16, 2022
  16. Feb 13, 2022
  17. Jan 22, 2022
  18. Sep 03, 2021
  19. Apr 11, 2021
  20. Nov 19, 2020
  21. May 24, 2020
  22. Apr 25, 2020
  23. Apr 05, 2020
  24. Apr 04, 2020
  25. Mar 14, 2020
  26. Mar 01, 2020
  27. Feb 28, 2020
  28. Feb 27, 2020
  29. Jan 28, 2020
    • Minecrell's avatar
      main/devicepkg-dev: Fix shellcheck warnings in splash screen generation (!899) · d4ee1230
      Minecrell authored and Bart Ribbers's avatar Bart Ribbers committed
      (These were present before the code was moved to devicepkg-dev.)
      Unverified
      d4ee1230
    • Minecrell's avatar
      main/{devicepkg-dev,postmarketos-mkinitfs}: statically generate splash screens (!899) · e3d07c83
      Minecrell authored and Bart Ribbers's avatar Bart Ribbers committed
      We need to generate the splash screens separately for each device,
      because they are specific to the device's display resolution.
      
      At the moment we do this dynamically during the installation process.
      This has the advantage that there is no need to re-build all device
      packages when one of the splash screen is changed (or a new one is added).
      
      In reality, however, the splash screens do not change very frequently.
      On the other hand, generating the splash screens dynamically has signficant
      disk usage overhead for a minimal ("none" UI) rootfs:
      
      The Python interpreter together with the necessary libraries requires
      about ~60 MB of disk space on aarch64.
      The splash screens itself require about ~100 KB for 720x1280.
      
      This is not necessary if we move the splash screen generation into
      devicepkg-dev, which is used to build the device package for all devices.
      Another advantage is that we no longer need the (rather complicated)
      caching mechanism for splash screens - so we actually end up with less
      lines than before.
      
      rootfs size for samsung-a5ulte ("none" UI):
        Before: 450M
        After:  388M (-62M)
      
      After this change, every(!) device package needs to be rebuilt once.
      No changes are necessary in device packages.
      Unverified
      e3d07c83
  30. Jan 18, 2020
  31. Sep 26, 2019
  32. Feb 05, 2019
  33. Jan 29, 2019
  34. Jan 28, 2019
  35. Nov 27, 2018
Loading