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

56 lines
2.7 KiB
Text
Raw Normal View History

New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
google-crosshatch: switch to LineageOS kernel (!184)
2019-01-29 06:53:07 +00:00
# Kernel config based on: arch/arm64/configs/lineageos_crosshatch_defconfig
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
*: 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-google-crosshatch
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
pkgver=4.9.200
pkgrel=0
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
pkgdesc="Google Pixel 3 XL kernel fork"
arch="aarch64"
_carch="arm64"
_flavor="google-crosshatch"
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"
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev dtbtool openssl-dev lz4 dtc"
# Source
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
_repository="android_kernel_google_msm-4.9"
# Lineage 17.1 branch
_commit="d6cae0bddcfc25ce897d43a11a4d3c5d07777831"
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"
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +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/LineageOS/$_repository/archive/$_commit.tar.gz
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
$_config
clk-qcom-mdss-fix-in-tree-build.patch
arm64-boot-disable-building-DTBO-images.patch
sec_ts-disable-touchscreen-firmware-upgrade.patch
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
cam_sensor_io-fix-in-tree-build.patch
cam_sensor_module-add-cam_sensor_utils-to-include-path.patch
thermal-fix-build-error.patch
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +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/$_repository-$_commit"
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +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
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
}
package() {
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
KERNEL_IMAGE_NAME="Image.lz4-dtb" downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
}
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
sha512sums="e63d9c877182952aff07beeb2581dae15ae2316a24deb5bffdc633884a438ae30685d7cdd3302d275443a7d0bcd02b33d0d49461abe56995adf43e5a5636a81e linux-google-crosshatch-d6cae0bddcfc25ce897d43a11a4d3c5d07777831.tar.gz
52b99fb7bc3ed2426ef4f352c38ff768b75fbfdc0b11c1e66f94bc37463ec7da64e6fed43a68b44013b02a751dd3bc2c5b288ddec369a2f1015e4721674e322d config-google-crosshatch.aarch64
New device: google-crosshatch (Google Pixel 3 XL) (!83) A lot of patching was necessary, see the merge request and device wiki page for details. Thanks to opendata26 for helping with the port. https://wiki.postmarketos.org/wiki/Google_Pixel_3_XL_(google-crosshatch) [skip ci]: this hits the compile timeout
2018-11-27 06:45:33 +00:00
720c5856b7d1d8b3cb20f77507818b7fe1b4950d444f7ed20cb02d255987d8860d5ed293e81ea326f147af13004b524886c733123794ac62978fda13689a5189 clk-qcom-mdss-fix-in-tree-build.patch
google-crosshatch: update downstream kernel to LineageOS 17.1 kernel (!1040) This updates google-crosshatch's downstream kernel to Lineage 17.1's version (4.9.200, shared with Lineage's Pixel 3a port). The newer kernel is needed because this device's kernel requires a matching dtbo partition. The previous kernel would fail to boot with an Android 10 dtbo partition. Two patches were removed: Android 10's bootloader no longer passes the dm or skip_initramfs boot arguments because of the new dynamic partitions (https://source.android.com/devices/tech/ota/dynamic_partitions/ab_legacy). Changes from the LineageOS kernel config: https://gist.github.com/zhuowei/89b4135ff27e88f5a3dd3e4bf3cd31ab Tested by booting to USB networking and debug-shell: I have not tested flashing full pmOS using this kernel yet. For some reason, on this kernel, when pmOS can't find system partitions during the "Trying to mount subpartitions for 10 seconds..." stage, it waits for 70 seconds instead of 10 seconds. I'm not sure why. It does go to debug-shell correctly after a minute. [ci:skip-build]: already built successfully in CI
2020-03-03 01:53:59 +00:00
f175233f0cd4e5658937cf50c8535a2b9f1a0d9c7c3fb52aa54096f7733f292e1ab6c2cebadde8479980f27d9b8f7d03f98da3f8166858c8519d91de2a37f1ba arm64-boot-disable-building-DTBO-images.patch
7c941332085c6a2372ad083400e354c61f38752c2706d07592a7ce6a72aa5d8bb9cb10521fe0c941ac4e49aa3dbd2f9473c42ed2a10ec66b1b50b65e8ad1e0a8 sec_ts-disable-touchscreen-firmware-upgrade.patch
95c385ceefac59f863629ea684d5bf47a37cbc45537a5539cccb47eb57ed5544987b7a7824677c96089e8c6d867cda45e419b478654f8485b0694506afa43135 cam_sensor_io-fix-in-tree-build.patch
3003e2b6f16edb8a5d3b52a65249ddce91ba3be4bed9f6f6bc193a55f667ff5e2d4ff667af623ba7b949006f2a5e45f13e12214c9068c6bfebfb34f04d2b631b cam_sensor_module-add-cam_sensor_utils-to-include-path.patch
7bc6d7fd84750ad9244fde9e1c74dab395a827a784c984ab51d71c7e122fb13dcef9b8863a3d31322af64da94a53327af6a83c613b3b46e6c17acf1dcb7c5823 thermal-fix-build-error.patch"
Reference in a new issue Copy permalink