Skip to content
Snippets Groups Projects
  1. Sep 21, 2020
  2. Sep 14, 2020
  3. Aug 31, 2020
  4. Aug 05, 2020
  5. Jul 28, 2020
  6. Jul 20, 2020
  7. Jul 07, 2020
  8. Jul 01, 2020
  9. Jun 23, 2020
  10. Jun 22, 2020
    • Martin Kepplinger's avatar
      remove usr/bin/power_key.py · 73895838
      Martin Kepplinger authored
      The /usr/bin/power_key.py script basically does 2 things:
      
      * set a devfreq governor once (and handle frequencies but only on old kernels)
      * shut down the system when the power button is being pressed for ca. 2 seconds
      
      The first task is to be replaced via a simple udev rule. The second one
      is being tracked by Librem5/OS-issues#146
      
      
      and will be replaced by a GUI anyways.
      
      This solves problems with the power_key script:
      * it is not syncronised with the display system.
      * it is a nightmare to maintain and keep working
      
      In my tests, the long-press shutdown mechanism didn't work anymore, but if
      it does for you, this will remove it (temporarily, see the above issue).
      
      Signed-off-by: default avatarMartin Kepplinger <martin.kepplinger@puri.sm>
      73895838
  11. Jun 09, 2020
  12. Apr 23, 2020
  13. Apr 22, 2020
  14. Apr 06, 2020
  15. Apr 05, 2020
  16. Apr 03, 2020
    • Martin Kepplinger's avatar
      power_key.py: make compatible with 5.6 and later and the devkit · 71f71c1c
      Martin Kepplinger authored
      devfreq is being handled differently on our kernels. With 5.6+ frequency
      is switched automatically by the kernel for devfreq, when the powersave
      governor is set. So in that case we only to that (done by udev in the future).
      
      This also makes devfreq settings compatible with the devkit again because
      it reads the minimum frequency which is different than on the phone,
      from sysfs.
      
      Also, we particularly handle 5.6-rc based kernel versions that
      include a broken devfreq implementation / setup. starting with version
      5.6.0 we need to increment the ABI version to 2.
      71f71c1c
  17. Apr 01, 2020
  18. Mar 30, 2020
  19. Mar 28, 2020
  20. Mar 23, 2020
  21. Mar 06, 2020
Loading