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

41 lines
1.1 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/devicepkg>
*: 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=device-google-crosshatch
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"
pkgver=0.1
device/*/device-*: rebuild for new splash screens (MR 2222) [ci:ignore-count]
2022-01-20 22:01:52 +00:00
pkgrel=10
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
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
depends="postmarketos-base mkbootimg mesa-dri-swrast"
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="devicepkg-dev"
source="deviceinfo"
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
subpackages="
$pkgname-kernel-downstream:kernel_downstream
$pkgname-kernel-mainline:kernel_mainline
"
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() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
kernel_downstream() {
pkgdesc="LineageOS downstream kernel (recommended)"
depends="linux-google-crosshatch"
google-crosshatch: fix build with downstream kernel (!1016) The downstream kernel doesn't provide a separate dtb file, but the experimental mainline kernel does. Previously, the deviceinfo specified a dtb file for both kernels, and pmbootstrap ignored the missing file for downstream kernel. pmbootstrap now errors when the dtb file is missing, so this fixes the downstream kernel by specifying a dtb file only for the upstream kernel.
2020-03-01 03:52:49 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
}
kernel_mainline() {
device/*: clarify "close to mainline" (cosmetic) (MR 1408) Make it clear, that these kernels are not mainline, but "close to mainline". [ci:skip-build] [ci:skip-vercheck]: just changing pkgdesc Related: https://wiki.postmarketos.org/wiki/(Close_to)_Mainline
2020-07-11 09:16:39 +00:00
pkgdesc="Close to mainline; DO NOT USE: doesn't work (only USB networking is supported)"
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
depends="linux-google-crosshatch-mainline firmware-google-crosshatch-mainline-dtbo"
google-crosshatch: fix build with downstream kernel (!1016) The downstream kernel doesn't provide a separate dtb file, but the experimental mainline kernel does. Previously, the deviceinfo specified a dtb file for both kernels, and pmbootstrap ignored the missing file for downstream kernel. pmbootstrap now errors when the dtb file is missing, so this fixes the downstream kernel by specifying a dtb file only for the upstream kernel.
2020-03-01 03:52:49 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
google-crosshatch: add WIP mainline kernel (!226) This is tested to boot on google-crosshatch, following these instructions: $ pmbootstrap init, choose the mainline kernel $ pmbootstrap install --no-fde $ pmbootstrap initfs hook_add debug-shell (enter fastboot mode on the device) $ fastboot set_active a $ fastboot flash dtbo_a ~/.local/var/pmbootstrap/chroot_rootfs_google-crosshatch/boot/dtbo-google-crosshatch-mainline.img $ pmbootstrap flasher boot And you should get telnet after a while. This kernel takes a long time to build, so [skip ci]. I can confirm it builds locally. Note that this patch adds the mainline dtb path to deviceinfo. But the parameter gets ignored on the downstream kernel, so it's fine to keep it in the shared deviceinfo. Mainlining this device is work in progress, details at: https://gitlab.com/postmarketOS/pmaports/issues/153
2019-02-17 06:00:28 +00:00
}
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/*: remove empty variables (MR 2534) [ci:ignore-count] [ci:skip-vercheck] [ci:skip-build]: built all the device packages successfully in CI already
2021-09-18 17:06:03 +00:00
sha512sums="
2a24ae9840959bf5fc39f15f2a4129690fd193450874193f8c312f4e26ee76b69d62baba1826824c566253288d9af91c79d6744e09f35fbc74cf6fc8bd63803f deviceinfo
"
Reference in a new issue Copy permalink