As part of an effort to foster better cross collaboration with
internal Red Hat kernels, align the configs layout to match
that kernel. This will allow Red Hat engineers to provide easier
guidance on how to set various config options.
In addition, the scripts that process the config options will migrate
to the configs/ directory too in later patches. Future config
workflows will stage all work in the configs/ area.
A simple diff between the kernels will easily expose which config
options are different. Reading the comments in the file provides
guidance to Fedora to determine if that kernel should make a
similar change or not.
Rename debugconfig -> configs/base-debug
Rename baseconfig -> configs/base-generic
Rename configs/base-generic/arm/arm64 -> configs/base-generic/arm/aarch64
No code changes made.
During the Kconfig factor, CONFIG_MAXSMP was set for all builds instead
of just debug builds. This bumps the NR_CPUs up to 8192 which is far
more than anyone actually needs for Fedora. Stop setting CONFIG_MAXSMP
on non-debug configs and adjust NR_CPUs back to what it was before.
- Enable AXP288 PMIC support on x86_64 for battery charging and monitoring
support on Bay and Cherry Trail tablets and laptops
- Enable various drivers for peripherals found on Bay and Cherry Trail tablets
- Add some small patches fixing suspend/resume touchscreen and accelerometer
issues on various Bay and Cherry Trail tablets
The kernel configuration generation currently checks to make sure
every option is defined with listnewconfig. It does not check that
each option is the same as listnewconfig. This can lead to odd
situations where the Fedora configuration does not match what's
actually present in the generated config. Add a script to check
for these kinds of changes.
Based on work done by Miguel Flores Silverio <floresmigu3l@gmail.com>
The existing method of managing configuration files gets unweildy.
Changing individual lines in text files gets difficult without
manual organization. Switch to a method of configuration generation
that's inspired from the method used inside Red Hat. Each configuration
option gets its own file which are then combined to form the
configuration files. This makes confirming what's actually enabled much
easier.
