diff options
author | Simon Arlott <simon@fire.lp0.eu> | 2007-05-02 08:08:26 -0400 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2007-05-02 08:08:26 -0400 |
commit | f6259deacfd55607ae57cff422d3bc7694ea14e7 (patch) | |
tree | d984d50afb2ee4cfa941008fd879fd64ca9629a0 /drivers/crypto/Kconfig | |
parent | e196d6259141eda47aeafd88514aae652bfbfc7f (diff) |
[CRYPTO] padlock: Remove pointless padlock module
When this is compiled in it is run too early to do anything useful:
[ 6.052000] padlock: No VIA PadLock drivers have been loaded.
[ 6.052000] padlock: Using VIA PadLock ACE for AES algorithm.
[ 6.052000] padlock: Using VIA PadLock ACE for SHA1/SHA256 algorithms.
When it's a module it isn't doing anything special, the same functionality
can be provided in userspace by "probeall padlock padlock-aes padlock-sha"
in modules.conf if it is required.
Signed-off-by: Simon Arlott <simon@fire.lp0.eu>
Cc: Michal Ludvig <michal@logix.cz>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/Kconfig')
-rw-r--r-- | drivers/crypto/Kconfig | 16 |
1 files changed, 3 insertions, 13 deletions
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig index ff8c4beaace4..f21fe66c9eef 100644 --- a/drivers/crypto/Kconfig +++ b/drivers/crypto/Kconfig | |||
@@ -1,10 +1,10 @@ | |||
1 | menu "Hardware crypto devices" | 1 | menu "Hardware crypto devices" |
2 | 2 | ||
3 | config CRYPTO_DEV_PADLOCK | 3 | config CRYPTO_DEV_PADLOCK |
4 | tristate "Support for VIA PadLock ACE" | 4 | bool "Support for VIA PadLock ACE" |
5 | depends on X86_32 | 5 | depends on X86_32 |
6 | select CRYPTO_ALGAPI | 6 | select CRYPTO_ALGAPI |
7 | default m | 7 | default y |
8 | help | 8 | help |
9 | Some VIA processors come with an integrated crypto engine | 9 | Some VIA processors come with an integrated crypto engine |
10 | (so called VIA PadLock ACE, Advanced Cryptography Engine) | 10 | (so called VIA PadLock ACE, Advanced Cryptography Engine) |
@@ -14,16 +14,6 @@ config CRYPTO_DEV_PADLOCK | |||
14 | The instructions are used only when the CPU supports them. | 14 | The instructions are used only when the CPU supports them. |
15 | Otherwise software encryption is used. | 15 | Otherwise software encryption is used. |
16 | 16 | ||
17 | Selecting M for this option will compile a helper module | ||
18 | padlock.ko that should autoload all below configured | ||
19 | algorithms. Don't worry if your hardware does not support | ||
20 | some or all of them. In such case padlock.ko will | ||
21 | simply write a single line into the kernel log informing | ||
22 | about its failure but everything will keep working fine. | ||
23 | |||
24 | If you are unsure, say M. The compiled module will be | ||
25 | called padlock.ko | ||
26 | |||
27 | config CRYPTO_DEV_PADLOCK_AES | 17 | config CRYPTO_DEV_PADLOCK_AES |
28 | tristate "PadLock driver for AES algorithm" | 18 | tristate "PadLock driver for AES algorithm" |
29 | depends on CRYPTO_DEV_PADLOCK | 19 | depends on CRYPTO_DEV_PADLOCK |
@@ -55,7 +45,7 @@ source "arch/s390/crypto/Kconfig" | |||
55 | 45 | ||
56 | config CRYPTO_DEV_GEODE | 46 | config CRYPTO_DEV_GEODE |
57 | tristate "Support for the Geode LX AES engine" | 47 | tristate "Support for the Geode LX AES engine" |
58 | depends on CRYPTO && X86_32 && PCI | 48 | depends on X86_32 && PCI |
59 | select CRYPTO_ALGAPI | 49 | select CRYPTO_ALGAPI |
60 | select CRYPTO_BLKCIPHER | 50 | select CRYPTO_BLKCIPHER |
61 | default m | 51 | default m |