- 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
If multiple options in a "choice" group are enabled, kconfig uses the
last (and warns about this). This means that the global default of
CONFIG_PREEMPT_VOLUNTARY=y has always overridden the setting of
CONFIG_PREEMPT_NONE=y here.
Since no-one seems to have complained, assume that the default is OK
and remove this.
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).
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).
BLK_DEV_FD has *never* been enabled on any of these architectures!
The old arm/footbridge configuration did enable it and this suggestion
seems to be have been thoughtlessly copied over to these other
architectures.
- Enable it by default
- Disable it for armel/marvell since signature verification is not enabled.
- Disable it for mips and mipsel so linux-signed can be uploaded without
waiting for them to build
- Disable it for all architectures not in the main archive, as linux-signed
won't support them (at least, not initially).
We don't need a variable to control signing of the image, because
we should do that for all flavours that have CONFIG_EFI_STUB=y.
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
The image-file path could potentially vary between flavours but
currently doesn't. buildcheck.py works either way.
svn path=/dists/trunk/linux/; revision=21251
No Alpha, PA-RISC or SH4 system supports PCI Express.
The older Marvell SoCs supported by iop32x and ixp4xx don't, but the
newer SoCs do. ARM Versatile doesn't support it and I'm pretty sure
QEMU won't let you add it, but will leave versatile alone for now.
Most supported MIPS platforms don't, but Octeon does.
I don't think PowerPC SPE systems have either PCI or PCI Express, but
I won't touch that configuration now.
svn path=/dists/trunk/linux/; revision=20579
Uwe Kleine-König
Ben Hutchings
Ben Hutchings
Bastian Blank
Aurelien Jarno
Maximilian Attems