forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/main/linux-postmarketos-qcom-msm8916/config-postmarketos-qcom-msm8916.armv7

5450 lines
141 KiB
Text
Raw Normal View History

main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Automatically generated file; DO NOT EDIT.
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
# Linux/arm 5.7.1 Kernel Configuration
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6 (!1115) - Update to Linux 5.6 - Major improvements for Samsung Galaxy Tab 4 10.1 WiFi (samsung-matissevewifi) - Buttons - Accelerometer - Display - Touchscreen - Audio (Speaker is WIP) - Upstreamed some patches
2020-03-31 08:22:35 +00:00
# Compiler: armv7-alpine-linux-musleabihf-gcc (Alpine 9.3.0) 9.3.0
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
CONFIG_CC_IS_GCC=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6 (!1115) - Update to Linux 5.6 - Major improvements for Samsung Galaxy Tab 4 10.1 WiFi (samsung-matissevewifi) - Buttons - Accelerometer - Display - Touchscreen - Audio (Speaker is WIP) - Upstreamed some patches
2020-03-31 08:22:35 +00:00
CONFIG_GCC_VERSION=90300
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_LD_VERSION=234000000
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_CLANG_VERSION=0
CONFIG_CC_HAS_ASM_GOTO=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_IRQ_WORK=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_BUILDTIME_TABLE_SORT=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION="-postmarketos-qcom-msm8916"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not set
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y
CONFIG_GENERIC_IRQ_MIGRATION=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_IRQ_MSI_IOMMU=y
CONFIG_HANDLE_DOMAIN_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_GENERIC_IRQ_MULTI_HANDLER=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
CONFIG_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_SCHED_AVG_IRQ=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SCHED_THERMAL_PRESSURE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_TREE_RCU=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_PREEMPT_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
# end of RCU Subsystem
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
CONFIG_GENERIC_SCHED_CLOCK=y
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_MEMCG_KMEM=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_CGROUP_PIDS=y
# CONFIG_CGROUP_RDMA is not set
# CONFIG_CGROUP_FREEZER is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
# CONFIG_BOOT_CONFIG is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SYSFS_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_IO_URING=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_BPF_SYSCALL is not set
# CONFIG_USERFAULTFD is not set
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_RSEQ=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
CONFIG_SLUB_CPU_PARTIAL=y
CONFIG_SYSTEM_DATA_VERIFICATION=y
CONFIG_PROFILING=y
# end of General setup
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=2
#
# System Type
#
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_OMAP1 is not set
#
# Multiple platform selection
#
#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not set
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_MULTI_V6_V7=y
# end of Multiple platform selection
# CONFIG_ARCH_VIRT is not set
# CONFIG_ARCH_ACTIONS is not set
# CONFIG_ARCH_ALPINE is not set
# CONFIG_ARCH_ARTPEC is not set
# CONFIG_ARCH_ASPEED is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_BCM is not set
# CONFIG_ARCH_BERLIN is not set
# CONFIG_ARCH_DIGICOLOR is not set
# CONFIG_ARCH_EXYNOS is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_HISI is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_KEYSTONE is not set
# CONFIG_ARCH_MEDIATEK is not set
# CONFIG_ARCH_MESON is not set
# CONFIG_ARCH_MILBEAUT is not set
# CONFIG_ARCH_MMP is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_ARCH_NPCM is not set
#
# TI OMAP/AM/DM/DRA Family
#
# CONFIG_ARCH_OMAP3 is not set
# CONFIG_ARCH_OMAP4 is not set
# CONFIG_SOC_OMAP5 is not set
# CONFIG_SOC_AM33XX is not set
# CONFIG_SOC_AM43XX is not set
# CONFIG_SOC_DRA7XX is not set
# end of TI OMAP/AM/DM/DRA Family
# CONFIG_ARCH_SIRF is not set
CONFIG_ARCH_QCOM=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_ARCH_IPQ40XX is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_ARCH_MSM8X60 is not set
# CONFIG_ARCH_MSM8960 is not set
# CONFIG_ARCH_MSM8974 is not set
CONFIG_ARCH_MSM8916=y
# CONFIG_ARCH_MDM9615 is not set
# CONFIG_ARCH_RDA is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_ARCH_S5PV210 is not set
# CONFIG_ARCH_RENESAS is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_PLAT_SPEAR is not set
# CONFIG_ARCH_STI is not set
# CONFIG_ARCH_STM32 is not set
# CONFIG_ARCH_SUNXI is not set
# CONFIG_ARCH_TANGO is not set
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_UNIPHIER is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_VEXPRESS is not set
# CONFIG_ARCH_WM8850 is not set
# CONFIG_ARCH_ZX is not set
# CONFIG_ARCH_ZYNQ is not set
#
# Processor Type
#
CONFIG_CPU_V7=y
CONFIG_CPU_THUMB_CAPABLE=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
# CONFIG_ARM_LPAE is not set
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
CONFIG_ARM_VIRT_EXT=y
CONFIG_SWP_EMULATE=y
# CONFIG_CPU_BIG_ENDIAN is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_ICACHE_MISMATCH_WORKAROUND is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_CPU_SPECTRE=y
CONFIG_HARDEN_BRANCH_PREDICTOR=y
CONFIG_KUSER_HELPERS=y
CONFIG_VDSO=y
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_CACHE_L2X0=y
# CONFIG_CACHE_L2X0_PMU is not set
# CONFIG_PL310_ERRATA_588369 is not set
# CONFIG_PL310_ERRATA_727915 is not set
# CONFIG_PL310_ERRATA_753970 is not set
# CONFIG_PL310_ERRATA_769419 is not set
CONFIG_ARM_L1_CACHE_SHIFT_6=y
CONFIG_ARM_L1_CACHE_SHIFT=6
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
CONFIG_ARM_HEAVY_MB=y
CONFIG_ARCH_SUPPORTS_BIG_ENDIAN=y
CONFIG_DEBUG_ALIGN_RODATA=y
# CONFIG_ARM_ERRATA_430973 is not set
CONFIG_ARM_ERRATA_643719=y
# CONFIG_ARM_ERRATA_720789 is not set
# CONFIG_ARM_ERRATA_754322 is not set
# CONFIG_ARM_ERRATA_754327 is not set
# CONFIG_ARM_ERRATA_764369 is not set
# CONFIG_ARM_ERRATA_775420 is not set
# CONFIG_ARM_ERRATA_798181 is not set
# CONFIG_ARM_ERRATA_773022 is not set
# CONFIG_ARM_ERRATA_818325_852422 is not set
# CONFIG_ARM_ERRATA_821420 is not set
# CONFIG_ARM_ERRATA_825619 is not set
# CONFIG_ARM_ERRATA_857271 is not set
# CONFIG_ARM_ERRATA_852421 is not set
# CONFIG_ARM_ERRATA_852423 is not set
# CONFIG_ARM_ERRATA_857272 is not set
# end of System Type
#
# Bus support
#
# CONFIG_ARM_ERRATA_814220 is not set
# end of Bus support
#
# Kernel Features
#
CONFIG_HAVE_SMP=y
CONFIG_SMP=y
CONFIG_SMP_ON_UP=y
CONFIG_ARM_CPU_TOPOLOGY=y
CONFIG_SCHED_MC=y
# CONFIG_SCHED_SMT is not set
CONFIG_HAVE_ARM_ARCH_TIMER=y
# CONFIG_MCPM is not set
# CONFIG_BIG_LITTLE is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_NR_CPUS=4
CONFIG_HOTPLUG_CPU=y
# CONFIG_ARM_PSCI is not set
CONFIG_ARCH_NR_GPIO=0
CONFIG_HZ_FIXED=0
# CONFIG_HZ_100 is not set
# CONFIG_HZ_200 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_500 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
# CONFIG_THUMB2_KERNEL is not set
CONFIG_ARM_PATCH_IDIV=y
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_HAVE_ARCH_PFN_VALID=y
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
CONFIG_CPU_SW_DOMAIN_PAN=y
CONFIG_HW_PERF_EVENTS=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ARM_MODULE_PLTS=y
CONFIG_FORCE_MAX_ZONEORDER=11
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
CONFIG_SECCOMP=y
# CONFIG_PARAVIRT is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
# CONFIG_XEN is not set
# end of Kernel Features
#
# Boot options
#
CONFIG_USE_OF=y
# CONFIG_ATAGS is not set
CONFIG_ZBOOT_ROM_TEXT=0
CONFIG_ZBOOT_ROM_BSS=0
# CONFIG_ARM_APPENDED_DTB is not set
CONFIG_CMDLINE=""
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_AUTO_ZRELADDR=y
# CONFIG_EFI is not set
# end of Boot options
#
# CPU Power Management
#
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#
CONFIG_CPUFREQ_DT=y
CONFIG_CPUFREQ_DT_PLATDEV=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_ARM_QCOM_CPUFREQ_NVMEM=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_ARM_QCOM_CPUFREQ_HW is not set
# CONFIG_QORIQ_CPUFREQ is not set
# end of CPU Frequency scaling
#
# CPU Idle
#
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
CONFIG_DT_IDLE_STATES=y
#
# ARM CPU Idle Drivers
#
# CONFIG_ARM_CPUIDLE is not set
CONFIG_ARM_QCOM_SPM_CPUIDLE=y
# end of ARM CPU Idle Drivers
# end of CPU Idle
# end of CPU Power Management
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
CONFIG_KERNEL_MODE_NEON=y
# end of Floating point emulation
#
# Power management options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATE_CALLBACKS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_APM_EMULATION is not set
CONFIG_PM_CLK=y
CONFIG_PM_GENERIC_DOMAINS=y
CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y
CONFIG_PM_GENERIC_DOMAINS_SLEEP=y
CONFIG_PM_GENERIC_DOMAINS_OF=y
CONFIG_CPU_PM=y
# CONFIG_ENERGY_MODEL is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARM_CPU_SUSPEND=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
# end of Power management options
#
# Firmware Drivers
#
# CONFIG_ARM_SCMI_PROTOCOL is not set
# CONFIG_ARM_SCPI_PROTOCOL is not set
# CONFIG_FW_CFG_SYSFS is not set
CONFIG_QCOM_SCM=y
# CONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT is not set
# CONFIG_TRUSTED_FOUNDATIONS is not set
CONFIG_HAVE_ARM_SMCCC=y
# CONFIG_GOOGLE_FIRMWARE is not set
#
# Tegra firmware driver
#
# end of Tegra firmware driver
# end of Firmware Drivers
CONFIG_ARM_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM=y
CONFIG_CRYPTO_SHA1_ARM_NEON=y
CONFIG_CRYPTO_SHA1_ARM_CE=y
CONFIG_CRYPTO_SHA2_ARM_CE=y
CONFIG_CRYPTO_SHA256_ARM=y
CONFIG_CRYPTO_SHA512_ARM=m
CONFIG_CRYPTO_AES_ARM=y
CONFIG_CRYPTO_AES_ARM_BS=y
CONFIG_CRYPTO_AES_ARM_CE=y
CONFIG_CRYPTO_GHASH_ARM_CE=y
CONFIG_CRYPTO_CRC32_ARM_CE=y
CONFIG_CRYPTO_CHACHA20_NEON=m
# CONFIG_CRYPTO_POLY1305_ARM is not set
CONFIG_CRYPTO_NHPOLY1305_NEON=m
# CONFIG_CRYPTO_CURVE25519_NEON is not set
#
# General architecture-dependent options
#
CONFIG_CRASH_CORE=y
CONFIG_KEXEC_CORE=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_IDLE_POLL_SETUP=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
CONFIG_ARCH_HAS_KEEPINITRD=y
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y
CONFIG_ARCH_32BIT_OFF_T=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_CLK=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_CC_HAS_STACKPROTECTOR_NONE=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS=8
CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.5-rc7 (!901) - Update to Linux 5.5-rc7 - Touchkey support for samsung-a5ulte/a3ulte/serranovelte [ci:skip-build]: already built successfully in CI
2020-01-21 10:39:18 +00:00
CONFIG_HAVE_COPY_THREAD_TLS=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_OLD_SIGACTION=y
CONFIG_COMPAT_32BIT_TIME=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=y
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_STRICT_MODULE_RWX=y
CONFIG_ARCH_HAS_PHYS_TO_DMA=y
# CONFIG_LOCK_EVENT_COUNTS is not set
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
CONFIG_MODULE_SRCVERSION_ALL=y
# CONFIG_MODULE_SIG is not set
CONFIG_MODULE_COMPRESS=y
CONFIG_MODULE_COMPRESS_GZIP=y
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_BLK_SCSI_REQUEST=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_DEV_ZONED is not set
# CONFIG_BLK_DEV_THROTTLING is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set
CONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
# end of Partition Types
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_BLK_PM=y
#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_ASN1=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7 (MR 1284) - Update to Linux 5.7 - motorola-harpia: Add battery reporting - bq-paella: Add accelerometer/magnetometer/gyroscope - bq-paella: Expose touch key backlight as LED
2020-06-04 09:35:11 +00:00
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_FREEZER=y
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_ELF_FDPIC is not set
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
CONFIG_ARCH_HAS_BINFMT_FLAT=y
# CONFIG_BINFMT_FLAT is not set
CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_ARCH_KEEP_MEMBLOCK=y
CONFIG_MEMORY_ISOLATION=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PAGE_REPORTING is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_MIGRATION=y
CONFIG_CONTIG_ALLOC=y
CONFIG_BOUNCE=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not set
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set
CONFIG_CMA_AREAS=7
# CONFIG_ZPOOL is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSMALLOC is not set
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_IDLE_PAGE_TRACKING is not set
CONFIG_FRAME_VECTOR=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_BENCHMARK is not set
# end of Memory Management options
CONFIG_NET=y
CONFIG_NET_INGRESS=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
CONFIG_UNIX_SCM=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not set
# CONFIG_XFRM_USER is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
CONFIG_NET_IP_TUNNEL=m
# CONFIG_IP_MROUTE is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
CONFIG_NET_UDP_TUNNEL=m
# CONFIG_NET_FOU is not set
# CONFIG_NET_FOU_IP_TUNNELS is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_INET_TUNNEL=m
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=m
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_IPV6_ILA is not set
# CONFIG_IPV6_VTI is not set
CONFIG_IPV6_SIT=m
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_IPV6_SEG6_LWTUNNEL is not set
# CONFIG_IPV6_SEG6_HMAC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_IPV6_RPL_LWTUNNEL is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_NETLABEL is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_MPTCP is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NET_PTP_CLASSIFY=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc3 (!992) - Update to Linux 5.6-rc3 - Fix orientation on wileyfox-crackling (add mount-matrix) - Fix sound (workaround inexistent backward compatibility in alsa-lib...)
2020-02-25 15:02:07 +00:00
# CONFIG_BRIDGE_NETFILTER is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
# CONFIG_NETFILTER_NETLINK_ACCT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NETFILTER_NETLINK_OSF is not set
CONFIG_NF_CONNTRACK=m
CONFIG_NF_LOG_COMMON=m
# CONFIG_NF_LOG_NETDEV is not set
# CONFIG_NF_CONNTRACK_MARK is not set
# CONFIG_NF_CONNTRACK_ZONES is not set
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
# CONFIG_NF_CONNTRACK_TIMEOUT is not set
# CONFIG_NF_CONNTRACK_TIMESTAMP is not set
# CONFIG_NF_CONNTRACK_LABELS is not set
CONFIG_NF_CT_PROTO_DCCP=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CT_PROTO_UDPLITE=y
# CONFIG_NF_CONNTRACK_AMANDA is not set
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
# CONFIG_NF_CONNTRACK_SNMP is not set
# CONFIG_NF_CONNTRACK_PPTP is not set
# CONFIG_NF_CONNTRACK_SANE is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CONNTRACK_TFTP is not set
# CONFIG_NF_CT_NETLINK is not set
CONFIG_NF_NAT=m
CONFIG_NF_NAT_MASQUERADE=y
# CONFIG_NF_TABLES is not set
CONFIG_NETFILTER_XTABLES=m
#
# Xtables combined modules
#
# CONFIG_NETFILTER_XT_MARK is not set
# CONFIG_NETFILTER_XT_CONNMARK is not set
#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
# CONFIG_NETFILTER_XT_TARGET_HL is not set
# CONFIG_NETFILTER_XT_TARGET_HMARK is not set
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
# CONFIG_NETFILTER_XT_TARGET_LED is not set
CONFIG_NETFILTER_XT_TARGET_LOG=m
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
CONFIG_NETFILTER_XT_NAT=m
# CONFIG_NETFILTER_XT_TARGET_NETMAP is not set
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_REDIRECT is not set
CONFIG_NETFILTER_XT_TARGET_MASQUERADE=m
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
# CONFIG_NETFILTER_XT_TARGET_TPROXY is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
# CONFIG_NETFILTER_XT_MATCH_BPF is not set
# CONFIG_NETFILTER_XT_MATCH_CGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLABEL is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNMARK is not set
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
# CONFIG_NETFILTER_XT_MATCH_CPU is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DEVGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ECN is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_HELPER is not set
# CONFIG_NETFILTER_XT_MATCH_HL is not set
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
# CONFIG_NETFILTER_XT_MATCH_L2TP is not set
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_MAC is not set
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_NFACCT is not set
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
# CONFIG_NETFILTER_XT_MATCH_SOCKET is not set
# CONFIG_NETFILTER_XT_MATCH_STATE is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# end of Core Netfilter Configuration
# CONFIG_IP_SET is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
# CONFIG_NF_SOCKET_IPV4 is not set
# CONFIG_NF_TPROXY_IPV4 is not set
# CONFIG_NF_DUP_IPV4 is not set
# CONFIG_NF_LOG_ARP is not set
CONFIG_NF_LOG_IPV4=m
CONFIG_NF_REJECT_IPV4=m
CONFIG_IP_NF_IPTABLES=m
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_RPFILTER is not set
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_SYNPROXY is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_REDIRECT is not set
CONFIG_IP_NF_MANGLE=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_TARGET_ECN is not set
# CONFIG_IP_NF_TARGET_TTL is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_SECURITY is not set
# CONFIG_IP_NF_ARPTABLES is not set
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_SOCKET_IPV6 is not set
# CONFIG_NF_TPROXY_IPV6 is not set
# CONFIG_NF_DUP_IPV6 is not set
CONFIG_NF_REJECT_IPV6=m
CONFIG_NF_LOG_IPV6=m
CONFIG_IP6_NF_IPTABLES=m
# CONFIG_IP6_NF_MATCH_AH is not set
# CONFIG_IP6_NF_MATCH_EUI64 is not set
# CONFIG_IP6_NF_MATCH_FRAG is not set
# CONFIG_IP6_NF_MATCH_OPTS is not set
# CONFIG_IP6_NF_MATCH_HL is not set
# CONFIG_IP6_NF_MATCH_IPV6HEADER is not set
# CONFIG_IP6_NF_MATCH_MH is not set
# CONFIG_IP6_NF_MATCH_RPFILTER is not set
# CONFIG_IP6_NF_MATCH_RT is not set
# CONFIG_IP6_NF_MATCH_SRH is not set
# CONFIG_IP6_NF_TARGET_HL is not set
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
# CONFIG_IP6_NF_TARGET_SYNPROXY is not set
CONFIG_IP6_NF_MANGLE=m
# CONFIG_IP6_NF_RAW is not set
# CONFIG_IP6_NF_SECURITY is not set
CONFIG_IP6_NF_NAT=m
CONFIG_IP6_NF_TARGET_MASQUERADE=m
# CONFIG_IP6_NF_TARGET_NPT is not set
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m
# CONFIG_NF_CONNTRACK_BRIDGE is not set
# CONFIG_BRIDGE_NF_EBTABLES is not set
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_MRP=m
CONFIG_BRIDGE=m
CONFIG_BRIDGE_IGMP_SNOOPING=y
CONFIG_BRIDGE_VLAN_FILTERING=y
CONFIG_HAVE_NET_DSA=y
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not set
CONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_DNS_RESOLVER is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_NET_NSH is not set
# CONFIG_HSR is not set
# CONFIG_NET_SWITCHDEV is not set
# CONFIG_NET_L3_MASTER_DEV is not set
CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
# CONFIG_NET_NCSI is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
CONFIG_BPF_JIT=y
CONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# end of Network testing
# end of Networking options
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
CONFIG_BT=m
CONFIG_BT_BREDR=y
# CONFIG_BT_RFCOMM is not set
# CONFIG_BT_BNEP is not set
CONFIG_BT_HIDP=m
CONFIG_BT_HS=y
CONFIG_BT_LE=y
CONFIG_BT_LEDS=y
# CONFIG_BT_SELFTEST is not set
CONFIG_BT_DEBUGFS=y
#
# Bluetooth device drivers
#
CONFIG_BT_INTEL=m
CONFIG_BT_BCM=m
CONFIG_BT_RTL=m
CONFIG_BT_QCA=m
CONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTUSB_AUTOSUSPEND is not set
CONFIG_BT_HCIBTUSB_BCM=y
# CONFIG_BT_HCIBTUSB_MTK is not set
CONFIG_BT_HCIBTUSB_RTL=y
# CONFIG_BT_HCIBTSDIO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
# CONFIG_BT_ATH3K is not set
# CONFIG_BT_MTKSDIO is not set
# CONFIG_BT_MTKUART is not set
CONFIG_BT_QCOMSMD=m
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
CONFIG_NFC=m
# CONFIG_NFC_DIGITAL is not set
CONFIG_NFC_NCI=m
# CONFIG_NFC_NCI_SPI is not set
# CONFIG_NFC_NCI_UART is not set
# CONFIG_NFC_HCI is not set
#
# Near Field Communication (NFC) devices
#
# CONFIG_NFC_FDP is not set
# CONFIG_NFC_PN533_USB is not set
# CONFIG_NFC_PN533_I2C is not set
# CONFIG_NFC_PN532_UART is not set
# CONFIG_NFC_MRVL_USB is not set
# CONFIG_NFC_ST_NCI_I2C is not set
# CONFIG_NFC_ST_NCI_SPI is not set
CONFIG_NFC_NXP_NCI=m
CONFIG_NFC_NXP_NCI_I2C=m
CONFIG_NFC_S3FWRN5=m
CONFIG_NFC_S3FWRN5_I2C=m
# end of Near Field Communication (NFC) devices
# CONFIG_PSAMPLE is not set
# CONFIG_NET_IFE is not set
# CONFIG_LWTUNNEL is not set
CONFIG_DST_CACHE=y
CONFIG_GRO_CELLS=y
# CONFIG_FAILOVER is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_ETHTOOL_NETLINK=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_HAVE_EBPF_JIT=y
#
# Device Drivers
#
CONFIG_ARM_AMBA=y
CONFIG_HAVE_PCI=y
# CONFIG_PCI is not set
# CONFIG_PCCARD is not set
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS is not set
CONFIG_FW_CACHE=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=y
CONFIG_ALLOW_DEV_COREDUMP=y
CONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
CONFIG_GENERIC_CPU_AUTOPROBE=y
CONFIG_SOC_BUS=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_REGMAP_SPI=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_REGMAP_SPMI=y
CONFIG_REGMAP_MMIO=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
CONFIG_GENERIC_ARCH_TOPOLOGY=y
# end of Generic Driver Options
#
# Bus devices
#
# CONFIG_BRCMSTB_GISB_ARB is not set
# CONFIG_MOXTET is not set
# CONFIG_QCOM_EBI2 is not set
# CONFIG_SIMPLE_PM_BUS is not set
# CONFIG_VEXPRESS_CONFIG is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_MHI_BUS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Bus devices
# CONFIG_CONNECTOR is not set
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_KOBJ=y
CONFIG_OF_DYNAMIC=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_NET=y
CONFIG_OF_RESERVED_MEM=y
CONFIG_OF_RESOLVE=y
CONFIG_OF_OVERLAY=y
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_RBD is not set
#
# NVME Support
#
# CONFIG_NVME_FC is not set
# CONFIG_NVME_TARGET is not set
# end of NVME Support
#
# Misc devices
#
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_QCOM_COINCELL is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_QCOM_FASTRPC=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_XILINX_SDFEC is not set
# CONFIG_PVPANIC is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not set
#
# Intel MIC & related support
#
# CONFIG_VOP_BUS is not set
# end of Intel MIC & related support
# CONFIG_ECHO is not set
# CONFIG_MISC_RTSX_USB is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_UACCE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Misc devices
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_DH is not set
# end of SCSI device support
# CONFIG_ATA is not set
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BCACHE is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_UNSTRIPED is not set
CONFIG_DM_CRYPT=m
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_WRITECACHE is not set
# CONFIG_DM_ERA is not set
# CONFIG_DM_CLONE is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_RAID is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_DUST is not set
# CONFIG_DM_INIT is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_DM_SWITCH is not set
# CONFIG_DM_LOG_WRITES is not set
# CONFIG_DM_INTEGRITY is not set
# CONFIG_TARGET_CORE is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_WIREGUARD is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_EQUALIZER is not set
# CONFIG_NET_TEAM is not set
CONFIG_MACVLAN=m
CONFIG_MACVTAP=m
# CONFIG_IPVLAN is not set
CONFIG_VXLAN=m
# CONFIG_GENEVE is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_BAREUDP is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_GTP is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not set
CONFIG_TUN=m
CONFIG_TAP=m
# CONFIG_TUN_VNET_CROSS_LE is not set
CONFIG_VETH=m
# CONFIG_VIRTIO_NET is not set
# CONFIG_NLMON is not set
#
# Distributed Switch Architecture drivers
#
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=y
CONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_ALTERA_TSE is not set
CONFIG_NET_VENDOR_AMAZON=y
CONFIG_NET_VENDOR_AQUANTIA=y
CONFIG_NET_VENDOR_ARC=y
CONFIG_NET_VENDOR_AURORA=y
# CONFIG_AURORA_NB8800 is not set
CONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_SYSTEMPORT is not set
CONFIG_NET_VENDOR_CADENCE=y
# CONFIG_MACB is not set
CONFIG_NET_VENDOR_CAVIUM=y
CONFIG_NET_VENDOR_CIRRUS=y
# CONFIG_CS89x0 is not set
CONFIG_NET_VENDOR_CORTINA=y
# CONFIG_GEMINI_ETHERNET is not set
# CONFIG_DM9000 is not set
# CONFIG_DNET is not set
CONFIG_NET_VENDOR_EZCHIP=y
# CONFIG_EZCHIP_NPS_MANAGEMENT_ENET is not set
CONFIG_NET_VENDOR_FARADAY=y
# CONFIG_FTMAC100 is not set
# CONFIG_FTGMAC100 is not set
CONFIG_NET_VENDOR_GOOGLE=y
CONFIG_NET_VENDOR_HISILICON=y
# CONFIG_HIX5HD2_GMAC is not set
# CONFIG_HISI_FEMAC is not set
# CONFIG_HIP04_ETH is not set
# CONFIG_HNS_DSAF is not set
# CONFIG_HNS_ENET is not set
CONFIG_NET_VENDOR_HUAWEI=y
CONFIG_NET_VENDOR_I825XX=y
CONFIG_NET_VENDOR_INTEL=y
CONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
CONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
CONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
CONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
# CONFIG_ENCX24J600 is not set
CONFIG_NET_VENDOR_MICROSEMI=y
CONFIG_NET_VENDOR_NATSEMI=y
CONFIG_NET_VENDOR_NETRONOME=y
CONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not set
CONFIG_NET_VENDOR_8390=y
# CONFIG_AX88796 is not set
# CONFIG_ETHOC is not set
CONFIG_NET_VENDOR_PENSANDO=y
CONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCA7000_SPI is not set
# CONFIG_QCA7000_UART is not set
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not set
CONFIG_NET_VENDOR_RENESAS=y
CONFIG_NET_VENDOR_ROCKER=y
CONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
CONFIG_NET_VENDOR_SEEQ=y
CONFIG_NET_VENDOR_SOLARFLARE=y
CONFIG_NET_VENDOR_SMSC=y
# CONFIG_SMC91X is not set
# CONFIG_SMC911X is not set
# CONFIG_SMSC911X is not set
CONFIG_NET_VENDOR_SOCIONEXT=y
CONFIG_NET_VENDOR_STMICRO=y
# CONFIG_STMMAC_ETH is not set
CONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not set
CONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not set
CONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_AXI_EMAC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_XILINX_LL_TEMAC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_MDIO_DEVICE is not set
# CONFIG_PHYLIB is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
CONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_RTL8152 is not set
# CONFIG_USB_LAN78XX is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not set
CONFIG_WLAN=y
CONFIG_WLAN_VENDOR_ADMTEK=y
CONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH9K is not set
# CONFIG_ATH9K_HTC is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_ATH10K is not set
CONFIG_WCN36XX=m
# CONFIG_WCN36XX_DEBUGFS is not set
CONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_AT76C50X_USB is not set
CONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not set
CONFIG_WLAN_VENDOR_CISCO=y
CONFIG_WLAN_VENDOR_INTEL=y
CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_P54_COMMON is not set
CONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
CONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x2U is not set
CONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not set
CONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8187 is not set
CONFIG_RTL_CARDS=m
# CONFIG_RTL8192CU is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not set
CONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not set
CONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not set
CONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
CONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not set
CONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
# CONFIG_WAN is not set
# CONFIG_NETDEVSIM is not set
# CONFIG_NET_FAILOVER is not set
# CONFIG_ISDN is not set
# CONFIG_NVM is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_LEDS=y
CONFIG_INPUT_FF_MEMLESS=y
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
# CONFIG_KEYBOARD_ATKBD is not set
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_OMAP4 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.5-rc7 (!901) - Update to Linux 5.5-rc7 - Touchkey support for samsung-a5ulte/a3ulte/serranovelte [ci:skip-build]: already built successfully in CI
2020-01-21 10:39:18 +00:00
CONFIG_KEYBOARD_TM2_TOUCHKEY=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CAP11XX is not set
# CONFIG_KEYBOARD_BCM is not set
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_PS2 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ADC is not set
# CONFIG_TOUCHSCREEN_AR1021_I2C is not set
CONFIG_TOUCHSCREEN_ATMEL_MXT=m
# CONFIG_TOUCHSCREEN_ATMEL_MXT_T37 is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8318 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
CONFIG_TOUCHSCREEN_MMS114=m
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not set
CONFIG_TOUCHSCREEN_ZINITIX=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_TOUCHSCREEN_HIMAX852X=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_ATMEL_CAPTOUCH is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_MSM_VIBRATOR is not set
CONFIG_INPUT_PM8941_PWRKEY=y
CONFIG_INPUT_PM8XXX_VIBRATOR=m
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_GP2A is not set
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_REGULATOR_HAPTIC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_INPUT_UINPUT=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_CMA3000 is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
CONFIG_RMI4_CORE=m
CONFIG_RMI4_I2C=m
# CONFIG_RMI4_SPI is not set
# CONFIG_RMI4_SMB is not set
# CONFIG_RMI4_F03 is not set
CONFIG_RMI4_2D_SENSOR=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_RMI4_F11=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_RMI4_F12=y
# CONFIG_RMI4_F30 is not set
# CONFIG_RMI4_F34 is not set
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set
#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports
# end of Input device support
#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=16
CONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_AMBA_PL010 is not set
# CONFIG_SERIAL_AMBA_PL011 is not set
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MSM=y
CONFIG_SERIAL_MSM_CONSOLE=y
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# CONFIG_SERIAL_ST_ASC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SERIAL_SPRD is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Serial drivers
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_NULL_TTY is not set
# CONFIG_TRACE_SINK is not set
# CONFIG_HVC_DCC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_SERIAL_DEV_BUS=y
CONFIG_SERIAL_DEV_CTRL_TTYPORT=y
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMB_DEVICE_INTERFACE is not set
CONFIG_HW_RANDOM=m
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_VIRTIO is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_XILLYBUS is not set
# end of Character devices
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_ARB_GPIO_CHALLENGE is not set
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_GPMUX is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_PINCTRL is not set
# CONFIG_I2C_MUX_REG is not set
# CONFIG_I2C_DEMUX_PINCTRL is not set
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
# CONFIG_I2C_EMEV2 is not set
CONFIG_I2C_GPIO=y
# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set
# CONFIG_I2C_NOMADIK is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
CONFIG_I2C_QUP=y
# CONFIG_I2C_RK3X is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# end of I2C Hardware Bus support
# CONFIG_I2C_STUB is not set
CONFIG_I2C_SLAVE=y
# CONFIG_I2C_SLAVE_EEPROM is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
CONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
CONFIG_SPI_BITBANG=m
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_FSL_SPI is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PL022 is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_QCOM_QSPI is not set
CONFIG_SPI_QUP=y
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=m
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
CONFIG_SPMI=y
CONFIG_SPMI_MSM_PMIC_ARB=y
# CONFIG_HSI is not set
CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_GPIO is not set
#
# PPS generators support
#
#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=y
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# end of PTP clock support
CONFIG_PINCTRL=y
CONFIG_GENERIC_PINCTRL_GROUPS=y
CONFIG_PINMUX=y
CONFIG_GENERIC_PINMUX_FUNCTIONS=y
CONFIG_PINCONF=y
CONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
# CONFIG_PINCTRL_AMD is not set
# CONFIG_PINCTRL_MCP23S08 is not set
CONFIG_PINCTRL_SINGLE=y
# CONFIG_PINCTRL_SX150X is not set
# CONFIG_PINCTRL_STMFX is not set
# CONFIG_PINCTRL_OCELOT is not set
CONFIG_PINCTRL_MSM=y
# CONFIG_PINCTRL_APQ8064 is not set
# CONFIG_PINCTRL_APQ8084 is not set
# CONFIG_PINCTRL_IPQ4019 is not set
# CONFIG_PINCTRL_IPQ8064 is not set
# CONFIG_PINCTRL_IPQ8074 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PINCTRL_IPQ6018 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_PINCTRL_MSM8660 is not set
# CONFIG_PINCTRL_MSM8960 is not set
# CONFIG_PINCTRL_MDM9615 is not set
# CONFIG_PINCTRL_MSM8X74 is not set
CONFIG_PINCTRL_MSM8916=y
# CONFIG_PINCTRL_MSM8976 is not set
# CONFIG_PINCTRL_MSM8994 is not set
# CONFIG_PINCTRL_MSM8996 is not set
# CONFIG_PINCTRL_MSM8998 is not set
# CONFIG_PINCTRL_QCS404 is not set
CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
# CONFIG_PINCTRL_QCOM_SSBI_PMIC is not set
# CONFIG_PINCTRL_SC7180 is not set
# CONFIG_PINCTRL_SDM660 is not set
# CONFIG_PINCTRL_SDM845 is not set
# CONFIG_PINCTRL_SM8150 is not set
# CONFIG_PINCTRL_EQUILIBRIUM is not set
CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
CONFIG_OF_GPIO=y
CONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
# CONFIG_GPIO_CADENCE is not set
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_FTGPIO010 is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_HLWD is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_GPIO_LOGICVC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_MPC8XXX is not set
# CONFIG_GPIO_PL061 is not set
# CONFIG_GPIO_SAMA5D2_PIOBU is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_GPIO_SIFIVE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_GPIO_SYSCON is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_ZEVIO is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_GW_PLD is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# CONFIG_HTC_EGPIO is not set
# end of MFD GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not set
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#
# end of USB GPIO expanders
# CONFIG_GPIO_MOCKUP is not set
# CONFIG_W1 is not set
CONFIG_POWER_AVS=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_QCOM_CPR=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_BRCMKONA is not set
# CONFIG_POWER_RESET_BRCMSTB is not set
# CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
CONFIG_POWER_RESET_MSM=y
CONFIG_POWER_RESET_QCOM_PON=y
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_RESTART is not set
# CONFIG_POWER_RESET_VERSATILE is not set
# CONFIG_POWER_RESET_SYSCON is not set
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not set
CONFIG_REBOOT_MODE=y
# CONFIG_SYSCON_REBOOT_MODE is not set
# CONFIG_NVMEM_REBOOT_MODE is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
CONFIG_DUMB_ADC_BATTERY=m
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_LEGO_EV3 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7 (MR 1284) - Update to Linux 5.7 - motorola-harpia: Add battery reporting - bq-paella: Add accelerometer/magnetometer/gyroscope - bq-paella: Expose touch key backlight as LED
2020-06-04 09:35:11 +00:00
CONFIG_BATTERY_MAX17042=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_MANAGER is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set
# CONFIG_CHARGER_QCOM_SMBB is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24190 is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_SMB347 is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
CONFIG_BATTERY_RT5033=m
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_UCS1002 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SENSORS_ADM1177 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_AS370 is not set
# CONFIG_SENSORS_ASC7621 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SENSORS_ASPEED is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FTSTEUTATES is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
# CONFIG_SENSORS_IIO_HWMON is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_POWR1220 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4260 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SENSORS_MAX31730 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SENSORS_MAX6621 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
# CONFIG_SENSORS_NCT6683 is not set
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
# CONFIG_SENSORS_OCC_P8_I2C is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_PWM_FAN is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_TMP513 is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_W83773G is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_STATISTICS is not set
CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_OF=y
# CONFIG_THERMAL_WRITABLE_TRIPS is not set
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
CONFIG_CPU_THERMAL=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_CPU_FREQ_THERMAL=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_CLOCK_THERMAL is not set
# CONFIG_DEVFREQ_THERMAL is not set
CONFIG_THERMAL_EMULATION=y
# CONFIG_THERMAL_MMIO is not set
# CONFIG_QORIQ_THERMAL is not set
# CONFIG_GENERIC_ADC_THERMAL is not set
#
# Qualcomm thermal drivers
#
CONFIG_QCOM_TSENS=y
CONFIG_QCOM_SPMI_TEMP_ALARM=m
# end of Qualcomm thermal drivers
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
# CONFIG_WATCHDOG_SYSFS is not set
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_ARM_SP805_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_FTWDT010_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_QCOM_WDT is not set
CONFIG_PM8916_WATCHDOG=y
# CONFIG_MEN_A21_WDT is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
# CONFIG_MFD_ACT8945A is not set
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_ATMEL_FLEXCOM is not set
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_MFD_IQS62X is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not set
# CONFIG_MFD_MAX77686 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_CPCAP is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_PM8XXX is not set
# CONFIG_MFD_QCOM_RPM is not set
CONFIG_MFD_SPMI_PMIC=y
CONFIG_MFD_RT5033=m
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK808 is not set
# CONFIG_MFD_RN5T618 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_SMSC is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not set
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_MFD_TQMX86 is not set
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_ROHM_BD718XX is not set
# CONFIG_MFD_ROHM_BD70528 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_MFD_ROHM_BD71828 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_MFD_STPMIC1 is not set
# CONFIG_MFD_STMFX is not set
# CONFIG_RAVE_SP_CORE is not set
# end of Multifunction device drivers
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_88PG86X is not set
# CONFIG_REGULATOR_ACT8865 is not set
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_DA9210 is not set
# CONFIG_REGULATOR_DA9211 is not set
# CONFIG_REGULATOR_FAN53555 is not set
# CONFIG_REGULATOR_GPIO is not set
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
# CONFIG_REGULATOR_LTC3676 is not set
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_MAX8973 is not set
# CONFIG_REGULATOR_MCP16502 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_REGULATOR_MP5416 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_REGULATOR_MP8859 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_REGULATOR_MP886X is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_REGULATOR_MPQ7920 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_REGULATOR_MT6311 is not set
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PV88060 is not set
# CONFIG_REGULATOR_PV88080 is not set
# CONFIG_REGULATOR_PV88090 is not set
# CONFIG_REGULATOR_PWM is not set
CONFIG_REGULATOR_QCOM_SMD_RPM=y
CONFIG_REGULATOR_QCOM_SPMI=y
CONFIG_REGULATOR_RT5033=m
# CONFIG_REGULATOR_SLG51000 is not set
# CONFIG_REGULATOR_SY8106A is not set
# CONFIG_REGULATOR_SY8824X is not set
# CONFIG_REGULATOR_TPS51632 is not set
# CONFIG_REGULATOR_TPS62360 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
# CONFIG_REGULATOR_TPS65132 is not set
# CONFIG_REGULATOR_TPS6524X is not set
# CONFIG_REGULATOR_VCTRL is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_REGULATOR_VQMMC_IPQ4019 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_CEC_CORE=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_RC_CORE is not set
CONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
# CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set
# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set
# CONFIG_MEDIA_RADIO_SUPPORT is not set
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_CEC_SUPPORT is not set
CONFIG_MEDIA_CONTROLLER=y
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_SUBDEV_API=y
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L2_I2C=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_V4L2_MEM2MEM_DEV=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_V4L2_FLASH_LED_CLASS=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_V4L2_FWNODE=m
#
# Media drivers
#
# CONFIG_MEDIA_USB_SUPPORT is not set
CONFIG_V4L_PLATFORM_DRIVERS=y
# CONFIG_VIDEO_CADENCE is not set
# CONFIG_VIDEO_ASPEED is not set
# CONFIG_VIDEO_MUX is not set
CONFIG_VIDEO_QCOM_CAMSS=m
# CONFIG_VIDEO_XILINX is not set
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_DEINTERLACE is not set
# CONFIG_VIDEO_SH_VEU is not set
CONFIG_VIDEO_QCOM_VENUS=m
# CONFIG_V4L_TEST_DRIVERS is not set
#
# Supported MMC/SDIO adapters
#
# CONFIG_CYPRESS_FIRMWARE is not set
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_V4L2=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_DMA_SG=m
#
# Media ancillary drivers (tuners, sensors, i2c, spi, frontends)
#
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
CONFIG_MEDIA_HIDE_ANCILLARY_SUBDRV=y
#
# I2C drivers hidden by 'Autoselect ancillary drivers'
#
#
# Audio decoders, processors and mixers
#
#
# RDS decoders
#
#
# Video decoders
#
#
# Video and audio decoders
#
#
# Video encoders
#
#
# Camera sensor devices
#
#
# Lens drivers
#
#
# Flash devices
#
#
# Video improvement chips
#
#
# Audio/Video compression chips
#
#
# SDR tuner chips
#
#
# Miscellaneous helper chips
#
#
# SPI drivers hidden by 'Autoselect ancillary drivers'
#
#
# Media SPI Adapters
#
# end of Media SPI Adapters
#
# DVB Frontend drivers hidden by 'Autoselect ancillary drivers'
#
#
# Tools to develop new frontends
#
#
# Graphics support
#
# CONFIG_IMX_IPUV3_CORE is not set
CONFIG_DRM=m
CONFIG_DRM_MIPI_DSI=y
# CONFIG_DRM_DP_AUX_CHARDEV is not set
# CONFIG_DRM_DEBUG_SELFTEST is not set
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_KMS_FB_HELPER=y
CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
# CONFIG_DRM_DP_CEC is not set
CONFIG_DRM_VM=y
#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_MALI_DISPLAY is not set
# CONFIG_DRM_KOMEDA is not set
# end of ARM devices
# CONFIG_DRM_VGEM is not set
# CONFIG_DRM_VKMS is not set
# CONFIG_DRM_EXYNOS is not set
# CONFIG_DRM_UDL is not set
# CONFIG_DRM_ARMADA is not set
# CONFIG_DRM_RCAR_DW_HDMI is not set
# CONFIG_DRM_RCAR_LVDS is not set
# CONFIG_DRM_OMAP is not set
# CONFIG_DRM_TILCDC is not set
# CONFIG_DRM_VIRTIO_GPU is not set
CONFIG_DRM_MSM=m
CONFIG_DRM_MSM_GPU_STATE=y
# CONFIG_DRM_MSM_REGISTER_LOGGING is not set
CONFIG_DRM_MSM_HDMI_HDCP=y
CONFIG_DRM_MSM_DSI=y
CONFIG_DRM_MSM_DSI_PLL=y
CONFIG_DRM_MSM_DSI_28NM_PHY=y
CONFIG_DRM_MSM_DSI_20NM_PHY=y
CONFIG_DRM_MSM_DSI_28NM_8960_PHY=y
CONFIG_DRM_MSM_DSI_14NM_PHY=y
CONFIG_DRM_MSM_DSI_10NM_PHY=y
# CONFIG_DRM_FSL_DCU is not set
# CONFIG_DRM_STM is not set
CONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_ARM_VERSATILE is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_PANEL_BOE_HIMAX8279D is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_PANEL_BOE_TV101WUM_NL6 is not set
CONFIG_DRM_PANEL_BOOYI_OTM1287=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_LVDS is not set
CONFIG_DRM_PANEL_SIMPLE=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_PANEL_ELIDA_KD35T133 is not set
# CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D is not set
# CONFIG_DRM_PANEL_ILITEK_IL9322 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9881C is not set
# CONFIG_DRM_PANEL_INNOLUX_P079ZCA is not set
# CONFIG_DRM_PANEL_JDI_LT070ME05000 is not set
# CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_SAMSUNG_LD9040 is not set
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_NEC_NL8048HL11 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_PANEL_NOVATEK_NT35510 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set
# CONFIG_DRM_PANEL_ORISETECH_OTM8009A is not set
# CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS is not set
# CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00 is not set
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM67191 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM68200 is not set
# CONFIG_DRM_PANEL_ROCKTECH_JH057N00900 is not set
# CONFIG_DRM_PANEL_RONBO_RB070D30 is not set
CONFIG_DRM_PANEL_SAMSUNG_EA8061V_AMS497EE01=m
# CONFIG_DRM_PANEL_SAMSUNG_S6D16D0 is not set
CONFIG_DRM_PANEL_SAMSUNG_S6D7AA0_LTL101AT01=m
# CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0 is not set
CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS427AP24=m
CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01=m
# CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6 (!1115) - Update to Linux 5.6 - Major improvements for Samsung Galaxy Tab 4 10.1 WiFi (samsung-matissevewifi) - Buttons - Accelerometer - Display - Touchscreen - Audio (Speaker is WIP) - Upstreamed some patches
2020-03-31 08:22:35 +00:00
CONFIG_DRM_PANEL_SAMSUNG_TC358764_LTL101AL06=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_SEIKO_43WVF1G is not set
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set
# CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set
# CONFIG_DRM_PANEL_SHARP_LS043T1LE01 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7789V is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_PANEL_SONY_ACX424AKP is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_DRM_PANEL_TIANMA_499=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_PANEL_TPO_TD028TTEC1 is not set
# CONFIG_DRM_PANEL_TPO_TD043MTEA1 is not set
# CONFIG_DRM_PANEL_TPO_TPG110 is not set
# CONFIG_DRM_PANEL_TRULY_NT35597_WQXGA is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_PANEL_XINPENG_XPP055C272 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_DRM_PANEL_YUSHUN_NT35520=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Display Panels
CONFIG_DRM_BRIDGE=y
CONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_CDNS_DSI is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_DRM_DISPLAY_CONNECTOR=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_LVDS_CODEC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set
# CONFIG_DRM_NXP_PTN3460 is not set
# CONFIG_DRM_PARADE_PS8622 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_PARADE_PS8640 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_SIL_SII8620 is not set
# CONFIG_DRM_SII902X is not set
# CONFIG_DRM_SII9234 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_SIMPLE_BRIDGE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_THINE_THC63LVD1024 is not set
# CONFIG_DRM_TOSHIBA_TC358764 is not set
# CONFIG_DRM_TOSHIBA_TC358767 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_TOSHIBA_TC358768 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DRM_TI_TFP410 is not set
# CONFIG_DRM_TI_SN65DSI86 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_TI_TPD12S015 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_DRM_I2C_ADV7511=m
CONFIG_DRM_I2C_ADV7511_AUDIO=y
CONFIG_DRM_I2C_ADV7511_CEC=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Display Interface Bridges
# CONFIG_DRM_STI is not set
# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_ARCPGU is not set
# CONFIG_DRM_MXSFB is not set
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_TINYDRM_ILI9486 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_PL111 is not set
# CONFIG_DRM_TVE200 is not set
# CONFIG_DRM_LIMA is not set
# CONFIG_DRM_PANFROST is not set
# CONFIG_DRM_MCDE is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DRM_TIDSS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_DRM_LEGACY=y
CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=m
#
# Frame buffer Devices
#
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#
# CONFIG_FB_ARMCLCD is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
CONFIG_FB_SIMPLE=y
# CONFIG_FB_SSD1307 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PWM=y
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
# CONFIG_BACKLIGHT_LED is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Backlight & LCD device support
CONFIG_VIDEOMODE_HELPERS=y
CONFIG_HDMI=y
#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
# CONFIG_LOGO is not set
# end of Graphics support
CONFIG_SOUND=m
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_PCM_ELD=y
CONFIG_SND_PCM_IEC958=y
CONFIG_SND_COMPRESS_OFFLOAD=m
CONFIG_SND_JACK=y
CONFIG_SND_JACK_INPUT_DEV=y
# CONFIG_SND_OSSEMUL is not set
CONFIG_SND_PCM_TIMER=y
# CONFIG_SND_HRTIMER is not set
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_MAX_CARDS=32
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_PROC_FS=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# HD-Audio
#
# end of HD-Audio
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_ARM=y
# CONFIG_SND_ARMAACI is not set
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_BCD2000 is not set
# CONFIG_SND_USB_POD is not set
# CONFIG_SND_USB_PODHD is not set
# CONFIG_SND_USB_TONEPORT is not set
# CONFIG_SND_USB_VARIAX is not set
CONFIG_SND_SOC=m
CONFIG_SND_SOC_COMPRESS=y
# CONFIG_SND_SOC_AMD_ACP is not set
# CONFIG_SND_ATMEL_SOC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SND_BCM63XX_I2S_WHISTLER is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_DESIGNWARE_I2S is not set
#
# SoC Audio for Freescale CPUs
#
#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# end of SoC Audio for Freescale CPUs
# CONFIG_SND_I2S_HI6210_I2S is not set
# CONFIG_SND_SOC_IMG is not set
# CONFIG_SND_SOC_MTK_BTCVSD is not set
CONFIG_SND_SOC_QCOM=m
CONFIG_SND_SOC_LPASS_CPU=m
CONFIG_SND_SOC_LPASS_PLATFORM=m
CONFIG_SND_SOC_LPASS_APQ8016=m
# CONFIG_SND_SOC_STORM is not set
CONFIG_SND_SOC_APQ8016_SBC=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.5-rc7 (!901) - Update to Linux 5.5-rc7 - Touchkey support for samsung-a5ulte/a3ulte/serranovelte [ci:skip-build]: already built successfully in CI
2020-01-21 10:39:18 +00:00
CONFIG_SND_SOC_QCOM_COMMON=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_SND_SOC_QDSP6_COMMON=m
CONFIG_SND_SOC_QDSP6_CORE=m
CONFIG_SND_SOC_QDSP6_AFE=m
CONFIG_SND_SOC_QDSP6_AFE_DAI=m
CONFIG_SND_SOC_QDSP6_ADM=m
CONFIG_SND_SOC_QDSP6_ROUTING=m
CONFIG_SND_SOC_QDSP6_ASM=m
CONFIG_SND_SOC_QDSP6_ASM_DAI=m
CONFIG_SND_SOC_QDSP6=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_SND_SOC_QDSP6_Q6VOICE_DAI=m
CONFIG_SND_SOC_QDSP6_Q6VOICE=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.5-rc7 (!901) - Update to Linux 5.5-rc7 - Touchkey support for samsung-a5ulte/a3ulte/serranovelte [ci:skip-build]: already built successfully in CI
2020-01-21 10:39:18 +00:00
CONFIG_SND_SOC_MSM8916_QDSP6=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_MSM8996 is not set
# CONFIG_SND_SOC_SOF_TOPLEVEL is not set
#
# STMicroelectronics STM32 SOC audio support
#
# end of STMicroelectronics STM32 SOC audio support
# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set
# CONFIG_SND_SOC_XILINX_SPDIF is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# CONFIG_ZX_TDM is not set
CONFIG_SND_SOC_I2C_AND_SPI=m
#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_ADAU7118_HW is not set
# CONFIG_SND_SOC_ADAU7118_I2C is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_SND_SOC_AW8738=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS42L42 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS53L30 is not set
# CONFIG_SND_SOC_CX2072X is not set
# CONFIG_SND_SOC_DA7213 is not set
# CONFIG_SND_SOC_DMIC is not set
CONFIG_SND_SOC_HDMI_CODEC=m
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not set
# CONFIG_SND_SOC_ES8316 is not set
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_GTM601 is not set
# CONFIG_SND_SOC_INNO_RK3036 is not set
# CONFIG_SND_SOC_MAX98088 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_SND_SOC_MAX98357A=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not set
# CONFIG_SND_SOC_MAX98927 is not set
# CONFIG_SND_SOC_MAX98373 is not set
# CONFIG_SND_SOC_MAX9860 is not set
CONFIG_SND_SOC_MSM8916_WCD_ANALOG=m
CONFIG_SND_SOC_MSM8916_WCD_DIGITAL=m
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RK3328 is not set
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not set
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS2562 is not set
# CONFIG_SND_SOC_TAS2770 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_SND_SOC_TFA9895=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SND_SOC_TLV320ADCX140 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_TS3A227E is not set
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_UDA1334 is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8904 is not set
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_WM8985 is not set
# CONFIG_SND_SOC_ZX_AUD96P22 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6358 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SND_SOC_MT6660 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8822 is not set
# CONFIG_SND_SOC_NAU8824 is not set
# CONFIG_SND_SOC_TPA6130A2 is not set
# end of CODEC drivers
# CONFIG_SND_SIMPLE_CARD is not set
# CONFIG_SND_AUDIO_GRAPH_CARD is not set
#
# HID support
#
CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=y
#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
# CONFIG_HID_ACCUTOUCH is not set
# CONFIG_HID_ACRUX is not set
CONFIG_HID_APPLE=y
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_ASUS is not set
# CONFIG_HID_AUREAL is not set
CONFIG_HID_BELKIN=y
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not set
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not set
# CONFIG_HID_PRODIKEYS is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CREATIVE_SB0540 is not set
CONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
CONFIG_HID_EZKEY=y
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_HID_GLORIOUS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_GT683R is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
CONFIG_HID_ITE=y
# CONFIG_HID_JABRA is not set
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=y
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LED is not set
# CONFIG_HID_LENOVO is not set
CONFIG_HID_LOGITECH=y
# CONFIG_HID_LOGITECH_HIDPP is not set
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
CONFIG_HID_REDRAGON=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTI is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_RETRODE is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
# CONFIG_HID_ALPS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_HID_MCP2221 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Special HID drivers
#
# USB HID support
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set
# end of USB HID support
#
# I2C HID support
#
CONFIG_I2C_HID=m
# end of I2C HID support
# end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_LED_TRIG=y
CONFIG_USB_ULPI_BUS=y
# CONFIG_USB_CONN_GPIO is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# CONFIG_USB_OTG_FSM is not set
# CONFIG_USB_LEDS_TRIGGER_USBPORT is not set
CONFIG_USB_AUTOSUSPEND_DELAY=2
# CONFIG_USB_MON is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
# CONFIG_USB_UAS is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_CDNS3 is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
CONFIG_USB_CHIPIDEA=y
CONFIG_USB_CHIPIDEA_OF=y
CONFIG_USB_CHIPIDEA_UDC=y
CONFIG_USB_CHIPIDEA_HOST=y
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_APPLE_MFI_FASTCHARGE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HUB_USB251XB is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_USB_HSIC_USB3503=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# CONFIG_USB_ULPI is not set
# end of USB Physical Layer drivers
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
#
# USB Peripheral Controller
#
# CONFIG_USB_FUSB300 is not set
# CONFIG_USB_FOTG210_UDC is not set
# CONFIG_USB_GR_UDC is not set
# CONFIG_USB_R8A66597 is not set
# CONFIG_USB_PXA27X is not set
# CONFIG_USB_MV_UDC is not set
# CONFIG_USB_MV_U3D is not set
# CONFIG_USB_SNP_UDC_PLAT is not set
# CONFIG_USB_M66592 is not set
# CONFIG_USB_BDC_UDC is not set
# CONFIG_USB_NET2272 is not set
# CONFIG_USB_GADGET_XILINX is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_USB_MAX3420_UDC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_USB_DUMMY_HCD is not set
# end of USB Peripheral Controller
CONFIG_USB_LIBCOMPOSITE=y
CONFIG_USB_U_ETHER=y
CONFIG_USB_F_RNDIS=y
CONFIG_USB_CONFIGFS=y
# CONFIG_USB_CONFIGFS_SERIAL is not set
# CONFIG_USB_CONFIGFS_ACM is not set
# CONFIG_USB_CONFIGFS_OBEX is not set
# CONFIG_USB_CONFIGFS_NCM is not set
# CONFIG_USB_CONFIGFS_ECM is not set
# CONFIG_USB_CONFIGFS_ECM_SUBSET is not set
CONFIG_USB_CONFIGFS_RNDIS=y
# CONFIG_USB_CONFIGFS_EEM is not set
# CONFIG_USB_CONFIGFS_MASS_STORAGE is not set
# CONFIG_USB_CONFIGFS_F_LB_SS is not set
# CONFIG_USB_CONFIGFS_F_FS is not set
# CONFIG_USB_CONFIGFS_F_UAC1 is not set
# CONFIG_USB_CONFIGFS_F_UAC1_LEGACY is not set
# CONFIG_USB_CONFIGFS_F_UAC2 is not set
# CONFIG_USB_CONFIGFS_F_MIDI is not set
# CONFIG_USB_CONFIGFS_F_HID is not set
# CONFIG_USB_CONFIGFS_F_UVC is not set
# CONFIG_USB_CONFIGFS_F_PRINTER is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
#
# USB Gadget precomposed configurations
#
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_NCM is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_MASS_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_ACM_MS is not set
# CONFIG_USB_G_MULTI is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not set
# CONFIG_USB_G_WEBCAM is not set
# CONFIG_USB_RAW_GADGET is not set
# end of USB Gadget precomposed configurations
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_TYPEC is not set
CONFIG_USB_ROLE_SWITCH=y
CONFIG_MMC=y
CONFIG_PWRSEQ_EMMC=y
CONFIG_PWRSEQ_SIMPLE=y
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=32
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_ARMMMCI is not set
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_IO_ACCESSORS=y
CONFIG_MMC_SDHCI_PLTFM=y
# CONFIG_MMC_SDHCI_OF_ARASAN is not set
# CONFIG_MMC_SDHCI_OF_ASPEED is not set
# CONFIG_MMC_SDHCI_OF_AT91 is not set
# CONFIG_MMC_SDHCI_OF_DWCMSHC is not set
# CONFIG_MMC_SDHCI_CADENCE is not set
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_SDHCI_MILBEAUT is not set
CONFIG_MMC_SDHCI_MSM=y
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_DW is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_MMC_CQHCI=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_MMC_HSQ is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not set
# CONFIG_MMC_SDHCI_OMAP is not set
# CONFIG_MMC_SDHCI_AM654 is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_LEDS_CLASS_FLASH=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_LEDS_AAT1290 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_AN30259A is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_LEDS_AS3645A is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
CONFIG_LEDS_AW2013=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_BCM6328 is not set
# CONFIG_LEDS_BCM6358 is not set
# CONFIG_LEDS_CR0014114 is not set
# CONFIG_LEDS_EL15203000 is not set
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_LM3692X is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_LEDS_LM3601X is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_PCA9532 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7.1 (MR 1295) We are in the midst of the Linux 5.8 merge window so there is no new -rc version to rebase on. -rc1 next week is also not the perfect choice for a release (first rc is usually still a bit unstable). On the other hand the changes that landed the last few days are quite nice and ready to go, so I decided to rebase on a stable kernel release (5.7.1). Not sure if I'm ever going to do this again :) Changes: - Update to Linux 5.7.1 - bq-paella: Add sound and modem - Enable some new kernel options for DB410c
2020-06-08 18:37:22 +00:00
CONFIG_LEDS_GPIO=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP5521 is not set
# CONFIG_LEDS_LP5523 is not set
# CONFIG_LEDS_LP5562 is not set
# CONFIG_LEDS_LP8501 is not set
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_LEDS_KTD2692 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LEDS_IS31FL319X is not set
# CONFIG_LEDS_IS31FL32XX is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
CONFIG_LEDS_QCOM_LPG=y
# CONFIG_LEDS_SYSCON is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_SPI_BYTE is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_LEDS_SGM3140=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_CPU=y
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
CONFIG_LEDS_TRIGGER_PANIC=y
# CONFIG_LEDS_TRIGGER_NETDEV is not set
# CONFIG_LEDS_TRIGGER_PATTERN is not set
# CONFIG_LEDS_TRIGGER_AUDIO is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
CONFIG_RTC_NVMEM=y
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12026 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF85363 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_RX6110 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
CONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_ZYNQMP is not set
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_PL030 is not set
# CONFIG_RTC_DRV_PL031 is not set
# CONFIG_RTC_DRV_CADENCE is not set
# CONFIG_RTC_DRV_FTRTC010 is not set
CONFIG_RTC_DRV_PM8XXX=y
# CONFIG_RTC_DRV_R7301 is not set
#
# HID Sensor RTC drivers
#
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
CONFIG_DMA_ENGINE=y
CONFIG_DMA_VIRTUAL_CHANNELS=y
CONFIG_DMA_OF=y
# CONFIG_ALTERA_MSGDMA is not set
# CONFIG_AMBA_PL08X is not set
# CONFIG_DW_AXI_DMAC is not set
# CONFIG_FSL_EDMA is not set
# CONFIG_FSL_QDMA is not set
# CONFIG_INTEL_IDMA64 is not set
# CONFIG_NBPFAXI_DMA is not set
# CONFIG_PL330_DMA is not set
CONFIG_QCOM_BAM_DMA=y
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not set
# CONFIG_DW_DMAC is not set
# CONFIG_SF_PDMA is not set
#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
#
# DMABUF options
#
CONFIG_SYNC_FILE=y
# CONFIG_SW_SYNC is not set
# CONFIG_UDMABUF is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_DMABUF_MOVE_NOTIFY is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DMABUF_SELFTESTS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DMABUF_HEAPS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of DMABUF options
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set
CONFIG_VIRTIO=y
CONFIG_VIRTIO_MENU=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_INPUT is not set
# CONFIG_VIRTIO_MMIO is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7_rc5 (MR 1228) - Update to Linux 5.7-rc5 - Add voice call audio - samsung-a3u/a5u: add speaker - wileyfox-crackling: add notification LED - bq-paella: add display, touchscreen, buttons - Initial support for Samsung Galaxy J5 (2015) (SM-J500FN) - Initial support for Samsung Galaxy J3 (2016) (SM-J320P)
2020-05-11 20:20:25 +00:00
# CONFIG_VDPA is not set
CONFIG_VHOST_DPN=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_VHOST_MENU=y
# CONFIG_VHOST_NET is not set
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Microsoft Hyper-V guest support
#
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_STAGING=y
# CONFIG_PRISM2_USB is not set
# CONFIG_COMEDI is not set
# CONFIG_RTLLIB is not set
# CONFIG_RTL8723BS is not set
# CONFIG_R8712U is not set
# CONFIG_R8188EU is not set
# CONFIG_VT6656 is not set
#
# IIO staging drivers
#
#
# Accelerometers
#
# CONFIG_ADIS16203 is not set
# CONFIG_ADIS16240 is not set
# end of Accelerometers
#
# Analog to digital converters
#
# CONFIG_AD7816 is not set
# CONFIG_AD7280 is not set
# end of Analog to digital converters
#
# Analog digital bi-direction converters
#
# CONFIG_ADT7316 is not set
# end of Analog digital bi-direction converters
#
# Capacitance to digital converters
#
# CONFIG_AD7150 is not set
# CONFIG_AD7746 is not set
# end of Capacitance to digital converters
#
# Direct Digital Synthesis
#
# CONFIG_AD9832 is not set
# CONFIG_AD9834 is not set
# end of Direct Digital Synthesis
#
# Network Analyzer, Impedance Converters
#
# CONFIG_AD5933 is not set
# end of Network Analyzer, Impedance Converters
#
# Active energy metering IC
#
# CONFIG_ADE7854 is not set
# end of Active energy metering IC
#
# Resolver to digital converters
#
# CONFIG_AD2S1210 is not set
# end of Resolver to digital converters
# end of IIO staging drivers
#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
# end of Speakup console speech
# CONFIG_STAGING_MEDIA is not set
#
# Android
#
CONFIG_ASHMEM=y
# CONFIG_ION is not set
# end of Android
# CONFIG_STAGING_BOARD is not set
# CONFIG_LTE_GDM724X is not set
# CONFIG_GS_FPGABOOT is not set
# CONFIG_UNISYSSPAR is not set
# CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set
# CONFIG_FB_TFT is not set
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not set
# CONFIG_KS7010 is not set
# CONFIG_PI433 is not set
#
# Gasket devices
#
# end of Gasket devices
# CONFIG_XIL_AXIS_FIFO is not set
# CONFIG_FIELDBUS_DEV is not set
# CONFIG_WFX is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_GOLDFISH is not set
# CONFIG_MFD_CROS_EC is not set
# CONFIG_CHROME_PLATFORMS is not set
# CONFIG_MELLANOX_PLATFORM is not set
CONFIG_CLKDEV_LOOKUP=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y
#
# Common Clock Framework
#
# CONFIG_CLK_HSDK is not set
# CONFIG_COMMON_CLK_MAX9485 is not set
# CONFIG_COMMON_CLK_SI5341 is not set
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI514 is not set
# CONFIG_COMMON_CLK_SI544 is not set
# CONFIG_COMMON_CLK_SI570 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CDCE925 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
# CONFIG_CLK_QORIQ is not set
# CONFIG_COMMON_CLK_PWM is not set
# CONFIG_COMMON_CLK_VC5 is not set
# CONFIG_COMMON_CLK_FIXED_MMIO is not set
CONFIG_QCOM_GDSC=y
CONFIG_QCOM_RPMCC=y
CONFIG_COMMON_CLK_QCOM=y
CONFIG_QCOM_A53PLL=y
CONFIG_QCOM_CLK_APCS_MSM8916=y
CONFIG_QCOM_CLK_SMD_RPM=y
# CONFIG_APQ_GCC_8084 is not set
# CONFIG_APQ_MMCC_8084 is not set
# CONFIG_IPQ_GCC_4019 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_IPQ_GCC_6018 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_IPQ_GCC_806X is not set
# CONFIG_IPQ_LCC_806X is not set
# CONFIG_IPQ_GCC_8074 is not set
# CONFIG_MSM_GCC_8660 is not set
CONFIG_MSM_GCC_8916=y
# CONFIG_MSM_GCC_8960 is not set
# CONFIG_MSM_LCC_8960 is not set
# CONFIG_MDM_GCC_9615 is not set
# CONFIG_MDM_LCC_9615 is not set
# CONFIG_MSM_MMCC_8960 is not set
# CONFIG_MSM_GCC_8974 is not set
# CONFIG_MSM_MMCC_8974 is not set
# CONFIG_MSM_GCC_8994 is not set
# CONFIG_MSM_GCC_8996 is not set
# CONFIG_MSM_MMCC_8996 is not set
# CONFIG_MSM_GCC_8998 is not set
# CONFIG_MSM_GPUCC_8998 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_MSM_MMCC_8998 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_QCS_GCC_404 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SC_DISPCC_7180 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SC_GCC_7180 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SC_GPUCC_7180 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SC_MSS_7180 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_SC_VIDEOCC_7180 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SDM_CAMCC_845 is not set
# CONFIG_SDM_GCC_660 is not set
# CONFIG_QCS_TURING_404 is not set
# CONFIG_QCS_Q6SSTOP_404 is not set
# CONFIG_SDM_GCC_845 is not set
# CONFIG_SDM_GPUCC_845 is not set
# CONFIG_SDM_VIDEOCC_845 is not set
# CONFIG_SDM_DISPCC_845 is not set
# CONFIG_SDM_LPASSCC_845 is not set
# CONFIG_SM_GCC_8150 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_SM_GCC_8250 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_SPMI_PMIC_CLKDIV is not set
# CONFIG_QCOM_HFPLL is not set
# CONFIG_KPSS_XCC is not set
# CONFIG_KRAITCC is not set
# end of Common Clock Framework
CONFIG_HWSPINLOCK=y
CONFIG_HWSPINLOCK_QCOM=y
#
# Clock Source drivers
#
CONFIG_TIMER_OF=y
CONFIG_TIMER_PROBE=y
CONFIG_ARM_ARCH_TIMER=y
CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_MICROCHIP_PIT64B is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Clock Source drivers
CONFIG_MAILBOX=y
# CONFIG_ARM_MHU is not set
# CONFIG_PLATFORM_MHU is not set
# CONFIG_PL320_MBOX is not set
# CONFIG_ALTERA_MBOX is not set
# CONFIG_MAILBOX_TEST is not set
CONFIG_QCOM_APCS_IPC=y
CONFIG_IOMMU_IOVA=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#
CONFIG_IOMMU_IO_PGTABLE=y
CONFIG_IOMMU_IO_PGTABLE_LPAE=y
# CONFIG_IOMMU_IO_PGTABLE_LPAE_SELFTEST is not set
# CONFIG_IOMMU_IO_PGTABLE_ARMV7S is not set
# end of Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
CONFIG_OF_IOMMU=y
CONFIG_IOMMU_DMA=y
# CONFIG_ARM_SMMU is not set
CONFIG_QCOM_IOMMU=y
#
# Remoteproc drivers
#
CONFIG_REMOTEPROC=y
CONFIG_QCOM_RPROC_COMMON=m
CONFIG_QCOM_Q6V5_COMMON=m
# CONFIG_QCOM_Q6V5_ADSP is not set
CONFIG_QCOM_Q6V5_MSS=m
# CONFIG_QCOM_Q6V5_PAS is not set
# CONFIG_QCOM_Q6V5_WCSS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_QCOM_Q6V5_IPA_NOTIFY=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_QCOM_SYSMON=m
CONFIG_QCOM_WCNSS_PIL=m
# end of Remoteproc drivers
#
# Rpmsg drivers
#
CONFIG_RPMSG=y
CONFIG_RPMSG_CHAR=y
CONFIG_RPMSG_QCOM_GLINK_NATIVE=m
# CONFIG_RPMSG_QCOM_GLINK_RPM is not set
CONFIG_RPMSG_QCOM_GLINK_SMEM=m
CONFIG_RPMSG_QCOM_SMD=y
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Aspeed SoC drivers
#
# end of Aspeed SoC drivers
#
# Broadcom SoC drivers
#
# CONFIG_SOC_BRCMSTB is not set
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_QUICC_ENGINE is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_FSL_RCPM is not set
# end of NXP/Freescale QorIQ SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Qualcomm SoC drivers
#
# CONFIG_QCOM_AOSS_QMP is not set
CONFIG_QCOM_COMMAND_DB=y
# CONFIG_QCOM_GENI_SE is not set
# CONFIG_QCOM_GLINK_SSR is not set
# CONFIG_QCOM_GSBI is not set
# CONFIG_QCOM_LLCC is not set
CONFIG_QCOM_MDT_LOADER=m
# CONFIG_QCOM_OCMEM is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_QCOM_PDR_HELPERS=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_QCOM_QMI_HELPERS=m
CONFIG_QCOM_RMTFS_MEM=m
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_QCOM_RPMPD=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_QCOM_SMEM=y
CONFIG_QCOM_SMD_RPM=y
CONFIG_QCOM_SMEM_STATE=y
CONFIG_QCOM_SMP2P=y
CONFIG_QCOM_SMSM=y
CONFIG_QCOM_SOCINFO=y
CONFIG_QCOM_WCNSS_CTRL=m
CONFIG_QCOM_APR=m
# end of Qualcomm SoC drivers
# CONFIG_SOC_TI is not set
#
# Xilinx SoC drivers
#
# CONFIG_XILINX_VCU is not set
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers
CONFIG_PM_DEVFREQ=y
#
# DEVFREQ Governors
#
CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=y
# CONFIG_DEVFREQ_GOV_PERFORMANCE is not set
# CONFIG_DEVFREQ_GOV_POWERSAVE is not set
# CONFIG_DEVFREQ_GOV_USERSPACE is not set
# CONFIG_DEVFREQ_GOV_PASSIVE is not set
#
# DEVFREQ Drivers
#
# CONFIG_PM_DEVFREQ_EVENT is not set
CONFIG_EXTCON=y
#
# Extcon Device Drivers
#
# CONFIG_EXTCON_ADC_JACK is not set
# CONFIG_EXTCON_FSA9480 is not set
# CONFIG_EXTCON_GPIO is not set
# CONFIG_EXTCON_MAX3355 is not set
# CONFIG_EXTCON_PTN5150 is not set
# CONFIG_EXTCON_QCOM_SPMI_MISC is not set
# CONFIG_EXTCON_RT8973A is not set
CONFIG_EXTCON_SM5502=y
CONFIG_EXTCON_USB_GPIO=y
CONFIG_MEMORY=y
# CONFIG_ARM_PL172_MPMC is not set
CONFIG_PL353_SMC=y
CONFIG_IIO=m
CONFIG_IIO_BUFFER=y
# CONFIG_IIO_BUFFER_CB is not set
# CONFIG_IIO_BUFFER_HW_CONSUMER is not set
CONFIG_IIO_KFIFO_BUF=m
CONFIG_IIO_TRIGGERED_BUFFER=m
# CONFIG_IIO_CONFIGFS is not set
CONFIG_IIO_TRIGGER=y
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_DEVICE is not set
# CONFIG_IIO_SW_TRIGGER is not set
#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
# CONFIG_ADIS16209 is not set
# CONFIG_ADXL345_I2C is not set
# CONFIG_ADXL345_SPI is not set
# CONFIG_ADXL372_SPI is not set
# CONFIG_ADXL372_I2C is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_BMA180=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_BMA220 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_BMA400 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_BMC150_ACCEL=m
CONFIG_BMC150_ACCEL_I2C=m
CONFIG_BMC150_ACCEL_SPI=m
# CONFIG_DA280 is not set
# CONFIG_DA311 is not set
# CONFIG_DMARD06 is not set
# CONFIG_DMARD09 is not set
# CONFIG_DMARD10 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6 (!1115) - Update to Linux 5.6 - Major improvements for Samsung Galaxy Tab 4 10.1 WiFi (samsung-matissevewifi) - Buttons - Accelerometer - Display - Touchscreen - Audio (Speaker is WIP) - Upstreamed some patches
2020-03-31 08:22:35 +00:00
CONFIG_IIO_ST_ACCEL_3AXIS=m
CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m
CONFIG_IIO_ST_ACCEL_SPI_3AXIS=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_KXSD9 is not set
# CONFIG_KXCJK1013 is not set
# CONFIG_MC3230 is not set
# CONFIG_MMA7455_I2C is not set
# CONFIG_MMA7455_SPI is not set
# CONFIG_MMA7660 is not set
# CONFIG_MMA8452 is not set
# CONFIG_MMA9551 is not set
# CONFIG_MMA9553 is not set
# CONFIG_MXC4005 is not set
# CONFIG_MXC6255 is not set
# CONFIG_SCA3000 is not set
# CONFIG_STK8312 is not set
# CONFIG_STK8BA50 is not set
# end of Accelerometers
#
# Analog to digital converters
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_AD7091R5 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_AD7124 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_AD7192 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_AD7266 is not set
# CONFIG_AD7291 is not set
# CONFIG_AD7292 is not set
# CONFIG_AD7298 is not set
# CONFIG_AD7476 is not set
# CONFIG_AD7606_IFACE_PARALLEL is not set
# CONFIG_AD7606_IFACE_SPI is not set
# CONFIG_AD7766 is not set
# CONFIG_AD7768_1 is not set
# CONFIG_AD7780 is not set
# CONFIG_AD7791 is not set
# CONFIG_AD7793 is not set
# CONFIG_AD7887 is not set
# CONFIG_AD7923 is not set
# CONFIG_AD7949 is not set
# CONFIG_AD799X is not set
# CONFIG_CC10001_ADC is not set
# CONFIG_ENVELOPE_DETECTOR is not set
# CONFIG_HI8435 is not set
# CONFIG_HX711 is not set
# CONFIG_INA2XX_ADC is not set
# CONFIG_LTC2471 is not set
# CONFIG_LTC2485 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_LTC2496 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_LTC2497 is not set
# CONFIG_MAX1027 is not set
# CONFIG_MAX11100 is not set
# CONFIG_MAX1118 is not set
# CONFIG_MAX1363 is not set
# CONFIG_MAX9611 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
# CONFIG_MCP3911 is not set
# CONFIG_NAU7802 is not set
CONFIG_QCOM_VADC_COMMON=m
# CONFIG_QCOM_SPMI_IADC is not set
CONFIG_QCOM_SPMI_VADC=m
# CONFIG_QCOM_SPMI_ADC5 is not set
# CONFIG_SD_ADC_MODULATOR is not set
# CONFIG_TI_ADC081C is not set
# CONFIG_TI_ADC0832 is not set
# CONFIG_TI_ADC084S021 is not set
# CONFIG_TI_ADC12138 is not set
# CONFIG_TI_ADC108S102 is not set
# CONFIG_TI_ADC128S052 is not set
# CONFIG_TI_ADC161S626 is not set
# CONFIG_TI_ADS1015 is not set
# CONFIG_TI_ADS7950 is not set
# CONFIG_TI_ADS8344 is not set
# CONFIG_TI_ADS8688 is not set
# CONFIG_TI_ADS124S08 is not set
# CONFIG_TI_TLC4541 is not set
# CONFIG_VF610_ADC is not set
# CONFIG_XILINX_XADC is not set
# end of Analog to digital converters
#
# Analog Front Ends
#
# CONFIG_IIO_RESCALE is not set
# end of Analog Front Ends
#
# Amplifiers
#
# CONFIG_AD8366 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_HMC425 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Amplifiers
#
# Chemical Sensors
#
# CONFIG_ATLAS_PH_SENSOR is not set
# CONFIG_BME680 is not set
# CONFIG_CCS811 is not set
# CONFIG_IAQCORE is not set
# CONFIG_PMS7003 is not set
# CONFIG_SENSIRION_SGP30 is not set
# CONFIG_SPS30 is not set
# CONFIG_VZ89X is not set
# end of Chemical Sensors
#
# Hid Sensor IIO Common
#
# end of Hid Sensor IIO Common
#
# SSP Sensor Common
#
# CONFIG_IIO_SSP_SENSORHUB is not set
# end of SSP Sensor Common
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6 (!1115) - Update to Linux 5.6 - Major improvements for Samsung Galaxy Tab 4 10.1 WiFi (samsung-matissevewifi) - Buttons - Accelerometer - Display - Touchscreen - Audio (Speaker is WIP) - Upstreamed some patches
2020-03-31 08:22:35 +00:00
CONFIG_IIO_ST_SENSORS_I2C=m
CONFIG_IIO_ST_SENSORS_SPI=m
CONFIG_IIO_ST_SENSORS_CORE=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Digital to analog converters
#
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5592R is not set
# CONFIG_AD5593R is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
# CONFIG_AD5686_SPI is not set
# CONFIG_AD5696_I2C is not set
# CONFIG_AD5755 is not set
# CONFIG_AD5758 is not set
# CONFIG_AD5761 is not set
# CONFIG_AD5764 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_AD5770R is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_AD5791 is not set
# CONFIG_AD7303 is not set
# CONFIG_AD8801 is not set
# CONFIG_DPOT_DAC is not set
# CONFIG_DS4424 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_LTC1660 is not set
# CONFIG_LTC2632 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_M62332 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4922 is not set
# CONFIG_TI_DAC082S085 is not set
# CONFIG_TI_DAC5571 is not set
# CONFIG_TI_DAC7311 is not set
# CONFIG_TI_DAC7612 is not set
# CONFIG_VF610_DAC is not set
# end of Digital to analog converters
#
# IIO dummy driver
#
# end of IIO dummy driver
#
# Frequency Synthesizers DDS/PLL
#
#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set
# end of Clock Generator/Distribution
#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF4350 is not set
# CONFIG_ADF4371 is not set
# end of Phase-Locked Loop (PLL) frequency synthesizers
# end of Frequency Synthesizers DDS/PLL
#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
# CONFIG_ADXRS450 is not set
CONFIG_BMG160=m
CONFIG_BMG160_I2C=m
CONFIG_BMG160_SPI=m
# CONFIG_FXAS21002C is not set
# CONFIG_MPU3050_I2C is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set
# end of Digital gyroscope sensors
#
# Health Sensors
#
#
# Heart Rate Monitors
#
# CONFIG_AFE4403 is not set
# CONFIG_AFE4404 is not set
# CONFIG_MAX30100 is not set
# CONFIG_MAX30102 is not set
# end of Heart Rate Monitors
# end of Health Sensors
#
# Humidity sensors
#
# CONFIG_AM2315 is not set
# CONFIG_DHT11 is not set
# CONFIG_HDC100X is not set
# CONFIG_HTS221 is not set
# CONFIG_HTU21 is not set
# CONFIG_SI7005 is not set
# CONFIG_SI7020 is not set
# end of Humidity sensors
#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16460 is not set
# CONFIG_ADIS16480 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7 (MR 1284) - Update to Linux 5.7 - motorola-harpia: Add battery reporting - bq-paella: Add accelerometer/magnetometer/gyroscope - bq-paella: Expose touch key backlight as LED
2020-06-04 09:35:11 +00:00
CONFIG_BMI160=m
CONFIG_BMI160_I2C=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_BMI160_SPI is not set
# CONFIG_FXOS8700_I2C is not set
# CONFIG_FXOS8700_SPI is not set
# CONFIG_KMX61 is not set
# CONFIG_INV_MPU6050_I2C is not set
# CONFIG_INV_MPU6050_SPI is not set
CONFIG_IIO_ST_LSM6DSX=m
CONFIG_IIO_ST_LSM6DSX_I2C=m
CONFIG_IIO_ST_LSM6DSX_SPI=m
# end of Inertial measurement units
#
# Light sensors
#
# CONFIG_ADJD_S311 is not set
# CONFIG_ADUX1020 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_AL3010 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_AL3320A is not set
# CONFIG_APDS9300 is not set
# CONFIG_APDS9960 is not set
# CONFIG_BH1750 is not set
# CONFIG_BH1780 is not set
# CONFIG_CM32181 is not set
# CONFIG_CM3232 is not set
# CONFIG_CM3323 is not set
# CONFIG_CM3605 is not set
# CONFIG_CM36651 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_GP2AP002 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_GP2AP020A00F is not set
# CONFIG_SENSORS_ISL29018 is not set
# CONFIG_SENSORS_ISL29028 is not set
# CONFIG_ISL29125 is not set
# CONFIG_JSA1212 is not set
# CONFIG_RPR0521 is not set
CONFIG_LTR501=m
# CONFIG_LV0104CS is not set
# CONFIG_MAX44000 is not set
# CONFIG_MAX44009 is not set
# CONFIG_NOA1305 is not set
# CONFIG_OPT3001 is not set
# CONFIG_PA12203001 is not set
# CONFIG_SI1133 is not set
# CONFIG_SI1145 is not set
# CONFIG_STK3310 is not set
# CONFIG_ST_UVIS25 is not set
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not set
# CONFIG_TSL2583 is not set
# CONFIG_TSL2772 is not set
# CONFIG_TSL4531 is not set
# CONFIG_US5182D is not set
# CONFIG_VCNL4000 is not set
# CONFIG_VCNL4035 is not set
# CONFIG_VEML6030 is not set
# CONFIG_VEML6070 is not set
# CONFIG_VL6180 is not set
# CONFIG_ZOPT2201 is not set
# end of Light sensors
#
# Magnetometer sensors
#
# CONFIG_AK8974 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7 (MR 1284) - Update to Linux 5.7 - motorola-harpia: Add battery reporting - bq-paella: Add accelerometer/magnetometer/gyroscope - bq-paella: Expose touch key backlight as LED
2020-06-04 09:35:11 +00:00
CONFIG_AK8975=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_AK09911 is not set
CONFIG_BMC150_MAGN=m
CONFIG_BMC150_MAGN_I2C=m
# CONFIG_BMC150_MAGN_SPI is not set
# CONFIG_MAG3110 is not set
# CONFIG_MMC35240 is not set
# CONFIG_IIO_ST_MAGN_3AXIS is not set
# CONFIG_SENSORS_HMC5843_I2C is not set
# CONFIG_SENSORS_HMC5843_SPI is not set
# CONFIG_SENSORS_RM3100_I2C is not set
# CONFIG_SENSORS_RM3100_SPI is not set
# end of Magnetometer sensors
#
# Multiplexers
#
# CONFIG_IIO_MUX is not set
# end of Multiplexers
#
# Inclinometer sensors
#
# end of Inclinometer sensors
#
# Triggers - standalone
#
# CONFIG_IIO_INTERRUPT_TRIGGER is not set
# CONFIG_IIO_SYSFS_TRIGGER is not set
# end of Triggers - standalone
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
#
# Linear and angular position sensors
#
# end of Linear and angular position sensors
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Digital potentiometers
#
# CONFIG_AD5272 is not set
# CONFIG_DS1803 is not set
# CONFIG_MAX5432 is not set
# CONFIG_MAX5481 is not set
# CONFIG_MAX5487 is not set
# CONFIG_MCP4018 is not set
# CONFIG_MCP4131 is not set
# CONFIG_MCP4531 is not set
# CONFIG_MCP41010 is not set
# CONFIG_TPL0102 is not set
# end of Digital potentiometers
#
# Digital potentiostats
#
# CONFIG_LMP91000 is not set
# end of Digital potentiostats
#
# Pressure sensors
#
# CONFIG_ABP060MG is not set
# CONFIG_BMP280 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_DLHL60D is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_DPS310 is not set
# CONFIG_HP03 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_ICP10100 is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL115_SPI is not set
# CONFIG_MPL3115 is not set
# CONFIG_MS5611 is not set
# CONFIG_MS5637 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set
# CONFIG_HP206C is not set
# CONFIG_ZPA2326 is not set
# end of Pressure sensors
#
# Lightning sensors
#
# CONFIG_AS3935 is not set
# end of Lightning sensors
#
# Proximity and distance sensors
#
# CONFIG_ISL29501 is not set
# CONFIG_LIDAR_LITE_V2 is not set
# CONFIG_MB1232 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_PING is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_RFD77402 is not set
# CONFIG_SRF04 is not set
# CONFIG_SX9500 is not set
# CONFIG_SRF08 is not set
# CONFIG_VL53L0X_I2C is not set
# end of Proximity and distance sensors
#
# Resolver to digital converters
#
# CONFIG_AD2S90 is not set
# CONFIG_AD2S1200 is not set
# end of Resolver to digital converters
#
# Temperature sensors
#
# CONFIG_LTC2983 is not set
# CONFIG_MAXIM_THERMOCOUPLE is not set
# CONFIG_MLX90614 is not set
# CONFIG_MLX90632 is not set
# CONFIG_TMP006 is not set
# CONFIG_TMP007 is not set
# CONFIG_TSYS01 is not set
# CONFIG_TSYS02D is not set
# CONFIG_MAX31856 is not set
# end of Temperature sensors
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PWM_DEBUG is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_PWM_FSL_FTM is not set
# CONFIG_PWM_PCA9685 is not set
#
# IRQ chip support
#
CONFIG_IRQCHIP=y
CONFIG_ARM_GIC=y
CONFIG_ARM_GIC_MAX_NR=1
# CONFIG_AL_FIC is not set
# CONFIG_QCOM_PDC is not set
# end of IRQ chip support
# CONFIG_IPACK_BUS is not set
CONFIG_RESET_CONTROLLER=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_RESET_BRCMSTB_RESCAL is not set
# CONFIG_RESET_INTEL_GW is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_RESET_QCOM_AOSS is not set
# CONFIG_RESET_QCOM_PDC is not set
# CONFIG_RESET_TI_SYSCON is not set
#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
# CONFIG_BCM_KONA_USB2_PHY is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PHY_CADENCE_TORRENT is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_PHY_CADENCE_DPHY is not set
# CONFIG_PHY_CADENCE_SIERRA is not set
# CONFIG_PHY_FSL_IMX8MQ_USB is not set
# CONFIG_PHY_MIXEL_MIPI_DPHY is not set
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
# CONFIG_PHY_CPCAP_USB is not set
# CONFIG_PHY_MAPPHONE_MDM6600 is not set
# CONFIG_PHY_OCELOT_SERDES is not set
# CONFIG_PHY_QCOM_APQ8064_SATA is not set
# CONFIG_PHY_QCOM_IPQ806X_SATA is not set
# CONFIG_PHY_QCOM_PCIE2 is not set
# CONFIG_PHY_QCOM_QMP is not set
# CONFIG_PHY_QCOM_QUSB2 is not set
# CONFIG_PHY_QCOM_UFS is not set
CONFIG_PHY_QCOM_USB_HS=y
# CONFIG_PHY_QCOM_USB_HSIC is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_PHY_QCOM_USB_HS_28NM is not set
# CONFIG_PHY_QCOM_USB_SS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_PHY_TUSB1210 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_PHY_INTEL_EMMC is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of PHY Subsystem
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
# CONFIG_ARM_CCI_PMU is not set
# CONFIG_ARM_CCN is not set
CONFIG_ARM_PMU=y
# end of Performance monitor support
# CONFIG_RAS is not set
#
# Android
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
# CONFIG_ANDROID_BINDERFS is not set
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Android
# CONFIG_DAX is not set
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
CONFIG_QCOM_QFPROM=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
# CONFIG_NVMEM_SPMI_SDAM is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# HW tracing support
#
# CONFIG_STM is not set
# CONFIG_INTEL_TH is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_FSI is not set
# CONFIG_TEE is not set
CONFIG_PM_OPP=y
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_MOST is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Device Drivers
#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not set
CONFIG_FS_IOMAP=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
# CONFIG_EXPORTFS_BLOCK_OPS is not set
CONFIG_FILE_LOCKING=y
CONFIG_MANDATORY_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
# CONFIG_FS_VERITY is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_AUTOFS4_FS=y
CONFIG_AUTOFS_FS=y
CONFIG_FUSE_FS=m
CONFIG_CUSE=m
# CONFIG_VIRTIO_FS is not set
CONFIG_OVERLAY_FS=m
# CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
# CONFIG_OVERLAY_FS_INDEX is not set
# CONFIG_OVERLAY_FS_METACOPY is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
# end of CD-ROM/DVD Filesystems
#
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# DOS/FAT/EXFAT/NT Filesystems
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
CONFIG_FAT_FS=y
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_FAT_DEFAULT_UTF8 is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_EXFAT_FS is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_NTFS_FS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# end of DOS/FAT/EXFAT/NT Filesystems
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_VMCORE=y
# CONFIG_PROC_VMCORE_DEVICE_DUMP is not set
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
# CONFIG_PROC_CHILDREN is not set
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_MEMFD_CREATE=y
CONFIG_CONFIGFS_FS=y
# end of Pseudo filesystems
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ORANGEFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc5 (!1055) - Update to Linux 5.6-rc5 - Basic audio support on samsung-gt510wifi (speaker is WIP) - Initial support for samsung-matissevewifi - Enable some kernel config options for elogind/Anbox/fbkeyboard
2020-03-11 12:40:04 +00:00
CONFIG_SQUASHFS=m
# CONFIG_SQUASHFS_FILE_CACHE is not set
CONFIG_SQUASHFS_FILE_DIRECT=y
# CONFIG_SQUASHFS_DECOMP_SINGLE is not set
# CONFIG_SQUASHFS_DECOMP_MULTI is not set
CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
# CONFIG_SQUASHFS_LZ4 is not set
# CONFIG_SQUASHFS_LZO is not set
CONFIG_SQUASHFS_XZ=y
# CONFIG_SQUASHFS_ZSTD is not set
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_PSTORE=y
CONFIG_PSTORE_DEFLATE_COMPRESS=y
# CONFIG_PSTORE_LZO_COMPRESS is not set
# CONFIG_PSTORE_LZ4_COMPRESS is not set
# CONFIG_PSTORE_LZ4HC_COMPRESS is not set
# CONFIG_PSTORE_842_COMPRESS is not set
CONFIG_PSTORE_ZSTD_COMPRESS=y
CONFIG_PSTORE_COMPRESS=y
# CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT is not set
CONFIG_PSTORE_ZSTD_COMPRESS_DEFAULT=y
CONFIG_PSTORE_COMPRESS_DEFAULT="zstd"
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_PMSG is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EROFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_DLM is not set
# CONFIG_UNICODE is not set
CONFIG_IO_WQ=y
# end of File systems
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_REQUEST_CACHE is not set
# CONFIG_PERSISTENT_KEYRINGS is not set
# CONFIG_BIG_KEYS is not set
# CONFIG_ENCRYPTED_KEYS is not set
# CONFIG_KEY_DH_OPERATIONS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_PATH is not set
CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
# CONFIG_HARDENED_USERCOPY is not set
# CONFIG_FORTIFY_SOURCE is not set
# CONFIG_STATIC_USERMODEHELPER is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
CONFIG_INTEGRITY=y
# CONFIG_INTEGRITY_SIGNATURE is not set
CONFIG_INTEGRITY_AUDIT=y
# CONFIG_IMA is not set
# CONFIG_EVM is not set
CONFIG_DEFAULT_SECURITY_DAC=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_LSM="lockdown,yama,loadpin,safesetid,integrity,bpf"
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
#
# Kernel hardening options
#
#
# Memory initialization
#
CONFIG_INIT_STACK_NONE=y
# CONFIG_INIT_ON_ALLOC_DEFAULT_ON is not set
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
# end of Memory initialization
# end of Kernel hardening options
# end of Security options
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_SKCIPHER=y
CONFIG_CRYPTO_SKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_RNG_DEFAULT=m
CONFIG_CRYPTO_AKCIPHER2=y
CONFIG_CRYPTO_AKCIPHER=y
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_KPP=m
CONFIG_CRYPTO_ACOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_NULL2=y
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_SIMD=y
#
# Public-key cryptography
#
CONFIG_CRYPTO_RSA=y
# CONFIG_CRYPTO_DH is not set
CONFIG_CRYPTO_ECC=m
CONFIG_CRYPTO_ECDH=m
# CONFIG_CRYPTO_ECRDSA is not set
# CONFIG_CRYPTO_CURVE25519 is not set
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
# CONFIG_CRYPTO_AEGIS128 is not set
CONFIG_CRYPTO_SEQIV=m
# CONFIG_CRYPTO_ECHAINIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=m
# CONFIG_CRYPTO_CFB is not set
CONFIG_CRYPTO_CTR=m
# CONFIG_CRYPTO_CTS is not set
main/linux-postmarketos-qcom-msm8916: enable CONFIG_CRYPTO_XTS (MR 1405) Seems like "pmbootstrap kconfig edit" causes unrelated kernel config changes for some reason (probably because pmbootstrap does not install a cross compiler for it). For now let's just edit the config manually with the new options so everything else stays as-is.
2020-07-11 11:05:00 +00:00
CONFIG_CRYPTO_ECB=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_OFB is not set
# CONFIG_CRYPTO_PCBC is not set
main/linux-postmarketos-qcom-msm8916: enable CONFIG_CRYPTO_XTS (MR 1405) Seems like "pmbootstrap kconfig edit" causes unrelated kernel config changes for some reason (probably because pmbootstrap does not install a cross compiler for it). For now let's just edit the config manually with the new options so everything else stays as-is.
2020-07-11 11:05:00 +00:00
CONFIG_CRYPTO_XTS=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_CRYPTO_KEYWRAP is not set
CONFIG_CRYPTO_NHPOLY1305=m
# CONFIG_CRYPTO_ADIANTUM is not set
CONFIG_CRYPTO_ESSIV=m
#
# Hash modes
#
CONFIG_CRYPTO_CMAC=m
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_XXHASH is not set
# CONFIG_CRYPTO_BLAKE2B is not set
# CONFIG_CRYPTO_BLAKE2S is not set
# CONFIG_CRYPTO_CRCT10DIF is not set
CONFIG_CRYPTO_GHASH=m
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_SHA3=m
CONFIG_CRYPTO_SM3=m
# CONFIG_CRYPTO_STREEBOG is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_TI is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_SM4=m
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_LZO is not set
# CONFIG_CRYPTO_842 is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set
CONFIG_CRYPTO_ZSTD=y
#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=y
CONFIG_CRYPTO_DRBG_MENU=y
CONFIG_CRYPTO_DRBG_HMAC=y
# CONFIG_CRYPTO_DRBG_HASH is not set
# CONFIG_CRYPTO_DRBG_CTR is not set
CONFIG_CRYPTO_DRBG=y
CONFIG_CRYPTO_JITTERENTROPY=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_CRYPTO_USER_API=m
CONFIG_CRYPTO_USER_API_HASH=m
CONFIG_CRYPTO_USER_API_SKCIPHER=m
CONFIG_CRYPTO_USER_API_RNG=m
CONFIG_CRYPTO_USER_API_AEAD=m
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_CRYPTO_HASH_INFO=y
#
# Crypto library routines
#
CONFIG_CRYPTO_LIB_AES=y
CONFIG_CRYPTO_LIB_ARC4=m
# CONFIG_CRYPTO_LIB_BLAKE2S is not set
CONFIG_CRYPTO_ARCH_HAVE_LIB_CHACHA=m
# CONFIG_CRYPTO_LIB_CHACHA is not set
# CONFIG_CRYPTO_LIB_CURVE25519 is not set
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=9
CONFIG_CRYPTO_LIB_POLY1305_GENERIC=m
# CONFIG_CRYPTO_LIB_POLY1305 is not set
# CONFIG_CRYPTO_LIB_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_LIB_SHA256=y
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_ATMEL_ECC is not set
# CONFIG_CRYPTO_DEV_ATMEL_SHA204A is not set
# CONFIG_CRYPTO_DEV_QCE is not set
CONFIG_CRYPTO_DEV_QCOM_RNG=y
# CONFIG_CRYPTO_DEV_VIRTIO is not set
# CONFIG_CRYPTO_DEV_SAFEXCEL is not set
# CONFIG_CRYPTO_DEV_CCREE is not set
# CONFIG_CRYPTO_DEV_AMLOGIC_GXL is not set
CONFIG_ASYMMETRIC_KEY_TYPE=y
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
CONFIG_X509_CERTIFICATE_PARSER=y
# CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set
CONFIG_PKCS7_MESSAGE_PARSER=y
# CONFIG_PKCS7_TEST_KEY is not set
# CONFIG_SIGNED_PE_FILE_VERIFICATION is not set
#
# Certificates for signature checking
#
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
# CONFIG_SYSTEM_EXTRA_CERTIFICATE is not set
# CONFIG_SECONDARY_TRUSTED_KEYRING is not set
# CONFIG_SYSTEM_BLACKLIST_KEYRING is not set
# end of Certificates for signature checking
#
# Library routines
#
# CONFIG_PACKING is not set
CONFIG_BITREVERSE=y
CONFIG_HAVE_ARCH_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
# CONFIG_CORDIC is not set
CONFIG_RATIONAL=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC64 is not set
# CONFIG_CRC4 is not set
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
# CONFIG_CRC8 is not set
CONFIG_XXHASH=y
CONFIG_AUDIT_GENERIC=y
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_ZSTD_COMPRESS=y
CONFIG_ZSTD_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_ASSOCIATIVE_ARRAY=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT_MAP=y
CONFIG_HAS_DMA=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_DMA_DECLARE_COHERENT=y
CONFIG_ARCH_HAS_SETUP_DMA_OPS=y
CONFIG_ARCH_HAS_TEARDOWN_DMA_OPS=y
CONFIG_ARCH_HAS_SYNC_DMA_FOR_DEVICE=y
CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU=y
CONFIG_ARCH_HAS_DMA_PREP_COHERENT=y
CONFIG_DMA_NONCOHERENT_MMAP=y
CONFIG_DMA_REMAP=y
CONFIG_DMA_CMA=y
#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=32
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8
# CONFIG_DMA_API_DEBUG is not set
CONFIG_SGL_ALLOC=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
# CONFIG_GLOB_SELFTEST is not set
CONFIG_NLATTR=y
CONFIG_CLZ_TAB=y
# CONFIG_IRQ_POLL is not set
CONFIG_MPILIB=y
CONFIG_LIBFDT=y
CONFIG_OID_REGISTRY=y
CONFIG_HAVE_GENERIC_VDSO=y
CONFIG_GENERIC_GETTIMEOFDAY=y
CONFIG_GENERIC_VDSO_32=y
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SG_POOL=y
CONFIG_SBITMAP=y
# CONFIG_STRING_SELFTEST is not set
# end of Library routines
#
# Kernel hacking
#
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
# CONFIG_PRINTK_CALLER is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
CONFIG_DYNAMIC_DEBUG=y
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
# end of printk and dmesg options
#
# Compile-time checks and compiler options
#
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
# CONFIG_DEBUG_INFO_DWARF4 is not set
# CONFIG_DEBUG_INFO_BTF is not set
# CONFIG_GDB_SCRIPTS is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
# CONFIG_HEADERS_INSTALL is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# end of Compile-time checks and compiler options
#
# Generic Kernel Debugging Instruments
#
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_MAGIC_SYSRQ_SERIAL=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_DEBUG_FS=y
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_UBSAN is not set
# end of Generic Kernel Debugging Instruments
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_MISC=y
#
# Memory Debugging
#
# CONFIG_PAGE_EXTENSION is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
# CONFIG_DEBUG_VM is not set
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_KASAN_STACK=1
# end of Memory Debugging
# CONFIG_DEBUG_SHIRQ is not set
#
# Debug Oops, Lockups and Hangs
#
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
# CONFIG_SOFTLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_WQ_WATCHDOG is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_TEST_LOCKUP is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# end of Debug Oops, Lockups and Hangs
#
# Scheduler Debugging
#
# CONFIG_SCHED_DEBUG is not set
CONFIG_SCHED_INFO=y
# CONFIG_SCHEDSTATS is not set
# end of Scheduler Debugging
# CONFIG_DEBUG_TIMEKEEPING is not set
# CONFIG_DEBUG_PREEMPT is not set
#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)
# CONFIG_STACKTRACE is not set
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
#
# Debug kernel data structures
#
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PLIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_BUG_ON_DATA_CORRUPTION is not set
# end of Debug kernel data structures
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
# CONFIG_RCU_PERF_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=21
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_RCU_TRACE=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_RCU_EQS_DEBUG is not set
# end of RCU Debugging
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
main/linux-postmarketos-qcom-msm8916: upgrade to 5.6-rc2 (!970) - Update to Linux 5.6-rc2 - Major improvements for Motorola Moto G4 Play (motorola-harpia) - Display - Touchscreen - Accelerometer - Audio - Modem - Vibrator - Fix headphones/headset detection for wileyfox-crackling - Add mount-matrix for samsung-a3ulte/a5ulte to fix orientation detection with iio-sensor-proxy - A lot of cleanup everywhere - APKBUILD: Clean up makedepends (a lot of them are unneeded)
2020-02-20 10:31:39 +00:00
CONFIG_TRACE_CLOCK=y
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_SAMPLES is not set
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
# CONFIG_IO_STRICT_DEVMEM is not set
#
# arm Debugging
#
# CONFIG_ARM_PTDUMP_DEBUGFS is not set
# CONFIG_DEBUG_WX is not set
# CONFIG_UNWINDER_FRAME_POINTER is not set
CONFIG_UNWINDER_ARM=y
CONFIG_ARM_UNWIND=y
# CONFIG_DEBUG_USER is not set
# CONFIG_DEBUG_LL is not set
CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h"
# CONFIG_PID_IN_CONTEXTIDR is not set
# CONFIG_CORESIGHT is not set
# end of arm Debugging
#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_CC_HAS_SANCOV_TRACE_PC=y
# CONFIG_KCOV is not set
CONFIG_RUNTIME_TESTING_MENU=y
# CONFIG_LKDTM is not set
# CONFIG_TEST_LIST_SORT is not set
main/linux-postmarketos-qcom-msm8916: upgrade to 5.7-rc2 (!1167) - Update to Linux 5.7-rc2 - Initial support for BQ Aquaris X5 (bq-paella/picmt) - Add speaker for samsung-gt510wifi/matissevewifi - Add flash LED for wileyfox-crackling
2020-04-20 10:15:21 +00:00
# CONFIG_TEST_MIN_HEAP is not set
main/linux-postmarketos-qcom-msm8916: build for armv7 (!828) Unfortunately, early firmware versions on MSM8916 (used together with Android 4.4) are not capable of booting aarch64 kernels. MSM8916 was Qualcomm's first 64-bit capable CPU, and back when it was introduced Android did not even support aarch64 yet. So the aarch64 capable hardware was usually used together with armv7 binaries. To make things worse, this firmware is also signed (usually per-device), making it (currently) impossible to update it without help from the manufacturer. This means that we are currently unable to run mainline on devices that never received an update to Android 5.0 (e.g. the Samsung Galaxy S4 Mini Value Edition). One way to circumvent this limitation is to build mainline for armv7. This works surprisingly well with some additional fixes. Devices with this firmware limitation are still unable to use aarch64 binaries, but at least we can run mainline on them!
2019-12-07 14:00:13 +00:00
# CONFIG_TEST_SORT is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_REED_SOLOMON_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_HEXDUMP is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_STRSCPY is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_PRINTF is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_BITFIELD is not set
# CONFIG_TEST_UUID is not set
# CONFIG_TEST_XARRAY is not set
# CONFIG_TEST_OVERFLOW is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_HASH is not set
# CONFIG_TEST_IDA is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_VMALLOC is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_TEST_BPF is not set
# CONFIG_TEST_BLACKHOLE_DEV is not set
# CONFIG_FIND_BIT_BENCHMARK is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_SYSCTL is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_TEST_KMOD is not set
# CONFIG_TEST_MEMCAT_P is not set
# CONFIG_TEST_STACKINIT is not set
# CONFIG_TEST_MEMINIT is not set
# CONFIG_MEMTEST is not set
# end of Kernel Testing and Coverage
# end of Kernel hacking
Reference in a new issue Copy permalink