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

87 lines
2.3 KiB
Text
Raw Normal View History

Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
# Maintainer: Thiago Foganholi <thiagaoplusplus@outlook.com>
main/linux-postmarketos-exynos4: add myself as co-maintainer (MR 2423) [ci:skip-build] already built successfully in CI
2021-08-13 11:23:45 +00:00
# Co-Maintainer: Newbyte <newbyte@disroot.org>
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
# Kernel config based on: arch/arm/configs/exynos_defconfig
pkgname=linux-postmarketos-exynos4
linux-postmarketos-exynos4: upgrade to 6.4.2 (MR 4241) [ci:skip-build]: already built successfully in CI
2023-07-08 20:28:04 +00:00
pkgver=6.4.2
{community,main}/*: enable USB_CONFIGFS_NCM (MR 4511) See also #1797 and !3670 [ci:skip-build] already built successfully in CI
2023-10-28 08:42:38 +00:00
pkgrel=2
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
pkgdesc="Mainline kernel fork for Samsung Exynos4 devices"
arch="armv7"
_carch="arm"
_flavor="${pkgname#linux-}"
linux-postmarketos-exynos4: upgrade to version 6.3-rc7 (MR 4018) And use gitlab.com/exynos4-mainline/linux as source so that we no longer have to carry all the patches in pmaports. [ci:skip-build]: Already built successfully in CI
2023-04-11 18:10:22 +00:00
url="https://gitlab.com/exynos4-mainline/linux"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
license="GPL-2.0-only"
linux-postmarketos-exynos4: enable nftables support (MR 2366) [ci:skip-build] too many changed kernels in series for CI to build
2021-07-19 21:31:42 +00:00
options="!strip !check !tracedeps
pmb:cross-native
device/{community,main}/*: migrate to pmb:kconfigcheck-community (MR 3422) Replace usages of pmb:kconfigcheck-* options with pmb:kconfigcheck-community which will be required for all devices in community/main category. This ensures more consistent features & behavior across devices.
2022-09-07 20:43:05 +00:00
pmb:kconfigcheck-community
linux-postmarketos-exynos4: enable nftables support (MR 2366) [ci:skip-build] too many changed kernels in series for CI to build
2021-07-19 21:31:42 +00:00
"
linux-postmarketos-exynos4: switch to installkernel-pmos (MR 2586)
2021-10-11 12:18:48 +00:00
makedepends="
linux-postmarketos-exynos4: update to 6.0.1 (MR 3522)
2022-10-11 11:30:55 +00:00
bash
linux-postmarketos-exynos4: switch to installkernel-pmos (MR 2586)
2021-10-11 12:18:48 +00:00
bison
busybox-static-armv7
findutils
flex
gmp-dev
mpc1-dev
mpfr-dev
openssl-dev
perl
postmarketos-installkernel
xz
"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
# Source
_config="config-$_flavor.$arch"
case $pkgver in
*.*.*) _kernver=${pkgver%.0};;
*.*) _kernver=$pkgver;;
esac
linux-postmarketos-exynos4: use tag instead of commit (MR 4270) I forgot to change this before merging. Commit remains the same, so package itself shouldn't change. Thus: [ci:skip-vercheck] [ci:skip-build]: already built successfully in CI
2023-07-22 06:46:15 +00:00
_tag="v${pkgver//_/-}-exynos4"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
source="
linux-postmarketos-exynos4: upgrade to version 6.3-rc7 (MR 4018) And use gitlab.com/exynos4-mainline/linux as source so that we no longer have to carry all the patches in pmaports. [ci:skip-build]: Already built successfully in CI
2023-04-11 18:10:22 +00:00
$pkgname-$_tag.tar.bz2::$url/-/archive/$_tag/linux-$_tag.tar.bz2
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
$_config
initramfs.list
init
"
linux-postmarketos-exynos4: upgrade to version 6.3-rc7 (MR 4018) And use gitlab.com/exynos4-mainline/linux as source so that we no longer have to carry all the patches in pmaports. [ci:skip-build]: Already built successfully in CI
2023-04-11 18:10:22 +00:00
builddir="$srcdir/linux-$_tag"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
prepare_isorec() {
# https://wiki.postmarketos.org/wiki/Boot_process#isorec
cp -v /usr/$(arch_to_hostspec $arch)/bin/busybox.static \
"$builddir"/usr/
cp -v "$srcdir"/init "$builddir"/usr/
cp -v "$srcdir"/initramfs.list "$builddir"/usr/
}
prepare() {
default_prepare
prepare_isorec
cp -v "$srcdir/$_config" .config
}
build() {
unset LDFLAGS
linux-postmarketos-exynos4: fix build with GCC 12 (MR 3389) [ci:skip-build]: already built successfully in CI
2022-08-27 09:34:02 +00:00
make ARCH="$_carch" CC="${CC:-gcc}" KCFLAGS="-Wno-array-bounds" \
linux-postmarketos-exynos4: upgrade to 6.3.5 (MR 4147) [ci:skip-build] already built successfully in CI
2023-06-04 08:21:06 +00:00
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
}
package() {
mkdir -p "$pkgdir"/boot
make zinstall modules_install dtbs_install \
ARCH="$_carch" \
INSTALL_MOD_STRIP=1 \
INSTALL_PATH="$pkgdir"/boot \
INSTALL_MOD_PATH="$pkgdir" \
linux-*: install dtbs to /boot/dtbs (MR 3254) [ci:ignore-count]: Too many packages probably [ci:skip-build]: No way this would finish in time
2022-07-30 18:11:01 +00:00
INSTALL_DTBS_PATH="$pkgdir/boot/dtbs"
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
install -D "$builddir"/include/config/kernel.release \
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
}
main/linux-postmarketos-exynos4: upgrade to 5.12.8 (MR 2209) Drop merged patches and add "ARM: dts: exynos: Disable unused camera input for I9100"
2021-05-31 18:39:37 +00:00
sha512sums="
linux-postmarketos-exynos4: use tag instead of commit (MR 4270) I forgot to change this before merging. Commit remains the same, so package itself shouldn't change. Thus: [ci:skip-vercheck] [ci:skip-build]: already built successfully in CI
2023-07-22 06:46:15 +00:00
23cdbf3ed735704ec14b5f032afd64b0200413c1d17d2917ffa9c11d6087d63830ddce38a2b3b6e70da55fe85265a0325f01f42092ac8a464c4bc9cdcfb773d7 linux-postmarketos-exynos4-v6.4.2-exynos4.tar.bz2
{community,main}/*: enable USB_CONFIGFS_NCM (MR 4511) See also #1797 and !3670 [ci:skip-build] already built successfully in CI
2023-10-28 08:42:38 +00:00
0da449ef706bda125b0a02aad217ad139b4b0a10654630e2e1f9bdcc18615c1e6b89e71008e0357907b79d209ed831d9306dfa255ba1d671ab6431a952113dcd config-postmarketos-exynos4.armv7
Add package main/linux-postmarketos-exynos4 (MR 1634) The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305, SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100) From this list, only the i9100 doesn't support the bootimg method. Because of this, this kernel package is using the isorec method for all the devices on the list. Additionally, for the midas devices, there is no problem with this because the boot.img file is, in fact, a copy of the kernel+initramfs on the pmos boot partition and what the isorec initramfs does is actually to load the initramfs on that partition directly (at least on my understanding).
2020-10-19 01:02:08 +00:00
aaff0332b90e1f9f62de1128cace934717336e54ab09de46477369fa808302482d97334e43a85ee8597c1bcab64d3484750103559fea2ce8cd51776156bf7591 initramfs.list
main/linux-postmarketos-exynos4: upgrade to 5.12.8 (MR 2209) Drop merged patches and add "ARM: dts: exynos: Disable unused camera input for I9100"
2021-05-31 18:39:37 +00:00
09f1f214a24300696809727a7b04378887c06ca6f40803ca51a12bf2176a360b2eb8632139d6a0722094e05cb2038bdb04018a1e3d33fc2697674552ade03bee init
"
Reference in a new issue Copy permalink