2019-12-09 16:37:22 +00:00
|
|
|
#
|
|
|
|
|
# Automatically generated make config: don't edit
|
|
|
|
|
# Linux/arm 3.0.101 Kernel Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARM=y
|
|
|
|
|
CONFIG_ARM_HAS_SG_CHAIN=y
|
|
|
|
|
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
|
|
|
|
|
CONFIG_HAVE_SCHED_CLOCK=y
|
|
|
|
|
CONFIG_GENERIC_GPIO=y
|
|
|
|
|
# CONFIG_ARCH_USES_GETTIMEOFFSET is not set
|
|
|
|
|
CONFIG_GENERIC_CLOCKEVENTS=y
|
|
|
|
|
CONFIG_KTIME_SCALAR=y
|
|
|
|
|
CONFIG_HAVE_PROC_CPU=y
|
|
|
|
|
CONFIG_STACKTRACE_SUPPORT=y
|
|
|
|
|
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
|
|
|
|
|
CONFIG_LOCKDEP_SUPPORT=y
|
|
|
|
|
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
|
|
|
|
|
CONFIG_HARDIRQS_SW_RESEND=y
|
|
|
|
|
CONFIG_GENERIC_IRQ_PROBE=y
|
|
|
|
|
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
|
|
|
|
|
CONFIG_ARCH_HAS_CPUFREQ=y
|
|
|
|
|
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
|
|
|
|
|
CONFIG_GENERIC_HWEIGHT=y
|
|
|
|
|
CONFIG_GENERIC_CALIBRATE_DELAY=y
|
|
|
|
|
CONFIG_NEED_DMA_MAP_STATE=y
|
|
|
|
|
CONFIG_VECTORS_BASE=0xffff0000
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_ARM_PATCH_PHYS_VIRT is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_GENERIC_BUG=y
|
|
|
|
|
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
|
|
|
|
|
CONFIG_HAVE_IRQ_WORK=y
|
|
|
|
|
CONFIG_IRQ_WORK=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# General setup
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_EXPERIMENTAL=y
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_BROKEN_ON_SMP=y
|
|
|
|
|
CONFIG_INIT_ENV_ARG_LIMIT=32
|
|
|
|
|
CONFIG_CROSS_COMPILE=""
|
|
|
|
|
CONFIG_LOCALVERSION="-PRIMO_POWER-KITKAT"
|
|
|
|
|
# CONFIG_LOCALVERSION_AUTO is not set
|
|
|
|
|
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 is not set
|
|
|
|
|
# CONFIG_KERNEL_LZMA is not set
|
|
|
|
|
CONFIG_KERNEL_XZ=y
|
|
|
|
|
# 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
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_POSIX_MQUEUE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_BSD_PROCESS_ACCT is not set
|
|
|
|
|
# CONFIG_FHANDLE is not set
|
|
|
|
|
# CONFIG_TASKSTATS is not set
|
|
|
|
|
CONFIG_AUDIT=y
|
|
|
|
|
CONFIG_AUDITSYSCALL=y
|
|
|
|
|
CONFIG_AUDIT_WATCH=y
|
|
|
|
|
CONFIG_AUDIT_TREE=y
|
|
|
|
|
CONFIG_HAVE_GENERIC_HARDIRQS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IRQ subsystem
|
|
|
|
|
#
|
|
|
|
|
CONFIG_GENERIC_HARDIRQS=y
|
|
|
|
|
CONFIG_HAVE_SPARSE_IRQ=y
|
|
|
|
|
CONFIG_GENERIC_IRQ_SHOW=y
|
|
|
|
|
# CONFIG_SPARSE_IRQ is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# RCU Subsystem
|
|
|
|
|
#
|
|
|
|
|
CONFIG_TINY_PREEMPT_RCU=y
|
|
|
|
|
CONFIG_PREEMPT_RCU=y
|
|
|
|
|
# CONFIG_PREEMPT_COUNT_CPU is not set
|
|
|
|
|
# CONFIG_RCU_TRACE is not set
|
|
|
|
|
# CONFIG_TREE_RCU_TRACE is not set
|
|
|
|
|
# CONFIG_RCU_BOOST is not set
|
|
|
|
|
CONFIG_IKCONFIG=y
|
|
|
|
|
CONFIG_IKCONFIG_PROC=y
|
|
|
|
|
CONFIG_LOG_BUF_SHIFT=17
|
|
|
|
|
CONFIG_CGROUPS=y
|
|
|
|
|
CONFIG_CGROUP_DEBUG=y
|
|
|
|
|
CONFIG_CGROUP_FREEZER=y
|
|
|
|
|
# CONFIG_CGROUP_TIMER_SLACK is not set
|
|
|
|
|
# CONFIG_CGROUP_DEVICE is not set
|
|
|
|
|
# CONFIG_CPUSETS is not set
|
|
|
|
|
CONFIG_CGROUP_CPUACCT=y
|
|
|
|
|
CONFIG_RESOURCE_COUNTERS=y
|
|
|
|
|
CONFIG_CGROUP_MEM_RES_CTLR=y
|
|
|
|
|
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
|
|
|
|
|
CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y
|
|
|
|
|
# CONFIG_CGROUP_PERF is not set
|
|
|
|
|
CONFIG_CGROUP_SCHED=y
|
|
|
|
|
CONFIG_FAIR_GROUP_SCHED=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CFS_BANDWIDTH is not set
|
|
|
|
|
# CONFIG_RT_GROUP_SCHED is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_BLK_CGROUP is not set
|
|
|
|
|
# CONFIG_NAMESPACES is not set
|
|
|
|
|
# CONFIG_SCHED_AUTOGROUP is not set
|
|
|
|
|
CONFIG_MM_OWNER=y
|
|
|
|
|
# CONFIG_SYSFS_DEPRECATED is not set
|
|
|
|
|
CONFIG_RELAY=y
|
|
|
|
|
CONFIG_BLK_DEV_INITRD=y
|
|
|
|
|
CONFIG_INITRAMFS_SOURCE=""
|
|
|
|
|
CONFIG_RD_GZIP=y
|
|
|
|
|
# CONFIG_RD_BZIP2 is not set
|
|
|
|
|
# CONFIG_RD_LZMA is not set
|
|
|
|
|
# CONFIG_RD_XZ is not set
|
|
|
|
|
# CONFIG_RD_LZO is not set
|
|
|
|
|
# CONFIG_RD_LZ4 is not set
|
|
|
|
|
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
|
|
|
|
|
# CONFIG_CC_OPTIMIZE_ALITTLE is not set
|
|
|
|
|
# CONFIG_CC_OPTIMIZE_DEFAULT is not set
|
|
|
|
|
# CONFIG_CC_OPTIMIZE_ALOT is not set
|
|
|
|
|
# CONFIG_CC_GRAPHITE_OPTIMIZATION is not set
|
|
|
|
|
# CONFIG_CC_LINK_TIME_OPTIMIZATION is not set
|
|
|
|
|
CONFIG_SYSCTL=y
|
|
|
|
|
CONFIG_ANON_INODES=y
|
|
|
|
|
CONFIG_PANIC_TIMEOUT=5
|
|
|
|
|
CONFIG_EXPERT=y
|
|
|
|
|
CONFIG_UID16=y
|
|
|
|
|
# CONFIG_SYSCTL_SYSCALL is not set
|
|
|
|
|
CONFIG_KALLSYMS=y
|
|
|
|
|
CONFIG_HOTPLUG=y
|
|
|
|
|
CONFIG_PRINTK=y
|
|
|
|
|
CONFIG_BUG=y
|
|
|
|
|
# CONFIG_ELF_CORE is not set
|
|
|
|
|
CONFIG_BASE_FULL=y
|
|
|
|
|
CONFIG_FUTEX=y
|
|
|
|
|
CONFIG_EPOLL=y
|
|
|
|
|
CONFIG_SIGNALFD=y
|
|
|
|
|
CONFIG_TIMERFD=y
|
|
|
|
|
CONFIG_EVENTFD=y
|
|
|
|
|
CONFIG_SHMEM=y
|
|
|
|
|
CONFIG_ASHMEM=y
|
|
|
|
|
CONFIG_AIO=y
|
|
|
|
|
CONFIG_EMBEDDED=y
|
|
|
|
|
CONFIG_HAVE_PERF_EVENTS=y
|
|
|
|
|
CONFIG_PERF_USE_VMALLOC=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel Performance Events And Counters
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PERF_EVENTS=y
|
|
|
|
|
# CONFIG_PERF_COUNTERS is not set
|
|
|
|
|
CONFIG_VM_EVENT_COUNTERS=y
|
|
|
|
|
CONFIG_SLUB_DEBUG=y
|
|
|
|
|
CONFIG_COMPAT_BRK=y
|
|
|
|
|
# CONFIG_SLAB is not set
|
|
|
|
|
CONFIG_SLUB=y
|
|
|
|
|
# CONFIG_SLQB is not set
|
|
|
|
|
# CONFIG_SLOB is not set
|
|
|
|
|
# CONFIG_PROFILING is not set
|
|
|
|
|
CONFIG_HAVE_OPROFILE=y
|
|
|
|
|
CONFIG_HAVE_KPROBES=y
|
|
|
|
|
CONFIG_HAVE_KRETPROBES=y
|
|
|
|
|
CONFIG_HAVE_DMA_ATTRS=y
|
|
|
|
|
CONFIG_HAVE_CLK=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# GCOV-based kernel profiling
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_GCOV_KERNEL is not set
|
|
|
|
|
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
|
|
|
|
|
CONFIG_SLABINFO=y
|
|
|
|
|
CONFIG_RT_MUTEXES=y
|
|
|
|
|
CONFIG_BASE_SMALL=0
|
|
|
|
|
# CONFIG_MODULES is not set
|
|
|
|
|
CONFIG_BLOCK=y
|
|
|
|
|
CONFIG_LBDAF=y
|
|
|
|
|
# CONFIG_BLK_DEV_BSG is not set
|
|
|
|
|
# CONFIG_BLK_DEV_INTEGRITY is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IO Schedulers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_IOSCHED_NOOP=y
|
|
|
|
|
CONFIG_IOSCHED_DEADLINE=y
|
|
|
|
|
CONFIG_IOSCHED_ROW=y
|
|
|
|
|
CONFIG_IOSCHED_CFQ=y
|
|
|
|
|
CONFIG_IOSCHED_SIO=y
|
|
|
|
|
# CONFIG_IOSCHED_FIOPS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IOSCHED_BFQ is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_DEFAULT_DEADLINE is not set
|
|
|
|
|
# CONFIG_DEFAULT_ROW is not set
|
|
|
|
|
# CONFIG_DEFAULT_CFQ is not set
|
|
|
|
|
# CONFIG_DEFAULT_SIO is not set
|
|
|
|
|
CONFIG_DEFAULT_NOOP=y
|
|
|
|
|
CONFIG_DEFAULT_IOSCHED="noop"
|
|
|
|
|
# CONFIG_INLINE_SPIN_TRYLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_LOCK is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_LOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_UNLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_UNLOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
|
|
|
|
|
# CONFIG_INLINE_READ_TRYLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_READ_LOCK is not set
|
|
|
|
|
# CONFIG_INLINE_READ_LOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_READ_LOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
|
|
|
|
|
# CONFIG_INLINE_READ_UNLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_READ_UNLOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_READ_UNLOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_TRYLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_LOCK is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_LOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_UNLOCK is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_UNLOCK_IRQ is not set
|
|
|
|
|
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
|
|
|
|
|
# CONFIG_MUTEX_SPIN_ON_OWNER is not set
|
|
|
|
|
CONFIG_FREEZER=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# System Type
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MMU=y
|
|
|
|
|
# CONFIG_ARCH_INTEGRATOR is not set
|
|
|
|
|
# CONFIG_ARCH_REALVIEW is not set
|
|
|
|
|
# CONFIG_ARCH_VERSATILE is not set
|
|
|
|
|
# CONFIG_ARCH_VEXPRESS is not set
|
|
|
|
|
# CONFIG_ARCH_AT91 is not set
|
|
|
|
|
# CONFIG_ARCH_BCMRING is not set
|
|
|
|
|
# CONFIG_ARCH_CLPS711X is not set
|
|
|
|
|
# CONFIG_ARCH_CNS3XXX is not set
|
|
|
|
|
# CONFIG_ARCH_GEMINI is not set
|
|
|
|
|
# CONFIG_ARCH_EBSA110 is not set
|
|
|
|
|
# CONFIG_ARCH_EP93XX is not set
|
|
|
|
|
# CONFIG_ARCH_FOOTBRIDGE is not set
|
|
|
|
|
# CONFIG_ARCH_MXC is not set
|
|
|
|
|
# CONFIG_ARCH_MXS is not set
|
|
|
|
|
# CONFIG_ARCH_NETX is not set
|
|
|
|
|
# CONFIG_ARCH_H720X is not set
|
|
|
|
|
# CONFIG_ARCH_IOP13XX is not set
|
|
|
|
|
# CONFIG_ARCH_IOP32X is not set
|
|
|
|
|
# CONFIG_ARCH_IOP33X is not set
|
|
|
|
|
# CONFIG_ARCH_IXP23XX is not set
|
|
|
|
|
# CONFIG_ARCH_IXP2000 is not set
|
|
|
|
|
# CONFIG_ARCH_IXP4XX is not set
|
|
|
|
|
# CONFIG_ARCH_DOVE is not set
|
|
|
|
|
# CONFIG_ARCH_KIRKWOOD is not set
|
|
|
|
|
# CONFIG_ARCH_LOKI is not set
|
|
|
|
|
# CONFIG_ARCH_LPC32XX is not set
|
|
|
|
|
# CONFIG_ARCH_MV78XX0 is not set
|
|
|
|
|
# CONFIG_ARCH_ORION5X is not set
|
|
|
|
|
# CONFIG_ARCH_MMP is not set
|
|
|
|
|
# CONFIG_ARCH_KS8695 is not set
|
|
|
|
|
# CONFIG_ARCH_W90X900 is not set
|
|
|
|
|
# CONFIG_ARCH_NUC93X is not set
|
|
|
|
|
# CONFIG_ARCH_TEGRA is not set
|
|
|
|
|
# CONFIG_ARCH_PNX4008 is not set
|
|
|
|
|
# CONFIG_ARCH_PXA is not set
|
|
|
|
|
CONFIG_ARCH_MSM=y
|
|
|
|
|
# CONFIG_ARCH_SHMOBILE is not set
|
|
|
|
|
# CONFIG_ARCH_RPC is not set
|
|
|
|
|
# CONFIG_ARCH_SA1100 is not set
|
|
|
|
|
# CONFIG_ARCH_S3C2410 is not set
|
|
|
|
|
# CONFIG_ARCH_S3C64XX is not set
|
|
|
|
|
# CONFIG_ARCH_S5P64X0 is not set
|
|
|
|
|
# CONFIG_ARCH_S5PC100 is not set
|
|
|
|
|
# CONFIG_ARCH_S5PV210 is not set
|
|
|
|
|
# CONFIG_ARCH_EXYNOS4 is not set
|
|
|
|
|
# CONFIG_ARCH_SHARK is not set
|
|
|
|
|
# CONFIG_ARCH_TCC_926 is not set
|
|
|
|
|
# CONFIG_ARCH_U300 is not set
|
|
|
|
|
# CONFIG_ARCH_U8500 is not set
|
|
|
|
|
# CONFIG_ARCH_NOMADIK is not set
|
|
|
|
|
# CONFIG_ARCH_DAVINCI is not set
|
|
|
|
|
# CONFIG_ARCH_OMAP is not set
|
|
|
|
|
# CONFIG_PLAT_SPEAR is not set
|
|
|
|
|
# CONFIG_ARCH_VT8500 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MSM SoC Type
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARCH_MSM7X30=y
|
|
|
|
|
CONFIG_MSM_SOC_REV_NONE=y
|
|
|
|
|
# CONFIG_MSM_SOC_REV_A is not set
|
|
|
|
|
CONFIG_ARCH_MSM_SCORPION=y
|
|
|
|
|
CONFIG_MSM_VIC=y
|
|
|
|
|
# CONFIG_MSM_RPM is not set
|
|
|
|
|
# CONFIG_MSM_MPM is not set
|
|
|
|
|
CONFIG_MSM_REMOTE_SPINLOCK_DEKKERS=y
|
|
|
|
|
# CONFIG_PERFLOCK is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MSM Board Selection
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MACH_MSM7X30_SURF=y
|
|
|
|
|
CONFIG_MACH_MSM7X30_FFA=y
|
|
|
|
|
CONFIG_MACH_MSM7X30_FLUID=y
|
|
|
|
|
CONFIG_ARCH_MSM7X30_SMD=y
|
|
|
|
|
CONFIG_MACH_PRIMOU=y
|
|
|
|
|
# CONFIG_MACH_PRIMOC is not set
|
|
|
|
|
CONFIG_MSM_MDP40=y
|
|
|
|
|
CONFIG_PHYS_OFFSET=0x13F00000
|
|
|
|
|
CONFIG_MSM_AMSS_VERSION=1200
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_6210 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_6220 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_6225 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_6350 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_6355 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_1355 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_4725 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_4735 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_4410 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_3200 is not set
|
|
|
|
|
# CONFIG_MSM_AMSS_VERSION_1170 is not set
|
|
|
|
|
CONFIG_MSM_AMSS_VERSION_1200=y
|
|
|
|
|
CONFIG_MSM_DEBUG_UART_NONE=y
|
|
|
|
|
# CONFIG_MSM_DEBUG_UART1 is not set
|
|
|
|
|
# CONFIG_MSM_DEBUG_UART2 is not set
|
|
|
|
|
# CONFIG_MSM_DEBUG_UART3 is not set
|
|
|
|
|
# CONFIG_MSM_DEBUG_UART8 is not set
|
|
|
|
|
# CONFIG_MSM_DEBUG_UART11 is not set
|
|
|
|
|
# CONFIG_HTC_BATT_CORE is not set
|
|
|
|
|
CONFIG_MSM7X00A_USE_GP_TIMER=y
|
|
|
|
|
CONFIG_MSM7X00A_SLEEP_MODE_POWER_COLLAPSE_SUSPEND=y
|
|
|
|
|
# CONFIG_MSM7X00A_SLEEP_MODE_POWER_COLLAPSE is not set
|
|
|
|
|
# CONFIG_MSM7X00A_SLEEP_MODE_APPS_SLEEP is not set
|
|
|
|
|
# CONFIG_MSM7X00A_SLEEP_MODE_RAMP_DOWN_AND_WAIT_FOR_INTERRUPT is not set
|
|
|
|
|
# CONFIG_MSM7X00A_SLEEP_WAIT_FOR_INTERRUPT is not set
|
|
|
|
|
CONFIG_MSM7X00A_SLEEP_MODE=0
|
|
|
|
|
CONFIG_MSM7X00A_IDLE_SLEEP_MODE_POWER_COLLAPSE_SUSPEND=y
|
|
|
|
|
# CONFIG_MSM7X00A_IDLE_SLEEP_MODE_POWER_COLLAPSE is not set
|
|
|
|
|
# CONFIG_MSM7X00A_IDLE_SLEEP_MODE_APPS_SLEEP is not set
|
|
|
|
|
# CONFIG_MSM7X00A_IDLE_SLEEP_MODE_RAMP_DOWN_AND_WAIT_FOR_INTERRUPT is not set
|
|
|
|
|
# CONFIG_MSM7X00A_IDLE_SLEEP_WAIT_FOR_INTERRUPT is not set
|
|
|
|
|
CONFIG_MSM7X00A_IDLE_SLEEP_MODE=0
|
|
|
|
|
CONFIG_MSM7X00A_IDLE_SLEEP_MIN_TIME=20000000
|
|
|
|
|
CONFIG_MSM7X00A_IDLE_SPIN_TIME=80000
|
|
|
|
|
CONFIG_MSM_IDLE_STATS=y
|
|
|
|
|
CONFIG_MSM_IDLE_STATS_FIRST_BUCKET=62500
|
|
|
|
|
CONFIG_MSM_IDLE_STATS_BUCKET_SHIFT=2
|
|
|
|
|
CONFIG_MSM_IDLE_STATS_BUCKET_COUNT=10
|
|
|
|
|
CONFIG_MSM_SUSPEND_STATS_FIRST_BUCKET=1000000000
|
|
|
|
|
# CONFIG_HTC_HEADSET is not set
|
|
|
|
|
CONFIG_HTC_BATTCHG=y
|
|
|
|
|
# CONFIG_HTC_BATTCHG_MAX8957 is not set
|
|
|
|
|
CONFIG_HTC_BATTCHG_SMEM=y
|
|
|
|
|
# CONFIG_HTC_PWRSINK is not set
|
|
|
|
|
# CONFIG_BUILD_OMA_DM is not set
|
|
|
|
|
# CONFIG_MSM_FIQ_SUPPORT is not set
|
|
|
|
|
# CONFIG_MSM_SERIAL_DEBUGGER is not set
|
|
|
|
|
CONFIG_MSM_PROC_COMM=y
|
|
|
|
|
CONFIG_MSM_SMD=y
|
|
|
|
|
CONFIG_MSM_SMD_PKG3=y
|
|
|
|
|
# CONFIG_MSM_SMD_PKG4 is not set
|
|
|
|
|
CONFIG_MSM_SMD0_WQ=y
|
|
|
|
|
# CONFIG_MSM_SMD_DEBUG is not set
|
|
|
|
|
# CONFIG_MSM_SDIO_AL is not set
|
|
|
|
|
CONFIG_MSM_N_WAY_SMD=y
|
|
|
|
|
CONFIG_MSM_N_WAY_SMSM=y
|
|
|
|
|
# CONFIG_MSM_RESET_MODEM is not set
|
|
|
|
|
CONFIG_MSM_SMD_LOGGING=y
|
|
|
|
|
CONFIG_MSM_SMD_NMEA=y
|
|
|
|
|
CONFIG_MSM_SMD_TTY=y
|
|
|
|
|
CONFIG_MSM_SMD_QMI=y
|
|
|
|
|
CONFIG_MSM_SMD_PKT=y
|
|
|
|
|
CONFIG_MSM_ONCRPCROUTER=y
|
|
|
|
|
# CONFIG_MSM_IPC_ROUTER is not set
|
|
|
|
|
CONFIG_MSM_ONCRPCROUTER_DEBUG=y
|
|
|
|
|
# CONFIG_MSM_RPC_LOOPBACK_XPRT is not set
|
|
|
|
|
CONFIG_MSM_RPCSERVER_TIME_REMOTE=y
|
|
|
|
|
CONFIG_MSM_RPCSERVER_WATCHDOG=y
|
|
|
|
|
# CONFIG_MSM_RPC_WATCHDOG is not set
|
|
|
|
|
CONFIG_MSM_RPC_PING=y
|
|
|
|
|
CONFIG_MSM_RPC_PROC_COMM_TEST=y
|
|
|
|
|
CONFIG_MSM_RPC_OEM_RAPI=y
|
|
|
|
|
CONFIG_MSM_RPCSERVER_HANDSET=y
|
|
|
|
|
CONFIG_MSM_RMT_STORAGE_CLIENT=y
|
|
|
|
|
# CONFIG_MSM_RMT_STORAGE_SERVER is not set
|
|
|
|
|
# CONFIG_MSM_RMT_STORAGE_CLIENT_STATS is not set
|
|
|
|
|
CONFIG_MSM_DALRPC=y
|
|
|
|
|
# CONFIG_MSM_DALRPC_TEST is not set
|
|
|
|
|
CONFIG_MSM_CPU_FREQ_SET_MIN_MAX=y
|
|
|
|
|
CONFIG_MSM_CPU_FREQ_MAX=1200000
|
|
|
|
|
CONFIG_MSM_CPU_FREQ_MIN=368640
|
|
|
|
|
# CONFIG_ACPUCLOCK_OVERCLOCKING is not set
|
|
|
|
|
# CONFIG_MSM_AVS_HW is not set
|
|
|
|
|
# CONFIG_MSM_HW3D is not set
|
|
|
|
|
CONFIG_AMSS_7X25_VERSION_2009=y
|
|
|
|
|
# CONFIG_AMSS_7X25_VERSION_2008 is not set
|
|
|
|
|
CONFIG_MSM7KV2_AUDIO=y
|
|
|
|
|
CONFIG_MSM_ADSP_REPORT_EVENTS=y
|
|
|
|
|
CONFIG_RTAC=y
|
|
|
|
|
# CONFIG_MSM_VREG_SWITCH_INVERTED is not set
|
|
|
|
|
CONFIG_MSM_DMA_TEST=y
|
|
|
|
|
CONFIG_WIFI_CONTROL_FUNC=y
|
|
|
|
|
CONFIG_WIFI_MEM_PREALLOC=y
|
|
|
|
|
CONFIG_WIFI_NVS_PROC_CREATE=y
|
|
|
|
|
CONFIG_ARCH_MSM_FLASHLIGHT=y
|
|
|
|
|
# CONFIG_ARCH_MSM_FLASHLIGHT_DEATH_RAY is not set
|
|
|
|
|
# CONFIG_QSD_AUDIO is not set
|
|
|
|
|
CONFIG_AUDIO_AAC_PLUS=y
|
|
|
|
|
CONFIG_AUDIO_ENHANCED_AAC_PLUS=y
|
|
|
|
|
CONFIG_SURF_FFA_GPIO_KEYPAD=y
|
|
|
|
|
CONFIG_MSM_SLEEP_TIME_OVERRIDE=y
|
|
|
|
|
# CONFIG_HTC_OFFMODE_ALARM is not set
|
|
|
|
|
# CONFIG_HTC_QUICKBOOT_OFFMODE_ALARM is not set
|
|
|
|
|
CONFIG_MSM_MEMORY_LOW_POWER_MODE=y
|
|
|
|
|
# CONFIG_MSM_MEMORY_LOW_POWER_MODE_IDLE_ACTIVE is not set
|
|
|
|
|
CONFIG_MSM_MEMORY_LOW_POWER_MODE_IDLE_RETENTION=y
|
|
|
|
|
# CONFIG_MSM_MEMORY_LOW_POWER_MODE_IDLE_DEEP_POWER_DOWN is not set
|
|
|
|
|
# CONFIG_MSM_MEMORY_LOW_POWER_MODE_SUSPEND_ACTIVE is not set
|
|
|
|
|
# CONFIG_MSM_MEMORY_LOW_POWER_MODE_SUSPEND_RETENTION is not set
|
|
|
|
|
CONFIG_MSM_MEMORY_LOW_POWER_MODE_SUSPEND_DEEP_POWER_DOWN=y
|
|
|
|
|
CONFIG_MSM_PM_TIMEOUT_HALT=y
|
|
|
|
|
# CONFIG_MSM_PM_TIMEOUT_RESET_MODEM is not set
|
|
|
|
|
# CONFIG_MSM_PM_TIMEOUT_RESET_CHIP is not set
|
|
|
|
|
CONFIG_MSM_IDLE_WAIT_ON_MODEM=2000
|
|
|
|
|
# CONFIG_MICROP_COMMON is not set
|
|
|
|
|
CONFIG_HTC_HEADSET_MGR=y
|
|
|
|
|
# CONFIG_HTC_HEADSET_H2W is not set
|
|
|
|
|
CONFIG_HTC_HEADSET_GPIO=y
|
|
|
|
|
CONFIG_HTC_HEADSET_PMIC=y
|
|
|
|
|
# CONFIG_HTC_HEADSET_MAX8957 is not set
|
|
|
|
|
# CONFIG_HTC_HEADSET_MISC is not set
|
|
|
|
|
# CONFIG_HTC_HEADSET_8X60 is not set
|
|
|
|
|
CONFIG_SMD_OFFSET_TCXO_STAT=0xFC2A0
|
|
|
|
|
CONFIG_SMD_OFFSET_NEGATE_CLIENT_STAT=0xFC124
|
|
|
|
|
# CONFIG_MSM_SCM is not set
|
|
|
|
|
CONFIG_SCORPION_Uni_45nm_BUG=y
|
|
|
|
|
# CONFIG_MSM_RPM_LOG is not set
|
|
|
|
|
CONFIG_MSM_GPIOMUX=y
|
|
|
|
|
# CONFIG_MSM_BUS_SCALING is not set
|
|
|
|
|
# CONFIG_HAS_QDSS is not set
|
|
|
|
|
CONFIG_MSM_DEBUG_ACROSS_PC=y
|
|
|
|
|
CONFIG_MSM_JTAG_V7=y
|
|
|
|
|
# CONFIG_MSM_TRACE_ACROSS_PC is not set
|
|
|
|
|
CONFIG_MSM_STANDALONE_POWER_COLLAPSE=y
|
|
|
|
|
# CONFIG_MSM_GSBI9_UART is not set
|
|
|
|
|
CONFIG_MSM_SHOW_RESUME_IRQ=y
|
|
|
|
|
CONFIG_SUPPORT_DQ_BATTERY=y
|
|
|
|
|
# CONFIG_MSM_FAKE_BATTERY is not set
|
|
|
|
|
# CONFIG_MSM_QDSP6_APR is not set
|
|
|
|
|
# CONFIG_MSM_AUDIO_QDSP6 is not set
|
|
|
|
|
# CONFIG_MSM_RPC_VIBRATOR is not set
|
|
|
|
|
# CONFIG_RPC_VER_60001 is not set
|
|
|
|
|
CONFIG_MSM_SPM_V1=y
|
|
|
|
|
CONFIG_MSM_MULTIMEDIA_USE_ION=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# TI WLAN driver
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_TIWLAN_SDIO is not set
|
|
|
|
|
# CONFIG_HTC_BATT_ALARM is not set
|
|
|
|
|
# CONFIG_REMOVE_EBI1_FIXED_CLK is not set
|
|
|
|
|
# CONFIG_HTC_ACCESSORY_ONEWIRE is not set
|
|
|
|
|
CONFIG_FORCE_FAST_CHARGE=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Processor Type
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CPU_V7=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_THUMB=y
|
|
|
|
|
CONFIG_ARM_THUMBEE=y
|
|
|
|
|
# CONFIG_SWP_EMULATE is not set
|
|
|
|
|
# CONFIG_CPU_ICACHE_DISABLE is not set
|
|
|
|
|
# CONFIG_CPU_DCACHE_DISABLE is not set
|
|
|
|
|
# CONFIG_CPU_CACHE_ERR_REPORT is not set
|
|
|
|
|
# CONFIG_CPU_BPREDICT_DISABLE is not set
|
|
|
|
|
CONFIG_ARM_L1_CACHE_SHIFT_6=y
|
|
|
|
|
CONFIG_ARM_L1_CACHE_SHIFT=6
|
|
|
|
|
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
|
|
|
|
|
# CONFIG_VCM is not set
|
|
|
|
|
# CONFIG_STRICT_MEMORY_RWX is not set
|
|
|
|
|
CONFIG_RESERVE_FIRST_PAGE=y
|
|
|
|
|
CONFIG_CPU_HAS_PMU=y
|
|
|
|
|
# CONFIG_ARM_ERRATA_430973 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_458693 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_460075 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_743622 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_754322 is not set
|
|
|
|
|
# CONFIG_KSAPI is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_775420 is not set
|
|
|
|
|
# CONFIG_FIQ_DEBUGGER is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bus support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_PCI_SYSCALL is not set
|
|
|
|
|
# CONFIG_ARCH_SUPPORTS_MSI is not set
|
|
|
|
|
# CONFIG_PCCARD is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel Features
|
|
|
|
|
#
|
|
|
|
|
CONFIG_TICK_ONESHOT=y
|
|
|
|
|
CONFIG_NO_HZ=y
|
|
|
|
|
CONFIG_HIGH_RES_TIMERS=y
|
|
|
|
|
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
|
|
|
|
|
# CONFIG_ARM_ARCH_TIMER is not set
|
|
|
|
|
CONFIG_VMSPLIT_3G=y
|
|
|
|
|
# CONFIG_VMSPLIT_2G is not set
|
|
|
|
|
# CONFIG_VMSPLIT_1G is not set
|
|
|
|
|
CONFIG_PAGE_OFFSET=0xC0000000
|
|
|
|
|
# CONFIG_PREEMPT_NONE is not set
|
|
|
|
|
# CONFIG_PREEMPT_VOLUNTARY is not set
|
|
|
|
|
CONFIG_PREEMPT=y
|
|
|
|
|
CONFIG_HZ=100
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_THUMB2_KERNEL is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_AEABI=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_OABI_COMPAT=y
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
|
|
|
|
|
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
|
|
|
|
|
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
|
|
|
|
|
CONFIG_HAVE_ARCH_PFN_VALID=y
|
|
|
|
|
CONFIG_HIGHMEM=y
|
|
|
|
|
# CONFIG_HIGHPTE is not set
|
|
|
|
|
CONFIG_HW_PERF_EVENTS=y
|
|
|
|
|
CONFIG_VMALLOC_RESERVE=0x08000000
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_SELECT_MEMORY_MODEL=y
|
|
|
|
|
CONFIG_FLATMEM_MANUAL=y
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_FLATMEM=y
|
|
|
|
|
CONFIG_FLAT_NODE_MEM_MAP=y
|
|
|
|
|
CONFIG_HAVE_MEMBLOCK=y
|
|
|
|
|
CONFIG_PAGEFLAGS_EXTENDED=y
|
|
|
|
|
CONFIG_SPLIT_PTLOCK_CPUS=4
|
|
|
|
|
CONFIG_COMPACTION=y
|
|
|
|
|
CONFIG_MIGRATION=y
|
|
|
|
|
# CONFIG_PHYS_ADDR_T_64BIT is not set
|
|
|
|
|
CONFIG_ZONE_DMA_FLAG=0
|
|
|
|
|
CONFIG_BOUNCE=y
|
|
|
|
|
CONFIG_VIRT_TO_BUS=y
|
|
|
|
|
CONFIG_KSM=y
|
|
|
|
|
CONFIG_UKSM=y
|
|
|
|
|
# CONFIG_KSM_LEGACY is not set
|
|
|
|
|
# CONFIG_KSM_CHECK_PAGE is not set
|
|
|
|
|
CONFIG_DEFAULT_MMAP_MIN_ADDR=32768
|
|
|
|
|
CONFIG_NEED_PER_CPU_KM=y
|
|
|
|
|
# CONFIG_CLEANCACHE is not set
|
|
|
|
|
# CONFIG_FRONTSWAP is not set
|
|
|
|
|
# CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG is not set
|
|
|
|
|
# CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE is not set
|
|
|
|
|
CONFIG_FORCE_MAX_ZONEORDER=11
|
|
|
|
|
CONFIG_ALIGNMENT_TRAP=y
|
|
|
|
|
CONFIG_ALLOW_CPU_ALIGNMENT=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_UACCESS_WITH_MEMCPY is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SECCOMP is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CC_STACKPROTECTOR is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
|
|
|
|
|
# CONFIG_ARM_FLUSH_CONSOLE_ON_RESTART is not set
|
|
|
|
|
CONFIG_CP_ACCESS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Boot options
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USE_OF is not set
|
|
|
|
|
CONFIG_ZBOOT_ROM_TEXT=0x0
|
|
|
|
|
CONFIG_ZBOOT_ROM_BSS=0x0
|
|
|
|
|
CONFIG_CMDLINE="androidboot.selinux=permissive"
|
|
|
|
|
# CONFIG_CMDLINE_FROM_BOOTLOADER is not set
|
|
|
|
|
CONFIG_CMDLINE_EXTEND=y
|
|
|
|
|
# CONFIG_CMDLINE_FORCE is not set
|
|
|
|
|
# CONFIG_XIP_KERNEL is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_KEXEC is not set
|
|
|
|
|
# CONFIG_CRASH_DUMP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_AUTO_ZRELADDR is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CPU Power Management
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CPU Frequency scaling
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CPU_FREQ=y
|
|
|
|
|
CONFIG_CPU_FREQ_TABLE=y
|
|
|
|
|
CONFIG_CPU_FREQ_STAT=y
|
|
|
|
|
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTASS2 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_INTERACTIVE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTELLIDEMAND is not set
|
|
|
|
|
CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTMAX=y
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTELLIACTIVE is not set
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_SMARTASS2=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_INTELLIDEMAND=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_SMARTMAX=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_SMARTMAX_30=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_SMARTMAX_PRIMOU=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_USERSPACE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_INTELLIACTIVE=y
|
|
|
|
|
CONFIG_CPU_FREQ_VDD_LEVELS=y
|
|
|
|
|
CONFIG_CPU_FREQ_MIN_TICKS=10
|
|
|
|
|
CONFIG_CPU_FREQ_SAMPLING_LATENCY_MULTIPLIER=1000
|
|
|
|
|
# CONFIG_SEC_DVFS is not set
|
|
|
|
|
CONFIG_SEC_LIMIT_LCD_OFF_CPU_MAX_FREQ=y
|
|
|
|
|
# CONFIG_CPU_IDLE is not set
|
|
|
|
|
CONFIG_CPU_FREQ_MSM=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Floating point emulation
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# At least one emulation must be selected
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_FPE_NWFPE is not set
|
|
|
|
|
# CONFIG_FPE_FASTFPE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_VFP=y
|
|
|
|
|
CONFIG_VFPv3=y
|
|
|
|
|
CONFIG_NEON=y
|
|
|
|
|
CONFIG_KERNEL_MODE_NEON=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Userspace binary formats
|
|
|
|
|
#
|
|
|
|
|
CONFIG_BINFMT_ELF=y
|
|
|
|
|
CONFIG_HAVE_AOUT=y
|
|
|
|
|
# CONFIG_BINFMT_AOUT is not set
|
|
|
|
|
# CONFIG_BINFMT_MISC is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Power management options
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SUSPEND=y
|
|
|
|
|
CONFIG_SUSPEND_FREEZER=y
|
|
|
|
|
CONFIG_HAS_WAKELOCK=y
|
|
|
|
|
CONFIG_HAS_EARLYSUSPEND=y
|
|
|
|
|
CONFIG_CPU_PM=y
|
|
|
|
|
CONFIG_WAKELOCK=y
|
|
|
|
|
CONFIG_WAKELOCK_STAT=y
|
|
|
|
|
CONFIG_USER_WAKELOCK=y
|
|
|
|
|
CONFIG_EARLYSUSPEND=y
|
|
|
|
|
# CONFIG_NO_USER_SPACE_SCREEN_ACCESS_CONTROL is not set
|
|
|
|
|
# CONFIG_CONSOLE_EARLYSUSPEND is not set
|
|
|
|
|
CONFIG_FB_EARLYSUSPEND=y
|
|
|
|
|
CONFIG_PM_SLEEP=y
|
|
|
|
|
CONFIG_PM_RUNTIME=y
|
|
|
|
|
CONFIG_PM=y
|
|
|
|
|
CONFIG_PM_DEBUG=y
|
|
|
|
|
# CONFIG_PM_ADVANCED_DEBUG is not set
|
|
|
|
|
# CONFIG_PM_TEST_SUSPEND is not set
|
|
|
|
|
CONFIG_CAN_PM_TRACE=y
|
|
|
|
|
# CONFIG_APM_EMULATION is not set
|
|
|
|
|
CONFIG_PM_RUNTIME_CLK=y
|
|
|
|
|
CONFIG_SUSPEND_TIME=y
|
|
|
|
|
CONFIG_ARCH_SUSPEND_POSSIBLE=y
|
|
|
|
|
CONFIG_NET=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Networking options
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PACKET=y
|
|
|
|
|
CONFIG_UNIX=y
|
|
|
|
|
CONFIG_XFRM=y
|
|
|
|
|
CONFIG_XFRM_USER=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_XFRM_SUB_POLICY is not set
|
|
|
|
|
# CONFIG_XFRM_MIGRATE is not set
|
|
|
|
|
# CONFIG_XFRM_STATISTICS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_XFRM_IPCOMP=y
|
|
|
|
|
CONFIG_NET_KEY=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NET_KEY_MIGRATE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_INET=y
|
|
|
|
|
CONFIG_IP_MULTICAST=y
|
|
|
|
|
CONFIG_IP_ADVANCED_ROUTER=y
|
|
|
|
|
# CONFIG_IP_FIB_TRIE_STATS is not set
|
|
|
|
|
CONFIG_IP_MULTIPLE_TABLES=y
|
|
|
|
|
# CONFIG_IP_ROUTE_MULTIPATH is not set
|
|
|
|
|
CONFIG_IP_ROUTE_VERBOSE=y
|
|
|
|
|
# CONFIG_IP_PNP is not set
|
|
|
|
|
# CONFIG_NET_IPIP is not set
|
|
|
|
|
# CONFIG_NET_IPGRE_DEMUX is not set
|
|
|
|
|
# CONFIG_IP_MROUTE is not set
|
|
|
|
|
CONFIG_LARGE_TCP_INITIAL_BUFFER=y
|
|
|
|
|
# CONFIG_ARPD is not set
|
|
|
|
|
# CONFIG_SYN_COOKIES is not set
|
|
|
|
|
CONFIG_INET_AH=y
|
|
|
|
|
CONFIG_INET_ESP=y
|
|
|
|
|
# CONFIG_INET_IPCOMP is not set
|
|
|
|
|
# CONFIG_INET_XFRM_TUNNEL is not set
|
|
|
|
|
CONFIG_INET_TUNNEL=y
|
|
|
|
|
CONFIG_INET_XFRM_MODE_TRANSPORT=y
|
|
|
|
|
CONFIG_INET_XFRM_MODE_TUNNEL=y
|
|
|
|
|
# CONFIG_INET_XFRM_MODE_BEET is not set
|
|
|
|
|
# CONFIG_INET_LRO is not set
|
|
|
|
|
CONFIG_INET_DIAG=y
|
|
|
|
|
CONFIG_INET_TCP_DIAG=y
|
|
|
|
|
# CONFIG_TCP_CONG_ADVANCED is not set
|
|
|
|
|
CONFIG_TCP_CONG_CUBIC=y
|
|
|
|
|
CONFIG_DEFAULT_TCP_CONG="cubic"
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_TCP_MD5SIG is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_IPV6=y
|
|
|
|
|
CONFIG_IPV6_PRIVACY=y
|
|
|
|
|
CONFIG_IPV6_ROUTER_PREF=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IPV6_ROUTE_INFO is not set
|
|
|
|
|
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_INET6_AH=y
|
|
|
|
|
CONFIG_INET6_ESP=y
|
|
|
|
|
CONFIG_INET6_IPCOMP=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IPV6_MIP6 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_INET6_XFRM_TUNNEL=y
|
|
|
|
|
CONFIG_INET6_TUNNEL=y
|
|
|
|
|
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
|
|
|
|
|
CONFIG_INET6_XFRM_MODE_TUNNEL=y
|
|
|
|
|
CONFIG_INET6_XFRM_MODE_BEET=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_IPV6_SIT=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IPV6_SIT_6RD is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_IPV6_NDISC_NODETYPE=y
|
|
|
|
|
CONFIG_IPV6_TUNNEL=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IPV6_MULTIPLE_TABLES is not set
|
|
|
|
|
# CONFIG_IPV6_MROUTE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_NETLABEL is not set
|
|
|
|
|
# CONFIG_ANDROID_PARANOID_NETWORK is not set
|
|
|
|
|
CONFIG_NET_ACTIVITY_STATS=y
|
|
|
|
|
CONFIG_NETWORK_SECMARK=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NETFILTER=y
|
|
|
|
|
# CONFIG_NETFILTER_DEBUG is not set
|
|
|
|
|
CONFIG_NETFILTER_ADVANCED=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Core Netfilter Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NETFILTER_NETLINK=y
|
|
|
|
|
CONFIG_NETFILTER_NETLINK_QUEUE=y
|
|
|
|
|
# CONFIG_NETFILTER_NETLINK_LOG is not set
|
|
|
|
|
CONFIG_NF_CONNTRACK=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_MARK=y
|
|
|
|
|
# CONFIG_NF_CONNTRACK_SECMARK is not set
|
|
|
|
|
CONFIG_NF_CONNTRACK_EVENTS=y
|
|
|
|
|
# CONFIG_NF_CONNTRACK_TIMESTAMP is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NF_CT_PROTO_DCCP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NF_CT_PROTO_GRE=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NF_CT_PROTO_SCTP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NF_CT_PROTO_UDPLITE=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_AMANDA=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_FTP=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_H323=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_IRC=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_BROADCAST=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
|
|
|
|
|
# CONFIG_NF_CONNTRACK_SNMP is not set
|
|
|
|
|
CONFIG_NF_CONNTRACK_PPTP=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NF_CONNTRACK_SANE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_NF_CONNTRACK_SIP is not set
|
|
|
|
|
CONFIG_NF_CONNTRACK_TFTP=y
|
|
|
|
|
CONFIG_NF_CT_NETLINK=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NETFILTER_TPROXY is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NETFILTER_XTABLES=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables combined modules
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NETFILTER_XT_MARK=y
|
|
|
|
|
CONFIG_NETFILTER_XT_CONNMARK=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables targets
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_CONNMARK=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_CT is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_HL=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_LED=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_MARK=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_TRACE=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_SECMARK is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables matches
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
|
|
|
|
|
# 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_ESP=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_HELPER=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_HL=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_MAC=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_MARK=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_POLICY=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QUOTA2=y
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_QUOTA2_LOG 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
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NETFILTER_XT_MATCH_STATE=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_STRING=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_TIME=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_U32=y
|
|
|
|
|
# CONFIG_IP_SET is not set
|
|
|
|
|
# CONFIG_IP_VS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IP: Netfilter Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NF_DEFRAG_IPV4=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_IPV4=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
|
|
|
|
|
# CONFIG_IP_NF_QUEUE is not set
|
|
|
|
|
CONFIG_IP_NF_IPTABLES=y
|
|
|
|
|
CONFIG_IP_NF_MATCH_AH=y
|
|
|
|
|
CONFIG_IP_NF_MATCH_ECN=y
|
|
|
|
|
CONFIG_IP_NF_MATCH_TTL=y
|
|
|
|
|
CONFIG_IP_NF_FILTER=y
|
|
|
|
|
CONFIG_IP_NF_TARGET_REJECT=y
|
|
|
|
|
CONFIG_IP_NF_TARGET_REJECT_SKERR=y
|
|
|
|
|
# CONFIG_IP_NF_TARGET_LOG is not set
|
|
|
|
|
# CONFIG_IP_NF_TARGET_ULOG is not set
|
|
|
|
|
CONFIG_NF_NAT=y
|
|
|
|
|
CONFIG_NF_NAT_NEEDED=y
|
|
|
|
|
CONFIG_IP_NF_TARGET_MASQUERADE=y
|
|
|
|
|
CONFIG_IP_NF_TARGET_NETMAP=y
|
|
|
|
|
CONFIG_IP_NF_TARGET_REDIRECT=y
|
|
|
|
|
CONFIG_NF_NAT_PROTO_GRE=y
|
|
|
|
|
CONFIG_NF_NAT_PROTO_UDPLITE=y
|
|
|
|
|
CONFIG_NF_NAT_FTP=y
|
|
|
|
|
CONFIG_NF_NAT_IRC=y
|
|
|
|
|
CONFIG_NF_NAT_TFTP=y
|
|
|
|
|
CONFIG_NF_NAT_AMANDA=y
|
|
|
|
|
CONFIG_NF_NAT_PPTP=y
|
|
|
|
|
CONFIG_NF_NAT_H323=y
|
|
|
|
|
# CONFIG_NF_NAT_SIP is not set
|
|
|
|
|
CONFIG_IP_NF_MANGLE=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_IP_NF_TARGET_ECN is not set
|
|
|
|
|
# CONFIG_IP_NF_TARGET_TTL is not set
|
|
|
|
|
CONFIG_IP_NF_RAW=y
|
|
|
|
|
# CONFIG_IP_NF_SECURITY is not set
|
|
|
|
|
CONFIG_IP_NF_ARPTABLES=y
|
|
|
|
|
CONFIG_IP_NF_ARPFILTER=y
|
|
|
|
|
CONFIG_IP_NF_ARP_MANGLE=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IPv6: Netfilter Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NF_DEFRAG_IPV6=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_IPV6=y
|
|
|
|
|
# CONFIG_IP6_NF_QUEUE is not set
|
|
|
|
|
CONFIG_IP6_NF_IPTABLES=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_AH=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_EUI64=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_FRAG=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_OPTS=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_HL=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_IPV6HEADER=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_MH=y
|
|
|
|
|
CONFIG_IP6_NF_MATCH_RT=y
|
|
|
|
|
CONFIG_IP6_NF_TARGET_HL=y
|
|
|
|
|
# CONFIG_IP6_NF_TARGET_LOG is not set
|
|
|
|
|
CONFIG_IP6_NF_FILTER=y
|
|
|
|
|
CONFIG_IP6_NF_TARGET_REJECT=y
|
|
|
|
|
# CONFIG_IP6_NF_TARGET_REJECT_SKERR is not set
|
|
|
|
|
CONFIG_IP6_NF_MANGLE=y
|
|
|
|
|
CONFIG_IP6_NF_RAW=y
|
|
|
|
|
# CONFIG_IP6_NF_SECURITY is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IP_DCCP is not set
|
|
|
|
|
# CONFIG_IP_SCTP is not set
|
|
|
|
|
# CONFIG_RDS is not set
|
|
|
|
|
# CONFIG_TIPC is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_ATM is not set
|
|
|
|
|
# CONFIG_L2TP is not set
|
|
|
|
|
# CONFIG_BRIDGE is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NET_DSA is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_VLAN_8021Q is not set
|
|
|
|
|
# CONFIG_DECNET is not set
|
|
|
|
|
# CONFIG_LLC2 is not set
|
|
|
|
|
# CONFIG_IPX is not set
|
|
|
|
|
# CONFIG_ATALK is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_X25 is not set
|
|
|
|
|
# CONFIG_LAPB is not set
|
|
|
|
|
# CONFIG_ECONET is not set
|
|
|
|
|
# CONFIG_WAN_ROUTER is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_PHONET is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IEEE802154 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_NET_SCHED=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Queueing/Scheduling
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NET_SCH_CBQ is not set
|
|
|
|
|
CONFIG_NET_SCH_HTB=y
|
|
|
|
|
# CONFIG_NET_SCH_HFSC is not set
|
|
|
|
|
# CONFIG_NET_SCH_PRIO is not set
|
|
|
|
|
# CONFIG_NET_SCH_MULTIQ is not set
|
|
|
|
|
# CONFIG_NET_SCH_RED is not set
|
|
|
|
|
CONFIG_NET_SCH_SFB=y
|
|
|
|
|
# CONFIG_NET_SCH_SFQ is not set
|
|
|
|
|
# CONFIG_NET_SCH_TEQL is not set
|
|
|
|
|
# CONFIG_NET_SCH_TBF is not set
|
|
|
|
|
# CONFIG_NET_SCH_GRED is not set
|
|
|
|
|
# CONFIG_NET_SCH_DSMARK is not set
|
|
|
|
|
# CONFIG_NET_SCH_NETEM is not set
|
|
|
|
|
# CONFIG_NET_SCH_DRR is not set
|
|
|
|
|
# CONFIG_NET_SCH_MQPRIO is not set
|
|
|
|
|
# CONFIG_NET_SCH_CHOKE is not set
|
|
|
|
|
# CONFIG_NET_SCH_QFQ is not set
|
|
|
|
|
CONFIG_NET_SCH_INGRESS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Classification
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NET_CLS=y
|
|
|
|
|
CONFIG_NET_CLS_BASIC=y
|
|
|
|
|
CONFIG_NET_CLS_TCINDEX=y
|
|
|
|
|
# CONFIG_NET_CLS_ROUTE4 is not set
|
|
|
|
|
# CONFIG_NET_CLS_FW is not set
|
|
|
|
|
CONFIG_NET_CLS_U32=y
|
|
|
|
|
# CONFIG_CLS_U32_PERF is not set
|
|
|
|
|
# CONFIG_CLS_U32_MARK is not set
|
|
|
|
|
# CONFIG_NET_CLS_RSVP is not set
|
|
|
|
|
# CONFIG_NET_CLS_RSVP6 is not set
|
|
|
|
|
# CONFIG_NET_CLS_FLOW is not set
|
|
|
|
|
# CONFIG_NET_CLS_CGROUP is not set
|
|
|
|
|
CONFIG_NET_EMATCH=y
|
|
|
|
|
CONFIG_NET_EMATCH_STACK=32
|
|
|
|
|
# CONFIG_NET_EMATCH_CMP is not set
|
|
|
|
|
# CONFIG_NET_EMATCH_NBYTE is not set
|
|
|
|
|
CONFIG_NET_EMATCH_U32=y
|
|
|
|
|
# CONFIG_NET_EMATCH_META is not set
|
|
|
|
|
# CONFIG_NET_EMATCH_TEXT is not set
|
|
|
|
|
CONFIG_NET_CLS_ACT=y
|
|
|
|
|
CONFIG_NET_ACT_POLICE=y
|
|
|
|
|
CONFIG_NET_ACT_GACT=y
|
|
|
|
|
# CONFIG_GACT_PROB is not set
|
|
|
|
|
CONFIG_NET_ACT_MIRRED=y
|
|
|
|
|
# CONFIG_NET_ACT_IPT is not set
|
|
|
|
|
# CONFIG_NET_ACT_NAT is not set
|
|
|
|
|
# CONFIG_NET_ACT_PEDIT is not set
|
|
|
|
|
# CONFIG_NET_ACT_SIMP is not set
|
|
|
|
|
# CONFIG_NET_ACT_SKBEDIT is not set
|
|
|
|
|
# CONFIG_NET_ACT_CSUM is not set
|
|
|
|
|
# CONFIG_NET_CLS_IND is not set
|
|
|
|
|
CONFIG_NET_SCH_FIFO=y
|
|
|
|
|
# CONFIG_DCB is not set
|
|
|
|
|
CONFIG_DNS_RESOLVER=y
|
|
|
|
|
# CONFIG_BATMAN_ADV is not set
|
|
|
|
|
CONFIG_HAVE_BPF_JIT=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Network testing
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NET_PKTGEN is not set
|
|
|
|
|
# CONFIG_HAMRADIO is not set
|
|
|
|
|
# CONFIG_CAN is not set
|
|
|
|
|
# CONFIG_IRDA is not set
|
|
|
|
|
CONFIG_BT=y
|
|
|
|
|
CONFIG_BT_L2CAP=y
|
|
|
|
|
CONFIG_BT_SCO=y
|
|
|
|
|
CONFIG_BT_RFCOMM=y
|
|
|
|
|
# CONFIG_BT_RFCOMM_TTY is not set
|
|
|
|
|
CONFIG_BT_BNEP=y
|
|
|
|
|
# CONFIG_BT_BNEP_MC_FILTER is not set
|
|
|
|
|
# CONFIG_BT_BNEP_PROTO_FILTER is not set
|
|
|
|
|
CONFIG_BT_HIDP=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bluetooth device drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_BT_HCISMD is not set
|
|
|
|
|
# CONFIG_BT_HCIBTUSB is not set
|
|
|
|
|
# CONFIG_BT_HCIBTSDIO is not set
|
|
|
|
|
CONFIG_BT_HCIUART=y
|
|
|
|
|
CONFIG_BT_HCIUART_H4=y
|
|
|
|
|
# CONFIG_BT_HCIUART_BCSP is not set
|
|
|
|
|
# CONFIG_BT_HCIUART_ATH3K is not set
|
|
|
|
|
# CONFIG_BT_HCIUART_LL is not set
|
|
|
|
|
# CONFIG_BT_HCIUART_IBS is not set
|
|
|
|
|
# CONFIG_BT_HCIBCM203X is not set
|
|
|
|
|
# CONFIG_BT_HCIBPA10X is not set
|
|
|
|
|
CONFIG_BT_MSM_SLEEP=y
|
|
|
|
|
# CONFIG_BT_HCIBFUSB is not set
|
|
|
|
|
# CONFIG_BT_HCIVHCI is not set
|
|
|
|
|
# CONFIG_BT_MRVL is not set
|
|
|
|
|
CONFIG_MSM_BT_POWER=y
|
|
|
|
|
# CONFIG_BT_WILINK is not set
|
|
|
|
|
CONFIG_BT_HID_BRCM=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_AF_RXRPC is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_FIB_RULES=y
|
|
|
|
|
CONFIG_WIRELESS=y
|
|
|
|
|
CONFIG_WIRELESS_EXT=y
|
|
|
|
|
CONFIG_WEXT_CORE=y
|
|
|
|
|
CONFIG_WEXT_PROC=y
|
|
|
|
|
CONFIG_WEXT_PRIV=y
|
|
|
|
|
CONFIG_CFG80211=y
|
|
|
|
|
# CONFIG_NL80211_TESTMODE is not set
|
|
|
|
|
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
|
|
|
|
|
# CONFIG_CFG80211_REG_DEBUG is not set
|
|
|
|
|
CONFIG_CFG80211_DEFAULT_PS=y
|
|
|
|
|
# CONFIG_CFG80211_DEBUGFS is not set
|
|
|
|
|
# CONFIG_CFG80211_INTERNAL_REGDB is not set
|
|
|
|
|
CONFIG_CFG80211_WEXT=y
|
|
|
|
|
CONFIG_WIRELESS_EXT_SYSFS=y
|
|
|
|
|
CONFIG_LIB80211=y
|
|
|
|
|
# CONFIG_LIB80211_DEBUG is not set
|
|
|
|
|
# CONFIG_CFG80211_ALLOW_RECONNECT is not set
|
|
|
|
|
# CONFIG_MAC80211 is not set
|
|
|
|
|
# CONFIG_WIMAX is not set
|
|
|
|
|
CONFIG_RFKILL=y
|
|
|
|
|
CONFIG_RFKILL_PM=y
|
|
|
|
|
CONFIG_RFKILL_LEDS=y
|
|
|
|
|
# CONFIG_RFKILL_INPUT is not set
|
|
|
|
|
# CONFIG_RFKILL_REGULATOR is not set
|
|
|
|
|
# CONFIG_RFKILL_GPIO is not set
|
|
|
|
|
# CONFIG_NET_9P is not set
|
|
|
|
|
# CONFIG_CAIF is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CEPH_LIB is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Device Drivers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Generic Driver Options
|
|
|
|
|
#
|
|
|
|
|
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
|
|
|
|
|
CONFIG_DEVTMPFS=y
|
|
|
|
|
# CONFIG_DEVTMPFS_MOUNT is not set
|
|
|
|
|
CONFIG_STANDALONE=y
|
|
|
|
|
CONFIG_PREVENT_FIRMWARE_BUILD=y
|
|
|
|
|
CONFIG_FW_LOADER=y
|
|
|
|
|
# CONFIG_FIRMWARE_IN_KERNEL is not set
|
|
|
|
|
CONFIG_EXTRA_FIRMWARE=""
|
|
|
|
|
# CONFIG_SYS_HYPERVISOR is not set
|
|
|
|
|
CONFIG_GENLOCK=y
|
|
|
|
|
CONFIG_GENLOCK_MISCDEVICE=y
|
|
|
|
|
CONFIG_SYNC=y
|
|
|
|
|
CONFIG_DMA_SHARED_BUFFER=y
|
|
|
|
|
CONFIG_SW_SYNC=y
|
|
|
|
|
# CONFIG_SW_SYNC_USER is not set
|
|
|
|
|
# CONFIG_CONNECTOR is not set
|
|
|
|
|
CONFIG_MTD=y
|
|
|
|
|
# CONFIG_MTD_DEBUG is not set
|
|
|
|
|
# CONFIG_MTD_REDBOOT_PARTS is not set
|
|
|
|
|
CONFIG_MTD_CMDLINE_PARTS=y
|
|
|
|
|
# CONFIG_MTD_AFS_PARTS is not set
|
|
|
|
|
# CONFIG_MTD_AR7_PARTS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# User Modules And Translation Layers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MTD_CHAR=y
|
|
|
|
|
CONFIG_MTD_BLKDEVS=y
|
|
|
|
|
CONFIG_MTD_BLOCK=y
|
|
|
|
|
# CONFIG_FTL is not set
|
|
|
|
|
# CONFIG_NFTL is not set
|
|
|
|
|
# CONFIG_INFTL is not set
|
|
|
|
|
# CONFIG_RFD_FTL is not set
|
|
|
|
|
# CONFIG_SSFDC is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SM_FTL is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_MTD_OOPS is not set
|
|
|
|
|
# CONFIG_MTD_SWAP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# RAM/ROM/Flash chip drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MTD_CFI is not set
|
|
|
|
|
# CONFIG_MTD_JEDECPROBE is not set
|
|
|
|
|
CONFIG_MTD_MAP_BANK_WIDTH_1=y
|
|
|
|
|
CONFIG_MTD_MAP_BANK_WIDTH_2=y
|
|
|
|
|
CONFIG_MTD_MAP_BANK_WIDTH_4=y
|
|
|
|
|
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
|
|
|
|
|
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
|
|
|
|
|
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
|
|
|
|
|
CONFIG_MTD_CFI_I1=y
|
|
|
|
|
CONFIG_MTD_CFI_I2=y
|
|
|
|
|
# CONFIG_MTD_CFI_I4 is not set
|
|
|
|
|
# CONFIG_MTD_CFI_I8 is not set
|
|
|
|
|
# CONFIG_MTD_RAM is not set
|
|
|
|
|
# CONFIG_MTD_ROM is not set
|
|
|
|
|
# CONFIG_MTD_ABSENT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Mapping drivers for chip access
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
|
|
|
|
|
# CONFIG_MTD_PLATRAM is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Self-contained MTD device drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MTD_MSM_NAND is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_MTD_DATAFLASH is not set
|
|
|
|
|
# CONFIG_MTD_M25P80 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_MTD_SST25L is not set
|
|
|
|
|
# CONFIG_MTD_SLRAM is not set
|
|
|
|
|
# CONFIG_MTD_PHRAM is not set
|
|
|
|
|
# CONFIG_MTD_MTDRAM is not set
|
|
|
|
|
# CONFIG_MTD_BLOCK2MTD is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Disk-On-Chip Device Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MTD_DOC2000 is not set
|
|
|
|
|
# CONFIG_MTD_DOC2001 is not set
|
|
|
|
|
# CONFIG_MTD_DOC2001PLUS is not set
|
|
|
|
|
# CONFIG_MTD_NAND_IDS is not set
|
|
|
|
|
# CONFIG_MTD_NAND is not set
|
|
|
|
|
# CONFIG_MTD_ONENAND is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# LPDDR flash memory drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MTD_LPDDR is not set
|
|
|
|
|
# CONFIG_MTD_UBI is not set
|
|
|
|
|
# CONFIG_PARPORT is not set
|
|
|
|
|
CONFIG_BLK_DEV=y
|
|
|
|
|
# CONFIG_BLK_DEV_COW_COMMON is not set
|
|
|
|
|
CONFIG_BLK_DEV_LOOP=y
|
|
|
|
|
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_BLK_DEV_NBD is not set
|
|
|
|
|
# CONFIG_BLK_DEV_UB is not set
|
|
|
|
|
CONFIG_BLK_DEV_RAM=y
|
|
|
|
|
CONFIG_BLK_DEV_RAM_COUNT=16
|
|
|
|
|
CONFIG_BLK_DEV_RAM_SIZE=8192
|
|
|
|
|
# CONFIG_BLK_DEV_XIP is not set
|
|
|
|
|
# CONFIG_CDROM_PKTCDVD is not set
|
|
|
|
|
# CONFIG_ATA_OVER_ETH is not set
|
|
|
|
|
# CONFIG_MG_DISK is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_BLK_DEV_RBD is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_LIS3LV02D is not set
|
|
|
|
|
CONFIG_MISC_DEVICES=y
|
|
|
|
|
# CONFIG_AD525X_DPOT is not set
|
|
|
|
|
CONFIG_ANDROID_PMEM=y
|
|
|
|
|
# CONFIG_INTEL_MID_PTI is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_ICS932S401 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_ENCLOSURE_SERVICES is not set
|
|
|
|
|
# CONFIG_APDS9802ALS is not set
|
|
|
|
|
# CONFIG_ISL29003 is not set
|
|
|
|
|
# CONFIG_ISL29020 is not set
|
|
|
|
|
# CONFIG_SENSORS_TSL2550 is not set
|
|
|
|
|
# CONFIG_SENSORS_BH1780 is not set
|
|
|
|
|
# CONFIG_SENSORS_BH1770 is not set
|
|
|
|
|
# CONFIG_SENSORS_APDS990X is not set
|
|
|
|
|
# CONFIG_HMC6352 is not set
|
|
|
|
|
# CONFIG_SENSORS_AK8975 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_DS1682 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_TI_DAC7512 is not set
|
|
|
|
|
CONFIG_UID_STAT=y
|
|
|
|
|
# CONFIG_BMP085 is not set
|
|
|
|
|
# CONFIG_WL127X_RFKILL is not set
|
|
|
|
|
# CONFIG_APANIC is not set
|
|
|
|
|
# CONFIG_TSIF is not set
|
|
|
|
|
CONFIG_HAPTIC_ISA1200=y
|
|
|
|
|
CONFIG_PMIC8058_PWM=y
|
|
|
|
|
# CONFIG_PMIC8058_VIBRATOR is not set
|
|
|
|
|
CONFIG_PMIC8XXX_VIBRATOR=y
|
|
|
|
|
# CONFIG_PMIC8XXX_NFC is not set
|
|
|
|
|
CONFIG_PMIC8XXX_UPL=y
|
|
|
|
|
# CONFIG_PMIC8058_XOADC is not set
|
|
|
|
|
# CONFIG_PMIC8058_MISC is not set
|
|
|
|
|
# CONFIG_PMIC8058_BATTALARM is not set
|
|
|
|
|
# CONFIG_TZCOM is not set
|
|
|
|
|
# CONFIG_QFP_FUSE is not set
|
|
|
|
|
CONFIG_CABLE_DETECT_8X55=y
|
|
|
|
|
CONFIG_CABLE_DETECT_ACCESSORY=y
|
|
|
|
|
# CONFIG_CABLE_DETECT_ACCESSORY_BY_ADC is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_C2PORT is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# EEPROM support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_EEPROM_AT24 is not set
|
|
|
|
|
# CONFIG_EEPROM_AT25 is not set
|
|
|
|
|
# CONFIG_EEPROM_LEGACY is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_EEPROM_MAX6875 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_EEPROM_93CX6 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IWMC3200TOP is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Texas Instruments shared transport line discipline
|
|
|
|
|
#
|
|
|
|
|
CONFIG_TI_ST=y
|
|
|
|
|
# CONFIG_SENSORS_LIS3_SPI is not set
|
|
|
|
|
# CONFIG_SENSORS_LIS3_I2C is not set
|
|
|
|
|
# CONFIG_MPU_SENSORS_MPU3050 is not set
|
|
|
|
|
# CONFIG_MPU_SENSORS_TIMERIRQ is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Motorola TS 27.010 Mux driver over UART
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MOT_FEAT_TS27010MUX_UART is not set
|
|
|
|
|
CONFIG_HAVE_IDE=y
|
|
|
|
|
# CONFIG_IDE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SCSI device support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SCSI_MOD=y
|
|
|
|
|
# CONFIG_RAID_ATTRS is not set
|
|
|
|
|
CONFIG_SCSI=y
|
|
|
|
|
CONFIG_SCSI_DMA=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SCSI_TGT is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SCSI_NETLINK is not set
|
|
|
|
|
CONFIG_SCSI_PROC_FS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SCSI support type (disk, tape, CD-ROM)
|
|
|
|
|
#
|
|
|
|
|
CONFIG_BLK_DEV_SD=y
|
|
|
|
|
# CONFIG_CHR_DEV_ST is not set
|
|
|
|
|
# CONFIG_CHR_DEV_OSST is not set
|
|
|
|
|
# CONFIG_BLK_DEV_SR is not set
|
|
|
|
|
CONFIG_CHR_DEV_SG=y
|
|
|
|
|
# CONFIG_CHR_DEV_SCH is not set
|
|
|
|
|
CONFIG_SCSI_MULTI_LUN=y
|
|
|
|
|
# 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
|
|
|
|
|
CONFIG_SCSI_LOWLEVEL=y
|
|
|
|
|
# CONFIG_ISCSI_TCP is not set
|
|
|
|
|
# CONFIG_ISCSI_BOOT_SYSFS is not set
|
|
|
|
|
# CONFIG_LIBFC is not set
|
|
|
|
|
# CONFIG_LIBFCOE is not set
|
|
|
|
|
# CONFIG_SCSI_DEBUG is not set
|
|
|
|
|
# CONFIG_SCSI_DH is not set
|
|
|
|
|
# CONFIG_SCSI_OSD_INITIATOR is not set
|
|
|
|
|
# CONFIG_ATA is not set
|
|
|
|
|
CONFIG_MD=y
|
|
|
|
|
# CONFIG_BLK_DEV_MD is not set
|
|
|
|
|
CONFIG_BLK_DEV_DM=y
|
|
|
|
|
# CONFIG_DM_DEBUG is not set
|
|
|
|
|
CONFIG_DM_CRYPT=y
|
|
|
|
|
# CONFIG_DM_SNAPSHOT is not set
|
|
|
|
|
# CONFIG_DM_MIRROR is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_DM_RAID is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_DM_ZERO is not set
|
|
|
|
|
# CONFIG_DM_MULTIPATH is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_DM_DELAY is not set
|
|
|
|
|
# CONFIG_DM_UEVENT is not set
|
|
|
|
|
# CONFIG_DM_FLAKEY is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_TARGET_CORE is not set
|
|
|
|
|
CONFIG_NETDEVICES=y
|
|
|
|
|
CONFIG_IFB=y
|
|
|
|
|
CONFIG_DUMMY=y
|
|
|
|
|
# CONFIG_BONDING is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_MACVLAN is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_EQUALIZER is not set
|
|
|
|
|
CONFIG_TUN=y
|
|
|
|
|
# CONFIG_VETH is not set
|
|
|
|
|
CONFIG_MII=y
|
|
|
|
|
# CONFIG_PHYLIB is not set
|
|
|
|
|
# CONFIG_NET_ETHERNET is not set
|
|
|
|
|
CONFIG_NETDEV_1000=y
|
|
|
|
|
# CONFIG_STMMAC_ETH is not set
|
|
|
|
|
# CONFIG_QFEC is not set
|
|
|
|
|
CONFIG_NETDEV_10000=y
|
|
|
|
|
CONFIG_WLAN=y
|
|
|
|
|
# CONFIG_USB_ZD1201 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_NET_RNDIS_WLAN is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_LIBRA_SDIOIF is not set
|
|
|
|
|
# CONFIG_BCMDHD_GOOGLE is not set
|
|
|
|
|
# CONFIG_ATH_COMMON is not set
|
|
|
|
|
# CONFIG_BCM4329 is not set
|
|
|
|
|
CONFIG_BCMDHD=y
|
|
|
|
|
CONFIG_BCMDHD_FW_PATH="/lib/firmware/postmarketos/bcmdhd/bcm4329/fw_bcm4329.bin"
|
|
|
|
|
CONFIG_BCMDHD_NVRAM_PATH="/proc/calibration"
|
|
|
|
|
# CONFIG_HOSTAP is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_IWM is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_LIBERTAS is not set
|
|
|
|
|
# CONFIG_WL12XX_PLATFORM_DATA is not set
|
|
|
|
|
# CONFIG_MWIFIEX is not set
|
|
|
|
|
# CONFIG_QUALCOMM_WLAN is not set
|
|
|
|
|
# CONFIG_BCM4329_248 is not set
|
|
|
|
|
# CONFIG_BCM4330B2 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Enable WiMAX (Networking options) to see the WiMAX drivers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Network Adapters
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_CATC is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_KAWETH is not set
|
|
|
|
|
# CONFIG_USB_PEGASUS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_RTL8150 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_USBNET is not set
|
|
|
|
|
# CONFIG_USB_HSO is not set
|
|
|
|
|
# CONFIG_USB_IPHETH is not set
|
|
|
|
|
# CONFIG_USB_NET_RAW_IP is not set
|
|
|
|
|
# CONFIG_WAN is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CAIF transport drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PPP=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_PPP_MULTILINK is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_PPP_FILTER is not set
|
|
|
|
|
# CONFIG_PPP_ASYNC is not set
|
|
|
|
|
# CONFIG_PPP_SYNC_TTY is not set
|
|
|
|
|
CONFIG_PPP_DEFLATE=y
|
|
|
|
|
CONFIG_PPP_BSDCOMP=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_PPP_MPPE is not set
|
|
|
|
|
# CONFIG_PPPOE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_PPPOLAC=y
|
|
|
|
|
CONFIG_PPPOPNS=y
|
|
|
|
|
# CONFIG_SLIP is not set
|
|
|
|
|
CONFIG_SLHC=y
|
|
|
|
|
# CONFIG_NETCONSOLE is not set
|
|
|
|
|
CONFIG_MSM_RMNET=y
|
|
|
|
|
# CONFIG_MSM_RMNET_DEBUG is not set
|
|
|
|
|
# CONFIG_NETPOLL is not set
|
|
|
|
|
# CONFIG_NET_POLL_CONTROLLER is not set
|
|
|
|
|
# CONFIG_KINETO_GAN is not set
|
|
|
|
|
# CONFIG_ISDN is not set
|
|
|
|
|
# CONFIG_PHONE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Input device support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_INPUT=y
|
|
|
|
|
CONFIG_INPUT_FF_MEMLESS=y
|
|
|
|
|
# CONFIG_INPUT_POLLDEV is not set
|
|
|
|
|
# CONFIG_INPUT_SPARSEKMAP 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
|
|
|
|
|
CONFIG_INPUT_KEYRESET=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Input Device Drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_INPUT_KEYBOARD=y
|
|
|
|
|
# CONFIG_KEYBOARD_ADP5588 is not set
|
|
|
|
|
# CONFIG_KEYBOARD_ADP5589 is not set
|
|
|
|
|
CONFIG_KEYBOARD_ATKBD=y
|
|
|
|
|
# CONFIG_KEYBOARD_QT1070 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_KEYBOARD_QT2160 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# 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_MATRIX is not set
|
|
|
|
|
# CONFIG_KEYBOARD_LM8323 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_PMIC8XXX is not set
|
|
|
|
|
# CONFIG_KEYBOARD_STOWAWAY is not set
|
|
|
|
|
# CONFIG_KEYBOARD_SUNKBD is not set
|
|
|
|
|
# CONFIG_KEYBOARD_XTKBD is not set
|
|
|
|
|
# CONFIG_KEYBOARD_QCIKBD is not set
|
|
|
|
|
# CONFIG_KEYBOARD_PMIC8058 is not set
|
|
|
|
|
# CONFIG_INPUT_MOUSE is not set
|
|
|
|
|
# CONFIG_INPUT_JOYSTICK is not set
|
|
|
|
|
# CONFIG_INPUT_TABLET is not set
|
|
|
|
|
CONFIG_INPUT_TOUCHSCREEN=y
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_DETECT_CABLE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_DETECT_USB is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_DETECT_USB_VBUS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_WLS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_224E is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ADS7846 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_AD7877 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_AD7879 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_MAXTOUCH is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CYPRESS_TMA is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_COMPATIBLE_REPORT is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_BU21013 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CYPRESS_CS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_EETI is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_FUJITSU is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_GUNZE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ELAN_KTF2K is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ELO is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MAX11801 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MCS5000 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MTOUCH is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_INEXIO is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MK712 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI is not set
|
|
|
|
|
CONFIG_TOUCHSCREEN_SYNAPTICS_3K=y
|
|
|
|
|
CONFIG_TOUCHSCREEN_SYNAPTICS_SWEEP2WAKE=y
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TSC2005 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TSC2007 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_W90X900 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ST1232 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TPS6507X is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CY8C_TS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CYTTSP_I2C is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_HIMAX is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_HIMAX_SH is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_HIMAX_SH2 is not set
|
|
|
|
|
CONFIG_INPUT_MISC=y
|
|
|
|
|
# CONFIG_INPUT_AD714X is not set
|
|
|
|
|
# CONFIG_INPUT_ATI_REMOTE is not set
|
|
|
|
|
# CONFIG_INPUT_ATI_REMOTE2 is not set
|
|
|
|
|
CONFIG_INPUT_KEYCHORD=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_INPUT_POWERMATE is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_INPUT_YEALINK is not set
|
|
|
|
|
# CONFIG_INPUT_CM109 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_INPUT_UINPUT=y
|
|
|
|
|
CONFIG_INPUT_GPIO=y
|
|
|
|
|
# CONFIG_INPUT_ISA1200_FF_MEMLESS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_INPUT_PCF8574 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_INPUT_PMIC8XXX_PWRKEY is not set
|
|
|
|
|
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
|
|
|
|
|
# CONFIG_INPUT_ADXL34X is not set
|
|
|
|
|
# CONFIG_INPUT_CMA3000 is not set
|
|
|
|
|
# CONFIG_PMIC8058_PWRKEY is not set
|
|
|
|
|
# CONFIG_PMIC8058_OTHC is not set
|
|
|
|
|
# CONFIG_INPUT_PMIC8058_VIBRA_MEMLESS is not set
|
|
|
|
|
# CONFIG_BOSCH_BMA150 is not set
|
|
|
|
|
# CONFIG_INPUT_CAPELLA_CM3602 is not set
|
|
|
|
|
CONFIG_INPUT_DUMMY_KEYPAD=y
|
|
|
|
|
CONFIG_POWER_KEY_LED=y
|
|
|
|
|
# CONFIG_INPUT_OPTICALJOYSTICK is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Hardware I/O ports
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SERIO=y
|
|
|
|
|
CONFIG_SERIO_SERPORT=y
|
|
|
|
|
CONFIG_SERIO_LIBPS2=y
|
|
|
|
|
# CONFIG_SERIO_RAW is not set
|
|
|
|
|
# CONFIG_SERIO_ALTERA_PS2 is not set
|
|
|
|
|
# CONFIG_SERIO_PS2MULT is not set
|
|
|
|
|
# CONFIG_GAMEPORT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Character devices
|
|
|
|
|
#
|
|
|
|
|
CONFIG_VT=y
|
|
|
|
|
CONFIG_CONSOLE_TRANSLATIONS=y
|
|
|
|
|
CONFIG_VT_CONSOLE=y
|
|
|
|
|
CONFIG_HW_CONSOLE=y
|
|
|
|
|
# CONFIG_VT_HW_CONSOLE_BINDING is not set
|
|
|
|
|
CONFIG_UNIX98_PTYS=y
|
|
|
|
|
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
|
|
|
|
|
# CONFIG_LEGACY_PTYS is not set
|
|
|
|
|
# CONFIG_SERIAL_NONSTANDARD is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_N_GSM is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_TRACE_SINK is not set
|
|
|
|
|
# CONFIG_DEVMEM is not set
|
|
|
|
|
# CONFIG_DEVKMEM is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Serial drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SERIAL_8250 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Non-8250 serial port support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SERIAL_MAX3100 is not set
|
|
|
|
|
# CONFIG_SERIAL_MAX3107 is not set
|
|
|
|
|
CONFIG_SERIAL_CORE=y
|
|
|
|
|
CONFIG_SERIAL_MSM=y
|
|
|
|
|
# CONFIG_SERIAL_MSM_CONSOLE is not set
|
|
|
|
|
CONFIG_SERIAL_MSM_HS=y
|
|
|
|
|
CONFIG_SERIAL_MSM_HS_PURE_ANDROID=y
|
|
|
|
|
# CONFIG_SERIAL_MSM_HS_IMC is not set
|
|
|
|
|
# CONFIG_SERIAL_MSM_CLOCK_CONTROL is not set
|
|
|
|
|
# CONFIG_SERIAL_MSM_HSL is not set
|
|
|
|
|
CONFIG_SERIAL_BCM_BT_LPM=y
|
|
|
|
|
# CONFIG_SERIAL_TIMBERDALE is not set
|
|
|
|
|
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
|
|
|
|
|
# CONFIG_SERIAL_ALTERA_UART is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SERIAL_IFX6X60 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SERIAL_MSM_SMD is not set
|
|
|
|
|
# CONFIG_SERIAL_XILINX_PS_UART is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Diag Support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_DIAG_CHAR=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# DIAG traffic over USB
|
|
|
|
|
#
|
|
|
|
|
CONFIG_DIAG_OVER_USB=y
|
|
|
|
|
# CONFIG_MODEM_DIAG_MASTER is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SDIO support for DIAG
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_TTY_PRINTK is not set
|
|
|
|
|
# CONFIG_HVC_DCC is not set
|
|
|
|
|
# CONFIG_IPMI_HANDLER is not set
|
|
|
|
|
# CONFIG_HW_RANDOM is not set
|
|
|
|
|
# CONFIG_R3964 is not set
|
|
|
|
|
# CONFIG_RAW_DRIVER is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_TCG_TPM is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_DCC_TTY is not set
|
|
|
|
|
# CONFIG_RAMOOPS is not set
|
|
|
|
|
# CONFIG_MSM_ROTATOR_LEGACY is not set
|
|
|
|
|
CONFIG_MSM_ROTATOR=y
|
|
|
|
|
CONFIG_MSM_ROTATOR_USE_IMEM=y
|
|
|
|
|
# CONFIG_MMC_GENERIC_CSDIO is not set
|
|
|
|
|
CONFIG_I2C=y
|
|
|
|
|
CONFIG_I2C_BOARDINFO=y
|
|
|
|
|
CONFIG_I2C_COMPAT=y
|
|
|
|
|
# CONFIG_I2C_CHARDEV is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_I2C_MUX is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Miscellaneous I2C Chip support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SENSORS_BMA150 is not set
|
|
|
|
|
CONFIG_SENSORS_ONLY_BMA250=y
|
|
|
|
|
# CONFIG_SENSORS_I2C_AK_BMA250 is not set
|
|
|
|
|
# CONFIG_SENSORS_AKM8975 is not set
|
|
|
|
|
# CONFIG_SENSORS_CAPSENSE is not set
|
|
|
|
|
# CONFIG_SENSORS_CAPSENSE_EXPRESS is not set
|
|
|
|
|
# CONFIG_SENSORS_AKM8975_PANA_GYRO is not set
|
|
|
|
|
# CONFIG_SENSORS_PANASONIC_GYRO is not set
|
|
|
|
|
CONFIG_TPS65200=y
|
|
|
|
|
# CONFIG_SENSORS_BMA250 is not set
|
|
|
|
|
# CONFIG_SENSORS_NFC_PN544 is not set
|
|
|
|
|
# CONFIG_INPUT_CAPELLA_CM3628 is not set
|
|
|
|
|
CONFIG_INPUT_CAPELLA_CM3629=y
|
|
|
|
|
# CONFIG_VP_A1026 is not set
|
|
|
|
|
# CONFIG_VP_A1028 is not set
|
|
|
|
|
CONFIG_AMP_TPA2051D3=y
|
|
|
|
|
# CONFIG_INPUT_ISL29028 is not set
|
|
|
|
|
# CONFIG_INPUT_ISL29029 is not set
|
|
|
|
|
# CONFIG_AMP_TPA2051D3_ON_GPIO is not set
|
|
|
|
|
# CONFIG_CODEC_AIC3254 is not set
|
|
|
|
|
# CONFIG_CODEC_AIC3008 is not set
|
|
|
|
|
CONFIG_SOUND_CONTROL_HAX_GPL=y
|
|
|
|
|
CONFIG_SND_CONTROL_HAS_BEATS=y
|
|
|
|
|
CONFIG_I2C_HELPER_AUTO=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C Hardware Bus support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C system bus drivers (mostly embedded / system-on-chip)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_DESIGNWARE is not set
|
|
|
|
|
# CONFIG_I2C_GPIO is not set
|
|
|
|
|
CONFIG_I2C_MSM=y
|
|
|
|
|
CONFIG_I2C_QUP=y
|
|
|
|
|
CONFIG_I2C_SSBI=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_I2C_OCORES is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_I2C_PCA_PLATFORM is not set
|
|
|
|
|
# CONFIG_I2C_PXA_PCI is not set
|
|
|
|
|
# CONFIG_I2C_SIMTEC is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_I2C_XILINX is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# External I2C/SMBus adapter drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_DIOLAN_U2C is not set
|
|
|
|
|
# CONFIG_I2C_PARPORT_LIGHT is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_I2C_TAOS_EVM is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_I2C_TINY_USB is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Other I2C/SMBus bus drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_DEBUG_CORE is not set
|
|
|
|
|
# CONFIG_I2C_DEBUG_ALGO is not set
|
|
|
|
|
# CONFIG_I2C_DEBUG_BUS is not set
|
|
|
|
|
CONFIG_SPI=y
|
|
|
|
|
CONFIG_SPI_MASTER=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI Master Controller Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SPI_ALTERA is not set
|
|
|
|
|
# CONFIG_SPI_BITBANG is not set
|
|
|
|
|
# CONFIG_SPI_GPIO is not set
|
|
|
|
|
# CONFIG_SPI_OC_TINY is not set
|
|
|
|
|
# CONFIG_SPI_AIC3254 is not set
|
|
|
|
|
# CONFIG_SPI_SP8803COM is not set
|
|
|
|
|
# CONFIG_SPI_PXA2XX_PCI is not set
|
|
|
|
|
CONFIG_SPI_QSD=y
|
|
|
|
|
# CONFIG_SPI_DISPLAY is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SPI_XILINX is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SPI_CRUCIAL_OJ is not set
|
|
|
|
|
# CONFIG_SPI_TOUCHSCREEN_NTRIG is not set
|
|
|
|
|
# CONFIG_SPI_DESIGNWARE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI Protocol Masters
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SPI_SPIDEV is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SPI_TLE62X0 is not set
|
|
|
|
|
# CONFIG_SLIMBUS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PPS support
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_PPS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PPS generators support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PTP clock support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Enable Device Drivers -> PPS to see the PTP clock options.
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARCH_REQUIRE_GPIOLIB=y
|
|
|
|
|
CONFIG_GPIOLIB=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_GPIO_SYSFS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Memory mapped GPIO drivers:
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_GPIO_BASIC_MMIO is not set
|
|
|
|
|
# CONFIG_GPIO_IT8761E is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
# 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_SX150X is not set
|
|
|
|
|
# CONFIG_GPIO_ADP5588 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PCI GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_GPIO_MAX7301 is not set
|
|
|
|
|
# CONFIG_GPIO_MCP23S08 is not set
|
|
|
|
|
# CONFIG_GPIO_MC33880 is not set
|
|
|
|
|
# CONFIG_GPIO_74X164 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# AC97 GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MODULbus GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
CONFIG_GPIO_PM8XXX=y
|
|
|
|
|
CONFIG_GPIO_PM8XXX_MPP=y
|
|
|
|
|
# CONFIG_GPIO_PM8XXX_RPC is not set
|
|
|
|
|
CONFIG_W1=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 1-wire Bus Masters
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_W1_MASTER_DS2490 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_W1_MASTER_DS2482 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_W1_MASTER_DS1WM is not set
|
|
|
|
|
# CONFIG_W1_MASTER_GPIO is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 1-wire Slaves
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_W1_SLAVE_THERM is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_SMEM is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2408 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2423 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2431 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2433 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2760 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_DS2780 is not set
|
|
|
|
|
# CONFIG_W1_SLAVE_BQ27000 is not set
|
|
|
|
|
CONFIG_POWER_SUPPLY=y
|
|
|
|
|
# CONFIG_POWER_SUPPLY_DEBUG is not set
|
|
|
|
|
# CONFIG_PDA_POWER is not set
|
|
|
|
|
# CONFIG_TEST_POWER is not set
|
|
|
|
|
# CONFIG_BATTERY_DS2780 is not set
|
|
|
|
|
# CONFIG_BATTERY_DS2782 is not set
|
|
|
|
|
# CONFIG_BATTERY_DS2746 is not set
|
|
|
|
|
# CONFIG_BATTERY_BQ20Z75 is not set
|
|
|
|
|
# CONFIG_BATTERY_BQ27x00 is not set
|
|
|
|
|
# CONFIG_BATTERY_MAX17040 is not set
|
|
|
|
|
# CONFIG_BATTERY_MAX17042 is not set
|
|
|
|
|
# CONFIG_CHARGER_ISP1704 is not set
|
|
|
|
|
# CONFIG_CHARGER_MAX8903 is not set
|
|
|
|
|
# CONFIG_CHARGER_GPIO is not set
|
|
|
|
|
# CONFIG_BATTERY_MSM is not set
|
|
|
|
|
# CONFIG_BATTERY_MSM8X60 is not set
|
|
|
|
|
# CONFIG_SMB137B_CHARGER is not set
|
|
|
|
|
# CONFIG_PM8058_FIX_USB is not set
|
|
|
|
|
# CONFIG_BATTERY_BQ27520 is not set
|
|
|
|
|
# CONFIG_BATTERY_BQ27541 is not set
|
|
|
|
|
CONFIG_HWMON=y
|
|
|
|
|
# CONFIG_HWMON_VID is not set
|
|
|
|
|
# CONFIG_SENSORS_WPCE775X is not set
|
|
|
|
|
# CONFIG_HWMON_DEBUG_CHIP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Native drivers
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_AD7414 is not set
|
|
|
|
|
# CONFIG_SENSORS_AD7418 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADCXX is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# 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
|
|
|
|
|
# CONFIG_SENSORS_ADM9240 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_ADT7411 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7462 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7470 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_ADT7475 is not set
|
|
|
|
|
# CONFIG_SENSORS_ASC7621 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_ATXP1 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# 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_G760A is not set
|
|
|
|
|
# CONFIG_SENSORS_GL518SM is not set
|
|
|
|
|
# CONFIG_SENSORS_GL520SM is not set
|
|
|
|
|
# CONFIG_SENSORS_GPIO_FAN is not set
|
|
|
|
|
# CONFIG_SENSORS_IT87 is not set
|
|
|
|
|
# CONFIG_SENSORS_JC42 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_LINEAGE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# 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_LTC4151 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_LTC4215 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4245 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4261 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_LM95241 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX1111 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX16065 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX1619 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_MAX6639 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX6642 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX6650 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_SENSORS_MSM_ADC=y
|
|
|
|
|
# CONFIG_SENSORS_PC87360 is not set
|
|
|
|
|
# CONFIG_SENSORS_PC87427 is not set
|
|
|
|
|
# CONFIG_SENSORS_PCF8591 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_PMBUS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_SHT15 is not set
|
|
|
|
|
# CONFIG_SENSORS_SHT21 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_SMM665 is not set
|
|
|
|
|
# CONFIG_SENSORS_DME1737 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# 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
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_SMSC47B397 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_SCH5627 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS1015 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS7828 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS7871 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_AMC6821 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_THMC50 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_TMP102 is not set
|
|
|
|
|
# CONFIG_SENSORS_TMP401 is not set
|
|
|
|
|
# CONFIG_SENSORS_TMP421 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_VT1211 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83781D is not set
|
|
|
|
|
# CONFIG_SENSORS_W83791D is not set
|
|
|
|
|
# CONFIG_SENSORS_W83792D is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_SENSORS_W83793 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83795 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83L785TS is not set
|
|
|
|
|
# CONFIG_SENSORS_W83L786NG is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_SENSORS_W83627HF is not set
|
|
|
|
|
# CONFIG_SENSORS_W83627EHF is not set
|
|
|
|
|
# CONFIG_THERMAL is not set
|
|
|
|
|
# CONFIG_WATCHDOG is not set
|
|
|
|
|
CONFIG_SSB_POSSIBLE=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Sonics Silicon Backplane
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SSB is not set
|
|
|
|
|
CONFIG_BCMA_POSSIBLE=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Broadcom specific AMBA
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_BCMA is not set
|
|
|
|
|
CONFIG_MFD_SUPPORT=y
|
|
|
|
|
CONFIG_MFD_CORE=y
|
|
|
|
|
# CONFIG_MFD_88PM860X is not set
|
|
|
|
|
# CONFIG_MFD_SM501 is not set
|
|
|
|
|
# CONFIG_MFD_ASIC3 is not set
|
|
|
|
|
# CONFIG_HTC_EGPIO is not set
|
|
|
|
|
# CONFIG_HTC_PASIC3 is not set
|
|
|
|
|
# CONFIG_HTC_I2CPLD is not set
|
|
|
|
|
# CONFIG_TPS6105X is not set
|
|
|
|
|
# CONFIG_TPS65010 is not set
|
|
|
|
|
CONFIG_TPS65023=y
|
|
|
|
|
CONFIG_PMIC8058=y
|
|
|
|
|
# CONFIG_MFD_MAX8957 is not set
|
|
|
|
|
# CONFIG_MARIMBA_TSADC is not set
|
|
|
|
|
# CONFIG_TPS6507X is not set
|
|
|
|
|
# CONFIG_MFD_TPS6586X is not set
|
|
|
|
|
CONFIG_MARIMBA_CORE=y
|
|
|
|
|
# CONFIG_MARIMBA_CODEC is not set
|
|
|
|
|
CONFIG_TIMPANI_CODEC=y
|
|
|
|
|
# CONFIG_TWL4030_CORE is not set
|
|
|
|
|
# CONFIG_MFD_STMPE is not set
|
|
|
|
|
# CONFIG_MFD_TC3589X is not set
|
|
|
|
|
# CONFIG_MFD_TMIO is not set
|
|
|
|
|
# CONFIG_MFD_T7L66XB is not set
|
|
|
|
|
# CONFIG_MFD_TC6387XB is not set
|
|
|
|
|
# CONFIG_MFD_TC6393XB is not set
|
|
|
|
|
# CONFIG_PMIC_DA903X is not set
|
|
|
|
|
# CONFIG_PMIC_ADP5520 is not set
|
|
|
|
|
# CONFIG_MFD_MAX8925 is not set
|
|
|
|
|
# CONFIG_MFD_MAX8997 is not set
|
|
|
|
|
# CONFIG_MFD_MAX8998 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_PCF50633 is not set
|
|
|
|
|
# CONFIG_MFD_MC13XXX is not set
|
|
|
|
|
# CONFIG_ABX500_CORE is not set
|
|
|
|
|
# CONFIG_EZX_PCAP is not set
|
|
|
|
|
# CONFIG_MFD_WL1273_CORE is not set
|
|
|
|
|
CONFIG_MFD_PM8XXX=y
|
|
|
|
|
# CONFIG_MFD_PM8921_CORE is not set
|
|
|
|
|
# CONFIG_MFD_PM8821_CORE is not set
|
|
|
|
|
# CONFIG_MFD_PM8018_CORE is not set
|
|
|
|
|
CONFIG_MFD_PM8XXX_IRQ=y
|
|
|
|
|
# CONFIG_MFD_TPS65910 is not set
|
|
|
|
|
# CONFIG_MFD_PM8XXX_DEBUG is not set
|
|
|
|
|
# CONFIG_MFD_PM8XXX_PWM is not set
|
|
|
|
|
# CONFIG_MFD_PM8XXX_MISC is not set
|
|
|
|
|
# CONFIG_MFD_PM8XXX_BATT_ALARM is not set
|
|
|
|
|
# CONFIG_WCD9310_CODEC is not set
|
|
|
|
|
CONFIG_REGULATOR=y
|
|
|
|
|
# CONFIG_REGULATOR_DEBUG is not set
|
|
|
|
|
# CONFIG_REGULATOR_DUMMY is not set
|
|
|
|
|
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
|
|
|
|
|
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
|
|
|
|
|
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
|
|
|
|
|
# CONFIG_REGULATOR_BQ24022 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_LP3971 is not set
|
|
|
|
|
# CONFIG_REGULATOR_LP3972 is not set
|
|
|
|
|
# CONFIG_REGULATOR_TPS65023 is not set
|
|
|
|
|
# CONFIG_REGULATOR_TPS6507X is not set
|
|
|
|
|
# CONFIG_REGULATOR_ISL6271A is not set
|
|
|
|
|
# CONFIG_REGULATOR_AD5398 is not set
|
|
|
|
|
# CONFIG_REGULATOR_TPS6524X is not set
|
|
|
|
|
# CONFIG_REGULATOR_GPIO is not set
|
|
|
|
|
# CONFIG_REGULATOR_PM8058_XO is not set
|
|
|
|
|
CONFIG_MEDIA_SUPPORT=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Multimedia core support
|
|
|
|
|
#
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_MEDIA_CONTROLLER is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_VIDEO_DEV is not set
|
|
|
|
|
# CONFIG_DVB_CORE is not set
|
|
|
|
|
# CONFIG_VIDEO_MEDIA is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Multimedia drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RC_CORE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Qualcomm MSM Camera And Video
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MSM_CAMERA=y
|
|
|
|
|
# CONFIG_MSM_CAMERA_DEBUG is not set
|
|
|
|
|
# CONFIG_MSM_CAMERA_V4L2 is not set
|
|
|
|
|
# CONFIG_MSM_CAMERA_LEGACY is not set
|
|
|
|
|
CONFIG_MSM_CAMERA_7X30=y
|
|
|
|
|
# CONFIG_MSM_CAMERA_8X60 is not set
|
|
|
|
|
CONFIG_CAMERA_MULTISHOT=y
|
|
|
|
|
CONFIG_FLASH_BACKLIGHT_OFF=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Camera Sensor Selection
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MT9T013 is not set
|
|
|
|
|
# CONFIG_MT9D112 is not set
|
|
|
|
|
# CONFIG_WEBCAM_OV9726 is not set
|
|
|
|
|
CONFIG_VX6953=y
|
|
|
|
|
CONFIG_SN12M0PZ=y
|
|
|
|
|
# CONFIG_MT9P012 is not set
|
|
|
|
|
CONFIG_MT9P012_KM=y
|
|
|
|
|
# CONFIG_MT9E013 is not set
|
|
|
|
|
# CONFIG_S5K3E2FX is not set
|
|
|
|
|
# CONFIG_S5K4E1 is not set
|
|
|
|
|
# CONFIG_S5K4E1GX is not set
|
|
|
|
|
# CONFIG_S5K6AAFX is not set
|
|
|
|
|
# CONFIG_S5K3H1GX is not set
|
|
|
|
|
# CONFIG_OV8810 is not set
|
|
|
|
|
# CONFIG_MSM_CAMERA_FLASH_SC628A is not set
|
|
|
|
|
# CONFIG_IMX072 is not set
|
|
|
|
|
# CONFIG_QS_MT9P017 is not set
|
|
|
|
|
# CONFIG_VB6801 is not set
|
|
|
|
|
# CONFIG_MSM_V4L2_VIDEO_OVERLAY_DEVICE is not set
|
|
|
|
|
# CONFIG_MSM_CAMERA_FLASH is not set
|
|
|
|
|
# CONFIG_MSM_CAMERA_SENSOR is not set
|
|
|
|
|
# CONFIG_MSM_ACTUATOR is not set
|
|
|
|
|
CONFIG_MSM_GEMINI=y
|
|
|
|
|
CONFIG_MSM_VPE=y
|
|
|
|
|
CONFIG_RAWCHIP=y
|
|
|
|
|
CONFIG_QUP_EXCLUSIVE_TO_CAMERA=y
|
|
|
|
|
# CONFIG_S5K3H2YX is not set
|
|
|
|
|
# CONFIG_S5K3H2YX_ACT is not set
|
|
|
|
|
CONFIG_S5K4E5YX=y
|
|
|
|
|
# CONFIG_S5K4E5YX_ACT is not set
|
|
|
|
|
# CONFIG_MT9V113 is not set
|
|
|
|
|
# CONFIG_S5K6A1GX is not set
|
|
|
|
|
# CONFIG_OV8830 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Graphics support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_DRM is not set
|
|
|
|
|
CONFIG_ION=y
|
|
|
|
|
CONFIG_ION_MSM=y
|
|
|
|
|
CONFIG_MSM_KGSL=y
|
|
|
|
|
# CONFIG_MSM_KGSL_CFF_DUMP is not set
|
|
|
|
|
# CONFIG_MSM_KGSL_PSTMRTMDMP_CP_STAT_NO_DETAIL is not set
|
|
|
|
|
# CONFIG_MSM_KGSL_PSTMRTMDMP_NO_IB_DUMP is not set
|
|
|
|
|
# CONFIG_MSM_KGSL_PSTMRTMDMP_RB_HEX is not set
|
|
|
|
|
CONFIG_MSM_KGSL_2D=y
|
|
|
|
|
# CONFIG_KGSL_PER_PROCESS_PAGE_TABLE is not set
|
|
|
|
|
CONFIG_MSM_KGSL_PAGE_TABLE_SIZE=0xFFF0000
|
|
|
|
|
CONFIG_MSM_KGSL_MMU_PAGE_FAULT=y
|
|
|
|
|
# CONFIG_MSM_KGSL_DISABLE_SHADOW_WRITES is not set
|
|
|
|
|
# CONFIG_VGASTATE is not set
|
|
|
|
|
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
|
|
|
|
|
CONFIG_FB=y
|
|
|
|
|
# CONFIG_FIRMWARE_EDID is not set
|
|
|
|
|
# CONFIG_FB_DDC is not set
|
|
|
|
|
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
|
|
|
|
|
CONFIG_FB_CFB_FILLRECT=y
|
|
|
|
|
CONFIG_FB_CFB_COPYAREA=y
|
|
|
|
|
CONFIG_FB_CFB_IMAGEBLIT=y
|
|
|
|
|
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
|
|
|
|
|
# CONFIG_FB_SYS_FILLRECT is not set
|
|
|
|
|
# CONFIG_FB_SYS_COPYAREA is not set
|
|
|
|
|
# CONFIG_FB_SYS_IMAGEBLIT is not set
|
|
|
|
|
# CONFIG_FB_FOREIGN_ENDIAN is not set
|
|
|
|
|
# CONFIG_FB_SYS_FOPS is not set
|
|
|
|
|
# CONFIG_FB_WMT_GE_ROPS is not set
|
|
|
|
|
# CONFIG_FB_SVGALIB is not set
|
|
|
|
|
# CONFIG_FB_MACMODES is not set
|
|
|
|
|
# CONFIG_FB_BACKLIGHT is not set
|
|
|
|
|
# CONFIG_FB_MODE_HELPERS is not set
|
|
|
|
|
# CONFIG_FB_TILEBLITTING is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Frame buffer hardware drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_FB_S1D13XXX is not set
|
|
|
|
|
# CONFIG_FB_TMIO is not set
|
|
|
|
|
# CONFIG_FB_UDL is not set
|
|
|
|
|
# CONFIG_FB_VIRTUAL is not set
|
|
|
|
|
# CONFIG_FB_METRONOME is not set
|
|
|
|
|
# CONFIG_FB_BROADSHEET is not set
|
|
|
|
|
CONFIG_MSM_VIDC=y
|
|
|
|
|
CONFIG_MSM_VIDC_720P=y
|
|
|
|
|
CONFIG_MSM_VIDC_VENC=y
|
|
|
|
|
CONFIG_MSM_VIDC_VDEC=y
|
|
|
|
|
CONFIG_FB_MSM=y
|
|
|
|
|
CONFIG_FB_MSM_LCDC=y
|
|
|
|
|
CONFIG_FB_MSM_OVERLAY=y
|
|
|
|
|
# CONFIG_FB_MSM_MDP_ABL is not set
|
|
|
|
|
CONFIG_MDP4_HW_VSYNC=y
|
|
|
|
|
# CONFIG_FB_MSM_NEW is not set
|
|
|
|
|
# CONFIG_FB_MSM_OVERLAY_LEGACY is not set
|
|
|
|
|
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Display device support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_DISPLAY_SUPPORT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Console display driver support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_DUMMY_CONSOLE=y
|
|
|
|
|
# CONFIG_FRAMEBUFFER_CONSOLE is not set
|
|
|
|
|
# CONFIG_LOGO is not set
|
|
|
|
|
CONFIG_SOUND=y
|
|
|
|
|
# CONFIG_SOUND_OSS_CORE is not set
|
|
|
|
|
CONFIG_SND=y
|
|
|
|
|
CONFIG_SND_TIMER=y
|
|
|
|
|
CONFIG_SND_PCM=y
|
|
|
|
|
CONFIG_SND_RAWMIDI=y
|
|
|
|
|
CONFIG_SND_JACK=y
|
|
|
|
|
# CONFIG_SND_SEQUENCER is not set
|
|
|
|
|
# CONFIG_SND_MIXER_OSS is not set
|
|
|
|
|
# CONFIG_SND_PCM_OSS is not set
|
|
|
|
|
# CONFIG_SND_HRTIMER is not set
|
|
|
|
|
# CONFIG_SND_DYNAMIC_MINORS is not set
|
|
|
|
|
CONFIG_SND_SUPPORT_OLD_API=y
|
|
|
|
|
CONFIG_SND_VERBOSE_PROCFS=y
|
|
|
|
|
# CONFIG_SND_VERBOSE_PRINTK is not set
|
|
|
|
|
# CONFIG_SND_DEBUG is not set
|
|
|
|
|
# CONFIG_SND_RAWMIDI_SEQ is not set
|
|
|
|
|
# CONFIG_SND_OPL3_LIB_SEQ is not set
|
|
|
|
|
# CONFIG_SND_OPL4_LIB_SEQ is not set
|
|
|
|
|
# CONFIG_SND_SBAWE_SEQ is not set
|
|
|
|
|
# CONFIG_SND_EMU10K1_SEQ is not set
|
|
|
|
|
# CONFIG_SND_DRIVERS is not set
|
|
|
|
|
# CONFIG_SND_ARM is not set
|
|
|
|
|
# CONFIG_SND_SPI is not set
|
|
|
|
|
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_SOC=y
|
|
|
|
|
# CONFIG_SND_SOC_CACHE_LZO is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MSM SoC Audio support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SND_MSM7KV2_SOC=y
|
|
|
|
|
CONFIG_SND_MSM7KV2_DAI_SOC=y
|
|
|
|
|
CONFIG_SND_MSM_SOC_MSM7KV2=y
|
|
|
|
|
# CONFIG_SND_MVS_SOC is not set
|
|
|
|
|
# CONFIG_SND_SOC_MSM8660 is not set
|
|
|
|
|
# CONFIG_SND_SOC_MSM8660_QRDC is not set
|
|
|
|
|
CONFIG_SND_SOC_I2C_AND_SPI=y
|
|
|
|
|
# CONFIG_SND_SOC_ALL_CODECS is not set
|
|
|
|
|
# CONFIG_SOUND_PRIME is not set
|
|
|
|
|
CONFIG_HID_SUPPORT=y
|
|
|
|
|
CONFIG_HID=y
|
|
|
|
|
CONFIG_HIDRAW=y
|
|
|
|
|
CONFIG_UHID=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Input Devices
|
|
|
|
|
#
|
|
|
|
|
CONFIG_USB_HID=y
|
|
|
|
|
# CONFIG_HID_PID is not set
|
|
|
|
|
CONFIG_USB_HIDDEV=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Special HID drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_HID_A4TECH=y
|
|
|
|
|
CONFIG_HID_ACRUX=y
|
|
|
|
|
CONFIG_HID_ACRUX_FF=y
|
|
|
|
|
CONFIG_HID_APPLE=y
|
|
|
|
|
CONFIG_HID_BELKIN=y
|
|
|
|
|
CONFIG_HID_CHERRY=y
|
|
|
|
|
CONFIG_HID_CHICONY=y
|
|
|
|
|
CONFIG_HID_PRODIKEYS=y
|
|
|
|
|
CONFIG_HID_CYPRESS=y
|
|
|
|
|
CONFIG_HID_DRAGONRISE=y
|
|
|
|
|
CONFIG_DRAGONRISE_FF=y
|
|
|
|
|
CONFIG_HID_EMS_FF=y
|
|
|
|
|
CONFIG_HID_ELECOM=y
|
|
|
|
|
CONFIG_HID_EZKEY=y
|
|
|
|
|
CONFIG_HID_KEYTOUCH=y
|
|
|
|
|
CONFIG_HID_KYE=y
|
|
|
|
|
CONFIG_HID_UCLOGIC=y
|
|
|
|
|
CONFIG_HID_WALTOP=y
|
|
|
|
|
CONFIG_HID_GYRATION=y
|
|
|
|
|
CONFIG_HID_TWINHAN=y
|
|
|
|
|
CONFIG_HID_KENSINGTON=y
|
|
|
|
|
CONFIG_HID_LCPOWER=y
|
|
|
|
|
CONFIG_HID_LOGITECH=y
|
|
|
|
|
CONFIG_LOGITECH_FF=y
|
|
|
|
|
CONFIG_LOGIRUMBLEPAD2_FF=y
|
|
|
|
|
CONFIG_LOGIG940_FF=y
|
|
|
|
|
# CONFIG_LOGIWII_FF is not set
|
|
|
|
|
CONFIG_HID_MAGICMOUSE=y
|
|
|
|
|
CONFIG_HID_MICROSOFT=y
|
|
|
|
|
CONFIG_HID_MONTEREY=y
|
|
|
|
|
CONFIG_HID_MULTITOUCH=y
|
|
|
|
|
CONFIG_HID_NTRIG=y
|
|
|
|
|
CONFIG_HID_ORTEK=y
|
|
|
|
|
CONFIG_HID_PANTHERLORD=y
|
|
|
|
|
CONFIG_PANTHERLORD_FF=y
|
|
|
|
|
CONFIG_HID_PETALYNX=y
|
|
|
|
|
CONFIG_HID_PICOLCD=y
|
|
|
|
|
# CONFIG_HID_PICOLCD_FB is not set
|
|
|
|
|
# CONFIG_HID_PICOLCD_LEDS is not set
|
|
|
|
|
# CONFIG_HID_QUANTA is not set
|
|
|
|
|
CONFIG_HID_ROCCAT=y
|
|
|
|
|
# CONFIG_HID_ROCCAT_ARVO is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_KONE is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_KONEPLUS is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_KOVAPLUS is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_PYRA is not set
|
|
|
|
|
CONFIG_HID_SAMSUNG=y
|
|
|
|
|
CONFIG_HID_SONY=y
|
|
|
|
|
CONFIG_HID_SUNPLUS=y
|
|
|
|
|
CONFIG_HID_GREENASIA=y
|
|
|
|
|
CONFIG_GREENASIA_FF=y
|
|
|
|
|
CONFIG_HID_SMARTJOYPLUS=y
|
|
|
|
|
CONFIG_SMARTJOYPLUS_FF=y
|
|
|
|
|
CONFIG_HID_TOPSEED=y
|
|
|
|
|
CONFIG_HID_THRUSTMASTER=y
|
|
|
|
|
# CONFIG_THRUSTMASTER_FF is not set
|
|
|
|
|
CONFIG_HID_WACOM=y
|
|
|
|
|
# CONFIG_HID_WACOM_POWER_SUPPLY is not set
|
|
|
|
|
# CONFIG_HID_ZEROPLUS is not set
|
|
|
|
|
# CONFIG_HID_ZYDACRON is not set
|
|
|
|
|
CONFIG_USB_SUPPORT=y
|
|
|
|
|
CONFIG_USB_ARCH_HAS_HCD=y
|
|
|
|
|
# CONFIG_USB_ARCH_HAS_OHCI is not set
|
|
|
|
|
CONFIG_USB_ARCH_HAS_EHCI=y
|
|
|
|
|
CONFIG_USB=y
|
|
|
|
|
# CONFIG_USB_DEBUG is not set
|
|
|
|
|
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Miscellaneous USB options
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USB_DEVICEFS is not set
|
|
|
|
|
CONFIG_USB_DEVICE_CLASS=y
|
|
|
|
|
# CONFIG_USB_DYNAMIC_MINORS is not set
|
|
|
|
|
# CONFIG_USB_SUSPEND is not set
|
|
|
|
|
# CONFIG_USB_OTG_WHITELIST is not set
|
|
|
|
|
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
|
|
|
|
|
# CONFIG_USB_MON is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_WUSB is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_WUSB_CBAF is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Host Controller Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USB_C67X00_HCD is not set
|
|
|
|
|
CONFIG_USB_EHCI_HCD=y
|
|
|
|
|
CONFIG_USB_EHCI_EHSET=y
|
|
|
|
|
CONFIG_USB_EHCI_ROOT_HUB_TT=y
|
|
|
|
|
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
|
|
|
|
|
CONFIG_USB_EHCI_MSM=y
|
|
|
|
|
# CONFIG_USB_EHCI_MSM_HSIC is not set
|
|
|
|
|
# CONFIG_USB_OXU210HP_HCD is not set
|
|
|
|
|
# CONFIG_USB_ISP116X_HCD is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_ISP1760_HCD is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_ISP1362_HCD is not set
|
|
|
|
|
# CONFIG_USB_SL811_HCD is not set
|
|
|
|
|
# CONFIG_USB_R8A66597_HCD is not set
|
|
|
|
|
# CONFIG_USB_PEHCI_HCD is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_HWA_HCD is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_MUSB_HDRC 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_LIBUSUAL is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Imaging devices
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USB_MDC800 is not set
|
|
|
|
|
# CONFIG_USB_MICROTEK 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_RIO500 is not set
|
|
|
|
|
# CONFIG_USB_LEGOTOWER is not set
|
|
|
|
|
# CONFIG_USB_LCD is not set
|
|
|
|
|
# CONFIG_USB_LED 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
|
|
|
|
|
# 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_QCOM_DIAG_BRIDGE is not set
|
|
|
|
|
# CONFIG_USB_QCOM_MDM_BRIDGE is not set
|
|
|
|
|
CONFIG_USB_GADGET=y
|
|
|
|
|
# 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_SELECTED=y
|
|
|
|
|
# CONFIG_USB_GADGET_FUSB300 is not set
|
|
|
|
|
# CONFIG_USB_GADGET_R8A66597 is not set
|
|
|
|
|
# CONFIG_USB_GADGET_PXA_U2O is not set
|
|
|
|
|
# CONFIG_USB_GADGET_M66592 is not set
|
|
|
|
|
CONFIG_USB_GADGET_CI13XXX_MSM=y
|
|
|
|
|
CONFIG_USB_CI13XXX_MSM=y
|
|
|
|
|
# CONFIG_USB_GADGET_MSM_72K is not set
|
|
|
|
|
# CONFIG_USB_GADGET_DUMMY_HCD is not set
|
|
|
|
|
CONFIG_USB_GADGET_DUALSPEED=y
|
|
|
|
|
# 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
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_GADGETFS is not set
|
|
|
|
|
# CONFIG_USB_FUNCTIONFS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_FILE_STORAGE is not set
|
|
|
|
|
# CONFIG_USB_MASS_STORAGE is not set
|
|
|
|
|
# CONFIG_USB_G_SERIAL is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USB_MIDI_GADGET is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_USB_G_PRINTER is not set
|
|
|
|
|
CONFIG_USB_G_ANDROID=y
|
|
|
|
|
# CONFIG_USB_ANDROID_ACM is not set
|
|
|
|
|
CONFIG_USB_ANDROID_ADB=y
|
|
|
|
|
CONFIG_USB_ANDROID_DIAG=y
|
|
|
|
|
# CONFIG_USB_ANDROID_MDM9K_DIAG is not set
|
|
|
|
|
# CONFIG_USB_ANDROID_MDM9K_MODEM is not set
|
|
|
|
|
CONFIG_USB_ANDROID_MASS_STORAGE=y
|
|
|
|
|
CONFIG_USB_ANDROID_MTP=y
|
|
|
|
|
CONFIG_USB_ANDROID_RNDIS=y
|
|
|
|
|
# CONFIG_USB_ANDROID_RMNET is not set
|
|
|
|
|
CONFIG_RMNET_SMD_CTL_CHANNEL=""
|
|
|
|
|
CONFIG_RMNET_SMD_DATA_CHANNEL=""
|
|
|
|
|
# CONFIG_USB_ANDROID_RMNET_CTRL_SMD is not set
|
|
|
|
|
# CONFIG_USB_F_SERIAL is not set
|
|
|
|
|
CONFIG_MODEM_SUPPORT=y
|
|
|
|
|
CONFIG_USB_ANDROID_SERIAL=y
|
|
|
|
|
# CONFIG_USB_ANDROID_PROJECTOR is not set
|
|
|
|
|
# CONFIG_USB_ANDROID_ECM is not set
|
|
|
|
|
# CONFIG_USB_F_SERIAL_SMD is not set
|
|
|
|
|
# CONFIG_USB_ANDROID_USBNET is not set
|
|
|
|
|
# CONFIG_USB_CDC_COMPOSITE 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_ACCESSORY_DETECT=y
|
|
|
|
|
CONFIG_USB_ACCESSORY_DETECT_BY_ADC=y
|
|
|
|
|
# CONFIG_USB_CSW_HACK is not set
|
|
|
|
|
# CONFIG_USB_HUB is not set
|
|
|
|
|
# CONFIG_USB_GADGET_VERIZON_PRODUCT_ID is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# OTG and related infrastructure
|
|
|
|
|
#
|
|
|
|
|
CONFIG_USB_OTG_UTILS=y
|
|
|
|
|
# CONFIG_USB_OTG_WAKELOCK is not set
|
|
|
|
|
# CONFIG_USB_GPIO_VBUS is not set
|
|
|
|
|
# CONFIG_USB_ULPI is not set
|
|
|
|
|
# CONFIG_USB_MSM_OTG_72K is not set
|
|
|
|
|
# CONFIG_NOP_USB_XCEIV is not set
|
|
|
|
|
CONFIG_USB_MSM_OTG=y
|
|
|
|
|
# CONFIG_USB_MSM_ACA is not set
|
|
|
|
|
CONFIG_MMC=y
|
|
|
|
|
# CONFIG_MMC_DEBUG is not set
|
|
|
|
|
CONFIG_MMC_PERF_PROFILING=y
|
|
|
|
|
CONFIG_ZIMMER=y
|
|
|
|
|
CONFIG_MMC_UNSAFE_RESUME=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_MMC_CLKGATE is not set
|
|
|
|
|
# CONFIG_MMC_EMBEDDED_SDIO is not set
|
|
|
|
|
# CONFIG_MMC_PARANOID_SD_INIT is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MMC/SD/SDIO Card Drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MMC_BLOCK=y
|
|
|
|
|
CONFIG_MMC_BLOCK_MINORS=64
|
|
|
|
|
CONFIG_MMC_BLOCK_BOUNCE=y
|
|
|
|
|
CONFIG_MMC_BLOCK_DEFERRED_RESUME=y
|
|
|
|
|
# CONFIG_SDIO_UART is not set
|
|
|
|
|
# CONFIG_MMC_TEST is not set
|
|
|
|
|
# CONFIG_MMC_TI_SDIO_ADAPT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MMC/SD/SDIO Host Controller Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MMC_SDHCI is not set
|
|
|
|
|
CONFIG_MMC_MSM=y
|
|
|
|
|
CONFIG_MMC_MSM_SDIO_SUPPORT=y
|
|
|
|
|
CONFIG_MMC_MSM_CARD_HW_DETECTION=y
|
|
|
|
|
# CONFIG_MMC_MSM_SDC1_SUPPORT is not set
|
|
|
|
|
CONFIG_MMC_MSM_SDC2_SUPPORT=y
|
|
|
|
|
CONFIG_MMC_MSM_SDC2_8_BIT_SUPPORT=y
|
|
|
|
|
CONFIG_MMC_MSM_SDC3_SUPPORT=y
|
|
|
|
|
# CONFIG_MMC_MSM_SDC3_8_BIT_SUPPORT is not set
|
|
|
|
|
# CONFIG_MMC_MSM_SDC3_WP_SUPPORT is not set
|
|
|
|
|
CONFIG_MMC_MSM_SDC4_SUPPORT=y
|
|
|
|
|
# CONFIG_MMC_MSM_SDC4_8_BIT_SUPPORT is not set
|
|
|
|
|
# CONFIG_MMC_MSM_SDC5_SUPPORT is not set
|
|
|
|
|
# CONFIG_MMC_DW is not set
|
|
|
|
|
# CONFIG_MMC_VUB300 is not set
|
|
|
|
|
# CONFIG_MMC_USHC is not set
|
|
|
|
|
# CONFIG_MMC_ATHEROS_SDIO is not set
|
|
|
|
|
# CONFIG_MEMSTICK is not set
|
|
|
|
|
CONFIG_NEW_LEDS=y
|
|
|
|
|
CONFIG_LEDS_CLASS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# LED drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_LEDS_LM3530 is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_LEDS_PCA9532 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_LEDS_GPIO=y
|
|
|
|
|
# CONFIG_LEDS_MSM_PDM is not set
|
|
|
|
|
CONFIG_LEDS_GPIO_PLATFORM=y
|
|
|
|
|
# CONFIG_LEDS_LP3944 is not set
|
|
|
|
|
# CONFIG_LEDS_CPLD is not set
|
|
|
|
|
# CONFIG_LEDS_LP5521 is not set
|
|
|
|
|
# CONFIG_LEDS_LP5523 is not set
|
|
|
|
|
# CONFIG_LEDS_PCA955X is not set
|
|
|
|
|
# CONFIG_LEDS_PM8XXX is not set
|
|
|
|
|
# CONFIG_LEDS_DAC124S085 is not set
|
|
|
|
|
# CONFIG_LEDS_REGULATOR is not set
|
|
|
|
|
# CONFIG_LEDS_BD2802 is not set
|
|
|
|
|
# CONFIG_LEDS_MSM_PMIC is not set
|
|
|
|
|
# CONFIG_LEDS_PMIC8058 is not set
|
|
|
|
|
# CONFIG_LEDS_LT3593 is not set
|
|
|
|
|
CONFIG_LEDS_TRIGGERS=y
|
|
|
|
|
# CONFIG_LEDS_PM8029 is not set
|
|
|
|
|
CONFIG_LEDS_PM8058=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# LED Triggers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_TIMER is not set
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_GPIO is not set
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
|
|
|
|
|
# CONFIG_LEDS_TRIGGER_SLEEP is not set
|
|
|
|
|
CONFIG_FLASHLIGHT_TPS61310=y
|
|
|
|
|
# CONFIG_FLASHLIGHT_AAT1271 is not set
|
|
|
|
|
# CONFIG_FLASHLIGHT_AAT1277 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# iptables trigger is under Netfilter config (LED target)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NFC_DEVICES is not set
|
|
|
|
|
CONFIG_SWITCH=y
|
|
|
|
|
CONFIG_SWITCH_GPIO=y
|
|
|
|
|
# CONFIG_ACCESSIBILITY is not set
|
|
|
|
|
CONFIG_RTC_LIB=y
|
|
|
|
|
CONFIG_RTC_CLASS=y
|
|
|
|
|
CONFIG_RTC_HCTOSYS=y
|
|
|
|
|
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
|
|
|
|
|
# CONFIG_RTC_DEBUG is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# RTC interfaces
|
|
|
|
|
#
|
|
|
|
|
CONFIG_RTC_INTF_SYSFS=y
|
|
|
|
|
CONFIG_RTC_INTF_PROC=y
|
|
|
|
|
CONFIG_RTC_INTF_DEV=y
|
|
|
|
|
CONFIG_RTC_INTF_ALARM=y
|
|
|
|
|
CONFIG_RTC_INTF_ALARM_DEV=y
|
|
|
|
|
# CONFIG_ANDROID_RTC_CHANGE_WAIT is not set
|
|
|
|
|
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
|
|
|
|
|
# CONFIG_RTC_DRV_TEST is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C RTC drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RTC_DRV_DS1307 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS1374 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS1672 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS3232 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_X1205 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_RX8581 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_RX8025 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_EM3027 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_RV3029C2 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI RTC drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RTC_DRV_M41T93 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_M41T94 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS1305 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS1390 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_MAX6902 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_R9701 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_RS5C348 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_DS3234 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_PCF2123 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_DS1742 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
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# on-CPU RTC drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_RTC_DRV_MSM=y
|
|
|
|
|
CONFIG_RTC_SECURE_TIME_SUPPORT=y
|
|
|
|
|
CONFIG_RTC_DRV_MSM7X00A=y
|
|
|
|
|
# CONFIG_RTC_PM8058 is not set
|
|
|
|
|
# CONFIG_RTC_DRV_PM8XXX is not set
|
|
|
|
|
# CONFIG_DMADEVICES is not set
|
|
|
|
|
# CONFIG_AUXDISPLAY is not set
|
|
|
|
|
# CONFIG_UIO is not set
|
|
|
|
|
CONFIG_STAGING=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_USBIP_CORE is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_PRISM2_USB is not set
|
|
|
|
|
# CONFIG_ECHO is not set
|
|
|
|
|
# CONFIG_BRCMUTIL is not set
|
|
|
|
|
# CONFIG_ASUS_OLED is not set
|
|
|
|
|
# CONFIG_R8712U is not set
|
|
|
|
|
# CONFIG_TRANZPORT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Android
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ANDROID=y
|
|
|
|
|
CONFIG_ANDROID_BINDER_IPC=y
|
|
|
|
|
# CONFIG_ANDROID_LOGGER is not set
|
|
|
|
|
# CONFIG_ANDROID_RAM_CONSOLE is not set
|
|
|
|
|
CONFIG_ANDROID_TIMED_OUTPUT=y
|
|
|
|
|
CONFIG_ANDROID_TIMED_GPIO=y
|
|
|
|
|
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
|
|
|
|
|
CONFIG_ANDROID_LOW_MEMORY_KILLER_AUTODETECT_OOM_ADJ_VALUES=y
|
|
|
|
|
CONFIG_ANDROID_RADIO_LOG_SIZE=256
|
|
|
|
|
CONFIG_ANDROID_DEVICE_LOG_SIZE=256
|
|
|
|
|
CONFIG_ANDROID_SYSTEM_LOG_SIZE=256
|
|
|
|
|
CONFIG_ANDROID_EVENTS_LOG_SIZE=256
|
|
|
|
|
# CONFIG_POHMELFS is not set
|
|
|
|
|
# CONFIG_LINE6_USB is not set
|
|
|
|
|
# CONFIG_IIO is not set
|
|
|
|
|
# CONFIG_SNAPPY_COMPRESS is not set
|
|
|
|
|
# CONFIG_SNAPPY_DECOMPRESS is not set
|
|
|
|
|
CONFIG_ZRAM=y
|
|
|
|
|
# CONFIG_ZRAM_DEBUG is not set
|
|
|
|
|
CONFIG_ZRAM_FOR_ANDROID=y
|
|
|
|
|
CONFIG_ZSMALLOC=y
|
|
|
|
|
# CONFIG_FB_SM7XX is not set
|
|
|
|
|
CONFIG_MACH_NO_WESTBRIDGE=y
|
|
|
|
|
# CONFIG_ATH6K_LEGACY is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_BCM_WIMAX is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_FT1000 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Speakup console speech
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SPEAKUP is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CLEARPAD_TM1217 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Altera FPGA firmware download module
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_ALTERA_STAPL is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Qualcomm MSM specific device drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MSM_SSBI=y
|
|
|
|
|
CONFIG_CLKDEV_LOOKUP=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# File systems
|
|
|
|
|
#
|
|
|
|
|
CONFIG_VFS_CACHE_PRESSURE=100
|
|
|
|
|
# CONFIG_EXT2_FS is not set
|
|
|
|
|
# CONFIG_EXT3_FS is not set
|
|
|
|
|
CONFIG_EXT4_FS=y
|
|
|
|
|
CONFIG_EXT4_USE_FOR_EXT23=y
|
|
|
|
|
CONFIG_EXT4_FS_XATTR=y
|
|
|
|
|
# CONFIG_EXT4_FS_POSIX_ACL is not set
|
|
|
|
|
CONFIG_EXT4_FS_SECURITY=y
|
|
|
|
|
# CONFIG_EXT4_DEBUG is not set
|
|
|
|
|
CONFIG_EXT4_E2FSCK_RECOVER=y
|
|
|
|
|
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
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_BTRFS_FS is not set
|
|
|
|
|
# CONFIG_NILFS2_FS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
CONFIG_FS_POSIX_ACL=y
|
|
|
|
|
CONFIG_FILE_LOCKING=y
|
|
|
|
|
CONFIG_FSNOTIFY=y
|
|
|
|
|
# CONFIG_DNOTIFY is not set
|
|
|
|
|
CONFIG_INOTIFY_USER=y
|
|
|
|
|
# CONFIG_FANOTIFY is not set
|
|
|
|
|
# CONFIG_QUOTA is not set
|
|
|
|
|
# CONFIG_QUOTACTL is not set
|
|
|
|
|
# CONFIG_AUTOFS4_FS is not set
|
|
|
|
|
CONFIG_FUSE_FS=y
|
|
|
|
|
# CONFIG_CUSE is not set
|
|
|
|
|
CONFIG_GENERIC_ACL=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Caches
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_FSCACHE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CD-ROM/DVD Filesystems
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_ISO9660_FS is not set
|
|
|
|
|
# CONFIG_UDF_FS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# DOS/FAT/NT Filesystems
|
|
|
|
|
#
|
|
|
|
|
CONFIG_FAT_FS=y
|
|
|
|
|
CONFIG_MSDOS_FS=y
|
|
|
|
|
CONFIG_VFAT_FS=y
|
|
|
|
|
CONFIG_FAT_DEFAULT_CODEPAGE=437
|
|
|
|
|
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
|
|
|
|
|
# CONFIG_NTFS_FS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Pseudo filesystems
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PROC_FS=y
|
|
|
|
|
CONFIG_PROC_SYSCTL=y
|
|
|
|
|
CONFIG_PROC_PAGE_MONITOR=y
|
|
|
|
|
CONFIG_SYSFS=y
|
|
|
|
|
CONFIG_TMPFS=y
|
|
|
|
|
CONFIG_TMPFS_POSIX_ACL=y
|
|
|
|
|
CONFIG_TMPFS_XATTR=y
|
|
|
|
|
# CONFIG_HUGETLB_PAGE is not set
|
|
|
|
|
# CONFIG_CONFIGFS_FS is not set
|
|
|
|
|
CONFIG_MISC_FILESYSTEMS=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_ADFS_FS is not set
|
|
|
|
|
# CONFIG_AFFS_FS is not set
|
|
|
|
|
# CONFIG_ECRYPT_FS is not set
|
|
|
|
|
# CONFIG_HFS_FS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_HFSPLUS_FS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_BEFS_FS is not set
|
|
|
|
|
# CONFIG_BFS_FS is not set
|
|
|
|
|
# CONFIG_EFS_FS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_YAFFS_FS is not set
|
|
|
|
|
# CONFIG_JFFS2_FS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_LOGFS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_CRAMFS is not set
|
|
|
|
|
# CONFIG_SQUASHFS is not set
|
|
|
|
|
# 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_ROMFS_FS is not set
|
|
|
|
|
# CONFIG_PSTORE is not set
|
|
|
|
|
# CONFIG_SYSV_FS is not set
|
|
|
|
|
# CONFIG_UFS_FS is not set
|
|
|
|
|
CONFIG_F2FS_FS=y
|
|
|
|
|
CONFIG_F2FS_STAT_FS=y
|
|
|
|
|
CONFIG_F2FS_FS_XATTR=y
|
|
|
|
|
CONFIG_F2FS_FS_POSIX_ACL=y
|
|
|
|
|
CONFIG_F2FS_FS_SECURITY=y
|
|
|
|
|
# CONFIG_F2FS_CHECK_FS is not set
|
|
|
|
|
CONFIG_NETWORK_FILESYSTEMS=y
|
|
|
|
|
CONFIG_NFS_FS=y
|
|
|
|
|
CONFIG_NFS_V3=y
|
|
|
|
|
CONFIG_NFS_V3_ACL=y
|
|
|
|
|
CONFIG_NFS_V4=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_NFS_V4_1 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_NFS_USE_LEGACY_DNS is not set
|
|
|
|
|
CONFIG_NFS_USE_KERNEL_DNS=y
|
|
|
|
|
# CONFIG_NFS_USE_NEW_IDMAPPER is not set
|
|
|
|
|
# CONFIG_NFSD is not set
|
|
|
|
|
CONFIG_LOCKD=y
|
|
|
|
|
CONFIG_LOCKD_V4=y
|
|
|
|
|
CONFIG_NFS_ACL_SUPPORT=y
|
|
|
|
|
CONFIG_NFS_COMMON=y
|
|
|
|
|
CONFIG_SUNRPC=y
|
|
|
|
|
CONFIG_SUNRPC_GSS=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CEPH_FS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_CIFS is not set
|
|
|
|
|
# CONFIG_NCP_FS is not set
|
|
|
|
|
# CONFIG_CODA_FS is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_AFS_FS is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Partition Types
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_PARTITION_ADVANCED is not set
|
|
|
|
|
CONFIG_MSDOS_PARTITION=y
|
|
|
|
|
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_UTF8 is not set
|
|
|
|
|
CONFIG_DYNAMIC_FSYNC=y
|
|
|
|
|
CONFIG_ASYNC_FSYNC=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel hacking
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PRINTK_TIME=y
|
|
|
|
|
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
|
|
|
|
|
CONFIG_ENABLE_WARN_DEPRECATED=y
|
|
|
|
|
CONFIG_ENABLE_MUST_CHECK=y
|
|
|
|
|
CONFIG_FRAME_WARN=1024
|
|
|
|
|
CONFIG_MAGIC_SYSRQ=y
|
|
|
|
|
# CONFIG_STRIP_ASM_SYMS is not set
|
|
|
|
|
# CONFIG_UNUSED_SYMBOLS is not set
|
|
|
|
|
CONFIG_DEBUG_FS=y
|
|
|
|
|
# CONFIG_HEADERS_CHECK is not set
|
|
|
|
|
# CONFIG_DEBUG_SECTION_MISMATCH is not set
|
|
|
|
|
# CONFIG_DEBUG_KERNEL is not set
|
|
|
|
|
# CONFIG_HARDLOCKUP_DETECTOR is not set
|
|
|
|
|
# CONFIG_SLUB_DEBUG_ON is not set
|
|
|
|
|
# CONFIG_SLUB_STATS is not set
|
|
|
|
|
# CONFIG_SPARSE_RCU_POINTER is not set
|
|
|
|
|
CONFIG_STACKTRACE=y
|
|
|
|
|
CONFIG_DEBUG_BUGVERBOSE=y
|
|
|
|
|
# CONFIG_DEBUG_MEMORY_INIT is not set
|
|
|
|
|
# CONFIG_LKDTM is not set
|
|
|
|
|
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
|
|
|
|
|
CONFIG_HAVE_FUNCTION_TRACER=y
|
|
|
|
|
CONFIG_TRACING_SUPPORT=y
|
|
|
|
|
# CONFIG_FTRACE is not set
|
|
|
|
|
# CONFIG_DYNAMIC_DEBUG is not set
|
|
|
|
|
# CONFIG_ATOMIC64_SELFTEST is not set
|
|
|
|
|
# CONFIG_SAMPLES is not set
|
|
|
|
|
CONFIG_HAVE_ARCH_KGDB=y
|
|
|
|
|
# CONFIG_TEST_KSTRTOX is not set
|
|
|
|
|
# CONFIG_STRICT_DEVMEM is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_ARM_UNWIND=y
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_DEBUG_USER is not set
|
|
|
|
|
# CONFIG_OC_ETM is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Security options
|
|
|
|
|
#
|
|
|
|
|
CONFIG_KEYS=y
|
|
|
|
|
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
|
|
|
|
|
# CONFIG_SECURITY_DMESG_RESTRICT is not set
|
|
|
|
|
CONFIG_SECURITY=y
|
|
|
|
|
# CONFIG_SECURITYFS is not set
|
|
|
|
|
CONFIG_SECURITY_NETWORK=y
|
|
|
|
|
# CONFIG_SECURITY_NETWORK_XFRM is not set
|
|
|
|
|
# CONFIG_SECURITY_PATH is not set
|
|
|
|
|
CONFIG_LSM_MMAP_MIN_ADDR=32768
|
|
|
|
|
CONFIG_SECURITY_SELINUX=y
|
|
|
|
|
# CONFIG_SECURITY_SELINUX_BOOTPARAM is not set
|
|
|
|
|
# CONFIG_SECURITY_SELINUX_DISABLE is not set
|
|
|
|
|
CONFIG_SECURITY_SELINUX_DEVELOP=y
|
|
|
|
|
CONFIG_SECURITY_SELINUX_AVC_STATS=y
|
|
|
|
|
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
|
|
|
|
|
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
|
|
|
|
|
# CONFIG_SECURITY_TOMOYO is not set
|
|
|
|
|
# CONFIG_SECURITY_APPARMOR is not set
|
|
|
|
|
# CONFIG_IMA is not set
|
|
|
|
|
CONFIG_DEFAULT_SECURITY_SELINUX=y
|
|
|
|
|
# CONFIG_DEFAULT_SECURITY_DAC is not set
|
|
|
|
|
CONFIG_DEFAULT_SECURITY="selinux"
|
|
|
|
|
CONFIG_CRYPTO=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Crypto core or helper
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_ALGAPI=y
|
|
|
|
|
CONFIG_CRYPTO_ALGAPI2=y
|
|
|
|
|
CONFIG_CRYPTO_AEAD=y
|
|
|
|
|
CONFIG_CRYPTO_AEAD2=y
|
|
|
|
|
CONFIG_CRYPTO_BLKCIPHER=y
|
|
|
|
|
CONFIG_CRYPTO_BLKCIPHER2=y
|
|
|
|
|
CONFIG_CRYPTO_HASH=y
|
|
|
|
|
CONFIG_CRYPTO_HASH2=y
|
|
|
|
|
CONFIG_CRYPTO_RNG=y
|
|
|
|
|
CONFIG_CRYPTO_RNG2=y
|
|
|
|
|
CONFIG_CRYPTO_PCOMP2=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER2=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_CRYPTO_GF128MUL=y
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_CRYPTO_NULL is not set
|
|
|
|
|
CONFIG_CRYPTO_WORKQUEUE=y
|
|
|
|
|
# CONFIG_CRYPTO_CRYPTD is not set
|
|
|
|
|
CONFIG_CRYPTO_AUTHENC=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Authenticated Encryption with Associated Data
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_CRYPTO_CCM is not set
|
|
|
|
|
# CONFIG_CRYPTO_GCM is not set
|
|
|
|
|
# CONFIG_CRYPTO_SEQIV is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Block modes
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_CBC=y
|
|
|
|
|
# CONFIG_CRYPTO_CTR is not set
|
|
|
|
|
# CONFIG_CRYPTO_CTS is not set
|
|
|
|
|
CONFIG_CRYPTO_ECB=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CRYPTO_LRW is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_CRYPTO_PCBC is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
CONFIG_CRYPTO_XTS=y
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Hash modes
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_HMAC=y
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CRYPTO_XCBC is not set
|
|
|
|
|
# CONFIG_CRYPTO_VMAC is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Digest
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_CRC32C=y
|
|
|
|
|
# CONFIG_CRYPTO_GHASH is not set
|
|
|
|
|
# CONFIG_CRYPTO_MD4 is not set
|
|
|
|
|
CONFIG_CRYPTO_MD5=y
|
|
|
|
|
# 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_SHA1_ARM=y
|
|
|
|
|
CONFIG_CRYPTO_SHA1_ARM_NEON=y
|
|
|
|
|
CONFIG_CRYPTO_SHA256=y
|
|
|
|
|
CONFIG_CRYPTO_SHA512=y
|
|
|
|
|
CONFIG_CRYPTO_SHA512_ARM_NEON=y
|
|
|
|
|
# CONFIG_CRYPTO_TGR192 is not set
|
|
|
|
|
# CONFIG_CRYPTO_WP512 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Ciphers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_AES=y
|
|
|
|
|
CONFIG_CRYPTO_AES_ARM=y
|
|
|
|
|
# CONFIG_CRYPTO_AES_ARM_BS is not set
|
|
|
|
|
# CONFIG_CRYPTO_ANUBIS is not set
|
|
|
|
|
CONFIG_CRYPTO_ARC4=y
|
|
|
|
|
# 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=y
|
|
|
|
|
# CONFIG_CRYPTO_FCRYPT is not set
|
|
|
|
|
# CONFIG_CRYPTO_KHAZAD is not set
|
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).
I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.
It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.
[skip ci]: I have verified, that every single one of these kernels builds.
CI will likely run out of time while downloading source tarballs.
2020-07-11 13:24:19 +00:00
|
|
|
# CONFIG_CRYPTO_SALSA20 is not set
|
2019-12-09 16:37:22 +00:00
|
|
|
# CONFIG_CRYPTO_SEED is not set
|
|
|
|
|
# CONFIG_CRYPTO_SERPENT is not set
|
|
|
|
|
# CONFIG_CRYPTO_TEA is not set
|
|
|
|
|
CONFIG_CRYPTO_TWOFISH=y
|
|
|
|
|
CONFIG_CRYPTO_TWOFISH_COMMON=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Compression
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_DEFLATE=y
|
|
|
|
|
# CONFIG_CRYPTO_ZLIB is not set
|
|
|
|
|
CONFIG_CRYPTO_LZO=y
|
|
|
|
|
CONFIG_CRYPTO_LZ4=y
|
|
|
|
|
CONFIG_CRYPTO_LZ4HC=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Random Number Generation
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_ANSI_CPRNG=y
|
|
|
|
|
# CONFIG_CRYPTO_USER_API_HASH is not set
|
|
|
|
|
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
|
|
|
|
|
CONFIG_CRYPTO_HW=y
|
|
|
|
|
CONFIG_CRYPTO_DEV_QCRYPTO=y
|
|
|
|
|
CONFIG_CRYPTO_DEV_QCE=y
|
|
|
|
|
CONFIG_CRYPTO_DEV_QCEDEV=y
|
|
|
|
|
# CONFIG_CRYPTO_DEV_OTA_CRYPTO is not set
|
|
|
|
|
# CONFIG_BINARY_PRINTF is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Library routines
|
|
|
|
|
#
|
|
|
|
|
CONFIG_BITREVERSE=y
|
|
|
|
|
CONFIG_GENERIC_STRNCPY_FROM_USER=y
|
|
|
|
|
CONFIG_GENERIC_STRNLEN_USER=y
|
|
|
|
|
CONFIG_CRC_CCITT=y
|
|
|
|
|
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_CRC7 is not set
|
|
|
|
|
CONFIG_LIBCRC32C=y
|
|
|
|
|
CONFIG_AUDIT_GENERIC=y
|
|
|
|
|
CONFIG_ZLIB_INFLATE=y
|
|
|
|
|
CONFIG_ZLIB_DEFLATE=y
|
|
|
|
|
CONFIG_LZO_COMPRESS=y
|
|
|
|
|
CONFIG_LZO_DECOMPRESS=y
|
|
|
|
|
CONFIG_LZ4_COMPRESS=y
|
|
|
|
|
CONFIG_LZ4HC_COMPRESS=y
|
|
|
|
|
CONFIG_LZ4_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_GENERIC_ALLOCATOR=y
|
|
|
|
|
CONFIG_TEXTSEARCH=y
|
|
|
|
|
CONFIG_TEXTSEARCH_KMP=y
|
|
|
|
|
CONFIG_TEXTSEARCH_BM=y
|
|
|
|
|
CONFIG_TEXTSEARCH_FSM=y
|
|
|
|
|
CONFIG_HAS_IOMEM=y
|
|
|
|
|
CONFIG_HAS_IOPORT=y
|
|
|
|
|
CONFIG_HAS_DMA=y
|
|
|
|
|
CONFIG_NLATTR=y
|
|
|
|
|
# CONFIG_AVERAGE is not set
|