Skip to content
Snippets Groups Projects
  1. Apr 25, 2020
  2. Apr 24, 2020
  3. Apr 23, 2020
  4. Apr 22, 2020
  5. Apr 21, 2020
  6. Apr 20, 2020
  7. Apr 19, 2020
  8. Apr 18, 2020
  9. Apr 16, 2020
    • Niklas Cathor's avatar
      samsung-kminilte: disable v4l udev rules (MR 1160) · 99d6f504
      Niklas Cathor authored and Minecrell's avatar Minecrell committed
      With the camera driver (VIDEO_EXYNOS_FIMC_IS) enabled, the system
      would randomly panic during startup. Even though the camera does
      not currently work on this system, the driver is nonetheless enabled
      to make the flashlight work.
      
      The panics seem to be triggered by udev's "v4l_id", which queries
      capabilities of video4linux devices.
      
      This change adds a udev rules file, to override the behavior of udev's
      default rules for v4l.
      Unverified
      99d6f504
  10. Apr 14, 2020
    • Minecrell's avatar
      device/device-<msm8916-mainline>: minor cleanup and fixes (MR 1125) · e129e3dd
      Minecrell authored
      - Cleanup kernel cmdline:
        - earlycon can automatically detect the memory address of
          the UART controller based on the device tree
        - the comma before n8 in console=ttyMSM0,115200,n8 is actually
          invalid so this was not parsed correctly. However, it is the
          default anyway so we might as well remove it completely
      
      - Configure deviceinfo_getty for all devices
      
      - Workaround probe issue of display by adding a softdep on the panel
        module. This allows the display to work when excluding proprietary
        firmware (just a weird side effect, see comment in modprobe.conf...)
      Unverified
      e129e3dd
    • Minecrell's avatar
      wileyfox-crackling: remove downstream kernel (MR 1125) · 9444bb30
      Minecrell authored
      The device port gets increasingly hard to maintain with all the differences
      between the downstream and the mainline kernel. Especially deviceinfo
      has quite some duplication only because the downstream kernel needs to be
      handled as well.
      
      The mainline port has much more features working. The only limitation
      compared to the downstream kernel is the lack of a proper charging driver.
      But even on downstream postmarketOS the battery driver is not working
      properly for some reason.
      
      For charging, a downstream installation in recovery seems more suitable
      at the moment. Eventually we will build some functionality into the
      bootloader to load a simple downstream initramfs when the device gets
      booted for charging.
      Unverified
      9444bb30
  11. Apr 13, 2020
Loading