- Set CONFIG_NR_CPUS to max number of CPUs, (from) 8 --> (to) 32
- Adjust config_generation to fix build_configs.sh failure
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Found CONFIG_CRYPTO_AUTHENC=y after generation, had CONFIG_CRYPTO_AUTHENC=m in Source tree
Found CONFIG_CRYPTO_ESSIV=y after generation, had CONFIG_CRYPTO_ESSIV=m in Source tree
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Two Kconfig symbols were part of upstream v5.3-rc1 but didn't make it
into v5.3 (for reasons I couldn't be bothered to unearth): PREEMPT_LL
and SOUNDWIRE_BUS. Remove them from our configuration generation system
too.
Commit 3e636fe3a6 ("Remove patch for GCC VTA") forgot to clean up the
configs/ directory. Do so now.
Commit e21e52b608 ("Linux v5.3-13236-g97f9a3c4eee5") forgot to remove
CONFIG_LOCK_DOWN_KERNEL and CONFIG_LOCK_DOWN_KERNEL_FORCE from the
configs/ directory. Do so now.
Commit 5c0d4daff4 ("Remove crash driver") forgot to clean up the
configs/ directory. Do so now.
There are 22 Kconfig symbols referenced in the files used for
configuration generation and in the shipped .config files that were
dropped in upstream v5.4-rc1. The references to these symbols can be
safely removed.
These symbols are:
CONFIG_ARM_QCOM_CPUFREQ_KRYO
CONFIG_CRYPTO_AEGIS128L
CONFIG_CRYPTO_AEGIS128L_AESNI_SSE2
CONFIG_CRYPTO_AEGIS256
CONFIG_CRYPTO_AEGIS256_AESNI_SSE2
CONFIG_CRYPTO_AES_586
CONFIG_CRYPTO_AES_X86_64
CONFIG_CRYPTO_MORUS1280
CONFIG_CRYPTO_MORUS1280_AVX2
CONFIG_CRYPTO_MORUS1280_SSE2
CONFIG_CRYPTO_MORUS640
CONFIG_CRYPTO_MORUS640_SSE2
CONFIG_DRM_TINYDRM
CONFIG_HISI_KIRIN_DW_DSI
CONFIG_I2C_BCM2048
CONFIG_KEXEC_VERIFY_SIG
CONFIG_MFD_CROS_EC_CHARDEV
CONFIG_MTD_M25P80
CONFIG_SENSORS_ADS1015
CONFIG_SERIAL_8250_MOXA
CONFIG_SGI_IOC4
CONFIG_TINYDRM_MIPI_DBI
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
The driver is needed for testing purposes, enable it on the architectures
where EFI is supported. Also, disallow access to the registered device if
the kernel is locked down.
This is a first pass at getting the secureboot patches working with the
upstream lockdown patches that got merged. The final patch from our
lockdown set is the sysrq patch which also needs work. For the present
it is not applied.
Found CONFIG_REGMAP_I2C=m after generation, had CONFIG_REGMAP_I2C=y in Source tree
Found CONFIG_REGMAP_SPI=m after generation, had CONFIG_REGMAP_SPI=y in Source tree
Cannot make then built-in, something forces them to be modules.
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Found CONFIG_CRC7=y after generation, had CONFIG_CRC7=m in Source tree
Found CONFIG_CRC_ITU_T=y after generation, had CONFIG_CRC_ITU_T=m in Source tree
Found CONFIG_REGMAP_SPI=m after generation, had CONFIG_REGMAP_SPI=y in Source tree
Still trying to get CONFIG_REGMAP_SPI=y to match OpenEmbedded config.
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Found CONFIG_MMC_SPI=m after generation, had CONFIG_MMC_SPI=y in Source tree
Found CONFIG_REGMAP_SPI=m after generation, had CONFIG_REGMAP_SPI=y in Source tree
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Upstream renamed the setting to DEBUG_KMEMLEAK_MEM_POOL_SIZE in upstream
commit c5665868183f and changed the default to 16000 in upstream commit
b751c52bb587.
Error: Mismatches found in configuration files
Found CONFIG_SND_SOC_ES8328_SPI=is not set after generation, had CONFIG_SND_SOC_ES8328_SPI=n in Source tree
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Error: Mismatches found in configuration files
Found # CONFIG_SND_SOC_ES8328 is not set, after generation, had CONFIG_SND_SOC_ES8328 m in Source tree
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
We've been carrying a patch to make CPUMASK_OFFSTACK selectable
without debugging for a long time now. The comment said this was
going to be replaced with something else but that never seemed
to happen. We're carrying it to have a higher number of CPUs but
at this point, adjusting NR_CPUS doesn't really get us that much
benfit. Drop the patch and just use 8192 or NR_CPUS on x86.
Signed-off-by: Laura Abbott <labbott@redhat.com>
- SECCOMP v2 was posted for review (one failing kernel selftest)
- SiFive Ethernet driver is approved upstream and might land in 5.3
- SiFive CPUFreq support is WIP, but people reported it working
Signed-off-by: David Abdurachmanov <david.abdurachmanov@sifive.com>
Some of the ISDN stack was deleted in the 5.3 window as per Paul's cleanup
patch. The vast majority of the remainder was moved to staging so let's
disable it in Fedora as it's unlikely to be used, and if se we can feed this
back to upstream.
For reference the main details from upstream are in these commits:
8a7e8ff8ce8a : ISDN removal/move merge overview
6d97985072dc : isdn: move capi drivers to staging
9c3c0c204814 : isdn: remove isdn4linux
85993b8c9786 : isdn: remove hisax driver
The Kconfig symbol ASIX_PHY was renamed to AX88796B_PHY in v5.2-rc6, see
upstream commit a9520543b123 ("net: phy: rename Asix Electronics PHY
driver"). CONFIG_AX88796B_PHY is already used in the configuration generation
system, so we can safely remove CONFIG_ASIX_PHY from that system.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
