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

55 lines
2.2 KiB
Text
Raw Normal View History

Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
# Kernel config based on: arch/arm/configs/kminilte_00_defconfig
*: 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-samsung-kminilte
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
pkgver=3.4.113
*/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 support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
pkgdesc="Samsung Galaxy S5 Mini kernel fork"
samsung-kminilte: change arch to armv7 (!1130) - disable CONFIG_CRYPTO_SHA256_ARM, since it causes the build to fail with: arch/arm/crypto/sha256-core.S:1831: Error: thumb conditional instruction should be in IT block
2020-04-06 14:23:55 +00:00
arch="armv7"
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
_carch="arm"
_flavor="samsung-kminilte"
url="https://github.com/cm-3470/android_kernel_samsung_kminilte"
license="GPL2"
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"
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"
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 support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
# Source
_repository="android_kernel_samsung_kminilte"
_commit="7a8c010f226189116dcf2301d338555ae0d270c3"
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"
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +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/cm-3470/$_repository/archive/$_commit.tar.gz
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
$_config
linux-samsung-kminilte: add flashlight support (MR 1150) These changes enable the flashlight LED driver (fled_rt5033), and add support for switching the light on and off from userspace. In more detail: * CONFIG_FLED_RT5033 enables the flashlight driver * CONFIG_VIDEO_EXYNOS_FIMC_IS is required for the flashlight driver to compile (there seems to be a lot of cross-dependency between the two drivers) * patch 0001 fixes the use of usleep (which no longer exists), to make the kernel compile with those settings With these changes, /sys/class/flashlight/rt-flash-led shows up in sysfs, but it's only possible to control the brightness of the LED, not to switch it on. Patch 0002 is what actually makes the flashlight usable: it makes the /sys/class/flashlight/rt-flash-led/mode file writable. Writing "Torch" there enables the flashlight, writing "Off" disables it again. "Mixed" mode works like "Torch" as well. I have not figured out yet how to trigger the camera flash, so setting the mode to "Flash" is possible, albeit pointless.
2020-04-12 18:46:22 +00:00
0001-drivers-leds-rt5033_fled-fix-use-of-usleep.patch
0002-drivers-leds-flashlight-add-support-for-setting-mode.patch
"
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"
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +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 support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
}
package() {
device/linux-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
Add support for the Samsung Galaxy S5 Mini (kminilte) (#1467)
2018-05-05 20:29:02 +00:00
}
sha512sums="351b043822d9fc25a002f07a490422341fd03671d661bb949085ef8d69042f1ae528f80ade7076aba3eaffec80f65c09fdbb600ffe04063c69d876c22a53709b linux-samsung-kminilte-7a8c010f226189116dcf2301d338555ae0d270c3.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
22485be5583ab10fa5c466758c7f3c2e31cc10979b53b4c2d7bf18c87303c4c7f009958857ff26f3b268553682a13bc3009f7ad27bc49eb163dbcbd4e03a5d9c config-samsung-kminilte.armv7
linux-samsung-kminilte: add flashlight support (MR 1150) These changes enable the flashlight LED driver (fled_rt5033), and add support for switching the light on and off from userspace. In more detail: * CONFIG_FLED_RT5033 enables the flashlight driver * CONFIG_VIDEO_EXYNOS_FIMC_IS is required for the flashlight driver to compile (there seems to be a lot of cross-dependency between the two drivers) * patch 0001 fixes the use of usleep (which no longer exists), to make the kernel compile with those settings With these changes, /sys/class/flashlight/rt-flash-led shows up in sysfs, but it's only possible to control the brightness of the LED, not to switch it on. Patch 0002 is what actually makes the flashlight usable: it makes the /sys/class/flashlight/rt-flash-led/mode file writable. Writing "Torch" there enables the flashlight, writing "Off" disables it again. "Mixed" mode works like "Torch" as well. I have not figured out yet how to trigger the camera flash, so setting the mode to "Flash" is possible, albeit pointless.
2020-04-12 18:46:22 +00:00
873e4ff64521f685b7948e7a55aba4a95e3c0086b54c8e1440f67630c49a6b17b10c71837ba44d0bdb9afb05ff3ee8c0c890f0053fb79cd733aa76aed53579c2 0001-drivers-leds-rt5033_fled-fix-use-of-usleep.patch
fb30ea67620fc0dae62943b512662e0f3a49b7509d5f3cddda4c1552fe365535ac414f4ae960356f18228ce49d5c362c512cec7a9b671ffe96408f91b1b9fdee 0002-drivers-leds-flashlight-add-support-for-setting-mode.patch"
Reference in a new issue Copy permalink