- 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
- Various ancient SCSI drivers were removed
- BT_HCIBTUART and INFINIBAND_CXGB3_DEBUG were removed
- OMAP_DM_TIMER is now an automatic symbol
- Marvell NAND driver was rewritten, so we enable MTD_NAND_MARVELL
instead of MTD_NAND_PXA3xx
- Various netfilter symbols are now boolean instead of tristate
- Drop patches already in 4.16
- Overwrite changes on master to debian/installer, which were also
applied on sid and then changed
- [x86] Fix up dell_smbios configuration; now it's a single driver
selected by DELL_SMBIOS, with DELL_SMBIOS_{SMM,WMI} being boolean
options
- Clean up configuration with kconfigeditor2
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
drivers/pci/pcie/Kconfig is only included for specific architectures.
These two correctly do not include it, so don't bother to override
it or claim that any configuration change was made.
svn path=/dists/trunk/linux/; revision=20603
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
This driver doesn't bind to any device IDs, and instead has a comment
saying that the serial_cs and hci_uart drivers should be used instead.
So there's not much point in building it.
svn path=/dists/trunk/linux/; revision=20559
Ben Hutchings
Uwe Kleine-König
Ben Hutchings
Helge Deller
Maximilian Attems
Ian Campbell
Bastian Blank