This matches the behaviour of previous boardfile based kirkwood kernels.
Otherwise the kernel silently crashes during boot.
svn path=/dists/trunk/linux/; revision=22191
I'm assuming orion5x also has a small initrd partition, so using
anything weaker than gzip is unlikely to work.
We have space to spare on kirkwood now, so there's no need to disable
RD_LZ4 though I doubt it's particularly useful.
svn path=/dists/trunk/linux/; revision=22188
Image doesn't fit, old hardware, no one cares.
Suggested-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: maximilian attems <maks@debian.org>
svn path=/dists/trunk/linux/; revision=21875
These seem to have been impossible to enable before 3.16. We need
to keep them disabled to avoid blowing up the kernel image size.
svn path=/dists/trunk/linux/; revision=21718
Replace 'powerpc/powernv: Add calls to support little endian host'
with the version committed upstream.
Drop the ABI-preserving changes.
svn path=/dists/trunk/linux/; revision=21452
Instead of overriding the global default in kernelarch-arm disable virtio on
those armel flavours which do not want it (which is all but vexpress). This
allows the armmp flavours to pickup the global default.
No change to any of the eventual .config files.
svn path=/dists/sid/linux/; revision=21412
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
These were disabled for armel in 3.2.1-1 due to size concerns, but
the armel config (now in kernelarch-arm) is shared by armhf. Move
the overrides into a new armel-specific config.
svn path=/dists/trunk/linux/; revision=21231
It is inconsistent and potentially surprising that armhf uses
armel/config as well as armhf/config. Move the common config into a
new kernelarch-arm directory.
While we're at it, remove some redundant lines from both files.
svn path=/dists/trunk/linux/; revision=21221
These have been promoted out of staging so hopefully they're really
portable now.
Keep them disabled on armel/{ixp4xx,orion5x} due to size constraints.
svn path=/dists/trunk/linux/; revision=21127
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
Leave it enabled for armel/{iop32x,ixp4xx,kirkwood,orion5x} and m68k.
Drop the workaround patch for powerpc.
svn path=/dists/sid/linux/; revision=20732
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
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
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
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
USB_EHCI_ROOT_HUB_TT adds about 10 lines of code and is safe even if
not needed, so it's never worth turning off.
USB_EHCI_TT_NEWSCHED was 'new' in 2006 and is now the default, so
hardly anyone will be testing the 'old' code now.
svn path=/dists/trunk/linux/; revision=20546
Ian Campbell
Ben Hutchings
Maximilian Attems
Ian Campbell
Bastian Blank
Arnaud Patard
Nobuhiro Iwamatsu