- Various config symbols were removed, renamed or split
- HOTPLUG_PCI_SHPC is now boolean, so set it to built-in
- The stack protector config symbols were changed to two booleans
with different names
FRAMEBUFFER_CONSOLE is enabled in almost all configurations. So make
this the top level default, and disable it in the few exceptional
configurations (armel/marvell, mips*/octeon, s390x).
BLK_DEV_NVME_SCSI removed in 3f7f25a910ed8988b2a87c1ca2bfee6b4fb83ac7
CIFS_SMB2 removed in 2a38e12053b760a8f5e85030eb89512660077c15
FUJITSU_LAPTOP_DEBUG removed in eee77da1a7f02fd114288c4c379fed3d2ca4593d
MCE_AMD_INJ removed in bc8e80d56c1ecb35e65df392d7601d1427d14efe
MMC_BLOCK_BOUNCE removed in c3dccb74be28a345a2ebcc224e41b774529b8b8f
QCA7000_SPI renamed in b2f98200c73cf4bd7c26438490b5a137210e9c7d
RCU_KTHREAD_PRIO removed in f7a10a975036ef9ca957bfe12ab2d4b1a46cccd1
SCM_BLOCK_CLUSTER_WRITE removed in 94d26bfcf31244d24fddbe7ba5b0dd17f3c32b11
SPARSE_RCU_POINTER removed in 41a2901e7d220875752a8c870e0b53288a578c20
TRACE_ENUM_MAP_FILE renamed in 681bec0367c2606b6154060310a2ffa543175980
UCSI renamed in 8243edf44152c08c3efa1d551fc48605d674ad18
Currently we don't explicitly set CONFIG_FB for arm64, and the only
reason it's enabled as a module is that the DRM drivers (which are
built as modules) select it. We *do* explicitly set CONFIG_FB=y on
almost all other architectures and flavours.
Simplify this by setting CONFIG_FB=y at the top level and overriding
where needed (not arm64).
This enables STRICT_DEVMEM in the top-level config rather than per-
architecture, but the only additional kernel architectures that we
build and that support it are arm and arm64.
Since we no longer build any kernel packages for s390, there is no
reason to keep these files under kernelarch-s390, or to keep them
separate from each other.
s390x/config is shared with s390, so move it to kernelarch-s390/config
where it will be automatically used for both of them.
s390x/config.s390x is also shared, so move it to
kernelarch-s390/config-arch-64.
svn path=/dists/trunk/linux/; revision=21266
The filename of the kernel image to be installed, and the stem of the
installed name, varies between architectures, so we define several
different rules to install it for different sets of architectures.
However the basic fact that we need to install this file in /boot does
not.
We also duplicate this name information in gencontrol.py and in
debian/config/{armel,armhf,sh4}/defines (used by buildcheck.py).
To address this:
* Define [image]install-stem and [build]image-file for each architecture
* Copy these settings to make-flags in gencontrol.py
* Copy [image]install-stem to the image-stem template variable in
gencontrol.py
* Replace the per-architecture rules with a single rule using those
make-flags
The per-architecture rules for ARM and PowerPC also installed DTB
and DTS files, respectively. Include those commands in the single
rule with appropriate conditions around them.
svn path=/dists/trunk/linux/; revision=21253
1. Reset or remove values for config symbols that were only
configurable if EXPERT.
2. Set additional configurable symbols to their default values.
This should have no effect on the actual configuration, except for
sh4 where EXPERT is *always* set and so the settings in 1 were
still being followed.
svn path=/dists/trunk/linux/; revision=20825
Ben Hutchings
Uwe Kleine-König
Ben Hutchings
Bastian Blank
Aurelien Jarno