forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

community/motorola-harpia: enable screen in initfs (MR 2110)

Browse source 
As of MR 2039, the kernel modules are now stripped (INSTALL_MOD_STRIP=1).
It turns out that this massively reduces their size so that including
the panel + touchscreen modules in the initfs still fits into the boot
partition. This allows the splash screen and osk-sdl to work correctly.
This commit is contained in:
Minecrell 2021-04-11 20:10:17 +02:00 committed by Clayton Craft
parent 70173bde87
commit d463361835
No known key found for this signature in database
GPG key ID: 7A3461CA187CEA54
3 changed files with 5 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
device/community/device-motorola-harpia/APKBUILD
View file

@ -3,15 +3,15 @@
# Co-Maintainer: Minecrell <minecrell@minecrell.net>
pkgname=device-motorola-harpia
pkgdesc="Motorola Moto G4 Play"
pkgver=3
pkgrel=2
pkgver=4
pkgrel=0
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
depends="postmarketos-base mkbootimg soc-qcom-msm8916"
makedepends="devicepkg-dev"
source="deviceinfo modprobe.conf"
source="deviceinfo"
subpackages="
$pkgname-kernel-mainline:kernel_mainline
@ -53,5 +53,4 @@ nonfree_firmware_modem() {
mkdir "$subpkgdir"
}
sha512sums="37fca3131876b7deeae86b0b7eec37ec649534cbfda85f6bc5c81e7066becb129752f019b528922f2d7d105f2879b38d3ad77080b42e3b89c3628709876acda6 deviceinfo
739d208365990a659a12b47013cc430d701bc5f202d5a7df93bf5db7628191d135825344087b93eb05f0db59d1d0e3adc0e49d102e294abf366902afd44251ab modprobe.conf"
sha512sums="15d2edecf5a9d3a2e08cda6a9a0ced7fc1d26cf9f151a7fbb949f08bbbb152561ba025dd2982de8c601966ac6d4740d5f79379911570b1ec0ba12b4281a0eeb8 deviceinfo"

5
device/community/device-motorola-harpia/deviceinfo
View file

@ -9,7 +9,7 @@ deviceinfo_year="2016"
deviceinfo_dtb_mainline="qcom/msm8916-motorola-harpia"
deviceinfo_dtb_mainline_modem="qcom/msm8916-motorola-harpia-modem"
deviceinfo_append_dtb="true"
deviceinfo_modules_initfs=""
deviceinfo_modules_initfs="panel-motorola-harpia-boe panel-motorola-harpia-tianma msm rmi-i2c"
deviceinfo_arch="aarch64"
# Device related
@ -20,9 +20,6 @@ deviceinfo_screen_width="720"
deviceinfo_screen_height="1280"
deviceinfo_getty="ttyMSM0;115200"
# MSM DRM cannot take over the framebuffer from the bootloader at the moment
deviceinfo_no_framebuffer="true"
# Bootloader related
deviceinfo_flash_method="fastboot"
deviceinfo_kernel_cmdline="earlycon console=ttyMSM0,115200 PMOS_NO_OUTPUT_REDIRECT"

20
device/community/device-motorola-harpia/modprobe.conf
View file

@ -1,20 +0,0 @@
#
# There is a weird probe issue if both MSM DRM and the panel driver are built
# as modules: When MSM DRM is loaded it registers the DSI bus for the panel.
# At this point the panel is not loaded yet, so the kernel sends an uevent
# to userspace to load the necessary panel module.
#
# This causes some delay until the panel module is loaded, so MSM DRM fails to
# probe temporarily and returns -EPROBE_DEFER (to request probing again later).
# Unfortunately this will also unregister the DSI bus for the panel, and the
# kernel will not try probing MSM DRM + panel again until some other (slow)
# driver loads after MSM DRM.
#
# Usually WCNSS (WiFi/BT) fits that criteria, allowing the display to work.
# But this does not work if the user decides to exclude proprietary firmware.
#
# To avoid this problem we add an explicit soft dependency for MSM DRM
# on the panel module, so modprobe loads the panel module first and MSM DRM
# will immediately find the panel it is looking for.
#
softdep msm pre: panel-tianma-499