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
These symbols were either (1) removed entirely or (2) merged or
renamed, and we already configure the other symbol.
svn path=/dists/trunk/linux/; revision=20604
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
All that config cleanup has brought them back under the size limit again
... for now ... with gcc-4.7. (I don't have a gcc-4.8 cross-compiler
to check with.)
svn path=/dists/trunk/linux/; revision=20588
Enable ARCH_OMAP3, ARCH_OMAP4 instead of the (now automatic) ARCH_OMAP2PLUS.
Enable MAILBOX, OMAP2PLUS_MBOX instead of the removed OMAP_MBOX_FWK.
svn path=/dists/trunk/linux/; revision=20580
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
efi-pstore is now a separate module (dependent on efivars). We still
want it to be auto-loaded to enable crash dumps on EFI systems, so add
another module alias.
While we're at it, explicitly set EFI_VARS_PSTORE=m matching what the
actual configuration will be.
svn path=/dists/sid/linux/; revision=20577
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
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
I still don't think it should be using this function, but the build
failure on MIPS was fixed by:
commit d3ce88431892b703b04769566338a89eda6b0477
Author: Ralf Baechle <ralf@linux-mips.org>
Date: Fri Dec 28 15:34:40 2012 +0100
MIPS: Fix modpost error in modules attepting to use virt_addr_valid().
svn path=/dists/trunk/linux/; revision=20553