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

80 lines
3.1 KiB
Text
Raw Normal View History

Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
# APKBUILD based on linux-vanilla aport. Changes:
# - disabled module installation
# - add !check !tracedeps
# - package: just install zimage-dtb and kernel.release
#
# Kernel config based on: arch/arm/configs/dory_defconfig
# Changes:
# - apply patches to compile with gcc6
# - enable devtmpfs (needed for udev -> touch support in weston)
# - enabled CONFIG_VT (needed for weston to work)
Fix #737: Disable ANDROID_PARANOID_NETWORK for all devices (#742) * Disable ANDROID_PARANOID_NETWORK for all devices * Add APKBUILD comments * Bump pkgrels This was done with a script, see: <https://github.com/postmarketOS/pmbootstrap/pull/742#issuecomment-335608932>
2017-10-11 15:11:05 +00:00
# - disable ANDROID_PARANOID_NETWORK (removes network restrictions)
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
_flavor=lg-dory
_hash="6924014484d3406e3d2da384efc20e40e8a5ae80"
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.armhf"
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
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=linux-$_flavor
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
pkgver=3.10.40
case $pkgver in
*.*.*) _kernver=${pkgver%.*};;
*.*) _kernver=$pkgver;;
esac
*/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=6
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
arch="armhf"
pkgdesc="Kernel for LG G Watch"
url="https://android.googlesource.com/kernel/msm/+/android-msm-dory-3.10-marshmallow-mr1-wear-release"
device/linux-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev gcc6"
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"
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +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-$_hash.tar.gz::https://github.com/android/kernel_msm/archive/$_hash.tar.gz
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
$_config
compiler-gcc6.h
00_fix_return_address.patch
01_avoid_rpmb_read_during_boot.patch
02_fix_mdss_fb_refresh_rate.patch
03_fix_mdss_fb_memory_allocation.patch
"
license="GPL2"
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
_abi_release=$pkgver
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
_carch="arm"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
# Compiler: this kernel was only tested with GCC6. Feel free to make a merge
# request if you find out that it is booting working with newer GCCs as
# well. See <https://postmarketos.org/vendorkernel> for instructions.
if [ "${CC:0:5}" != "gcc6-" ]; then
CC="gcc6-$CC"
Revert "linux-*: use upstream gcc6 [skip ci]" This reverts commit ee659a5bb4ad94f33ec47e6ae7bf9e856f627155 and increases the pkgrels of all affected linux pmaports. I have compiled *every single kernel* that was modified with this commit, and it worked. That took 12 hours. So I'm pretty confident that this is a good commit. Let's roll it out and go back to stability \o/ I'll kick off the binary repo building directly after pushing this, but it will take some time until all binary packages are available again. [skip ci]: it wouldn't finish in time.
2018-11-30 20:56:06 +00:00
HOSTCC="gcc6-gcc"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
fi
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
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/kernel_msm-$_hash"
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +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
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-Alpine"
}
package() {
install -Dm644 "$builddir/arch/arm/boot/zImage-dtb" \
"$pkgdir/boot/vmlinuz-$_flavor"
install -D "$builddir/include/config/kernel.release" \
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
}
sha512sums="adc1e7852bebf3c11af87cfe9c994025e1415468be707664a25df33507d33de62125ab367dbc3f57ff84213ea479c2e8870d45603bc96df641b1bf853216201a linux-lg-dory-6924014484d3406e3d2da384efc20e40e8a5ae80.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
fb229e424d46e350d624bf39c5872642a64bf36a1072a9563bf8c1695de0498b6c574bc60c6eb638fa693b8b0979a7371300ca384b8649df0a4ceb7fc76c5700 config-lg-dory.armhf
Add LG G Watch (dory) support (#595) * Add LG G Watch (dory) support * Use github.com mirror instead of googlesource.com to have fixed checksum * Fix kernel compilation and remove unnecessary initfs-hook for framebuffer settings
2017-09-18 23:15:04 +00:00
d80980e9474c82ba0ef1a6903b434d8bd1b092c40367ba543e72d2c119301c8b2d05265740e4104ca1ac5d15f6c4aa49e8776cb44264a9a28dc551e0d1850dcc compiler-gcc6.h
ea1d3b5a234fa565e3c1a792de48f4fc4e6023d281d303c8e319c7ef28edc5739ab0e4dea0139a41f0a5c7d03e27921ccaa214fd0ac5c72245a094ce60128864 00_fix_return_address.patch
760fdff79df31754ebed59839f34fc8c5a61750471614ac93a01b1e13b2535e7ca1f879c0cad3e83ad92946586c91679ba853eac4fe454d7e948317c84d81941 01_avoid_rpmb_read_during_boot.patch
26b599d6b0c435d9e0b80f578c1cc0714d60f532a98efbbcb0e313f5c5dcd2c8619afa5776091d14ea65e268a1f128b378fe30ba1743e1428f3300b505a9861c 02_fix_mdss_fb_refresh_rate.patch
5208c3f33099e22516e00ab90234784918157d0712a8a9cf81418a7ea1c136601cb54f83d490577f2cadb6ed94ac6c6f242e7b310fb5f09222de568e416c6731 03_fix_mdss_fb_memory_allocation.patch"
Reference in a new issue Copy permalink