Initial import

21 files changed, 3893 insertions, 0 deletions

diff --git a/target/linux/config/Config.in.block b/target/linux/config/Config.in.block
new file mode 100644
index 000000000..7bd303c60
--- /dev/null
+++ b/target/linux/config/Config.in.block
@@ -0,0 +1,246 @@
+menu "Block devices support"
+
+config ADK_KERNEL_MD
+	boolean
+	default n
+
+config ADK_KERNEL_SWAP
+	boolean
+	default n
+
+config ADK_KERNEL_LBD
+	boolean
+	default n
+
+config ADK_KERNEL_BLK_DEV_IO_TRACE
+	boolean
+	default n
+
+config ADK_KERNEL_LSF
+	boolean
+	default n
+
+config ADK_KERNEL_IOSCHED_AS
+	boolean
+	default n
+
+config ADK_KERNEL_IOSCHED_DEADLINE
+	boolean
+	default n
+
+config ADK_KERNEL_IOSCHED_CFQ
+	boolean
+	default n
+
+config ADK_KERNEL_SCSI
+	boolean
+	default n
+
+#config ADK_KERNEL_IDE
+#	boolean
+#	default n
+#
+#config ADK_KPACKAGE_KMOD_BLK_DEV_IDE
+#	prompt "kmod-ide.......................... IDE support"
+#	tristate
+#	select ADK_KERNEL_BLOCK
+#	select ADK_KERNEL_IDE
+#	default n
+#	help
+#	  If you say Y here, you will use the full-featured IDE driver to
+#	  control up to ten ATA/IDE interfaces, each being able to serve a
+#	  "master" and a "slave" device, for a total of up to twenty ATA/IDE
+#	  disk/cdrom/tape/floppy drives.
+#
+#	  Useful information about large (>540 MB) IDE disks, multiple
+#	  interfaces, what to do if ATA/IDE devices are not automatically
+#	  detected, sound card ATA/IDE ports, module support, and other
+#	  topics, is contained in <file:Documentation/ide.txt>. For detailed
+#	  information about hard drives, consult the Disk-HOWTO and the
+#	  Multi-Disk-HOWTO, available from
+#	  <http://www.tldp.org/docs.html#howto>.
+#
+#	  To fine-tune ATA/IDE drive/interface parameters for improved
+#	  performance, look for the hdparm package at
+#	  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
+#
+#	  To compile this driver as a module, choose M here and read
+#	  <file:Documentation/ide.txt>. The module will be called ide-mod.
+#	  Do not compile this driver as a module if your root file system (the
+#	  one containing the directory /) is located on an IDE device.
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_LOOP
+	prompt "kmod-loop......................... Loop mount support"
+	tristate
+	default n
+	help
+	  Saying Y here will allow you to use a regular file as a block
+	  device; you can then create a file system on that block device and
+	  mount it just as you would mount other block devices such as hard
+	  drive partitions, CD-ROM drives or floppy drives. The loop devices
+	  are block special device files with major number 7 and typically
+	  called /dev/loop0, /dev/loop1 etc.
+
+	  This is useful if you want to check an ISO 9660 file system before
+	  burning the CD, or if you want to use floppy images without first
+	  writing them to floppy. Furthermore, some Linux distributions avoid
+	  the need for a dedicated Linux partition by keeping their complete
+	  root file system inside a DOS FAT file using this loop device
+	  driver.
+
+	  To use the loop device, you need the losetup utility, found in the
+	  util-linux package, see
+	  <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
+
+	  The loop device driver can also be used to "hide" a file system in
+	  a disk partition, floppy, or regular file, either using encryption
+	  (scrambling the data) or steganography (hiding the data in the low
+	  bits of, say, a sound file). This is also safe if the file resides
+	  on a remote file server.
+
+	  There are several ways of encrypting disks. Some of these require
+	  kernel patches. The vanilla kernel offers the cryptoloop option
+	  and a Device Mapper target (which is superior, as it supports all
+	  file systems). If you want to use the cryptoloop, say Y to both
+	  LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
+	  or later) version of util-linux. Additionally, be aware that
+	  the cryptoloop is not safe for storing journaled filesystems.
+
+	  Note that this loop device has nothing to do with the loopback
+	  device used for network connections from the machine to itself.
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_NBD
+	prompt "kmod-nbd.......................... Network Block Device"
+	tristate
+	default n
+	help
+	  Saying Y here will allow your computer to be a client for network
+	  block devices, i.e. it will be able to use block devices exported by
+	  servers (mount file systems on them etc.). Communication between
+	  client and server works over TCP/IP networking, but to the client
+	  program this is hidden: it looks like a regular local file access to
+	  a block device special file such as /dev/nd0.
+
+	  Network block devices also allows you to run a block-device in
+	  userland (making server and client physically the same computer,
+	  communicating using the loopback network device).
+
+	  Read <file:Documentation/nbd.txt> for more information, especially
+	  about where to find the server code, which runs in user space and
+	  does not need special kernel support.
+
+	  Note that this has nothing to do with the network file systems NFS
+	  or Coda; you can say N here even if you intend to use NFS or Coda.
+
+config ADK_KPACKAGE_KMOD_SCSI
+	prompt "kmod-scsi......................... SCSI support"
+	select ADK_KERNEL_LBD
+	select ADK_KERNEL_LSF
+	select ADK_KERNEL_IOSCHED_AS
+	depends on !ADK_KERNEL_SCSI
+	tristate
+	help
+	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
+	  any other SCSI device under Linux, say Y and make sure that you know
+	  the name of your SCSI host adapter (the card inside your computer
+	  that "speaks" the SCSI protocol, also called SCSI controller),
+	  because you will be asked for it.
+
+	  You also need to say Y here if you have a device which speaks
+	  the SCSI protocol.  Examples of this include the parallel port
+	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
+	  Channel, FireWire storage and the IDE-SCSI emulation driver.
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_SD
+	prompt "kmod-scsi-disk.................... SCSI disk support"
+	depends !ADK_KERNEL_SCSI
+	depends ADK_KPACKAGE_KMOD_SCSI
+	tristate
+	help
+	  If you want to use SCSI hard disks, Fibre Channel disks,
+	  USB storage or the SCSI or parallel port version of
+	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
+	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
+	  CD-ROMs.
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_SR
+	prompt "kmod-scsi-cdrom................... SCSI CDROM support"
+	depends !ADK_KERNEL_SCSI
+	depends ADK_KPACKAGE_KMOD_SCSI
+	tristate
+	help
+	  If you want to use a SCSI or FireWire CD-ROM under Linux,
+	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
+	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
+	  Y or M to "ISO 9660 CD-ROM file system support" later.
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_MD
+	prompt "kmod-md........................... RAID support"
+	tristate
+	select ADK_KERNEL_MD
+	help
+
+config ADK_KPACKAGE_KMOD_MD_RAID0
+	prompt "kmod-md-raid0..................... RAID0 support"
+	tristate
+	depends ADK_KPACKAGE_KMOD_BLK_DEV_MD
+	help
+
+config ADK_KPACKAGE_KMOD_MD_RAID1
+	prompt "kmod-md-raid1..................... RAID1 support"
+	tristate
+	depends ADK_KPACKAGE_KMOD_BLK_DEV_MD
+	help
+
+config ADK_KPACKAGE_KMOD_MD_RAID456
+	prompt "kmod-md-raid456................... RAID456 support"
+	tristate
+	depends ADK_KPACKAGE_KMOD_BLK_DEV_MD
+	help
+
+config ADK_KPACKAGE_KMOD_BLK_DEV_DM
+	prompt "kmod-dm........................... Device Mapper support"
+	select ADK_KERNEL_MD
+	tristate
+	help
+	  Device-mapper is a low level volume manager.  It works by allowing
+	  people to specify mappings for ranges of logical sectors.  Various
+	  mapping types are available, in addition people may write their own
+	  modules containing custom mappings if they wish.
+
+	  Higher level volume managers such as LVM2 use this driver.
+
+config ADK_KPACKAGE_KMOD_DM_CRYPT
+	prompt "kmod-dm-crypt................... Crypt target support"
+	depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
+	select ADK_KERNEL_MD
+	select ADK_KERNEL_CRYPTO
+	select ADK_KPACKAGE_KMOD_CRYPTO_CBC
+	select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	tristate
+	help
+	  This device-mapper target allows you to create a device that
+	  transparently encrypts the data on it. You'll need to activate
+	  the ciphers you're going to use in the cryptoapi configuration.
+
+	  Information on how to use dm-crypt can be found on
+
+	  <http://www.saout.de/misc/dm-crypt/>
+
+config ADK_KPACKAGE_KMOD_DM_SNAPSHOT
+	prompt "kmod-dm-snapshot................ Snapshot target"
+	depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
+	tristate
+	help
+         Allow volume managers to take writable snapshots of a device.
+
+config ADK_KPACKAGE_KMOD_DM_MIRROR
+	prompt "kmod-dm-mirror.................. Mirror target"
+	depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
+	tristate
+	help
+         Allow volume managers to mirror logical volumes, also
+         needed for live data migration tools such as 'pvmove'.
+
+endmenu
diff --git a/target/linux/config/Config.in.bluetooth b/target/linux/config/Config.in.bluetooth
new file mode 100644
index 000000000..7d868ace5
--- /dev/null
+++ b/target/linux/config/Config.in.bluetooth
@@ -0,0 +1,120 @@
+menu "Bluetooth"
+
+config ADK_KPACKAGE_KMOD_BT
+	prompt "kmod-bluetooth.................... Bluetooth drivers and network stack"
+	tristate
+	default n
+	help
+	  Bluetooth is low-cost, low-power, short-range wireless technology.
+	  It was designed as a replacement for cables and other short-range
+	  technologies like IrDA.  Bluetooth operates in personal area range
+	  that typically extends up to 10 meters.  More information about
+	  Bluetooth can be found at <http://www.bluetooth.com/>.
+
+	  Linux Bluetooth subsystem consist of several layers:
+	     Bluetooth Core (HCI device and connection manager, scheduler)
+	     HCI Device drivers (Interface to the hardware)
+	     SCO Module (SCO audio links)
+	     L2CAP Module (Logical Link Control and Adaptation Protocol)
+	     RFCOMM Module (RFCOMM Protocol)  
+	     BNEP Module (Bluetooth Network Encapsulation Protocol)
+	     CMTP Module (CAPI Message Transport Protocol)
+	     HIDP Module (Human Interface Device Protocol)
+
+config ADK_KPACKAGE_KMOD_BT_L2CAP
+	prompt "kmod-bluetooth-l2cap.............. L2CAP protocol support"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  L2CAP (Logical Link Control and Adaptation Protocol) provides
+	  connection oriented and connection-less data transport.  L2CAP
+	  support is required for most Bluetooth applications.
+
+
+config ADK_KPACKAGE_KMOD_BT_SCO
+	prompt "kmod-bluetooth-sco................ SCO links support"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  SCO link provides voice transport over Bluetooth.  SCO support is
+	  required for voice applications like Headset and Audio.
+
+config ADK_KPACKAGE_KMOD_BT_RFCOMM
+	prompt "kmod-bluetooth-rfcomm............. RFCOMM protocol support"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	depends ADK_KPACKAGE_KMOD_BT_L2CAP
+	help
+	  RFCOMM provides connection oriented stream transport.  RFCOMM
+	  support is required for Dialup Networking, OBEX and other Bluetooth
+	  applications.
+
+config ADK_KPACKAGE_KMOD_BT_BNEP
+	prompt "kmod-bluetooth-bnep............... BNEP protocol support"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	depends ADK_KPACKAGE_KMOD_BT_L2CAP
+	help
+	  BNEP (Bluetooth Network Encapsulation Protocol) is Ethernet
+	  emulation layer on top of Bluetooth.  BNEP is required for
+	  Bluetooth PAN (Personal Area Network).
+
+config ADK_KPACKAGE_KMOD_BT_HIDP
+	prompt "kmod-bluetooth-hidp............... HIDP protocol support"
+	tristate
+	default n
+	select ADK_KERNEL_HID
+	depends ADK_KPACKAGE_KMOD_BT
+	depends ADK_KPACKAGE_KMOD_BT_L2CAP
+	help
+	  HIDP (Human Interface Device Protocol) is a transport layer
+	  for HID reports.  HIDP is required for the Bluetooth Human
+	  Interface Device Profile.
+
+config ADK_KPACKAGE_KMOD_BT_HCIBTUSB
+	prompt "kmod-bluetooth-hci-usb............ HCI USB driver"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  Bluetooth HCI USB driver.
+	  This driver is required if you want to use Bluetooth devices with
+	  USB interface.
+
+config ADK_KPACKAGE_KMOD_BT_HCIUART
+	prompt "kmod-bluetooth-hci-uart........... HCI UART driver"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  Bluetooth HCI UART driver.
+	  This driver is required if you want to use Bluetooth devices with
+	  serial port interface. You will also need this driver if you have 
+	  UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card 
+	  adapter and BrainBoxes Bluetooth PC Card.
+
+config ADK_KPACKAGE_KMOD_BT_HCIBCM203X
+	prompt "kmod-bluetooth-hci-bcm203x........ HCI BCM203x USB driver"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  Bluetooth HCI BCM203x USB driver.
+	  This driver provides the firmware loading mechanism for the Broadcom
+	  Blutonium based devices.
+
+config ADK_KPACKAGE_KMOD_BT_HCIBPA10X
+	prompt "kmod-bluetooth-hci-bpa10x......... HCI BPA10x USB driver"
+	tristate
+	default n
+	depends ADK_KPACKAGE_KMOD_BT
+	help
+	  Bluetooth HCI BPA10x USB driver.
+	  This driver provides support for the Digianswer BPA 100/105 Bluetooth
+	  sniffer devices.
+
+endmenu
diff --git a/target/linux/config/Config.in.crypto b/target/linux/config/Config.in.crypto
new file mode 100644
index 000000000..a2d88655d
--- /dev/null
+++ b/target/linux/config/Config.in.crypto
@@ -0,0 +1,536 @@
+menu "Crypto kernel modules"
+config ADK_KERNEL_CRYPTO
+	boolean
+	default n
+
+config ADK_KERNEL_CRYPTO_HW
+	boolean
+	default n
+
+config ADK_KERNEL_OCF_FIPS
+	boolean
+	default n
+
+config ADK_KERNEL_OCF_CRYPTODEV
+	boolean
+	default n
+
+config ADK_KERNEL_OCF_OCF
+	boolean
+	default n
+	select ADK_KERNEL_CRYPTO
+	select ADK_KERNEL_OCF_FIPS
+	select ADK_KERNEL_OCF_CRYPTODEV
+
+comment "Hardware cryptography"
+
+menu "Hardware crypto devices"
+
+config ADK_KPACKAGE_KMOD_CRYPTO_DEV_GEODE
+	prompt "Support for the Geode LX/GX AES engine"
+	tristate
+	select ADK_KERNEL_CRYPTO_HW
+	select ADK_KERNEL_CRYPTO
+	depends on ADK_LINUX_X86_ALIX1C
+	help
+	  Say 'Y' here to use the AMD Geode LX processor on-board AES
+	  engine for the CryptoAPI AES algorithm.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_DEV_HIFN_795X
+	prompt "Driver HIFN 795x crypto accelerator chips"
+	tristate
+	select ADK_KERNEL_CRYPTO_HW
+	select ADK_KERNEL_CRYPTO
+	select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_DES
+	help
+	  This option allows you to have support for HIFN 795x crypto adapters.
+
+endmenu
+
+menu "OpenBSD Cryptographic framework"
+depends on !ADK_LINUX_CRIS_FOXBOARD
+
+config ADK_KPACKAGE_KMOD_OCF_HIFN
+	prompt "kmod-cryptodev-hifn................ hifn engine"
+	tristate
+	default n
+	select ADK_KERNEL_OCF_OCF
+	help
+	  Engine for cryptodev that uses Hifn based accelerators
+	  such as the 7951, 7955, 7956, 7751, 7811.
+
+config ADK_KPACKAGE_KMOD_OCF_SAFE
+	prompt "kmod-cryptodev-safe................ safenet engine"
+	tristate
+	default n
+	select ADK_KERNEL_OCF_OCF
+	help
+	  Engine for cryptodev that uses a number of the safenet Excel
+	  crypto accelerators. Currently for the 1141 and 1741.
+
+config ADK_KPACKAGE_KMOD_OCF_IXP4XX
+	prompt "kmod-cryptodev-ixp4xx.............. IXP4xx engine"
+	tristate
+	default n
+	select ADK_KERNEL_OCF_OCF
+	depends on ADK_arm
+	help
+	  Engine for cryptodev that uses XScale IXP4xx.
+	  Requires the Intel Access library.
+
+config ADK_KPACKAGE_KMOD_OCF_TALITOS
+	prompt "kmod-cryptodev-talitos............. talitos engine"
+	tristate
+	default n
+	select ADK_KERNEL_OCF_OCF
+	depends on ADK_powerpc || ADK_m68k || ADK_ppc
+	help
+	  Engine for cryptodev that uses Freescale's security engine (SEC/talitos).
+
+endmenu
+
+comment "Software cryptography"
+
+menu "Crypto core / Block and Hash modes"
+config ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	prompt "kmod-crypto-algapi.................. Crypto algorithm API"
+	tristate
+	default n
+	select ADK_KERNEL_CRYPTO
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_AEAD
+	prompt "kmod-crypto-aead.................... Crypto algorithm AEAD"
+	tristate
+	default n
+	select ADK_KERNEL_CRYPTO
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_MANAGER
+	prompt "kmod-crypto-manager.................. Crypto algorithm manager"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_AEAD
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	prompt "kmod-crypto-hash..................... Crypto hash support"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	prompt "kmod-crypto-blkcipher................ Crypto block cipher support"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_CBC
+	prompt "kmod-crypto-cbc...................... CBC support"
+	tristate
+	select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	select ADK_KPACKAGE_KMOD_CRYPTO_MANAGER
+	default n
+	help
+	  CBC: Cipher Block Chaining mode
+	  This block cipher algorithm is required for IPSec.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_ECB
+	prompt "kmod-crypto-ecb...................... ECB support"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	select ADK_KPACKAGE_KMOD_CRYPTO_MANAGER
+	help
+	  ECB: Electronic CodeBook mode
+	  This is the simplest block cipher algorithm.  It simply encrypts
+	  the input block by block.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_HMAC
+	prompt "kmod-crypto-hmac..................... HMAC support"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	select ADK_KPACKAGE_KMOD_CRYPTO_MANAGER
+	help
+	  HMAC: Keyed-Hashing for Message Authentication (RFC2104).
+	  This is required for IPSec.
+
+endmenu
+
+menu "Digest algorithms"
+
+config ADK_KPACKAGE_KMOD_CRYPTO_MD4
+	prompt "kmod-crypto-md4...................... MD4 digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  MD4 message digest algorithm (RFC1320).
+
+config ADK_KPACKAGE_KMOD_CRYPTO_MD5
+	prompt "kmod-crypto-md5...................... MD5 digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  MD5 message digest algorithm (RFC1321).
+
+config ADK_KPACKAGE_KMOD_CRYPTO_SHA1
+	prompt "kmod-crypto-sha1..................... SHA1 digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
+
+config ADK_KPACKAGE_KMOD_CRYPTO_SHA256
+	prompt "kmod-crypto-sha256................... SHA256 digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  SHA256 secure hash standard (DFIPS 180-2).
+	  
+	  This version of SHA implements a 256 bit hash with 128 bits of
+	  security against collision attacks.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_SHA512
+	prompt "kmod-crypto-sha512................... SHA512 digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  SHA512 secure hash standard (DFIPS 180-2).
+	  
+	  This version of SHA implements a 512 bit hash with 256 bits of
+	  security against collision attacks.
+
+	  This code also includes SHA-384, a 384 bit hash with 192 bits
+	  of security against collision attacks.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_WP512
+	prompt "kmod-crypto-whirlpool................ Whirlpool digest algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  Whirlpool hash algorithm 512, 384 and 256-bit hashes
+
+	  Whirlpool-512 is part of the NESSIE cryptographic primitives.
+	  Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
+
+	  See also:
+	  <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_TGR192
+	prompt "kmod-crypto-tiger.................... Tiger digest algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	help
+	  Tiger hash algorithm 192, 160 and 128-bit hashes
+
+	  Tiger is a hash function optimized for 64-bit processors while
+	  still having decent performance on 32-bit processors.
+	  Tiger was developed by Ross Anderson and Eli Biham.
+
+	  See also:
+	  <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
+
+endmenu
+
+menu "Cipher algoritms"
+
+config ADK_KPACKAGE_KMOD_CRYPTO_AES
+	prompt "kmod-crypto-aes...................... AES cipher algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  AES cipher algorithms (FIPS-197). AES uses the Rijndael 
+	  algorithm.
+
+	  Rijndael appears to be consistently a very good performer in
+	  both hardware and software across a wide range of computing 
+	  environments regardless of its use in feedback or non-feedback 
+	  modes. Its key setup time is excellent, and its key agility is 
+	  good. Rijndael's very low memory requirements make it very well 
+	  suited for restricted-space environments, in which it also 
+	  demonstrates excellent performance. Rijndael's operations are 
+	  among the easiest to defend against power and timing attacks.	
+
+	  The AES specifies three key sizes: 128, 192 and 256 bits	  
+
+	  See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_AES_586
+	prompt "kmod-crypto-aes-i586................. AES cipher algorithms (i586)"
+	tristate
+	default n
+	depends on ADK_x86
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  AES cipher algorithms (FIPS-197). AES uses the Rijndael 
+	  algorithm.
+
+	  Rijndael appears to be consistently a very good performer in
+	  both hardware and software across a wide range of computing 
+	  environments regardless of its use in feedback or non-feedback 
+	  modes. Its key setup time is excellent, and its key agility is 
+	  good. Rijndael's very low memory requirements make it very well 
+	  suited for restricted-space environments, in which it also 
+	  demonstrates excellent performance. Rijndael's operations are 
+	  among the easiest to defend against power and timing attacks.	
+
+	  The AES specifies three key sizes: 128, 192 and 256 bits	  
+
+	  See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_ANUBIS
+	prompt "kmod-crypto-anubis................... Anubis cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Anubis cipher algorithm.
+
+	  Anubis is a variable key length cipher which can use keys from 
+	  128 bits to 320 bits in length.  It was evaluated as a entrant
+	  in the NESSIE competition.
+	  
+	  See also:
+	  <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
+	  <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_ARC4
+	prompt "kmod-crypto-arc4..................... ARC4 cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  ARC4 cipher algorithm.
+
+	  ARC4 is a stream cipher using keys ranging from 8 bits to 2048
+	  bits in length.  This algorithm is required for driver-based 
+	  WEP, but it should not be for other purposes because of the
+	  weakness of the algorithm.
+
+
+config ADK_KPACKAGE_KMOD_CRYPTO_BLOWFISH
+	prompt "kmod-crypto-blowfish................. Blowfish cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Blowfish cipher algorithm, by Bruce Schneier.
+	  
+	  This is a variable key length cipher which can use keys from 32
+	  bits to 448 bits in length.  It's fast, simple and specifically
+	  designed for use on "large microprocessors".
+	  
+	  See also:
+	  <http://www.schneier.com/blowfish.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_CAMELLIA
+	prompt "kmod-crypto-camellia................. Camellia cipher algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Camellia cipher algorithms module.
+
+	  Camellia is a symmetric key block cipher developed jointly
+	  at NTT and Mitsubishi Electric Corporation.
+
+	  The Camellia specifies three key sizes: 128, 192 and 256 bits.
+
+	  See also:
+	  <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_CAST5
+	prompt "kmod-crypto-cast5.................... CAST5 (CAST-128) cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  The CAST5 encryption algorithm (synonymous with CAST-128) is
+	  described in RFC2144.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_CAST6
+	prompt "kmod-crypto-cast6.................... CAST6 (CATS-256) cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  The CAST6 encryption algorithm (synonymous with CAST-256) is
+	  described in RFC2612.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_DES
+	prompt "kmod-crypto-des...................... DES and Triple DES EDE cipher algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
+
+config ADK_KPACKAGE_KMOD_CRYPTO_FCRYPT
+	prompt "kmod-crypto-fcrypt................... FCrypt cipher algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  FCrypt algorithm used by RxRPC.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_KHAZAD
+	prompt "kmod-crypto-khazad................... Khazad cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Khazad cipher algorithm.
+
+	  Khazad was a finalist in the initial NESSIE competition.  It is
+	  an algorithm optimized for 64-bit processors with good performance
+	  on 32-bit processors.  Khazad uses an 128 bit key size.
+
+	  See also:
+	  <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_SERPENT
+	prompt "kmod-crypto-serpent.................. Serpent cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Serpent cipher algorithm, by Anderson, Biham & Knudsen.
+
+	  Keys are allowed to be from 0 to 256 bits in length, in steps
+	  of 8 bits.  Also includes the 'Tnepres' algorithm, a reversed
+	  variant of Serpent for compatibility with old kerneli code.
+
+	  See also:
+	  <http://www.cl.cam.ac.uk/~rja14/serpent.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_TEA
+	prompt "kmod-crypto-tea...................... TEA, XTEA and XETA cipher algorithms"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  TEA cipher algorithm.
+
+	  Tiny Encryption Algorithm is a simple cipher that uses
+	  many rounds for security.  It is very fast and uses
+	  little memory.
+
+	  Xtendend Tiny Encryption Algorithm is a modification to
+	  the TEA algorithm to address a potential key weakness
+	  in the TEA algorithm.
+
+	  Xtendend Encryption Tiny Algorithm is a mis-implementation 
+	  of the XTEA algorithm for compatibility purposes.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_TWOFISH
+	prompt "kmod-crypto-twofish.................. Twofish cipher algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Twofish cipher algorithm.
+	  
+	  Twofish was submitted as an AES (Advanced Encryption Standard)
+	  candidate cipher by researchers at CounterPane Systems.  It is a
+	  16 round block cipher supporting key sizes of 128, 192, and 256
+	  bits.
+	  
+	  See also:
+	  <http://www.schneier.com/twofish.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_TWOFISH_586
+	prompt "kmod-crypto-twofish-586.............. Twofish cipher algorithm (i586)"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	depends on ADK_x86
+	help
+	  Twofish cipher algorithm.
+	  
+	  Twofish was submitted as an AES (Advanced Encryption Standard)
+	  candidate cipher by researchers at CounterPane Systems.  It is a
+	  16 round block cipher supporting key sizes of 128, 192, and 256
+	  bits.
+	  
+	  See also:
+	  <http://www.schneier.com/twofish.html>
+
+config ADK_KPACKAGE_KMOD_CRYPTO_NULL
+	prompt "kmod-crypto-null..................... Null algorithms"
+	tristate
+	select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	default n
+	help
+	  These are 'Null' algorithms, used by IPsec, which do nothing.
+
+endmenu
+
+menu "Compression"
+
+config ADK_KPACKAGE_KMOD_CRYPTO_DEFLATE
+	prompt "kmod-crypto-deflate.................. Deflate compression algorithm"
+	tristate
+	default n
+	select ADK_KERNEL_CRYPTO
+	help
+	  This is the Deflate algorithm (RFC1951), specified for use in
+	  IPSec with the IPCOMP protocol (RFC3173, RFC2394).
+	  
+	  You will most probably want this if using IPSec.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_LZO
+	prompt "kmod-crypto-lzo...................... LZO compression algorithm"
+	tristate
+	default n
+	select ADK_KERNEL_CRYPTO
+	help
+
+config ADK_KPACKAGE_KMOD_CRYPTO_MICHAEL_MIC
+	prompt "kmod-crypto-michael-mic.............. Michael MIC keyed digest algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_ALGAPI
+	help
+	  Michael MIC is used for message integrity protection in TKIP
+	  (IEEE 802.11i). This algorithm is required for TKIP, but it
+	  should not be used for other purposes because of the weakness
+	  of the algorithm.
+
+config ADK_KPACKAGE_KMOD_CRYPTO_CRC32C
+	prompt "kmod-crypto-crc32c................... CRC32c CRC algorithm"
+	tristate
+	default n
+	select ADK_KPACKAGE_KMOD_CRYPTO_HASH
+	select ADK_KPACKAGE_KMOD_LIBCRC32C
+	help
+	  Castagnoli, et al Cyclic Redundancy-Check Algorithm.  Used
+	  by iSCSI for header and data digests and by others.
+	  See Castagnoli93.  This implementation uses lib/libcrc32c.
+          Module will be crc32c.
+