*/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
|
|
|
#
|
|
|
|
|
# Automatically generated make config: don't edit
|
|
|
|
|
# Linux/arm 3.0.101 Kernel Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARM=y
|
|
|
|
|
CONFIG_HAVE_PWM=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_GENERIC_CLOCKEVENTS_BROADCAST=y
|
|
|
|
|
CONFIG_KTIME_SCALAR=y
|
|
|
|
|
CONFIG_HAVE_PROC_CPU=y
|
|
|
|
|
CONFIG_STACKTRACE_SUPPORT=y
|
|
|
|
|
CONFIG_LOCKDEP_SUPPORT=y
|
|
|
|
|
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
|
|
|
|
|
CONFIG_HARDIRQS_SW_RESEND=y
|
|
|
|
|
CONFIG_GENERIC_IRQ_PROBE=y
|
|
|
|
|
CONFIG_GENERIC_LOCKBREAK=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
|
|
|
|
|
# CONFIG_ARM_PATCH_PHYS_VIRT is not set
|
|
|
|
|
CONFIG_GENERIC_BUG=y
|
|
|
|
|
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
|
|
|
|
|
CONFIG_HAVE_IRQ_WORK=y
|
|
|
|
|
CONFIG_IRQ_WORK=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# General setup
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXPERIMENTAL=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_INIT_ENV_ARG_LIMIT=32
|
|
|
|
|
CONFIG_CROSS_COMPILE=""
|
|
|
|
|
CONFIG_LOCALVERSION=""
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_LOCALVERSION_AUTO 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_HAVE_KERNEL_GZIP=y
|
|
|
|
|
CONFIG_HAVE_KERNEL_LZMA=y
|
|
|
|
|
CONFIG_HAVE_KERNEL_LZO=y
|
|
|
|
|
CONFIG_HAVE_KERNEL_LZ4=y
|
|
|
|
|
CONFIG_KERNEL_GZIP=y
|
|
|
|
|
# CONFIG_KERNEL_LZMA is not set
|
|
|
|
|
# CONFIG_KERNEL_LZO is not set
|
|
|
|
|
# CONFIG_KERNEL_LZ4 is not set
|
|
|
|
|
CONFIG_DEFAULT_HOSTNAME="(none)"
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_SWAP is not set
|
|
|
|
|
CONFIG_SYSVIPC=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_SYSVIPC_SYSCTL=y
|
|
|
|
|
# CONFIG_POSIX_MQUEUE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BSD_PROCESS_ACCT=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_BSD_PROCESS_ACCT_V3 is not set
|
|
|
|
|
# CONFIG_FHANDLE is not set
|
|
|
|
|
# CONFIG_TASKSTATS is not set
|
|
|
|
|
# CONFIG_AUDIT is not set
|
|
|
|
|
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_TREE_PREEMPT_RCU=y
|
|
|
|
|
CONFIG_PREEMPT_RCU=y
|
|
|
|
|
# CONFIG_RCU_TRACE is not set
|
|
|
|
|
CONFIG_RCU_FANOUT=32
|
|
|
|
|
# CONFIG_RCU_FANOUT_EXACT is not set
|
|
|
|
|
# CONFIG_TREE_RCU_TRACE is not set
|
|
|
|
|
# CONFIG_RCU_BOOST is not set
|
|
|
|
|
# CONFIG_IKCONFIG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_LOG_BUF_SHIFT=18
|
|
|
|
|
CONFIG_CGROUPS=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_CGROUP_DEBUG is not set
|
|
|
|
|
# CONFIG_CGROUP_FREEZER is not set
|
|
|
|
|
# CONFIG_CGROUP_DEVICE is not set
|
|
|
|
|
# CONFIG_CPUSETS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CGROUP_CPUACCT=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_RESOURCE_COUNTERS is not set
|
|
|
|
|
# CONFIG_CGROUP_PERF is not set
|
|
|
|
|
# CONFIG_CGROUP_SCHED is not set
|
|
|
|
|
# CONFIG_BLK_CGROUP is not set
|
|
|
|
|
# CONFIG_NAMESPACES is not set
|
|
|
|
|
# CONFIG_SCHED_AUTOGROUP is not set
|
|
|
|
|
# CONFIG_SYSFS_DEPRECATED is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RELAY=y
|
|
|
|
|
CONFIG_BLK_DEV_INITRD=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_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 is not set
|
|
|
|
|
CONFIG_SYSCTL=y
|
|
|
|
|
CONFIG_ANON_INODES=y
|
|
|
|
|
CONFIG_PANIC_TIMEOUT=0
|
|
|
|
|
CONFIG_EXPERT=y
|
|
|
|
|
CONFIG_UID16=y
|
|
|
|
|
CONFIG_SYSCTL_SYSCALL=y
|
|
|
|
|
CONFIG_KALLSYMS=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KALLSYMS_ALL=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_HOTPLUG=y
|
|
|
|
|
CONFIG_PRINTK=y
|
|
|
|
|
CONFIG_BUG=y
|
|
|
|
|
CONFIG_ELF_CORE=y
|
|
|
|
|
CONFIG_BASE_FULL=y
|
|
|
|
|
CONFIG_FUTEX=y
|
|
|
|
|
CONFIG_EPOLL=y
|
|
|
|
|
CONFIG_SIGNALFD=y
|
|
|
|
|
CONFIG_TIMERFD=y
|
|
|
|
|
CONFIG_EVENTFD=y
|
|
|
|
|
CONFIG_SHMEM=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ASHMEM=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_AIO=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EMBEDDED=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_HAVE_PERF_EVENTS=y
|
|
|
|
|
CONFIG_PERF_USE_VMALLOC=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel Performance Events And Counters
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PERF_EVENTS=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_PERF_COUNTERS is not set
|
|
|
|
|
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
|
|
|
|
|
CONFIG_VM_EVENT_COUNTERS=y
|
|
|
|
|
CONFIG_COMPAT_BRK=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SLAB=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_SLUB is not set
|
|
|
|
|
# CONFIG_SLOB is not set
|
|
|
|
|
# CONFIG_PROFILING is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BOOTTIME=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_TRACEPOINTS=y
|
|
|
|
|
CONFIG_HAVE_OPROFILE=y
|
|
|
|
|
# CONFIG_KPROBES is not set
|
|
|
|
|
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
|
|
|
|
|
CONFIG_HAVE_KPROBES=y
|
|
|
|
|
CONFIG_HAVE_KRETPROBES=y
|
|
|
|
|
CONFIG_USE_GENERIC_SMP_HELPERS=y
|
|
|
|
|
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
|
|
|
|
|
CONFIG_HAVE_CLK=y
|
|
|
|
|
CONFIG_HAVE_DMA_API_DEBUG=y
|
|
|
|
|
CONFIG_HAVE_HW_BREAKPOINT=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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MODULES=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_MODULE_FORCE_LOAD is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MODULE_UNLOAD=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_MODULE_FORCE_UNLOAD is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MODVERSIONS=y
|
|
|
|
|
CONFIG_MODULE_SRCVERSION_ALL=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_STOP_MACHINE=y
|
|
|
|
|
CONFIG_BLOCK=y
|
|
|
|
|
CONFIG_LBDAF=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_BLK_DEV_BSG 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_INTEGRITY is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IO Schedulers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_IOSCHED_NOOP=y
|
|
|
|
|
CONFIG_IOSCHED_DEADLINE=y
|
|
|
|
|
CONFIG_IOSCHED_CFQ=y
|
|
|
|
|
CONFIG_IOSCHED_SIOPLUS=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DEFAULT_DEADLINE=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_DEFAULT_CFQ is not set
|
|
|
|
|
# CONFIG_DEFAULT_NOOP is not set
|
|
|
|
|
# CONFIG_DEFAULT_SIOPLUS is not set
|
|
|
|
|
CONFIG_DEFAULT_IOSCHED="deadline"
|
|
|
|
|
# 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=y
|
|
|
|
|
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 is not set
|
|
|
|
|
# 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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ARCH_U8500=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_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
|
|
|
|
|
# CONFIG_GPIO_PCA953X is not set
|
|
|
|
|
# CONFIG_KEYBOARD_GPIO_POLLED is not set
|
|
|
|
|
CONFIG_PLAT_NOMADIK=y
|
|
|
|
|
CONFIG_HAS_MTU=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# System MMU
|
|
|
|
|
#
|
|
|
|
|
CONFIG_UX500_SOC_COMMON=y
|
|
|
|
|
CONFIG_UX500_SOC_DBX500=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Ux500 SoC
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_UX500_SOC_DB5500 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UX500_SOC_DB8500=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Ux500 target platform (boards)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MACH_U8500 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MACH_SAMSUNG_U8500=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_MACH_HREFV60 is not set
|
|
|
|
|
# CONFIG_MACH_U8520 is not set
|
|
|
|
|
# CONFIG_MACH_SNOWBALL is not set
|
|
|
|
|
# CONFIG_MACH_CCU9540 is not set
|
|
|
|
|
# CONFIG_MACH_U9540 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Samsung Ux500 Options
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_CONNECTOR_SAMSUNG_3PI is not set
|
|
|
|
|
CONFIG_MACH_SAMSUNG_UX500=y
|
|
|
|
|
CONFIG_KEYLAYOUT_LAYOUT1=y
|
|
|
|
|
# CONFIG_KEYLAYOUT_LAYOUT2 is not set
|
|
|
|
|
# CONFIG_MACH_GAVINI is not set
|
|
|
|
|
# CONFIG_MACH_JANICE is not set
|
|
|
|
|
# CONFIG_MACH_JANICE_KOR is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MACH_CODINA=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_MACH_SEC_KYLE is not set
|
|
|
|
|
# CONFIG_MACH_SEC_GOLDEN is not set
|
|
|
|
|
# CONFIG_MACH_SEC_SKOMER is not set
|
|
|
|
|
# CONFIG_MACH_SEC_HENDRIX is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Samsung Product Features
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SAMSUNG_PRODUCT_SHIP is not set
|
|
|
|
|
CONFIG_DBX500_SCHED_CLOCK_PRCMU=y
|
|
|
|
|
# CONFIG_DBX500_MTU_SCHED_CLOCK is not set
|
|
|
|
|
CONFIG_UX500_DEBUG_UART=2
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UX500_GPIO_KEYS=y
|
|
|
|
|
CONFIG_DBX500_PRCMU_DEBUG=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_TEE_UX500=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DB8500_MLOADER=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_UX500_DEBUG_HWREG is not set
|
|
|
|
|
# CONFIG_UX500_DEBUG_NO_LAUTERBACH is not set
|
|
|
|
|
CONFIG_UX500_L2X0_PREFETCH_CTRL=y
|
|
|
|
|
CONFIG_UX500_DB_DUMP=y
|
|
|
|
|
# CONFIG_UX500_DEBUG_LAST_IO is not set
|
|
|
|
|
CONFIG_RTC_HCTOHC=y
|
|
|
|
|
CONFIG_UX500_HW_OBSERVER=y
|
|
|
|
|
# CONFIG_U8500_CUSTOM_RF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_BCM4330=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_BT_BCM4334 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_MGMT=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_ANDROID_WIP is not set
|
|
|
|
|
# CONFIG_AB8505_SMPL is not set
|
|
|
|
|
# CONFIG_TARGET_LOCALE_CHN is not set
|
|
|
|
|
CONFIG_MACH_CODINA_EURO=y
|
|
|
|
|
# CONFIG_U8500_HOTPLUG is not set
|
|
|
|
|
# CONFIG_U8500_SECURE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Display setup
|
|
|
|
|
#
|
|
|
|
|
CONFIG_DBX500_PRCMU_QOS_POWER=y
|
|
|
|
|
CONFIG_DBX500_CONTEXT=y
|
|
|
|
|
CONFIG_UX500_PM_PERFORMANCE=y
|
|
|
|
|
CONFIG_UX500_CONSOLE_UART_GPIO_PIN=29
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UX500_SUSPEND=y
|
|
|
|
|
CONFIG_UX500_SUSPEND_STANDBY=y
|
|
|
|
|
CONFIG_UX500_SUSPEND_MEM=y
|
|
|
|
|
CONFIG_UX500_SUSPEND_DBG=y
|
|
|
|
|
CONFIG_UX500_SUSPEND_DBG_WAKE_ON_UART=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_UX500_USECASE_GOVERNOR=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DB8500_PWR_TEST=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 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 is not set
|
|
|
|
|
CONFIG_SWP_EMULATE=y
|
|
|
|
|
# CONFIG_CPU_ICACHE_DISABLE is not set
|
|
|
|
|
# CONFIG_CPU_DCACHE_DISABLE is not set
|
|
|
|
|
# CONFIG_CPU_BPREDICT_DISABLE is not set
|
|
|
|
|
CONFIG_OUTER_CACHE=y
|
|
|
|
|
CONFIG_OUTER_CACHE_SYNC=y
|
|
|
|
|
CONFIG_CACHE_L2X0=y
|
|
|
|
|
CONFIG_CACHE_PL310=y
|
|
|
|
|
CONFIG_ARM_L1_CACHE_SHIFT=5
|
|
|
|
|
CONFIG_ARM_DMA_MEM_BUFFERABLE=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_742230 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_742231 is not set
|
|
|
|
|
# CONFIG_PL310_ERRATA_588369 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_720789 is not set
|
|
|
|
|
# CONFIG_PL310_ERRATA_727915 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_743622 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_751472 is not set
|
|
|
|
|
CONFIG_ARM_ERRATA_753970=y
|
|
|
|
|
CONFIG_ARM_ERRATA_754322=y
|
|
|
|
|
# CONFIG_ARM_ERRATA_754327 is not set
|
|
|
|
|
CONFIG_ARM_ERRATA_764369=y
|
|
|
|
|
# CONFIG_PL310_ERRATA_769419 is not set
|
|
|
|
|
# CONFIG_ARM_ERRATA_775420 is not set
|
|
|
|
|
CONFIG_ARM_GIC=y
|
|
|
|
|
# CONFIG_FIQ_DEBUGGER is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bus support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARM_AMBA=y
|
|
|
|
|
# CONFIG_PCI_SYSCALL is not set
|
|
|
|
|
# CONFIG_ARCH_SUPPORTS_MSI is not set
|
|
|
|
|
# CONFIG_PCCARD is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel Features
|
|
|
|
|
#
|
|
|
|
|
CONFIG_TICK_ONESHOT=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NO_HZ=y
|
|
|
|
|
CONFIG_HIGH_RES_TIMERS=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_GENERIC_CLOCKEVENTS_BUILD=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SMP=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_SMP_ON_UP=y
|
|
|
|
|
CONFIG_ARM_CPU_TOPOLOGY=y
|
|
|
|
|
# CONFIG_SCHED_MC is not set
|
|
|
|
|
# CONFIG_SCHED_SMT is not set
|
|
|
|
|
CONFIG_HAVE_ARM_SCU=y
|
|
|
|
|
CONFIG_HAVE_ARM_TWD=y
|
|
|
|
|
CONFIG_VMSPLIT_3G=y
|
|
|
|
|
# CONFIG_VMSPLIT_2G is not set
|
|
|
|
|
# CONFIG_VMSPLIT_1G is not set
|
|
|
|
|
CONFIG_PAGE_OFFSET=0xC0000000
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NR_CPUS=2
|
*/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_HOTPLUG_CPU=y
|
|
|
|
|
CONFIG_LOCAL_TIMERS=y
|
|
|
|
|
# CONFIG_PREEMPT_NONE is not set
|
|
|
|
|
# CONFIG_PREEMPT_VOLUNTARY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PREEMPT=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_HZ=100
|
|
|
|
|
# CONFIG_THUMB2_KERNEL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_AEABI=y
|
|
|
|
|
# CONFIG_OABI_COMPAT 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_ARCH_SPARSEMEM_DEFAULT is not set
|
|
|
|
|
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
|
|
|
|
|
CONFIG_HAVE_ARCH_PFN_VALID=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HIGHMEM=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_HIGHPTE is not set
|
|
|
|
|
CONFIG_HW_PERF_EVENTS=y
|
|
|
|
|
CONFIG_SELECT_MEMORY_MODEL=y
|
|
|
|
|
CONFIG_FLATMEM_MANUAL=y
|
|
|
|
|
CONFIG_FLATMEM=y
|
|
|
|
|
CONFIG_FLAT_NODE_MEM_MAP=y
|
|
|
|
|
CONFIG_HAVE_MEMBLOCK=y
|
|
|
|
|
CONFIG_PAGEFLAGS_EXTENDED=y
|
|
|
|
|
CONFIG_SPLIT_PTLOCK_CPUS=4
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_COMPACTION=y
|
|
|
|
|
CONFIG_COMPACTION_RETRY=y
|
|
|
|
|
CONFIG_COMPACTION_RETRY_DEBUG=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_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 is not set
|
|
|
|
|
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
|
|
|
|
|
# CONFIG_CLEANCACHE is not set
|
|
|
|
|
CONFIG_FORCE_MAX_ZONEORDER=12
|
|
|
|
|
CONFIG_ALIGNMENT_TRAP=y
|
|
|
|
|
# CONFIG_UACCESS_WITH_MEMCPY is not set
|
|
|
|
|
# CONFIG_SECCOMP is not set
|
|
|
|
|
# CONFIG_CC_STACKPROTECTOR is not set
|
|
|
|
|
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
|
|
|
|
|
# CONFIG_ARM_FLUSH_CONSOLE_ON_RESTART is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
|
*/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
|
|
|
#
|
|
|
|
|
# Boot options
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USE_OF is not set
|
|
|
|
|
CONFIG_ZBOOT_ROM_TEXT=0x0
|
|
|
|
|
CONFIG_ZBOOT_ROM_BSS=0x0
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CMDLINE="root=/dev/ram0 init=init rw console=ttyAMA2,115200n8 mem=256M initrd=0x800000,72M"
|
*/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_CMDLINE_FROM_BOOTLOADER=y
|
|
|
|
|
# CONFIG_CMDLINE_EXTEND is not set
|
|
|
|
|
# CONFIG_CMDLINE_FORCE is not set
|
|
|
|
|
# CONFIG_XIP_KERNEL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KEXEC=y
|
|
|
|
|
CONFIG_CRASH_SWRESET=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_ATAGS_PROC=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRASH_DUMP=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_AUTO_ZRELADDR is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CPU Power Management
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CPU Frequency scaling
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_FREQ=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_CPU_FREQ_TABLE=y
|
|
|
|
|
CONFIG_CPU_FREQ_STAT=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_FREQ_STAT_DETAILS=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_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=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_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
|
|
|
|
|
# CONFIG_CPU_FREQ_DEFAULT_GOV_ABYSSPLUG is not set
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
|
|
|
|
|
CONFIG_CPU_FREQ_GOV_USERSPACE=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_CPU_FREQ_GOV_ONDEMAND=y
|
|
|
|
|
# CONFIG_CPU_FREQ_GOV_INTERACTIVE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=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_CPU_FREQ_GOV_ABYSSPLUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CPU_IDLE=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_CPU_IDLE_GOV_LADDER=y
|
|
|
|
|
CONFIG_CPU_IDLE_GOV_MENU=y
|
|
|
|
|
CONFIG_DBX500_CPUIDLE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DBX500_CPUIDLE_DEEPEST_STATE=3
|
*/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_DBX500_CPUIDLE_APDEEPIDLE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DBX500_CPUIDLE_DEBUG=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Floating point emulation
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# At least one emulation must be selected
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_VFP=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_VFPv3=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NEON=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Userspace binary formats
|
|
|
|
|
#
|
|
|
|
|
CONFIG_BINFMT_ELF=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS 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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_WAKELOCK=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_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_SLEEP_SMP=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PM_RUNTIME=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_PM=y
|
|
|
|
|
# CONFIG_PM_DEBUG is not set
|
|
|
|
|
# CONFIG_APM_EMULATION is not set
|
|
|
|
|
CONFIG_PM_RUNTIME_CLK=y
|
|
|
|
|
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
|
|
|
|
|
# CONFIG_SUSPEND_TIME is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DVFS_LIMIT=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_ARCH_SUSPEND_POSSIBLE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Networking options
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PACKET=y
|
|
|
|
|
CONFIG_UNIX=y
|
|
|
|
|
CONFIG_XFRM=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_USER is not set
|
|
|
|
|
# CONFIG_XFRM_SUB_POLICY is not set
|
|
|
|
|
# CONFIG_XFRM_MIGRATE is not set
|
|
|
|
|
# CONFIG_XFRM_STATISTICS is not set
|
2020-06-12 17:59:18 +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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INET=y
|
|
|
|
|
CONFIG_IP_MULTICAST=y
|
|
|
|
|
CONFIG_IP_ADVANCED_ROUTER=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_FIB_TRIE_STATS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IP_MULTIPLE_TABLES=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_ROUTE_MULTIPATH is not set
|
|
|
|
|
# CONFIG_IP_ROUTE_VERBOSE is not set
|
|
|
|
|
# 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_ARPD is not set
|
|
|
|
|
# CONFIG_SYN_COOKIES is not set
|
|
|
|
|
# CONFIG_INET_AH is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INET_ESP=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_INET_IPCOMP is not set
|
|
|
|
|
# CONFIG_INET_XFRM_TUNNEL is not set
|
|
|
|
|
CONFIG_INET_TUNNEL=y
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
*/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_CONG_ADVANCED is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
2020-06-12 17:59:18 +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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IPV6_OPTIMISTIC_DAD=y
|
|
|
|
|
CONFIG_INET6_AH=y
|
|
|
|
|
CONFIG_INET6_ESP=y
|
|
|
|
|
CONFIG_INET6_IPCOMP=y
|
|
|
|
|
CONFIG_IPV6_MIP6=y
|
|
|
|
|
CONFIG_INET6_XFRM_TUNNEL=y
|
|
|
|
|
CONFIG_INET6_TUNNEL=y
|
|
|
|
|
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
|
|
|
|
|
CONFIG_INET6_XFRM_MODE_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_INET6_XFRM_MODE_BEET=y
|
|
|
|
|
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
|
2020-06-12 17:59:18 +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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IPV6_NDISC_NODETYPE=y
|
|
|
|
|
CONFIG_IPV6_TUNNEL=y
|
|
|
|
|
CONFIG_IPV6_MULTIPLE_TABLES=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_SUBTREES is not set
|
|
|
|
|
# CONFIG_IPV6_MROUTE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_ANDROID_PARANOID_NETWORK is not set
|
|
|
|
|
CONFIG_NET_ACTIVITY_STATS=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_SECMARK is not set
|
|
|
|
|
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER=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_DEBUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_ADVANCED=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Core Netfilter Configuration
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_NETLINK=y
|
|
|
|
|
CONFIG_NETFILTER_NETLINK_QUEUE=y
|
|
|
|
|
CONFIG_NETFILTER_NETLINK_LOG=y
|
|
|
|
|
CONFIG_NF_CONNTRACK=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_MARK=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_EVENTS=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_TIMESTAMP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NF_CT_PROTO_DCCP=y
|
|
|
|
|
CONFIG_NF_CT_PROTO_GRE=y
|
|
|
|
|
CONFIG_NF_CT_PROTO_SCTP=y
|
|
|
|
|
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
|
*/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_SNMP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NF_CONNTRACK_PPTP=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_SANE=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_SIP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NF_CONNTRACK_TFTP=y
|
|
|
|
|
CONFIG_NF_CT_NETLINK=y
|
|
|
|
|
CONFIG_NETFILTER_TPROXY=y
|
|
|
|
|
CONFIG_NETFILTER_XTABLES=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables combined modules
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_MARK=y
|
|
|
|
|
CONFIG_NETFILTER_XT_CONNMARK=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables targets
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_CONNMARK=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_CT is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_HL is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_LED is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_TARGET_MARK=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=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_NOTRACK is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_TARGET_TPROXY=y
|
|
|
|
|
CONFIG_NETFILTER_XT_TARGET_TRACE=y
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Xtables matches
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
*/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_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 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
*/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_MULTIPORT is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_MATCH_POLICY=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QTAGUID=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QUOTA2=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_QUOTA2_LOG=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_MATCH_RATEEST is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
|
|
|
|
|
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_MATCH_SOCKET=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_STATE=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_STRING=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_MATCH_TCPMSS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETFILTER_XT_MATCH_TIME=y
|
|
|
|
|
CONFIG_NETFILTER_XT_MATCH_U32=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_SET is not set
|
|
|
|
|
# CONFIG_IP_VS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IP: Netfilter Configuration
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NF_DEFRAG_IPV4=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_IPV4=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_PROC_COMPAT=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_QUEUE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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=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_ULOG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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_DCCP=y
|
|
|
|
|
CONFIG_NF_NAT_PROTO_GRE=y
|
|
|
|
|
CONFIG_NF_NAT_PROTO_UDPLITE=y
|
|
|
|
|
CONFIG_NF_NAT_PROTO_SCTP=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
|
*/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_NAT_SIP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
|
|
|
|
# CONFIG_IP_NF_TARGET_ECN is not set
|
|
|
|
|
# CONFIG_IP_NF_TARGET_TTL is not set
|
|
|
|
|
CONFIG_IP_NF_RAW=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IP_NF_ARPTABLES=y
|
|
|
|
|
CONFIG_IP_NF_ARPFILTER=y
|
|
|
|
|
CONFIG_IP_NF_ARP_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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# IPv6: Netfilter Configuration
|
|
|
|
|
#
|
|
|
|
|
CONFIG_NF_DEFRAG_IPV6=y
|
|
|
|
|
CONFIG_NF_CONNTRACK_IPV6=y
|
|
|
|
|
# CONFIG_IP6_NF_QUEUE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IP6_NF_IPTABLES=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_IP6_NF_MATCH_AH is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_EUI64 is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_FRAG is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_OPTS is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_HL is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_IPV6HEADER is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_MH is not set
|
|
|
|
|
# CONFIG_IP6_NF_MATCH_RT is not set
|
|
|
|
|
# CONFIG_IP6_NF_TARGET_HL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IP6_NF_TARGET_LOG=y
|
|
|
|
|
CONFIG_IP6_NF_FILTER=y
|
|
|
|
|
CONFIG_IP6_NF_TARGET_REJECT=y
|
|
|
|
|
CONFIG_IP6_NF_TARGET_REJECT_SKERR=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_IP6_NF_MANGLE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_IP6_NF_RAW=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_DCCP is not set
|
|
|
|
|
# CONFIG_IP_SCTP is not set
|
|
|
|
|
# CONFIG_RDS is not set
|
|
|
|
|
# CONFIG_TIPC is not set
|
|
|
|
|
# CONFIG_ATM is not set
|
|
|
|
|
# CONFIG_L2TP is not set
|
|
|
|
|
# CONFIG_BRIDGE is not set
|
|
|
|
|
# CONFIG_NET_DSA is not set
|
|
|
|
|
# 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
|
|
|
|
|
# CONFIG_X25 is not set
|
|
|
|
|
# CONFIG_LAPB is not set
|
|
|
|
|
# CONFIG_ECONET is not set
|
|
|
|
|
# CONFIG_WAN_ROUTER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PHONET=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_IEEE802154 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Queueing/Scheduling
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NET_SCH_CBQ is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_SCH_HTB=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_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 is not set
|
|
|
|
|
# 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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_SCH_INGRESS=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Classification
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_CLS=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_CLS_BASIC is not set
|
|
|
|
|
# CONFIG_NET_CLS_TCINDEX is not set
|
|
|
|
|
# CONFIG_NET_CLS_ROUTE4 is not set
|
|
|
|
|
# CONFIG_NET_CLS_FW is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_CLS_U32=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_EMATCH=y
|
|
|
|
|
CONFIG_NET_EMATCH_STACK=32
|
*/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_EMATCH_CMP is not set
|
|
|
|
|
# CONFIG_NET_EMATCH_NBYTE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_EMATCH_U32=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_EMATCH_META is not set
|
|
|
|
|
# CONFIG_NET_EMATCH_TEXT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_CLS_ACT=y
|
|
|
|
|
CONFIG_NET_ACT_POLICE=y
|
|
|
|
|
CONFIG_NET_ACT_GACT=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_GACT_PROB is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_ACT_MIRRED=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_SCH_FIFO=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_DCB is not set
|
|
|
|
|
# CONFIG_DNS_RESOLVER is not set
|
|
|
|
|
# CONFIG_BATMAN_ADV is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RPS=y
|
|
|
|
|
CONFIG_RFS_ACCEL=y
|
|
|
|
|
CONFIG_XPS=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Network testing
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NET_PKTGEN is not set
|
|
|
|
|
# CONFIG_NET_DROP_MONITOR is not set
|
|
|
|
|
# CONFIG_HAMRADIO is not set
|
|
|
|
|
# CONFIG_CAN is not set
|
|
|
|
|
# CONFIG_IRDA is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT=y
|
|
|
|
|
CONFIG_BT_L2CAP=y
|
|
|
|
|
CONFIG_BT_SCO=y
|
|
|
|
|
CONFIG_BT_RFCOMM=y
|
|
|
|
|
CONFIG_BT_RFCOMM_TTY=y
|
|
|
|
|
CONFIG_BT_BNEP=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_BT_BNEP_MC_FILTER is not set
|
|
|
|
|
# CONFIG_BT_BNEP_PROTO_FILTER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_HIDP=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bluetooth device drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_BT_HCISMD is not set
|
|
|
|
|
# CONFIG_BT_HCIBTUSB is not set
|
|
|
|
|
# CONFIG_BT_HCIBTSDIO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_HCIUART=y
|
|
|
|
|
CONFIG_BT_HCIUART_H4=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_BT_HCIUART_BCSP is not set
|
|
|
|
|
# CONFIG_BT_HCIUART_ATH3K is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_HCIUART_LL=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_BT_HCIUART_IBS is not set
|
|
|
|
|
# CONFIG_BT_HCIBCM203X is not set
|
|
|
|
|
# CONFIG_BT_HCIBPA10X is not set
|
|
|
|
|
# CONFIG_BT_HCIBFUSB is not set
|
|
|
|
|
# CONFIG_BT_HCIVHCI is not set
|
|
|
|
|
# CONFIG_BT_MRVL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BT_HID=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
|
|
|
|
|
CONFIG_FIB_RULES=y
|
|
|
|
|
CONFIG_WIRELESS=y
|
|
|
|
|
# CONFIG_COMPAT_WIRELESS is not set
|
|
|
|
|
CONFIG_WEXT_CORE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CFG80211=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_CFG80211_WEXT=y
|
|
|
|
|
# CONFIG_MAC80211 is not set
|
|
|
|
|
# CONFIG_NL80211_TESTMODE is not set
|
|
|
|
|
CONFIG_CFG80211_DEFAULT_PS=y
|
|
|
|
|
# CONFIG_CFG80211_REG_DEBUG is not set
|
|
|
|
|
CONFIG_WEXT_PROC=y
|
|
|
|
|
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
|
|
|
|
|
# CONFIG_CFG80211_DEBUGFS is not set
|
|
|
|
|
# CONFIG_CFG80211_INTERNAL_REGDB is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_WIRELESS_EXT_SYSFS 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_LIB80211 is not set
|
|
|
|
|
# CONFIG_CFG80211_ALLOW_RECONNECT is not set
|
|
|
|
|
CONFIG_CFG80211_REG_NOT_UPDATED=y
|
|
|
|
|
# CONFIG_WIMAX is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RFKILL=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_RFKILL_PM=y
|
|
|
|
|
CONFIG_RFKILL_LEDS=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RFKILL_INPUT=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_RFKILL_REGULATOR is not set
|
|
|
|
|
# CONFIG_RFKILL_GPIO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_9P=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_9P_DEBUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CAIF=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_CAIF_DEBUG is not set
|
|
|
|
|
CONFIG_CAIF_NETDEV=y
|
|
|
|
|
# CONFIG_CEPH_LIB is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Device Drivers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Generic Driver Options
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
|
*/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_DEVTMPFS=y
|
|
|
|
|
# CONFIG_DEVTMPFS_MOUNT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_STANDALONE 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_PREVENT_FIRMWARE_BUILD=y
|
|
|
|
|
CONFIG_FW_LOADER=y
|
|
|
|
|
CONFIG_FIRMWARE_IN_KERNEL=y
|
|
|
|
|
CONFIG_EXTRA_FIRMWARE=""
|
|
|
|
|
# CONFIG_DEBUG_DRIVER is not set
|
|
|
|
|
# CONFIG_DEBUG_DEVRES is not set
|
|
|
|
|
# CONFIG_SYS_HYPERVISOR is not set
|
|
|
|
|
CONFIG_SYS_SOC=y
|
|
|
|
|
# CONFIG_BATTERY_SAMSUNG is not set
|
|
|
|
|
# CONFIG_CHARGER_MAX8903 is not set
|
|
|
|
|
# CONFIG_CONNECTOR is not set
|
|
|
|
|
# CONFIG_MTD is not set
|
|
|
|
|
# CONFIG_PARPORT is not set
|
|
|
|
|
CONFIG_BLK_DEV=y
|
|
|
|
|
# CONFIG_BLK_DEV_COW_COMMON is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLK_DEV_LOOP=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLK_DEV_RAM=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_BLK_DEV_RAM_COUNT=16
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLK_DEV_RAM_SIZE=73728
|
*/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_XIP is not set
|
|
|
|
|
# CONFIG_CDROM_PKTCDVD is not set
|
|
|
|
|
# CONFIG_ATA_OVER_ETH is not set
|
|
|
|
|
# CONFIG_MG_DISK is not set
|
|
|
|
|
# CONFIG_BLK_DEV_RBD is not set
|
|
|
|
|
# CONFIG_SENSORS_LIS3LV02D is not set
|
|
|
|
|
# CONFIG_MACH_CODINA_CHN is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MISC_DEVICES=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_AD525X_DPOT is not set
|
|
|
|
|
CONFIG_ANDROID_PMEM=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_AB8500_PWM=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_INTEL_MID_PTI is not set
|
|
|
|
|
# CONFIG_ICS932S401 is not set
|
|
|
|
|
# CONFIG_ENCLOSURE_SERVICES is not set
|
|
|
|
|
# CONFIG_KERNEL_DEBUGGER_CORE 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
|
|
|
|
|
# CONFIG_DS1682 is not set
|
|
|
|
|
# CONFIG_TI_DAC7512 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UID_STAT=y
|
|
|
|
|
CONFIG_STE_TRACE_MODEM=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_DBX500_MLOADER=y
|
|
|
|
|
# CONFIG_BMP085 is not set
|
|
|
|
|
# CONFIG_WL127X_RFKILL is not set
|
|
|
|
|
# CONFIG_APANIC is not set
|
|
|
|
|
CONFIG_HWMEM=y
|
|
|
|
|
# CONFIG_DISPDEV is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_COMPDEV=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_COMPDEV_DEBUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CLONEDEV=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_CLONEDEV_DEBUG is not set
|
|
|
|
|
# CONFIG_NFC_PN544 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SAMSUNG_JACK=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_SAMSUNG_JACK_SW_WATERPROOF is not set
|
|
|
|
|
# CONFIG_U8500_SIM_DETECT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_SWITCHER=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_TORCH_FLASH is not set
|
|
|
|
|
CONFIG_GENERIC_BLN=y
|
|
|
|
|
# CONFIG_GENERIC_BLN_EMULATE_BUTTONS_LED is not set
|
|
|
|
|
# CONFIG_GENERIC_BLN_USE_WAKELOCK is not set
|
|
|
|
|
# CONFIG_STM_TRACE is not set
|
|
|
|
|
# CONFIG_C2PORT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# EEPROM support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_EEPROM_AT24 is not set
|
|
|
|
|
# CONFIG_EEPROM_AT25 is not set
|
|
|
|
|
# CONFIG_EEPROM_LEGACY is not set
|
|
|
|
|
# CONFIG_EEPROM_MAX6875 is not set
|
|
|
|
|
# CONFIG_EEPROM_93CX6 is not set
|
|
|
|
|
# CONFIG_IWMC3200TOP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Texas Instruments shared transport line discipline
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_TI_ST is not set
|
|
|
|
|
# CONFIG_SENSORS_LIS3_SPI is not set
|
|
|
|
|
# CONFIG_SENSORS_LIS3_I2C is not set
|
|
|
|
|
# CONFIG_USE_DPP2601 is not set
|
|
|
|
|
# CONFIG_IMMERSION_TSPDRV 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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SCSI=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_DMA=y
|
|
|
|
|
# CONFIG_SCSI_TGT is not set
|
|
|
|
|
# CONFIG_SCSI_NETLINK is not set
|
|
|
|
|
CONFIG_SCSI_PROC_FS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SCSI support type (disk, tape, CD-ROM)
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLK_DEV_SD=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_CHR_DEV_ST is not set
|
|
|
|
|
# CONFIG_CHR_DEV_OSST is not set
|
|
|
|
|
# CONFIG_BLK_DEV_SR is not set
|
|
|
|
|
# CONFIG_CHR_DEV_SG is not set
|
|
|
|
|
# CONFIG_CHR_DEV_SCH is not set
|
|
|
|
|
# CONFIG_SCSI_MULTI_LUN is not set
|
|
|
|
|
# CONFIG_SCSI_CONSTANTS is not set
|
|
|
|
|
# CONFIG_SCSI_LOGGING is not set
|
|
|
|
|
# CONFIG_SCSI_SCAN_ASYNC is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SCSI Transports
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SCSI_SPI_ATTRS is not set
|
|
|
|
|
# CONFIG_SCSI_FC_ATTRS is not set
|
|
|
|
|
# CONFIG_SCSI_ISCSI_ATTRS is not set
|
|
|
|
|
# CONFIG_SCSI_SAS_ATTRS is not set
|
|
|
|
|
# CONFIG_SCSI_SAS_LIBSAS is not set
|
|
|
|
|
# CONFIG_SCSI_SRP_ATTRS is not set
|
|
|
|
|
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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MD=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_BLK_DEV_MD is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLK_DEV_DM=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_DM_DEBUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DM_CRYPT=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_DM_SNAPSHOT is not set
|
|
|
|
|
# CONFIG_DM_MIRROR is not set
|
|
|
|
|
# CONFIG_DM_RAID is not set
|
|
|
|
|
# CONFIG_DM_ZERO is not set
|
|
|
|
|
# CONFIG_DM_MULTIPATH is not set
|
|
|
|
|
# CONFIG_DM_DELAY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DM_UEVENT=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_DM_FLAKEY is not set
|
|
|
|
|
# CONFIG_TARGET_CORE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NETDEVICES=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_IFB is not set
|
|
|
|
|
# CONFIG_DUMMY is not set
|
|
|
|
|
# CONFIG_BONDING is not set
|
|
|
|
|
# CONFIG_MACVLAN is not set
|
|
|
|
|
# CONFIG_EQUALIZER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_TUN=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_VETH is not set
|
|
|
|
|
CONFIG_MII=y
|
|
|
|
|
CONFIG_PHYLIB=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MII PHY device drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MARVELL_PHY is not set
|
|
|
|
|
# CONFIG_DAVICOM_PHY is not set
|
|
|
|
|
# CONFIG_QSEMI_PHY is not set
|
|
|
|
|
# CONFIG_LXT_PHY is not set
|
|
|
|
|
# CONFIG_CICADA_PHY is not set
|
|
|
|
|
# CONFIG_VITESSE_PHY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SMSC_PHY=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_BROADCOM_PHY is not set
|
|
|
|
|
# CONFIG_ICPLUS_PHY is not set
|
|
|
|
|
# CONFIG_REALTEK_PHY is not set
|
|
|
|
|
# CONFIG_NATIONAL_PHY is not set
|
|
|
|
|
# CONFIG_STE10XP is not set
|
|
|
|
|
# CONFIG_LSI_ET1011C_PHY is not set
|
|
|
|
|
# CONFIG_MICREL_PHY is not set
|
|
|
|
|
# CONFIG_FIXED_PHY is not set
|
|
|
|
|
# CONFIG_MDIO_BITBANG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NET_ETHERNET=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_AX88796 is not set
|
|
|
|
|
# CONFIG_SMC91X is not set
|
|
|
|
|
# CONFIG_DM9000 is not set
|
|
|
|
|
# CONFIG_ENC28J60 is not set
|
|
|
|
|
# CONFIG_ETHOC is not set
|
|
|
|
|
# CONFIG_SMC911X is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SMSC911X=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_SMSC911X_ARCH_HOOKS is not set
|
|
|
|
|
# CONFIG_DNET is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_ZMII is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_RGMII is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_TAH is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
|
|
|
|
|
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
|
|
|
|
|
# CONFIG_B44 is not set
|
|
|
|
|
# CONFIG_KS8842 is not set
|
|
|
|
|
# CONFIG_KS8851 is not set
|
|
|
|
|
# CONFIG_KS8851_MLL is not set
|
|
|
|
|
# CONFIG_FTMAC100 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_NETDEV_1000 is not set
|
|
|
|
|
# CONFIG_NETDEV_10000 is not set
|
|
|
|
|
CONFIG_WLAN=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_USB_ZD1201 is not set
|
|
|
|
|
# CONFIG_USB_NET_RNDIS_WLAN is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_WIFI_CONTROL_FUNC=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_ATH_COMMON is not set
|
|
|
|
|
# CONFIG_BCM4329 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BCM4330=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_BCM4334 is not set
|
|
|
|
|
# CONFIG_BCM43241 is not set
|
|
|
|
|
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcmdhd.bin"
|
|
|
|
|
CONFIG_BCMDHD_NVRAM_PATH="/system/etc/wifi/bcmdhd.cal"
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BROADCOM_WIFI_RESERVED_MEM=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_WLAN_REGION_CODE=100
|
|
|
|
|
# CONFIG_HOSTAP is not set
|
|
|
|
|
# CONFIG_IWM is not set
|
|
|
|
|
# CONFIG_LIBERTAS is not set
|
|
|
|
|
# CONFIG_MWIFIEX is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Enable WiMAX (Networking options) to see the WiMAX drivers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Network Adapters
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USB_CATC is not set
|
|
|
|
|
# CONFIG_USB_KAWETH is not set
|
|
|
|
|
# CONFIG_USB_PEGASUS is not set
|
|
|
|
|
# CONFIG_USB_RTL8150 is not set
|
|
|
|
|
# CONFIG_USB_USBNET is not set
|
|
|
|
|
# CONFIG_USB_HSO is not set
|
|
|
|
|
# CONFIG_USB_CDC_PHONET is not set
|
|
|
|
|
# CONFIG_USB_IPHETH is not set
|
|
|
|
|
# CONFIG_WAN is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# CAIF transport drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_CAIF_TTY is not set
|
|
|
|
|
# CONFIG_CAIF_SPI_SLAVE is not set
|
|
|
|
|
# CONFIG_CAIF_HSI is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
|
|
|
|
# CONFIG_PPP_FILTER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PPP_ASYNC=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_SYNC_TTY is not set
|
|
|
|
|
# CONFIG_PPP_DEFLATE is not set
|
|
|
|
|
# CONFIG_PPP_BSDCOMP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PPP_MPPE=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_PPPOE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PPPOLAC=y
|
|
|
|
|
CONFIG_PPPOPNS=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_SLIP is not set
|
|
|
|
|
CONFIG_SLHC=y
|
|
|
|
|
# CONFIG_NETCONSOLE is not set
|
|
|
|
|
# CONFIG_NETPOLL is not set
|
|
|
|
|
# CONFIG_NET_POLL_CONTROLLER is not set
|
|
|
|
|
# CONFIG_ISDN is not set
|
|
|
|
|
# CONFIG_PHONE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Input device support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_INPUT=y
|
|
|
|
|
# CONFIG_INPUT_FF_MEMLESS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_POLLDEV=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_SPARSEKMAP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Userland interfaces
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_INPUT_MOUSEDEV 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_JOYDEV is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_EVDEV=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_EVBUG is not set
|
|
|
|
|
# CONFIG_INPUT_KEYRESET is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Input Device Drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_INPUT_KEYBOARD=y
|
|
|
|
|
# CONFIG_KEYBOARD_ADP5588 is not set
|
|
|
|
|
# CONFIG_KEYBOARD_ADP5589 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_KEYBOARD_ATKBD 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_QT1070 is not set
|
|
|
|
|
# CONFIG_KEYBOARD_QT2160 is not set
|
|
|
|
|
# CONFIG_KEYBOARD_LKKBD is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KEYBOARD_GPIO=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_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_NOMADIK_SKE is not set
|
|
|
|
|
# CONFIG_KEYBOARD_OPENCORES is not set
|
|
|
|
|
# CONFIG_KEYBOARD_STOWAWAY is not set
|
|
|
|
|
# CONFIG_KEYBOARD_SUNKBD is not set
|
|
|
|
|
# CONFIG_KEYBOARD_STMPE is not set
|
|
|
|
|
# CONFIG_KEYBOARD_XTKBD is not set
|
|
|
|
|
# CONFIG_KEYBOARD_NTS_TOUCHKEY is not set
|
|
|
|
|
# CONFIG_KEYBOARD_TC360_TOUCHKEY is not set
|
|
|
|
|
# CONFIG_KEYBOARD_CYPRESS_TOUCH is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_INPUT_MOUSE 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_JOYSTICK is not set
|
|
|
|
|
# CONFIG_INPUT_TABLET is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_TOUCHSCREEN=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_TOUCHSCREEN_ADS7846 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_AD7877 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_AD7879 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_MXT224S is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_BU21013 is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_CY8CTMG110 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_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_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_STMPE is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TPS6507X is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_TOUCHSCREEN_ZINITIX_BT404=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_TOUCHSCREEN_ZINITIX is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_ATMEL_MXT224E is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MMS136_TS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MMS134S_TS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_MMS1XX_TS is not set
|
|
|
|
|
# CONFIG_TOUCHSCREEN_TMA140 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_MISC=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_AB8500_ACCDET is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_AB8500_PONKEY=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_AB8505_MICRO_USB_DETECT is not set
|
|
|
|
|
# CONFIG_INPUT_AD714X is not set
|
|
|
|
|
# CONFIG_INPUT_ATI_REMOTE is not set
|
|
|
|
|
# CONFIG_INPUT_ATI_REMOTE2 is not set
|
|
|
|
|
# CONFIG_INPUT_KEYCHORD is not set
|
|
|
|
|
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
|
|
|
|
|
# CONFIG_INPUT_LPS001WP is not set
|
|
|
|
|
# CONFIG_INPUT_LPS331AP is not set
|
|
|
|
|
# CONFIG_INPUT_POWERMATE is not set
|
|
|
|
|
# CONFIG_INPUT_YEALINK is not set
|
|
|
|
|
# CONFIG_INPUT_CM109 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_INPUT_UINPUT=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_GPIO is not set
|
|
|
|
|
# CONFIG_INPUT_PCF8574 is not set
|
|
|
|
|
# CONFIG_INPUT_PWM_BEEPER is not set
|
|
|
|
|
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
|
|
|
|
|
# CONFIG_INPUT_ADXL34X is not set
|
|
|
|
|
# CONFIG_INPUT_CMA3000 is not set
|
|
|
|
|
# CONFIG_INPUT_MPU6050 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Hardware I/O ports
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SERIO=y
|
|
|
|
|
CONFIG_SERIO_SERPORT=y
|
|
|
|
|
# CONFIG_SERIO_AMBAKMI is not set
|
|
|
|
|
# CONFIG_SERIO_LIBPS2 is not set
|
|
|
|
|
# CONFIG_SERIO_RAW is not set
|
|
|
|
|
# CONFIG_SERIO_ALTERA_PS2 is not set
|
|
|
|
|
# CONFIG_SERIO_PS2MULT is not set
|
|
|
|
|
# CONFIG_GAMEPORT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
|
*/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
|
|
|
#
|
|
|
|
|
# Character devices
|
|
|
|
|
#
|
|
|
|
|
CONFIG_VT=y
|
|
|
|
|
CONFIG_CONSOLE_TRANSLATIONS=y
|
|
|
|
|
# CONFIG_VT_CONSOLE is not set
|
|
|
|
|
CONFIG_HW_CONSOLE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_VT_HW_CONSOLE_BINDING=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_UNIX98_PTYS=y
|
2021-04-29 11:38:24 +00:00
|
|
|
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_LEGACY_PTYS 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_NONSTANDARD is not set
|
|
|
|
|
# CONFIG_N_GSM is not set
|
|
|
|
|
# CONFIG_TRACE_SINK is not set
|
|
|
|
|
CONFIG_DEVMEM=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_DEVKMEM 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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Serial drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SERIAL_8250 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Non-8250 serial port support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SERIAL_AMBA_PL010 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SERIAL_AMBA_PL011=y
|
|
|
|
|
CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
|
|
|
|
|
CONFIG_SERIAL_AMBA_PL011_CLOCK_CONTROL=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_SERIAL_MAX3100 is not set
|
|
|
|
|
# CONFIG_SERIAL_MAX3107 is not set
|
|
|
|
|
CONFIG_SERIAL_CORE=y
|
|
|
|
|
CONFIG_SERIAL_CORE_CONSOLE=y
|
|
|
|
|
CONFIG_CONSOLE_POLL=y
|
|
|
|
|
# CONFIG_SERIAL_TIMBERDALE is not set
|
|
|
|
|
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
|
|
|
|
|
# CONFIG_SERIAL_ALTERA_UART is not set
|
|
|
|
|
# CONFIG_SERIAL_IFX6X60 is not set
|
|
|
|
|
# CONFIG_SERIAL_XILINX_PS_UART is not set
|
|
|
|
|
# CONFIG_TTY_PRINTK is not set
|
|
|
|
|
# CONFIG_HVC_DCC is not set
|
|
|
|
|
# CONFIG_IPMI_HANDLER is not set
|
|
|
|
|
CONFIG_HW_RANDOM=m
|
|
|
|
|
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
|
|
|
|
|
# CONFIG_HW_RANDOM_NOMADIK is not set
|
|
|
|
|
# CONFIG_R3964 is not set
|
|
|
|
|
# CONFIG_RAW_DRIVER is not set
|
|
|
|
|
# CONFIG_TCG_TPM is not set
|
|
|
|
|
# CONFIG_DCC_TTY is not set
|
|
|
|
|
# CONFIG_RAMOOPS is not set
|
|
|
|
|
CONFIG_HWREG=m
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_I2C=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_BOARDINFO=y
|
|
|
|
|
CONFIG_I2C_COMPAT=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_I2C_CHARDEV=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_MUX is not set
|
|
|
|
|
CONFIG_I2C_HELPER_AUTO=y
|
|
|
|
|
CONFIG_I2C_ALGOBIT=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C Hardware Bus support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C system bus drivers (mostly embedded / system-on-chip)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_DESIGNWARE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_I2C_GPIO=y
|
|
|
|
|
CONFIG_I2C_NOMADIK=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
|
|
|
|
|
# CONFIG_I2C_PCA_PLATFORM is not set
|
|
|
|
|
# CONFIG_I2C_PXA_PCI is not set
|
|
|
|
|
# CONFIG_I2C_SIMTEC is not set
|
|
|
|
|
# CONFIG_I2C_XILINX is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# External I2C/SMBus adapter drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_DIOLAN_U2C is not set
|
|
|
|
|
# CONFIG_I2C_PARPORT_LIGHT is not set
|
|
|
|
|
# CONFIG_I2C_TAOS_EVM is not set
|
|
|
|
|
# CONFIG_I2C_TINY_USB is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Other I2C/SMBus bus drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_I2C_STUB is not set
|
|
|
|
|
# CONFIG_I2C_DEBUG_CORE is not set
|
|
|
|
|
# CONFIG_I2C_DEBUG_ALGO is not set
|
|
|
|
|
# CONFIG_I2C_DEBUG_BUS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SPI=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_SPI_DEBUG is not set
|
|
|
|
|
CONFIG_SPI_MASTER=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI Master Controller Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SPI_ALTERA is not set
|
|
|
|
|
CONFIG_SPI_BITBANG=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_STM_MSP_SPI is not set
|
|
|
|
|
CONFIG_SPI_GPIO=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_SPI_OC_TINY is not set
|
|
|
|
|
# CONFIG_SPI_PL022 is not set
|
|
|
|
|
# CONFIG_SPI_PXA2XX_PCI is not set
|
|
|
|
|
# CONFIG_SPI_XILINX is not set
|
|
|
|
|
# CONFIG_SPI_DESIGNWARE is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# SPI Protocol Masters
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SPI_SPIDEV is not set
|
|
|
|
|
# CONFIG_SPI_TLE62X0 is not set
|
|
|
|
|
# CONFIG_HSI is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PPS support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_PPS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PPS generators support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PTP clock support
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Enable Device Drivers -> PPS to see the PTP clock options.
|
|
|
|
|
#
|
|
|
|
|
CONFIG_ARCH_REQUIRE_GPIOLIB=y
|
|
|
|
|
CONFIG_GPIOLIB=y
|
|
|
|
|
# CONFIG_DEBUG_GPIO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_GPIO_SYSFS=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Memory mapped GPIO drivers:
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_GPIO_GENERIC_PLATFORM is not set
|
|
|
|
|
# CONFIG_GPIO_IT8761E is not set
|
|
|
|
|
# CONFIG_GPIO_PL061 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# I2C GPIO expanders:
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_GPIO_MAX7300 is not set
|
|
|
|
|
# CONFIG_GPIO_MAX732X is not set
|
|
|
|
|
# CONFIG_GPIO_PCF857X is not set
|
|
|
|
|
# CONFIG_GPIO_SX150X is not set
|
|
|
|
|
# CONFIG_GPIO_STMPE 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:
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_GPIO_AB8500=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_W1 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_POWER_SUPPLY=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_POWER_SUPPLY_DEBUG is not set
|
|
|
|
|
# CONFIG_PDA_POWER is not set
|
|
|
|
|
# CONFIG_TEST_POWER is not set
|
|
|
|
|
# CONFIG_FAKE_DFMS_DEVICES is not set
|
|
|
|
|
CONFIG_ABB_FAKE_DFMS_DEVICES=y
|
|
|
|
|
# CONFIG_BATTERY_DS2780 is not set
|
|
|
|
|
# CONFIG_BATTERY_DS2782 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_GPIO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SAMSUNG_CHARGER_SPEC=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_AB8500_BM is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ABB_BM=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_MEASURE_TEMP_BY_ADC_TABLE is not set
|
|
|
|
|
CONFIG_HWMON=y
|
|
|
|
|
# CONFIG_HWMON_VID is not set
|
|
|
|
|
# CONFIG_HWMON_DEBUG_CHIP is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Native drivers
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SENSORS_AB8500=y
|
|
|
|
|
CONFIG_SENSORS_DBX500=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_SENSORS_AD7414 is not set
|
|
|
|
|
# CONFIG_SENSORS_AD7418 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADCXX is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM1021 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM1025 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM1026 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM1029 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM1031 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADM9240 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7411 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7462 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7470 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADT7475 is not set
|
|
|
|
|
# CONFIG_SENSORS_ASC7621 is not set
|
|
|
|
|
# CONFIG_SENSORS_ATXP1 is not set
|
|
|
|
|
# CONFIG_SENSORS_DS620 is not set
|
|
|
|
|
# CONFIG_SENSORS_DS1621 is not set
|
|
|
|
|
# CONFIG_SENSORS_F71805F is not set
|
|
|
|
|
# CONFIG_SENSORS_F71882FG is not set
|
|
|
|
|
# CONFIG_SENSORS_F75375S is not set
|
|
|
|
|
# CONFIG_SENSORS_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
|
|
|
|
|
# CONFIG_SENSORS_LINEAGE is not set
|
|
|
|
|
# CONFIG_SENSORS_LM63 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM70 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM73 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM75 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM77 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM78 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM80 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM83 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM85 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM87 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM90 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM92 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM93 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4151 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4215 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4245 is not set
|
|
|
|
|
# CONFIG_SENSORS_LTC4261 is not set
|
|
|
|
|
# CONFIG_SENSORS_LM95241 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX1111 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX16065 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX1619 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX6639 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX6642 is not set
|
|
|
|
|
# CONFIG_SENSORS_MAX6650 is not set
|
|
|
|
|
# CONFIG_SENSORS_PC87360 is not set
|
|
|
|
|
# CONFIG_SENSORS_PC87427 is not set
|
|
|
|
|
# CONFIG_SENSORS_PCF8591 is not set
|
|
|
|
|
# CONFIG_PMBUS is not set
|
|
|
|
|
# CONFIG_SENSORS_SHT15 is not set
|
|
|
|
|
# CONFIG_SENSORS_SHT21 is not set
|
|
|
|
|
# CONFIG_SENSORS_SMM665 is not set
|
|
|
|
|
# CONFIG_SENSORS_DME1737 is not set
|
|
|
|
|
# CONFIG_SENSORS_EMC1403 is not set
|
|
|
|
|
# CONFIG_SENSORS_EMC2103 is not set
|
|
|
|
|
# CONFIG_SENSORS_EMC6W201 is not set
|
|
|
|
|
# CONFIG_SENSORS_SMSC47M1 is not set
|
|
|
|
|
# CONFIG_SENSORS_SMSC47M192 is not set
|
|
|
|
|
# CONFIG_SENSORS_SMSC47B397 is not set
|
|
|
|
|
# CONFIG_SENSORS_SCH5627 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS1015 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS7828 is not set
|
|
|
|
|
# CONFIG_SENSORS_ADS7871 is not set
|
|
|
|
|
# CONFIG_SENSORS_AMC6821 is not set
|
|
|
|
|
# CONFIG_SENSORS_THMC50 is not set
|
|
|
|
|
# CONFIG_SENSORS_TMP102 is not set
|
|
|
|
|
# CONFIG_SENSORS_TMP401 is not set
|
|
|
|
|
# CONFIG_SENSORS_TMP421 is not set
|
|
|
|
|
# CONFIG_SENSORS_VT1211 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83781D is not set
|
|
|
|
|
# CONFIG_SENSORS_W83791D is not set
|
|
|
|
|
# CONFIG_SENSORS_W83792D is not set
|
|
|
|
|
# CONFIG_SENSORS_W83793 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83795 is not set
|
|
|
|
|
# CONFIG_SENSORS_W83L785TS is not set
|
|
|
|
|
# CONFIG_SENSORS_W83L786NG is not set
|
|
|
|
|
# CONFIG_SENSORS_W83627HF is not set
|
|
|
|
|
# CONFIG_SENSORS_W83627EHF is not set
|
|
|
|
|
# CONFIG_THERMAL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_WATCHDOG=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_WATCHDOG_NOWAYOUT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Watchdog Device Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_SOFT_WATCHDOG is not set
|
|
|
|
|
# CONFIG_ARM_SP805_WATCHDOG is not set
|
|
|
|
|
# CONFIG_MPCORE_WATCHDOG is not set
|
|
|
|
|
# CONFIG_MAX63XX_WATCHDOG is not set
|
|
|
|
|
CONFIG_UX500_WATCHDOG=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UX500_WATCHDOG_DEBUG=y
|
|
|
|
|
CONFIG_UX500_WATCHDOG_KERNEL_KICKER=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB-based Watchdog Cards
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USBPCWATCHDOG 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_TPS6507X is not set
|
|
|
|
|
# CONFIG_MFD_TPS6586X is not set
|
|
|
|
|
# CONFIG_TWL4030_CORE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MFD_STMPE=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# STMPE Interface Drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_STMPE_I2C=y
|
|
|
|
|
# CONFIG_STMPE_SPI is not set
|
|
|
|
|
# CONFIG_MFD_TC3589X is not set
|
|
|
|
|
# CONFIG_MFD_TC35892 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_AB5500_CORE 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=y
|
|
|
|
|
# CONFIG_AB3100_CORE is not set
|
|
|
|
|
# CONFIG_EZX_PCAP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_AB8500_CORE=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_AB8500_I2C_CORE=y
|
|
|
|
|
# CONFIG_AB8500_DENC is not set
|
|
|
|
|
CONFIG_AB8500_DEBUG=y
|
|
|
|
|
CONFIG_AB8500_GPADC=y
|
|
|
|
|
# CONFIG_AB3550_CORE is not set
|
|
|
|
|
CONFIG_DBX500_PRCMU=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MFD_DB8500_PRCMU=y
|
|
|
|
|
CONFIG_MFD_DBX540_PRCMU=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_DB8500_LIVEOPP is not set
|
|
|
|
|
CONFIG_LIVEOPP_DEBUG=0
|
|
|
|
|
# CONFIG_MFD_WL1273_CORE is not set
|
|
|
|
|
# CONFIG_MFD_TPS65910 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_REGULATOR=y
|
|
|
|
|
CONFIG_REGULATOR_DEBUG=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_REGULATOR_DUMMY is not set
|
|
|
|
|
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_REGULATOR_VIRTUAL_CONSUMER=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_REGULATOR_AB8500=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_REGULATOR_AB8500_EXT=y
|
|
|
|
|
CONFIG_REGULATOR_DBX500_PRCMU=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_REGULATOR_DB8500_PRCMU=y
|
|
|
|
|
CONFIG_REGULATOR_AB8500_DEBUG=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_REGULATOR_TPS6524X is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MEDIA_SUPPORT=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Multimedia core support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MEDIA_CONTROLLER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_VIDEO_DEV=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_VIDEO_V4L2_COMMON=y
|
|
|
|
|
# CONFIG_DVB_CORE is not set
|
|
|
|
|
CONFIG_VIDEO_MEDIA=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Multimedia drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RC_CORE is not set
|
|
|
|
|
# CONFIG_MEDIA_ATTACH is not set
|
|
|
|
|
# CONFIG_MEDIA_TUNER is not set
|
|
|
|
|
CONFIG_VIDEO_V4L2=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_VIDEO_CAPTURE_DRIVERS 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_V4L_MEM2MEM_DRIVERS is not set
|
|
|
|
|
CONFIG_RADIO_ADAPTERS=y
|
|
|
|
|
# CONFIG_I2C_SI4713 is not set
|
|
|
|
|
# CONFIG_RADIO_SI4713 is not set
|
|
|
|
|
# CONFIG_USB_DSBR is not set
|
|
|
|
|
# CONFIG_RADIO_SI470X is not set
|
|
|
|
|
# CONFIG_USB_MR800 is not set
|
|
|
|
|
# CONFIG_RADIO_TEA5764 is not set
|
|
|
|
|
# CONFIG_RADIO_SAA7706H is not set
|
|
|
|
|
# CONFIG_RADIO_TEF6862 is not set
|
|
|
|
|
# CONFIG_RADIO_WL1273 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
|
*/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
|
|
|
#
|
|
|
|
|
# Texas Instruments WL128x FM driver (ST based)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RADIO_WL128X is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Graphics support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_DRM is not set
|
|
|
|
|
# CONFIG_ION is not set
|
|
|
|
|
CONFIG_GPU_MALI=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MALI400=y
|
|
|
|
|
CONFIG_MALI400_DEBUG=y
|
|
|
|
|
CONFIG_MALI400_PROFILING=y
|
|
|
|
|
CONFIG_MALI400_GPU_UTILIZATION=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_VGASTATE is not set
|
|
|
|
|
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_FB=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_FIRMWARE_EDID is not set
|
|
|
|
|
# CONFIG_FB_DDC is not set
|
|
|
|
|
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
|
|
|
|
|
# CONFIG_FB_CFB_FILLRECT is not set
|
|
|
|
|
# CONFIG_FB_CFB_COPYAREA is not set
|
|
|
|
|
# CONFIG_FB_CFB_IMAGEBLIT is not set
|
|
|
|
|
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
|
|
|
|
|
CONFIG_FB_SYS_FILLRECT=y
|
|
|
|
|
CONFIG_FB_SYS_COPYAREA=y
|
|
|
|
|
CONFIG_FB_SYS_IMAGEBLIT=y
|
|
|
|
|
# CONFIG_FB_FOREIGN_ENDIAN is not set
|
|
|
|
|
CONFIG_FB_SYS_FOPS=y
|
|
|
|
|
# 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_MCDE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_FB_MCDE=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_FB_MCDE_DEBUG is not set
|
|
|
|
|
# CONFIG_MCDE_FB_AVOID_REALLOC is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_MCDE_DISPLAY_DSI is not set
|
|
|
|
|
CONFIG_MCDE_DISPLAY_DPI=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MCDE DPI displays
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_MCDE_DISPLAY_VUIB500_DPI is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MCDE_DISPLAY_WS2401_DPI=y
|
|
|
|
|
CONFIG_MCDE_DISPLAY_S6D27A1_DPI=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_MCDE_DISPLAY_LD9040_DPI is not set
|
|
|
|
|
# CONFIG_MCDE_DISPLAY_S6E63MN0_DPI is not set
|
|
|
|
|
# CONFIG_MCDE_DISPLAY_GAVINI_DPI is not set
|
|
|
|
|
# CONFIG_MCDE_DISPLAY_LMS397KF_DPI is not set
|
|
|
|
|
# CONFIG_MCDE_DISPLAY_I9060_DPI is not set
|
|
|
|
|
# CONFIG_FB_ARMCLCD is not set
|
|
|
|
|
# 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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BACKLIGHT_LCD_SUPPORT=y
|
|
|
|
|
CONFIG_LCD_CLASS_DEVICE=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_LCD_L4F00242T03 is not set
|
|
|
|
|
# CONFIG_LCD_LMS283GF05 is not set
|
|
|
|
|
# CONFIG_LCD_LTV350QV is not set
|
|
|
|
|
# CONFIG_LCD_TDO24M is not set
|
|
|
|
|
# CONFIG_LCD_VGG2432A4 is not set
|
|
|
|
|
# CONFIG_LCD_PLATFORM is not set
|
|
|
|
|
# CONFIG_LCD_S6E63M0 is not set
|
|
|
|
|
# CONFIG_LCD_LD9040 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BACKLIGHT_CLASS_DEVICE=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_BACKLIGHT_GENERIC=y
|
|
|
|
|
# CONFIG_BACKLIGHT_PWM is not set
|
|
|
|
|
# CONFIG_BACKLIGHT_ADP8860 is not set
|
|
|
|
|
# CONFIG_BACKLIGHT_ADP8870 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BACKLIGHT_KTD259=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_BACKLIGHT_KTD253 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Display device support
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_DISPLAY_SUPPORT is not set
|
|
|
|
|
# CONFIG_AV8100 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_FB_B2R2=y
|
|
|
|
|
CONFIG_B2R2_PLUG_CONF=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_B2R2_OPSIZE_8 is not set
|
|
|
|
|
# CONFIG_B2R2_OPSIZE_16 is not set
|
|
|
|
|
# CONFIG_B2R2_OPSIZE_32 is not set
|
|
|
|
|
CONFIG_B2R2_OPSIZE_64=y
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_1 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_2 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_4 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_8 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_16 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_32 is not set
|
|
|
|
|
# CONFIG_B2R2_CHSIZE_64 is not set
|
|
|
|
|
CONFIG_B2R2_CHSIZE_128=y
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_1 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_2 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_4 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_8 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_16 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_32 is not set
|
|
|
|
|
# CONFIG_B2R2_MGSIZE_64 is not set
|
|
|
|
|
CONFIG_B2R2_MGSIZE_128=y
|
|
|
|
|
# CONFIG_B2R2_PGSIZE_64 is not set
|
|
|
|
|
# CONFIG_B2R2_PGSIZE_128 is not set
|
|
|
|
|
CONFIG_B2R2_PGSIZE_256=y
|
|
|
|
|
# CONFIG_B2R2_DEBUG is not set
|
|
|
|
|
# CONFIG_B2R2_PROFILER is not set
|
|
|
|
|
CONFIG_B2R2_GENERIC=y
|
|
|
|
|
CONFIG_B2R2_GENERIC_FALLBACK=y
|
|
|
|
|
# CONFIG_B2R2_GENERIC_ONLY is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Console display driver support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_DUMMY_CONSOLE=y
|
|
|
|
|
# CONFIG_FRAMEBUFFER_CONSOLE is not set
|
|
|
|
|
# CONFIG_LOGO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SOUND=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_SOUND_OSS_CORE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SND=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_SND_TIMER=y
|
|
|
|
|
CONFIG_SND_PCM=y
|
|
|
|
|
CONFIG_SND_HWDEP=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=y
|
|
|
|
|
# CONFIG_SND_DUMMY is not set
|
|
|
|
|
# CONFIG_SND_ALOOP is not set
|
|
|
|
|
# CONFIG_SND_MTPAV is not set
|
|
|
|
|
# CONFIG_SND_SERIAL_U16550 is not set
|
|
|
|
|
# CONFIG_SND_MPU401 is not set
|
|
|
|
|
CONFIG_SND_ARM=y
|
|
|
|
|
# CONFIG_SND_ARMAACI is not set
|
|
|
|
|
CONFIG_SND_SPI=y
|
|
|
|
|
CONFIG_SND_USB=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SND_USB_AUDIO=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_SND_USB_UA101 is not set
|
|
|
|
|
# CONFIG_SND_USB_CAIAQ is not set
|
|
|
|
|
# CONFIG_SND_USB_6FIRE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SND_SOC=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_SND_SOC_CACHE_LZO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SND_SOC_UX500=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_SND_SOC_U8500=y
|
|
|
|
|
# CONFIG_SND_SOC_U5500 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SND_SOC_UX500_AB8500=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_SND_SOC_UX500_DEBUG is not set
|
|
|
|
|
# CONFIG_SND_SOC_UX500_AB8500_MID_WIDGET is not set
|
|
|
|
|
CONFIG_SND_SOC_I2C_AND_SPI=y
|
|
|
|
|
# CONFIG_SND_SOC_ALL_CODECS is not set
|
|
|
|
|
CONFIG_SND_SOC_AB8500=y
|
|
|
|
|
# CONFIG_SOUND_PRIME is not set
|
|
|
|
|
CONFIG_HID_SUPPORT=y
|
|
|
|
|
CONFIG_HID=y
|
|
|
|
|
# CONFIG_HIDRAW is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Input Devices
|
|
|
|
|
#
|
|
|
|
|
CONFIG_USB_HID=y
|
|
|
|
|
# CONFIG_HID_PID is not set
|
|
|
|
|
# CONFIG_USB_HIDDEV is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Special HID drivers
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_A4TECH=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_HID_ACRUX is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_APPLE=y
|
|
|
|
|
CONFIG_HID_BELKIN=y
|
|
|
|
|
CONFIG_HID_CHERRY=y
|
|
|
|
|
CONFIG_HID_CHICONY=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_HID_PRODIKEYS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_CYPRESS=y
|
|
|
|
|
CONFIG_HID_DRAGONRISE=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_DRAGONRISE_FF is not set
|
|
|
|
|
# CONFIG_HID_EMS_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_ELECOM=y
|
|
|
|
|
CONFIG_HID_EZKEY=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_HID_KEYTOUCH is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_KYE=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_HID_UCLOGIC is not set
|
|
|
|
|
# CONFIG_HID_WALTOP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_GYRATION=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_HID_TWINHAN is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_KENSINGTON=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_HID_LCPOWER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_LOGITECH=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_LOGITECH_FF is not set
|
|
|
|
|
# CONFIG_LOGIRUMBLEPAD2_FF is not set
|
|
|
|
|
# CONFIG_LOGIG940_FF is not set
|
|
|
|
|
# CONFIG_LOGIWII_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_MAGICMOUSE=y
|
|
|
|
|
CONFIG_HID_MICROSOFT=y
|
|
|
|
|
CONFIG_HID_MONTEREY=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_HID_MULTITOUCH is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_NTRIG=y
|
|
|
|
|
CONFIG_HID_ORTEK=y
|
|
|
|
|
CONFIG_HID_PANTHERLORD=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_PANTHERLORD_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_PETALYNX=y
|
|
|
|
|
CONFIG_HID_PICOLCD=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_HID_PICOLCD_FB is not set
|
|
|
|
|
# CONFIG_HID_PICOLCD_BACKLIGHT is not set
|
|
|
|
|
# CONFIG_HID_PICOLCD_LCD is not set
|
|
|
|
|
# CONFIG_HID_PICOLCD_LEDS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_QUANTA=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_HID_ROCCAT=y
|
|
|
|
|
CONFIG_HID_ROCCAT_COMMON=y
|
|
|
|
|
# CONFIG_HID_ROCCAT_ARVO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_ROCCAT_KONE=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_HID_ROCCAT_KONEPLUS is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_KOVAPLUS is not set
|
|
|
|
|
# CONFIG_HID_ROCCAT_PYRA is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_SAMSUNG=y
|
|
|
|
|
CONFIG_HID_SONY=y
|
|
|
|
|
CONFIG_HID_SUNPLUS=y
|
|
|
|
|
CONFIG_HID_GREENASIA=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_GREENASIA_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_SMARTJOYPLUS=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_SMARTJOYPLUS_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_TOPSEED=y
|
|
|
|
|
CONFIG_HID_THRUSTMASTER=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_THRUSTMASTER_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_WACOM=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_HID_WACOM_POWER_SUPPLY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_ZEROPLUS=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_ZEROPLUS_FF is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_HID_ZYDACRON=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_USB_SUPPORT=y
|
|
|
|
|
CONFIG_USB_ARCH_HAS_HCD=y
|
|
|
|
|
# CONFIG_USB_ARCH_HAS_OHCI is not set
|
|
|
|
|
# CONFIG_USB_ARCH_HAS_EHCI is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB=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_USB_DEBUG is not set
|
|
|
|
|
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Miscellaneous USB options
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_DEVICEFS=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_USB_DEVICE_CLASS=y
|
|
|
|
|
# CONFIG_USB_DYNAMIC_MINORS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_SUSPEND=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_USB_OTG=y
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_USB_OTG_WHITELIST 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_OTG_BLACKLIST_HUB is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_MON=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_USB_WUSB is not set
|
|
|
|
|
# CONFIG_USB_WUSB_CBAF is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Host Controller Drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_USB_C67X00_HCD is not set
|
|
|
|
|
# CONFIG_USB_OXU210HP_HCD is not set
|
|
|
|
|
# CONFIG_USB_ISP116X_HCD is not set
|
|
|
|
|
# CONFIG_USB_ISP1760_HCD is not set
|
|
|
|
|
# CONFIG_USB_ISP1362_HCD is not set
|
|
|
|
|
# CONFIG_USB_SL811_HCD is not set
|
|
|
|
|
# CONFIG_USB_R8A66597_HCD is not set
|
|
|
|
|
# CONFIG_USB_HWA_HCD is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_MUSB_HDRC=y
|
|
|
|
|
CONFIG_USB_MUSB_UX500=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_USB_MUSB_HOST is not set
|
|
|
|
|
# CONFIG_USB_MUSB_PERIPHERAL is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_MUSB_OTG=y
|
|
|
|
|
CONFIG_USB_GADGET_MUSB_HDRC=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_USB_MUSB_HDRC_HCD=y
|
|
|
|
|
# CONFIG_MUSB_PIO_ONLY is not set
|
|
|
|
|
CONFIG_USB_UX500_DMA=y
|
|
|
|
|
# CONFIG_USB_INVENTRA_DMA is not set
|
|
|
|
|
# CONFIG_USB_TI_CPPI_DMA is not set
|
|
|
|
|
# CONFIG_USB_MUSB_DEBUG is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Device Class drivers
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_ACM=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_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
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_STORAGE=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_LIBUSUAL=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 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_ISIGHTFW is not set
|
|
|
|
|
# CONFIG_USB_YUREX is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_GADGET=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_USB_GADGET_DEBUG is not set
|
|
|
|
|
# CONFIG_USB_GADGET_DEBUG_FILES is not set
|
|
|
|
|
# CONFIG_USB_GADGET_DEBUG_FS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_USB_GADGET_VBUS_DRAW=500
|
*/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_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_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
|
|
|
|
|
# CONFIG_USB_GADGETFS is not set
|
|
|
|
|
# CONFIG_USB_FUNCTIONFS is not set
|
|
|
|
|
# CONFIG_USB_FILE_STORAGE is not set
|
|
|
|
|
# CONFIG_USB_MASS_STORAGE is not set
|
|
|
|
|
# CONFIG_USB_G_SERIAL is not set
|
|
|
|
|
# CONFIG_USB_MIDI_GADGET is not set
|
|
|
|
|
# CONFIG_USB_G_PRINTER is not set
|
|
|
|
|
# CONFIG_USB_CDC_COMPOSITE is not set
|
|
|
|
|
# CONFIG_USB_G_NOKIA is not set
|
|
|
|
|
# CONFIG_USB_G_MULTI is not set
|
|
|
|
|
# CONFIG_USB_G_HID is not set
|
|
|
|
|
# CONFIG_USB_G_DBGP is not set
|
|
|
|
|
# CONFIG_USB_G_WEBCAM is not set
|
|
|
|
|
# CONFIG_USB_OTG_20 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_NOP_USB_XCEIV is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_AB8500_USB=y
|
|
|
|
|
CONFIG_MMC=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_DEBUG is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MMC_PARANOID_SD_INIT=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MMC/SD/SDIO Card Drivers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MMC_BLOCK=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MMC_BLOCK_MINORS=32
|
|
|
|
|
# CONFIG_MMC_BLOCK_BOUNCE 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_SDIO_UART is not set
|
|
|
|
|
# CONFIG_MMC_TEST is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MMC/SD/SDIO Host Controller Drivers
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MMC_ARMMMCI=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_SDHCI is not set
|
|
|
|
|
# CONFIG_MMC_DW is not set
|
|
|
|
|
# CONFIG_MMC_VUB300 is not set
|
|
|
|
|
# CONFIG_MMC_USHC is not set
|
|
|
|
|
# CONFIG_MEMSTICK is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NEW_LEDS=y
|
|
|
|
|
CONFIG_LEDS_CLASS=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_FLASH_LED_KTD267 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# LED drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_LEDS_LM3530 is not set
|
|
|
|
|
# CONFIG_LEDS_PCA9532 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_LEDS_GPIO=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_LEDS_GPIO_PLATFORM=y
|
|
|
|
|
# CONFIG_LEDS_LP3944 is not set
|
|
|
|
|
# CONFIG_LEDS_LP5521 is not set
|
|
|
|
|
# CONFIG_LEDS_LP5523 is not set
|
|
|
|
|
# CONFIG_LEDS_PCA955X is not set
|
|
|
|
|
# CONFIG_LEDS_DAC124S085 is not set
|
|
|
|
|
# CONFIG_LEDS_PWM is not set
|
|
|
|
|
# CONFIG_LEDS_REGULATOR is not set
|
|
|
|
|
# CONFIG_LEDS_BD2802 is not set
|
|
|
|
|
# CONFIG_LEDS_LT3593 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_LEDS_TRIGGERS=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 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
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# iptables trigger is under Netfilter config (LED target)
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NFC_DEVICES is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SWITCH=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_SWITCH_GPIO is not set
|
|
|
|
|
# CONFIG_ACCESSIBILITY is not set
|
|
|
|
|
CONFIG_RTC_LIB=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RTC_CLASS=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_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_DEV_UIE_EMUL is not set
|
|
|
|
|
CONFIG_RTC_INTF_ALARM=y
|
|
|
|
|
CONFIG_RTC_INTF_ALARM_DEV=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RTC_ALARM_DEV_NAME="pl031"
|
*/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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RTC_DRV_AB8500=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# on-CPU RTC drivers
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_RTC_DRV_PL030 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_RTC_DRV_PL031=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_MACH_SEC_GOLDEN_CHN is not set
|
|
|
|
|
# CONFIG_MACH_JANICE_CHN is not set
|
|
|
|
|
# CONFIG_MACH_GAVINI_CHN is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DMADEVICES=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_DMADEVICES_DEBUG is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# DMA Devices
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_AMBA_PL08X is not set
|
|
|
|
|
# CONFIG_DW_DMAC is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_STE_DMA40=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_TIMB_DMA is not set
|
|
|
|
|
CONFIG_DMA_ENGINE=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# DMA Clients
|
|
|
|
|
#
|
|
|
|
|
# CONFIG_NET_DMA is not set
|
|
|
|
|
# CONFIG_ASYNC_TX_DMA is not set
|
|
|
|
|
# CONFIG_DMATEST is not set
|
|
|
|
|
# CONFIG_AUXDISPLAY is not set
|
|
|
|
|
# CONFIG_UIO is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
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
|
|
|
|
|
# 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
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ANDROID=y
|
|
|
|
|
CONFIG_ANDROID_BINDER_IPC=y
|
|
|
|
|
CONFIG_ANDROID_LOGGER=y
|
|
|
|
|
CONFIG_ANDROID_RAM_CONSOLE=y
|
|
|
|
|
# CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE 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_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
|
|
|
|
|
# CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT is not set
|
|
|
|
|
CONFIG_ANDROID_TIMED_OUTPUT=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ANDROID_TIMED_GPIO=y
|
|
|
|
|
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
|
|
|
|
|
# CONFIG_ANDROID_STE_TIMED_VIBRA 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_POHMELFS is not set
|
|
|
|
|
# CONFIG_LINE6_USB is not set
|
|
|
|
|
# CONFIG_VT6656 is not set
|
|
|
|
|
# CONFIG_IIO is not set
|
|
|
|
|
# CONFIG_XVMALLOC is not set
|
|
|
|
|
# CONFIG_ZRAM is not set
|
|
|
|
|
# CONFIG_FB_SM7XX is not set
|
|
|
|
|
# CONFIG_EASYCAP is not set
|
|
|
|
|
CONFIG_MACH_NO_WESTBRIDGE=y
|
|
|
|
|
# CONFIG_ATH6K_LEGACY is not set
|
|
|
|
|
# CONFIG_USB_ENESTORAGE is not set
|
|
|
|
|
# CONFIG_BCM_WIMAX is not set
|
|
|
|
|
# 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
|
|
|
|
|
# CONFIG_CG2900 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_U8500_MMIO=y
|
|
|
|
|
CONFIG_U8500_CM=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_U8500_FLASH is not set
|
|
|
|
|
CONFIG_ARCH_HAS_PASR=y
|
|
|
|
|
# CONFIG_PASR is not set
|
|
|
|
|
CONFIG_CLKDEV_LOOKUP=y
|
|
|
|
|
CONFIG_TEE_SUPPORT=y
|
|
|
|
|
CONFIG_CLKSRC_MMIO=y
|
|
|
|
|
CONFIG_CLKSRC_DBX500_PRCMU=y
|
|
|
|
|
CONFIG_CLKSRC_DBX500_PRCMU_SCHED_CLOCK=y
|
|
|
|
|
CONFIG_MODEM=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_MODEM_U8500=y
|
|
|
|
|
CONFIG_U8500_SHRM=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_SHRM_ED_V1_VERSION is not set
|
|
|
|
|
CONFIG_SHRM_V1_UPDATES_VERSION=y
|
|
|
|
|
# CONFIG_U8500_SHRM_DEFAULT_NET is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_U8500_SHRM_SVNET=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_U8500_SHRM_LOOP_BACK is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_U8500_SHRM_MODEM_SILENT_RESET=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_U8500_SHRM_ENABLE_FEATURE_SIGNATURE_VERIFICATION=y
|
|
|
|
|
# CONFIG_MODEM_M6718 is not set
|
|
|
|
|
# CONFIG_U8500_KERNEL_CLIENT is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Samsung Kernel Modules
|
|
|
|
|
#
|
|
|
|
|
CONFIG_SAMSUNG_MODULES=m
|
|
|
|
|
CONFIG_J4FS=m
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SAMSUNG_PARAM=m
|
|
|
|
|
CONFIG_STARTUP_REASON=y
|
|
|
|
|
CONFIG_AB8500_STARTUP_REASON=y
|
|
|
|
|
CONFIG_NEW_SENSORS=y
|
|
|
|
|
CONFIG_SENSORS_ALPS=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_SENSORS_ALPS_CORE is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SENSORS_ACCEL=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_SENSORS_KXDM=y
|
|
|
|
|
CONFIG_SENSORS_HSCD=y
|
|
|
|
|
# CONFIG_SENSORS_GOLDEN is not set
|
|
|
|
|
# CONFIG_SENSORS_HSCDTD008A is not set
|
|
|
|
|
# CONFIG_SENSORS_BMA254 is not set
|
|
|
|
|
# CONFIG_BMA254_SMART_ALERT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PROXIMITY=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_PROXIMITY_CM3607 is not set
|
|
|
|
|
# CONFIG_PROXIMITY_GP2A is not set
|
|
|
|
|
# CONFIG_PROXIMITY_GP2A030 is not set
|
|
|
|
|
# CONFIG_LIGHT_PROX_GP2A is not set
|
|
|
|
|
# CONFIG_GP2A_MODE_B is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PROXIMITY_TMD2672=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_PROXIMITY_PX3215 is not set
|
|
|
|
|
# CONFIG_PROXIMITY_PX3315 is not set
|
|
|
|
|
# CONFIG_SENSORS_STK3X1X is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_ORIENTATION 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_YAS_ORIENTATION is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Motion Sensors Support
|
|
|
|
|
#
|
|
|
|
|
CONFIG_MPU_NONE=y
|
|
|
|
|
# CONFIG_MPU_SENSORS_MPU3050 is not set
|
|
|
|
|
# CONFIG_MPU_SENSORS_MPU6000 is not set
|
|
|
|
|
# CONFIG_SENSORS_MMC328X is not set
|
|
|
|
|
# CONFIG_ECOMPASS is not set
|
|
|
|
|
# CONFIG_MPU_SENSORS_TIMERIRQ is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SENSORS_CORE=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_COMPASS=y
|
|
|
|
|
# CONFIG_INPUT_YAS_MAGNETOMETER is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SAMSUNG_PHONE_SVNET=y
|
|
|
|
|
# CONFIG_PHONE_MODEMCTL is not set
|
|
|
|
|
# CONFIG_PHONE_ONEDRAM is not set
|
|
|
|
|
CONFIG_PHONE_SVNET=y
|
|
|
|
|
CONFIG_SVNET_WHITELIST=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_AUTHENTEC_VPNCLIENT_INTERCEPTOR is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# File systems
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXT2_FS=y
|
|
|
|
|
CONFIG_EXT2_FS_XATTR=y
|
|
|
|
|
CONFIG_EXT2_FS_POSIX_ACL=y
|
|
|
|
|
CONFIG_EXT2_FS_SECURITY=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_EXT2_FS_XIP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXT3_FS=y
|
|
|
|
|
# CONFIG_EXT3_DEFAULTS_TO_ORDERED 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_EXT3_FS_XATTR=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXT3_FS_POSIX_ACL=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_EXT3_FS_SECURITY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXT4_FS=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_EXT4_FS_XATTR=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EXT4_FS_POSIX_ACL=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_EXT4_FS_SECURITY is not set
|
|
|
|
|
# CONFIG_EXT4_DEBUG is not set
|
|
|
|
|
CONFIG_JBD=y
|
|
|
|
|
# CONFIG_JBD_DEBUG is not set
|
|
|
|
|
CONFIG_JBD2=y
|
|
|
|
|
# CONFIG_JBD2_DEBUG is not set
|
|
|
|
|
CONFIG_FS_MBCACHE=y
|
|
|
|
|
# CONFIG_REISERFS_FS is not set
|
|
|
|
|
# CONFIG_JFS_FS is not set
|
|
|
|
|
# CONFIG_XFS_FS is not set
|
|
|
|
|
# CONFIG_GFS2_FS is not set
|
|
|
|
|
# CONFIG_BTRFS_FS is not set
|
|
|
|
|
# CONFIG_NILFS2_FS is not set
|
|
|
|
|
CONFIG_FS_POSIX_ACL=y
|
|
|
|
|
CONFIG_FILE_LOCKING=y
|
|
|
|
|
CONFIG_FSNOTIFY=y
|
|
|
|
|
CONFIG_DNOTIFY=y
|
|
|
|
|
CONFIG_INOTIFY_USER=y
|
|
|
|
|
# CONFIG_FANOTIFY is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_QUOTA=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_QUOTA_NETLINK_INTERFACE is not set
|
|
|
|
|
CONFIG_PRINT_QUOTA_WARNING=y
|
|
|
|
|
# CONFIG_QUOTA_DEBUG is not set
|
|
|
|
|
CONFIG_QUOTA_TREE=y
|
|
|
|
|
# CONFIG_QFMT_V1 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_QFMT_V2=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_QUOTACTL=y
|
|
|
|
|
# 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 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_VFAT_FS=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_FAT_DEFAULT_CODEPAGE=437
|
|
|
|
|
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
|
|
|
|
|
# CONFIG_EXFAT_FS is not set
|
|
|
|
|
# CONFIG_NTFS_FS is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Pseudo filesystems
|
|
|
|
|
#
|
|
|
|
|
CONFIG_PROC_FS=y
|
|
|
|
|
CONFIG_PROC_VMCORE=y
|
|
|
|
|
CONFIG_PROC_SYSCTL=y
|
|
|
|
|
CONFIG_PROC_PAGE_MONITOR=y
|
|
|
|
|
CONFIG_SYSFS=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_TMPFS=y
|
|
|
|
|
CONFIG_TMPFS_POSIX_ACL=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_TMPFS_XATTR=y
|
|
|
|
|
# CONFIG_HUGETLB_PAGE is not set
|
|
|
|
|
# CONFIG_CONFIGFS_FS is not set
|
|
|
|
|
CONFIG_MISC_FILESYSTEMS=y
|
|
|
|
|
# CONFIG_ADFS_FS is not set
|
|
|
|
|
# CONFIG_AFFS_FS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_ECRYPT_FS=y
|
|
|
|
|
CONFIG_WTL_ENCRYPTION_FILTER=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_HFS_FS is not set
|
|
|
|
|
# CONFIG_HFSPLUS_FS is not set
|
|
|
|
|
# CONFIG_BEFS_FS is not set
|
|
|
|
|
# CONFIG_BFS_FS is not set
|
|
|
|
|
# CONFIG_EFS_FS is not set
|
|
|
|
|
# CONFIG_LOGFS is not set
|
|
|
|
|
# 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_NETWORK_FILESYSTEMS=y
|
|
|
|
|
# CONFIG_NFS_FS is not set
|
|
|
|
|
# CONFIG_NFSD is not set
|
|
|
|
|
# CONFIG_CEPH_FS is not set
|
|
|
|
|
# CONFIG_CIFS is not set
|
|
|
|
|
# CONFIG_NCP_FS is not set
|
|
|
|
|
# CONFIG_CODA_FS is not set
|
|
|
|
|
# CONFIG_AFS_FS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_9P_FS=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_9P_FS_POSIX_ACL is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Partition Types
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PARTITION_ADVANCED=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_ACORN_PARTITION is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_BLKDEV_PARTITION=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_OSF_PARTITION is not set
|
|
|
|
|
# CONFIG_AMIGA_PARTITION is not set
|
|
|
|
|
# CONFIG_ATARI_PARTITION is not set
|
|
|
|
|
# CONFIG_MAC_PARTITION is not set
|
|
|
|
|
CONFIG_MSDOS_PARTITION=y
|
|
|
|
|
# CONFIG_BSD_DISKLABEL is not set
|
|
|
|
|
# CONFIG_MINIX_SUBPARTITION is not set
|
|
|
|
|
# CONFIG_SOLARIS_X86_PARTITION is not set
|
|
|
|
|
# CONFIG_UNIXWARE_DISKLABEL is not set
|
|
|
|
|
# CONFIG_LDM_PARTITION is not set
|
|
|
|
|
# CONFIG_SGI_PARTITION is not set
|
|
|
|
|
# CONFIG_ULTRIX_PARTITION is not set
|
|
|
|
|
# CONFIG_SUN_PARTITION is not set
|
|
|
|
|
# CONFIG_KARMA_PARTITION is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_EFI_PARTITION=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_SYSV68_PARTITION is not set
|
|
|
|
|
# CONFIG_RPMB_PARTITION is not set
|
|
|
|
|
CONFIG_NLS=y
|
|
|
|
|
CONFIG_NLS_DEFAULT="iso8859-1"
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NLS_CODEPAGE_437=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NLS_ASCII=y
|
|
|
|
|
CONFIG_NLS_ISO8859_1=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_NLS_UTF8=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
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Kernel hacking
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_PRINTK_TIME=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_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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_UNUSED_SYMBOLS=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_DEBUG_FS=y
|
|
|
|
|
# CONFIG_HEADERS_CHECK is not set
|
|
|
|
|
# CONFIG_DEBUG_SECTION_MISMATCH is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DEBUG_KERNEL=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_DEBUG_SHIRQ is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_LOCKUP_DETECTOR=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_HARDLOCKUP_DETECTOR is not set
|
|
|
|
|
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
|
|
|
|
|
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
|
|
|
|
|
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
|
|
|
|
|
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DETECT_HUNG_TASK=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_DEFAULT_HUNG_TASK_TIMEOUT=120
|
|
|
|
|
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
|
|
|
|
|
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
|
|
|
|
|
CONFIG_SCHED_DEBUG=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SCHEDSTATS=y
|
|
|
|
|
CONFIG_TIMER_STATS=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_DEBUG_OBJECTS is not set
|
|
|
|
|
# CONFIG_DEBUG_SLAB is not set
|
|
|
|
|
# CONFIG_DEBUG_KMEMLEAK is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_DEBUG_PREEMPT 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_DEBUG_RT_MUTEXES is not set
|
|
|
|
|
# CONFIG_RT_MUTEX_TESTER is not set
|
|
|
|
|
# CONFIG_DEBUG_SPINLOCK is not set
|
|
|
|
|
# CONFIG_DEBUG_MUTEXES is not set
|
|
|
|
|
# CONFIG_DEBUG_LOCK_ALLOC is not set
|
|
|
|
|
# CONFIG_PROVE_LOCKING is not set
|
|
|
|
|
# CONFIG_SPARSE_RCU_POINTER is not set
|
|
|
|
|
# CONFIG_LOCK_STAT is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DEBUG_SPINLOCK_SLEEP=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_DEBUG_LOCKING_API_SELFTESTS is not set
|
|
|
|
|
CONFIG_STACKTRACE=y
|
|
|
|
|
# CONFIG_DEBUG_STACK_USAGE is not set
|
|
|
|
|
# CONFIG_DEBUG_KOBJECT is not set
|
|
|
|
|
# CONFIG_DEBUG_HIGHMEM is not set
|
|
|
|
|
CONFIG_DEBUG_BUGVERBOSE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DEBUG_INFO=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_DEBUG_INFO_REDUCED is not set
|
|
|
|
|
# CONFIG_DEBUG_VM is not set
|
|
|
|
|
# CONFIG_DEBUG_WRITECOUNT is not set
|
|
|
|
|
# CONFIG_DEBUG_MEMORY_INIT is not set
|
|
|
|
|
# CONFIG_DEBUG_LIST is not set
|
|
|
|
|
# CONFIG_TEST_LIST_SORT is not set
|
|
|
|
|
# CONFIG_DEBUG_SG is not set
|
|
|
|
|
# CONFIG_DEBUG_NOTIFIERS is not set
|
|
|
|
|
# CONFIG_DEBUG_CREDENTIALS is not set
|
|
|
|
|
CONFIG_FRAME_POINTER=y
|
|
|
|
|
# CONFIG_BOOT_PRINTK_DELAY is not set
|
|
|
|
|
# CONFIG_RCU_TORTURE_TEST is not set
|
|
|
|
|
CONFIG_RCU_CPU_STALL_TIMEOUT=60
|
|
|
|
|
CONFIG_RCU_CPU_STALL_VERBOSE=y
|
|
|
|
|
# CONFIG_BACKTRACE_SELF_TEST is not set
|
|
|
|
|
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
|
|
|
|
|
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
|
|
|
|
|
# CONFIG_DEBUG_PER_CPU_MAPS is not set
|
|
|
|
|
# CONFIG_LKDTM is not set
|
|
|
|
|
# CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
|
|
|
|
|
# CONFIG_FAULT_INJECTION is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_SYSCTL_SYSCALL_CHECK=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_DEBUG_PAGEALLOC is not set
|
|
|
|
|
CONFIG_NOP_TRACER=y
|
|
|
|
|
CONFIG_HAVE_FUNCTION_TRACER=y
|
|
|
|
|
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
|
|
|
|
|
CONFIG_HAVE_DYNAMIC_FTRACE=y
|
|
|
|
|
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
|
|
|
|
|
CONFIG_HAVE_C_RECORDMCOUNT=y
|
|
|
|
|
CONFIG_RING_BUFFER=y
|
|
|
|
|
CONFIG_EVENT_TRACING=y
|
|
|
|
|
CONFIG_EVENT_POWER_TRACING_DEPRECATED=y
|
|
|
|
|
CONFIG_CONTEXT_SWITCH_TRACER=y
|
|
|
|
|
CONFIG_TRACING=y
|
|
|
|
|
CONFIG_GENERIC_TRACER=y
|
|
|
|
|
CONFIG_TRACING_SUPPORT=y
|
|
|
|
|
CONFIG_FTRACE=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_FUNCTION_TRACER=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_FUNCTION_GRAPH_TRACER=y
|
|
|
|
|
# CONFIG_IRQSOFF_TRACER is not set
|
|
|
|
|
# CONFIG_PREEMPT_TRACER is not set
|
|
|
|
|
# CONFIG_SCHED_TRACER is not set
|
|
|
|
|
CONFIG_BRANCH_PROFILE_NONE=y
|
|
|
|
|
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
|
|
|
|
|
# CONFIG_PROFILE_ALL_BRANCHES is not set
|
|
|
|
|
# CONFIG_STACK_TRACER is not set
|
|
|
|
|
# CONFIG_BLK_DEV_IO_TRACE is not set
|
|
|
|
|
CONFIG_DYNAMIC_FTRACE=y
|
|
|
|
|
# CONFIG_FUNCTION_PROFILER is not set
|
|
|
|
|
CONFIG_FTRACE_MCOUNT_RECORD=y
|
|
|
|
|
# CONFIG_FTRACE_STARTUP_TEST is not set
|
|
|
|
|
# CONFIG_RING_BUFFER_BENCHMARK is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DYNAMIC_DEBUG=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_DMA_API_DEBUG is not set
|
|
|
|
|
# CONFIG_ATOMIC64_SELFTEST is not set
|
|
|
|
|
# CONFIG_SAMPLES is not set
|
|
|
|
|
CONFIG_HAVE_ARCH_KGDB=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KGDB=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_KGDB_SERIAL_CONSOLE=y
|
|
|
|
|
# CONFIG_KGDB_TESTS is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KGDB_KDB=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_KDB_KEYBOARD is not set
|
|
|
|
|
# CONFIG_TEST_KSTRTOX is not set
|
|
|
|
|
# CONFIG_STRICT_DEVMEM is not set
|
|
|
|
|
CONFIG_ARM_UNWIND=y
|
|
|
|
|
CONFIG_OLD_MCOUNT=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_DEBUG_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_DEBUG_LL is not set
|
|
|
|
|
# CONFIG_OC_ETM is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Security options
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_KEYS=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_KEYS_DEBUG_PROC_KEYS is not set
|
|
|
|
|
# CONFIG_SECURITY_DMESG_RESTRICT is not set
|
|
|
|
|
# CONFIG_SECURITY is not set
|
|
|
|
|
# CONFIG_SECURITYFS is not set
|
|
|
|
|
CONFIG_DEFAULT_SECURITY_DAC=y
|
|
|
|
|
CONFIG_DEFAULT_SECURITY=""
|
|
|
|
|
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_RNG2=y
|
|
|
|
|
CONFIG_CRYPTO_PCOMP2=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER2=y
|
|
|
|
|
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
|
|
|
|
|
CONFIG_CRYPTO_GF128MUL=y
|
|
|
|
|
# CONFIG_CRYPTO_NULL is not set
|
|
|
|
|
# CONFIG_CRYPTO_PCRYPT is not set
|
|
|
|
|
CONFIG_CRYPTO_WORKQUEUE=y
|
|
|
|
|
# CONFIG_CRYPTO_CRYPTD is not set
|
|
|
|
|
CONFIG_CRYPTO_AUTHENC=y
|
|
|
|
|
# CONFIG_CRYPTO_TEST is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 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
|
|
|
|
|
# CONFIG_CRYPTO_LRW is not set
|
|
|
|
|
# CONFIG_CRYPTO_PCBC is not set
|
|
|
|
|
CONFIG_CRYPTO_XTS=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Hash modes
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_HMAC=y
|
|
|
|
|
# CONFIG_CRYPTO_XCBC is not set
|
|
|
|
|
# CONFIG_CRYPTO_VMAC is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# 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 is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRYPTO_SHA256=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_SHA512 is not set
|
|
|
|
|
# CONFIG_CRYPTO_TGR192 is not set
|
|
|
|
|
# CONFIG_CRYPTO_WP512 is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Ciphers
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_AES=y
|
|
|
|
|
# CONFIG_CRYPTO_AES_ARM 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
|
|
|
|
|
# CONFIG_CRYPTO_SALSA20 is not set
|
|
|
|
|
# CONFIG_CRYPTO_SEED is not set
|
|
|
|
|
# CONFIG_CRYPTO_SERPENT is not set
|
|
|
|
|
# CONFIG_CRYPTO_TEA is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRYPTO_TWOFISH=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_TWOFISH_COMMON=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Compression
|
|
|
|
|
#
|
|
|
|
|
CONFIG_CRYPTO_DEFLATE=y
|
|
|
|
|
# CONFIG_CRYPTO_ZLIB is not set
|
|
|
|
|
# CONFIG_CRYPTO_LZO is not set
|
|
|
|
|
# CONFIG_CRYPTO_LZ4 is not set
|
|
|
|
|
# CONFIG_CRYPTO_LZ4HC is not set
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Random Number Generation
|
|
|
|
|
#
|
2020-06-12 17:59:18 +00:00
|
|
|
# CONFIG_CRYPTO_ANSI_CPRNG 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_USER_API_HASH is not set
|
|
|
|
|
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
|
|
|
|
|
CONFIG_CRYPTO_HW=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRYPTO_DEV_UX500=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_DEV_UX500_CRYP is not set
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRYPTO_DEV_UX500_HASH=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_DEV_UX500_DEBUG is not set
|
|
|
|
|
CONFIG_BINARY_PRINTF=y
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Library routines
|
|
|
|
|
#
|
|
|
|
|
CONFIG_BITREVERSE=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
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_CRC7=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_LIBCRC32C=y
|
|
|
|
|
CONFIG_ZLIB_INFLATE=y
|
|
|
|
|
CONFIG_ZLIB_DEFLATE=y
|
|
|
|
|
# CONFIG_XZ_DEC is not set
|
|
|
|
|
# CONFIG_XZ_DEC_BCJ is not set
|
|
|
|
|
CONFIG_DECOMPRESS_GZIP=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_CPU_RMAP=y
|
|
|
|
|
CONFIG_NLATTR=y
|
2020-06-12 17:59:18 +00:00
|
|
|
CONFIG_AVERAGE=y
|