This adds support for PREEMPT_RT by adding two new featureset: none and
rt. For now the rt featureset supports armmp only, support for lpae
might be added later. the none featureset supports both flavours armmp
and armmp-lpae.
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.
config.armmp is used by both flavours and there's unlikely to be a
reason to add any non-multiplatform flavour. Rename it so that it's
the per-architecture config.
config.lpae is then the only per-flavour config file for armmp-lpae,
so rename it to the default filename for that flavour.
With armmp now being the baseline flavour the (rather arbitrary) split between
config and config.armmp doesn't make much sense. Move the contents of config
into config.armmp.
Implemented (mostly) automatically with:
$ ../kconfigeditor2/process.py .
-> Results in no change
$ cat debian/config/armhf/config debian/config/armhf/config.armmp | sponge debian/config/armhf/config.armmp
$ rm debian/config/armhf/config
$ vi debian/config/armhf/defines
$ ../kconfigeditor2/process.py .
svn path=/dists/trunk/linux/; revision=22732
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
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