forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/community/linux-asus-me176c/APKBUILD

71 lines
2.2 KiB
Text
Raw Normal View History

asus-me176c: upgrade mainline kernel to 5.4.17 (LTS) (!922)
2020-02-02 13:49:05 +00:00
# Maintainer: Minecrell <minecrell@minecrell.net>
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
# Kernel config based on: https://github.com/me176c-dev/archlinux-me176c/blob/master/linux-me176c/config
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
_flavor="asus-me176c"
*: 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-$_flavor
community/linux-asus-me176c: upgrade to 5.4.197 (MR 3195) The new linux-edge / 5.18 kernel will likely not make it in time for the v22.06 release so let's upgrade the good old 5.4 kernel to the latest stable release at least.
2022-06-06 08:11:27 +00:00
pkgver=5.4.197
asus-me176c: upgrade mainline kernel to 5.4.20, enable Anbox options (!942) The patch set for asus-me176c is really small at this point, and there is no need to make a new tag for each minor kernel update. Usually the previous patch set will still apply correctly. Refactor the APKBUILD to build the kernel similar to linux-lts in Alpine, and use the original kernel tarball together with a small patch file on top. Also enable Android-related options in the kernel so we can test Anbox on asus-me176c.
2020-02-10 12:33:06 +00:00
_kernver=${pkgver%.*}
_me176cver=5.4.17
community/linux-asus-me176c: upgrade to 5.4.159 (MR 2685) [ci:skip-build]: already built successfully in CI
2021-11-15 14:56:11 +00:00
pkgrel=0
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
pkgdesc="Mainline kernel fork for ASUS MeMO Pad 7 (ME176C(X))"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
arch="x86_64"
_carch="x86_64"
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
url="https://github.com/me176c-dev/linux-me176c"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
license="GPL-2.0-only"
linux-asus-me176c: add kconfig check for nftables (MR 2060)
2021-03-30 23:43:54 +00:00
options="!strip !check !tracedeps pmb:cross-native pmb:kconfigcheck-anbox
pmb:kconfigcheck-nftables"
linux-asus-me176c: switch to installkernel-pmos (MR 2586) [ci:skip-build] Will never finish in time
2021-10-12 12:29:33 +00:00
makedepends="
bison
diffutils
elfutils-dev
flex
gmp-dev
linux-headers
mpc1-dev
mpfr-dev
openssl-dev
perl
postmarketos-installkernel
xz
"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
# Source
source="
asus-me176c: upgrade mainline kernel to 5.4.20, enable Anbox options (!942) The patch set for asus-me176c is really small at this point, and there is no need to make a new tag for each minor kernel update. Usually the previous patch set will still apply correctly. Refactor the APKBUILD to build the kernel similar to linux-lts in Alpine, and use the original kernel tarball together with a small patch file on top. Also enable Android-related options in the kernel so we can test Anbox on asus-me176c.
2020-02-10 12:33:06 +00:00
https://cdn.kernel.org/pub/linux/kernel/v${pkgver%%.*}.x/linux-$_kernver.tar.xz
linux-$pkgver.patch.xz::https://cdn.kernel.org/pub/linux/kernel/v${pkgver%%.*}.x/patch-$pkgver.xz
https://github.com/me176c-dev/linux-me176c/releases/download/$_me176cver/linux-me176c-$_me176cver.patch.xz
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
config-$_flavor.$arch
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
"
asus-me176c: upgrade mainline kernel to 5.4.20, enable Anbox options (!942) The patch set for asus-me176c is really small at this point, and there is no need to make a new tag for each minor kernel update. Usually the previous patch set will still apply correctly. Refactor the APKBUILD to build the kernel similar to linux-lts in Alpine, and use the original kernel tarball together with a small patch file on top. Also enable Android-related options in the kernel so we can test Anbox on asus-me176c.
2020-02-10 12:33:06 +00:00
builddir="$srcdir/linux-$_kernver"
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
prepare() {
default_prepare
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
cp "$srcdir/config-$_flavor.$arch" .config
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
}
build() {
unset LDFLAGS
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION=$((pkgrel + 1 ))
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
}
package() {
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
mkdir -p "$pkgdir"/boot
make install modules_install \
ARCH="$_carch" \
INSTALL_PATH="$pkgdir"/boot \
community/linux-asus-me176c: upgrade to 5.4.107 (MR 2047)
2021-03-20 16:38:24 +00:00
INSTALL_MOD_PATH="$pkgdir" \
INSTALL_MOD_STRIP=1
asus-me176c: rework packages (!699) device/device-asus-me176c: - Install me176c-factory to apply correct MAC addresses for WiFi and BT - Use FAT32 for boot partition. This allows flashing the boot partition directly as ESP (EFI System Partition). - Overall cleanup device/linux-asus-me176c: - Update kernel fork to 4.19.80 - Cleanup APKBUILD - Stop building patched ACPI DSDT table directly into kernel firmware/firmware-asus-me176c: - Package WiFi firmware firmware/firmware-asus-me176c-acpi: - New package for the patched ACPI DSDT table -> Separate from firmware-asus-me176c because it is always required, (not optional) [ci:skip-build]: runs into timeout
2019-10-10 17:10:11 +00:00
rm -f "$pkgdir"/lib/modules/*/build "$pkgdir"/lib/modules/*/source
install -D "$builddir"/include/config/kernel.release \
"$pkgdir"/usr/share/kernel/$_flavor/kernel.release
New device: asus-me176cx (Asus MeMo Pad 7) (!123) Use upstream Linux with patches, which are needed for a lot of things. lambdadroid said he will upstream some of them, but the battery driver would need to be written from scratch, which is apparentely non-trivial. [skip ci]: kernel doesn't build under one hour (maybe too many modules are selected), but it does build eventually
2018-12-31 19:44:13 +00:00
}
community/linux-asus-me176c: upgrade to 5.4.159 (MR 2685) [ci:skip-build]: already built successfully in CI
2021-11-15 14:56:11 +00:00
sha512sums="
9f60f77e8ab972b9438ac648bed17551c8491d6585a5e85f694b2eaa4c623fbc61eb18419b2656b6795eac5deec0edaa04547fc6723fbda52256bd7f3486898f linux-5.4.tar.xz
community/linux-asus-me176c: upgrade to 5.4.197 (MR 3195) The new linux-edge / 5.18 kernel will likely not make it in time for the v22.06 release so let's upgrade the good old 5.4 kernel to the latest stable release at least.
2022-06-06 08:11:27 +00:00
74d40207bec5273988759660cee5d5ed4fdd993ca92027a726d4d4f45a23c2c86f4a42fc060af8bcf2a367cab8c17f19eccb85c7f473e11bae6c5cac405c32dc linux-5.4.197.patch.xz
asus-me176c: upgrade mainline kernel to 5.4.20, enable Anbox options (!942) The patch set for asus-me176c is really small at this point, and there is no need to make a new tag for each minor kernel update. Usually the previous patch set will still apply correctly. Refactor the APKBUILD to build the kernel similar to linux-lts in Alpine, and use the original kernel tarball together with a small patch file on top. Also enable Android-related options in the kernel so we can test Anbox on asus-me176c.
2020-02-10 12:33:06 +00:00
aa462bfcbba87469a617e2ffd4058cd41137b74f836aae47ac89bc70de2836b8f3ddce94f597e61bb287eb009bb71f4e831c487b0073011673d5db4a8d8ae080 linux-me176c-5.4.17.patch.xz
community/linux-asus-me176c: fix build by updating kernel config Run "pmbootstrap kconfig migrate asus-me176c" to update the kernel config for the new Linux version. Otherwise there is an interactive prompt that times out on BPO (although it succeeds on GitLab CI for some strange reason).
2022-06-07 17:40:27 +00:00
c4ad6bfb37990a51ee83b8791bc6f9fb47ccd566de0282deb595a00d9a4787e13e1a01810212a966e3e8090c61bd513869af346704b8c2f22c7bbeea5e8eada4 config-asus-me176c.x86_64
community/linux-asus-me176c: upgrade to 5.4.159 (MR 2685) [ci:skip-build]: already built successfully in CI
2021-11-15 14:56:11 +00:00
"
Reference in a new issue Copy permalink