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

107 lines
3.7 KiB
Text
Raw Normal View History

device-huawei-y530: Modernize APKBUILD
2018-06-28 22:03:50 +00:00
# Reference: <https://postmarketos.org/devicepkg>
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
# Contributor: Alexey Min <alexey.min@gmail.com>
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
pkgname="device-samsung-klte"
pkgdesc="Samsung Galaxy S5"
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
pkgver=0.3
main/linux-postmarketos-qcom: rename to linux-postmarketos-qcom-msm8974 (!662) We have linux-postmarketos-qcom and linux-postmarketos-qcom-msm8916 now, which is quite confusing. linux-postmarketos-qcom was originally added for MSM8974 devices (e.g. Nexus 5) and its patches on top of mainline are therefore quite focused on MSM8974. linux-postmarketos-qcom-msm8916 on the other hand, has patches specific to MSM8916. The two packages do not have any patch in common, therefore merging the two would only cause signficiant overhead to coordinate testing for devices of the two SoCs. Therefore, it is better to keep them separate. To avoid confusion, rename linux-postmarketos-qcom to linux-postmarketos-qcom-msm8974 to make it clear that it is really a close-to-mainline kernel for MSM8974 devices. [ci:skip-build]: already built successfully in CI
2019-10-05 14:09:52 +00:00
pkgrel=2
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
url="https://postmarketos.org"
license="MIT"
samsung-klte: Switch to armv7 (!272) Tested. Works fine on klte. Boots to weston. [ci:skip-build]: already built successfully
2019-03-11 08:41:05 +00:00
arch="armv7"
device-*: don't use noarch anymore Use the device's architecture instead of noarch. Because the device packages should never be built for other architectures, even if all depends can be built for other arches as well. This simplifies package building as part of the new build infrastructure effort. pmbootstrap has also been changed to output this by default in aportgen.
2018-11-07 06:45:58 +00:00
options="!check !archcheck"
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
depends="postmarketos-base mkbootimg msm-fb-refresher"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
makedepends="devicepkg-dev"
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
subpackages="
$pkgname-kernel-downstream:kernel_downstream
$pkgname-kernel-mainline:kernel_mainline
samsung-klte: add nonfree_firmware() to device package (!327)
2019-04-19 12:40:44 +00:00
$pkgname-nonfree-firmware:nonfree_firmware
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
$pkgname-nonfree-userland:nonfree_userland
$pkgname-hybris:hybris
$pkgname-hybris-x11:hybris_x11
"
source="
deviceinfo
fstab.android
set-brightness
battery-status
70-klte-android.rules
NetworkManager-klte.conf
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
kernel_downstream() {
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
pkgdesc="Display, touchscreen, Wi-Fi works (see device table for details)"
depends="linux-samsung-klte firmware-samsung-klte"
install="$pkgname-kernel-downstream.post-install"
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
# Disable v4l udev rules (video4linux), because without the camera
# firmware blobs this makes udev helper hang (#1033)
mkdir -p "${subpkgdir}"/etc/udev/rules.d
ln -s /dev/null "${subpkgdir}"/etc/udev/rules.d/60-persistent-v4l.rules
# NetworkManager configuration - ignore unsupported devices for now and set default dhcp client
install -Dm644 "${startdir}/NetworkManager-klte.conf" \
"${subpkgdir}/etc/NetworkManager/conf.d/10-klte.conf"
# Extras, helper scripts that make life of developer/user easier
install -Dm755 "${startdir}/set-brightness" "${subpkgdir}/usr/bin/set-brightness"
install -Dm755 "${startdir}/battery-status" "${subpkgdir}/usr/bin/battery-status"
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
}
kernel_mainline() {
pkgdesc="For kernel development only (most features aren't working)"
main/linux-postmarketos-qcom: rename to linux-postmarketos-qcom-msm8974 (!662) We have linux-postmarketos-qcom and linux-postmarketos-qcom-msm8916 now, which is quite confusing. linux-postmarketos-qcom was originally added for MSM8974 devices (e.g. Nexus 5) and its patches on top of mainline are therefore quite focused on MSM8974. linux-postmarketos-qcom-msm8916 on the other hand, has patches specific to MSM8916. The two packages do not have any patch in common, therefore merging the two would only cause signficiant overhead to coordinate testing for devices of the two SoCs. Therefore, it is better to keep them separate. To avoid confusion, rename linux-postmarketos-qcom to linux-postmarketos-qcom-msm8974 to make it clear that it is really a close-to-mainline kernel for MSM8974 devices. [ci:skip-build]: already built successfully in CI
2019-10-05 14:09:52 +00:00
depends="linux-postmarketos-qcom-msm8974"
Add support to different deviceinfo variables in mainline/downstream subpackages
2018-10-15 19:54:15 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
[samsung-klte] Add mainline kernel (linux-postmarketos-qcom) (#1479) Changes: * device-samsung-klte with both downstream and mainline kernel subpackages * linux-postmarketos-qcom updated to last commit What works in mainline kernel: * internal SD card * volume and home key buttons * usb network
2018-05-13 19:47:32 +00:00
}
samsung-klte: add nonfree_firmware() to device package (!327)
2019-04-19 12:40:44 +00:00
nonfree_firmware() {
pkgdesc="Wifi firmware"
depends="firmware-samsung-klte"
mkdir "$subpkgdir"
}
samsung-klte: downstream: add android adaptation (!332) Lots of device-specific configurations: * android mount points and mounts * android groups and users (needed for udev rules) * android udev rules for platform devices (needed for android services to run) * NetworkManager device-specific config * wpa_supplicant device-specific config * device-specific openrc service for late initcalls to bring up Wi-Fi hardware * extra helper scripts to call logcat, set backlight brightness, get battery status, unlock kde screenlocker session * use kernel cmdline from downstream android to keep it as close to android as possible. Important for android in lxc container later
2019-06-02 02:49:02 +00:00
nonfree_userland() {
pkgdesc="Pulls libhybris (Android) hardware adaptation"
depends="$pkgname-hybris"
mkdir "$subpkgdir"
}
hybris () {
pkgdesc="libhybris (Android) hardware adaptation"
depends="hybris-base"
install="$pkgname-hybris.post-install"
mkdir "$subpkgdir"
# Android mounts (needed for loading firmware and configs from android container)
# Appended to fstab in post-install script
install -Dm644 "${startdir}/fstab.android" "${subpkgdir}/etc/fstab.android"
# Android udev rules, depend on android users and groups presence
install -Dm644 "${startdir}/70-klte-android.rules" \
"${subpkgdir}/etc/udev/rules.d/70-klte-android.rules"
}
hybris_x11() {
pkgdesc="x11 modules for libhybris adaptation"
depends="hybris-base-x11-caf"
install_if="$pkgname-hybris xorg-server"
mkdir "$subpkgdir"
}
sha512sums="334b57770c4b0e78e385b3c8a30eb4fad9eea88fed3ddbe7d82341b600feae5418feda6c3afc4ef57bb0a870996c4f249f449cced2a5d952da80158cd7e2c632 deviceinfo
35f3b120152ebe709e11cebc9ced03f21f52768d88bd68ed23ed864fe1dd3b63665c8f74575882e217dd8226ae5d260e5ad2045dc4ab2470c89185f19b81c4a7 fstab.android
f773a9792407c1ad96b11c6673093c9eeff7d538459b7772c5956760a8cbb4de8912b24c77e8812afe056db26fa3e29af09e2a3851828baa0b9a9986bf80790b set-brightness
66db173b9f1075a133efeea8bda94ef08089b7c15acbc1e3aefb9f8510daa7690a0ce2739d20647e096ba69940ac5c4c6699f3b032ec67609ca56f116bb25256 battery-status
a68734d3fe30695d5a9302c92327e8ca564a73d06f0de87371800d1bdf4c541c3721af380b8d44cfa0b4cc1dc8a71586aec3f00bb877ee9dc18f41ba34caaeff 70-klte-android.rules
device-samsung-klte: don't replace NM unmanaged devices (!434) Do not overwrite NM unmanaged devices, append instead. [ci:skip-build]: already built successfully in CI
2019-06-03 20:14:31 +00:00
3753dcd8c25cfbbdd8f087a3168537df1334f0d33f36bc8923ec3d225ceb88121aa8d1670d6c6a2baab3d7067c86a43571695ce22e3b47076f97fcb53d1d7e6f NetworkManager-klte.conf"
Reference in a new issue Copy permalink