diff options
Diffstat (limited to 'target/linux/config')
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. + +endmenu + +endmenu diff --git a/target/linux/config/Config.in.debug b/target/linux/config/Config.in.debug new file mode 100644 index 000000000..9c876e205 --- /dev/null +++ b/target/linux/config/Config.in.debug @@ -0,0 +1,53 @@ +menu "Kernel debugging" + +config ADK_KERNEL_DEBUG_KERNEL + boolean + default n + +config ADK_KERNEL_DEBUG_INFO + boolean + default n + +config ADK_KERNEL_KGDB + boolean + default n + +config ADK_KERNEL_KGDB_SERIAL_CONSOLE + boolean + default n + +config ADK_KERNEL_FRAME_POINTER + boolean + default n + +config ADK_KERNEL_MAGIC_SYSRQ + prompt "Magic BREAK sequence" + bool + default y + help + Enable this to be able to use the Magic SysRq functions, + probably using a serial console break. + +config ADK_KERNEL_DEBUG_FS + prompt "Debug Filesystem" + bool + default n + help + debugfs is a virtual file system that kernel developers use to put + debugging files into. Enable this option to be able to read and + write to these files. + +config ADK_KERNEL_DEBUG_WITH_KGDB + boolean + prompt "Enable remote kernel debugging using KGDB" + depends on ADK_TARGET_ROOTFS_NFSROOT || \ + ADK_TARGET_ROOTFS_EXT2_CF || \ + ADK_TARGET_ROOTFS_EXT2 + default n + select ADK_KERNEL_DEBUG_KERNEL + select ADK_KERNEL_DEBUG_INFO + select ADK_KERNEL_KGDB + select ADK_KERNEL_KGDB_SERIAL_CONSOLE + select ADK_KERNEL_FRAME_POINTER + +endmenu diff --git a/target/linux/config/Config.in.fs b/target/linux/config/Config.in.fs new file mode 100644 index 000000000..020025f95 --- /dev/null +++ b/target/linux/config/Config.in.fs @@ -0,0 +1,201 @@ +menu "Filesystems support" + +config ADK_KERNEL_EXT3_FS_XATTR + boolean + default n + +config ADK_KERNEL_FAT_DEFAULT_CODEPAGE + int + default 850 + +config ADK_KERNEL_FAT_DEFAULT_IOCHARSET + string + default "iso8859-1" + +config ADK_KPACKAGE_KMOD_EXPORTFS + tristate + default n + help + +config ADK_KPACKAGE_KMOD_EXT2_FS + prompt "kmod-fs-ext2...................... EXT2 filesystem support" + tristate + default n + depends !ADK_TARGET_ROOTFS_EXT2_CF + depends !ADK_KERNEL_EXT2_FS + help + Ext2 is a standard Linux file system for hard disks. + +config ADK_KPACKAGE_KMOD_EXT3_FS + prompt "kmod-fs-ext3...................... EXT3 filesystem support" + tristate + default n + help + This is the journalling version of the Second extended file system + (often called ext3), the de facto standard Linux file system + (method to organize files on a storage device) for hard disks. + + The journalling code included in this driver means you do not have + to run e2fsck (file system checker) on your file systems after a + crash. The journal keeps track of any changes that were being made + at the time the system crashed, and can ensure that your file system + is consistent without the need for a lengthy check. + + Other than adding the journal to the file system, the on-disk format + of ext3 is identical to ext2. It is possible to freely switch + between using the ext3 driver and the ext2 driver, as long as the + file system has been cleanly unmounted, or e2fsck is run on the file + system. + + To add a journal on an existing ext2 file system or change the + behavior of ext3 file systems, you can use the tune2fs utility ("man + tune2fs"). To modify attributes of files and directories on ext3 + file systems, use chattr ("man chattr"). You need to be using + e2fsprogs version 1.20 or later in order to create ext3 journals + (available at <http://sourceforge.net/projects/e2fsprogs/>). + +config ADK_KPACKAGE_KMOD_HFSPLUS_FS + prompt "kmod-fs-hfsplus................... HFS+ filesystem support" + tristate + select ADK_KPACKAGE_KMOD_NLS + select ADK_KPACKAGE_KMOD_NLS_UTF8 + default n + help + If you say Y here, you will be able to mount extended format + Macintosh-formatted hard drive partitions with full read-write access. + + This file system is often called HFS+ and was introduced with + MacOS 8. It includes all Mac specific filesystem data such as + data forks and creator codes, but it also has several UNIX + style features such as file ownership and permissions. + + +source "package/ntfs-3g/Config.in" + +config ADK_KPACKAGE_KMOD_NTFS_FS + prompt "kmod-fs-ntfs...................... NTFS file system support" + tristate + select ADK_KPACKAGE_KMOD_NLS + default n + help + NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. + + Saying Y or M here enables read support. There is partial, but + safe, write support available. For write support you must also + say Y to "NTFS write support" below. + + There are also a number of user-space tools available, called + ntfsprogs. These include ntfsundelete and ntfsresize, that work + without NTFS support enabled in the kernel. + + This is a rewrite from scratch of Linux NTFS support and replaced + the old NTFS code starting with Linux 2.5.11. A backport to + the Linux 2.4 kernel series is separately available as a patch + from the project web site. + + For more information see <file:Documentation/filesystems/ntfs.txt> + and <http://linux-ntfs.sourceforge.net/>. + + If you are not using Windows NT, 2000, XP or 2003 in addition to + Linux on your computer it is safe to say N. + Kernel modules for NTFS support + +config ADK_KERNEL_FAT_FS + tristate + default n + +config ADK_KPACKAGE_KMOD_VFAT_FS + prompt "kmod-fs-vfat...................... VFAT filesystem support" + select ADK_KERNEL_FAT_FS + select ADK_KPACKAGE_KMOD_NLS + select ADK_KPACKAGE_KMOD_NLS_CODEPAGE_850 + select ADK_KPACKAGE_KMOD_NLS_ISO8859_1 + tristate + default n + help + This option provides support for normal Windows file systems with + long filenames. That includes non-compressed FAT-based file systems + used by Windows 95, Windows 98, Windows NT 4.0, and the Unix + programs from the mtools package. + + The VFAT support enlarges your kernel by about 10 KB Please read the + file <file:Documentation/filesystems/vfat.txt> for details. + +config ADK_KPACKAGE_KMOD_XFS_FS + prompt "kmod-fs-xfs....................... XFS filesystem support" + tristate + select ADK_KPACKAGE_KMOD_EXPORTFS + default n + help + XFS is a high performance journaling filesystem which originated + on the SGI IRIX platform. It is completely multi-threaded, can + support large files and large filesystems, extended attributes, + variable block sizes, is extent based, and makes extensive use of + Btrees (directories, extents, free space) to aid both performance + and scalability. + + Refer to the documentation at <http://oss.sgi.com/projects/xfs/> + for complete details. This implementation is on-disk compatible + with the IRIX version of XFS. + +#config ADK_KPACKAGE_KMOD_YAFFS_FS +# prompt "kmod-fs-yaffs..................... YAFFS1/2 filesystem support" +# tristate +# default n +# select ADK_KERNEL_YAFFS_FS +# select ADK_KERNEL_YAFFS_YAFFS1 +# select ADK_KERNEL_YAFFS_YAFFS2 +# select ADK_KERNEL_YAFFS_AUTO_YAFFS2 +# select ADK_KERNEL_YAFFS_SHORT_NAMES_IN_RAM +# help +# Support for the YAFFS1 and YAFFS2 filesystems for the rb532 NAND +# internal flash (for example). Say 'yes' here if you want to build +# an initramfs for the Routerboard with access to internal flash. +# +config ADK_KPACKAGE_KMOD_FUSE_FS + prompt "kmod-fs-fuse...................... Filesystem in Userspace support" + tristate + default n + help + With FUSE it is possible to implement a fully functional + filesystem in a userspace program. + + By enabling this, only the kernel module gets build. + For using it, you will most likely also want to enable + fuse-utils. + +config ADK_KERNEL_JOLIET + bool + default n + +config ADK_KPACKAGE_KMOD_ISO9660_FS + prompt "kmod-fs-iso9660................... ISO 9660 CDROM file system support" + tristate + select ADK_KERNEL_JOLIET + default n + help + This is the standard file system used on CD-ROMs. It was previously + known as "High Sierra File System" and is called "hsfs" on other + Unix systems. The so-called Rock-Ridge extensions which allow for + long Unix filenames and symbolic links are also supported by this + driver. If you have a CD-ROM drive and want to do more with it than + just listen to audio CDs and watch its LEDs, say Y (and read + <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, + available from <http://www.tldp.org/docs.html#howto>), thereby + enlarging your kernel by about 27 KB; otherwise say N. + +config ADK_KPACKAGE_KMOD_UDF_FS + prompt "kmod-fs-udf....................... UDF file system support" + tristate + select ADK_KPACKAGE_KMOD_CRC_ITU_T + default n + help + This is the new file system used on some CD-ROMs and DVDs. Say Y if + you intend to mount DVD discs or CDRW's written in packet mode, or + if written to by other UDF utilities, such as DirectCD. + Please read <file:Documentation/filesystems/udf.txt>. + +source target/linux/config/Config.in.fsnet +source target/linux/config/Config.in.nls + +endmenu diff --git a/target/linux/config/Config.in.fsnet b/target/linux/config/Config.in.fsnet new file mode 100644 index 000000000..3cb37e52f --- /dev/null +++ b/target/linux/config/Config.in.fsnet @@ -0,0 +1,139 @@ +config ADK_KPACKAGE_KMOD_CIFS + prompt "kmod-fs-cifs...................... CIFS support" + select ADK_KPACKAGE_KMOD_NLS + tristate + default n + help + This is the client VFS module for the Common Internet File System + (CIFS) protocol which is the successor to the Server Message Block + (SMB) protocol, the native file sharing mechanism for most early + PC operating systems. The CIFS protocol is fully supported by + file servers such as Windows 2000 (including Windows 2003, NT 4 + and Windows XP) as well by Samba (which provides excellent CIFS + server support for Linux and many other operating systems). Limited + support for Windows ME and similar servers is provided as well. + You must use the smbfs client filesystem to access older SMB servers + such as OS/2 and DOS. + + The intent of the cifs module is to provide an advanced + network file system client for mounting to CIFS compliant servers, + including support for dfs (hierarchical name space), secure per-user + session establishment, safe distributed caching (oplock), optional + packet signing, Unicode and other internationalization improvements, + and optional Winbind (nsswitch) integration. You do not need to enable + cifs if running only a (Samba) server. It is possible to enable both + smbfs and cifs (e.g. if you are using CIFS for accessing Windows 2003 + and Samba 3 servers, and smbfs for accessing old servers). If you need + to mount to Samba or Windows from this machine, say Y. + +config ADK_KPACKAGE_KMOD_CODA_FS + prompt "kmod-fs-coda...................... support for coda client" + tristate + default n + help + This is the kernel part of the client for the CODA filesystem. + +config ADK_KERNEL_NFS_V4 + boolean + depends on !ADK_TARGET_ROOTFS_NFSROOT + default n + +config ADK_KERNEL_RPCSEC_GSS_KRB5 + boolean + depends on !ADK_TARGET_ROOTFS_NFSROOT + default n + +config ADK_KPACKAGE_KMOD_NFS_FS + prompt "kmod-fs-nfs....................... NFS client support (includes V3 support)" + tristate + default n + select ADK_KERNEL_NFS_V3 + select ADK_KPACKAGE_KMOD_SUNRPC + depends on !ADK_TARGET_ROOTFS_NFSROOT + help + If you are connected to some other (usually local) Unix computer + (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing + on that computer (the NFS server) using the Network File Sharing + protocol, say Y. "Mounting files" means that the client can access + the files with usual UNIX commands as if they were sitting on the + client's hard disk. For this to work, the server must run the + programs nfsd and mountd (but does not need to have NFS file system + support enabled in its kernel). NFS is explained in the Network + Administrator's Guide, available from + <http://www.tldp.org/docs.html#guide>, on its man page: "man + nfs", and in the NFS-HOWTO. + + A superior but less widely used alternative to NFS is provided by + the Coda file system; see "Coda file system support" below. + + If you say Y here, you should have said Y to TCP/IP networking also. + This option would enlarge your kernel by about 27 KB. + + To compile this file system support as a module, choose M here: the + module will be called nfs. + + If you are configuring a diskless machine which will mount its root + file system over NFS at boot time, say Y here and to "Kernel + level IP autoconfiguration" above and to "Root file system on NFS" + below. You cannot compile this driver as a module in this case. + There are two packages designed for booting diskless machines over + the net: netboot, available from + <http://ftp1.sourceforge.net/netboot/>, and Etherboot, + available from <http://ftp1.sourceforge.net/etherboot/>. + + If you don't know what all this is about, say N. + Kernel modules for NFS client support + +config ADK_KERNEL_NFSD_V3 + boolean + default n + +config ADK_KPACKAGE_KMOD_NFSD + prompt "kmod-fs-nfsd...................... NFS server support (includes V3 support)" + tristate + default n + select ADK_KPACKAGE_KMOD_EXPORTFS + select ADK_KERNEL_NFSD_V3 + depends ADK_KPACKAGE_KMOD_NFS_FS + help + If you want your Linux box to act as an NFS *server*, so that other + computers on your local network which support NFS can access certain + directories on your box transparently, you have two options: you can + use the self-contained user space program nfsd, in which case you + should say N here, or you can say Y and use the kernel based NFS + server. The advantage of the kernel based solution is that it is + faster. + + In either case, you will need support software; the respective + locations are given in the file <file:Documentation/Changes> in the + NFS section. + + If you say Y here, you will get support for version 2 of the NFS + protocol (NFSv2). If you also want NFSv3, say Y to the next question + as well. + + Please read the NFS-HOWTO, available from + <http://www.tldp.org/docs.html#howto>. + +config ADK_KERNEL_NFSD_V4 + prompt "Enable NFSv4 and RPC Kerberos" + boolean + depends on ADK_KPACKAGE_KMOD_NFSD + select ADK_KPACKAGE_KMOD_SUNRPC_GSS + select ADK_KPACKAGE_KMOD_RPCSEC_GSS_KRB5 + select ADK_KERNEL_NFS_V4 + default n + help + NFSv4 with Kerberos authentication. + +config ADK_KPACKAGE_KMOD_SUNRPC + tristate + default n + +config ADK_KPACKAGE_KMOD_SUNRPC_GSS + tristate + default n + +config ADK_KPACKAGE_KMOD_RPCSEC_GSS_KRB5 + tristate + default n diff --git a/target/linux/config/Config.in.input b/target/linux/config/Config.in.input new file mode 100644 index 000000000..5f1cffd77 --- /dev/null +++ b/target/linux/config/Config.in.input @@ -0,0 +1,41 @@ +menu "Input devices" + +config ADK_KERNEL_INPUT + bool + default n + +config ADK_KERNEL_INPUT_KEYBOARD + bool + default n + +config ADK_KERNEL_HID_SUPPORT + bool + default n + +config ADK_KERNEL_HID + tristate + select ADK_KERNEL_HID_SUPPORT + default n + +config ADK_KPACKAGE_KMOD_USB_HID + prompt "kmod-usb-hid..................... USB keyboard/mouse support" + tristate + select ADK_KERNEL_INPUT + select ADK_KERNEL_HID + select ADK_PACKAGE_KMOD_USB_CONTROLLER + default n + +config ADK_KPACKAGE_KMOD_KEYBOARD_ATKBD + prompt "kmod-input-keyboard.............. Keyboard support (AT)" + tristate + select ADK_KERNEL_INPUT + select ADK_KERNEL_INPUT_KEYBOARD + default n + +config ADK_KPACKAGE_KMOD_INPUT_MOUSEDEV + prompt "kmod-input-mouse................. Mouse support (PS/2)" + select ADK_KERNEL_INPUT + tristate + default n + +endmenu diff --git a/target/linux/config/Config.in.ipvs b/target/linux/config/Config.in.ipvs new file mode 100644 index 000000000..cec68d6cf --- /dev/null +++ b/target/linux/config/Config.in.ipvs @@ -0,0 +1,118 @@ +menu "IPVS support" + +config ADK_KPACKAGE_KMOD_IP_VS + prompt "kmod-ip-vs............................ IPVS support" + tristate + select ADK_KERNEL_NETFILTER + default n + +config ADK_KERNEL_IP_VS_DEBUG + prompt "enable debugging support" + boolean + default n + depends ADK_KPACKAGE_KMOD_IP_VS + +menu "IPVS transport protocol load balancing support" + depends ADK_KPACKAGE_KMOD_IP_VS + +config ADK_KERNEL_IP_VS_PROTO_TCP + prompt "TCP load balancing support" + boolean + default n + help + This option enables support for load balancing TCP transport + protocol. Say Y if unsure. + +config ADK_KERNEL_IP_VS_PROTO_UDP + prompt "UDP load balancing support" + boolean + default n + help + This option enables support for load balancing UDP transport + protocol. Say Y if unsure. + +config ADK_KERNEL_IP_VS_PROTO_ESP + prompt "ESP load balancing support" + boolean + default n + help + This option enables support for load balancing ESP (Encapsulation + Security Payload) transport protocol. Say Y if unsure. + +config ADK_KERNEL_IP_VS_PROTO_AH + prompt "AH load balancing support" + boolean + default n + help + This option enables support for load balancing AH (Authentication + Header) transport protocol. Say Y if unsure. + +endmenu + +menu "IPVS Scheduler" + depends ADK_KPACKAGE_KMOD_IP_VS + +config ADK_KPACKAGE_KMOD_IP_VS_RR + prompt "kmod-ip-vs-rr......................... round-robin" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_WRR + prompt "kmod-ip-vs-wrr........................ weighted round-robin" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_LC + prompt "kmod-ip-vs-lc......................... least-connection" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_WLC + prompt "kmod-ip-vs-wlc........................ weighted least-connection" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_LBLC + prompt "kmod-ip-vs-lblc....................... locality-based least-connection" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_LBLCR + prompt "kmod-ip-vs-lblcr...................... locality-based least-connection with replication" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_DH + prompt "kmod-ip-vs-dh......................... destination hashing" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_SH + prompt "kmod-ip-vs-sh......................... source hashing" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_SED + prompt "kmod-ip-vs-sed........................ shortest expected delay" + tristate + default n + +config ADK_KPACKAGE_KMOD_IP_VS_NQ + prompt "kmod-ip-vs-nq......................... never queue" + tristate + default n + +endmenu + +menu "IPVS application helper" + depends ADK_KPACKAGE_KMOD_IP_VS + +config ADK_KPACKAGE_KMOD_IP_VS_FTP + prompt "kmod-ip-vs-ftp........................ FTP protocol" + tristate + default n + select ADK_KERNEL_IP_VS_PROTO_TCP + +endmenu + +endmenu diff --git a/target/linux/config/Config.in.isdn b/target/linux/config/Config.in.isdn new file mode 100644 index 000000000..8f6da5ef8 --- /dev/null +++ b/target/linux/config/Config.in.isdn @@ -0,0 +1,44 @@ +menu "ISDN" + +config ADK_KERNEL_ISDN + bool + default n + +config ADK_KERNEL_ISDN_I4L + bool + default n + +config ADK_KERNEL_ISDN_DRV_AVMB1_VERBOSE_REASON + bool + default n + +config ADK_KERNEL_CAPI_AVM + bool + default n + +config ADK_KERNEL_CAPI_EICON + bool + default n + +config ADK_KERNEL_HFCMULTI_PCIMEM + bool + default n + +config ADK_KERNEL_ISDN_CAPI_MIDDLEWARE + bool + default n + +config ADK_KERNEL_ISDN_CAPI_CAPI20 + tristate + default n + +config ADK_KPACKAGE_KMOD_ISDN_CAPI + prompt "kmod-isdn-capi.................... Support for CAPI 2.0" + tristate + select ADK_KERNEL_ISDN_CAPI_CAPI20 + select ADK_KERNEL_ISDN + default n + help + Kernel support for CAPI 2.0 and /dev/capi20 + +endmenu diff --git a/target/linux/config/Config.in.kernel b/target/linux/config/Config.in.kernel new file mode 100644 index 000000000..6b34b2448 --- /dev/null +++ b/target/linux/config/Config.in.kernel @@ -0,0 +1,82 @@ +config ADK_KERNEL_ETRAX_MTD_SIZE + hex + depends on ADK_LINUX_CRIS_FOXBOARD_CLASSIC || ADK_LINUX_CRIS_FOXBOARD_LX + default "0x00400000" if ADK_LINUX_CRIS_FOXBOARD_CLASSIC + default "0x00800000" if ADK_LINUX_CRIS_FOXBOARD_LX + +config ADK_KERNEL_ETRAX_DRAM_SIZE + int + depends on ADK_LINUX_CRIS_FOXBOARD_CLASSIC || ADK_LINUX_CRIS_FOXBOARD_LX + default "16" if ADK_LINUX_CRIS_FOXBOARD_CLASSIC + default "32" if ADK_LINUX_CRIS_FOXBOARD_LX + +config ADK_KERNEL_ETRAX_DEF_R_SDRAM_TIMING + hex + depends on ADK_LINUX_CRIS_FOXBOARD_CLASSIC || ADK_LINUX_CRIS_FOXBOARD_LX + default "0x80608002" if ADK_LINUX_CRIS_FOXBOARD_CLASSIC + default "0x80008002" if ADK_LINUX_CRIS_FOXBOARD_LX + +config ADK_KERNEL_NETWORK_FILESYSTEMS + boolean + default y + +config ADK_KERNEL_IP_PNP + boolean + default n + +config ADK_KERNEL_IP_PNP_DHCP + boolean + default n + +config ADK_KERNEL_NFS_FS + boolean + default n + +config ADK_KERNEL_NFS_V3 + boolean + default n + +config ADK_KERNEL_ROOT_NFS + boolean + default n + +config ADK_KERNEL_LOCKD + boolean + default n + +config ADK_KERNEL_NFS_COMMON + boolean + default n + +config ADK_KERNEL_SUNRPC + boolean + default n + +#config ADK_KERNEL_YAFFS_FS +# tristate +# default n + +#config ADK_KERNEL_YAFFS_YAFFS1 +# boolean +# default n + +#config ADK_KERNEL_YAFFS_YAFFS2 +# boolean +# default n + +#config ADK_KERNEL_YAFFS_AUTO_YAFFS2 +# boolean +# default n + +#config ADK_KERNEL_YAFFS_CHECKPOINT_RESERVED_BLOCKS +# int +# default 0 + +#config ADK_KERNEL_YAFFS_SHORT_NAMES_IN_RAM +# boolean +# default n + +config ADK_KERNEL_EXT2_FS + boolean + default n + diff --git a/target/linux/config/Config.in.leds b/target/linux/config/Config.in.leds new file mode 100644 index 000000000..46da9914b --- /dev/null +++ b/target/linux/config/Config.in.leds @@ -0,0 +1,14 @@ +menu "LEDS driver support" + +config ADK_KERNEL_NEW_LEDS + bool + default n + help + +config ADK_KPACKAGE_KMOD_LEDS_CLASS + prompt "LED Class support" + tristate + default n + help + +endmenu diff --git a/target/linux/config/Config.in.lib b/target/linux/config/Config.in.lib new file mode 100644 index 000000000..e7b223c43 --- /dev/null +++ b/target/linux/config/Config.in.lib @@ -0,0 +1,42 @@ +menu "Library Routines" + +config ADK_KERNEL_CRC32 + bool + default n + +config ADK_KPACKAGE_KMOD_CRC_ITU_T + prompt "kmod-crc-itu-t...................... CRC ITU-T V.41 functions" + tristate + default n + help + This option is provided for the case where no in-kernel-tree + modules require CRC ITU-T V.41 functions, but a module built outside + the kernel tree does. Such modules that use library CRC ITU-T V.41 + functions require M here. + +config ADK_KPACKAGE_KMOD_CRC32 + prompt "kmod-crc32.......................... provide CRC32 library functions" + tristate + depends ! ADK_KERNEL_CRC32 + default n + help + +config ADK_KPACKAGE_KMOD_LIBCRC32C + prompt "kmod-libcrc32c...................... CRC32c Cyclic Redundancy-Check" + tristate + default n + help + This option is provided for the case where no in-kernel-tree + modules require CRC32c functions, but a module built outside the + kernel tree does. Such modules that use library CRC32c functions + require M here. See Castagnoli93. + +config ADK_KPACKAGE_KMOD_CRC_CCITT + prompt "kmod-crc-ccitt...................... provide CRC-CCITT library functions" + tristate + default n + help + This module provides CRC-CCITT library functions for kernel modules built + outside the kernel. + +endmenu diff --git a/target/linux/config/Config.in.misc b/target/linux/config/Config.in.misc new file mode 100644 index 000000000..eea6ccc38 --- /dev/null +++ b/target/linux/config/Config.in.misc @@ -0,0 +1,77 @@ +menu "Miscellaneous devices support" + +source target/linux/config/Config.in.leds + +config ADK_KERNEL_WATCHDOG + boolean + default n + +config ADK_KPACKAGE_KMOD_SOFT_WATCHDOG + prompt "kmod-softdog...................... Software watchdog" + tristate + default n + select ADK_KERNEL_WATCHDOG + help + A software monitoring watchdog. This will fail to reboot your system + from some situations that the hardware watchdog will recover + from. Equally it's a lot cheaper to install. + +config ADK_KPACKAGE_KMOD_WD1100 + prompt "kmod-wd1100....................... Soekris net4801 watchdog" + tristate + select ADK_KERNEL_WATCHDOG + default n + help + Driver for the NatSemi SC1x00 series Watchdog + found on Soekris net4801 boards + +config ADK_KPACKAGE_KMOD_PARPORT + prompt "kmod-parport...................... generic parallel port support" + tristate + default n + help + Kernel module for generic parallel port support + +config ADK_KPACKAGE_KMOD_PLIP + prompt "kmod-plip....................... PLIP (internet over parallel port)" + tristate + default n + depends on ADK_KPACKAGE_KMOD_PARPORT + help + PLIP: IPv4 over parallel port, using a Turbo Laplink + (crossed null-printer) cable. Drivers exist for DOS + (from Crynwr), Linux 2.x (protocol changed and is no + longer compatible with Linux 1.x), FreeBSD and MirBSD. + This will enlarge your kernel by about 8 KiB. + +config ADK_KPACKAGE_KMOD_PRINTER + prompt "kmod-lp......................... line printer support" + tristate + default n + depends on ADK_KPACKAGE_KMOD_PARPORT + help + Kernel module for line printer support + +config ADK_KPACKAGE_KMOD_PPDEV + prompt "kmod-ppdev...................... userland parallel port driver" + tristate + default n + depends on ADK_KPACKAGE_KMOD_PARPORT + help + Kernel module for userland parallel port access + +config ADK_KPACKAGE_KMOD_FW_LOADER + prompt "kmod-fw-loader.................. userspace firmware loading support" + tristate + default n + help + This may be necessary when using drivers which require + loading of external firmware files. + +config ADK_KPACKAGE_KMOD_EEPROM_93CX6 + prompt "kmod-eeprom-93cx6................ 93cx6 eeprom support" + tristate + default n + help + +endmenu diff --git a/target/linux/config/Config.in.multimedia b/target/linux/config/Config.in.multimedia new file mode 100644 index 000000000..88ee9e00c --- /dev/null +++ b/target/linux/config/Config.in.multimedia @@ -0,0 +1,113 @@ +menu "Multimedia devices support" + +config ADK_KERNEL_SND_TIMER + boolean + default n + +config ADK_KERNEL_SND_PCM + boolean + default n + +config ADK_KERNEL_SND_HWDEP + boolean + default n + +config ADK_KERNEL_SND_MIXER_OSS + boolean + default n + +config ADK_KERNEL_SND_PCM_OSS + boolean + default n + +config ADK_KPACKAGE_KMOD_SOUND + tristate + default n + help + Basic support for sound. + +config ADK_KPACKAGE_KMOD_SND + prompt "kmod-sound-alsa................. ALSA sound support" + select ADK_KPACKAGE_KMOD_SOUND + select ADK_KERNEL_SND_TIMER + select ADK_KERNEL_SND_PCM + select ADK_KERNEL_SND_HWDEP + tristate + default n + help + Basic ALSA sound support. + +config ADK_KPACKAGE_KMOD_SND_OSSEMUL + prompt "kmod-sound-alsa-oss-emul........ ALSA OSS Emulation" + depends ADK_KPACKAGE_KMOD_SND + select ADK_KERNEL_SND_MIXER_OSS + select ADK_KERNEL_SND_PCM_OSS + tristate + default n + help + ALSA OSS Emulation + +config ADK_KPACKAGE_KMOD_SND_AC97_CODEC + prompt "kmod-sound-alsa-ac97-codec..... ALSA AC97 codec" + depends ADK_KPACKAGE_KMOD_SND + tristate + default n + help + ALSA AC97 driver + +config ADK_KPACKAGE_KMOD_SND_VIA82XX + prompt "kmod-sound-alsa-via82xx........ ALSA VIA82XX driver" + depends ADK_KPACKAGE_KMOD_SND + select ADK_KPACKAGE_KMOD_SND_AC97_CODEC + tristate + default n + help + ALSA VIA82XX driver + +config ADK_KPACKAGE_KMOD_SND_CS5535AUDIO + prompt "kmod-sound-alsa-cs5535......... ALSA AMD CS5535 driver (ALIX1C)" + depends ADK_KPACKAGE_KMOD_SND + select ADK_KPACKAGE_KMOD_SND_AC97_CODEC + depends on ADK_LINUX_X86_ALIX1C + tristate + default n + help + ALSA AMD CS5535 driver + +config ADK_KPACKAGE_KMOD_VIDEO_DEV + prompt "kmod-videodev................... Video (For Linux) kernel support" + tristate + default n + help + Support for audio/video capture and overlay devices and FM radio + cards. The exact capabilities of each device vary. + + This kernel includes support for the new Video for Linux Two API, + (V4L2) as well as the original system. Drivers and applications + need to be rewritten to use V4L2, but drivers for popular cards + and applications for most video capture functions already exist. + + Additional info and docs are available on the web at + <http://linuxtv.org> + + Documentation for V4L2 is also available on the web at + <http://bytesex.org/v4l/>. + +config ADK_KPACKAGE_KMOD_VIDEO_V4L1 + prompt "................................ Enable Video For Linux API 1 (DEPRECATED)" + boolean + default n + depends ADK_KPACKAGE_KMOD_VIDEO_DEV + help + Enables a compatibility API used by most V4L2 devices to allow + its usage with legacy applications that supports only V4L1 api. + +config ADK_KPACKAGE_KMOD_USB_PWC + prompt "kmod-usb-pwc.................... Kernel driver for USB Philips Cameras" + tristate + depends ADK_KPACKAGE_KMOD_USB + default n + help + +#source package/em28xx/Config.in +endmenu diff --git a/target/linux/config/Config.in.netdevice b/target/linux/config/Config.in.netdevice new file mode 100644 index 000000000..49e772238 --- /dev/null +++ b/target/linux/config/Config.in.netdevice @@ -0,0 +1,191 @@ +menu "Network devices support" +depends on !ADK_LINUX_CRIS_FOXBOARD + +config ADK_KERNEL_NET_ETHERNET + boolean + default n + +config ADK_KERNEL_MII + boolean + default n + +config ADK_KERNEL_NET_PCI + boolean + default n + +config ADK_KERNEL_NETDEV_1000 + boolean + default n + +menu "Ethernet card support" + +config ADK_KPACKAGE_KMOD_NE2K_PCI + prompt "kmod-net-ne2k-pci............. NE2000 PCI driver" + select ADK_KERNEL_NET_ETHERNET + select ADK_KERNEL_NET_PCI + select ADK_KERNEL_MII + tristate + default n + help + NE2000 pci driver + +config ADK_KPACKAGE_KMOD_E100 + prompt "kmod-net-e100................. Intel(R) PRO/100+ driver" + select ADK_KERNEL_NET_ETHERNET + select ADK_KERNEL_NET_PCI + select ADK_KERNEL_MII + tristate + default n + help + Intel(R) PRO/100+ cards kernel support + +config ADK_KPACKAGE_KMOD_E1000 + prompt "kmod-net-e1000................ Intel(R) PRO/1000 Gigabit Ethernet driver" + select ADK_KERNEL_NET_ETHERNET + select ADK_KERNEL_NETDEV_1000 + tristate + default n + help + This driver supports Intel(R) PRO/1000 gigabit ethernet family of + adapters. For more information on how to identify your adapter, go + to the Adapter & Driver ID Guide at: + + <http://support.intel.com/support/network/adapter/pro100/21397.htm> + +endmenu + +config ADK_KERNEL_WIRELESS + boolean + default n + +config ADK_KERNEL_WIRELESS_EXT + boolean + default n + +config ADK_KERNEL_MAC80211_LEDS + bool + select ADK_KPACKAGE_KMOD_LEDS_CLASS + select ADK_KERNEL_NEW_LEDS + default n + +config ADK_KERNEL_WLAN_80211 + boolean + default n + +config ADK_KERNEL_RT2X00 + boolean + select ADK_KPACKAGE_KMOD_RT2X00 + select ADK_KPACKAGE_KMOD_FW_LOADER + select ADK_KPACKAGE_KMOD_EEPROM_93CX6 + default n + +config ADK_MOD_KERNEL_CFG80211 + tristate + default n + +config ADK_MOD_KERNEL_MAC80211 + tristate + select ADK_MOD_KERNEL_CFG80211 + select ADK_KPACKAGE_KMOD_CRYPTO_AES + select ADK_KPACKAGE_KMOD_CRYPTO_ECB + select ADK_KPACKAGE_KMOD_CRYPTO_ARC4 + select ADK_KERNEL_CRC32 + select ADK_KERNEL_WIRELESS + select ADK_KERNEL_WIRELESS_EXT + select ADK_KERNEL_WLAN_80211 + select ADK_KERNEL_MAC80211_LEDS + default n + +menu "Wireless card support" + +config ADK_KPACKAGE_KMOD_MAC80211 + prompt "kmod-mac80211................... mac80211 softmac" + tristate + select ADK_MOD_KERNEL_CFG80211 + select ADK_KPACKAGE_KMOD_CRYPTO_AES + select ADK_KPACKAGE_KMOD_CRYPTO_ECB + select ADK_KPACKAGE_KMOD_CRYPTO_ARC4 + select ADK_KERNEL_WIRELESS + select ADK_KERNEL_WIRELESS_EXT + select ADK_KERNEL_WLAN_80211 + select ADK_KERNEL_CRC32 + default n + +config ADK_KPACKAGE_KMOD_ATH5K + prompt "kmod-mac80211-ath5k............ Atheros 5xxx wireless cards" + tristate + select ADK_KERNEL_MAC80211_LEDS + depends on ADK_KPACKAGE_KMOD_MAC80211 + default n + help + Driver for Atheros 5xxx/24xx cards. + +config ADK_KERNEL_ATH5K_DEBUG + prompt "enable debugging info via debugfs" + depends on ADK_KPACKAGE_KMOD_ATH5K + default n + select ADK_KERNEL_DEBUG_FS + boolean + help + Atheros 5xxx debugging messages. + Say Y, if and you will get debug options for ath5k. + To use this, you need to mount debugfs: + mkdir /debug/ + mount -t debugfs debug /debug/ + You will get access to files under: + /debug/ath5k/phy0/ + To enable debug, pass the debug level to the debug module + parameter. For example: + insmod ath5k.ko debug=0x00000400 + +config ADK_KPACKAGE_KMOD_RT2X00 + tristate + default n + +config ADK_KPACKAGE_KMOD_RT2400PCI + prompt "kmod-mac80211-rt2400........... Ralink rt2400" + tristate + default n + select ADK_KERNEL_RT2X00 + select ADK_KERNEL_MAC80211_LEDS + depends on ADK_KPACKAGE_KMOD_MAC80211 + help + This adds support for rt2400 wireless chipset family. + Supported chips: RT2460. + +config ADK_KPACKAGE_KMOD_RT2500PCI + prompt "kmod-mac80211-rt2500........... Ralink rt2500" + tristate + default n + select ADK_KERNEL_RT2X00 + select ADK_KERNEL_MAC80211_LEDS + depends on ADK_KPACKAGE_KMOD_MAC80211 + help + This adds support for rt2500 wireless chipset family. + Supported chips: RT2560. + +config ADK_KPACKAGE_KMOD_RT61PCI + prompt "kmod-mac80211-rt2501........... Ralink rt2501/rt61" + tristate + default n + select ADK_KERNEL_RT2X00 + select ADK_KERNEL_MAC80211_LEDS + select ADK_KPACKAGE_KMOD_CRC_ITU_T + select ADK_PACKAGE_WIRELESS_FIRMWARE_RT61 + depends on ADK_KPACKAGE_KMOD_MAC80211 + help + This adds support for rt2501 wireless chipset family. + Supported chips: RT2561, RT2561S & RT2661. + +config ADK_KERNEL_RT2X00_DEBUG + prompt "enable debugging info" + depends on ADK_KPACKAGE_KMOD_RT61PCI || \ + ADK_KPACKAGE_KMOD_RT2500PCI || ADK_KPACKAGE_KMOD_RT2400PCI + default n + boolean + help + +source package/mac80211/Config.in + +endmenu +endmenu diff --git a/target/linux/config/Config.in.netfilter b/target/linux/config/Config.in.netfilter new file mode 100644 index 000000000..6553471a0 --- /dev/null +++ b/target/linux/config/Config.in.netfilter @@ -0,0 +1,456 @@ +menu "Netfilter (Firewall/Filtering)" + +config ADK_KERNEL_NETFILTER + bool + default n + +config ADK_KERNEL_NETFILTER_ADVANCED + bool + default n + +config ADK_KERNEL_NETFILTER_XTABLES + bool + select ADK_KERNEL_NETFILTER + select ADK_KERNEL_NETFILTER_ADVANCED + default n + +config ADK_KERNEL_NETFILTER_DEBUG + bool + default n + +config ADK_KERNEL_IP_NF_MATCH_LAYER7_DEBUG + bool + default n + +config ADK_KERNEL_IP_NF_TARGET_MIRROR + tristate + default n + +config ADK_KERNEL_IP_NF_NAT_SNMP_BASIC + tristate + default n + +config ADK_KERNEL_IP_NF_TARGET_DSCP + tristate + default n + +config ADK_KERNEL_IP_NF_TARGET_MARK + tristate + default n + +config ADK_KERNEL_IP_NF_TARGET_CLASSIFY + tristate + default n + +config ADK_KERNEL_IP_NF_TARGET_IMQ + tristate + default n + +config ADK_KERNEL_IP_NF_TARGET_CONNMARK + tristate + default n + +config ADK_KERNEL_IP_NF_ARPTABLES + tristate + default n + +config ADK_KERNEL_IP_NF_COMPAT_IPCHAINS + tristate + default n + +config ADK_KERNEL_IP_NF_COMPAT_IPFWADM + tristate + default n + +config ADK_KERNEL_IP6_NF_QUEUE + tristate + default n + +config ADK_KERNEL_IP6_NF_IPTABLES + tristate + default n + +config ADK_KERNEL_IP_ROUTE_FWMARK + bool + default n + +config ADK_KERNEL_IP_NF_QUEUE + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_TIME + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_CONDITION + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_DSCP + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_AH_ESP + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_LENGTH + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_HELPER + tristate + default n + +# cannot be ADK_KERNEL_IP_NF_MATCH_STATE because +# netfilter is built as a module -> this'll always be +# a module, too +config ADK_KPACKAGE_KMOD_IP_NF_MATCH_STATE + tristate + select ADK_KPACKAGE_KMOD_NETFILTER_XT_MATCH_STATE + default n + +config ADK_KPACKAGE_KMOD_NETFILTER_XT_MATCH_STATE + tristate + default n + +# cannot be ADK_KERNEL_IP_NF_MATCH_CONNTRACK because +# netfilter is built as a module -> this'll always be +# a module, too +config ADK_KPACKAGE_KMOD_IP_NF_MATCH_CONNTRACK + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_CONNMARK + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_UNCLEAN + tristate + default n + +config ADK_KERNEL_IP_NF_MATCH_STRING + tristate + default n + +menu "Core Netfilter Configuration" + +config ADK_KPACKAGE_KMOD_NF_CONNTRACK + tristate 'Netfilter connection tracking support' + select ADK_KERNEL_NETFILTER_XTABLES + help + Connection tracking keeps a record of what packets have passed + through your machine, in order to figure out how they are related + into connections. + + Layer 3 independent connection tracking is experimental scheme + which generalize ip_conntrack to support other layer 3 protocols. + +config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CLASSIFY + tristate '"CLASSIFY" target support' + select ADK_KERNEL_NETFILTER_XTABLES + help + This option adds a `CLASSIFY' target, which enables the user to set + the priority of a packet. Some qdiscs can use this value for + classification, among these are: + + atm, cbq, dsmark, pfifo_fast, htb, prio + +config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CONNMARK + tristate '"CONNMARK" target support' + select ADK_KERNEL_NETFILTER_XTABLES + select ADK_KPACKAGE_KMOD_NF_CONNTRACK + help + This option adds a `CONNMARK' target, which allows one to manipulate + the connection mark value. Similar to the MARK target, but + affects the connection mark value rather than the packet mark value. + +config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_MARK + tristate '"MARK" target support' + select ADK_KERNEL_NETFILTER_XTABLES + help + This option adds a `MARK' target, which allows you to create rules + in the `mangle' table which alter the netfilter mark (nfmark) field + associated with the packet prior to routing. This can change + the routing method (see `Use netfilter MARK value as routing + key') and can also be used by other subsystems to change their + behavior. + +config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_NFQUEUE + tristate '"NFQUEUE" target support' + select ADK_KERNEL_NETFILTER_XTABLES + help + This target replaced the old obsolete QUEUE target. + + As opposed to QUEUE, it supports 65535 different queues, + not just one. + +endmenu + +menu "IP: Netfilter Configuration" + +config ADK_KPACKAGE_KMOD_NF_CONNTRACK_IPV4 + bool 'IPv4 connection tracking support (required for NAT)' + select ADK_KPACKAGE_KMOD_NF_CONNTRACK + help + Connection tracking keeps a record of what packets have passed + through your machine, in order to figure out how they are related + into connections. + +config ADK_KPACKAGE_KMOD_IP_NF_CT_ACCT + bool 'Connection tracking flow accounting' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + If this option is enabled, the connection tracking code will + keep per-flow packet and byte counters. + + Those counters can be used for flow-based accounting or the + `connbytes' match. + +config ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK_MARK + bool 'Connection mark tracking support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + select ADK_KERNEL_IP_NF_MATCH_CONNMARK + help + This option enables support for connection marks, used by the + `CONNMARK' target and `connmark' match. Similar to the mark value + of packets, but this mark value is kept in the conntrack session + instead of the individual packets. + +config ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK_SECMARK + bool 'Connection tracking security mark support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + #FIXME select NETWORK_SECMARK + help + This option enables security markings to be applied to + connections. Typically they are copied to connections from + packets using the CONNSECMARK target and copied back from + connections to packets with the same target, with the packets + being originally labeled via SECMARK. + +config ADK_KPACKAGE_KMOD_IP_NF_FTP + tristate 'FTP protocol support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + Tracking FTP connections is problematic: special helpers are + required for tracking them, and doing masquerading and other forms + of Network Address Translation on them. + +config ADK_KPACKAGE_KMOD_IP_NF_IRC + tristate 'IRC protocol support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + There is a commonly-used extension to IRC called + Direct Client-to-Client Protocol (DCC). This enables users to send + files to each other, and also chat to each other without the need + of a server. DCC Sending is used anywhere you send files over IRC, + and DCC Chat is most commonly used by Eggdrop bots. If you are + using NAT, this extension will enable you to send files and initiate + chats. Note that you do NOT need this extension to get files or + have others initiate chats, or everything else in IRC. + +config ADK_KPACKAGE_KMOD_IP_NF_NETBIOS_NS + tristate 'NetBIOS name service protocol support (EXPERIMENTAL)' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + NetBIOS name service requests are sent as broadcast messages from an + unprivileged port and responded to with unicast messages to the + same port. This make them hard to firewall properly because connection + tracking doesn't deal with broadcasts. This helper tracks locally + originating NetBIOS name service requests and the corresponding + responses. It relies on correct IP address configuration, specifically + netmask and broadcast address. When properly configured, the output + of "ip address show" should look similar to this: + + $ ip -4 address show eth0 + 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 + inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0 + +config ADK_KPACKAGE_KMOD_IP_NF_TFTP + tristate 'TFTP protocol support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + TFTP connection tracking helper, this is required depending + on how restrictive your ruleset is. + If you are using a tftp client behind -j SNAT or -j MASQUERADING + you will need this. + +config ADK_KPACKAGE_KMOD_IP_NF_AMANDA + tristate 'Amanda backup protocol support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + #FIXME TEXTSEARCH && TEXTSEARCH_KMP + help + If you are running the Amanda backup package <http://www.amanda.org/> + on this machine or machines that will be MASQUERADED through this + machine, then you may want to enable this feature. This allows the + connection tracking and natting code to allow the sub-channels that + Amanda requires for communication of the backup data, messages and + index. + +config ADK_KPACKAGE_KMOD_IP_NF_PPTP + tristate 'PPTP protocol support' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + This module adds support for PPTP (Point to Point Tunnelling + Protocol, RFC2637) connection tracking and NAT. + + If you are running PPTP sessions over a stateful firewall or NAT + box, you may want to enable this feature. + + Please note that not all PPTP modes of operation are supported yet. + For more info, read top of the file + net/ipv4/netfilter/ip_conntrack_pptp.c + +config ADK_KPACKAGE_KMOD_IP_NF_H323 + tristate 'H.323 protocol support (EXPERIMENTAL)' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + H.323 is a VoIP signalling protocol from ITU-T. As one of the most + important VoIP protocols, it is widely used by voice hardware and + software including voice gateways, IP phones, Netmeeting, OpenPhone, + Gnomemeeting, etc. + + With this module you can support H.323 on a connection tracking/NAT + firewall. + + This module supports RAS, Fast Start, H.245 Tunnelling, Call + Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat, + whiteboard, file transfer, etc. For more information, please + visit http://nath323.sourceforge.net/. + +config ADK_KPACKAGE_KMOD_IP_NF_SIP + tristate 'SIP protocol support (EXPERIMENTAL)' + depends ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK + help + SIP is an application-layer control protocol that can establish, + modify, and terminate multimedia sessions (conferences) such as + Internet telephony calls. With the ip_conntrack_sip and + the ip_nat_sip modules you can support the protocol on a connection + tracking/NATing firewall. + + +config ADK_KPACKAGE_KMOD_IP_NF_IPTABLES + tristate 'IP tables support (required for filtering/masq/NAT)' + select ADK_KERNEL_NETFILTER_XTABLES + help + iptables is a general, extensible packet identification framework. + The packet filtering and full NAT (masquerading, port forwarding, + etc) subsystems now use this: say `Y' or `M' here if you want to use + either of those. + +config ADK_KPACKAGE_KMOD_IP_NF_FILTER + tristate 'Packet Filtering' + depends ADK_KPACKAGE_KMOD_IP_NF_IPTABLES + help + Packet filtering defines a table `filter', which has a series of + rules for simple packet filtering at local input, forwarding and + local output. See the man page for iptables(8). + +config ADK_KPACKAGE_KMOD_NF_NAT + tristate 'Full NAT' + depends ADK_KPACKAGE_KMOD_IP_NF_IPTABLES + help + The Full NAT option allows masquerading, port forwarding and other + forms of full Network Address Port Translation. It is controlled by + the `nat' table in iptables: see the man page for iptables(8). + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_MASQUERADE + tristate 'MASQUERADE target support' + depends ADK_KPACKAGE_KMOD_NF_NAT + help + Masquerading is a special case of NAT: all outgoing connections are + changed to seem to come from a particular interface's address, and + if the interface goes down, those connections are lost. This is + only useful for dialup accounts with dynamic IP address (ie. your IP + address will be different on next dialup). + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REJECT + tristate 'REJECT target support' + depends ADK_KPACKAGE_KMOD_IP_NF_FILTER + help + The REJECT target allows a filtering rule to specify that an ICMP + error should be issued in response to an incoming packet, rather + than silently being dropped. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_LOG + tristate 'LOG target support' + depends ADK_KPACKAGE_KMOD_IP_NF_FILTER + help + This option adds a `LOG' target, which allows you to create rules in + any iptables table which records the packet header to the syslog. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ULOG + tristate 'ULOG target support (ipv4 only)' + depends ADK_KPACKAGE_KMOD_IP_NF_FILTER + help + This option enables the old IPv4-only "ipt_ULOG" implementation + which has been obsoleted by the new "nfnetlink_log" code (see + CONFIG_NETFILTER_NETLINK_LOG). + + This option adds a `ULOG' target, which allows you to create rules in + any iptables table. The packet is passed to a userspace logging + daemon using netlink multicast sockets; unlike the LOG target + which can only be viewed through syslog. + + The appropriate userspace logging daemon (ulogd) may be obtained from + <http://www.gnumonks.org/projects/ulogd/> + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REDIRECT + tristate 'REDIRECT target support' + depends ADK_KPACKAGE_KMOD_IP_NF_NAT + help + REDIRECT is a special case of NAT: all incoming connections are + mapped onto the incoming interface's address, causing the packets to + come to the local machine instead of passing through. This is + useful for transparent proxies. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_NETMAP + tristate 'NETMAP target support' + depends ADK_KPACKAGE_KMOD_IP_NF_NAT + help + NETMAP is an implementation of static 1:1 NAT mapping of network + addresses. It maps the network address part, while keeping the host + address part intact. It is similar to Fast NAT, except that + Netfilter's connection tracking doesn't work well with Fast NAT. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_SAME + tristate 'SAME target support' + depends ADK_KPACKAGE_KMOD_IP_NF_NAT + help + This option adds a `SAME' target, which works like the standard SNAT + target, but attempts to give clients the same IP for all connections. + +config ADK_KPACKAGE_KMOD_IP_NF_MANGLE + tristate 'Packet mangling' + depends ADK_KPACKAGE_KMOD_IP_NF_IPTABLES + help + This option adds a `mangle' table to iptables: see the man page for + iptables(8). This table is used for various packet alterations + which can effect how the packet is routed. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ECN + tristate 'ECN target support' + depends ADK_KPACKAGE_KMOD_IP_NF_MANGLE + help + This option adds a `ECN' target, which can be used in the iptables mangle + table. + + You can use this target to remove the ECN bits from the IPv4 header of + an IP packet. This is particularly useful, if you need to work around + existing ECN blackholes on the internet, but don't want to disable + ECN support in general. + +config ADK_KPACKAGE_KMOD_IP_NF_TARGET_TTL + tristate 'TTL target support' + depends ADK_KPACKAGE_KMOD_IP_NF_MANGLE + help + This option adds a `TTL' target, which enables the user to modify + the TTL value of the IP header. + + While it is safe to decrement/lower the TTL, this target also enables + functionality to increment and set the TTL value of the IP header to + arbitrary values. This is EXTREMELY DANGEROUS since you can easily + create immortal packets that loop forever on the network. + +endmenu +endmenu diff --git a/target/linux/config/Config.in.network b/target/linux/config/Config.in.network new file mode 100644 index 000000000..724233ab3 --- /dev/null +++ b/target/linux/config/Config.in.network @@ -0,0 +1,232 @@ +menu "Network support" + +config ADK_KERNEL_INET + boolean + default y + +config ADK_KERNEL_IP_FIB_HASH + boolean + default y + +config ADK_KERNEL_SYN_COOKIES + boolean + default y + +config ADK_KERNEL_IP_PNP_BOOTP + boolean + default n + +config ADK_KERNEL_IP_PNP_RARP + boolean + default n + +config ADK_KERNEL_NET_IPGRE_BROADCAST + boolean + default n + +config ADK_KERNEL_PPP_ASYNC + boolean + default n + +config ADK_KERNEL_SLHC + boolean + default n + +config ADK_KERNEL_IMQ + tristate + default n + +config ADK_KERNEL_LLC + tristate + default n + +#config ADK_KPACKAGE_KMOD_ATM +# prompt "kmod-atm.......................... Asynchronous Transfer Mode (ATM)" +# tristate +# default n +# help +# ATM is a high-speed networking technology for Local Area Networks +# and Wide Area Networks. It uses a fixed packet size and is +# connection oriented, allowing for the negotiation of minimum +# bandwidth requirements. +# +# In order to participate in an ATM network, your Linux box needs an +# ATM networking card. If you have that, say Y here and to the driver +# of your ATM card below. +# +# Note that you need a set of user-space programs to actually make use +# of ATM. See the file <file:Documentation/networking/atm.txt> for +# further details. + +config ADK_KPACKAGE_KMOD_BRIDGE + prompt "kmod-net-bridge................... 802.1d Ethernet Bridging" + tristate + select ADK_KERNEL_LLC + default n + help + If you say Y here, then your Linux box will be able to act as an + Ethernet bridge, which means that the different Ethernet segments it + is connected to will appear as one Ethernet to the participants. + Several such bridges can work together to create even larger + networks of Ethernets using the IEEE 802.1 spanning tree algorithm. + As this is a standard, Linux bridges will cooperate properly with + other third party bridge products. + + In order to use the Ethernet bridge, you'll need the bridge + configuration tools; see <file:Documentation/networking/bridge.txt> + for location. Please read the Bridge mini-HOWTO for more + information. + + If you enable iptables support along with the bridge support then you + turn your bridge into a bridging IP firewall. + iptables will then see the IP packets being bridged, so you need to + take this into account when setting up your firewall rules. + Enabling arptables support when bridging will let arptables see + bridged ARP traffic in the arptables FORWARD chain. + +config ADK_KPACKAGE_KMOD_NET_IPIP + prompt "kmod-net-ipip..................... IP in IP encapsulation support" + tristate + default n + help + Tunneling means encapsulating data of one protocol type within + another protocol and sending it over a channel that understands the + encapsulating protocol. This particular tunneling driver implements + encapsulation of IP within IP, which sounds kind of pointless, but + can be useful if you want to make your (or some other) machine + appear on a different network than it physically is, or to use + mobile-IP facilities (allowing laptops to seamlessly move between + networks without changing their IP addresses). + + +config ADK_KPACKAGE_KMOD_NET_IPGRE + prompt "kmod-net-ipgre.................... GRE tunnels over IP" + tristate + #depends ADK_KPACKAGE_KMOD_NET_IPGRE_BROADCAST + default n + help + Tunneling means encapsulating data of one protocol type within + another protocol and sending it over a channel that understands the + encapsulating protocol. This particular tunneling driver implements + GRE (Generic Routing Encapsulation) and at this time allows + encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure. + This driver is useful if the other endpoint is a Cisco router: Cisco + likes GRE much better than the other Linux tunneling driver ("IP + tunneling" above). In addition, GRE allows multicast redistribution + through the tunnel. + +config ADK_KPACKAGE_KMOD_IPV6 + prompt "kmod-ipv6......................... IPv6 support" + tristate + depends ADK_IPV6 + default n + help + This is complemental support for the IP version 6. + You will still be able to do traditional IPv4 networking as well. + + For general information about IPv6, see + <http://playground.sun.com/pub/ipng/html/ipng-main.html>. + For Linux IPv6 development information, see <http://www.linux-ipv6.org>. + For specific information about IPv6 under Linux, read the HOWTO at + <http://www.bieringer.de/linux/IPv6/>. + +config ADK_KPACKAGE_KMOD_IPV6_SIT + prompt "kmod-ipv6-sit..................... IPv6-in-IPv4 tunnel (SIT driver)" + tristate + depends ADK_IPV6 + default n + help + Tunneling means encapsulating data of one protocol type within + another protocol and sending it over a channel that understands the + encapsulating protocol. This driver implements encapsulation of IPv6 + into IPv4 packets. This is useful if you want to connect two IPv6 + networks over an IPv4-only path. + +config ADK_KPACKAGE_KMOD_PPP + prompt "kmod-ppp.......................... PPP support" + tristate + select ADK_KERNEL_PPP_ASYNC + select ADK_KERNEL_SLHC + select ADK_KPACKAGE_KMOD_CRC_CCITT + default n + help + PPP (Point to Point Protocol) is a newer and better SLIP. It serves + the same purpose: sending Internet traffic over telephone (and other + serial) lines. Ask your access provider if they support it, because + otherwise you can't use it; most Internet access providers these + days support PPP rather than SLIP. + + To use PPP, you need an additional program called pppd as described + in the PPP-HOWTO, available at + <http://www.tldp.org/docs.html#howto>. Make sure that you have + the version of pppd recommended in <file:Documentation/Changes>. + The PPP option enlarges your kernel by about 16 KB. + + There are actually two versions of PPP: the traditional PPP for + asynchronous lines, such as regular analog phone lines, and + synchronous PPP which can be used over digital ISDN lines for + example. If you want to use PPP over phone lines or other + asynchronous serial lines, you need to say Y (or M) here and also to + the next option, "PPP support for async serial ports". For PPP over + synchronous lines, you should say Y (or M) here and to "Support + synchronous PPP", below. + +config ADK_KPACKAGE_KMOD_PPP_MPPE + prompt "kmod-ppp-mppe................... PPP MPPE/MPPC module" + tristate + default n + depends ADK_KPACKAGE_KMOD_PPP + select ADK_KERNEL_CRYPTO + select ADK_KPACKAGE_KMOD_CRYPTO_ARC4 + select ADK_KPACKAGE_KMOD_CRYPTO_SHA1 + select ADK_KPACKAGE_KMOD_CRYPTO_ECB if ADK_LINUX_2_6 + help + Support for the MPPE Encryption protocol, as employed by the + Microsoft Point-to-Point Tunneling Protocol. + + See http://pptpclient.sourceforge.net/ for information on + configuring PPTP clients and servers to utilize this method. + +#config ADK_KPACKAGE_KMOD_PPPOATM +# prompt "kmod-pppoatm.................... PPPoA (PPP over ATM) kernel support" +# tristate +# default n +# depends ADK_KPACKAGE_KMOD_PPP +# select ADK_KPACKAGE_KMOD_ATM +# help +# Support for PPP over ATM + +config ADK_KPACKAGE_KMOD_PPPOE + prompt "kmod-pppoe...................... PPPoE (PPP over Ethernet) kernel support" + tristate + default n + depends ADK_KPACKAGE_KMOD_PPP + help + Support for PPP over Ethernet + +config ADK_KPACKAGE_KMOD_TUN + prompt "kmod-tun.......................... Universal TUN/TAP driver" + tristate + default n + help + Kernel support for the TUN/TAP tunneling device + +config ADK_KPACKAGE_KMOD_BONDING + prompt "kmod-bonding...................... Bonding driver support" + tristate + default n + help + Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet + Channels together. This is called 'Etherchannel' by Cisco, + 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. + + The driver supports multiple bonding modes to allow for both high + performance and high availability operation. + + Refer to <file:Documentation/networking/bonding.txt> for more + information. + +source target/linux/config/Config.in.sched + +endmenu + diff --git a/target/linux/config/Config.in.nls b/target/linux/config/Config.in.nls new file mode 100644 index 000000000..e656fe7f9 --- /dev/null +++ b/target/linux/config/Config.in.nls @@ -0,0 +1,555 @@ +menu "Native Language support" + +config ADK_KERNEL_NLS_DEFAULT + string + default "iso8859-1" + +config ADK_KPACKAGE_KMOD_NLS + prompt "kmod-nls.......................... Base native language support" + tristate + default n + help + The base Native Language Support. A number of filesystems + depend on it (e.g. FAT, JOLIET, NT, BEOS filesystems), as well + as the ability of some filesystems to use native languages + (NCP, SMB). + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_437 + prompt "kmod-nls-codepage-437........... Codepage 437 (United States, Canada)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used in + the United States and parts of Canada. This is recommended. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_737 + prompt "kmod-nls-codepage-737........... Codepage 737 (Greek)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used for + Greek. If unsure, say N. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_775 + prompt "kmod-nls-codepage-775........... Codepage 775 (Baltic Rim)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used + for the Baltic Rim Languages (Latvian and Lithuanian). If unsure, + say N. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_850 + prompt "kmod-nls-codepage-850........... Codepage 850 (Western European Languages)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used for + much of Europe -- United Kingdom, Germany, Spain, Italy, and [add + more countries here]. It has some characters useful to many European + languages that are not part of the US codepage 437. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_852 + prompt "kmod-nls-codepage-852........... Codepage 852 (Eastern European Languages)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the Latin 2 codepage used by DOS + for much of Central and Eastern Europe. It has all the required + characters for these languages: Albanian, Croatian, Czech, English, + Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin + transcription), Slovak, Slovenian, and Sorbian. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_855 + prompt "kmod-nls-codepage-855........... Codepage 855 (Cyrillic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Cyrillic. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_857 + prompt "kmod-nls-codepage-857........... Codepage 857 (Turkish)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Turkish. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_860 + prompt "kmod-nls-codepage-860........... Codepage 860 (Portuguese)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Portuguese. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_861 + prompt "kmod-nls-codepage-861........... Codepage 861 (Icelandic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Icelandic. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_862 + prompt "kmod-nls-codepage-862........... Codepage 862 (Hebrew)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Hebrew. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_863 + prompt "kmod-nls-codepage-863........... Codepage 863 (French Canadian)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Canadian + French. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_864 + prompt "kmod-nls-codepage-864........... Codepage 864 (Arabic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Arabic. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_865 + prompt "kmod-nls-codepage-865........... Codepage 865 (Norwegian, Danish)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for the Nordic + European countries. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_866 + prompt "kmod-nls-codepage-866........... Codepage 866 (Cyrillic/Russian)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for + Cyrillic/Russian. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_869 + prompt "kmod-nls-codepage-869........... Codepage 869 (Greek)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Greek. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_874 + prompt "kmod-nls-codepage-874........... Codepage 874 (Thai)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Thai. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_932 + prompt "kmod-nls-codepage-932........... Codepage 932 (Japanese)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Shift-JIS + or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or + NLS Default value during kernel configuration, instead of 'cp932'. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_936 + prompt "kmod-nls-codepage-936........... Codepage 936 (Simplified Chinese)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Simplified + Chinese(GBK). + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_949 + prompt "kmod-nls-codepage-949........... Codepage 949 (Korean)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for UHC. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_950 + prompt "kmod-nls-codepage-950........... Codepage 950 (Traditional Chinese)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Traditional + Chinese(Big5). + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_1250 + prompt "kmod-nls-codepage-1250.......... Codepage 1250 (Slavic/Central European)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Windows CP-1250 + character set, which works for most Latin-written Slavic and Central + European languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, + Slovak, Slovene. + +config ADK_KPACKAGE_KMOD_NLS_CODEPAGE_1251 + prompt "kmod-nls-codepage-1251.......... Codepage 1251 (Bulgarian, Belarusian)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + The Microsoft FAT file system family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Russian and + Bulgarian and Belarusian. + +config ADK_KPACKAGE_KMOD_NLS_ASCII + prompt "kmod-nls-ascii.................. ASCII (United States)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + An ASCII NLS module is needed if you want to override the + DEFAULT NLS with this very basic charset and don't want any + non-ASCII characters to be translated. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_1 + prompt "kmod-nls-iso8859-1.............. NLS ISO 8859-1 (Latin-1; Western European Languages)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 1 character + set, which covers most West European languages such as Albanian, + Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German, + Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, + and Swedish. It is also the default for the US. If unsure, say Y. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_2 + prompt "kmod-nls-iso8859-2.............. NLS ISO 8859-2 (Latin-2; Central European Languages)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 2 character + set, which works for most Latin-written Slavic and Central European + languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, + Slovak, Slovene. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_3 + prompt "kmod-nls-iso8859-3.............. NLS ISO 8859-3 (Latin-3; Esperanto, Galician, Maltese, Turkish)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 3 character + set, which is popular with authors of Esperanto, Galician, Maltese, + and Turkish. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_4 + prompt "kmod-nls-iso8859-4.............. NLS ISO 8859-4 (Latin-4; old Baltic charset)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 4 character + set which introduces letters for Estonian, Latvian, and + Lithuanian. It is an incomplete predecessor of Latin 7. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_5 + prompt "kmod-nls-iso8859-5.............. NLS ISO 8859-5 (Cyrillic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-5, a Cyrillic + character set with which you can type Bulgarian, Belarusian, + Macedonian, Russian, Serbian, and Ukrainian. Note that the charset + KOI8-R is preferred in Russia. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_6 + prompt "kmod-nls-iso8859-6.............. NLS ISO 8859-6 (Arabic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-6, the Arabic + character set. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_7 + prompt "kmod-nls-iso8859-7.............. NLS ISO 8859-7 (Greek)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-7, the Modern + Greek character set. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_8 + prompt "kmod-nls-iso8859-8.............. NLS ISO 8859-8 (Hebrew)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-8, the Hebrew + character set. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_9 + prompt "kmod-nls-iso8859-9.............. NLS ISO 8859-9 (Latin-5; Turkish)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 5 character + set, and it replaces the rarely needed Icelandic letters in Latin 1 + with the Turkish ones. Useful in Turkey. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_13 + prompt "kmod-nls-iso8859-13............. NLS ISO 8859-13 (Latin-7; Baltic Rim)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 7 character + set, which supports modern Baltic languages including Latvian + and Lithuanian. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_14 + prompt "kmod-nls-iso8859-14............. NLS ISO 8859-14 (Latin-8; Celtic)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 8 character + set, which adds the last accented vowels for Welsh (aka Cymraeg) + (and Manx Gaelic) that were missing in Latin 1. + <http://linux.speech.cymru.org/> has further information. + +config ADK_KPACKAGE_KMOD_NLS_ISO8859_15 + prompt "kmod-nls-iso8859-15............. NLS ISO 8859-15 (Latin-9; Western European Languages with Euro)" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 9 character + set, which covers most West European languages such as Albanian, + Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish, + French, German, Galician, Irish, Icelandic, Italian, Norwegian, + Portuguese, Spanish, and Swedish. Latin 9 is an update to + Latin 1 (ISO 8859-1) that removes a handful of rarely used + characters and instead adds support for Estonian, corrects the + support for French and Finnish, and adds the new Euro character. + If unsure, say Y. + +config ADK_KPACKAGE_KMOD_NLS_KOI8_R + prompt "kmod-nls-koi8-r................. NLS KOI8-R (Cryllic for Russian and Bulgarian" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the preferred Russian + character set. + +config ADK_KPACKAGE_KMOD_NLS_KOI8_U + prompt "kmod-nls-koi8-u................. NLS KOI8-U (Cyrillic for Russian, Bulgarian and Ukrainian" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the preferred Ukrainian + (koi8-u) and Belarusian (koi8-ru) character sets. + +config ADK_KPACKAGE_KMOD_NLS_UTF8 + prompt "kmod-nls-utf8................... NLS UTF8" + tristate + default n + depends ADK_KPACKAGE_KMOD_NLS + help + If you want to display filenames with native language characters + from the Microsoft FAT file system family or from JOLIET CD-ROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the UTF-8 encoding of + the Unicode/ISO9646 universal character set. + +endmenu + diff --git a/target/linux/config/Config.in.pcmcia b/target/linux/config/Config.in.pcmcia new file mode 100644 index 000000000..f06ad0783 --- /dev/null +++ b/target/linux/config/Config.in.pcmcia @@ -0,0 +1,32 @@ +menu "PCMCIA/CardBus support" + +config ADK_KERNEL_CARDBUS + boolean + default n + +config ADK_KPACKAGE_KMOD_PCCARD + prompt "kmod-pccard....................... PCCARD support" + tristate + default n + +config ADK_KPACKAGE_KMOD_PCMCIA + prompt "kmod-pcmcia....................... 16-bit PCMCIA support" + tristate + depends ADK_KPACKAGE_KMOD_PCCARD + select ADK_KERNEL_CRC32 + default n + +config ADK_KPACKAGE_KMOD_YENTA + prompt "kmod-cardbus...................... 32-bit CardBus support" + tristate + depends ADK_KPACKAGE_KMOD_PCCARD + select ADK_KERNEL_CARDBUS + default n + +config ADK_KPACKAGE_KMOD_SERIAL_8250_CS + prompt "kmod-pcmcia-serial................ PCMCIA/CardBus serial device support" + tristate + default n + depends on ADK_KPACKAGE_KMOD_PCMCIA || ADK_KPACKAGE_KMOD_CARDBUS + +endmenu diff --git a/target/linux/config/Config.in.sched b/target/linux/config/Config.in.sched new file mode 100644 index 000000000..c5a992ba4 --- /dev/null +++ b/target/linux/config/Config.in.sched @@ -0,0 +1,337 @@ +menu "QoS and/or fair queueing" + +config ADK_KERNEL_NET_SCH_CSZ + boolean + default n + +config ADK_KERNEL_NET_SCH_NETEM + boolean + default n + +config ADK_KERNEL_NET_QOS + boolean + default n + +config ADK_KERNEL_NET_ESTIMATOR + boolean + default n + +config ADK_KERNEL_NET_SCHED + #prompt "kmod-net-sched.................... QoS and/or fair queueing support" + boolean + default n + help + When the kernel has several packets to send out over a network + device, it has to decide which ones to send first, which ones to + delay, and which ones to drop. This is the job of the queueing + disciplines, several different algorithms for how to do this + "fairly" have been proposed. + + If you say N here, you will get the standard packet scheduler, which + is a FIFO (first come, first served). If you say Y here, you will be + able to choose from among several alternative algorithms which can + then be attached to different network devices. This is useful for + example if some of your network devices are real time devices that + need a certain minimum data flow rate, or if you need to limit the + maximum data flow rate for traffic which matches specified criteria. + This code is considered to be experimental. + + To administer these schedulers, you'll need the user-level utilities + from the package iproute2+tc at <ftp://ftp.tux.org/pub/net/ip-routing/>. + That package also contains some documentation; for more, check out + <http://linux-net.osdl.org/index.php/Iproute2>. + + This Quality of Service (QoS) support will enable you to use + Differentiated Services (diffserv) and Resource Reservation Protocol + (RSVP) on your Linux router if you also say Y to the corresponding + classifiers below. Documentation and software is at + <http://diffserv.sourceforge.net/>. + +comment "Queueing/Scheduling" + +config ADK_KPACKAGE_KMOD_NET_SCH_CBQ + prompt "kmod-sched-cbq.................... Class Based Queueing (CBQ)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Class-Based Queueing (CBQ) packet + scheduling algorithm. This algorithm classifies the waiting packets + into a tree-like hierarchy of classes; the leaves of this tree are + in turn scheduled by separate algorithms. + + See the top of <file:net/sched/sch_cbq.c> for more details. + + CBQ is a commonly used scheduler, so if you're unsure, you should + say Y here. Then say Y to all the queueing algorithms below that you + want to use as leaf disciplines. + +config ADK_KPACKAGE_KMOD_NET_SCH_HTB + prompt "kmod-sched-htb.................... Hierarchical Token Bucket (HTB)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Hierarchical Token Buckets (HTB) + packet scheduling algorithm. See + <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and + in-depth articles. + + HTB is very similar to CBQ regarding its goals however is has + different properties and different algorithm. + +config ADK_KPACKAGE_KMOD_NET_SCH_HFSC + prompt "kmod-sched-hfsc................... Hierarchical Fair Service Curve (HFSC)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Hierarchical Fair Service Curve + (HFSC) packet scheduling algorithm. + +config ADK_KPACKAGE_KMOD_NET_SCH_ATM + prompt "kmod-sched-atm.................... ATM Virtual Circuits (ATM)" + tristate + depends ADK_KPACKAGE_KMOD_ATM + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the ATM pseudo-scheduler. This + provides a framework for invoking classifiers, which in turn + select classes of this queuing discipline. Each class maps + the flow(s) it is handling to a given virtual circuit. + + See the top of <file:net/sched/sch_atm.c>) for more details. + +config ADK_KPACKAGE_KMOD_NET_SCH_PRIO + prompt "kmod-sched-prio................... Multi Band Priority Queueing (PRIO)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use an n-band priority queue packet + scheduler. + +config ADK_KPACKAGE_KMOD_NET_SCH_RED + prompt "kmod-sched-red.................... Random Early Detection (RED)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Random Early Detection (RED) + packet scheduling algorithm. + + See the top of <file:net/sched/sch_red.c> for more details. + +config ADK_KPACKAGE_KMOD_NET_SCH_SFQ + prompt "kmod-sched-sfq.................... Stochastic Fairness Queueing (SFQ)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) + packet scheduling algorithm . + + See the top of <file:net/sched/sch_sfq.c> for more details. + +#config ADK_KPACKAGE_KMOD_NET_SCH_TEQL +# prompt "kmod-sched-teql................... True Link Equalizer (TEQL)" +# tristate +# select ADK_KERNEL_NET_SCHED +# default n +# help +# Say Y here if you want to use the True Link Equalizer (TLE) packet +# scheduling algorithm. This queueing discipline allows the combination +# of several physical devices into one virtual device. +# +# See the top of <file:net/sched/sch_teql.c> for more details. + +config ADK_KPACKAGE_KMOD_NET_SCH_TBF + prompt "kmod-sched-tbf.................... Token Bucket Filter (TBF)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Token Bucket Filter (TBF) packet + scheduling algorithm. + + See the top of <file:net/sched/sch_tbf.c> for more details. + +config ADK_KPACKAGE_KMOD_NET_SCH_GRED + prompt "kmod-sched-gred................... Generic Random Early Detection (GRED)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y here if you want to use the Generic Random Early Detection + (GRED) packet scheduling algorithm for some of your network devices + (see the top of <file:net/sched/sch_red.c> for details and + references about the algorithm). + +config ADK_KPACKAGE_KMOD_NET_SCH_DSMARK + prompt "kmod-sched-dsmark................. Differentiated Services marker (DSMARK)" + tristate + select ADK_KERNEL_NET_SCHED + default n + help + Say Y if you want to schedule packets according to the + Differentiated Services architecture proposed in RFC 2475. + Technical information on this method, with pointers to associated + RFCs, is available at <http://www.gta.ufrj.br/diffserv/>. + +config ADK_KPACKAGE_KMOD_NET_SCH_INGRESS + prompt "kmod-sched-ingress................ Ingress Qdisc" + tristate + select ADK_KERNEL_NET_SCHED + select ADK_KERNEL_NETFILTER + select ADK_KERNEL_NET_CLS_ACT + default n + help + Say Y here if you want to use classifiers for incoming packets. + If unsure, say Y. + +comment "Classification" + +config ADK_KERNEL_NET_CLS + boolean + select ADK_KERNEL_NET_SCHED + default n + +config ADK_KPACKAGE_KMOD_NET_CLS_BASIC + prompt "kmod-cls-basic.................... Elementary classification (BASIC)" + tristate + select ADK_KERNEL_NET_CLS + depends on ADK_LINUX_2_6 + default n + help + Say Y here if you want to be able to classify packets using + only extended matches and actions. + +config ADK_KPACKAGE_KMOD_NET_CLS_TCINDEX + prompt "kmod-cls-tcindex.................. Traffic-Control Index (TCINDEX)" + tristate + select ADK_KERNEL_NET_CLS + default n + help + Say Y here if you want to be able to classify packets based on + traffic control indices. You will want this feature if you want + to implement Differentiated Services together with DSMARK. + +config ADK_KPACKAGE_KMOD_NET_CLS_ROUTE4 + prompt "kmod-cls-route4................... Routing decision (ROUTE)" + tristate + select ADK_KERNEL_NET_CLS + default n + help + If you say Y here, you will be able to classify packets + according to the route table entry they matched. + +config ADK_KPACKAGE_KMOD_NET_CLS_FW + prompt "kmod-cls-fw....................... Netfilter mark (FW)" + tristate + select ADK_KERNEL_NET_CLS + default n + help + If you say Y here, you will be able to classify packets + according to netfilter/firewall marks. + +config ADK_KPACKAGE_KMOD_NET_CLS_U32 + prompt "kmod-cls-u32...................... Universal 32bit comparisons w/ hashing (U32)" + tristate + select ADK_KERNEL_NET_CLS + default n + help + Say Y here to be able to classify packets using a universal + 32bit pieces based comparison scheme. + +config ADK_KPACKAGE_KMOD_NET_CLS_U32_PERF + prompt ".................................. Performance counters support" + bool + select ADK_KERNEL_NET_CLS + depends ADK_KPACKAGE_KMOD_NET_CLS_U32 + default n + help + Say Y here to make u32 gather additional statistics useful for + fine tuning u32 classifiers. + +config ADK_KPACKAGE_KMOD_NET_CLS_U32_MARK + prompt ".................................. Netfilter marks support" + bool + select ADK_KERNEL_NET_CLS + depends ADK_KPACKAGE_KMOD_NET_CLS_U32 + depends ADK_KPACKAGE_KMOD_NET_CLS_FW + default n + help + Say Y here to be able to use netfilter marks as u32 key. + +comment "Actions" + +config ADK_KERNEL_NET_CLS_ACT + boolean + select ADK_KERNEL_NET_SCHED + select ADK_KERNEL_NET_ESTIMATOR + default n + +config ADK_KPACKAGE_KMOD_NET_CLS_POLICE + prompt "kmod-act-police................... Traffic Policing" + tristate + select ADK_KERNEL_NET_CLS_ACT + depends ADK_LINUX_2_4 + default n + help + Say Y here if you want to do traffic policing, i.e. strict + bandwidth limiting. This action replaces the existing policing + module. + +config ADK_KPACKAGE_KMOD_NET_ACT_POLICE + prompt "kmod-act-police................... Traffic Policing" + tristate + select ADK_KERNEL_NET_CLS_ACT + depends ADK_LINUX_2_6 + default n + help + Say Y here if you want to do traffic policing, i.e. strict + bandwidth limiting. This action replaces the existing policing + module. + +config ADK_KPACKAGE_KMOD_NET_ACT_GACT + prompt "kmod-act-gact..................... Generic actions" + tristate + select ADK_KERNEL_NET_CLS_ACT + depends ADK_LINUX_2_6 + default n + help + Say Y here to take generic actions such as dropping and + accepting packets. + +config ADK_KPACKAGE_KMOD_NET_ACT_MIRRED + prompt "kmod-act-mirred................... Redirecting and Mirroring" + tristate + select ADK_KERNEL_NET_CLS_ACT + depends ADK_LINUX_2_6 + default n + help + Say Y here to allow packets to be mirrored or redirected to + other devices. + +config ADK_KPACKAGE_KMOD_NET_ACT_IPT + prompt "kmod-act-ipt...................... IPtables targets" + tristate + select ADK_KERNEL_NET_CLS_ACT + select ADK_KPACKAGE_KMOD_IP_NF_IPTABLES + depends ADK_LINUX_2_6 + default n + help + Say Y here to be able to invoke iptables targets after successful + classification. + +config ADK_KPACKAGE_KMOD_NET_ACT_PEDIT + prompt "kmod-act-pedit.................... Packet Editing" + tristate + select ADK_KERNEL_NET_CLS_ACT + depends ADK_LINUX_2_6 + default n + help + Say Y here if you want to mangle the content of packets. + +endmenu diff --git a/target/linux/config/Config.in.usb b/target/linux/config/Config.in.usb new file mode 100644 index 000000000..b3dfa9cbd --- /dev/null +++ b/target/linux/config/Config.in.usb @@ -0,0 +1,264 @@ +menu "USB support" + +config ADK_KERNEL_USB_DEVICEFS + boolean + default n + +config ADK_KERNEL_USB_LIBUSUAL + tristate + default n + +config ADK_KERNEL_USB_SERIAL + boolean + default n + +config ADK_KPACKAGE_KMOD_USB + prompt "kmod-usb-core..................... USB support" + tristate + default y if ADK_LINUX_X86_ALIX1C || ADK_LINUX_CRIS_FOXBOARD + default n + select ADK_KERNEL_USB_DEVICEFS + help + Universal Serial Bus (USB) is a specification for a serial bus + subsystem which offers higher speeds and more features than the + traditional PC serial port. The bus supplies power to peripherals + and allows for hot swapping. Up to 127 USB peripherals can be + connected to a single USB host in a tree structure. + + The USB host is the root of the tree, the peripherals are the + leaves and the inner nodes are special USB devices called hubs. + Most PCs now have USB host ports, used to connect peripherals + such as scanners, keyboards, mice, modems, cameras, disks, + flash memory, network links, and printers to the PC. + + Say Y here if your computer has a host-side USB port and you want + to use USB devices. You then need to say Y to at least one of the + Host Controller Driver (HCD) options below. Choose a USB 1.1 + controller, such as "UHCI HCD support" or "OHCI HCD support", + and "EHCI HCD (USB 2.0) support" except for older systems that + do not have USB 2.0 support. It doesn't normally hurt to select + them all if you are not certain. + + If your system has a device-side USB port, used in the peripheral + side of the USB protocol, see the "USB Gadget" framework instead. + + After choosing your HCD, then select drivers for the USB peripherals + you'll be using. You may want to check out the information provided + in <file:Documentation/usb/> and especially the links given in + <file:Documentation/usb/usb-help.txt>. + +config ADK_KPACKAGE_KMOD_USB_UHCI_HCD + prompt "kmod-usb-uhci................... Support for UHCI controllers" + tristate + depends ADK_KPACKAGE_KMOD_USB + depends !ADK_LINUX_CRIS_FOXBOARD + select ADK_PACKAGE_KMOD_USB_CONTROLLER + help + The Universal Host Controller Interface is a standard by Intel for + accessing the USB hardware in the PC (which is also called the USB + host controller). If your USB host controller conforms to this + standard, you may want to say Y, but see below. All recent boards + with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX, + i810, i820) conform to this standard. Also all VIA PCI chipsets + (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro + 133). If unsure, say Y. + +config ADK_KPACKAGE_KMOD_USB_OHCI_HCD + prompt "kmod-usb-ohci................... Support for OHCI controllers" + tristate + default y if ADK_LINUX_X86_ALIX1C + default n + depends !ADK_LINUX_CRIS_FOXBOARD + depends ADK_KPACKAGE_KMOD_USB + select ADK_PACKAGE_KMOD_USB_CONTROLLER + help + The Open Host Controller Interface (OHCI) is a standard for accessing + USB 1.1 host controller hardware. It does more in hardware than Intel's + UHCI specification. If your USB host controller follows the OHCI spec, + say Y. On most non-x86 systems, and on x86 hardware that's not using a + USB controller from Intel or VIA, this is appropriate. If your host + controller doesn't use PCI, this is probably appropriate. For a PCI + based system where you're not sure, the "lspci -v" entry will list the + right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI. + +config ADK_KPACKAGE_KMOD_USB_ISP116X_HCD + prompt "kmod-usb-isp116x................ ISP116X HCD support" + tristate + default n + depends !ADK_LINUX_CRIS_FOXBOARD + depends on ADK_KPACKAGE_KMOD_USB + select ADK_PACKAGE_KMOD_USB_CONTROLLER + help + The ISP1160 and ISP1161 chips are USB host controllers. Enable this + option if your board has this chip. If unsure, say N. + + This driver does not support isochronous transfers. + +config ADK_KPACKAGE_KMOD_USB_SL811_HCD + prompt "kmod-usb-sl811.................. SL811HS HCD support" + tristate + default n + depends !ADK_LINUX_CRIS_FOXBOARD + depends on ADK_KPACKAGE_KMOD_USB + select ADK_PACKAGE_KMOD_USB_CONTROLLER + help + The SL811HS is a single-port USB controller that supports either + host side or peripheral side roles. Enable this option if your + board has this chip, and you want to use it as a host controller. + If unsure, say N. + + +config ADK_KPACKAGE_KMOD_USB_EHCI_HCD + prompt "kmod-usb-ehci................... Support for USB 2.0 controllers" + tristate + depends !ADK_LINUX_CRIS_FOXBOARD + default y if ADK_LINUX_X86_ALIX1C + default n + depends ADK_KPACKAGE_KMOD_USB + select ADK_PACKAGE_KMOD_USB_CONTROLLER + help + The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0 + "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware. + If your USB host controller supports USB 2.0, you will likely want to + configure this Host Controller Driver. At the time of this writing, + the primary implementation of EHCI is a chip from NEC, widely available + in add-on PCI cards, but implementations are in the works from other + vendors including Intel and Philips. Motherboard support is appearing. + + EHCI controllers are packaged with "companion" host controllers (OHCI + or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports + will connect to EHCI if the device is high speed, otherwise they + connect to a companion controller. If you configure EHCI, you should + probably configure the OHCI (for NEC and some other vendors) USB Host + Controller Driver or UHCI (for Via motherboards) Host Controller + Driver too. + + You may want to read <file:Documentation/usb/ehci.txt>. + +config ADK_PACKAGE_KMOD_USB_CONTROLLER + tristate + depends on ADK_KPACKAGE_KMOD_USB_UHCI_HCD || ADK_KPACKAGE_KMOD_USB_OHCI_HCD || ADK_KPACKAGE_KMOD_EHCI_HCD || ADK_LINUX_CRIS_FOXBOARD + select ADK_KERNEL_USB_DEVICEFS + default n + +config ADK_KPACKAGE_KMOD_USB_ACM + prompt "kmod-usb-acm...................... Support for USB modems/isdn controllers" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +config ADK_KPACKAGE_KMOD_USB_PEGASUS + prompt "kmod-usb-pegasus.................. Support for USB Pegasus" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +config ADK_KPACKAGE_KMOD_USB_PRINTER + prompt "kmod-usb-printer.................. Support for USB printers" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +config ADK_KPACKAGE_KMOD_USB_SERIAL + prompt "kmod-usb-serial................... Support for USB-to-serial converters" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + help + Say Y here if you have a USB device that provides normal serial + ports, or acts like a serial device, and you want to connect it to + your USB bus. + + Please read <file:Documentation/usb/usb-serial.txt> for more + information on the specifics of the different devices that are + supported, and on how to use them. + + +config ADK_KPACKAGE_KMOD_USB_SERIAL_BELKIN + prompt "kmod-usb-serial-belkin.......... Support for Belkin USB-to-serial converters" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_SERIAL + help + Say Y here if you want to use a Belkin USB Serial single port + adaptor (F5U103 is one of the model numbers) or the Peracom single + port USB to serial adapter. + +config ADK_KPACKAGE_KMOD_USB_SERIAL_FTDI_SIO + prompt "kmod-usb-serial-ftdi............ Support for FTDI USB-to-serial converter" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_SERIAL + help + Say Y here if you want to use a FTDI SIO single port USB to serial + converter device. The implementation I have is called the USC-1000. + This driver has also be tested with the 245 and 232 devices. + + See <http://ftdi-usb-sio.sourceforge.net/> for more + information on this driver and the device. + +config ADK_KPACKAGE_KMOD_USB_SERIAL_MCT_U232 + prompt "kmod-usb-serial-mct-u232........ Support for Magic Control Technology USB-to-Serial converters" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_SERIAL + help + Say Y here if you want to use a USB Serial single port adapter from + Magic Control Technology Corp. (U232 is one of the model numbers). + + This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB + BAY, Belkin F5U109, and Belkin F5U409 devices. + +config ADK_KPACKAGE_KMOD_USB_SERIAL_PL2303 + prompt "kmod-usb-serial-pl2303.......... Support for Prolific PL2303 USB-to-Serial converters" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_SERIAL + help + Say Y here if you want to use the PL2303 USB Serial single port + adapter from Prolific. + +config ADK_KPACKAGE_KMOD_USB_SERIAL_VISOR + prompt "kmod-usb-serial-visor........... Support for Handspring Visor / Palm m50x / Sony Clie Driver" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_SERIAL + help + Say Y here if you want to connect to your HandSpring Visor, Palm + m500 or m505 through its USB docking station. See + <http://usbvisor.sourceforge.net/> for more information on using this + driver. + +config ADK_KPACKAGE_KMOD_USB_STORAGE + prompt "kmod-usb-storage.................. Support for USB storage devices" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + select ADK_KPACKAGE_KMOD_SCSI if !ADK_KERNEL_SCSI + select ADK_KPACKAGE_KMOD_BLK_DEV_SD if !ADK_KERNEL_SCSI + +config ADK_KPACKAGE_KMOD_USB_ATM + prompt "kmod-usb-atm...................... Support for USB ATM devices" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +config ADK_KPACKAGE_KMOD_USB_ATM_SPEEDTOUCH + prompt "kmod-usb-atm-speedtouch......... Support for USB Speedtouch ADSL modem" + tristate + default n + depends ADK_KPACKAGE_KMOD_USB_ATM + +config ADK_KPACKAGE_KMOD_USB_USBNET + prompt "kmod-usb-usbnet................... Multi-purpose USB Networking Framework" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +config ADK_KPACKAGE_KMOD_USB_SISUSBVGA + prompt "kmod-usb-svga..................... USB 2.0 SVGA dongle support (Net2280/SiS315)" + tristate + default n + depends ADK_PACKAGE_KMOD_USB_CONTROLLER + +endmenu |