2007-07-16 06:39:36 +00:00
|
|
|
|
|
|
|
|
menuconfig CRYPTO_HW
|
|
|
|
|
bool "Hardware crypto devices"
|
|
|
|
|
default y
|
2007-08-18 10:56:21 +00:00
|
|
|
---help---
|
|
|
|
|
Say Y here to get to see options for hardware crypto devices and
|
|
|
|
|
processors. This option alone does not add any kernel code.
|
|
|
|
|
|
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
2007-07-16 06:39:36 +00:00
|
|
|
|
|
|
|
|
if CRYPTO_HW
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config CRYPTO_DEV_PADLOCK
|
2007-05-18 03:17:22 +00:00
|
|
|
tristate "Support for VIA PadLock ACE"
|
2007-12-01 20:16:29 +00:00
|
|
|
depends on X86_32 && !UML
|
2006-08-21 11:08:13 +00:00
|
|
|
select CRYPTO_ALGAPI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Some VIA processors come with an integrated crypto engine
|
|
|
|
|
(so called VIA PadLock ACE, Advanced Cryptography Engine)
|
2006-08-06 12:46:20 +00:00
|
|
|
that provides instructions for very fast cryptographic
|
|
|
|
|
operations with supported algorithms.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
The instructions are used only when the CPU supports them.
|
2006-08-06 12:50:30 +00:00
|
|
|
Otherwise software encryption is used.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config CRYPTO_DEV_PADLOCK_AES
|
2006-08-06 12:46:20 +00:00
|
|
|
tristate "PadLock driver for AES algorithm"
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on CRYPTO_DEV_PADLOCK
|
2006-08-21 11:38:42 +00:00
|
|
|
select CRYPTO_BLKCIPHER
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Use VIA PadLock for AES algorithm.
|
|
|
|
|
|
2006-08-06 12:46:20 +00:00
|
|
|
Available in VIA C3 and newer CPUs.
|
|
|
|
|
|
|
|
|
|
If unsure say M. The compiled module will be
|
|
|
|
|
called padlock-aes.ko
|
|
|
|
|
|
2006-07-12 02:29:38 +00:00
|
|
|
config CRYPTO_DEV_PADLOCK_SHA
|
|
|
|
|
tristate "PadLock driver for SHA1 and SHA256 algorithms"
|
|
|
|
|
depends on CRYPTO_DEV_PADLOCK
|
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
|
select CRYPTO_SHA256
|
|
|
|
|
help
|
|
|
|
|
Use VIA PadLock for SHA1/SHA256 algorithms.
|
|
|
|
|
|
|
|
|
|
Available in VIA C7 and newer processors.
|
|
|
|
|
|
|
|
|
|
If unsure say M. The compiled module will be
|
|
|
|
|
called padlock-sha.ko
|
|
|
|
|
|
2007-02-05 20:18:22 +00:00
|
|
|
source "arch/s390/crypto/Kconfig"
|
|
|
|
|
|
2006-10-04 08:48:57 +00:00
|
|
|
config CRYPTO_DEV_GEODE
|
|
|
|
|
tristate "Support for the Geode LX AES engine"
|
2007-05-02 12:08:26 +00:00
|
|
|
depends on X86_32 && PCI
|
2006-10-04 08:48:57 +00:00
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
|
select CRYPTO_BLKCIPHER
|
|
|
|
|
help
|
|
|
|
|
Say 'Y' here to use the AMD Geode LX processor on-board AES
|
2007-05-09 05:12:20 +00:00
|
|
|
engine for the CryptoAPI AES algorithm.
|
2006-10-04 08:48:57 +00:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called geode-aes.
|
|
|
|
|
|
2007-05-10 13:46:00 +00:00
|
|
|
config ZCRYPT
|
|
|
|
|
tristate "Support for PCI-attached cryptographic adapters"
|
|
|
|
|
depends on S390
|
|
|
|
|
select ZCRYPT_MONOLITHIC if ZCRYPT="y"
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to use a PCI-attached cryptographic
|
|
|
|
|
adapter like:
|
|
|
|
|
+ PCI Cryptographic Accelerator (PCICA)
|
|
|
|
|
+ PCI Cryptographic Coprocessor (PCICC)
|
|
|
|
|
+ PCI-X Cryptographic Coprocessor (PCIXCC)
|
|
|
|
|
+ Crypto Express2 Coprocessor (CEX2C)
|
|
|
|
|
+ Crypto Express2 Accelerator (CEX2A)
|
|
|
|
|
|
|
|
|
|
config ZCRYPT_MONOLITHIC
|
|
|
|
|
bool "Monolithic zcrypt module"
|
|
|
|
|
depends on ZCRYPT="m"
|
|
|
|
|
help
|
|
|
|
|
Select this option if you want to have a single module z90crypt.ko
|
|
|
|
|
that contains all parts of the crypto device driver (ap bus,
|
|
|
|
|
request router and all the card drivers).
|
|
|
|
|
|
2007-07-16 06:39:36 +00:00
|
|
|
endif # CRYPTO_HW
|
