| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
SVN-Revision: 28074
|
|
|
|
|
|
|
|
|
| |
Add kernel crypto user-space interface (af_alg). Includes interface for
hash algorithms (algif_hash) and skcipher algorithms (algif_skcipher).
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 28026
|
|
|
|
|
|
| |
Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
SVN-Revision: 28010
|
|
|
|
|
|
| |
Based on a patch by Layne Edwards <ledwards76@gmail.com>
SVN-Revision: 27998
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SetDepends/...)
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
|
|
|
|
|
|
|
|
|
|
| |
The module definitions depend on 001-depends.mk being the first included,
but make 3.82 does not sort the results of wildcards anymore, so do an
explicit sort of the includes.
Found by Philip Prindeville, thanks!
SVN-Revision: 27982
|
|
|
|
|
|
| |
mvswitch does not compile because of VLAN API changes.
SVN-Revision: 27936
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
closes #9773
SVN-Revision: 27924
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 27862
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 27757
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 27732
|
|
|
|
| |
SVN-Revision: 27591
|
|
|
|
| |
SVN-Revision: 27543
|
|
|
|
| |
SVN-Revision: 27458
|
|
|
|
| |
SVN-Revision: 27436
|
|
|
|
| |
SVN-Revision: 27402
|
|
|
|
| |
SVN-Revision: 27401
|
|
|
|
|
|
|
|
|
| |
that not only the MFGPT module but also the new GPIO driver both rely on the mfd_core functionality to operate correctly.
Signed-off-by: Alexandros C. Couloumbis <alex@ozo.com>
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27372
|
|
|
|
|
|
|
|
| |
MFD driver to be present for the BAR's to be mapped."
This reverts commit c485487b63d1c1de72a375f1278d8a98546ba3af.
SVN-Revision: 27370
|
|
|
|
|
|
|
|
| |
driver to be present for the BAR's to be mapped.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27369
|
|
|
|
|
|
| |
kmod-net-zd1201
SVN-Revision: 27274
|
|
|
|
|
|
| |
This module is also needed for e.g: kmod-bcm63xx-pcmcia
SVN-Revision: 27253
|
|
|
|
|
|
| |
SysKonnect Yukon support * Atheros L2 Fast Ethernet support * Atheros L1 Gigabit Ethernet support * Atheros L1C * Atheros L1E Patch by Lauri Võsandi<lauri.vosandi@gmail.com>
SVN-Revision: 27242
|
|
|
|
|
|
| |
kmod-bluetooth compile.
SVN-Revision: 27201
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 27150
|
|
|
|
| |
SVN-Revision: 27149
|
|
|
|
| |
SVN-Revision: 27126
|
|
|
|
| |
SVN-Revision: 27125
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
dependency to kmod-crypto-iv. chainiv.ko and eseqiv.ko from kmod-crypto-iv depend on crypto_blkcipher.ko from kmod-crypto-manager.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26984
|
|
|
|
| |
SVN-Revision: 26977
|
|
|
|
|
|
| |
Signed-off-by: Jan Willies <jan@willies.info>
SVN-Revision: 26920
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
stuff into its own file makes sense.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26868
|
|
|
|
| |
SVN-Revision: 26815
|
|
|
|
|
|
|
|
| |
unprovided kernel crypto modules that are useful for IPSEC. This is an alternative to breaking these modules out into kmod-crypto-wq (crypto_wq.ko), kmod-crypto-rng (rng.ko and krng.ko), and kmod-crypto-iv (eseqiv.ko and chainiv.ko).
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26814
|
|
|
|
|
|
|
|
| |
kmod-ipsec. Also remove the extraneous kmod-crypto-core dependency to eliminate recursion.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26813
|
|
|
|
|
|
|
|
|
|
|
|
| |
kmod-crypto-rng, and kmod-crypto-iv packages. These packages provide some missing kernel crypto modules which are required for IPSEC. The strongswan4, ipsec-tools, and possibly other IPSEC packages do not work properly without these modules.
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
|
|
|
|
| |
SVN-Revision: 26781
|
|
|
|
|
|
|
|
|
|
| |
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
|