forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/testing/linux-xiaomi-aries/APKBUILD

62 lines
3.1 KiB
Text
Raw Normal View History

xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
# Kernel config based on: arch/arm/configs/aries-perf-user_defconfig
*: remove quotes around pkgname (MR 1186) TP:[AL3]:APKBUILD:5:pkgname must not be quoted [skip ci]: won't finish within 3 hours
2020-04-25 09:51:42 +00:00
pkgname=linux-xiaomi-aries
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
pkgver=3.4.113
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405) Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using aes-xts-plain64 as default cipher for cryptsetup (override with "pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940). I have executed "pmbootstrap kconfig edit" on each kernel, and manually toggled the option. The diff is not always clean, because for some kernels it is apparently the first time, that menuconfig was executed on the configs like that. In a few instances, it turned out that CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is already a requirement, but as the config was incomplete, it was not visible that this option was enabled). Very few times, I had to enable CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS. It would be great if we could automate such mass kconfig edits in the future, see pmbootstrap#1942. [skip ci]: I have verified, that every single one of these kernels builds. CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
pkgrel=1
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
pkgdesc="Xiaomi Mi 2 kernel fork"
arch="armhf"
_carch="arm"
_flavor="xiaomi-aries"
url="https://kernel.org"
license="GPL-2.0-only"
cross/arch-bin-masquerade, main/anbox-image, linux-*: use pmb:cross-native (MR 1169) https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1910 [skip ci]: CI fails because it can't download every release tarball to check checksums in 3h.
2020-04-21 01:24:27 +00:00
options="!strip !check !tracedeps pmb:cross-native"
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev xz"
# Source
_username="MoKee"
_repository="android_kernel_xiaomi_aries"
_commit="6a30963cf10e5b7cc938f3ac7b22af4ad72c0bf9"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
_config="config-$_flavor.$arch"
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
source="
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
$pkgname-$_commit.tar.gz::https://github.com/$_username/$_repository/archive/$_commit.tar.gz
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
$_config
gcc7-give-up-on-ilog2-const-optimizations.patch
gcc8-fix-put-user.patch
02_gpu-msm-fix-gcc5-compile.patch
03_fix-return-address.patch
04_fix-perf-trace-counters.patch
05_fix-adreno-trace.patch
06_fix-kgsl-events-include.patch
07_fix-kgsl-trace-h.patch
08_fix-red-screen.patch
"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
builddir="$srcdir/$_repository-$_commit"
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
prepare() {
default_prepare
**/linux-*: update usage of downstreamkernel_prepare helper (!1084) [skip-ci]: just downloading all kernel sources takes about one hour and ollieparanoid wants to merge it now. This already ran successfully with [ci:skip-build] and [ci:skip-vercheck].
2020-04-01 07:09:30 +00:00
. downstreamkernel_prepare
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
}
package() {
device/linux-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
}
sha512sums="3d461173c0ec72d243870bcb2ce1935b2ba1652a532b9b09ef0a3823b5961a3d58415fce2d57f054e1945dc9e70c5c9a68fc45aad26a0adb894bc96120847bc9 linux-xiaomi-aries-6a30963cf10e5b7cc938f3ac7b22af4ad72c0bf9.tar.gz
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405) Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using aes-xts-plain64 as default cipher for cryptsetup (override with "pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940). I have executed "pmbootstrap kconfig edit" on each kernel, and manually toggled the option. The diff is not always clean, because for some kernels it is apparently the first time, that menuconfig was executed on the configs like that. In a few instances, it turned out that CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is already a requirement, but as the config was incomplete, it was not visible that this option was enabled). Very few times, I had to enable CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS. It would be great if we could automate such mass kconfig edits in the future, see pmbootstrap#1942. [skip ci]: I have verified, that every single one of these kernels builds. CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
592ef2f3260be3eea45cf000817f76738492e48524d44093bc07c22d3ed7e33e78505a67ba0dfd5fb13948459d3cf67d3e76517a8700de327f2680475024e878 config-xiaomi-aries.armhf
xiaomi-aries: new device (Xiaomi Mi2) (!171) Finally got display working, but it's based on MoKee kernel which is also hosted on GitHub by community. So what works: * USB Networking * Flashing * Touchscreen * Display * Weston with Xwayland The device boots and shows the splash screen properly, after about 3 sec the screen went black. I had to "echo 127 > /sys/devices/i2c-0/0-0038/leds/lm3530-backlight/brightness" to make the backlight work, even though the value of it was already 127. [skip ci]: this was built successfully in CI already
2019-01-24 03:32:46 +00:00
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
87ff591431c34d920527de8d7640b93bfc1f09ad541a58645969bc1e6b64b89e7443c38dd263cafa9a6090f4a74e0ffcd49f94dba0a4f1df5306dad106ecfb3f 02_gpu-msm-fix-gcc5-compile.patch
7d5ca9d460030adf529466a8e8ef430337cbb998f78b1b5f37a2809fc745cdb16421dc314045ae411069d5af2ace7028f1139303ae4d6d583b6ae07ad931295e 03_fix-return-address.patch
f85ced49ee2f2461adea68dac0a10452aa809a7d41d869092d94eb085344919a9a385dec0c48011f4601ca4f441700f7fe49075c7eca4fb2d66b01f7d413ccb7 04_fix-perf-trace-counters.patch
71465422481ff79d2ddde7a9b55531b963f9a72efa9df47ecd5666353fbfb72e698290fa9e7f51522e2dadb2fa719ad5fc05fabe6c4ff7b9d387243a46d97d72 05_fix-adreno-trace.patch
f58e3d2d327f2fc06b3599903eca8113facd550010e8e0db4ace8fbdeb042f62fdca61e9748770a8891e21dc8211c8366518e8e16c5d61c6b49a88d34a16493c 06_fix-kgsl-events-include.patch
30b66b3b82a762a70381cc3e000f092c739714b116ff7fa4d13108e782789dce2f6e1490de54d720a8870fc52d379bd266abb873f79f7a021c0eced0fdbc70af 07_fix-kgsl-trace-h.patch
67c5d25b7d18644266ea043430655f46edf9cb7ff82612e25e63015a183206966cb41865236ebf642e83bed454cdc0392400e26f4be14f649c615415599229c7 08_fix-red-screen.patch"
Reference in a new issue Copy permalink