- 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).
- [alpha] fbdev: Re-enable FRAMEBUFFER_CONSOLE as built-in
- [armel] fbdev: Explicitly disable FRAMEBUFFER_CONSOLE, as it can no longer
be a module
- [arm64] Re-enable MMC_QCOM_DML
- Change RC_CORE back to being a module
- power/supply: Enable BATTERY_BQ27XXX and BATTERY_BQ27XXX_HDQ as modules,
replacing W1_SLAVE_BQ27000
Clean up with kconfigeditor2 and delete obsolete symbols.
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).
- Various ancient SCSI drivers were removed; delete config for them
- r8723au was replaced by rtl8xxxu; enable the latter instead and for
all architectures
- netfilter config symbols were renamed; enable the new ones
- Various other config symbols are obsolete; delete them
- Various other config symbols moved to different Kconfig files
- 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
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
Apparently no m68k platform has configurable HZ, cpufreq or system
power management support. The corresponding Kconfig files are not
included from arch/m68k/Kconfig, and there is no point in setting
their symbols.
svn path=/dists/trunk/linux/; revision=20605
Disable most platform drivers, SPI and I2C drivers at the top level.
Platform drivers should be selected by architecture and flavour
configurations, and generally are. SPI and I2C devices aren't easily
detectable and their drivers aren't auto-loaded, so again they should
usually be selected in specific configuration files and probed
according to board code or FDTs.
As exceptions, I2C hwmon devices may be probed by lm-sensors and many
media tuners include I2C devices which are probed with the help of the
higher-level device driver. I've tried to be conservative and also
left I2C iio, input, leds and misc devices alone for now.
Disable the regulator subsystem at the top level as only some
architectures will need it.
Disable MTD_NAND_PLATFORM, PDA_POWER and FB_S1D13XXX on x86, as these
don't appear likely to be used on any x86 system that could run our
generic kernel images.
svn path=/dists/trunk/linux/; revision=20556
From: Thorsten Glaser <tg@mirbsd.de>
- disable some functionality due to size constraints
- switch to using initrd
- drop all flavours; build a generic image that runs on
multiple subarchitectores (old Amiga, Atari, Macintosh tested;
old BVME6000, MVME147, MVME16x, new Apollo, Q40/Q60 untested)
- use gcc-4.8
- add patch to make Atari EtherNAT actually selectable
svn path=/dists/sid/linux/; revision=20413
Ben Hutchings
Uwe Kleine-König
John Paul Adrian Glaubitz
Ben Hutchings
Bastian Blank