Not all x86 profiles have CONFIG_INPUT=y in their configuration. Just remove kmod-input-core for them.
Thank you Philip Prindeville for pointing out this problem.
SVN-Revision: 27988
Since the SetDepends macro does a:
DEPENDS:= ...
it can't be used after setting DEPENDS:= explicitly, or it will clobber the previous value.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27983
Instead of depending on new kernel versions, depend on not having one
of the older ones (or vice versa for modules removed in current kernels).
SVN-Revision: 27934
The old ieee1394 stack was removed in 2.6.37. The new firewire stack is
available for all kernel versions, but experimental for the older one, so
make both available where appropriate.
SVN-Revision: 27874
mbcache is only needed if xattr support is enabled, but this is only true
for ext4 on 2.6.37+, so just bundle it with ext4 when needed.
SVN-Revision: 27849
Fixes problem with TFM allocation in cryptosoft.c
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Hauke:
* remove ubsec_ssb package and take it from ocf-linux
* use patches from ocf-linux package
* refresh all patches
* readd some build fixes for OpenWrt.
* readd CRYPTO_MANAGER dependency
SVN-Revision: 27753
Also disable rtc-core for now since this changed to a bool, now directly
used in the kernel if enabled.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27186
The pata-cs5535/pata-cs5536 driver is actually fairly rare: it only gets used on embedded platforms. Therefore, we remove it from the generic x86 configuration.
Also, add definitions for other useful geode modules (high-res timers, MFGPT timers, etc).
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27037
* Add missing config symbols
* Update package/kernel for 2.6.39
CONFIG_BT_L2CAP=y and CONFIG_BT_SCO=y are set to build them into the bluetooth module.
Thank you Jonas Gorski for the patch
SVN-Revision: 27010
Since the oldest kernel in trunk is 2.6.30 the modules always use the
newer names, so we can just use the _generic prefix directly.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26903
There's only 2.6, so it doesn't make sense to mention modules that are
2.4 only or for modules that they are available only for 2.6.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26902
With no 2.4 support in trunk, we can safely remove any 2.4 definitions for
kmods and merge the 2.6 definitions into the generic ones.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26901
Since there's only 2.6 in trunk $(KMOD_SUFFIX) can be safely replaced with
ko for all mainline kernel modules.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26900
NOTE: The KCONFIG associated with each of these modules gets selected
whenever CRYPTO_MANAGER (kmod-crypto-manager) is selected so these
modules are already being built.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26812
For kernel versions newer then 2.6.31 the ext4 module can be used to mount
ext2/3 filesystems.
Building ext2/3 as modules on the other hand breaks using ext4 for mounting ext2
or ext3, which breaks booting from ext2/3 on machines where the ext4 module is
built into the kernel.
SVN-Revision: 26645
