1.1 --- a/.hg-to-bk	Tue Jan 06 17:57:55 2004 +0000
     1.2 +++ b/.hg-to-bk	Mon Jan 12 08:53:30 2004 +0000
     1.3 @@ -1,5 +1,5 @@
     1.4  #!/bin/sh -x
     1.5  set -e
     1.6 -ln -s xenolinux-2.4.23-sparse xenolinux-sparse
     1.7 +ln -s xenolinux-2.4.24-sparse xenolinux-sparse
     1.8  (find -depth -type d -print | xargs -r rmdir 2>/dev/null) || true
     1.9  exit 0

     2.1 --- a/.rootkeys	Tue Jan 06 17:57:55 2004 +0000
     2.2 +++ b/.rootkeys	Mon Jan 12 08:53:30 2004 +0000
     2.3 @@ -490,87 +490,87 @@ 3eb3c87fPL2T_zBb0bHlbZY-ACEKRw xen/tools
     2.4  3eb3c87fmKYTC5GCh_rydFakZp9ayw xen/tools/figlet/README
     2.5  3eb3c87fdQKQ5OBGbM-KjZfi9Us4ng xen/tools/figlet/figlet.c
     2.6  3eb3c87fS7DNbg0i6yhFs28UIqAK5g xen/tools/figlet/xen.flf
     2.7 -3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.23-sparse/Documentation/Configure.help
     2.8 -3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.23-sparse/Makefile
     2.9 -3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.23-sparse/arch/xeno/Makefile
    2.10 -3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.23-sparse/arch/xeno/boot/Makefile
    2.11 -3e5a4e65OV_j_DBtjzt5vej771AJsA xenolinux-2.4.23-sparse/arch/xeno/config.in
    2.12 -3e5a4e65TNEycLeXqPSXQJQm_xGecA xenolinux-2.4.23-sparse/arch/xeno/defconfig
    2.13 -3e6377f5xwPfYZkPHPrDbEq1PRN7uQ xenolinux-2.4.23-sparse/arch/xeno/drivers/balloon/Makefile
    2.14 -3e6377f8Me8IqtvEhb70XFgOvqQH7A xenolinux-2.4.23-sparse/arch/xeno/drivers/balloon/balloon.c
    2.15 -3e5a4e65iHEuC5sjFhj42XALYbLVRw xenolinux-2.4.23-sparse/arch/xeno/drivers/block/Makefile
    2.16 -3e5a4e65pP5spJErBW69pJxSSdK9RA xenolinux-2.4.23-sparse/arch/xeno/drivers/block/xl_block.c
    2.17 -3e67f822FOPwqHiaRKbrskgWgoNL5g xenolinux-2.4.23-sparse/arch/xeno/drivers/block/xl_block.h
    2.18 -3e676eb5RXnHzSHgA1BvM0B1aIm4qg xenolinux-2.4.23-sparse/arch/xeno/drivers/block/xl_vbd.c
    2.19 -3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ xenolinux-2.4.23-sparse/arch/xeno/drivers/console/Makefile
    2.20 -3e5a4e651TH-SXHoufurnWjgl5bfOA xenolinux-2.4.23-sparse/arch/xeno/drivers/console/console.c
    2.21 -3e5a4e656nfFISThfbyXQOA6HN6YHw xenolinux-2.4.23-sparse/arch/xeno/drivers/dom0/Makefile
    2.22 -3e5a4e65BXtftInNHUC2PjDfPhdZZA xenolinux-2.4.23-sparse/arch/xeno/drivers/dom0/dom0_core.c
    2.23 -3e5a4e65gfn_ltB8ujHMVFApnTTNRQ xenolinux-2.4.23-sparse/arch/xeno/drivers/dom0/vfr.c
    2.24 -3e5a4e65gZBRBB6RsSVg1c9iahigAw xenolinux-2.4.23-sparse/arch/xeno/drivers/network/Makefile
    2.25 -3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ xenolinux-2.4.23-sparse/arch/xeno/drivers/network/network.c
    2.26 -3e5a4e65lWzkiPXsZdzPt2RNnJGG1g xenolinux-2.4.23-sparse/arch/xeno/kernel/Makefile
    2.27 -3e5a4e65_hqfuxtGG8IUy6wRM86Ecg xenolinux-2.4.23-sparse/arch/xeno/kernel/entry.S
    2.28 -3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg xenolinux-2.4.23-sparse/arch/xeno/kernel/head.S
    2.29 -3e5a4e65ibVQmwlOn0j3sVH_j_6hAg xenolinux-2.4.23-sparse/arch/xeno/kernel/hypervisor.c
    2.30 -3e5a4e65RMGcuA-HCn3-wNx3fFQwdg xenolinux-2.4.23-sparse/arch/xeno/kernel/i386_ksyms.c
    2.31 -3e5a4e65MEvZhlr070sK5JsfAQlv7Q xenolinux-2.4.23-sparse/arch/xeno/kernel/ioport.c
    2.32 -3e5a4e653U6cELGv528IxOLHvCq8iA xenolinux-2.4.23-sparse/arch/xeno/kernel/irq.c
    2.33 -3e5a4e65muT6SU3ck47IP87Q7Ti5hA xenolinux-2.4.23-sparse/arch/xeno/kernel/ldt.c
    2.34 -3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ xenolinux-2.4.23-sparse/arch/xeno/kernel/process.c
    2.35 -3e5a4e66tR-qJMLj3MppcKqmvuI2XQ xenolinux-2.4.23-sparse/arch/xeno/kernel/setup.c
    2.36 -3e5a4e66fWSTagLGU2P8BGFGRjhDiw xenolinux-2.4.23-sparse/arch/xeno/kernel/signal.c
    2.37 -3e5a4e66N__lUXNwzQ-eADRzK9LXuQ xenolinux-2.4.23-sparse/arch/xeno/kernel/time.c
    2.38 -3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ xenolinux-2.4.23-sparse/arch/xeno/kernel/traps.c
    2.39 -3e5a4e66-9_NczrVMbuQkoSLyXckIw xenolinux-2.4.23-sparse/arch/xeno/lib/Makefile
    2.40 -3e5a4e6637ZDk0BvFEC-aFQs599-ng xenolinux-2.4.23-sparse/arch/xeno/lib/delay.c
    2.41 -3f68905cF5i8-NYpIhGjKmh0y8Gu5g xenolinux-2.4.23-sparse/arch/xeno/lib/xeno_proc.c
    2.42 -3e5a4e66croVgpcJyJuF2ycQw0HuJw xenolinux-2.4.23-sparse/arch/xeno/mm/Makefile
    2.43 -3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg xenolinux-2.4.23-sparse/arch/xeno/mm/fault.c
    2.44 -3e5a4e668SE9rixq4ahho9rNhLUUFQ xenolinux-2.4.23-sparse/arch/xeno/mm/hypervisor.c
    2.45 -3e5a4e661gLzzff25pJooKIIWe7IWg xenolinux-2.4.23-sparse/arch/xeno/mm/init.c
    2.46 -3f0bed43UUdQichXAiVNrjV-y2Kzcg xenolinux-2.4.23-sparse/arch/xeno/mm/ioremap.c
    2.47 -3e5a4e66qRlSTcjafidMB6ulECADvg xenolinux-2.4.23-sparse/arch/xeno/vmlinux.lds
    2.48 -3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.23-sparse/drivers/block/ll_rw_blk.c
    2.49 -3f108aeaLcGDgQdFAANLTUEid0a05w xenolinux-2.4.23-sparse/drivers/char/mem.c
    2.50 -3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.23-sparse/drivers/char/tty_io.c
    2.51 -3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.23-sparse/fs/exec.c
    2.52 -3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.23-sparse/include/asm-xeno/bugs.h
    2.53 -3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.23-sparse/include/asm-xeno/desc.h
    2.54 -3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.23-sparse/include/asm-xeno/fixmap.h
    2.55 -3e5a4e67w_DWgjIJ17Tlossu1LGujQ xenolinux-2.4.23-sparse/include/asm-xeno/highmem.h
    2.56 -3e5a4e67YtcyDLQsShhCfQwPSELfvA xenolinux-2.4.23-sparse/include/asm-xeno/hw_irq.h
    2.57 -3e5a4e677VBavzM1UZIEcH1B-RlXMA xenolinux-2.4.23-sparse/include/asm-xeno/hypervisor.h
    2.58 -3e5a4e673p7PEOyHFm3nHkYX6HQYBg xenolinux-2.4.23-sparse/include/asm-xeno/irq.h
    2.59 -3ead095db_LRUXnxaqs0dA1DWhPoQQ xenolinux-2.4.23-sparse/include/asm-xeno/keyboard.h
    2.60 -3e5a4e678ddsQOpbSiRdy1GRcDc9WA xenolinux-2.4.23-sparse/include/asm-xeno/mmu_context.h
    2.61 -3f8707e7ZmZ6TxyX0ZUEfvhA2Pb_xQ xenolinux-2.4.23-sparse/include/asm-xeno/msr.h
    2.62 -3e7270deQqtGPSnFxcW4AvJZuTUWfg xenolinux-2.4.23-sparse/include/asm-xeno/multicall.h
    2.63 -3e5a4e67mnQfh-R8KcQCaVo2Oho6yg xenolinux-2.4.23-sparse/include/asm-xeno/page.h
    2.64 -3e5a4e67uTYU5oEnIDjxuaez8njjqg xenolinux-2.4.23-sparse/include/asm-xeno/pgalloc.h
    2.65 -3e5a4e67X7JyupgdYkgDX19Huj2sAw xenolinux-2.4.23-sparse/include/asm-xeno/pgtable-2level.h
    2.66 -3e5a4e67gr4NLGtQ5CvSLimMYZlkOA xenolinux-2.4.23-sparse/include/asm-xeno/pgtable.h
    2.67 -3f108af1qNv8DVSGPv4zpqIU1txCkg xenolinux-2.4.23-sparse/include/asm-xeno/proc_cmd.h
    2.68 -3e5a4e676uK4xErTBDH6XJREn9LSyg xenolinux-2.4.23-sparse/include/asm-xeno/processor.h
    2.69 -3e5a4e67AJPjW-zL7p-xWuA6IVeH1g xenolinux-2.4.23-sparse/include/asm-xeno/ptrace.h
    2.70 -3e5a4e68uJz-xI0IBVMD7xRLQKJDFg xenolinux-2.4.23-sparse/include/asm-xeno/segment.h
    2.71 -3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA xenolinux-2.4.23-sparse/include/asm-xeno/smp.h
    2.72 -3fa8e3f0kBLeE4To2vpdi3cpJbIkbQ xenolinux-2.4.23-sparse/include/asm-xeno/suspend.h
    2.73 -3e5a4e68mTr0zcp9SXDbnd-XLrrfxw xenolinux-2.4.23-sparse/include/asm-xeno/system.h
    2.74 -3f1056a9L_kqHcFheV00KbKBzv9j5w xenolinux-2.4.23-sparse/include/asm-xeno/vga.h
    2.75 -3f689063nhrIRsMMZjZxMFk7iEINqQ xenolinux-2.4.23-sparse/include/asm-xeno/xeno_proc.h
    2.76 -3f056927gMHl7mWB89rb73JahbhQIA xenolinux-2.4.23-sparse/include/linux/blk.h
    2.77 -3e5a4e68WLX3B8owTvktP3HHOtznPQ xenolinux-2.4.23-sparse/include/linux/major.h
    2.78 -3e5a4e686V0nioX2ZpFf056sgvdiQw xenolinux-2.4.23-sparse/include/linux/sunrpc/debug.h
    2.79 -3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ xenolinux-2.4.23-sparse/init/do_mounts.c
    2.80 -3e5a4e68TJJavrunYwTAnLRSBxSYqQ xenolinux-2.4.23-sparse/kernel/panic.c
    2.81 -3f1056a9LXNTgSzITNh1mb-MIKV1Ng xenolinux-2.4.23-sparse/kernel/printk.c
    2.82 -3f9d4b44247udoqWEgFkaHiWv6Uvyg xenolinux-2.4.23-sparse/kernel/time.c
    2.83 -3eba8f878XjouY21EkQBXwYBsPsipQ xenolinux-2.4.23-sparse/lndir-rel
    2.84 -3e6e7c1efbQe93xCvOpOVCnXTMmQ5w xenolinux-2.4.23-sparse/mkbuildtree
    2.85 -3e5a4e68GxCIaFH4sy01v1wjapetaA xenolinux-2.4.23-sparse/mm/memory.c
    2.86 -3f108af5VxPkLv13tXpXgoRKALQtXQ xenolinux-2.4.23-sparse/mm/mprotect.c
    2.87 -3e5a4e681xMPdF9xCMwpyfuYMySU5g xenolinux-2.4.23-sparse/mm/mremap.c
    2.88 -3e5a4e683HKVU-sxtagrDasRB8eBVw xenolinux-2.4.23-sparse/mm/swapfile.c
    2.89 -3f108af81Thhb242EmKjGCYkjx-GJA xenolinux-2.4.23-sparse/mm/vmalloc.c
    2.90 -3fe30e99dFNs6b9uUZGMrVy2A5qfGg xenolinux-sparse
    2.91 +3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.24-sparse/Documentation/Configure.help
    2.92 +3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.24-sparse/Makefile
    2.93 +3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.24-sparse/arch/xeno/Makefile
    2.94 +3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.24-sparse/arch/xeno/boot/Makefile
    2.95 +3e5a4e65OV_j_DBtjzt5vej771AJsA xenolinux-2.4.24-sparse/arch/xeno/config.in
    2.96 +3e5a4e65TNEycLeXqPSXQJQm_xGecA xenolinux-2.4.24-sparse/arch/xeno/defconfig
    2.97 +3e6377f5xwPfYZkPHPrDbEq1PRN7uQ xenolinux-2.4.24-sparse/arch/xeno/drivers/balloon/Makefile
    2.98 +3e6377f8Me8IqtvEhb70XFgOvqQH7A xenolinux-2.4.24-sparse/arch/xeno/drivers/balloon/balloon.c
    2.99 +3e5a4e65iHEuC5sjFhj42XALYbLVRw xenolinux-2.4.24-sparse/arch/xeno/drivers/block/Makefile
   2.100 +3e5a4e65pP5spJErBW69pJxSSdK9RA xenolinux-2.4.24-sparse/arch/xeno/drivers/block/xl_block.c
   2.101 +3e67f822FOPwqHiaRKbrskgWgoNL5g xenolinux-2.4.24-sparse/arch/xeno/drivers/block/xl_block.h
   2.102 +3e676eb5RXnHzSHgA1BvM0B1aIm4qg xenolinux-2.4.24-sparse/arch/xeno/drivers/block/xl_vbd.c
   2.103 +3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ xenolinux-2.4.24-sparse/arch/xeno/drivers/console/Makefile
   2.104 +3e5a4e651TH-SXHoufurnWjgl5bfOA xenolinux-2.4.24-sparse/arch/xeno/drivers/console/console.c
   2.105 +3e5a4e656nfFISThfbyXQOA6HN6YHw xenolinux-2.4.24-sparse/arch/xeno/drivers/dom0/Makefile
   2.106 +3e5a4e65BXtftInNHUC2PjDfPhdZZA xenolinux-2.4.24-sparse/arch/xeno/drivers/dom0/dom0_core.c
   2.107 +3e5a4e65gfn_ltB8ujHMVFApnTTNRQ xenolinux-2.4.24-sparse/arch/xeno/drivers/dom0/vfr.c
   2.108 +3e5a4e65gZBRBB6RsSVg1c9iahigAw xenolinux-2.4.24-sparse/arch/xeno/drivers/network/Makefile
   2.109 +3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ xenolinux-2.4.24-sparse/arch/xeno/drivers/network/network.c
   2.110 +3e5a4e65lWzkiPXsZdzPt2RNnJGG1g xenolinux-2.4.24-sparse/arch/xeno/kernel/Makefile
   2.111 +3e5a4e65_hqfuxtGG8IUy6wRM86Ecg xenolinux-2.4.24-sparse/arch/xeno/kernel/entry.S
   2.112 +3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg xenolinux-2.4.24-sparse/arch/xeno/kernel/head.S
   2.113 +3e5a4e65ibVQmwlOn0j3sVH_j_6hAg xenolinux-2.4.24-sparse/arch/xeno/kernel/hypervisor.c
   2.114 +3e5a4e65RMGcuA-HCn3-wNx3fFQwdg xenolinux-2.4.24-sparse/arch/xeno/kernel/i386_ksyms.c
   2.115 +3e5a4e65MEvZhlr070sK5JsfAQlv7Q xenolinux-2.4.24-sparse/arch/xeno/kernel/ioport.c
   2.116 +3e5a4e653U6cELGv528IxOLHvCq8iA xenolinux-2.4.24-sparse/arch/xeno/kernel/irq.c
   2.117 +3e5a4e65muT6SU3ck47IP87Q7Ti5hA xenolinux-2.4.24-sparse/arch/xeno/kernel/ldt.c
   2.118 +3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ xenolinux-2.4.24-sparse/arch/xeno/kernel/process.c
   2.119 +3e5a4e66tR-qJMLj3MppcKqmvuI2XQ xenolinux-2.4.24-sparse/arch/xeno/kernel/setup.c
   2.120 +3e5a4e66fWSTagLGU2P8BGFGRjhDiw xenolinux-2.4.24-sparse/arch/xeno/kernel/signal.c
   2.121 +3e5a4e66N__lUXNwzQ-eADRzK9LXuQ xenolinux-2.4.24-sparse/arch/xeno/kernel/time.c
   2.122 +3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ xenolinux-2.4.24-sparse/arch/xeno/kernel/traps.c
   2.123 +3e5a4e66-9_NczrVMbuQkoSLyXckIw xenolinux-2.4.24-sparse/arch/xeno/lib/Makefile
   2.124 +3e5a4e6637ZDk0BvFEC-aFQs599-ng xenolinux-2.4.24-sparse/arch/xeno/lib/delay.c
   2.125 +3f68905cF5i8-NYpIhGjKmh0y8Gu5g xenolinux-2.4.24-sparse/arch/xeno/lib/xeno_proc.c
   2.126 +3e5a4e66croVgpcJyJuF2ycQw0HuJw xenolinux-2.4.24-sparse/arch/xeno/mm/Makefile
   2.127 +3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg xenolinux-2.4.24-sparse/arch/xeno/mm/fault.c
   2.128 +3e5a4e668SE9rixq4ahho9rNhLUUFQ xenolinux-2.4.24-sparse/arch/xeno/mm/hypervisor.c
   2.129 +3e5a4e661gLzzff25pJooKIIWe7IWg xenolinux-2.4.24-sparse/arch/xeno/mm/init.c
   2.130 +3f0bed43UUdQichXAiVNrjV-y2Kzcg xenolinux-2.4.24-sparse/arch/xeno/mm/ioremap.c
   2.131 +3e5a4e66qRlSTcjafidMB6ulECADvg xenolinux-2.4.24-sparse/arch/xeno/vmlinux.lds
   2.132 +3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.24-sparse/drivers/block/ll_rw_blk.c
   2.133 +3f108aeaLcGDgQdFAANLTUEid0a05w xenolinux-2.4.24-sparse/drivers/char/mem.c
   2.134 +3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.24-sparse/drivers/char/tty_io.c
   2.135 +3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.24-sparse/fs/exec.c
   2.136 +3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.24-sparse/include/asm-xeno/bugs.h
   2.137 +3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.24-sparse/include/asm-xeno/desc.h
   2.138 +3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.24-sparse/include/asm-xeno/fixmap.h
   2.139 +3e5a4e67w_DWgjIJ17Tlossu1LGujQ xenolinux-2.4.24-sparse/include/asm-xeno/highmem.h
   2.140 +3e5a4e67YtcyDLQsShhCfQwPSELfvA xenolinux-2.4.24-sparse/include/asm-xeno/hw_irq.h
   2.141 +3e5a4e677VBavzM1UZIEcH1B-RlXMA xenolinux-2.4.24-sparse/include/asm-xeno/hypervisor.h
   2.142 +3e5a4e673p7PEOyHFm3nHkYX6HQYBg xenolinux-2.4.24-sparse/include/asm-xeno/irq.h
   2.143 +3ead095db_LRUXnxaqs0dA1DWhPoQQ xenolinux-2.4.24-sparse/include/asm-xeno/keyboard.h
   2.144 +3e5a4e678ddsQOpbSiRdy1GRcDc9WA xenolinux-2.4.24-sparse/include/asm-xeno/mmu_context.h
   2.145 +3f8707e7ZmZ6TxyX0ZUEfvhA2Pb_xQ xenolinux-2.4.24-sparse/include/asm-xeno/msr.h
   2.146 +3e7270deQqtGPSnFxcW4AvJZuTUWfg xenolinux-2.4.24-sparse/include/asm-xeno/multicall.h
   2.147 +3e5a4e67mnQfh-R8KcQCaVo2Oho6yg xenolinux-2.4.24-sparse/include/asm-xeno/page.h
   2.148 +3e5a4e67uTYU5oEnIDjxuaez8njjqg xenolinux-2.4.24-sparse/include/asm-xeno/pgalloc.h
   2.149 +3e5a4e67X7JyupgdYkgDX19Huj2sAw xenolinux-2.4.24-sparse/include/asm-xeno/pgtable-2level.h
   2.150 +3e5a4e67gr4NLGtQ5CvSLimMYZlkOA xenolinux-2.4.24-sparse/include/asm-xeno/pgtable.h
   2.151 +3f108af1qNv8DVSGPv4zpqIU1txCkg xenolinux-2.4.24-sparse/include/asm-xeno/proc_cmd.h
   2.152 +3e5a4e676uK4xErTBDH6XJREn9LSyg xenolinux-2.4.24-sparse/include/asm-xeno/processor.h
   2.153 +3e5a4e67AJPjW-zL7p-xWuA6IVeH1g xenolinux-2.4.24-sparse/include/asm-xeno/ptrace.h
   2.154 +3e5a4e68uJz-xI0IBVMD7xRLQKJDFg xenolinux-2.4.24-sparse/include/asm-xeno/segment.h
   2.155 +3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA xenolinux-2.4.24-sparse/include/asm-xeno/smp.h
   2.156 +3fa8e3f0kBLeE4To2vpdi3cpJbIkbQ xenolinux-2.4.24-sparse/include/asm-xeno/suspend.h
   2.157 +3e5a4e68mTr0zcp9SXDbnd-XLrrfxw xenolinux-2.4.24-sparse/include/asm-xeno/system.h
   2.158 +3f1056a9L_kqHcFheV00KbKBzv9j5w xenolinux-2.4.24-sparse/include/asm-xeno/vga.h
   2.159 +3f689063nhrIRsMMZjZxMFk7iEINqQ xenolinux-2.4.24-sparse/include/asm-xeno/xeno_proc.h
   2.160 +3f056927gMHl7mWB89rb73JahbhQIA xenolinux-2.4.24-sparse/include/linux/blk.h
   2.161 +3e5a4e68WLX3B8owTvktP3HHOtznPQ xenolinux-2.4.24-sparse/include/linux/major.h
   2.162 +3e5a4e686V0nioX2ZpFf056sgvdiQw xenolinux-2.4.24-sparse/include/linux/sunrpc/debug.h
   2.163 +3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ xenolinux-2.4.24-sparse/init/do_mounts.c
   2.164 +3e5a4e68TJJavrunYwTAnLRSBxSYqQ xenolinux-2.4.24-sparse/kernel/panic.c
   2.165 +3f1056a9LXNTgSzITNh1mb-MIKV1Ng xenolinux-2.4.24-sparse/kernel/printk.c
   2.166 +3f9d4b44247udoqWEgFkaHiWv6Uvyg xenolinux-2.4.24-sparse/kernel/time.c
   2.167 +3eba8f878XjouY21EkQBXwYBsPsipQ xenolinux-2.4.24-sparse/lndir-rel
   2.168 +3e6e7c1efbQe93xCvOpOVCnXTMmQ5w xenolinux-2.4.24-sparse/mkbuildtree
   2.169 +3e5a4e68GxCIaFH4sy01v1wjapetaA xenolinux-2.4.24-sparse/mm/memory.c
   2.170 +3f108af5VxPkLv13tXpXgoRKALQtXQ xenolinux-2.4.24-sparse/mm/mprotect.c
   2.171 +3e5a4e681xMPdF9xCMwpyfuYMySU5g xenolinux-2.4.24-sparse/mm/mremap.c
   2.172 +3e5a4e683HKVU-sxtagrDasRB8eBVw xenolinux-2.4.24-sparse/mm/swapfile.c
   2.173 +3f108af81Thhb242EmKjGCYkjx-GJA xenolinux-2.4.24-sparse/mm/vmalloc.c
   2.174 +40026087QHbrW3n3XbK2U-hilL-K2g xenolinux-sparse

     3.1 --- a/xenolinux-2.4.23-sparse/Documentation/Configure.help	Tue Jan 06 17:57:55 2004 +0000
     3.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.3 @@ -1,28869 +0,0 @@
     3.4 -# Maintained by:
     3.5 -#	Eric S. Raymond <mailto:esr@thyrsus.com>
     3.6 -#	Steven Cole <mailto:elenstev@mesatop.com>
     3.7 -#
     3.8 -# Translations of this file available on the WWW:
     3.9 -#
    3.10 -#   - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
    3.11 -#     <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
    3.12 -#   - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
    3.13 -#     <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
    3.14 -#   - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
    3.15 -#     <http://www.traduc.org/kernelfr/>
    3.16 -#   - Polish, by Dominik Mierzejewski <mailto:dominik@piorunek.pl>, at
    3.17 -#     <http://www.piorunek.pl/~dominik/linux/kernel/>
    3.18 -#   - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
    3.19 -#     also includes infrastructure to support different languages.
    3.20 -#   - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
    3.21 -#     <http://www.terra.es/personal7/bella5/traduccions.htm>
    3.22 -#
    3.23 -# Information about what a kernel is, what it does, how to patch and
    3.24 -# compile it and much more is contained in the Kernel-HOWTO, available
    3.25 -# at <http://www.tldp.org/docs.html#howto>. Before you start
    3.26 -# compiling, make sure that you have the necessary versions of all
    3.27 -# programs and libraries required to compile and run this kernel; they
    3.28 -# are listed in the <file:Documentation/Changes>. Make sure to read the
    3.29 -# toplevel kernel README file as well.
    3.30 -#
    3.31 -# Format of this file: description<nl>variable<nl>help text<nl><nl>.
    3.32 -# The help texts may contain empty lines, but every non-empty line must
    3.33 -# be indented two positions.  Order of the help texts does not matter,
    3.34 -# however, no variable should be documented twice: if it is, only the
    3.35 -# first occurrence will be used. We try to keep the help texts of related
    3.36 -# variables close together. Lines starting with `#' are ignored. To be
    3.37 -# nice to menuconfig, limit your line length to 70 characters. Use emacs'
    3.38 -# kfill.el to edit and ispell.el to spell check this file or you lose.
    3.39 -#
    3.40 -# Comments of the form "# Choice:" followed by a menu name are used
    3.41 -# internally by the maintainers' consistency-checking tools.
    3.42 -#
    3.43 -# If you add a help text to this file, please try to be as gentle as
    3.44 -# possible. Don't use unexplained acronyms and generally write for the
    3.45 -# hypothetical ignorant but intelligent user who has just bought a PC,
    3.46 -# removed Windows, installed Linux and is now recompiling the kernel
    3.47 -# for the first time. Tell them what to do if they're unsure. Technical
    3.48 -# information should go in a README in the Documentation directory.
    3.49 -#
    3.50 -# Mention all the relevant READMEs and HOWTOs in the help text.
    3.51 -# Make them file URLs relative to the top level of the source tree so
    3.52 -# that help browsers can turn them into hotlinks.  All URLs should be
    3.53 -# surrounded by <>.
    3.54 -#
    3.55 -# Repetitions are fine since the help texts are not meant to be read
    3.56 -# in sequence.  It is good style to include URLs pointing to more
    3.57 -# detailed technical information, pictures of the hardware, etc.
    3.58 -#
    3.59 -# The most important thing to include in a help entry is *motivation*.
    3.60 -# Explain why someone configuring a kernel might want to select your
    3.61 -# option.
    3.62 -#
    3.63 -# All this was shamelessly stolen from numerous different sources. Many
    3.64 -# thanks to all the contributors. Feel free to use these help texts in
    3.65 -# your own kernel configuration tools. The texts are copyrighted (c)
    3.66 -# 1995-2000 by Axel Boldt and many others and are governed by the GNU
    3.67 -# General Public License.
    3.68 -
    3.69 -Prompt for development and/or incomplete code/drivers
    3.70 -CONFIG_EXPERIMENTAL
    3.71 -  Some of the various things that Linux supports (such as network
    3.72 -  drivers, file systems, network protocols, etc.) can be in a state
    3.73 -  of development where the functionality, stability, or the level of
    3.74 -  testing is not yet high enough for general use. This is usually
    3.75 -  known as the "alpha-test" phase among developers. If a feature is
    3.76 -  currently in alpha-test, then the developers usually discourage
    3.77 -  uninformed widespread use of this feature by the general public to
    3.78 -  avoid "Why doesn't this work?" type mail messages. However, active
    3.79 -  testing and use of these systems is welcomed. Just be aware that it
    3.80 -  may not meet the normal level of reliability or it may fail to work
    3.81 -  in some special cases. Detailed bug reports from people familiar
    3.82 -  with the kernel internals are usually welcomed by the developers
    3.83 -  (before submitting bug reports, please read the documents
    3.84 -  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
    3.85 -  <file:Documentation/BUG-HUNTING>, and
    3.86 -  <file:Documentation/oops-tracing.txt> in the kernel source).
    3.87 -
    3.88 -  This option will also make obsoleted drivers available. These are
    3.89 -  drivers that have been replaced by something else, and/or are
    3.90 -  scheduled to be removed in a future kernel release.
    3.91 -
    3.92 -  Unless you intend to help test and develop a feature or driver that
    3.93 -  falls into this category, or you have a situation that requires
    3.94 -  using these features, you should probably say N here, which will
    3.95 -  cause the configurator to present you with fewer choices. If
    3.96 -  you say Y here, you will be offered the choice of using features or
    3.97 -  drivers that are currently considered to be in the alpha-test phase.
    3.98 -
    3.99 -Prompt for drivers for obsolete features and hardware
   3.100 -CONFIG_OBSOLETE
   3.101 -  Obsolete drivers have usually been replaced by more recent software
   3.102 -  that can talk to the same hardware.  Obsolete hardware is things
   3.103 -  like MGA monitors that you are very unlikely to see on today's
   3.104 -  systems.
   3.105 -
   3.106 -Prompt for advanced kernel configuration options
   3.107 -CONFIG_ADVANCED_OPTIONS
   3.108 -  This option will enable prompting for a variety of advanced kernel
   3.109 -  configuration options.  These options can cause the kernel to not
   3.110 -  work if they are set incorrectly, but can be used to optimize certain
   3.111 -  aspects of kernel memory management.
   3.112 -
   3.113 -  Unless you know what you are doing you *should not* enable this option.
   3.114 -
   3.115 -Symmetric Multi-Processing support
   3.116 -CONFIG_SMP
   3.117 -  This enables support for systems with more than one CPU. If you have
   3.118 -  a system with only one CPU, like most personal computers, say N. If
   3.119 -  you have a system with more than one CPU, say Y.
   3.120 -
   3.121 -  If you say N here, the kernel will run on single and multiprocessor
   3.122 -  machines, but will use only one CPU of a multiprocessor machine. If
   3.123 -  you say Y here, the kernel will run on many, but not all,
   3.124 -  single machines. On a singleprocessor machine, the kernel
   3.125 -  will run faster if you say N here.
   3.126 -
   3.127 -  Note that if you say Y here and choose architecture "586" or
   3.128 -  "Pentium" under "Processor family", the kernel will not work on 486
   3.129 -  architectures. Similarly, multiprocessor kernels for the "PPro"
   3.130 -  architecture may not work on all Pentium based boards.
   3.131 -
   3.132 -  People using multiprocessor machines who say Y here should also say
   3.133 -  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
   3.134 -  Management" code will be disabled if you say Y here.
   3.135 -
   3.136 -  See also the <file:Documentation/smp.tex>,
   3.137 -  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
   3.138 -  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
   3.139 -  <http://www.tldp.org/docs.html#howto>.
   3.140 -
   3.141 -  If you don't know what to do here, say N.
   3.142 -
   3.143 -Maximum number of CPUs
   3.144 -CONFIG_NR_CPUS
   3.145 -  This allows you to specify the maximum number of CPUs which this
   3.146 -  kernel will support.  The maximum supported value is 32 and the
   3.147 -  mimimum value which makes sense is 2.
   3.148 -
   3.149 -  This is purely to save memory - each supported CPU adds
   3.150 -  approximately eight kilobytes to the kernel image.
   3.151 -
   3.152 -Intel or compatible 80x86 processor
   3.153 -CONFIG_X86
   3.154 -  This is Linux's home port.  Linux was originally native to the Intel
   3.155 -  386, and runs on all the later x86 processors including the Intel
   3.156 -  486, 586, Pentiums, and various instruction-set-compatible chips by
   3.157 -  AMD, Cyrix, and others.
   3.158 -
   3.159 -Alpha processor
   3.160 -CONFIG_ALPHA
   3.161 -  The Alpha is a 64-bit general-purpose processor designed and
   3.162 -  marketed by the Digital Equipment Corporation of blessed memory, now
   3.163 -  Compaq.  Alpha Linux dates from 1995-1996 and was the first non-x86
   3.164 -  port. The Alpha Linux project has a home page at
   3.165 -  <http://www.alphalinux.org/>.
   3.166 -
   3.167 -32-bit Sun Sparc
   3.168 -CONFIG_SPARC32
   3.169 -  SPARC is a family of RISC microprocessors designed and marketed by
   3.170 -  Sun Microsystems, incorporated.  They are very widely found in Sun
   3.171 -  workstations and clones. This port covers the original 32-bit SPARC;
   3.172 -  it is old and stable and usually considered one of the "big three"
   3.173 -  along with the Intel and Alpha ports.  The UltraLinux project
   3.174 -  maintains both the SPARC32 and SPARC64 ports; its web page is
   3.175 -  available at <http://www.ultralinux.org/>.
   3.176 -
   3.177 -64-bit Sun Sparc
   3.178 -CONFIG_SPARC64
   3.179 -  SPARC is a family of RISC microprocessors designed and marketed by
   3.180 -  Sun Microsystems, incorporated.  This port covers the newer 64-bit
   3.181 -  UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
   3.182 -  SPARC64 ports; its web page is available at
   3.183 -  <http://www.ultralinux.org/>.
   3.184 -
   3.185 -Power PC processor
   3.186 -CONFIG_PPC
   3.187 -  The PowerPC is a very capable 32-bit RISC processor from Motorola,
   3.188 -  the successor to their 68000 and 88000 series.  It powers recent
   3.189 -  Macintoshes and also a widely-used series of single-board computers
   3.190 -  from Motorola.  The Linux PowerPC port has a home page at
   3.191 -  <http://penguinppc.org/>.
   3.192 -
   3.193 -Motorola 68K processors
   3.194 -CONFIG_M68K
   3.195 -  The Motorola 68K microprocessors are now obsolete, having been
   3.196 -  superseded by the PowerPC line also from Motorola.  But they powered
   3.197 -  the first wave of workstation hardware in the 1980s, including Sun
   3.198 -  workstations; they were also the basis of the original Amiga and
   3.199 -  later Atari personal computers.  A lot of this hardware is still
   3.200 -  around.  The m68k project has a home page at
   3.201 -  <http://www.linux-m68k.org/>.
   3.202 -
   3.203 -ARM processors
   3.204 -CONFIG_ARM
   3.205 -  The ARM series is a line of low-power-consumption RISC chip designs
   3.206 -  licensed by ARM ltd and targeted at embedded applications and
   3.207 -  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
   3.208 -  manufactured, but  legacy ARM-based PC hardware remains popular in
   3.209 -  Europe.  There is an ARM Linux project with a web page at
   3.210 -  <http://www.arm.linux.org.uk/>.
   3.211 -
   3.212 -SuperH processors
   3.213 -CONFIG_SUPERH
   3.214 -  The SuperH is a RISC processor targeted for use in embedded systems
   3.215 -  and consumer electronics; it was also used in the Sega Dreamcast
   3.216 -  gaming console.  The SuperH port has a home page at
   3.217 -  <http://www.sh-linux.org/>.
   3.218 -
   3.219 -IA64 processors, including Intel Itanium
   3.220 -CONFIG_IA64
   3.221 -  The Itanium is Intel's 64-bit successor to the 32-bit X86 line.  As
   3.222 -  of early 2001 it is not yet in widespread production use.  The Linux
   3.223 -  IA-64 project has a home page at <http://www.linuxia64.org/>.
   3.224 -
   3.225 -HP PA-RISC processor
   3.226 -CONFIG_PARISC
   3.227 -  The PA-RISC microprocessor is a RISC chip designed by
   3.228 -  Hewlett-Packard and used in their line of workstations.  The PA-RISC
   3.229 -  Linux project has a home page at <www.parisc-linux.org>.
   3.230 -
   3.231 -IBM System/390
   3.232 -CONFIG_S390
   3.233 -  Linux now runs on the venerable System/390 mainframe from IBM, in a
   3.234 -  guest partition under VM.  In fact, over 40,000 simultaneous Linux
   3.235 -  images have been run on a single mainframe!  The S390 Linux project
   3.236 -  has a home page at <http://linux.s390.org/>.
   3.237 -
   3.238 -Axis Communications ETRAX 100LX embedded network CPU
   3.239 -CONFIG_CRIS
   3.240 -  Linux has been ported to run on the Axis Communications ETRAX 100LX
   3.241 -  CPU and the single-board computers built around it, targeted for
   3.242 -  network and embedded applications.  For more information see the
   3.243 -  Axis Communication site, <http://developer.axis.com/>.
   3.244 -
   3.245 -Unsynced TSC support
   3.246 -CONFIG_X86_TSC_DISABLE
   3.247 -  This option is used for getting Linux to run on a NUMA multi-node 
   3.248 -  boxes, laptops and other systems suffering from unsynced TSCs or 
   3.249 -  TSC drift, which can cause gettimeofday to return non-monotonic values. 
   3.250 -  Choosing this option will disable the CONFIG_X86_TSC optimization,
   3.251 -  and allows you to then specify "notsc" as a boot option regardless of 
   3.252 -  which processor you have compiled for. 
   3.253 -  
   3.254 -  NOTE: If your system hangs when init should run, you are probably
   3.255 -  using a i686 compiled glibc which reads the TSC without checking for 
   3.256 -  availability. Boot without "notsc" and install a i386 compiled glibc 
   3.257 -  to solve the problem.
   3.258 -
   3.259 -  If unsure, say N.
   3.260 -
   3.261 -Multiquad support for NUMAQ systems
   3.262 -CONFIG_X86_NUMAQ
   3.263 -  This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
   3.264 -  multiquad box. This changes the way that processors are bootstrapped,
   3.265 -  and uses Clustered Logical APIC addressing mode instead of Flat Logical.
   3.266 -  You will need a new lynxer.elf file to flash your firmware with - send
   3.267 -  email to Martin.Bligh@us.ibm.com
   3.268 -
   3.269 -Support for IBM Summit (EXA) systems
   3.270 -CONFIG_X86_SUMMIT
   3.271 -  This option is needed for IBM systems that use the Summit/EXA chipset.
   3.272 -  (EXA: Extendable Xseries Architecture)In particular, it is needed for 
   3.273 -  the x440 (even for the 4-CPU model).
   3.274 -
   3.275 -  If you don't have this computer, you may safely say N.
   3.276 -
   3.277 -IO-APIC support on uniprocessors
   3.278 -CONFIG_X86_UP_IOAPIC
   3.279 -  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
   3.280 -  SMP-capable replacement for PC-style interrupt controllers. Most
   3.281 -  SMP systems and a small number of uniprocessor systems have one.
   3.282 -  If you have a single-CPU system with an IO-APIC, you can say Y here
   3.283 -  to use it. If you say Y here even though your machine doesn't have
   3.284 -  an IO-APIC, then the kernel will still run with no slowdown at all.
   3.285 -
   3.286 -  If you have a system with several CPUs, you do not need to say Y
   3.287 -  here: the IO-APIC will be used automatically.
   3.288 -
   3.289 -Local APIC Support on Uniprocessors
   3.290 -CONFIG_X86_UP_APIC
   3.291 -  A local APIC (Advanced Programmable Interrupt Controller) is an
   3.292 -  integrated interrupt controller in the CPU. If you have a single-CPU
   3.293 -  system which has a processor with a local APIC, you can say Y here to
   3.294 -  enable and use it. If you say Y here even though your machine doesn't
   3.295 -  have a local APIC, then the kernel will still run with no slowdown at
   3.296 -  all. The local APIC supports CPU-generated self-interrupts (timer,
   3.297 -  performance counters), and the NMI watchdog which detects hard lockups.
   3.298 -
   3.299 -  If you have a system with several CPUs, you do not need to say Y
   3.300 -  here: the local APIC will be used automatically.
   3.301 -
   3.302 -Kernel math emulation
   3.303 -CONFIG_MATH_EMULATION
   3.304 -  Linux can emulate a math coprocessor (used for floating point
   3.305 -  operations) if you don't have one. 486DX and Pentium processors have
   3.306 -  a math coprocessor built in, 486SX and 386 do not, unless you added
   3.307 -  a 487DX or 387, respectively. (The messages during boot time can
   3.308 -  give you some hints here ["man dmesg"].) Everyone needs either a
   3.309 -  coprocessor or this emulation.
   3.310 -
   3.311 -  If you don't have a math coprocessor, you need to say Y here; if you
   3.312 -  say Y here even though you have a coprocessor, the coprocessor will
   3.313 -  be used nevertheless. (This behaviour can be changed with the kernel
   3.314 -  command line option "no387", which comes handy if your coprocessor
   3.315 -  is broken. Try "man bootparam" or see the documentation of your boot
   3.316 -  loader (lilo or loadlin) about how to pass options to the kernel at
   3.317 -  boot time.) This means that it is a good idea to say Y here if you
   3.318 -  intend to use this kernel on different machines.
   3.319 -
   3.320 -  More information about the internals of the Linux math coprocessor
   3.321 -  emulation can be found in <file:arch/i386/math-emu/README>.
   3.322 -
   3.323 -  If you are not sure, say Y; apart from resulting in a 66 KB bigger
   3.324 -  kernel, it won't hurt.
   3.325 -
   3.326 -Timer and CPU usage LEDs
   3.327 -CONFIG_LEDS
   3.328 -  If you say Y here, the LEDs on your machine will be used
   3.329 -  to provide useful information about your current system status.
   3.330 -
   3.331 -  If you are compiling a kernel for a NetWinder or EBSA-285, you will
   3.332 -  be able to select which LEDs are active using the options below. If
   3.333 -  you are compiling a kernel for the EBSA-110 or the LART however, the
   3.334 -  red LED will simply flash regularly to indicate that the system is
   3.335 -  still functional. It is safe to say Y here if you have a CATS
   3.336 -  system, but the driver will do nothing.
   3.337 -
   3.338 -Timer LED
   3.339 -CONFIG_LEDS_TIMER
   3.340 -  If you say Y here, one of the system LEDs (the green one on the
   3.341 -  NetWinder, the amber one on the EBSA285, or the red one on the LART)
   3.342 -  will flash regularly to indicate that the system is still
   3.343 -  operational. This is mainly useful to kernel hackers who are
   3.344 -  debugging unstable kernels.
   3.345 -
   3.346 -  The LART uses the same LED for both Timer LED and CPU usage LED
   3.347 -  functions. You may choose to use both, but the Timer LED function
   3.348 -  will overrule the CPU usage LED.
   3.349 -
   3.350 -CPU usage LED
   3.351 -CONFIG_LEDS_CPU
   3.352 -  If you say Y here, the red LED will be used to give a good real
   3.353 -  time indication of CPU usage, by lighting whenever the idle task
   3.354 -  is not currently executing.
   3.355 -
   3.356 -  The LART uses the same LED for both Timer LED and CPU usage LED
   3.357 -  functions. You may choose to use both, but the Timer LED function
   3.358 -  will overrule the CPU usage LED.
   3.359 -
   3.360 -Kernel FP software completion
   3.361 -CONFIG_MATHEMU
   3.362 -  This option is required for IEEE compliant floating point arithmetic
   3.363 -  on the Alpha. The only time you would ever not say Y is to say M in
   3.364 -  order to debug the code. Say Y unless you know what you are doing.
   3.365 -
   3.366 -# Choice: himem
   3.367 -High Memory support
   3.368 -CONFIG_NOHIGHMEM
   3.369 -  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
   3.370 -  However, the address space of 32-bit x86 processors is only 4
   3.371 -  Gigabytes large. That means that, if you have a large amount of
   3.372 -  physical memory, not all of it can be "permanently mapped" by the
   3.373 -  kernel. The physical memory that's not permanently mapped is called
   3.374 -  "high memory".
   3.375 -
   3.376 -  If you are compiling a kernel which will never run on a machine with
   3.377 -  more than 960 megabytes of total physical RAM, answer "off" here (default
   3.378 -  choice and suitable for most users). This will result in a "3GB/1GB"
   3.379 -  split: 3GB are mapped so that each process sees a 3GB virtual memory
   3.380 -  space and the remaining part of the 4GB virtual memory space is used
   3.381 -  by the kernel to permanently map as much physical memory as
   3.382 -  possible.
   3.383 -
   3.384 -  If the machine has between 1 and 4 Gigabytes physical RAM, then
   3.385 -  answer "4GB" here.
   3.386 -
   3.387 -  If more than 4 Gigabytes is used then answer "64GB" here. This
   3.388 -  selection turns Intel PAE (Physical Address Extension) mode on.
   3.389 -  PAE implements 3-level paging on IA32 processors. PAE is fully
   3.390 -  supported by Linux, PAE mode is implemented on all recent Intel
   3.391 -  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
   3.392 -  then the kernel will not boot on CPUs that don't support PAE!
   3.393 -
   3.394 -  The actual amount of total physical memory will either be auto
   3.395 -  detected or can be forced by using a kernel command line option such
   3.396 -  as "mem=256M". (Try "man bootparam" or see the documentation of your
   3.397 -  boot loader (grub, lilo or loadlin) about how to pass options to the
   3.398 -  kernel at boot time.)
   3.399 -
   3.400 -  If unsure, say "off".
   3.401 -
   3.402 -4GB
   3.403 -CONFIG_HIGHMEM4G
   3.404 -  Select this if you have a 32-bit processor and between 1 and 4
   3.405 -  gigabytes of physical RAM.
   3.406 -
   3.407 -64GB
   3.408 -CONFIG_HIGHMEM64G
   3.409 -  Select this if you have a 32-bit processor and more than 4
   3.410 -  gigabytes of physical RAM.
   3.411 -
   3.412 -HIGHMEM I/O support
   3.413 -CONFIG_HIGHIO
   3.414 -  If you want to be able to do I/O to high memory pages, say Y.
   3.415 -  Otherwise low memory pages are used as bounce buffers causing a
   3.416 -  degrade in performance.
   3.417 -
   3.418 -Normal floppy disk support
   3.419 -CONFIG_BLK_DEV_FD
   3.420 -  If you want to use the floppy disk drive(s) of your PC under Linux,
   3.421 -  say Y. Information about this driver, especially important for IBM
   3.422 -  Thinkpad users, is contained in <file:Documentation/floppy.txt>.
   3.423 -  That file also contains the location of the Floppy driver FAQ as
   3.424 -  well as location of the fdutils package used to configure additional
   3.425 -  parameters of the driver at run time.
   3.426 -
   3.427 -  This driver is also available as a module ( = code which can be
   3.428 -  inserted in and removed from the running kernel whenever you want).
   3.429 -  The module will be called floppy.o. If you want to compile it as a
   3.430 -  module, say M here and read <file:Documentation/modules.txt>.
   3.431 -
   3.432 -iSeries Virtual I/O Disk Support
   3.433 -CONFIG_VIODASD
   3.434 -  If you are running on an iSeries system and you want to use
   3.435 -  virtual disks created and managed by OS/400, say Y.
   3.436 -
   3.437 -iSeries Virtual I/O Disk IDE Emulation
   3.438 -CONFIG_VIODASD_IDE
   3.439 -  This causes the iSeries virtual disks to look like IDE disks.
   3.440 -  If you have programs or utilities that only support certain
   3.441 -  kinds of disks, this option will cause iSeries virtual disks
   3.442 -  to pretend to be IDE disks, which may satisfy the program.
   3.443 -
   3.444 -Support for PowerMac floppy
   3.445 -CONFIG_MAC_FLOPPY
   3.446 -  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
   3.447 -  floppy controller, say Y here. Most commonly found in PowerMacs.
   3.448 -
   3.449 -RAM disk support
   3.450 -CONFIG_BLK_DEV_RAM
   3.451 -  Saying Y here will allow you to use a portion of your RAM memory as
   3.452 -  a block device, so that you can make file systems on it, read and
   3.453 -  write to it and do all the other things that you can do with normal
   3.454 -  block devices (such as hard drives). It is usually used to load and
   3.455 -  store a copy of a minimal root file system off of a floppy into RAM
   3.456 -  during the initial install of Linux.
   3.457 -
   3.458 -  Note that the kernel command line option "ramdisk=XX" is now
   3.459 -  obsolete. For details, read <file:Documentation/ramdisk.txt>.
   3.460 -
   3.461 -  If you want to compile this as a module ( = code which can be
   3.462 -  inserted in and removed from the running kernel whenever you want),
   3.463 -  say M and read <file:Documentation/modules.txt>. The module will be
   3.464 -  called rd.o.
   3.465 -
   3.466 -  Most normal users won't need the RAM disk functionality, and can
   3.467 -  thus say N here.
   3.468 -
   3.469 -Default RAM disk size
   3.470 -CONFIG_BLK_DEV_RAM_SIZE
   3.471 -  The default value is 4096. Only change this if you know what are
   3.472 -  you doing. If you are using IBM S/390, then set this to 8192.
   3.473 -
   3.474 -Initial RAM disk (initrd) support
   3.475 -CONFIG_BLK_DEV_INITRD
   3.476 -  The initial RAM disk is a RAM disk that is loaded by the boot loader
   3.477 -  (loadlin or lilo) and that is mounted as root before the normal boot
   3.478 -  procedure. It is typically used to load modules needed to mount the
   3.479 -  "real" root file system, etc. See <file:Documentation/initrd.txt>
   3.480 -  for details.
   3.481 -
   3.482 -Embed root filesystem ramdisk into the kernel
   3.483 -CONFIG_EMBEDDED_RAMDISK
   3.484 -  Select this option if you want to build the ramdisk image into the
   3.485 -  the final kernel binary.
   3.486 -
   3.487 -Filename of gziped ramdisk image
   3.488 -CONFIG_EMBEDDED_RAMDISK_IMAGE
   3.489 -  This is the filename of the ramdisk image to be built into the
   3.490 -  kernel.  Relative pathnames are relative to arch/mips/ramdisk/.
   3.491 -  The ramdisk image is not part of the kernel distribution; you must
   3.492 -  provide one yourself.
   3.493 -
   3.494 -Loopback device support
   3.495 -CONFIG_BLK_DEV_LOOP
   3.496 -  Saying Y here will allow you to use a regular file as a block
   3.497 -  device; you can then create a file system on that block device and
   3.498 -  mount it just as you would mount other block devices such as hard
   3.499 -  drive partitions, CD-ROM drives or floppy drives. The loop devices
   3.500 -  are block special device files with major number 7 and typically
   3.501 -  called /dev/loop0, /dev/loop1 etc.
   3.502 -
   3.503 -  This is useful if you want to check an ISO 9660 file system before
   3.504 -  burning the CD, or if you want to use floppy images without first
   3.505 -  writing them to floppy. Furthermore, some Linux distributions avoid
   3.506 -  the need for a dedicated Linux partition by keeping their complete
   3.507 -  root file system inside a DOS FAT file using this loop device
   3.508 -  driver.
   3.509 -
   3.510 -  The loop device driver can also be used to "hide" a file system in a
   3.511 -  disk partition, floppy, or regular file, either using encryption
   3.512 -  (scrambling the data) or steganography (hiding the data in the low
   3.513 -  bits of, say, a sound file). This is also safe if the file resides
   3.514 -  on a remote file server. If you want to do this, you will first have
   3.515 -  to acquire and install a kernel patch from
   3.516 -  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
   3.517 -  say Y to this option.
   3.518 -
   3.519 -  Note that alternative ways to use encrypted file systems are
   3.520 -  provided by the cfs package, which can be gotten from
   3.521 -  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
   3.522 -  package, available at <http://tcfs.dia.unisa.it/>. You do not need
   3.523 -  to say Y here if you want to use one of these. However, using cfs
   3.524 -  requires saying Y to "NFS file system support" below while using
   3.525 -  tcfs requires applying a kernel patch. An alternative steganography
   3.526 -  solution is provided by StegFS, also available from
   3.527 -  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
   3.528 -
   3.529 -  To use the loop device, you need the losetup utility and a recent
   3.530 -  version of the mount program, both contained in the util-linux
   3.531 -  package. The location and current version number of util-linux is
   3.532 -  contained in the file <file:Documentation/Changes>.
   3.533 -
   3.534 -  Note that this loop device has nothing to do with the loopback
   3.535 -  device used for network connections from the machine to itself.
   3.536 -
   3.537 -  If you want to compile this driver as a module ( = code which can be
   3.538 -  inserted in and removed from the running kernel whenever you want),
   3.539 -  say M here and read <file:Documentation/modules.txt>. The module
   3.540 -  will be called loop.o.
   3.541 -
   3.542 -  Most users will answer N here.
   3.543 -
   3.544 -Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
   3.545 -CONFIG_BLK_DEV_UMEM
   3.546 -  Saying Y here will include support for the MM5415 family of
   3.547 -  battery backed (Non-volatile) RAM cards.
   3.548 -  <http://www.umem.com/>
   3.549 -
   3.550 -  The cards appear as block devices that can be partitioned into
   3.551 -  as many as 15 partitions.
   3.552 -
   3.553 -  If you want to compile this driver as a module ( = code which can be
   3.554 -  inserted in and removed from the running kernel whenever you want),
   3.555 -  say M here and read Documentation/modules.txt. The module will be
   3.556 -  called umem.o.
   3.557 -
   3.558 -  The umem driver has been allocated block major number 116.
   3.559 -  See Documentation/devices.txt for recommended device naming.
   3.560 -
   3.561 -Network block device support
   3.562 -CONFIG_BLK_DEV_NBD
   3.563 -  Saying Y here will allow your computer to be a client for network
   3.564 -  block devices, i.e. it will be able to use block devices exported by
   3.565 -  servers (mount file systems on them etc.). Communication between
   3.566 -  client and server works over TCP/IP networking, but to the client
   3.567 -  program this is hidden: it looks like a regular local file access to
   3.568 -  a block device special file such as /dev/nd0.
   3.569 -
   3.570 -  Network block devices also allows you to run a block-device in
   3.571 -  userland (making server and client physically the same computer,
   3.572 -  communicating using the loopback network device).
   3.573 -
   3.574 -  Read <file:Documentation/nbd.txt> for more information, especially
   3.575 -  about where to find the server code, which runs in user space and
   3.576 -  does not need special kernel support.
   3.577 -
   3.578 -  Note that this has nothing to do with the network file systems NFS
   3.579 -  or Coda; you can say N here even if you intend to use NFS or Coda.
   3.580 -
   3.581 -  If you want to compile this driver as a module ( = code which can be
   3.582 -  inserted in and removed from the running kernel whenever you want),
   3.583 -  say M here and read <file:Documentation/modules.txt>. The module
   3.584 -  will be called nbd.o.
   3.585 -
   3.586 -  If unsure, say N.
   3.587 -
   3.588 -XenoLinux virtual block device support
   3.589 -CONFIG_XENOLINUX_BLOCK
   3.590 -  Xen can export virtual block devices which map back to extents of
   3.591 -  blocks on the physical partitions.  This option is needed for
   3.592 -  xenolinux to make use of such devices when running as a Xen guest.
   3.593 -
   3.594 -  If unsure, say Y.
   3.595 -
   3.596 -Per partition statistics in /proc/partitions
   3.597 -CONFIG_BLK_STATS
   3.598 -  If you say yes here, your kernel will keep statistical information
   3.599 -  for every partition. The information includes things as numbers of
   3.600 -  read and write accesses, the number of merged requests etc.
   3.601 -
   3.602 -  This is required for the full functionality of sar(8) and interesting
   3.603 -  if you want to do performance tuning, by tweaking the elevator, e.g.
   3.604 -
   3.605 -  If unsure, say N.
   3.606 -
   3.607 -ATA/IDE/MFM/RLL support
   3.608 -CONFIG_IDE
   3.609 -  If you say Y here, your kernel will be able to manage low cost mass
   3.610 -  storage units such as ATA/(E)IDE and ATAPI units. The most common
   3.611 -  cases are IDE hard drives and ATAPI CD-ROM drives.
   3.612 -
   3.613 -  If your system is pure SCSI and doesn't use these interfaces, you
   3.614 -  can say N here.
   3.615 -
   3.616 -  Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
   3.617 -  for mass storage units such as hard disks. It was designed by
   3.618 -  Western Digital and Compaq Computer in 1984. It was then named
   3.619 -  ST506. Quite a number of disks use the IDE interface.
   3.620 -
   3.621 -  AT Attachment (ATA) is the superset of the IDE specifications.
   3.622 -  ST506 was also called ATA-1.
   3.623 -
   3.624 -  Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
   3.625 -  ATA-3. It provides support for larger disks (up to 8.4GB by means of
   3.626 -  the LBA standard), more disks (4 instead of 2) and for other mass
   3.627 -  storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
   3.628 -  ATA-4 and provides faster (and more CPU friendly) transfer modes
   3.629 -  than previous PIO (Programmed processor Input/Output) from previous
   3.630 -  ATA/IDE standards by means of fast DMA controllers.
   3.631 -
   3.632 -  ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
   3.633 -  CD-ROM drives, similar in many respects to the SCSI protocol.
   3.634 -
   3.635 -  SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
   3.636 -  designed in order to prevent data corruption and disk crash by
   3.637 -  detecting pre hardware failure conditions (heat, access time, and
   3.638 -  the like...). Disks built since June 1995 may follow this standard.
   3.639 -  The kernel itself don't manage this; however there are quite a
   3.640 -  number of user programs such as smart that can query the status of
   3.641 -  SMART parameters disk.
   3.642 -
   3.643 -  If you want to compile this driver as a module ( = code which can be
   3.644 -  inserted in and removed from the running kernel whenever you want),
   3.645 -  say M here and read <file:Documentation/modules.txt>. The module
   3.646 -  will be called ide.o.
   3.647 -
   3.648 -  For further information, please read <file:Documentation/ide.txt>.
   3.649 -
   3.650 -  If unsure, say Y.
   3.651 -
   3.652 -Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
   3.653 -CONFIG_BLK_DEV_IDE
   3.654 -  If you say Y here, you will use the full-featured IDE driver to
   3.655 -  control up to ten ATA/IDE interfaces, each being able to serve a
   3.656 -  "master" and a "slave" device, for a total of up to twenty ATA/IDE
   3.657 -  disk/cdrom/tape/floppy drives.
   3.658 -
   3.659 -  Useful information about large (>540 MB) IDE disks, multiple
   3.660 -  interfaces, what to do if ATA/IDE devices are not automatically
   3.661 -  detected, sound card ATA/IDE ports, module support, and other
   3.662 -  topics, is contained in <file:Documentation/ide.txt>. For detailed
   3.663 -  information about hard drives, consult the Disk-HOWTO and the
   3.664 -  Multi-Disk-HOWTO, available from
   3.665 -  <http://www.tldp.org/docs.html#howto>.
   3.666 -
   3.667 -  To fine-tune ATA/IDE drive/interface parameters for improved
   3.668 -  performance, look for the hdparm package at
   3.669 -  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   3.670 -
   3.671 -  If you want to compile this driver as a module ( = code which can be
   3.672 -  inserted in and removed from the running kernel whenever you want),
   3.673 -  say M here and read <file:Documentation/modules.txt> and
   3.674 -  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
   3.675 -  Do not compile this driver as a module if your root file system (the
   3.676 -  one containing the directory /) is located on an IDE device.
   3.677 -
   3.678 -  If you have one or more IDE drives, say Y or M here. If your system
   3.679 -  has no IDE drives, or if memory requirements are really tight, you
   3.680 -  could say N here, and select the "Old hard disk driver" below
   3.681 -  instead to save about 13 KB of memory in the kernel.
   3.682 -
   3.683 -Old hard disk (MFM/RLL/IDE) driver
   3.684 -CONFIG_BLK_DEV_HD_ONLY
   3.685 -  There are two drivers for MFM/RLL/IDE hard disks. Most people use
   3.686 -  the newer enhanced driver, but this old one is still around for two
   3.687 -  reasons. Some older systems have strange timing problems and seem to
   3.688 -  work only with the old driver (which itself does not work with some
   3.689 -  newer systems). The other reason is that the old driver is smaller,
   3.690 -  since it lacks the enhanced functionality of the new one. This makes
   3.691 -  it a good choice for systems with very tight memory restrictions, or
   3.692 -  for systems with only older MFM/RLL/ESDI drives. Choosing the old
   3.693 -  driver can save 13 KB or so of kernel memory.
   3.694 -
   3.695 -  If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
   3.696 -  instead of this one. For more detailed information, read the
   3.697 -  Disk-HOWTO, available from
   3.698 -  <http://www.tldp.org/docs.html#howto>.
   3.699 -
   3.700 -Use old disk-only driver on primary interface
   3.701 -CONFIG_BLK_DEV_HD_IDE
   3.702 -  There are two drivers for MFM/RLL/IDE disks.  Most people use just
   3.703 -  the new enhanced driver by itself.  This option however installs the
   3.704 -  old hard disk driver to control the primary IDE/disk interface in
   3.705 -  the system, leaving the new enhanced IDE driver to take care of only
   3.706 -  the 2nd/3rd/4th IDE interfaces.  Doing this will prevent you from
   3.707 -  having an IDE/ATAPI CD-ROM or tape drive connected to the primary
   3.708 -  IDE interface.  Choosing this option may be useful for older systems
   3.709 -  which have MFM/RLL/ESDI controller+drives at the primary port
   3.710 -  address (0x1f0), along with IDE drives at the secondary/3rd/4th port
   3.711 -  addresses.
   3.712 -
   3.713 -  Normally, just say N here; you will then use the new driver for all
   3.714 -  4 interfaces.
   3.715 -
   3.716 -Include IDE/ATA-2 DISK support
   3.717 -CONFIG_BLK_DEV_IDEDISK
   3.718 -  This will include enhanced support for MFM/RLL/IDE hard disks.  If
   3.719 -  you have a MFM/RLL/IDE disk, and there is no special reason to use
   3.720 -  the old hard disk driver instead, say Y.  If you have an SCSI-only
   3.721 -  system, you can say N here.
   3.722 -
   3.723 -  If you want to compile this driver as a module ( = code which can be
   3.724 -  inserted in and removed from the running kernel whenever you want),
   3.725 -  say M here and read <file:Documentation/modules.txt>.  The module
   3.726 -  will be called ide-disk.o.  Do not compile this driver as a module
   3.727 -  if your root file system (the one containing the directory /) is
   3.728 -  located on the IDE disk. If unsure, say Y.
   3.729 -
   3.730 -Use multi-mode by default
   3.731 -CONFIG_IDEDISK_MULTI_MODE
   3.732 -  If you get this error, try to say Y here:
   3.733 -
   3.734 -  hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
   3.735 -  hda: set_multmode: error=0x04 { DriveStatusError }
   3.736 -
   3.737 -  If in doubt, say N.
   3.738 -
   3.739 -PCMCIA IDE support
   3.740 -CONFIG_BLK_DEV_IDECS
   3.741 -  Support for outboard IDE disks, tape drives, and CD-ROM drives
   3.742 -  connected through a  PCMCIA card.
   3.743 -
   3.744 -  This driver is also available as a module ( = code which can be
   3.745 -  inserted in and removed from the running kernel whenever you want).
   3.746 -  If you want to compile it as a module, say M here and read
   3.747 -  <file:Documentation/modules.txt>. The module will be called
   3.748 -  ide-cs.o
   3.749 -
   3.750 -Include IDE/ATAPI CD-ROM support
   3.751 -CONFIG_BLK_DEV_IDECD
   3.752 -  If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
   3.753 -  a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
   3.754 -  SCSI protocol. Most new CD-ROM drives use ATAPI, including the
   3.755 -  NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
   3.756 -  double(2X) or better speed drives.
   3.757 -
   3.758 -  If you say Y here, the CD-ROM drive will be identified at boot time
   3.759 -  along with other IDE devices, as "hdb" or "hdc", or something
   3.760 -  similar (check the boot messages with dmesg). If this is your only
   3.761 -  CD-ROM drive, you can say N to all other CD-ROM options, but be sure
   3.762 -  to say Y or M to "ISO 9660 CD-ROM file system support".
   3.763 -
   3.764 -  Note that older versions of LILO (LInux LOader) cannot properly deal
   3.765 -  with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
   3.766 -  <ftp://brun.dyndns.org/pub/linux/lilo/>.
   3.767 -
   3.768 -  If you want to compile the driver as a module ( = code which can be
   3.769 -  inserted in and removed from the running kernel whenever you want),
   3.770 -  say M here and read <file:Documentation/modules.txt>.  The module
   3.771 -  will be called ide-cd.o.
   3.772 -
   3.773 -Include IDE/ATAPI TAPE support
   3.774 -CONFIG_BLK_DEV_IDETAPE
   3.775 -  If you have an IDE tape drive using the ATAPI protocol, say Y.
   3.776 -  ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
   3.777 -  similar to the SCSI protocol.  If you have an SCSI tape drive
   3.778 -  however, you can say N here.
   3.779 -
   3.780 -  You should also say Y if you have an OnStream DI-30 tape drive; this
   3.781 -  will not work with the SCSI protocol, until there is support for the
   3.782 -  SC-30 and SC-50 versions.
   3.783 -
   3.784 -  If you say Y here, the tape drive will be identified at boot time
   3.785 -  along with other IDE devices, as "hdb" or "hdc", or something
   3.786 -  similar, and will be mapped to a character device such as "ht0"
   3.787 -  (check the boot messages with dmesg).  Be sure to consult the
   3.788 -  <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
   3.789 -  for usage information.
   3.790 -
   3.791 -  If you want to compile the driver as a module ( = code which can be
   3.792 -  inserted in and removed from the running kernel whenever you want),
   3.793 -  say M here and read <file:Documentation/modules.txt>.  The module
   3.794 -  will be called ide-tape.o.
   3.795 -
   3.796 -Include IDE/ATAPI FLOPPY support
   3.797 -CONFIG_BLK_DEV_IDEFLOPPY
   3.798 -  If you have an IDE floppy drive which uses the ATAPI protocol,
   3.799 -  answer Y.  ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
   3.800 -  drives, similar to the SCSI protocol.
   3.801 -
   3.802 -  The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
   3.803 -  this driver. For information about jumper settings and the question
   3.804 -  of when a ZIP drive uses a partition table, see
   3.805 -  <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
   3.806 -  (ATAPI PD-CD/CDR drives are not supported by this driver; support
   3.807 -  for PD-CD/CDR drives is available if you answer Y to
   3.808 -  "SCSI emulation support", below).
   3.809 -
   3.810 -  If you say Y here, the FLOPPY drive will be identified along with
   3.811 -  other IDE devices, as "hdb" or "hdc", or something similar (check
   3.812 -  the boot messages with dmesg).
   3.813 -
   3.814 -  If you want to compile the driver as a module ( = code which can be
   3.815 -  inserted in and removed from the running kernel whenever you want),
   3.816 -  say M here and read <file:Documentation/modules.txt>.  The module
   3.817 -  will be called ide-floppy.o.
   3.818 -
   3.819 -AWARD Bios Work-Around
   3.820 -CONFIG_IDEDISK_STROKE
   3.821 -  Should you have a system w/ an AWARD Bios and your drives are larger
   3.822 -  than 32GB and it will not boot, one is required to perform a few OEM
   3.823 -  operations first.  The option is called "STROKE" because it allows
   3.824 -  one to "soft clip" the drive to work around a barrier limit.  For
   3.825 -  Maxtor drives it is called "jumpon.exe".  Please search Maxtor's
   3.826 -  web-site for "JUMPON.EXE".  IBM has a similar tool at:
   3.827 -  <http://www.storage.ibm.com/hdd/support/download.htm>.
   3.828 -
   3.829 -  If you are unsure, say N here.
   3.830 -
   3.831 -Raw Access to Media
   3.832 -CONFIG_IDE_TASK_IOCTL
   3.833 -  This is a direct raw access to the media.  It is a complex but
   3.834 -  elegant solution to test and validate the domain of the hardware and
   3.835 -  perform below the driver data recover if needed.  This is the most
   3.836 -  basic form of media-forensics.
   3.837 -
   3.838 -  If you are unsure, say N here.
   3.839 -
   3.840 -Use Taskfile I/O
   3.841 -CONFIG_IDE_TASKFILE_IO
   3.842 -  This is the "Jewel" of the patch.  It will go away and become the new
   3.843 -  driver core.  Since all the chipsets/host side hardware deal w/ their
   3.844 -  exceptions in "their local code" currently, adoption of a
   3.845 -  standardized data-transport is the only logical solution.
   3.846 -  Additionally we packetize the requests and gain rapid performance and
   3.847 -  a reduction in system latency.  Additionally by using a memory struct
   3.848 -  for the commands we can redirect to a MMIO host hardware in the next
   3.849 -  generation of controllers, specifically second generation Ultra133
   3.850 -  and Serial ATA.
   3.851 -
   3.852 -  Since this is a major transition, it was deemed necessary to make the
   3.853 -  driver paths buildable in separate models.  Therefore if using this
   3.854 -  option fails for your arch then we need to address the needs for that
   3.855 -  arch.
   3.856 -
   3.857 -  If you want to test this functionality, say Y here.
   3.858 -
   3.859 -Force DMA
   3.860 -CONFIG_BLK_DEV_IDEDMA_FORCED
   3.861 -  This is an old piece of lost code from Linux 2.0 Kernels.
   3.862 -
   3.863 -  Generally say N here.
   3.864 -
   3.865 -DMA Only on Disks
   3.866 -CONFIG_IDEDMA_ONLYDISK
   3.867 -  This is used if you know your ATAPI Devices are going to fail DMA
   3.868 -  Transfers.
   3.869 -
   3.870 -  Generally say N here.
   3.871 -
   3.872 -SCSI emulation support
   3.873 -CONFIG_BLK_DEV_IDESCSI
   3.874 -  This will provide SCSI host adapter emulation for IDE ATAPI devices,
   3.875 -  and will allow you to use a SCSI device driver instead of a native
   3.876 -  ATAPI driver.
   3.877 -
   3.878 -  This is useful if you have an ATAPI device for which no native
   3.879 -  driver has been written (for example, an ATAPI PD-CD or CDR drive);
   3.880 -  you can then use this emulation together with an appropriate SCSI
   3.881 -  device driver. In order to do this, say Y here and to "SCSI support"
   3.882 -  and "SCSI generic support", below. You must then provide the kernel
   3.883 -  command line "hdx=scsi" (try "man bootparam" or see the
   3.884 -  documentation of your boot loader (lilo or loadlin) about how to
   3.885 -  pass options to the kernel at boot time) for devices if you want the
   3.886 -  native EIDE sub-drivers to skip over the native support, so that
   3.887 -  this SCSI emulation can be used instead. This is required for use of
   3.888 -  CD-RW's.
   3.889 -
   3.890 -  Note that this option does NOT allow you to attach SCSI devices to a
   3.891 -  box that doesn't have a SCSI host adapter installed.
   3.892 -
   3.893 -  If both this SCSI emulation and native ATAPI support are compiled
   3.894 -  into the kernel, the native support will be used.
   3.895 -
   3.896 -  This driver is also available as a module ( = code which can be
   3.897 -  inserted in and removed from the running kernel whenever you want).
   3.898 -  If you want to compile it as a module, say M here and read
   3.899 -  <file:Documentation/modules.txt>. The module will be called
   3.900 -  ide-scsi.o
   3.901 -
   3.902 -Use the NOOP Elevator (WARNING)
   3.903 -CONFIG_BLK_DEV_ELEVATOR_NOOP
   3.904 -  If you are using a raid class top-level driver above the ATA/IDE core,
   3.905 -  one may find a performance boost by preventing a merging and re-sorting
   3.906 -  of the new requests.
   3.907 -
   3.908 -  If unsure, say N.
   3.909 -
   3.910 -ISA-PNP EIDE support
   3.911 -CONFIG_BLK_DEV_ISAPNP
   3.912 -  If you have an ISA EIDE card that is PnP (Plug and Play) and
   3.913 -  requires setup first before scanning for devices, say Y here.
   3.914 -
   3.915 -  If unsure, say N.
   3.916 -
   3.917 -CMD640 chipset bugfix/support
   3.918 -CONFIG_BLK_DEV_CMD640
   3.919 -  The CMD-Technologies CMD640 IDE chip is used on many common 486 and
   3.920 -  Pentium motherboards, usually in combination with a "Neptune" or
   3.921 -  "SiS" chipset. Unfortunately, it has a number of rather nasty
   3.922 -  design flaws that can cause severe data corruption under many common
   3.923 -  conditions. Say Y here to include code which tries to automatically
   3.924 -  detect and correct the problems under Linux. This option also
   3.925 -  enables access to the secondary IDE ports in some CMD640 based
   3.926 -  systems.
   3.927 -
   3.928 -  This driver will work automatically in PCI based systems (most new
   3.929 -  systems have PCI slots). But if your system uses VESA local bus
   3.930 -  (VLB) instead of PCI, you must also supply a kernel boot parameter
   3.931 -  to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
   3.932 -  bootparam" or see the documentation of your boot loader about how to
   3.933 -  pass options to the kernel.)
   3.934 -
   3.935 -  The CMD640 chip is also used on add-in cards by Acculogic, and on
   3.936 -  the "CSA-6400E PCI to IDE controller" that some people have. For
   3.937 -  details, read <file:Documentation/ide.txt>.
   3.938 -
   3.939 -CMD640 enhanced support
   3.940 -CONFIG_BLK_DEV_CMD640_ENHANCED
   3.941 -  This option includes support for setting/autotuning PIO modes and
   3.942 -  prefetch on CMD640 IDE interfaces.  For details, read
   3.943 -  <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
   3.944 -  and your BIOS does not already do this for you, then say Y here.
   3.945 -  Otherwise say N.
   3.946 -
   3.947 -RZ1000 chipset bugfix/support
   3.948 -CONFIG_BLK_DEV_RZ1000
   3.949 -  The PC-Technologies RZ1000 IDE chip is used on many common 486 and
   3.950 -  Pentium motherboards, usually along with the "Neptune" chipset.
   3.951 -  Unfortunately, it has a rather nasty design flaw that can cause
   3.952 -  severe data corruption under many conditions. Say Y here to include
   3.953 -  code which automatically detects and corrects the problem under
   3.954 -  Linux. This may slow disk throughput by a few percent, but at least
   3.955 -  things will operate 100% reliably.
   3.956 -
   3.957 -Generic PCI IDE chipset support
   3.958 -CONFIG_BLK_DEV_IDEPCI
   3.959 -  Say Y here for PCI systems which use IDE drive(s).
   3.960 -  This option helps the IDE driver to automatically detect and
   3.961 -  configure all PCI-based IDE interfaces in your system.
   3.962 -
   3.963 -Support for sharing PCI IDE interrupts
   3.964 -CONFIG_IDEPCI_SHARE_IRQ
   3.965 -  Some ATA/IDE chipsets have hardware support which allows for
   3.966 -  sharing a single IRQ with other cards. To enable support for
   3.967 -  this in the ATA/IDE driver, say Y here.
   3.968 -
   3.969 -  It is safe to say Y to this question, in most cases.
   3.970 -  If unsure, say N.
   3.971 -
   3.972 -Generic PCI bus-master DMA support
   3.973 -CONFIG_BLK_DEV_IDEDMA_PCI
   3.974 -  If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
   3.975 -  is capable of bus-master DMA operation (most Pentium PCI systems),
   3.976 -  you will want to say Y here to reduce CPU overhead. You can then use
   3.977 -  the "hdparm" utility to enable DMA for drives for which it was not
   3.978 -  enabled automatically. By default, DMA is not enabled automatically
   3.979 -  for these drives, but you can change that by saying Y to the
   3.980 -  following question "Use DMA by default when available". You can get
   3.981 -  the latest version of the hdparm utility from
   3.982 -  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   3.983 -
   3.984 -  Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
   3.985 -  and the file <file:Documentation/ide.txt> for more information.
   3.986 -
   3.987 -  It is safe to say Y to this question.
   3.988 -
   3.989 -Good-Bad DMA Model-Firmware (WIP)
   3.990 -CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
   3.991 -  If you say Y here, the model and firmware revision of your drive
   3.992 -  will be compared against a blacklist of buggy drives that claim to
   3.993 -  be (U)DMA capable but aren't. This is a blanket on/off test with no
   3.994 -  speed limit options.
   3.995 -
   3.996 -  Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
   3.997 -  whereas, many versions of EGCS have a problem and miscompile if you
   3.998 -  say Y here.
   3.999 -
  3.1000 -  If in doubt, say N.
  3.1001 -
  3.1002 -Attempt to HACK around Chipsets that TIMEOUT (WIP)
  3.1003 -CONFIG_BLK_DEV_IDEDMA_TIMEOUT
  3.1004 -  If you say Y here, this is a NASTY UGLY HACK!
  3.1005 -
  3.1006 -  We have to issue an abort and requeue the request DMA engine got
  3.1007 -  turned off by a goofy ASIC, and we have to clean up the mess, and
  3.1008 -  here is as good as any.  Do it globally for all chipsets.
  3.1009 -
  3.1010 -  If in doubt, say N.
  3.1011 -
  3.1012 -Boot off-board chipsets first support
  3.1013 -CONFIG_BLK_DEV_OFFBOARD
  3.1014 -  Normally, IDE controllers built into the motherboard (on-board
  3.1015 -  controllers) are assigned to ide0 and ide1 while those on add-in PCI
  3.1016 -  cards (off-board controllers) are relegated to ide2 and ide3.
  3.1017 -  Answering Y here will allow you to reverse the situation, with
  3.1018 -  off-board controllers on ide0/1 and on-board controllers on ide2/3.
  3.1019 -  This can improve the usability of some boot managers such as lilo
  3.1020 -  when booting from a drive on an off-board controller.
  3.1021 -
  3.1022 -  If you say Y here, and you actually want to reverse the device scan
  3.1023 -  order as explained above, you also need to issue the kernel command
  3.1024 -  line option "ide=reverse". (Try "man bootparam" or see the
  3.1025 -  documentation of your boot loader (lilo or loadlin) about how to
  3.1026 -  pass options to the kernel at boot time.)
  3.1027 -
  3.1028 -  Note that, if you do this, the order of the hd* devices will be
  3.1029 -  rearranged which may require modification of fstab and other files.
  3.1030 -
  3.1031 -  If in doubt, say N.
  3.1032 -
  3.1033 -Use PCI DMA by default when available
  3.1034 -CONFIG_IDEDMA_PCI_AUTO
  3.1035 -  Prior to kernel version 2.1.112, Linux used to automatically use
  3.1036 -  DMA for IDE drives and chipsets which support it. Due to concerns
  3.1037 -  about a couple of cases where buggy hardware may have caused damage,
  3.1038 -  the default is now to NOT use DMA automatically. To revert to the
  3.1039 -  previous behaviour, say Y to this question.
  3.1040 -
  3.1041 -  If you suspect your hardware is at all flakey, say N here.
  3.1042 -  Do NOT email the IDE kernel people regarding this issue!
  3.1043 -
  3.1044 -  It is normally safe to answer Y to this question unless your
  3.1045 -  motherboard uses a VIA VP2 chipset, in which case you should say N.
  3.1046 -
  3.1047 -IGNORE word93 Validation BITS
  3.1048 -CONFIG_IDEDMA_IVB
  3.1049 -  There are unclear terms in ATA-4 and ATA-5 standards how certain
  3.1050 -  hardware (an 80c ribbon) should be detected. Different interpretations
  3.1051 -  of the standards have been released in hardware. This causes problems:
  3.1052 -  for example, a host with Ultra Mode 4 (or higher) will not run
  3.1053 -  in that mode with an 80c ribbon.
  3.1054 -
  3.1055 -  If you are experiencing compatibility or performance problems, you
  3.1056 -  MAY try to answering Y here. However, it does not necessarily solve
  3.1057 -  any of your problems, it could even cause more of them.
  3.1058 -
  3.1059 -  It is normally safe to answer Y; however, the default is N.
  3.1060 -
  3.1061 -ATA Work(s) In Progress (EXPERIMENTAL)
  3.1062 -CONFIG_IDEDMA_PCI_WIP
  3.1063 -  If you enable this you will be able to use and test highly
  3.1064 -  developmental projects. If you say N, the configurator will
  3.1065 -  simply skip those options.
  3.1066 -
  3.1067 -  It is SAFEST to say N to this question.
  3.1068 -
  3.1069 -Asynchronous DMA support (EXPERIMENTAL)
  3.1070 -CONFIG_BLK_DEV_ADMA
  3.1071 -  Please read the comments at the top of
  3.1072 -  <file:drivers/ide/ide-adma.c>.
  3.1073 -
  3.1074 -Pacific Digital A-DMA support (EXPERIMENTAL)
  3.1075 -CONFIG_BLK_DEV_PDC_ADMA
  3.1076 -  Please read the comments at the top of <file:drivers/ide/setup-pci.c>.
  3.1077 -
  3.1078 -3ware Hardware ATA-RAID support
  3.1079 -CONFIG_BLK_DEV_3W_XXXX_RAID
  3.1080 -  3ware is the only hardware ATA-Raid product in Linux to date.
  3.1081 -  This card is 2,4, or 8 channel master mode support only.
  3.1082 -  SCSI support required!!!
  3.1083 -
  3.1084 -  <http://www.3ware.com/>
  3.1085 -
  3.1086 -  Please read the comments at the top of
  3.1087 -  <file:drivers/scsi/3w-xxxx.c>.
  3.1088 -
  3.1089 -  If you want to compile the driver as a module ( = code which can be
  3.1090 -  inserted in and removed from the running kernel whenever you want),
  3.1091 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.1092 -  will be called 3w-xxxx.o.
  3.1093 -
  3.1094 -AEC62XX chipset support
  3.1095 -CONFIG_BLK_DEV_AEC62XX
  3.1096 -  This driver adds up to 4 more EIDE devices sharing a single
  3.1097 -  interrupt. This add-on card is a bootable PCI UDMA controller. In
  3.1098 -  order to get this card to initialize correctly in some cases, you
  3.1099 -  should say Y here, and preferably also to "Use DMA by default when
  3.1100 -  available".
  3.1101 -
  3.1102 -  The ATP850U/UF is an UltraDMA 33 chipset base.
  3.1103 -  The ATP860 is an UltraDMA 66 chipset base.
  3.1104 -  The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
  3.1105 -
  3.1106 -  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  3.1107 -  If you say Y here, then say Y to "Use DMA by default when available"
  3.1108 -  as well.
  3.1109 -
  3.1110 -AEC62XX Tuning support
  3.1111 -CONFIG_AEC62XX_TUNING
  3.1112 -  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  3.1113 -  If unsure, say N.
  3.1114 -
  3.1115 -ALI M15x3 chipset support
  3.1116 -CONFIG_BLK_DEV_ALI15X3
  3.1117 -  This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
  3.1118 -  onboard chipsets.  It also tests for Simplex mode and enables
  3.1119 -  normal dual channel support.
  3.1120 -
  3.1121 -  If you say Y here, you also need to say Y to "Use DMA by default
  3.1122 -  when available", above.  Please read the comments at the top of
  3.1123 -  <file:drivers/ide/pci/alim15x3.c>.
  3.1124 -
  3.1125 -  If unsure, say N.
  3.1126 -
  3.1127 -ALI M15x3 WDC support (DANGEROUS)
  3.1128 -CONFIG_WDC_ALI15X3
  3.1129 -  This allows for UltraDMA support for WDC drives that ignore CRC
  3.1130 -  checking. You are a fool for enabling this option, but there have
  3.1131 -  been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
  3.1132 -  YOU ENABLE THIS! No one will listen, just laugh for ignoring this
  3.1133 -  SERIOUS WARNING.
  3.1134 -
  3.1135 -  Using this option can allow WDC drives to run at ATA-4/5 transfer
  3.1136 -  rates with only an ATA-2 support structure.
  3.1137 -
  3.1138 -  SAY N!
  3.1139 -
  3.1140 -AMD and nVidia IDE support
  3.1141 -CONFIG_BLK_DEV_AMD74XX
  3.1142 -  This driver adds explicit support for AMD-7xx and AMD-8111 chips
  3.1143 -  and also for the nVidia nForce chip.  This allows the kernel to
  3.1144 -  change PIO, DMA and UDMA speeds and to configure the chip to
  3.1145 -  optimum performance.
  3.1146 -
  3.1147 -  If you say Y here, you also need to say Y to "Use DMA by default
  3.1148 -  when available", above.
  3.1149 -  Please read the comments at the top of <file:drivers/ide/pci/amd74xx.c>.
  3.1150 -
  3.1151 -  If unsure, say N.
  3.1152 -
  3.1153 -AMD Viper ATA-66 Override support (WIP)
  3.1154 -CONFIG_AMD74XX_OVERRIDE
  3.1155 -  This option auto-forces the ata66 flag.
  3.1156 -  This effect can be also invoked by calling "idex=ata66"
  3.1157 -  If unsure, say N.
  3.1158 -
  3.1159 -CMD64X/CMD680 chipset support
  3.1160 -CONFIG_BLK_DEV_CMD64X
  3.1161 -  Say Y here if you have an IDE controller which uses any of these
  3.1162 -  chipsets: CMD643, CMD646 and CMD648.
  3.1163 -
  3.1164 -Compaq Triflex IDE support
  3.1165 -CONFIG_BLK_DEV_TRIFLEX
  3.1166 -  Say Y here if you have a Compaq Triflex IDE controller, such
  3.1167 -  as those commonly found on Compaq Pentium-Pro systems
  3.1168 -
  3.1169 -  If you want to compile it as a module, say M here and read
  3.1170 -  <file:Documentation/modules.txt>.  The module will be called
  3.1171 -  triflex.o.
  3.1172 -
  3.1173 -CY82C693 chipset support
  3.1174 -CONFIG_BLK_DEV_CY82C693
  3.1175 -  This driver adds detection and support for the CY82C693 chipset
  3.1176 -  used on Digital's PC-Alpha 164SX boards.
  3.1177 -
  3.1178 -  If you say Y here, you need to say Y to "Use DMA by default
  3.1179 -  when available" as well.
  3.1180 -
  3.1181 -Cyrix CS5530 MediaGX chipset support
  3.1182 -CONFIG_BLK_DEV_CS5530
  3.1183 -  Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
  3.1184 -  will automatically be detected and configured if found.
  3.1185 -
  3.1186 -  It is safe to say Y to this question.
  3.1187 -
  3.1188 -  People with SCSI-only systems should say N here. If unsure, say Y.
  3.1189 -
  3.1190 -HPT34X chipset support
  3.1191 -CONFIG_BLK_DEV_HPT34X
  3.1192 -  This driver adds up to 4 more EIDE devices sharing a single
  3.1193 -  interrupt. The HPT343 chipset in its current form is a non-bootable
  3.1194 -  controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
  3.1195 -  PCI UDMA controllers. This driver requires dynamic tuning of the
  3.1196 -  chipset during the ide-probe at boot time. It is reported to support
  3.1197 -  DVD II drives, by the manufacturer.
  3.1198 -
  3.1199 -HPT34X AUTODMA support (WIP)
  3.1200 -CONFIG_HPT34X_AUTODMA
  3.1201 -  This is a dangerous thing to attempt currently! Please read the
  3.1202 -  comments at the top of <file:drivers/ide/pci/hpt34x.c>.  If you say Y
  3.1203 -  here, then say Y to "Use DMA by default when available" as well.
  3.1204 -
  3.1205 -  If unsure, say N.
  3.1206 -
  3.1207 -HPT36X/37X chipset support
  3.1208 -CONFIG_BLK_DEV_HPT366
  3.1209 -  HPT366 is an Ultra DMA chipset for ATA-66.
  3.1210 -  HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
  3.1211 -  HPT370 is an Ultra DMA chipset for ATA-100.
  3.1212 -  HPT372 is an Ultra DMA chipset for ATA-133.
  3.1213 -  HPT374 is an Ultra DMA chipset for ATA-133.
  3.1214 -
  3.1215 -  This driver adds up to 4 more EIDE devices sharing a single
  3.1216 -  interrupt.
  3.1217 -
  3.1218 -  The HPT366 chipset in its current form is bootable. One solution
  3.1219 -  for this problem are special LILO commands for redirecting the
  3.1220 -  reference to device 0x80. The other solution is to say Y to "Boot
  3.1221 -  off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
  3.1222 -  your mother board has the chipset natively mounted. Regardless one
  3.1223 -  should use the fore mentioned option and call at LILO or include
  3.1224 -  "ide=reverse" in LILO's append-line.
  3.1225 -
  3.1226 -  This driver requires dynamic tuning of the chipset during the
  3.1227 -  ide-probe at boot. It is reported to support DVD II drives, by the
  3.1228 -  manufacturer.
  3.1229 -
  3.1230 -NS87415 chipset support (EXPERIMENTAL)
  3.1231 -CONFIG_BLK_DEV_NS87415
  3.1232 -  This driver adds detection and support for the NS87415 chip
  3.1233 -  (used in SPARC64, among others).
  3.1234 -
  3.1235 -  Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
  3.1236 -
  3.1237 -OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
  3.1238 -CONFIG_BLK_DEV_OPTI621
  3.1239 -  This is a driver for the OPTi 82C621 EIDE controller.
  3.1240 -  Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
  3.1241 -
  3.1242 -National SCx200 chipset support
  3.1243 -CONFIG_BLK_DEV_SC1200
  3.1244 -  This driver adds support for the built in IDE on the National
  3.1245 -  SCx200 series of embedded x86 "Geode" systems
  3.1246 -
  3.1247 -  If you want to compile it as a module, say M here and read
  3.1248 -  <file:Documentation/modules.txt>.  The module will be called
  3.1249 -  sc1200.o.
  3.1250 -
  3.1251 -ServerWorks OSB4/CSB5 chipset support
  3.1252 -CONFIG_BLK_DEV_SVWKS
  3.1253 -  This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
  3.1254 -  chipsets.
  3.1255 -
  3.1256 -SGI IOC4 chipset support
  3.1257 -CONFIG_BLK_DEV_SGIIOC4
  3.1258 -  This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
  3.1259 -  chipset.  Please say Y here, if you have an Altix System from
  3.1260 -  Silicon Graphics Inc.
  3.1261 -
  3.1262 -Intel PIIXn chipsets support
  3.1263 -CONFIG_BLK_DEV_PIIX
  3.1264 -  This driver adds PIO mode setting and tuning for all PIIX IDE
  3.1265 -  controllers by Intel.  Since the BIOS can sometimes improperly tune
  3.1266 -  PIO 0-4 mode settings, this allows dynamic tuning of the chipset
  3.1267 -  via the standard end-user tool 'hdparm'.
  3.1268 -
  3.1269 -  Please read the comments at the top of <file:drivers/ide/pci/piix.c>.
  3.1270 -
  3.1271 -  If you say Y here, you should also say Y to "PIIXn Tuning support",
  3.1272 -  below.
  3.1273 -
  3.1274 -  If unsure, say N.
  3.1275 -
  3.1276 -PIIXn Tuning support
  3.1277 -CONFIG_PIIX_TUNING
  3.1278 -  This driver extension adds DMA mode setting and tuning for all PIIX
  3.1279 -  IDE controllers by Intel. Since the BIOS can sometimes improperly
  3.1280 -  set up the device/adapter combination and speed limits, it has
  3.1281 -  become a necessity to back/forward speed devices as needed.
  3.1282 -
  3.1283 -  Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
  3.1284 -  2 if the BIOS can not perform this task at initialization.
  3.1285 -
  3.1286 -  If unsure, say N.
  3.1287 -
  3.1288 -PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
  3.1289 -CONFIG_BLK_DEV_PDC202XX_OLD
  3.1290 -  Promise Ultra33 or PDC20246
  3.1291 -  Promise Ultra66 or PDC20262
  3.1292 -  Promise Ultra100 or PDC20265/PDC20267/PDC20268
  3.1293 -
  3.1294 -  This driver adds up to 4 more EIDE devices sharing a single
  3.1295 -  interrupt. This add-on card is a bootable PCI UDMA controller. Since
  3.1296 -  multiple cards can be installed and there are BIOS ROM problems that
  3.1297 -  happen if the BIOS revisions of all installed cards (three-max) do
  3.1298 -  not match, the driver attempts to do dynamic tuning of the chipset
  3.1299 -  at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
  3.1300 -  for more than one card. This card may require that you say Y to
  3.1301 -  "Special UDMA Feature".
  3.1302 -
  3.1303 -  If you say Y here, you need to say Y to "Use DMA by default when
  3.1304 -  available" as well.
  3.1305 -
  3.1306 -  Please read the comments at the top of
  3.1307 -  <file:drivers/ide/pci/pdc202xx_old.c>.
  3.1308 -
  3.1309 -  If unsure, say N.
  3.1310 -
  3.1311 -PROMISE PDC202{68|69|70|71|75|76|77} support
  3.1312 -CONFIG_BLK_DEV_PDC202XX_NEW
  3.1313 -  Promise Ultra 100 TX2 [PDC20268]
  3.1314 -  Promise Ultra 133 PTX2 [PDC20269]
  3.1315 -  Promise FastTrak LP/TX2/TX4 [PDC20270]
  3.1316 -  Promise FastTrak TX2000 [PDC20271]
  3.1317 -  Promise MB Ultra 133 [PDC20275]
  3.1318 -  Promise MB FastTrak 133 [PDC20276]
  3.1319 -  Promise FastTrak 133 [PDC20277]
  3.1320 -
  3.1321 -  This driver adds up to 4 more EIDE devices sharing a single
  3.1322 -  interrupt. This device is a bootable PCI UDMA controller. Since
  3.1323 -  multiple cards can be installed and there are BIOS ROM problems that
  3.1324 -  happen if the BIOS revisions of all installed cards (max of five) do
  3.1325 -  not match, the driver attempts to do dynamic tuning of the chipset
  3.1326 -  at boot-time for max speed.  Ultra33 BIOS 1.25 or newer is required
  3.1327 -  for more than one card.
  3.1328 -
  3.1329 -  If you say Y here, you need to say Y to "Use DMA by default when
  3.1330 -  available" as well.
  3.1331 -
  3.1332 -  If unsure, say N.
  3.1333 -
  3.1334 -Special UDMA Feature
  3.1335 -CONFIG_PDC202XX_BURST
  3.1336 -  This option causes the pdc202xx driver to enable UDMA modes on the
  3.1337 -  PDC202xx even when the PDC202xx BIOS has not done so.
  3.1338 -
  3.1339 -  It was originally designed for the PDC20246/Ultra33, whose BIOS will
  3.1340 -  only setup UDMA on the first two PDC20246 cards.  It has also been
  3.1341 -  used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
  3.1342 -  when the PDC20265 BIOS has been disabled (for faster boot up).
  3.1343 -
  3.1344 -  Please read the comments at the top of
  3.1345 -  <file:drivers/ide/pci/pdc202xx_old.c>.
  3.1346 -
  3.1347 -  If unsure, say N.
  3.1348 -
  3.1349 -Special FastTrak Feature
  3.1350 -CONFIG_PDC202XX_FORCE
  3.1351 -  For FastTrak enable overriding BIOS.
  3.1352 -
  3.1353 -SiS5513 chipset support
  3.1354 -CONFIG_BLK_DEV_SIS5513
  3.1355 -  This driver ensures (U)DMA support for SIS5513 chipset family based
  3.1356 -  mainboards.
  3.1357 -
  3.1358 -  The following chipsets are supported:
  3.1359 -  ATA16:  SiS5511, SiS5513
  3.1360 -  ATA33:  SiS5591, SiS5597, SiS5598, SiS5600
  3.1361 -  ATA66:  SiS530, SiS540, SiS620, SiS630, SiS640
  3.1362 -  ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
  3.1363 -          SiS745, SiS750
  3.1364 -
  3.1365 -  If you say Y here, you need to say Y to "Use DMA by default when
  3.1366 -  available" as well.
  3.1367 -
  3.1368 -  Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
  3.1369 -
  3.1370 -Silicon Image chipset support
  3.1371 -CONFIG_BLK_DEV_SIIMAGE
  3.1372 -  This driver provides (U)DMA support for the SII3112 SATA controllers and
  3.1373 -  for the CMD/SI680 UDMA/DMA ATA controller.
  3.1374 -
  3.1375 -SLC90E66 chipset support
  3.1376 -CONFIG_BLK_DEV_SLC90E66
  3.1377 -  This driver ensures (U)DMA support for Victroy66 SouthBridges for
  3.1378 -  SMsC with Intel NorthBridges.  This is an Ultra66 based chipset.
  3.1379 -  The nice thing about it is that you can mix Ultra/DMA/PIO devices
  3.1380 -  and it will handle timing cycles.  Since this is an improved
  3.1381 -  look-a-like to the PIIX4 it should be a nice addition.
  3.1382 -
  3.1383 -  If you say Y here, you need to say Y to "Use DMA by default when
  3.1384 -  available" as well.
  3.1385 -
  3.1386 -  Please read the comments at the top of
  3.1387 -  <file:drivers/ide/pci/slc90e66.c>.
  3.1388 -
  3.1389 -Winbond SL82c105 support
  3.1390 -CONFIG_BLK_DEV_SL82C105
  3.1391 -  If you have a Winbond SL82c105 IDE controller, say Y here to enable
  3.1392 -  special configuration for this chip. This is common on various CHRP
  3.1393 -  motherboards, but could be used elsewhere. If in doubt, say Y.
  3.1394 -
  3.1395 -Tekram TRM290 chipset support
  3.1396 -CONFIG_BLK_DEV_TRM290
  3.1397 -  This driver adds support for bus master DMA transfers
  3.1398 -  using the Tekram TRM290 PCI IDE chip. Volunteers are
  3.1399 -  needed for further tweaking and development.
  3.1400 -  Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
  3.1401 -
  3.1402 -VIA82CXXX chipset support
  3.1403 -CONFIG_BLK_DEV_VIA82CXXX
  3.1404 -  This allows you to configure your chipset for a better use while
  3.1405 -  running PIO/(U)DMA, it will allow you to enable efficiently the
  3.1406 -  second channel dma usage, as it may not be set by BIOS.  It will try
  3.1407 -  to set fifo configuration at its best.  It will allow you to get
  3.1408 -  information from /proc/ide/via provided you enabled "/proc file
  3.1409 -  system" support.
  3.1410 -
  3.1411 -  Please read the comments at the top of
  3.1412 -  <file:drivers/ide/pci/via82cxxx.c>.
  3.1413 -
  3.1414 -  If you say Y here, then say Y to "Use DMA by default when available"
  3.1415 -  as well.
  3.1416 -
  3.1417 -  If unsure, say N.
  3.1418 -
  3.1419 -RapIDE interface support
  3.1420 -CONFIG_BLK_DEV_IDE_RAPIDE
  3.1421 -  Say Y here if you want to support the Yellowstone RapIDE controller
  3.1422 -  manufactured for use with Acorn computers.
  3.1423 -
  3.1424 -Other IDE chipset support
  3.1425 -CONFIG_IDE_CHIPSETS
  3.1426 -  Say Y here if you want to include enhanced support for various IDE
  3.1427 -  interface chipsets used on motherboards and add-on cards. You can
  3.1428 -  then pick your particular IDE chip from among the following options.
  3.1429 -  This enhanced support may be necessary for Linux to be able to
  3.1430 -  access the 3rd/4th drives in some systems. It may also enable
  3.1431 -  setting of higher speed I/O rates to improve system performance with
  3.1432 -  these chipsets. Most of these also require special kernel boot
  3.1433 -  parameters to actually turn on the support at runtime; you can find
  3.1434 -  a list of these in the file <file:Documentation/ide.txt>.
  3.1435 -
  3.1436 -  People with SCSI-only systems can say N here.
  3.1437 -
  3.1438 -Generic 4 drives/port support
  3.1439 -CONFIG_BLK_DEV_4DRIVES
  3.1440 -  Certain older chipsets, including the Tekram 690CD, use a single set
  3.1441 -  of I/O ports at 0x1f0 to control up to four drives, instead of the
  3.1442 -  customary two drives per port. Support for this can be enabled at
  3.1443 -  runtime using the "ide0=four" kernel boot parameter if you say Y
  3.1444 -  here.
  3.1445 -
  3.1446 -ALI M14xx support
  3.1447 -CONFIG_BLK_DEV_ALI14XX
  3.1448 -  This driver is enabled at runtime using the "ide0=ali14xx" kernel
  3.1449 -  boot parameter.  It enables support for the secondary IDE interface
  3.1450 -  of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
  3.1451 -  I/O speeds to be set as well.  See the files
  3.1452 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
  3.1453 -  more info.
  3.1454 -
  3.1455 -DTC-2278 support
  3.1456 -CONFIG_BLK_DEV_DTC2278
  3.1457 -  This driver is enabled at runtime using the "ide0=dtc2278" kernel
  3.1458 -  boot parameter. It enables support for the secondary IDE interface
  3.1459 -  of the DTC-2278 card, and permits faster I/O speeds to be set as
  3.1460 -  well. See the <file:Documentation/ide.txt> and
  3.1461 -  <file:drivers/ide/legacy/dtc2278.c> files for more info.
  3.1462 -
  3.1463 -Holtek HT6560B support
  3.1464 -CONFIG_BLK_DEV_HT6560B
  3.1465 -  This driver is enabled at runtime using the "ide0=ht6560b" kernel
  3.1466 -  boot parameter. It enables support for the secondary IDE interface
  3.1467 -  of the Holtek card, and permits faster I/O speeds to be set as well.
  3.1468 -  See the <file:Documentation/ide.txt> and
  3.1469 -  <file:drivers/ide/legacy/ht6560b.c> files for more info.
  3.1470 -
  3.1471 -PROMISE DC4030 support (EXPERIMENTAL)
  3.1472 -CONFIG_BLK_DEV_PDC4030
  3.1473 -  This driver provides support for the secondary IDE interface and
  3.1474 -  cache of Promise IDE chipsets, e.g. DC4030 and DC5030.  This driver
  3.1475 -  is known to incur timeouts/retries during heavy I/O to drives
  3.1476 -  attached to the secondary interface.  CD-ROM and TAPE devices are
  3.1477 -  not supported yet.  This driver is enabled at runtime using the
  3.1478 -  "ide0=dc4030" kernel boot parameter.  See the
  3.1479 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/pdc4030.c> files
  3.1480 -  for more info.
  3.1481 -
  3.1482 -QDI QD65XX support
  3.1483 -CONFIG_BLK_DEV_QD65XX
  3.1484 -  This driver is enabled at runtime using the "ide0=qd65xx" kernel
  3.1485 -  boot parameter.  It permits faster I/O speeds to be set.  See the
  3.1486 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
  3.1487 -  more info.
  3.1488 -
  3.1489 -UMC 8672 support
  3.1490 -CONFIG_BLK_DEV_UMC8672
  3.1491 -  This driver is enabled at runtime using the "ide0=umc8672" kernel
  3.1492 -  boot parameter. It enables support for the secondary IDE interface
  3.1493 -  of the UMC-8672, and permits faster I/O speeds to be set as well.
  3.1494 -  See the files <file:Documentation/ide.txt> and
  3.1495 -  <file:drivers/ide/legacy/umc8672.c> for more info.
  3.1496 -
  3.1497 -Amiga Gayle IDE interface support
  3.1498 -CONFIG_BLK_DEV_GAYLE
  3.1499 -  This is the IDE driver for the builtin IDE interface on some Amiga
  3.1500 -  models. It supports both the `A1200 style' (used in A600 and A1200)
  3.1501 -  and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
  3.1502 -  interface. Say Y if you have such an Amiga model and want to use IDE
  3.1503 -  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  3.1504 -  builtin IDE interface.
  3.1505 -
  3.1506 -Falcon IDE interface support
  3.1507 -CONFIG_BLK_DEV_FALCON_IDE
  3.1508 -  This is the IDE driver for the builtin IDE interface on the Atari
  3.1509 -  Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
  3.1510 -  disks, CD-ROM drives, etc.) that are connected to the builtin IDE
  3.1511 -  interface.
  3.1512 -
  3.1513 -Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
  3.1514 -CONFIG_BLK_DEV_BUDDHA
  3.1515 -  This is the IDE driver for the IDE interfaces on the Buddha, 
  3.1516 -  Catweasel and X-Surf expansion boards.  It supports up to two interfaces 
  3.1517 -  on the Buddha, three on the Catweasel and two on the X-Surf.
  3.1518 -
  3.1519 -  Say Y if you have a Buddha or Catweasel expansion board and want to
  3.1520 -  use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
  3.1521 -  to one of its IDE interfaces.
  3.1522 -
  3.1523 -Amiga IDE Doubler support (EXPERIMENTAL)
  3.1524 -CONFIG_BLK_DEV_IDEDOUBLER
  3.1525 -  This driver provides support for the so-called `IDE doublers' (made
  3.1526 -  by various manufacturers, e.g. Eyetech) that can be connected to the
  3.1527 -  builtin IDE interface of some Amiga models. Using such an IDE
  3.1528 -  doubler, you can connect up to four instead of two IDE devices on
  3.1529 -  the Amiga's builtin IDE interface.
  3.1530 -
  3.1531 -  Note that the normal Amiga Gayle IDE driver may not work correctly
  3.1532 -  if you have an IDE doubler and don't enable this driver!
  3.1533 -
  3.1534 -  Say Y if you have an IDE doubler.  The driver is enabled at kernel
  3.1535 -  runtime using the "ide=doubler" kernel boot parameter.
  3.1536 -
  3.1537 -WarpEngine SCSI support
  3.1538 -CONFIG_WARPENGINE_SCSI
  3.1539 -  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
  3.1540 -  controller. Info at
  3.1541 -  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
  3.1542 -
  3.1543 -Builtin PowerMac IDE support
  3.1544 -CONFIG_BLK_DEV_IDE_PMAC
  3.1545 -  This driver provides support for the built-in IDE controller on
  3.1546 -  most of the recent Apple Power Macintoshes and PowerBooks.
  3.1547 -  If unsure, say Y.
  3.1548 -
  3.1549 -PowerMac IDE DMA support
  3.1550 -CONFIG_BLK_DEV_IDEDMA_PMAC
  3.1551 -  This option allows the driver for the built-in IDE controller on
  3.1552 -  Power Macintoshes and PowerBooks to use DMA (direct memory access)
  3.1553 -  to transfer data to and from memory.  Saying Y is safe and improves
  3.1554 -  performance.
  3.1555 -
  3.1556 -Broadcom SiByte onboard IDE support
  3.1557 -CONFIG_BLK_DEV_IDE_SIBYTE
  3.1558 -  Include the driver for on-board IDE on the SiByte Generic Bus.  Note
  3.1559 -  that this limits the number of IDE devices to 4 (ide0...ide3).
  3.1560 -
  3.1561 -Use DMA by default
  3.1562 -CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
  3.1563 -  This option allows the driver for the built-in IDE controller on
  3.1564 -  Power Macintoshes and PowerBooks to use DMA automatically, without
  3.1565 -  it having to be explicitly enabled.  This option is provided because
  3.1566 -  of concerns about a couple of cases where using DMA on buggy PC
  3.1567 -  hardware may have caused damage.  Saying Y should be safe on all
  3.1568 -  Apple machines.
  3.1569 -
  3.1570 -Macintosh Quadra/Powerbook IDE interface support
  3.1571 -CONFIG_BLK_DEV_MAC_IDE
  3.1572 -  This is the IDE driver for the builtin IDE interface on some m68k
  3.1573 -  Macintosh models. It supports both the `Quadra style' (used in
  3.1574 -  Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
  3.1575 -  (used in the Powerbook 150 and 190 models) IDE interface.
  3.1576 -
  3.1577 -  Say Y if you have such an Macintosh model and want to use IDE
  3.1578 -  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  3.1579 -  builtin IDE interface.
  3.1580 -
  3.1581 -ICS IDE interface support
  3.1582 -CONFIG_BLK_DEV_IDE_ICSIDE
  3.1583 -  On Acorn systems, say Y here if you wish to use the ICS IDE
  3.1584 -  interface card.  This is not required for ICS partition support.
  3.1585 -  If you are unsure, say N to this.
  3.1586 -
  3.1587 -ICS DMA support
  3.1588 -CONFIG_BLK_DEV_IDEDMA_ICS
  3.1589 -  Say Y here if you want to add DMA (Direct Memory Access) support to
  3.1590 -  the ICS IDE driver.
  3.1591 -
  3.1592 -Use ICS DMA by default
  3.1593 -CONFIG_IDEDMA_ICS_AUTO
  3.1594 -  Prior to kernel version 2.1.112, Linux used to automatically use
  3.1595 -  DMA for IDE drives and chipsets which support it. Due to concerns
  3.1596 -  about a couple of cases where buggy hardware may have caused damage,
  3.1597 -  the default is now to NOT use DMA automatically. To revert to the
  3.1598 -  previous behaviour, say Y to this question.
  3.1599 -
  3.1600 -  If you suspect your hardware is at all flakey, say N here.
  3.1601 -  Do NOT email the IDE kernel people regarding this issue!
  3.1602 -
  3.1603 -XT hard disk support
  3.1604 -CONFIG_BLK_DEV_XD
  3.1605 -  Very old 8 bit hard disk controllers used in the IBM XT computer
  3.1606 -  will be supported if you say Y here.
  3.1607 -
  3.1608 -  If you want to compile the driver as a module ( = code which can be
  3.1609 -  inserted in and removed from the running kernel whenever you want),
  3.1610 -  say M here and read <file:Documentation/modules.txt>. The module
  3.1611 -  will be called xd.o.
  3.1612 -
  3.1613 -  It's pretty unlikely that you have one of these: say N.
  3.1614 -
  3.1615 -PS/2 ESDI hard disk support
  3.1616 -CONFIG_BLK_DEV_PS2
  3.1617 -  Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  3.1618 -  hard disk.
  3.1619 -
  3.1620 -  If you want to compile the driver as a module ( = code which can be
  3.1621 -  inserted in and removed from the running kernel whenever you want),
  3.1622 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.1623 -  will be called ps2esdi.o.
  3.1624 -
  3.1625 -Mylex DAC960/DAC1100 PCI RAID Controller support
  3.1626 -CONFIG_BLK_DEV_DAC960
  3.1627 -  This driver adds support for the Mylex DAC960, AcceleRAID, and
  3.1628 -  eXtremeRAID PCI RAID controllers.  See the file
  3.1629 -  <file:Documentation/README.DAC960> for further information about
  3.1630 -  this driver.
  3.1631 -
  3.1632 -  If you want to compile the driver as a module ( = code which can be
  3.1633 -  inserted in and removed from the running kernel whenever you want),
  3.1634 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.1635 -  will be called DAC960.o.
  3.1636 -
  3.1637 -Parallel port IDE device support
  3.1638 -CONFIG_PARIDE
  3.1639 -  There are many external CD-ROM and disk devices that connect through
  3.1640 -  your computer's parallel port. Most of them are actually IDE devices
  3.1641 -  using a parallel port IDE adapter. This option enables the PARIDE
  3.1642 -  subsystem which contains drivers for many of these external drives.
  3.1643 -  Read <file:Documentation/paride.txt> for more information.
  3.1644 -
  3.1645 -  If you have said Y to the "Parallel-port support" configuration
  3.1646 -  option, you may share a single port between your printer and other
  3.1647 -  parallel port devices. Answer Y to build PARIDE support into your
  3.1648 -  kernel, or M if you would like to build it as a loadable module. If
  3.1649 -  your parallel port support is in a loadable module, you must build
  3.1650 -  PARIDE as a module. If you built PARIDE support into your kernel,
  3.1651 -  you may still build the individual protocol modules and high-level
  3.1652 -  drivers as loadable modules. If you build this support as a module,
  3.1653 -  it will be called paride.o.
  3.1654 -
  3.1655 -  To use the PARIDE support, you must say Y or M here and also to at
  3.1656 -  least one high-level driver (e.g. "Parallel port IDE disks",
  3.1657 -  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  3.1658 -  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  3.1659 -  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  3.1660 -  etc.).
  3.1661 -
  3.1662 -Parallel port IDE disks
  3.1663 -CONFIG_PARIDE_PD
  3.1664 -  This option enables the high-level driver for IDE-type disk devices
  3.1665 -  connected through a parallel port. If you chose to build PARIDE
  3.1666 -  support into your kernel, you may answer Y here to build in the
  3.1667 -  parallel port IDE driver, otherwise you should answer M to build
  3.1668 -  it as a loadable module. The module will be called pd.o. You
  3.1669 -  must also have at least one parallel port protocol driver in your
  3.1670 -  system. Among the devices supported by this driver are the SyQuest
  3.1671 -  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
  3.1672 -  hard drives from MicroSolutions.
  3.1673 -
  3.1674 -Parallel port ATAPI CD-ROMs
  3.1675 -CONFIG_PARIDE_PCD
  3.1676 -  This option enables the high-level driver for ATAPI CD-ROM devices
  3.1677 -  connected through a parallel port. If you chose to build PARIDE
  3.1678 -  support into your kernel, you may answer Y here to build in the
  3.1679 -  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
  3.1680 -  build it as a loadable module. The module will be called pcd.o. You
  3.1681 -  must also have at least one parallel port protocol driver in your
  3.1682 -  system. Among the devices supported by this driver are the
  3.1683 -  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
  3.1684 -  you have such a CD-ROM drive, you should also say Y or M to "ISO
  3.1685 -  9660 CD-ROM file system support" below, because that's the file
  3.1686 -  system used on CD-ROMs.
  3.1687 -
  3.1688 -Parallel port ATAPI disks
  3.1689 -CONFIG_PARIDE_PF
  3.1690 -  This option enables the high-level driver for ATAPI disk devices
  3.1691 -  connected through a parallel port. If you chose to build PARIDE
  3.1692 -  support into your kernel, you may answer Y here to build in the
  3.1693 -  parallel port ATAPI disk driver, otherwise you should answer M
  3.1694 -  to build it as a loadable module. The module will be called pf.o.
  3.1695 -  You must also have at least one parallel port protocol driver in
  3.1696 -  your system. Among the devices supported by this driver are the
  3.1697 -  MicroSolutions backpack PD/CD drive and the Imation Superdisk
  3.1698 -  LS-120 drive.
  3.1699 -
  3.1700 -Parallel port ATAPI tapes
  3.1701 -CONFIG_PARIDE_PT
  3.1702 -  This option enables the high-level driver for ATAPI tape devices
  3.1703 -  connected through a parallel port. If you chose to build PARIDE
  3.1704 -  support into your kernel, you may answer Y here to build in the
  3.1705 -  parallel port ATAPI disk driver, otherwise you should answer M
  3.1706 -  to build it as a loadable module. The module will be called pt.o.
  3.1707 -  You must also have at least one parallel port protocol driver in
  3.1708 -  your system. Among the devices supported by this driver is the
  3.1709 -  parallel port version of the HP 5GB drive.
  3.1710 -
  3.1711 -Parallel port generic ATAPI devices
  3.1712 -CONFIG_PARIDE_PG
  3.1713 -  This option enables a special high-level driver for generic ATAPI
  3.1714 -  devices connected through a parallel port. The driver allows user
  3.1715 -  programs, such as cdrtools, to send ATAPI commands directly to a
  3.1716 -  device.
  3.1717 -
  3.1718 -  If you chose to build PARIDE support into your kernel, you may
  3.1719 -  answer Y here to build in the parallel port generic ATAPI driver,
  3.1720 -  otherwise you should answer M to build it as a loadable module. The
  3.1721 -  module will be called pg.o.
  3.1722 -
  3.1723 -  You must also have at least one parallel port protocol driver in
  3.1724 -  your system.
  3.1725 -
  3.1726 -  This driver implements an API loosely related to the generic SCSI
  3.1727 -  driver. See <file:include/linux/pg.h>. for details.
  3.1728 -
  3.1729 -  You can obtain the most recent version of cdrtools from
  3.1730 -  <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
  3.1731 -  later fully support this driver.
  3.1732 -
  3.1733 -ATEN EH-100 protocol
  3.1734 -CONFIG_PARIDE_ATEN
  3.1735 -  This option enables support for the ATEN EH-100 parallel port IDE
  3.1736 -  protocol. This protocol is used in some inexpensive low performance
  3.1737 -  parallel port kits made in Hong Kong. If you chose to build PARIDE
  3.1738 -  support into your kernel, you may answer Y here to build in the
  3.1739 -  protocol driver, otherwise you should answer M to build it as a
  3.1740 -  loadable module. The module will be called aten.o. You must also
  3.1741 -  have a high-level driver for the type of device that you want to
  3.1742 -  support.
  3.1743 -
  3.1744 -Micro Solutions BACKPACK Series 5 protocol
  3.1745 -CONFIG_PARIDE_BPCK
  3.1746 -  This option enables support for the Micro Solutions BACKPACK
  3.1747 -  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
  3.1748 -  before 1999 were Series 5) Series 5 drives will NOT always have the
  3.1749 -  Series noted on the bottom of the drive. Series 6 drivers will.
  3.1750 -
  3.1751 -  In other words, if your BACKPACK drive dosen't say "Series 6" on the
  3.1752 -  bottom, enable this option.
  3.1753 -
  3.1754 -  If you chose to build PARIDE support into your kernel, you may
  3.1755 -  answer Y here to build in the protocol driver, otherwise you should
  3.1756 -  answer M to build it as a loadable module.  The module will be
  3.1757 -  called bpck.o.  You must also have a high-level driver for the type
  3.1758 -  of device that you want to support.
  3.1759 -
  3.1760 -Micro Solutions BACKPACK Series 6 protocol
  3.1761 -CONFIG_PARIDE_BPCK6
  3.1762 -  This option enables support for the Micro Solutions BACKPACK
  3.1763 -  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
  3.1764 -  after 1999 were Series 6) Series 6 drives will have the Series noted
  3.1765 -  on the bottom of the drive.  Series 5 drivers don't always have it
  3.1766 -  noted.
  3.1767 -
  3.1768 -  In other words, if your BACKPACK drive says "Series 6" on the
  3.1769 -  bottom, enable this option.
  3.1770 -
  3.1771 -  If you chose to build PARIDE support into your kernel, you may
  3.1772 -  answer Y here to build in the protocol driver, otherwise you should
  3.1773 -  answer M to build it as a loadable module.  The module will be
  3.1774 -  called bpck6.o.  You must also have a high-level driver for the type
  3.1775 -  of device that you want to support.
  3.1776 -
  3.1777 -DataStor Commuter protocol
  3.1778 -CONFIG_PARIDE_COMM
  3.1779 -  This option enables support for the Commuter parallel port IDE
  3.1780 -  protocol from DataStor. If you chose to build PARIDE support
  3.1781 -  into your kernel, you may answer Y here to build in the protocol
  3.1782 -  driver, otherwise you should answer M to build it as a loadable
  3.1783 -  module. The module will be called comm.o. You must also have
  3.1784 -  a high-level driver for the type of device that you want to support.
  3.1785 -
  3.1786 -DataStor EP-2000 protocol
  3.1787 -CONFIG_PARIDE_DSTR
  3.1788 -  This option enables support for the EP-2000 parallel port IDE
  3.1789 -  protocol from DataStor. If you chose to build PARIDE support
  3.1790 -  into your kernel, you may answer Y here to build in the protocol
  3.1791 -  driver, otherwise you should answer M to build it as a loadable
  3.1792 -  module. The module will be called dstr.o. You must also have
  3.1793 -  a high-level driver for the type of device that you want to support.
  3.1794 -
  3.1795 -Shuttle EPAT/EPEZ protocol
  3.1796 -CONFIG_PARIDE_EPAT
  3.1797 -  This option enables support for the EPAT parallel port IDE protocol.
  3.1798 -  EPAT is a parallel port IDE adapter manufactured by Shuttle
  3.1799 -  Technology and widely used in devices from major vendors such as
  3.1800 -  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
  3.1801 -  PARIDE support into your kernel, you may answer Y here to build in
  3.1802 -  the protocol driver, otherwise you should answer M to build it as a
  3.1803 -  loadable module. The module will be called epat.o. You must also
  3.1804 -  have a high-level driver for the type of device that you want to
  3.1805 -  support.
  3.1806 -
  3.1807 -Shuttle EPAT c7/c8 extension
  3.1808 -CONFIG_PARIDE_EPATC8
  3.1809 -  This option enables support for the newer Shuttle EP1284 (aka c7 and
  3.1810 -  c8) chip. You need this if you are using any recent Imation SuperDisk
  3.1811 -  (LS-120) drive.
  3.1812 -
  3.1813 -Shuttle EPIA protocol
  3.1814 -CONFIG_PARIDE_EPIA
  3.1815 -  This option enables support for the (obsolete) EPIA parallel port
  3.1816 -  IDE protocol from Shuttle Technology. This adapter can still be
  3.1817 -  found in some no-name kits. If you chose to build PARIDE support
  3.1818 -  into your kernel, you may answer Y here to build in the protocol
  3.1819 -  driver, otherwise you should answer M to build it as a loadable
  3.1820 -  module. The module will be called epia.o. You must also have a
  3.1821 -  high-level driver for the type of device that you want to support.
  3.1822 -
  3.1823 -FIT TD-2000 protocol
  3.1824 -CONFIG_PARIDE_FIT2
  3.1825 -  This option enables support for the TD-2000 parallel port IDE
  3.1826 -  protocol from Fidelity International Technology. This is a simple
  3.1827 -  (low speed) adapter that is used in some portable hard drives. If
  3.1828 -  you chose to build PARIDE support into your kernel, you may answer Y
  3.1829 -  here to build in the protocol driver, otherwise you should answer M
  3.1830 -  to build it as a loadable module. The module will be called fit2.o.
  3.1831 -  You must also have a high-level driver for the type of device that
  3.1832 -  you want to support.
  3.1833 -
  3.1834 -FIT TD-3000 protocol
  3.1835 -CONFIG_PARIDE_FIT3
  3.1836 -  This option enables support for the TD-3000 parallel port IDE
  3.1837 -  protocol from Fidelity International Technology. This protocol is
  3.1838 -  used in newer models of their portable disk, CD-ROM and PD/CD
  3.1839 -  devices. If you chose to build PARIDE support into your kernel, you
  3.1840 -  may answer Y here to build in the protocol driver, otherwise you
  3.1841 -  should answer M to build it as a loadable module. The module will be
  3.1842 -  called fit3.o. You must also have a high-level driver for the type
  3.1843 -  of device that you want to support.
  3.1844 -
  3.1845 -Freecom IQ ASIC-2 protocol
  3.1846 -CONFIG_PARIDE_FRIQ
  3.1847 -  This option enables support for version 2 of the Freecom IQ parallel
  3.1848 -  port IDE adapter.  This adapter is used by the Maxell Superdisk
  3.1849 -  drive.  If you chose to build PARIDE support into your kernel, you
  3.1850 -  may answer Y here to build in the protocol driver, otherwise you
  3.1851 -  should answer M to build it as a loadable module. The module will be
  3.1852 -  called friq.o. You must also have a high-level driver for the type
  3.1853 -  of device that you want to support.
  3.1854 -
  3.1855 -FreeCom power protocol
  3.1856 -CONFIG_PARIDE_FRPW
  3.1857 -  This option enables support for the Freecom power parallel port IDE
  3.1858 -  protocol. If you chose to build PARIDE support into your kernel, you
  3.1859 -  may answer Y here to build in the protocol driver, otherwise you
  3.1860 -  should answer M to build it as a loadable module. The module will be
  3.1861 -  called frpw.o. You must also have a high-level driver for the type
  3.1862 -  of device that you want to support.
  3.1863 -
  3.1864 -KingByte KBIC-951A/971A protocols
  3.1865 -CONFIG_PARIDE_KBIC
  3.1866 -  This option enables support for the KBIC-951A and KBIC-971A parallel
  3.1867 -  port IDE protocols from KingByte Information Corp. KingByte's
  3.1868 -  adapters appear in many no-name portable disk and CD-ROM products,
  3.1869 -  especially in Europe. If you chose to build PARIDE support into your
  3.1870 -  kernel, you may answer Y here to build in the protocol driver,
  3.1871 -  otherwise you should answer M to build it as a loadable module. The
  3.1872 -  module will be called kbic.o. You must also have a high-level driver
  3.1873 -  for the type of device that you want to support.
  3.1874 -
  3.1875 -KT PHd protocol
  3.1876 -CONFIG_PARIDE_KTTI
  3.1877 -  This option enables support for the "PHd" parallel port IDE protocol
  3.1878 -  from KT Technology. This is a simple (low speed) adapter that is
  3.1879 -  used in some 2.5" portable hard drives. If you chose to build PARIDE
  3.1880 -  support into your kernel, you may answer Y here to build in the
  3.1881 -  protocol driver, otherwise you should answer M to build it as a
  3.1882 -  loadable module. The module will be called ktti.o. You must also
  3.1883 -  have a high-level driver for the type of device that you want to
  3.1884 -  support.
  3.1885 -
  3.1886 -OnSpec 90c20 protocol
  3.1887 -CONFIG_PARIDE_ON20
  3.1888 -  This option enables support for the (obsolete) 90c20 parallel port
  3.1889 -  IDE protocol from OnSpec (often marketed under the ValuStore brand
  3.1890 -  name). If you chose to build PARIDE support into your kernel, you
  3.1891 -  may answer Y here to build in the protocol driver, otherwise you
  3.1892 -  should answer M to build it as a loadable module. The module will
  3.1893 -  be called on20.o. You must also have a high-level driver for the
  3.1894 -  type of device that you want to support.
  3.1895 -
  3.1896 -OnSpec 90c26 protocol
  3.1897 -CONFIG_PARIDE_ON26
  3.1898 -  This option enables support for the 90c26 parallel port IDE protocol
  3.1899 -  from OnSpec Electronics (often marketed under the ValuStore brand
  3.1900 -  name). If you chose to build PARIDE support into your kernel, you
  3.1901 -  may answer Y here to build in the protocol driver, otherwise you
  3.1902 -  should answer M to build it as a loadable module. The module will be
  3.1903 -  called on26.o. You must also have a high-level driver for the type
  3.1904 -  of device that you want to support.
  3.1905 -
  3.1906 -Logical Volume Manager (LVM) support
  3.1907 -CONFIG_BLK_DEV_LVM
  3.1908 -  This driver lets you combine several hard disks, hard disk
  3.1909 -  partitions, multiple devices or even loop devices (for evaluation
  3.1910 -  purposes) into a volume group.  Imagine a volume group as a kind of
  3.1911 -  virtual disk. Logical volumes, which can be thought of as virtual
  3.1912 -  partitions, can be created in the volume group.  You can resize
  3.1913 -  volume groups and logical volumes after creation time, corresponding
  3.1914 -  to new capacity needs.  Logical volumes are accessed as block
  3.1915 -  devices named /dev/VolumeGroupName/LogicalVolumeName.
  3.1916 -
  3.1917 -  For details see <file:Documentation/LVM-HOWTO>.  You will need
  3.1918 -  supporting user space software; location is in
  3.1919 -  <file:Documentation/Changes>.
  3.1920 -
  3.1921 -  If you want to compile this support as a module ( = code which can
  3.1922 -  be inserted in and removed from the running kernel whenever you
  3.1923 -  want), say M here and read <file:Documentation/modules.txt>.  The
  3.1924 -  module will be called lvm-mod.o.
  3.1925 -
  3.1926 -Multiple devices driver support (RAID and LVM)
  3.1927 -CONFIG_MD
  3.1928 -  Support multiple physical spindles through a single logical device.
  3.1929 -  Required for RAID and logical volume management (LVM).
  3.1930 -
  3.1931 -Multiple devices driver support
  3.1932 -CONFIG_BLK_DEV_MD
  3.1933 -  This driver lets you combine several hard disk partitions into one
  3.1934 -  logical block device. This can be used to simply append one
  3.1935 -  partition to another one or to combine several redundant hard disks
  3.1936 -  into a RAID1/4/5 device so as to provide protection against hard
  3.1937 -  disk failures. This is called "Software RAID" since the combining of
  3.1938 -  the partitions is done by the kernel. "Hardware RAID" means that the
  3.1939 -  combining is done by a dedicated controller; if you have such a
  3.1940 -  controller, you do not need to say Y here.
  3.1941 -
  3.1942 -  More information about Software RAID on Linux is contained in the
  3.1943 -  Software RAID mini-HOWTO, available from
  3.1944 -  <http://www.tldp.org/docs.html#howto>. There you will also learn
  3.1945 -  where to get the supporting user space utilities raidtools.
  3.1946 -
  3.1947 -  This driver is also available as a module ( = code which can be
  3.1948 -  inserted in and removed from the running kernel whenever you want).
  3.1949 -  If you want to compile it as a module, say M here and read
  3.1950 -  <file:Documentation/modules.txt>. The module will be called
  3.1951 -  md.o
  3.1952 -
  3.1953 -  If unsure, say N.
  3.1954 -
  3.1955 -Linear (append) mode
  3.1956 -CONFIG_MD_LINEAR
  3.1957 -  If you say Y here, then your multiple devices driver will be able to
  3.1958 -  use the so-called linear mode, i.e. it will combine the hard disk
  3.1959 -  partitions by simply appending one to the other.
  3.1960 -
  3.1961 -  If you want to compile this as a module ( = code which can be
  3.1962 -  inserted in and removed from the running kernel whenever you want),
  3.1963 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.1964 -  will be called linear.o.
  3.1965 -
  3.1966 -  If unsure, say Y.
  3.1967 -
  3.1968 -RAID-0 (striping) mode
  3.1969 -CONFIG_MD_RAID0
  3.1970 -  If you say Y here, then your multiple devices driver will be able to
  3.1971 -  use the so-called raid0 mode, i.e. it will combine the hard disk
  3.1972 -  partitions into one logical device in such a fashion as to fill them
  3.1973 -  up evenly, one chunk here and one chunk there. This will increase
  3.1974 -  the throughput rate if the partitions reside on distinct disks.
  3.1975 -
  3.1976 -  Information about Software RAID on Linux is contained in the
  3.1977 -  Software-RAID mini-HOWTO, available from
  3.1978 -  <http://www.tldp.org/docs.html#howto>. There you will also
  3.1979 -  learn where to get the supporting user space utilities raidtools.
  3.1980 -
  3.1981 -  If you want to compile this as a module ( = code which can be
  3.1982 -  inserted in and removed from the running kernel whenever you want),
  3.1983 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.1984 -  will be called raid0.o.
  3.1985 -
  3.1986 -  If unsure, say Y.
  3.1987 -
  3.1988 -RAID-1 (mirroring) mode
  3.1989 -CONFIG_MD_RAID1
  3.1990 -  A RAID-1 set consists of several disk drives which are exact copies
  3.1991 -  of each other.  In the event of a mirror failure, the RAID driver
  3.1992 -  will continue to use the operational mirrors in the set, providing
  3.1993 -  an error free MD (multiple device) to the higher levels of the
  3.1994 -  kernel.  In a set with N drives, the available space is the capacity
  3.1995 -  of a single drive, and the set protects against a failure of (N - 1)
  3.1996 -  drives.
  3.1997 -
  3.1998 -  Information about Software RAID on Linux is contained in the
  3.1999 -  Software-RAID mini-HOWTO, available from
  3.2000 -  <http://www.tldp.org/docs.html#howto>.  There you will also
  3.2001 -  learn where to get the supporting user space utilities raidtools.
  3.2002 -
  3.2003 -  If you want to use such a RAID-1 set, say Y. This code is also
  3.2004 -  available as a module called raid1.o ( = code which can be inserted
  3.2005 -  in and removed from the running kernel whenever you want).  If you
  3.2006 -  want to compile it as a module, say M here and read
  3.2007 -  <file:Documentation/modules.txt>.
  3.2008 -
  3.2009 -  If unsure, say Y.
  3.2010 -
  3.2011 -RAID-4/RAID-5 mode
  3.2012 -CONFIG_MD_RAID5
  3.2013 -  A RAID-5 set of N drives with a capacity of C MB per drive provides
  3.2014 -  the capacity of C * (N - 1) MB, and protects against a failure
  3.2015 -  of a single drive. For a given sector (row) number, (N - 1) drives
  3.2016 -  contain data sectors, and one drive contains the parity protection.
  3.2017 -  For a RAID-4 set, the parity blocks are present on a single drive,
  3.2018 -  while a RAID-5 set distributes the parity across the drives in one
  3.2019 -  of the available parity distribution methods.
  3.2020 -
  3.2021 -  Information about Software RAID on Linux is contained in the
  3.2022 -  Software-RAID mini-HOWTO, available from
  3.2023 -  <http://www.tldp.org/docs.html#howto>. There you will also
  3.2024 -  learn where to get the supporting user space utilities raidtools.
  3.2025 -
  3.2026 -  If you want to use such a RAID-4/RAID-5 set, say Y. This code is
  3.2027 -  also available as a module called raid5.o ( = code which can be
  3.2028 -  inserted in and removed from the running kernel whenever you want).
  3.2029 -  If you want to compile it as a module, say M here and read
  3.2030 -  <file:Documentation/modules.txt>.
  3.2031 -
  3.2032 -  If unsure, say Y.
  3.2033 -
  3.2034 -Multipath I/O support
  3.2035 -CONFIG_MD_MULTIPATH
  3.2036 -  Multipath-IO is the ability of certain devices to address the same
  3.2037 -  physical disk over multiple 'IO paths'. The code ensures that such
  3.2038 -  paths can be defined and handled at runtime, and ensures that a
  3.2039 -  transparent failover to the backup path(s) happens if a IO errors
  3.2040 -  arrives on the primary path.
  3.2041 -
  3.2042 -  This driver is also available as a module ( = code which can be
  3.2043 -  inserted in and removed from the running kernel whenever you want).
  3.2044 -  If you want to compile it as a module, say M here and read
  3.2045 -  <file:Documentation/modules.txt>. The module will be called
  3.2046 -  multipath.o
  3.2047 -
  3.2048 -  If unsure, say N.
  3.2049 -
  3.2050 -Support for IDE Raid controllers
  3.2051 -CONFIG_BLK_DEV_ATARAID
  3.2052 -  Say Y or M if you have an IDE Raid controller and want linux
  3.2053 -  to use its softwareraid feature.  You must also select an
  3.2054 -  appropriate for your board low-level driver below.
  3.2055 -
  3.2056 -  Note, that Linux does not use the Raid implementation in BIOS, and
  3.2057 -  the main purpose for this feature is to retain compatibility and
  3.2058 -  data integrity with other OS-es, using the same disk array. Linux
  3.2059 -  has its own Raid drivers, which you should use if you need better
  3.2060 -  performance.
  3.2061 -
  3.2062 -  This driver is also available as a module ( = code which can be
  3.2063 -  inserted in and removed from the running kernel whenever you want).
  3.2064 -  If you want to compile it as a module, say M here and read
  3.2065 -  <file:Documentation/modules.txt>. The module will be called
  3.2066 -  ataraid.o
  3.2067 -
  3.2068 -Support Promise software RAID (Fasttrak(tm))
  3.2069 -CONFIG_BLK_DEV_ATARAID_PDC
  3.2070 -  Say Y or M if you have a Promise Fasttrak (tm) Raid controller
  3.2071 -  and want linux to use the softwareraid feature of this card.
  3.2072 -  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  3.2073 -  names.
  3.2074 -
  3.2075 -  If you choose to compile this as a module, the module will be called
  3.2076 -  pdcraid.o.
  3.2077 -
  3.2078 -Highpoint 370 software RAID
  3.2079 -CONFIG_BLK_DEV_ATARAID_HPT
  3.2080 -  Say Y or M if you have a Highpoint HPT 370 Raid controller
  3.2081 -  and want linux to use the softwareraid feature of this card.
  3.2082 -  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  3.2083 -  names.
  3.2084 -
  3.2085 -  If you choose to compile this as a module, the module will be called
  3.2086 -  hptraid.o.
  3.2087 -
  3.2088 -Support for Acer PICA 1 chipset
  3.2089 -CONFIG_ACER_PICA_61
  3.2090 -  This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
  3.2091 -  kernel that runs on these, say Y here. For details about Linux on
  3.2092 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  3.2093 -  <http://oss.sgi.com/mips/>.
  3.2094 -
  3.2095 -Support for Algorithmics P4032 (EXPERIMENTAL)
  3.2096 -CONFIG_ALGOR_P4032
  3.2097 -  This is an evaluation board of the British company Algorithmics.
  3.2098 -  The board uses the R4300 and a R5230 CPUs.  For more information
  3.2099 -  about this board see <http://www.algor.co.uk/>.
  3.2100 -
  3.2101 -SGI SN2 L1 serial port support
  3.2102 -CONFIG_SGI_L1_SERIAL
  3.2103 -  If you have an SGI SN2 and you want to use the serial port connected
  3.2104 -  to the system controller (you want this!), say Y.  Otherwise, say N.
  3.2105 -
  3.2106 -SGI SN2 L1 serial console support
  3.2107 -CONFIG_SGI_L1_SERIAL_CONSOLE
  3.2108 -  If you have an SGI SN2 and you would like to use the system
  3.2109 -  controller serial port as your console (you want this!), say Y.
  3.2110 -  Otherwise, say N.
  3.2111 -
  3.2112 -Support for BAGET MIPS series
  3.2113 -CONFIG_BAGET_MIPS
  3.2114 -  This enables support for the Baget, a Russian embedded system.  For
  3.2115 -  more details about the Baget see the Linux/MIPS FAQ on
  3.2116 -  <http://oss.sgi.com/mips/>.
  3.2117 -
  3.2118 -Baget AMD LANCE support
  3.2119 -CONFIG_BAGETLANCE
  3.2120 -  Say Y to enable kernel support for AMD Lance Ethernet cards on the
  3.2121 -  MIPS-32-based Baget embedded system.  This chipset is better known
  3.2122 -  via the NE2100 cards.
  3.2123 -
  3.2124 -Support for DECstations
  3.2125 -CONFIG_DECSTATION
  3.2126 -  This enables support for DEC's MIPS based workstations.  For details
  3.2127 -  see the Linux/MIPS FAQ on <http://oss.sgi.com/mips/> and the
  3.2128 -  DECstation porting pages on <http://decstation.unix-ag.org/>.
  3.2129 -
  3.2130 -  If you have one of the following DECstation Models you definitely
  3.2131 -  want to choose R4xx0 for the CPU Type:
  3.2132 -
  3.2133 -	DECstation 5000/50
  3.2134 -	DECstation 5000/150
  3.2135 -	DECstation 5000/260
  3.2136 -	DECsystem 5900/260
  3.2137 -
  3.2138 -  otherwise choose R3000.
  3.2139 -
  3.2140 -Support for Cobalt Micro Server
  3.2141 -CONFIG_COBALT_MICRO_SERVER
  3.2142 -  Support for MIPS-based Cobalt boxes (they have been bought by Sun
  3.2143 -  and are now the "Server Appliance Business Unit") including the 2700
  3.2144 -  series -- versions 1 of the Qube and Raq.  To compile a Linux kernel
  3.2145 -  for this hardware, say Y here.
  3.2146 -
  3.2147 -Support for Cobalt 2800
  3.2148 -CONFIG_COBALT_28
  3.2149 -  Support for the second generation of MIPS-based Cobalt boxes (they
  3.2150 -  have been bought by Sun and are now the "Server Appliance Business
  3.2151 -  Unit") including the 2800 series -- versions 2 of the Qube and Raq.
  3.2152 -  To compile a Linux kernel for this hardware, say Y here.
  3.2153 -
  3.2154 -Support for the Momentum Computer Ocelot SBC
  3.2155 -CONFIG_MOMENCO_OCELOT
  3.2156 -  The Ocelot is a MIPS-based Single Board Computer (SBC) made by
  3.2157 -  Momentum Computer <http://www.momenco.com/>.
  3.2158 -
  3.2159 -Support for NEC DDB Vrc-5074
  3.2160 -CONFIG_DDB5074
  3.2161 -  This enables support for the VR5000-based NEC DDB Vrc-5074
  3.2162 -  evaluation board.
  3.2163 -
  3.2164 -Support for NEC DDB Vrc-5476
  3.2165 -CONFIG_DDB5476
  3.2166 -  This enables support for the R5432-based NEC DDB Vrc-5476
  3.2167 -  evaluation board.
  3.2168 -
  3.2169 -  Features : kernel debugging, serial terminal, NFS root fs, on-board
  3.2170 -  ether port (Need an additional patch at <http://linux.junsun.net/>),
  3.2171 -  USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
  3.2172 -  PS2 keyboard, PS2 mouse, etc.
  3.2173 -
  3.2174 -Support for NEC DDB Vrc-5477
  3.2175 -CONFIG_DDB5477
  3.2176 -  This enables support for the R5432-based NEC DDB Vrc-5477
  3.2177 -  evaluation board.
  3.2178 -
  3.2179 -  Features : kernel debugging, serial terminal, NFS root fs, on-board
  3.2180 -  ether port (Need an additional patch at <http://linux.junsun.net/>),
  3.2181 -  USB, AC97, PCI, etc.
  3.2182 -
  3.2183 -Support for MIPS Atlas board
  3.2184 -CONFIG_MIPS_ATLAS
  3.2185 -  This enables support for the QED R5231-based MIPS Atlas evaluation
  3.2186 -  board.
  3.2187 -
  3.2188 -Support for MIPS Malta board
  3.2189 -CONFIG_MIPS_MALTA
  3.2190 -  This enables support for the VR5000-based MIPS Malta evaluation
  3.2191 -  board.
  3.2192 -
  3.2193 -# Choice: bcmboard
  3.2194 -Support for Broadcom SiByte boards
  3.2195 -CONFIG_SIBYTE_SWARM
  3.2196 -  Enable support for boards based on the Broadcom SiByte family:
  3.2197 -
  3.2198 -  BCM91250A-SWARM    BCM1250 ATX size Eval Board (BCM91250A-SWARM)
  3.2199 -
  3.2200 -  BCM91250E-Sentosa  BCM1250 PCI card Eval Board (BCM91250E-Sentosa)
  3.2201 -
  3.2202 -  BCM91125E-Rhone    BCM1125 PCI card Eval Board (BCM91125E-Rhone)
  3.2203 -
  3.2204 -  Other              Non-Broadcom SiByte-based platform
  3.2205 -
  3.2206 -# Choice: bcmsoc
  3.2207 -Support for Broadcom BCM1xxx SOCs
  3.2208 -CONFIG_SIBYTE_SB1250
  3.2209 -
  3.2210 -  BCM1250     Dual-CPU SB1 with PCI and HyperTransport.
  3.2211 -
  3.2212 -  BCM1120     Uniprocessor SB1.
  3.2213 -
  3.2214 -  BCM1125     Uniprocessor SB1 with PCI (and HyperTransport for 1125H).
  3.2215 -
  3.2216 -BCM1250 Stepping
  3.2217 -CONFIG_CPU_SB1_PASS_1
  3.2218 -  Which pass of the SOC is supported (see the "system_revision"
  3.2219 -  register in the User Manual for more discussion of revisions):
  3.2220 -
  3.2221 -  Pass1    1250 "Pass 1"
  3.2222 -
  3.2223 -  An       1250 "Pass 2"
  3.2224 -
  3.2225 -  Bn       1250 "Pass 2.2"
  3.2226 -
  3.2227 -  Cn       1250 "Pass 3"
  3.2228 -
  3.2229 -BCM112x Stepping
  3.2230 -CONFIG_CPU_SB1_PASS_2
  3.2231 -  Which pass of the SOC is supported (see the "system_revision"
  3.2232 -  register in the User Manual for more discussion of revisions):
  3.2233 -
  3.2234 -  Hybrid   1250 "Pass 2"
  3.2235 -
  3.2236 -  An       112x "Pass 1"
  3.2237 -
  3.2238 -Booting from CFE
  3.2239 -CONFIG_SIBYTE_CFE
  3.2240 -  Make use of the CFE API for enumerating available memory,
  3.2241 -  controlling secondary CPUs, and possibly console output.
  3.2242 -
  3.2243 -Use firmware console
  3.2244 -CONFIG_SIBYTE_CFE_CONSOLE
  3.2245 -  Use the CFE API's console write routines during boot.  Other console
  3.2246 -  options (VT console, sb1250 duart console, etc.) should not be
  3.2247 -  configured.
  3.2248 -
  3.2249 -Support for Bus Watcher statistics
  3.2250 -CONFIG_SIBYTE_BUS_WATCHER
  3.2251 -  Handle and keep statistics on the bus error interrupts (COR_ECC,
  3.2252 -  BAD_ECC, IO_BUS).
  3.2253 -
  3.2254 -Corelis Debugger
  3.2255 -CONFIG_SB1XXX_CORELIS
  3.2256 -  Select compile flags that produce code that can be processed by the
  3.2257 -  Corelis mksym utility and UDB Emulator.
  3.2258 -
  3.2259 -DMA for page clear and copy
  3.2260 -CONFIG_SIBYTE_DMA_PAGEOPS
  3.2261 -  Instead of using the CPU to zero and copy pages, use a Data Mover
  3.2262 -  channel.  These DMA channels are otherwise unused by the standard
  3.2263 -  SiByte Linux port.  Seems to give a small performance benefit.
  3.2264 -
  3.2265 -Support for Galileo Evaluation board or CoSine Orion
  3.2266 -CONFIG_ORION
  3.2267 -  Say Y if configuring for the Galileo evaluation board
  3.2268 -  or CoSine Orion.  More information is available at
  3.2269 -  <http://tochna.technion.ac.il/project/linux/html/linux.html>.
  3.2270 -
  3.2271 -  Otherwise, say N.
  3.2272 -
  3.2273 -Support for Mips Magnum 4000
  3.2274 -CONFIG_MIPS_MAGNUM_4000
  3.2275 -  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  3.2276 -  kernel that runs on these, say Y here. For details about Linux on
  3.2277 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  3.2278 -  <http://oss.sgi.com/mips/>.
  3.2279 -
  3.2280 -Enable Qtronix 990P Keyboard Support
  3.2281 -CONFIG_QTRONIX_KEYBOARD
  3.2282 -  Images of Qtronix keyboards are at
  3.2283 -  <http://www.qtronix.com/keyboard.html>.
  3.2284 -
  3.2285 -Support for Olivetti M700
  3.2286 -CONFIG_OLIVETTI_M700
  3.2287 -  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  3.2288 -  kernel that runs on these, say Y here. For details about Linux on
  3.2289 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  3.2290 -  <http://oss.sgi.com/mips/>.
  3.2291 -
  3.2292 -Support for SNI RM200 PCI
  3.2293 -CONFIG_SNI_RM200_PCI
  3.2294 -  The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
  3.2295 -  Nixdorf Informationssysteme (SNI), parent company of Pyramid
  3.2296 -  Technology and now in turn merged with Fujitsu.  Say Y here to
  3.2297 -  support this machine type.
  3.2298 -
  3.2299 -Support for SGI-IP22 (Indy/Indigo2)
  3.2300 -CONFIG_SGI_IP22
  3.2301 -  This are the SGI Indy, Challenge S and Indigo2, as well as certain
  3.2302 -  OEM variants like the Tandem CMN B006S. To compile a Linux kernel
  3.2303 -  that runs on these, say Y here.
  3.2304 -
  3.2305 -Support for SGI IP27 (Origin200/2000)
  3.2306 -CONFIG_SGI_IP27
  3.2307 -  This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
  3.2308 -  workstations.  To compile a Linux kernel that runs on these, say Y
  3.2309 -  here.
  3.2310 -
  3.2311 -IP27 N-Mode
  3.2312 -CONFIG_SGI_SN0_N_MODE
  3.2313 -  The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
  3.2314 -  configured in either N-Modes which allows for more nodes or M-Mode
  3.2315 -  which allows for more memory.  Your system is most probably
  3.2316 -  running in M-Mode, so you should say N here.
  3.2317 -
  3.2318 -Lasi Ethernet
  3.2319 -CONFIG_LASI_82596
  3.2320 -  Say Y here to support the on-board Intel 82596 ethernet controller
  3.2321 -  built into Hewlett-Packard PA-RISC machines.
  3.2322 -
  3.2323 -MIPS JAZZ onboard SONIC Ethernet support
  3.2324 -CONFIG_MIPS_JAZZ_SONIC
  3.2325 -  This is the driver for the onboard card of MIPS Magnum 4000,
  3.2326 -  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
  3.2327 -
  3.2328 -MIPS JAZZ FAS216 SCSI support
  3.2329 -CONFIG_JAZZ_ESP
  3.2330 -  This is the driver for the onboard SCSI host adapter of MIPS Magnum
  3.2331 -  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
  3.2332 -  systems.
  3.2333 -
  3.2334 -MIPS GT96100 Ethernet support
  3.2335 -CONFIG_MIPS_GT96100ETH
  3.2336 -  Say Y here to support the Ethernet subsystem on your GT96100 card.
  3.2337 -
  3.2338 -Zalon SCSI support
  3.2339 -CONFIG_SCSI_ZALON
  3.2340 -  The Zalon is an interface chip that sits between the PA-RISC
  3.2341 -  processor and the NCR 53c720 SCSI controller on K-series PA-RISC
  3.2342 -  boards (these are used, among other places, on some HP 780
  3.2343 -  workstations).  Say Y here to make sure it gets initialized
  3.2344 -  correctly before the Linux kernel tries to talk to the controller.
  3.2345 -
  3.2346 -SGI PROM Console Support
  3.2347 -CONFIG_SGI_PROM_CONSOLE
  3.2348 -  Say Y here to set up the boot console on serial port 0.
  3.2349 -
  3.2350 -DECstation serial support
  3.2351 -CONFIG_SERIAL_DEC
  3.2352 -  This selects whether you want to be asked about drivers for
  3.2353 -  DECstation serial ports.
  3.2354 -
  3.2355 -  Note that the answer to this question won't directly affect the
  3.2356 -  kernel: saying N will just cause the configurator to skip all
  3.2357 -  the questions about DECstation serial ports.
  3.2358 -
  3.2359 -  If unsure, say Y.
  3.2360 -
  3.2361 -Support for console on a DECstation serial port
  3.2362 -CONFIG_SERIAL_DEC_CONSOLE
  3.2363 -  If you say Y here, it will be possible to use a serial port as the
  3.2364 -  system console (the system console is the device which receives all
  3.2365 -  kernel messages and warnings and which allows logins in single user
  3.2366 -  mode).  Note that the firmware uses ttyS0 as the serial console on
  3.2367 -  the Maxine and ttyS2 on the others.
  3.2368 -
  3.2369 -  If unsure, say Y.
  3.2370 -
  3.2371 -DZ11 Serial Support
  3.2372 -CONFIG_DZ
  3.2373 -  DZ11-family serial controllers for VAXstations, including the
  3.2374 -  DC7085, M7814, and M7819.
  3.2375 -
  3.2376 -TURBOchannel support
  3.2377 -CONFIG_TC
  3.2378 -  TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
  3.2379 -  Documentation on writing device drivers for TurboChannel is available at:
  3.2380 -  <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
  3.2381 -
  3.2382 -# Choice: galileo_clock
  3.2383 -75
  3.2384 -CONFIG_SYSCLK_75
  3.2385 -  Configure the kernel for clock speed of your Galileo board.  
  3.2386 -  The choices are 75MHz, 83.3MHz, and 100MHz.
  3.2387 -
  3.2388 -83.3
  3.2389 -CONFIG_SYSCLK_83
  3.2390 -  Configure the Galileo kernel for a clock speed of 83.3 MHz.
  3.2391 -
  3.2392 -100
  3.2393 -CONFIG_SYSCLK_100
  3.2394 -  Configure the Galileo kernel for a clock speed of 100 MHz.
  3.2395 -
  3.2396 -Z85C30 Serial Support
  3.2397 -CONFIG_ZS
  3.2398 -  Documentation on the Zilog 85C350 serial communications controller
  3.2399 -  is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
  3.2400 -
  3.2401 -PCMCIA SCSI adapter support
  3.2402 -CONFIG_SCSI_PCMCIA
  3.2403 -  Say Y here if you intend to attach a PCMCIA or CardBus card to your
  3.2404 -  computer which acts as a SCSI host adapter. These are credit card
  3.2405 -  size devices often used with laptops.
  3.2406 -
  3.2407 -  Note that the answer to this question won't directly affect the
  3.2408 -  kernel: saying N will just cause the configurator to skip all
  3.2409 -  the questions PCMCIA SCSI host adapters.
  3.2410 -
  3.2411 -Adaptec APA1480 CardBus support
  3.2412 -CONFIG_PCMCIA_APA1480
  3.2413 -  Say Y here if you intend to attach this type of CardBus SCSI host
  3.2414 -  adapter to your computer.
  3.2415 -
  3.2416 -  This driver is also available as a module called apa1480_cb.o ( =
  3.2417 -  code which can be inserted in and removed from the running kernel
  3.2418 -  whenever you want). If you want to compile it as a module, say M
  3.2419 -  here and read <file:Documentation/modules.txt>.
  3.2420 -
  3.2421 -NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
  3.2422 -CONFIG_PCMCIA_NINJA_SCSI
  3.2423 -  If you intend to attach this type of PCMCIA SCSI host adapter to
  3.2424 -  your computer, say Y here and read
  3.2425 -  <file:Documentation/README.nsp_cs.eng>.
  3.2426 -
  3.2427 -  This driver is also available as a module called nsp_cs.o ( =
  3.2428 -  code which can be inserted in and removed from the running kernel
  3.2429 -  whenever you want). If you want to compile it as a module, say M
  3.2430 -  here and read <file:Documentation/modules.txt>.
  3.2431 -
  3.2432 -Adaptec AHA152X PCMCIA support
  3.2433 -CONFIG_PCMCIA_AHA152X
  3.2434 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  3.2435 -  adapter to your computer.
  3.2436 -
  3.2437 -  This driver is also available as a module called aha152x_cs.o ( =
  3.2438 -  code which can be inserted in and removed from the running kernel
  3.2439 -  whenever you want). If you want to compile it as a module, say M
  3.2440 -  here and read <file:Documentation/modules.txt>.
  3.2441 -
  3.2442 -Qlogic PCMCIA support
  3.2443 -CONFIG_PCMCIA_QLOGIC
  3.2444 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  3.2445 -  adapter to your computer.
  3.2446 -
  3.2447 -  This driver is also available as a module called qlogic_cs.o ( =
  3.2448 -  code which can be inserted in and removed from the running kernel
  3.2449 -  whenever you want).  If you want to compile it as a module, say M
  3.2450 -  here and read <file:Documentation/modules.txt>.
  3.2451 -
  3.2452 -Future Domain PCMCIA support
  3.2453 -CONFIG_PCMCIA_FDOMAIN
  3.2454 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  3.2455 -  adapter to your computer.
  3.2456 -
  3.2457 -  This driver is also available as a module called fdomain_cs.o ( =
  3.2458 -  code which can be inserted in and removed from the running kernel
  3.2459 -  whenever you want).  If you want to compile it as a module, say M
  3.2460 -  here and read <file:Documentation/modules.txt>.
  3.2461 -
  3.2462 -# Choice: mipstype
  3.2463 -CPU type
  3.2464 -CONFIG_CPU_R3000
  3.2465 -  Please make sure to pick the right CPU type. Linux/MIPS is not
  3.2466 -  designed to be generic, i.e. Kernels compiled for R3000 CPUs will
  3.2467 -  *not* work on R4000 machines and vice versa.  However, since most
  3.2468 -  of the supported machines have an R4000 (or similar) CPU, R4x00
  3.2469 -  might be a safe bet.  If the resulting kernel does not work,
  3.2470 -  try to recompile with R3000.
  3.2471 -
  3.2472 -  R3000    MIPS Technologies R3000-series processors,
  3.2473 -           including the 3041, 3051, and 3081.
  3.2474 -
  3.2475 -  R6000    MIPS Technologies R6000-series processors,
  3.2476 -           including the 64474, 64475, 64574 and 64575.
  3.2477 -
  3.2478 -  R4300    MIPS Technologies R4300-series processors.
  3.2479 -
  3.2480 -  R4x00    MIPS Technologies R4000-series processors other than 4300,
  3.2481 -           including the 4640, 4650, and 4700.
  3.2482 -
  3.2483 -  R5000    MIPS Technologies R5000-series processors other than the
  3.2484 -           Nevada.
  3.2485 -
  3.2486 -  R52xx    MIPS Technologies R52xx-series ("Nevada") processors.
  3.2487 -
  3.2488 -  R10000   MIPS Technologies R10000-series processors.
  3.2489 -
  3.2490 -  SB1      Broadcom SiByte SB1 processor.
  3.2491 -
  3.2492 -R6000
  3.2493 -CONFIG_CPU_R6000
  3.2494 -  MIPS Technologies R6000-series processors, including the 64474,
  3.2495 -  64475, 64574 and 64575.
  3.2496 -
  3.2497 -R4300
  3.2498 -CONFIG_CPU_R4300
  3.2499 -  MIPS Technologies R4300-series processors.
  3.2500 -
  3.2501 -R4x00
  3.2502 -CONFIG_CPU_R4X00
  3.2503 -  MIPS Technologies R4000-series processors other than 4300, including
  3.2504 -  the 4640, 4650, and 4700.
  3.2505 -
  3.2506 -R5000
  3.2507 -CONFIG_CPU_R5000
  3.2508 -  MIPS Technologies R5000-series processors other than the Nevada.
  3.2509 -
  3.2510 -R52x0
  3.2511 -CONFIG_CPU_NEVADA
  3.2512 -  MIPS Technologies R52x0-series ("Nevada") processors.
  3.2513 -
  3.2514 -R8000
  3.2515 -CONFIG_CPU_R8000
  3.2516 -  MIPS Technologies R8000-series processors.
  3.2517 -
  3.2518 -R10000
  3.2519 -CONFIG_CPU_R10000
  3.2520 -  MIPS Technologies R10000-series processors.
  3.2521 -
  3.2522 -SB1
  3.2523 -CONFIG_CPU_SB1
  3.2524 -  Broadcom SiByte SB1 processor.
  3.2525 -
  3.2526 -Discontiguous Memory Support
  3.2527 -CONFIG_DISCONTIGMEM
  3.2528 -  Say Y to support efficient handling of discontiguous physical memory,
  3.2529 -  for architectures which are either NUMA (Non-Uniform Memory Access)
  3.2530 -  or have huge holes in the physical address space for other reasons.
  3.2531 -  See <file:Documentation/vm/numa> for more.
  3.2532 -
  3.2533 -Mapped kernel support
  3.2534 -CONFIG_MAPPED_KERNEL
  3.2535 -  Change the way a Linux kernel is loaded unto memory on a MIPS64
  3.2536 -  machine.  This is required in order to support text replication and
  3.2537 -  NUMA.  If you need to understand it, read the source code.
  3.2538 -
  3.2539 -Kernel text replication support
  3.2540 -CONFIG_REPLICATE_KTEXT
  3.2541 -  Say Y here to enable replicating the kernel text across multiple
  3.2542 -  nodes in a NUMA cluster.  This trades memory for speed.
  3.2543 -
  3.2544 -Exception handler replication support
  3.2545 -CONFIG_REPLICATE_EXHANDLERS
  3.2546 -  Say Y here to enable replicating the kernel exception handlers
  3.2547 -  across multiple nodes in a NUMA cluster. This trades memory for
  3.2548 -  speed.
  3.2549 -
  3.2550 -NUMA support?
  3.2551 -CONFIG_NUMA
  3.2552 -  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
  3.2553 -  Access).  This option is for configuring high-end multiprocessor
  3.2554 -  server machines.  If in doubt, say N.
  3.2555 -
  3.2556 -R41xx
  3.2557 -CONFIG_CPU_VR41XX
  3.2558 -  The options selects support for the NEC VR41xx series of processors.
  3.2559 -  Only choose this option if you have one of these processors as a
  3.2560 -  kernel built with this option will not run on any other type of
  3.2561 -  processor or vice versa.
  3.2562 -
  3.2563 -CPU feature configuration
  3.2564 -CONFIG_CPU_ADVANCED
  3.2565 -  Saying yes here allows you to select support for various features
  3.2566 -  your CPU may or may not have.  Most people should say N here.
  3.2567 -
  3.2568 -ll and sc instructions available
  3.2569 -CONFIG_CPU_HAS_LLSC
  3.2570 -  MIPS R4000 series and later provide the Load Linked (ll)
  3.2571 -  and Store Conditional (sc) instructions. More information is
  3.2572 -  available at <http://www.go-ecs.com/mips/miptek1.htm>.
  3.2573 -
  3.2574 -  Say Y here if your CPU has the ll and sc instructions.  Say Y here
  3.2575 -  for better performance, N if you don't know.  You must say Y here
  3.2576 -  for multiprocessor machines.
  3.2577 -
  3.2578 -lld and scd instructions available
  3.2579 -CONFIG_CPU_HAS_LLDSCD
  3.2580 -  Say Y here if your CPU has the lld and scd instructions, the 64-bit
  3.2581 -  equivalents of ll and sc.  Say Y here for better performance, N if
  3.2582 -  you don't know.  You must say Y here for multiprocessor machines.
  3.2583 -
  3.2584 -Writeback Buffer available
  3.2585 -CONFIG_CPU_HAS_WB
  3.2586 -  Say N here for slightly better performance.  You must say Y here for
  3.2587 -  machines which require flushing of write buffers in software.  Saying
  3.2588 -  Y is the safe option; N may result in kernel malfunction and crashes.
  3.2589 -
  3.2590 -Support for large 64-bit configurations
  3.2591 -CONFIG_MIPS_INSANE_LARGE
  3.2592 -  MIPS R10000 does support a 44 bit / 16TB address space as opposed to
  3.2593 -  previous 64-bit processors which only supported 40 bit / 1TB. If you
  3.2594 -  need processes of more than 1TB virtual address space, say Y here.
  3.2595 -  This will result in additional memory usage, so it is not
  3.2596 -  recommended for normal users.
  3.2597 -
  3.2598 -Generate little endian code
  3.2599 -CONFIG_CPU_LITTLE_ENDIAN
  3.2600 -  Some MIPS machines can be configured for either little or big endian
  3.2601 -  byte order. These modes require different kernels. Say Y if your
  3.2602 -  machine is little endian, N if it's a big endian machine.
  3.2603 -
  3.2604 -Use power LED as a heartbeat
  3.2605 -CONFIG_HEARTBEAT
  3.2606 -  Use the power-on LED on your machine as a load meter.  The exact
  3.2607 -  behaviour is platform-dependent, but normally the flash frequency is
  3.2608 -  a hyperbolic function of the 5-minute load average.
  3.2609 -
  3.2610 -Networking support
  3.2611 -CONFIG_NET
  3.2612 -  Unless you really know what you are doing, you should say Y here.
  3.2613 -  The reason is that some programs need kernel networking support even
  3.2614 -  when running on a stand-alone machine that isn't connected to any
  3.2615 -  other computer. If you are upgrading from an older kernel, you
  3.2616 -  should consider updating your networking tools too because changes
  3.2617 -  in the kernel and the tools often go hand in hand. The tools are
  3.2618 -  contained in the package net-tools, the location and version number
  3.2619 -  of which are given in <file:Documentation/Changes>.
  3.2620 -
  3.2621 -  For a general introduction to Linux networking, it is highly
  3.2622 -  recommended to read the NET-HOWTO, available from
  3.2623 -  <http://www.tldp.org/docs.html#howto>.
  3.2624 -
  3.2625 -Socket filtering
  3.2626 -CONFIG_FILTER
  3.2627 -  The Linux Socket Filter is derived from the Berkeley Packet Filter.
  3.2628 -  If you say Y here, user-space programs can attach a filter to any
  3.2629 -  socket and thereby tell the kernel that it should allow or disallow
  3.2630 -  certain types of data to get through the socket.  Linux Socket
  3.2631 -  Filtering works on all socket types except TCP for now.  See the
  3.2632 -  text file <file:Documentation/networking/filter.txt> for more
  3.2633 -  information.
  3.2634 -
  3.2635 -  You need to say Y here if you want to use PPP packet filtering
  3.2636 -  (see the CONFIG_PPP_FILTER option below).
  3.2637 -
  3.2638 -  If unsure, say N.
  3.2639 -
  3.2640 -Network packet filtering (replaces ipchains)
  3.2641 -CONFIG_NETFILTER
  3.2642 -  Netfilter is a framework for filtering and mangling network packets
  3.2643 -  that pass through your Linux box.
  3.2644 -
  3.2645 -  The most common use of packet filtering is to run your Linux box as
  3.2646 -  a firewall protecting a local network from the Internet. The type of
  3.2647 -  firewall provided by this kernel support is called a "packet
  3.2648 -  filter", which means that it can reject individual network packets
  3.2649 -  based on type, source, destination etc. The other kind of firewall,
  3.2650 -  a "proxy-based" one, is more secure but more intrusive and more
  3.2651 -  bothersome to set up; it inspects the network traffic much more
  3.2652 -  closely, modifies it and has knowledge about the higher level
  3.2653 -  protocols, which a packet filter lacks. Moreover, proxy-based
  3.2654 -  firewalls often require changes to the programs running on the local
  3.2655 -  clients. Proxy-based firewalls don't need support by the kernel, but
  3.2656 -  they are often combined with a packet filter, which only works if
  3.2657 -  you say Y here.
  3.2658 -
  3.2659 -  You should also say Y here if you intend to use your Linux box as
  3.2660 -  the gateway to the Internet for a local network of machines without
  3.2661 -  globally valid IP addresses. This is called "masquerading": if one
  3.2662 -  of the computers on your local network wants to send something to
  3.2663 -  the outside, your box can "masquerade" as that computer, i.e. it
  3.2664 -  forwards the traffic to the intended outside destination, but
  3.2665 -  modifies the packets to make it look like they came from the
  3.2666 -  firewall box itself. It works both ways: if the outside host
  3.2667 -  replies, the Linux box will silently forward the traffic to the
  3.2668 -  correct local computer. This way, the computers on your local net
  3.2669 -  are completely invisible to the outside world, even though they can
  3.2670 -  reach the outside and can receive replies. It is even possible to
  3.2671 -  run globally visible servers from within a masqueraded local network
  3.2672 -  using a mechanism called portforwarding. Masquerading is also often
  3.2673 -  called NAT (Network Address Translation).
  3.2674 -
  3.2675 -  Another use of Netfilter is in transparent proxying: if a machine on
  3.2676 -  the local network tries to connect to an outside host, your Linux
  3.2677 -  box can transparently forward the traffic to a local server,
  3.2678 -  typically a caching proxy server.
  3.2679 -
  3.2680 -  Various modules exist for netfilter which replace the previous
  3.2681 -  masquerading (ipmasqadm), packet filtering (ipchains), transparent
  3.2682 -  proxying, and portforwarding mechanisms. Please see
  3.2683 -  <file:Documentation/Changes> under "iptables" for the location of
  3.2684 -  these packages.
  3.2685 -
  3.2686 -  Make sure to say N to "Fast switching" below if you intend to say Y
  3.2687 -  here, as Fast switching currently bypasses netfilter.
  3.2688 -
  3.2689 -  Chances are that you should say Y here if you compile a kernel which
  3.2690 -  will run as a router and N for regular hosts. If unsure, say N.
  3.2691 -
  3.2692 -Network packet filtering debugging
  3.2693 -CONFIG_NETFILTER_DEBUG
  3.2694 -  You can say Y here if you want to get additional messages useful in
  3.2695 -  debugging the netfilter code.
  3.2696 -
  3.2697 -Connection tracking (required for masq/NAT)
  3.2698 -CONFIG_IP_NF_CONNTRACK
  3.2699 -  Connection tracking keeps a record of what packets have passed
  3.2700 -  through your machine, in order to figure out how they are related
  3.2701 -  into connections.
  3.2702 -
  3.2703 -  This is required to do Masquerading or other kinds of Network
  3.2704 -  Address Translation (except for Fast NAT).  It can also be used to
  3.2705 -  enhance packet filtering (see `Connection state match support'
  3.2706 -  below).
  3.2707 -
  3.2708 -  If you want to compile it as a module, say M here and read
  3.2709 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2710 -
  3.2711 -Amanda protocol support
  3.2712 -CONFIG_IP_NF_AMANDA
  3.2713 -  If you are running the Amanda backup package (http://www.amanda.org/)
  3.2714 -  on this machine or machines that will be MASQUERADED through this
  3.2715 -  machine, then you may want to enable this feature.  This allows the
  3.2716 -  connection tracking and natting code to allow the sub-channels that
  3.2717 -  Amanda requires for communication of the backup data, messages and
  3.2718 -  index.
  3.2719 -
  3.2720 -  If you want to compile it as a module, say M here and read
  3.2721 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2722 -
  3.2723 -
  3.2724 -IRC Send/Chat protocol support
  3.2725 -CONFIG_IP_NF_IRC
  3.2726 -  There is a commonly-used extension to IRC called
  3.2727 -  Direct Client-to-Client Protocol (DCC).  This enables users to send
  3.2728 -  files to each other, and also chat to each other without the need
  3.2729 -  of a server.  DCC Sending is used anywhere you send files over IRC,
  3.2730 -  and DCC Chat is most commonly used by Eggdrop bots.  If you are
  3.2731 -  using NAT, this extension will enable you to send files and initiate
  3.2732 -  chats.  Note that you do NOT need this extension to get files or
  3.2733 -  have others initiate chats, or everything else in IRC.
  3.2734 -
  3.2735 -  If you want to compile it as a module, say 'M' here and read
  3.2736 -  Documentation/modules.txt.  If unsure, say 'N'.
  3.2737 -
  3.2738 -TFTP protocol support
  3.2739 -CONFIG_IP_NF_TFTP
  3.2740 -  TFTP connection tracking helper, this is required depending
  3.2741 -  on how restrictive your ruleset is.
  3.2742 -  If you are using a tftp client behind -j SNAT or -j MASQUERADING
  3.2743 -  you will need this.
  3.2744 -
  3.2745 -  If you want to compile it as a module, say M here and read
  3.2746 -  Documentation/modules.txt.  If unsure, say `Y'.
  3.2747 -
  3.2748 -FTP protocol support
  3.2749 -CONFIG_IP_NF_FTP
  3.2750 -  Tracking FTP connections is problematic: special helpers are
  3.2751 -  required for tracking them, and doing masquerading and other forms
  3.2752 -  of Network Address Translation on them.
  3.2753 -
  3.2754 -  If you want to compile it as a module, say M here and read
  3.2755 -  <file:Documentation/modules.txt>.  If unsure, say `Y'.
  3.2756 -
  3.2757 -User space queueing via NETLINK
  3.2758 -CONFIG_IP_NF_QUEUE
  3.2759 -  Netfilter has the ability to queue packets to user space: the
  3.2760 -  netlink device can be used to access them using this driver.
  3.2761 -
  3.2762 -  If you want to compile it as a module, say M here and read
  3.2763 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2764 -
  3.2765 -IP tables support (required for filtering/masq/NAT)
  3.2766 -CONFIG_IP_NF_IPTABLES
  3.2767 -  iptables is a general, extensible packet identification framework.
  3.2768 -  The packet filtering and full NAT (masquerading, port forwarding,
  3.2769 -  etc) subsystems now use this: say `Y' or `M' here if you want to use
  3.2770 -  either of those.
  3.2771 -
  3.2772 -  If you want to compile it as a module, say M here and read
  3.2773 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2774 -
  3.2775 -recent match support
  3.2776 -CONFIG_IP_NF_MATCH_RECENT
  3.2777 -  This match is used for creating one or many lists of recently
  3.2778 -  used addresses and then matching against that/those list(s).
  3.2779 -
  3.2780 -  Short options are available by using 'iptables -m recent -h'
  3.2781 -  Official Website: <http://snowman.net/projects/ipt_recent/>
  3.2782 -
  3.2783 -  If you want to compile it as a module, say M here and read
  3.2784 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2785 -
  3.2786 -limit match support
  3.2787 -CONFIG_IP_NF_MATCH_LIMIT
  3.2788 -  limit matching allows you to control the rate at which a rule can be
  3.2789 -  matched: mainly useful in combination with the LOG target ("LOG
  3.2790 -  target support", below) and to avoid some Denial of Service attacks.
  3.2791 -
  3.2792 -  If you want to compile it as a module, say M here and read
  3.2793 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2794 -
  3.2795 -skb->pkt_type packet match support
  3.2796 -CONFIG_IP_NF_MATCH_PKTTYPE
  3.2797 -  This patch allows you to match packet in accrodance
  3.2798 -  to its "class", eg. BROADCAST, MULTICAST, ...
  3.2799 -  
  3.2800 -  Typical usage:
  3.2801 -  iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  3.2802 -  
  3.2803 -  If you want to compile it as a module, say M here and read
  3.2804 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2805 -
  3.2806 -MAC address match support
  3.2807 -CONFIG_IP_NF_MATCH_MAC
  3.2808 -  MAC matching allows you to match packets based on the source
  3.2809 -  Ethernet address of the packet.
  3.2810 -
  3.2811 -  If you want to compile it as a module, say M here and read
  3.2812 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2813 -
  3.2814 -Netfilter MARK match support
  3.2815 -CONFIG_IP_NF_MATCH_MARK
  3.2816 -  Netfilter mark matching allows you to match packets based on the
  3.2817 -  `nfmark' value in the packet.  This can be set by the MARK target
  3.2818 -  (see below).
  3.2819 -
  3.2820 -  If you want to compile it as a module, say M here and read
  3.2821 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2822 -
  3.2823 -Multiple port match support
  3.2824 -CONFIG_IP_NF_MATCH_MULTIPORT
  3.2825 -  Multiport matching allows you to match TCP or UDP packets based on
  3.2826 -  a series of source or destination ports: normally a rule can only
  3.2827 -  match a single range of ports.
  3.2828 -
  3.2829 -  If you want to compile it as a module, say M here and read
  3.2830 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2831 -
  3.2832 -TTL match support
  3.2833 -CONFIG_IP_NF_MATCH_TTL
  3.2834 -  This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
  3.2835 -  to match packets by their TTL value.
  3.2836 -
  3.2837 -  If you want to compile it as a module, say M here and read
  3.2838 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2839 -
  3.2840 -LENGTH match support
  3.2841 -CONFIG_IP_NF_MATCH_LENGTH
  3.2842 -  This option allows you to match the length of a packet against a
  3.2843 -  specific value or range of values.
  3.2844 -
  3.2845 -  If you want to compile it as a module, say M here and read
  3.2846 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2847 -
  3.2848 -AH/ESP match support
  3.2849 -CONFIG_IP_NF_MATCH_AH_ESP
  3.2850 -  These two match extensions (`ah' and `esp') allow you to match a
  3.2851 -  range of SPIs inside AH or ESP headers of IPSec packets.
  3.2852 -
  3.2853 -  If you want to compile it as a module, say M here and read
  3.2854 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2855 -
  3.2856 -DSCP match support
  3.2857 -CONFIG_IP_NF_MATCH_DSCP
  3.2858 -  This option adds a `DSCP' match, which allows you to match against
  3.2859 -  the IPv4 header DSCP field (DSCP codepoint).
  3.2860 -
  3.2861 -  The DSCP codepoint can have any value between 0x0 and 0x4f.
  3.2862 -
  3.2863 -  If you want to compile it as a module, say M here and read
  3.2864 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2865 -
  3.2866 - 
  3.2867 -
  3.2868 -ECN match support
  3.2869 -CONFIG_IP_NF_MATCH_ECN
  3.2870 -  This option adds a `ECN' match, which allows you to match against
  3.2871 -  the IPv4 and TCP header ECN fields.
  3.2872 -
  3.2873 -  If you want to compile it as a module, say M here and read
  3.2874 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2875 -
  3.2876 - 
  3.2877 -
  3.2878 -TOS match support
  3.2879 -CONFIG_IP_NF_MATCH_TOS
  3.2880 -  TOS matching allows you to match packets based on the Type Of
  3.2881 -  Service fields of the IP packet.
  3.2882 -
  3.2883 -  If you want to compile it as a module, say M here and read
  3.2884 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2885 -
  3.2886 -conntrack match support
  3.2887 -CONFIG_IP_NF_MATCH_CONNTRACK
  3.2888 -  This is a general conntrack match module, a superset of the state match.
  3.2889 -
  3.2890 -  It allows matching on additional conntrack information, which is
  3.2891 -  useful in complex configurations, such as NAT gateways with multiple
  3.2892 -  internet links or tunnels.
  3.2893 -
  3.2894 -  If you want to compile it as a module, say M here and read
  3.2895 -  Documentation/modules.txt.  If unsure, say `N'.
  3.2896 -
  3.2897 -
  3.2898 -Connection state match support
  3.2899 -CONFIG_IP_NF_MATCH_STATE
  3.2900 -  Connection state matching allows you to match packets based on their
  3.2901 -  relationship to a tracked connection (ie. previous packets).  This
  3.2902 -  is a powerful tool for packet classification.
  3.2903 -
  3.2904 -  If you want to compile it as a module, say M here and read
  3.2905 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2906 -
  3.2907 -Unclean match support
  3.2908 -CONFIG_IP_NF_MATCH_UNCLEAN
  3.2909 -  Unclean packet matching matches any strange or invalid packets, by
  3.2910 -  looking at a series of fields in the IP, TCP, UDP and ICMP headers.
  3.2911 -
  3.2912 -  If you want to compile it as a module, say M here and read
  3.2913 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2914 -
  3.2915 -Owner match support
  3.2916 -CONFIG_IP_NF_MATCH_OWNER
  3.2917 -  Packet owner matching allows you to match locally-generated packets
  3.2918 -  based on who created them: the user, group, process or session.
  3.2919 -
  3.2920 -  If you want to compile it as a module, say M here and read
  3.2921 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2922 -
  3.2923 -Packet filtering
  3.2924 -CONFIG_IP_NF_FILTER
  3.2925 -  Packet filtering defines a table `filter', which has a series of
  3.2926 -  rules for simple packet filtering at local input, forwarding and
  3.2927 -  local output.  See the man page for iptables(8).
  3.2928 -
  3.2929 -  If you want to compile it as a module, say M here and read
  3.2930 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2931 -
  3.2932 -REJECT target support
  3.2933 -CONFIG_IP_NF_TARGET_REJECT
  3.2934 -  The REJECT target allows a filtering rule to specify that an ICMP
  3.2935 -  error should be issued in response to an incoming packet, rather
  3.2936 -  than silently being dropped.
  3.2937 -
  3.2938 -  If you want to compile it as a module, say M here and read
  3.2939 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2940 -
  3.2941 -MIRROR target support
  3.2942 -CONFIG_IP_NF_TARGET_MIRROR
  3.2943 -  The MIRROR target allows a filtering rule to specify that an
  3.2944 -  incoming packet should be bounced back to the sender.
  3.2945 -
  3.2946 -  If you want to compile it as a module, say M here and read
  3.2947 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2948 -
  3.2949 -Local NAT support
  3.2950 -CONFIG_IP_NF_NAT_LOCAL
  3.2951 -  This option enables support for NAT of locally originated connections. 
  3.2952 -  Enable this if you need to use destination NAT on connections
  3.2953 -  originating from local processes on the nat box itself.
  3.2954 -
  3.2955 -  Please note that you will need a recent version (>= 1.2.6a)
  3.2956 -  of the iptables userspace program in order to use this feature.
  3.2957 -  See <http://www.iptables.org/> for download instructions.
  3.2958 -
  3.2959 -  If unsure, say 'N'.
  3.2960 -
  3.2961 -
  3.2962 -Full NAT (Network Address Translation)
  3.2963 -CONFIG_IP_NF_NAT
  3.2964 -  The Full NAT option allows masquerading, port forwarding and other
  3.2965 -  forms of full Network Address Port Translation.  It is controlled by
  3.2966 -  the `nat' table in iptables: see the man page for iptables(8).
  3.2967 -
  3.2968 -  If you want to compile it as a module, say M here and read
  3.2969 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2970 -
  3.2971 -MASQUERADE target support
  3.2972 -CONFIG_IP_NF_TARGET_MASQUERADE
  3.2973 -  Masquerading is a special case of NAT: all outgoing connections are
  3.2974 -  changed to seem to come from a particular interface's address, and
  3.2975 -  if the interface goes down, those connections are lost.  This is
  3.2976 -  only useful for dialup accounts with dynamic IP address (ie. your IP
  3.2977 -  address will be different on next dialup).
  3.2978 -
  3.2979 -  If you want to compile it as a module, say M here and read
  3.2980 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2981 -
  3.2982 -Basic SNMP-ALG support
  3.2983 -CONFIG_IP_NF_NAT_SNMP_BASIC
  3.2984 -
  3.2985 -  This module implements an Application Layer Gateway (ALG) for
  3.2986 -  SNMP payloads.  In conjunction with NAT, it allows a network
  3.2987 -  management system to access multiple private networks with
  3.2988 -  conflicting addresses.  It works by modifying IP addresses
  3.2989 -  inside SNMP payloads to match IP-layer NAT mapping.
  3.2990 -
  3.2991 -  This is the "basic" form of SNMP-ALG, as described in RFC 2962
  3.2992 -
  3.2993 -  If you want to compile it as a module, say M here and read
  3.2994 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.2995 -
  3.2996 -REDIRECT target support
  3.2997 -CONFIG_IP_NF_TARGET_REDIRECT
  3.2998 -  REDIRECT is a special case of NAT: all incoming connections are
  3.2999 -  mapped onto the incoming interface's address, causing the packets to
  3.3000 -  come to the local machine instead of passing through.  This is
  3.3001 -  useful for transparent proxies.
  3.3002 -
  3.3003 -  If you want to compile it as a module, say M here and read
  3.3004 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3005 -
  3.3006 -Packet mangling
  3.3007 -CONFIG_IP_NF_MANGLE
  3.3008 -  This option adds a `mangle' table to iptables: see the man page for
  3.3009 -  iptables(8).  This table is used for various packet alterations
  3.3010 -  which can effect how the packet is routed.
  3.3011 -
  3.3012 -  If you want to compile it as a module, say M here and read
  3.3013 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3014 -
  3.3015 -DSCP target support
  3.3016 -CONFIG_IP_NF_TARGET_DSCP
  3.3017 -  This option adds a `DSCP' target, which allows you to create rules in
  3.3018 -  the iptables mangle table. The selected packet has the DSCP field set
  3.3019 -  to the hex value provided on the command line; unlike the TOS target
  3.3020 -  which will only set the legal values within ip.h.
  3.3021 -
  3.3022 -  The DSCP field can be set to any value between 0x0 and 0x4f. It does
  3.3023 -  take into account that bits 6 and 7 are used by ECN.
  3.3024 -
  3.3025 -  If you want to compile it as a module, say M here and read
  3.3026 -  Documentation/modules.txt.  If unsure, say `N'.
  3.3027 -
  3.3028 - 
  3.3029 -
  3.3030 -ECN target support
  3.3031 -CONFIG_IP_NF_TARGET_ECN
  3.3032 -  This option adds a `ECN' target, which can be used in the iptables mangle
  3.3033 -  table.  
  3.3034 -
  3.3035 -  You can use this target to remove the ECN bits from the IPv4 header of
  3.3036 -  an IP packet.  This is particularly useful, if you need to work around
  3.3037 -  existing ECN blackholes on the internet, but don't want to disable
  3.3038 -  ECN support in general.
  3.3039 -
  3.3040 -  If you want to compile it as a module, say M here and read
  3.3041 -  Documentation/modules.txt.  If unsure, say `N'.
  3.3042 -
  3.3043 - 
  3.3044 -
  3.3045 -TOS target support
  3.3046 -CONFIG_IP_NF_TARGET_TOS
  3.3047 -  This option adds a `TOS' target, which allows you to create rules in
  3.3048 -  the `mangle' table which alter the Type Of Service field of an IP
  3.3049 -  packet prior to routing.
  3.3050 -
  3.3051 -  If you want to compile it as a module, say M here and read
  3.3052 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3053 -
  3.3054 -MARK target support
  3.3055 -CONFIG_IP_NF_TARGET_MARK
  3.3056 -  This option adds a `MARK' target, which allows you to create rules
  3.3057 -  in the `mangle' table which alter the netfilter mark (nfmark) field
  3.3058 -  associated with the packet prior to routing. This can change
  3.3059 -  the routing method (see `Use netfilter MARK value as routing
  3.3060 -  key') and can also be used by other subsystems to change their
  3.3061 -  behaviour.
  3.3062 -
  3.3063 -  If you want to compile it as a module, say M here and read
  3.3064 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3065 -
  3.3066 -TCPMSS target support
  3.3067 -CONFIG_IP_NF_TARGET_TCPMSS
  3.3068 -  This option adds a `TCPMSS' target, which allows you to alter the
  3.3069 -  MSS value of TCP SYN packets, to control the maximum size for that
  3.3070 -  connection (usually limiting it to your outgoing interface's MTU
  3.3071 -  minus 40).
  3.3072 -
  3.3073 -  This is used to overcome criminally braindead ISPs or servers which
  3.3074 -  block ICMP Fragmentation Needed packets.  The symptoms of this
  3.3075 -  problem are that everything works fine from your Linux
  3.3076 -  firewall/router, but machines behind it can never exchange large
  3.3077 -  packets:
  3.3078 -	1) Web browsers connect, then hang with no data received.
  3.3079 -	2) Small mail works fine, but large emails hang.
  3.3080 -	3) ssh works fine, but scp hangs after initial handshaking.
  3.3081 -
  3.3082 -  Workaround: activate this option and add a rule to your firewall
  3.3083 -  configuration like:
  3.3084 -
  3.3085 -        iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  3.3086 -		 -j TCPMSS --clamp-mss-to-pmtu
  3.3087 -
  3.3088 -  If you want to compile it as a module, say M here and read
  3.3089 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3090 -
  3.3091 -Helper match support
  3.3092 -CONFIG_IP_NF_MATCH_HELPER
  3.3093 -  Helper matching allows you to match packets in dynamic connections
  3.3094 -  tracked by a conntrack-helper, ie. ip_conntrack_ftp
  3.3095 -
  3.3096 -  If you want to compile it as a module, say M here and read
  3.3097 -  Documentation/modules.txt.  If unsure, say `Y'.
  3.3098 -
  3.3099 -TCPMSS match support
  3.3100 -CONFIG_IP_NF_MATCH_TCPMSS
  3.3101 -  This option adds a `tcpmss' match, which allows you to examine the
  3.3102 -  MSS value of TCP SYN packets, which control the maximum packet size
  3.3103 -  for that connection.
  3.3104 -
  3.3105 -  If you want to compile it as a module, say M here and read
  3.3106 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3107 -
  3.3108 -ULOG target support
  3.3109 -CONFIG_IP_NF_TARGET_ULOG
  3.3110 -  This option adds a `ULOG' target, which allows you to create rules in
  3.3111 -  any iptables table. The packet is passed to a userspace logging
  3.3112 -  daemon using netlink multicast sockets; unlike the LOG target
  3.3113 -  which can only be viewed through syslog.
  3.3114 -
  3.3115 -  The appropriate userspace logging daemon (ulogd) may be obtained from
  3.3116 -  <http://www.gnumonks.org/projects/ulogd>
  3.3117 -
  3.3118 -  If you want to compile it as a module, say M here and read
  3.3119 -  Documentation/modules.txt.  If unsure, say `N'.
  3.3120 -
  3.3121 -LOG target support
  3.3122 -CONFIG_IP_NF_TARGET_LOG
  3.3123 -  This option adds a `LOG' target, which allows you to create rules in
  3.3124 -  any iptables table which records the packet header to the syslog.
  3.3125 -
  3.3126 -  If you want to compile it as a module, say M here and read
  3.3127 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3128 -
  3.3129 -ipchains (2.2-style) support
  3.3130 -CONFIG_IP_NF_COMPAT_IPCHAINS
  3.3131 -  This option places ipchains (with masquerading and redirection
  3.3132 -  support) back into the kernel, using the new netfilter
  3.3133 -  infrastructure.  It is not recommended for new installations (see
  3.3134 -  `Packet filtering').  With this enabled, you should be able to use
  3.3135 -  the ipchains tool exactly as in 2.2 kernels.
  3.3136 -
  3.3137 -  If you want to compile it as a module, say M here and read
  3.3138 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3139 -
  3.3140 -ipfwadm (2.0-style) support
  3.3141 -CONFIG_IP_NF_COMPAT_IPFWADM
  3.3142 -  This option places ipfwadm (with masquerading and redirection
  3.3143 -  support) back into the kernel, using the new netfilter
  3.3144 -  infrastructure.  It is not recommended for new installations (see
  3.3145 -  `Packet filtering').  With this enabled, you should be able to use
  3.3146 -  the ipfwadm tool exactly as in 2.0 kernels.
  3.3147 -
  3.3148 -  If you want to compile it as a module, say M here and read
  3.3149 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3150 -
  3.3151 -EUI64 address check (EXPERIMENTAL)
  3.3152 -CONFIG_IP6_NF_MATCH_EUI64
  3.3153 -  This module performs checking on the IPv6 source address
  3.3154 -  Compares the last 64 bits with the EUI64 (delivered
  3.3155 -  from the MAC address) address
  3.3156 -
  3.3157 -  If you want to compile it as a module, say M here and read
  3.3158 -  Documentation/modules.txt.  If unsure, say `N'.
  3.3159 -
  3.3160 -MAC address match support
  3.3161 -CONFIG_IP6_NF_MATCH_MAC
  3.3162 -  mac matching allows you to match packets based on the source
  3.3163 -  Ethernet address of the packet.
  3.3164 -
  3.3165 -  If you want to compile it as a module, say M here and read
  3.3166 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3167 -
  3.3168 -length match support
  3.3169 -CONFIG_IP6_NF_MATCH_LENGTH
  3.3170 -  This option allows you to match the length of a packet against a
  3.3171 -  specific value or range of values.
  3.3172 -
  3.3173 -  If you want to compile it as a module, say M here and read
  3.3174 -  Documentation/modules.txt.  If unsure, say `N'.
  3.3175 -
  3.3176 -Netfilter MARK match support
  3.3177 -CONFIG_IP6_NF_MATCH_MARK
  3.3178 -  Netfilter mark matching allows you to match packets based on the
  3.3179 -  `nfmark' value in the packet.  This can be set by the MARK target
  3.3180 -  (see below).
  3.3181 -
  3.3182 -  If you want to compile it as a module, say M here and read
  3.3183 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3184 -
  3.3185 -Multiple port match support
  3.3186 -CONFIG_IP6_NF_MATCH_MULTIPORT
  3.3187 -  Multiport matching allows you to match TCP or UDP packets based on
  3.3188 -  a series of source or destination ports: normally a rule can only
  3.3189 -  match a single range of ports.
  3.3190 -
  3.3191 -  If you want to compile it as a module, say M here and read
  3.3192 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3193 -
  3.3194 -IPV6 queue handler (EXPERIMENTAL)
  3.3195 -CONFIG_IP6_NF_QUEUE
  3.3196 -
  3.3197 -  This option adds a queue handler to the kernel for IPv6
  3.3198 -  packets which lets us to receive the filtered packets
  3.3199 -  with QUEUE target using libiptc as we can do with
  3.3200 -  the IPv4 now.
  3.3201 -
  3.3202 -  (C) Fernando Anton 2001
  3.3203 -  IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
  3.3204 -  Universidad Carlos III de Madrid
  3.3205 -  Universidad Politecnica de Alcala de Henares
  3.3206 -  email: fanton@it.uc3m.es
  3.3207 -
  3.3208 -  If you want to compile it as a module, say M here and read
  3.3209 -  Documentation/modules.txt. If unsure, say `N'.
  3.3210 -
  3.3211 -Owner match support
  3.3212 -CONFIG_IP6_NF_MATCH_OWNER
  3.3213 -  Packet owner matching allows you to match locally-generated packets
  3.3214 -  based on who created them: the user, group, process or session.
  3.3215 -
  3.3216 -  If you want to compile it as a module, say M here and read
  3.3217 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3218 -
  3.3219 -Packet filtering
  3.3220 -CONFIG_IP6_NF_FILTER
  3.3221 -  Packet filtering defines a table `filter', which has a series of
  3.3222 -  rules for simple packet filtering at local input, forwarding and
  3.3223 -  local output.  See the man page for iptables(8).
  3.3224 -
  3.3225 -  If you want to compile it as a module, say M here and read
  3.3226 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3227 -
  3.3228 -Packet mangling
  3.3229 -CONFIG_IP6_NF_MANGLE
  3.3230 -  This option adds a `mangle' table to iptables: see the man page for
  3.3231 -  iptables(8).  This table is used for various packet alterations
  3.3232 -  which can effect how the packet is routed.
  3.3233 -
  3.3234 -  If you want to compile it as a module, say M here and read
  3.3235 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3236 -
  3.3237 -MARK target support
  3.3238 -CONFIG_IP6_NF_TARGET_MARK
  3.3239 -  This option adds a `MARK' target, which allows you to create rules
  3.3240 -  in the `mangle' table which alter the netfilter mark (nfmark) field
  3.3241 -  associated with the packet packet prior to routing. This can change
  3.3242 -  the routing method (see `Use netfilter MARK value as routing
  3.3243 -  key') and can also be used by other subsystems to change their
  3.3244 -  behaviour.
  3.3245 -
  3.3246 -  If you want to compile it as a module, say M here and read
  3.3247 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3248 -
  3.3249 -ARP payload mangling
  3.3250 -CONFIG_IP_NF_ARP_MANGLE
  3.3251 -  Allows altering the ARP packet payload: source and destination
  3.3252 -  hardware and network addresses.
  3.3253 -
  3.3254 -TCP Explicit Congestion Notification support
  3.3255 -CONFIG_INET_ECN
  3.3256 -  Explicit Congestion Notification (ECN) allows routers to notify
  3.3257 -  clients about network congestion, resulting in fewer dropped packets
  3.3258 -  and increased network performance.  This option adds ECN support to
  3.3259 -  the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
  3.3260 -  which allows ECN support to be disabled at runtime.
  3.3261 -
  3.3262 -  Note that, on the Internet, there are many broken firewalls which
  3.3263 -  refuse connections from ECN-enabled machines, and it may be a while
  3.3264 -  before these firewalls are fixed.  Until then, to access a site
  3.3265 -  behind such a firewall (some of which are major sites, at the time
  3.3266 -  of this writing) you will have to disable this option, either by
  3.3267 -  saying N now or by using the sysctl.
  3.3268 -
  3.3269 -  If in doubt, say N.
  3.3270 -
  3.3271 -IPv6 tables support (required for filtering/masq/NAT)
  3.3272 -CONFIG_IP6_NF_IPTABLES
  3.3273 -  ip6tables is a general, extensible packet identification framework.
  3.3274 -  Currently only the packet filtering and packet mangling subsystem
  3.3275 -  for IPv6 use this, but connection tracking is going to follow.
  3.3276 -  Say 'Y' or 'M' here if you want to use either of those.
  3.3277 -
  3.3278 -  If you want to compile it as a module, say M here and read
  3.3279 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3280 -
  3.3281 -IPv6 limit match support
  3.3282 -CONFIG_IP6_NF_MATCH_LIMIT
  3.3283 -  limit matching allows you to control the rate at which a rule can be
  3.3284 -  matched: mainly useful in combination with the LOG target ("LOG
  3.3285 -  target support", below) and to avoid some Denial of Service attacks.
  3.3286 -
  3.3287 -  If you want to compile it as a module, say M here and read
  3.3288 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3289 -
  3.3290 -LOG target support
  3.3291 -CONFIG_IP6_NF_TARGET_LOG
  3.3292 -  This option adds a `LOG' target, which allows you to create rules in
  3.3293 -  any iptables table which records the packet header to the syslog.
  3.3294 -
  3.3295 -  If you want to compile it as a module, say M here and read
  3.3296 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  3.3297 -
  3.3298 -IP: virtual server support
  3.3299 -CONFIG_IP_VS
  3.3300 -  IP Virtual Server support will let you build a high-performance
  3.3301 -  virtual server based on cluster of two or more real servers. This
  3.3302 -  option must be enabled for at least one of the clustered computers
  3.3303 -  that will take care of intercepting incomming connections to a
  3.3304 -  single IP address and scheduling them to real servers.
  3.3305 -
  3.3306 -  Three request dispatching techniques are implemented, they are
  3.3307 -  virtual server via NAT, virtual server via tunneling and virtual
  3.3308 -  server via direct routing. The several scheduling algorithms can
  3.3309 -  be used to choose which server the connection is directed to,
  3.3310 -  thus load balancing can be achieved among the servers.  For more
  3.3311 -  information and its administration program, please visit the
  3.3312 -  following URL:
  3.3313 -	http://www.linuxvirtualserver.org/
  3.3314 -
  3.3315 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3316 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3317 -  unsure, say N.
  3.3318 -
  3.3319 -IP virtual server debugging
  3.3320 -CONFIG_IP_VS_DEBUG
  3.3321 -  Say Y here if you want to get additional messages useful in
  3.3322 -  debugging the IP virtual server code. You can change the debug
  3.3323 -  level in /proc/sys/net/ipv4/vs/debug_level
  3.3324 -
  3.3325 -IPVS connection hash table size (the Nth power of 2)
  3.3326 -CONFIG_IP_VS_TAB_BITS
  3.3327 -  The IPVS connection hash table uses the chaining scheme to handle
  3.3328 -  hash collisions. Using a big IPVS connection hash table will greatly
  3.3329 -  reduce conflicts when there are hundreds of thousands of connections
  3.3330 -  in the hash table.
  3.3331 -
  3.3332 -  Note the table size must be power of 2. The table size will be the
  3.3333 -  value of 2 to the your input number power. The number to choose is
  3.3334 -  from 8 to 20, the default number is 12, which means the table size
  3.3335 -  is 4096. Don't input the number too small, otherwise you will lose
  3.3336 -  performance on it. You can adapt the table size yourself, according
  3.3337 -  to your virtual server application. It is good to set the table size
  3.3338 -  not far less than the number of connections per second multiplying
  3.3339 -  average lasting time of connection in the table.  For example, your
  3.3340 -  virtual server gets 200 connections per second, the connection lasts
  3.3341 -  for 200 seconds in average in the connection table, the table size
  3.3342 -  should be not far less than 200x200, it is good to set the table
  3.3343 -  size 32768 (2**15).
  3.3344 -
  3.3345 -  Another note that each connection occupies 128 bytes effectively and
  3.3346 -  each hash entry uses 8 bytes, so you can estimate how much memory is
  3.3347 -  needed for your box.
  3.3348 -
  3.3349 -IPVS: round-robin scheduling
  3.3350 -CONFIG_IP_VS_RR
  3.3351 -  The robin-robin scheduling algorithm simply directs network
  3.3352 -  connections to different real servers in a round-robin manner.
  3.3353 -
  3.3354 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3355 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3356 -  unsure, say N.
  3.3357 -
  3.3358 -IPVS: weighted round-robin scheduling
  3.3359 -CONFIG_IP_VS_WRR
  3.3360 -  The weighted robin-robin scheduling algorithm directs network
  3.3361 -  connections to different real servers based on server weights
  3.3362 -  in a round-robin manner. Servers with higher weights receive
  3.3363 -  new connections first than those with less weights, and servers
  3.3364 -  with higher weights get more connections than those with less
  3.3365 -  weights and servers with equal weights get equal connections.
  3.3366 -
  3.3367 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3368 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3369 -  unsure, say N.
  3.3370 -
  3.3371 -IPVS: least-connection scheduling
  3.3372 -CONFIG_IP_VS_LC
  3.3373 -  The least-connection scheduling algorithm directs network
  3.3374 -  connections to the server with the least number of active 
  3.3375 -  connections.
  3.3376 -
  3.3377 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3378 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3379 -  unsure, say N.
  3.3380 -
  3.3381 -IPVS: weighted least-connection scheduling
  3.3382 -CONFIG_IP_VS_WLC
  3.3383 -  The weighted least-connection scheduling algorithm directs network
  3.3384 -  connections to the server with the least active connections
  3.3385 -  normalized by the server weight.
  3.3386 -
  3.3387 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3388 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3389 -  unsure, say N.
  3.3390 -
  3.3391 -IPVS: locality-based least-connection scheduling
  3.3392 -CONFIG_IP_VS_LBLC
  3.3393 -  The locality-based least-connection scheduling algorithm is for
  3.3394 -  destination IP load balancing. It is usually used in cache cluster.
  3.3395 -  This algorithm usually directs packet destined for an IP address to
  3.3396 -  its server if the server is alive and under load. If the server is
  3.3397 -  overloaded (its active connection numbers is larger than its weight)
  3.3398 -  and there is a server in its half load, then allocate the weighted
  3.3399 -  least-connection server to this IP address.
  3.3400 -
  3.3401 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3402 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3403 -  unsure, say N.
  3.3404 -
  3.3405 -IPVS: locality-based least-connection with replication scheduling
  3.3406 -CONFIG_IP_VS_LBLCR
  3.3407 -  The locality-based least-connection with replication scheduling
  3.3408 -  algorithm is also for destination IP load balancing. It is 
  3.3409 -  usually used in cache cluster. It differs from the LBLC scheduling
  3.3410 -  as follows: the load balancer maintains mappings from a target
  3.3411 -  to a set of server nodes that can serve the target. Requests for
  3.3412 -  a target are assigned to the least-connection node in the target's
  3.3413 -  server set. If all the node in the server set are over loaded,
  3.3414 -  it picks up a least-connection node in the cluster and adds it
  3.3415 -  in the sever set for the target. If the server set has not been
  3.3416 -  modified for the specified time, the most loaded node is removed
  3.3417 -  from the server set, in order to avoid high degree of replication.
  3.3418 -
  3.3419 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3420 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3421 -  unsure, say N.
  3.3422 -
  3.3423 -IPVS: destination hashing scheduling
  3.3424 -CONFIG_IP_VS_DH
  3.3425 -  The destination hashing scheduling algorithm assigns network
  3.3426 -  connections to the servers through looking up a statically assigned
  3.3427 -  hash table by their destination IP addresses.
  3.3428 -
  3.3429 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3430 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3431 -  unsure, say N.
  3.3432 -
  3.3433 -IPVS: source hashing scheduling
  3.3434 -CONFIG_IP_VS_SH
  3.3435 -  The source hashing scheduling algorithm assigns network
  3.3436 -  connections to the servers through looking up a statically assigned
  3.3437 -  hash table by their source IP addresses.
  3.3438 -
  3.3439 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3440 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3441 -  unsure, say N.
  3.3442 -
  3.3443 -IPVS: shortest expected delay scheduling
  3.3444 -CONFIG_IP_VS_SED
  3.3445 -  The shortest expected delay scheduling algorithm assigns network
  3.3446 -  connections to the server with the shortest expected delay. The 
  3.3447 -  expected delay that the job will experience is (Ci + 1) / Ui if 
  3.3448 -  sent to the ith server, in which Ci is the number of connections
  3.3449 -  on the the ith server and Ui is the fixed service rate (weight)
  3.3450 -  of the ith server.
  3.3451 -
  3.3452 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3453 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3454 -  unsure, say N.
  3.3455 -
  3.3456 -IPVS: never queue scheduling
  3.3457 -CONFIG_IP_VS_NQ
  3.3458 -  The never queue scheduling algorithm adopts a two-speed model.
  3.3459 -  When there is an idle server available, the job will be sent to
  3.3460 -  the idle server, instead of waiting for a fast one. When there
  3.3461 -  is no idle server available, the job will be sent to the server
  3.3462 -  that minimize its expected delay (The Shortest Expected Delay
  3.3463 -  scheduling algorithm).
  3.3464 -
  3.3465 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3466 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3467 -  unsure, say N.
  3.3468 -
  3.3469 -IPVS: FTP protocol helper
  3.3470 -CONFIG_IP_VS_FTP
  3.3471 -  FTP is a protocol that transfers IP address and/or port number in
  3.3472 -  the payload. In the virtual server via Network Address Translation,
  3.3473 -  the IP address and port number of real servers cannot be sent to
  3.3474 -  clients in ftp connections directly, so FTP protocol helper is
  3.3475 -  required for tracking the connection and mangling it back to that of
  3.3476 -  virtual service.
  3.3477 -
  3.3478 -  If you want to compile it in kernel, say Y. If you want to compile
  3.3479 -  it as a module, say M here and read Documentation/modules.txt. If
  3.3480 -  unsure, say N.
  3.3481 -
  3.3482 -AH/ESP match support (EXPERIMENTAL)
  3.3483 -CONFIG_IP6_NF_MATCH_AHESP
  3.3484 -  This module allows one to match AH and ESP packets.
  3.3485 -
  3.3486 -  If you want to compile it as a module, say M here and read
  3.3487 -  <file:Documentation/modules.txt>.  The modules will be called
  3.3488 -  ip6t_ah.o and ip6t_esp.o.
  3.3489 -
  3.3490 -  If unsure, say 'N'.
  3.3491 -
  3.3492 -Routing header match support
  3.3493 -CONFIG_IP6_NF_MATCH_RT
  3.3494 -  rt matching allows you to match packets based on the routing
  3.3495 -  header of the packet.
  3.3496 -
  3.3497 -  If you want to compile it as a module, say M here and read
  3.3498 -  <file:Documentation/modules.txt>.  The module will be called
  3.3499 -  ip6t_rt.o.
  3.3500 -
  3.3501 -  If unsure, say 'N'.
  3.3502 -
  3.3503 -Hop-by-hop and Dst opts header match support
  3.3504 -CONFIG_IP6_NF_MATCH_OPTS
  3.3505 -  This allows one to match packets based on the hop-by-hop
  3.3506 -  and destination options headers of a packet.
  3.3507 -
  3.3508 -  If you want to compile it as a module, say M here and read
  3.3509 -  <file:Documentation/modules.txt>.  The modules will be called
  3.3510 -  ip6t_hbh.o and ip6t_dst.o.
  3.3511 -
  3.3512 -  If unsure, say 'N'.
  3.3513 -
  3.3514 -Fragmentation header match support
  3.3515 -CONFIG_IP6_NF_MATCH_FRAG
  3.3516 -  frag matching allows you to match packets based on the fragmentation
  3.3517 -  header of the packet.
  3.3518 -
  3.3519 -  If you want to compile it as a module, say M here and read
  3.3520 -  <file:Documentation/modules.txt>.  The module will be called
  3.3521 -  ip6t_frag.o.
  3.3522 -
  3.3523 -  If unsure, say 'N'.
  3.3524 -
  3.3525 -HL match support
  3.3526 -CONFIG_IP6_NF_MATCH_HL
  3.3527 -  HL matching allows you to match packets based on the hop
  3.3528 -  limit of the packet.
  3.3529 -
  3.3530 -  If you want to compile it as a module, say M here and read
  3.3531 -  <file:Documentation/modules.txt>.  The module will be called
  3.3532 -  ip6t_hl.o.
  3.3533 -
  3.3534 -  If unsure, say 'N'.
  3.3535 -
  3.3536 -IPv6 Extension Headers Match (EXPERIMENTAL)
  3.3537 -CONFIG_IP6_NF_MATCH_IPV6HEADER
  3.3538 -  This module allows one to match packets based upon
  3.3539 -  the ipv6 extension headers.
  3.3540 -
  3.3541 -  If you want to compile it as a module, say M here and read
  3.3542 -  <file:Documentation/modules.txt>.  The module will be called
  3.3543 -  ip6t_ipv6header.o.
  3.3544 -
  3.3545 -  If unsure, say 'N'.
  3.3546 -
  3.3547 -SYN flood protection
  3.3548 -CONFIG_SYN_COOKIES
  3.3549 -  Normal TCP/IP networking is open to an attack known as "SYN
  3.3550 -  flooding". This denial-of-service attack prevents legitimate remote
  3.3551 -  users from being able to connect to your computer during an ongoing
  3.3552 -  attack and requires very little work from the attacker, who can
  3.3553 -  operate from anywhere on the Internet.
  3.3554 -
  3.3555 -  SYN cookies provide protection against this type of attack. If you
  3.3556 -  say Y here, the TCP/IP stack will use a cryptographic challenge
  3.3557 -  protocol known as "SYN cookies" to enable legitimate users to
  3.3558 -  continue to connect, even when your machine is under attack. There
  3.3559 -  is no need for the legitimate users to change their TCP/IP software;
  3.3560 -  SYN cookies work transparently to them. For technical information
  3.3561 -  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
  3.3562 -
  3.3563 -  If you are SYN flooded, the source address reported by the kernel is
  3.3564 -  likely to have been forged by the attacker; it is only reported as
  3.3565 -  an aid in tracing the packets to their actual source and should not
  3.3566 -  be taken as absolute truth.
  3.3567 -
  3.3568 -  SYN cookies may prevent correct error reporting on clients when the
  3.3569 -  server is really overloaded. If this happens frequently better turn
  3.3570 -  them off.
  3.3571 -
  3.3572 -  If you say Y here, note that SYN cookies aren't enabled by default;
  3.3573 -  you can enable them by saying Y to "/proc file system support" and
  3.3574 -  "Sysctl support" below and executing the command
  3.3575 -
  3.3576 -    echo 1 >/proc/sys/net/ipv4/tcp_syncookies
  3.3577 -
  3.3578 -  at boot time after the /proc file system has been mounted.
  3.3579 -
  3.3580 -  If unsure, say N.
  3.3581 -
  3.3582 -# Choice: alphatype
  3.3583 -Alpha system type
  3.3584 -CONFIG_ALPHA_GENERIC
  3.3585 -  This is the system type of your hardware.  A "generic" kernel will
  3.3586 -  run on any supported Alpha system. However, if you configure a
  3.3587 -  kernel for your specific system, it will be faster and smaller.
  3.3588 -
  3.3589 -  To find out what type of Alpha system you have, you may want to
  3.3590 -  check out the Linux/Alpha FAQ, accessible on the WWW from
  3.3591 -  <http://www.alphalinux.org/>. In summary:
  3.3592 -
  3.3593 -  Alcor/Alpha-XLT     AS 600
  3.3594 -  Alpha-XL            XL-233, XL-266
  3.3595 -  AlphaBook1          Alpha laptop
  3.3596 -  Avanti              AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
  3.3597 -  Cabriolet           AlphaPC64, AlphaPCI64
  3.3598 -  DP264               DP264
  3.3599 -  EB164               EB164 21164 evaluation board
  3.3600 -  EB64+               EB64+ 21064 evaluation board
  3.3601 -  EB66                EB66 21066 evaluation board
  3.3602 -  EB66+               EB66+ 21066 evaluation board
  3.3603 -  Jensen              DECpc 150, DEC 2000 model 300,
  3.3604 -                      DEC 2000 model 500
  3.3605 -  LX164               AlphaPC164-LX
  3.3606 -  Miata               Personal Workstation 433a, 433au, 500a,
  3.3607 -                      500au, 600a, or 600au
  3.3608 -  Mikasa              AS 1000
  3.3609 -  Noname              AXPpci33, UDB (Multia)
  3.3610 -  Noritake            AS 1000A, AS 600A, AS 800
  3.3611 -  PC164               AlphaPC164
  3.3612 -  Rawhide             AS 1200, AS 4000, AS 4100
  3.3613 -  Ruffian             RPX164-2, AlphaPC164-UX, AlphaPC164-BX
  3.3614 -  SX164               AlphaPC164-SX
  3.3615 -  Sable               AS 2000, AS 2100
  3.3616 -  Shark		      DS 20L
  3.3617 -  Takara              Takara
  3.3618 -  Titan               Privateer
  3.3619 -  Wildfire            AlphaServer GS 40/80/160/320
  3.3620 -
  3.3621 -  If you don't know what to do, choose "generic".
  3.3622 -
  3.3623 -# Most of the information on these variants is from
  3.3624 -# <http://www.alphalinux.org/docs/alpha-howto.html>
  3.3625 -Alcor/Alpha-XLT
  3.3626 -CONFIG_ALPHA_ALCOR
  3.3627 -  For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
  3.3628 -  slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
  3.3629 -  Address, CIA) - a 383 pin plastic PGA).  It provides a DRAM
  3.3630 -  controller (256-bit memory bus) and a PCI interface.  It also does
  3.3631 -  all the work required to support an external Bcache and to maintain
  3.3632 -  memory coherence when a PCI device DMAs into (or out of) memory.
  3.3633 -
  3.3634 -Alpha-XL
  3.3635 -CONFIG_ALPHA_XL
  3.3636 -  XL-233 and XL-266-based Alpha systems.
  3.3637 -
  3.3638 -AlphaBook1
  3.3639 -CONFIG_ALPHA_BOOK1
  3.3640 -  Dec AlphaBook1/Burns Alpha-based laptops.
  3.3641 -
  3.3642 -Avanti
  3.3643 -CONFIG_ALPHA_AVANTI
  3.3644 -  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
  3.3645 -  Alphas. Info at
  3.3646 -  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
  3.3647 -
  3.3648 -Cabriolet
  3.3649 -CONFIG_ALPHA_CABRIOLET
  3.3650 -  Cabriolet AlphaPC64, AlphaPCI64 systems.  Derived from EB64+ but now
  3.3651 -  baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
  3.3652 -  slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
  3.3653 -  Bcache SIMMs.  Requires power supply with 3.3V output.
  3.3654 -
  3.3655 -DP264
  3.3656 -CONFIG_ALPHA_DP264
  3.3657 -  Various 21264 systems with the tsunami core logic chipset.
  3.3658 -  API Networks: 264DP, UP2000(+), CS20;
  3.3659 -  Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
  3.3660 -
  3.3661 -EB164
  3.3662 -CONFIG_ALPHA_EB164
  3.3663 -  EB164 21164 evaluation board from DEC.  Uses 21164 and ALCOR.  Has
  3.3664 -  ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
  3.3665 -  shared with an ISA slot) and 2 32-bit PCI slots.  Uses plus-in
  3.3666 -  Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
  3.3667 -  MOUSE (PS2 style), RTC/NVRAM.  Boot ROM is Flash.  PC-AT-sized
  3.3668 -  motherboard.  Requires power supply with 3.3V output.
  3.3669 -
  3.3670 -EB64+
  3.3671 -CONFIG_ALPHA_EB64P
  3.3672 -  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,
  3.3673 -  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
  3.3674 -  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
  3.3675 -  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
  3.3676 -  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.
  3.3677 -  Runs from standard PC power supply.
  3.3678 -
  3.3679 -EB66
  3.3680 -CONFIG_ALPHA_EB66
  3.3681 -  A Digital DS group board.  Uses 21066 or 21066A.  I/O sub-system is
  3.3682 -  identical to EB64+.  Baby PC-AT size.  Runs from standard PC power
  3.3683 -  supply.  The EB66 schematic was published as a marketing poster
  3.3684 -  advertising the 21066 as "the first microprocessor in the world with
  3.3685 -  embedded PCI".
  3.3686 -
  3.3687 -EB66+
  3.3688 -CONFIG_ALPHA_EB66P
  3.3689 -  Later variant of the EB66 board.
  3.3690 -
  3.3691 -Eiger
  3.3692 -CONFIG_ALPHA_EIGER
  3.3693 -  Apparently an obscure OEM single-board computer based on the
  3.3694 -  Typhoon/Tsunami chipset family. Information on it is scanty.
  3.3695 -
  3.3696 -Jensen
  3.3697 -CONFIG_ALPHA_JENSEN
  3.3698 -  DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
  3.3699 -  of the first-generation Alpha systems. A number of these systems
  3.3700 -  seem to be available on the second- hand market. The Jensen is a
  3.3701 -  floor-standing tower system which originally used a 150MHz 21064 It
  3.3702 -  used programmable logic to interface a 486 EISA I/O bridge to the
  3.3703 -  CPU.
  3.3704 -
  3.3705 -LX164
  3.3706 -CONFIG_ALPHA_LX164
  3.3707 -  A technical overview of this board is available at
  3.3708 -  <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
  3.3709 -
  3.3710 -Miata
  3.3711 -CONFIG_ALPHA_MIATA
  3.3712 -  The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
  3.3713 -  or 600au).  There is an Installation HOWTO for this hardware at
  3.3714 -  <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
  3.3715 -
  3.3716 -Mikasa
  3.3717 -CONFIG_ALPHA_MIKASA
  3.3718 -  AlphaServer 1000-based Alpha systems.
  3.3719 -
  3.3720 -Nautilus
  3.3721 -CONFIG_ALPHA_NAUTILUS
  3.3722 -  Alpha systems based on the AMD 751 & ALI 1543C chipsets.
  3.3723 -
  3.3724 -Noname
  3.3725 -CONFIG_ALPHA_NONAME
  3.3726 -  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
  3.3727 -  UDB).  This design was produced by Digital's Technical OEM (TOEM)
  3.3728 -  group. It uses the 21066 processor running at 166MHz or 233MHz. It
  3.3729 -  is a baby-AT size, and runs from a standard PC power supply. It has
  3.3730 -  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
  3.3731 -  2 versions, with either PS/2 or large DIN connectors for the
  3.3732 -  keyboard.
  3.3733 -
  3.3734 -Noritake
  3.3735 -CONFIG_ALPHA_NORITAKE
  3.3736 -  AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
  3.3737 -  systems.
  3.3738 -
  3.3739 -Rawhide
  3.3740 -CONFIG_ALPHA_RAWHIDE
  3.3741 -  AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
  3.3742 -  See HOWTO at
  3.3743 -  <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
  3.3744 -
  3.3745 -Ruffian
  3.3746 -CONFIG_ALPHA_RUFFIAN
  3.3747 -  Samsung APC164UX.  There is a page on known problems and workarounds
  3.3748 -  at <http://www.alphalinux.org/faq/FAQ-11.html>.
  3.3749 -
  3.3750 -Sable
  3.3751 -CONFIG_ALPHA_SABLE
  3.3752 -  Digital AlphaServer 2000 and 2100-based systems.
  3.3753 -
  3.3754 -Takara
  3.3755 -CONFIG_ALPHA_TAKARA
  3.3756 -  Alpha 11164-based OEM single-board computer.
  3.3757 -
  3.3758 -Wildfire
  3.3759 -CONFIG_ALPHA_WILDFIRE
  3.3760 -  AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
  3.3761 -
  3.3762 -EV5 CPU daughtercard (model 5/xxx)
  3.3763 -CONFIG_ALPHA_PRIMO
  3.3764 -  Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
  3.3765 -
  3.3766 -EV5 CPU(s) (model 5/xxx)
  3.3767 -CONFIG_ALPHA_GAMMA
  3.3768 -  Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
  3.3769 -
  3.3770 -EV67 (or later) CPU (speed > 600MHz)?
  3.3771 -CONFIG_ALPHA_EV67
  3.3772 -  Is this a machine based on the EV67 core?  If in doubt, select N here
  3.3773 -  and the machine will be treated as an EV6.
  3.3774 -
  3.3775 -Use SRM as bootloader
  3.3776 -CONFIG_ALPHA_SRM
  3.3777 -  There are two different types of booting firmware on Alphas: SRM,
  3.3778 -  which is command line driven, and ARC, which uses menus and arrow
  3.3779 -  keys. Details about the Linux/Alpha booting process are contained in
  3.3780 -  the Linux/Alpha FAQ, accessible on the WWW from
  3.3781 -  <http://www.alphalinux.org/>.
  3.3782 -
  3.3783 -  The usual way to load Linux on an Alpha machine is to use MILO
  3.3784 -  (a bootloader that lets you pass command line parameters to the
  3.3785 -  kernel just like lilo does for the x86 architecture) which can be
  3.3786 -  loaded either from ARC or can be installed directly as a permanent
  3.3787 -  firmware replacement from floppy (which requires changing a certain
  3.3788 -  jumper on the motherboard). If you want to do either of these, say N
  3.3789 -  here. If MILO doesn't work on your system (true for Jensen
  3.3790 -  motherboards), you can bypass it altogether and boot Linux directly
  3.3791 -  from an SRM console; say Y here in order to do that. Note that you
  3.3792 -  won't be able to boot from an IDE disk using old versions of SRM.
  3.3793 -
  3.3794 -  If unsure, say N.
  3.3795 -
  3.3796 -Legacy kernel start address
  3.3797 -CONFIG_ALPHA_LEGACY_START_ADDRESS
  3.3798 -  The 2.4 kernel changed the kernel start address from 0x310000
  3.3799 -  to 0x810000 to make room for the Wildfire's larger SRM console.
  3.3800 -
  3.3801 -  If you're using aboot 0.7 or later, the bootloader will examine the
  3.3802 -  ELF headers to determine where to transfer control. Unfortunately,
  3.3803 -  most older bootloaders -- APB or MILO -- hardcoded the kernel start
  3.3804 -  address rather than examining the ELF headers, and the result is a
  3.3805 -  hard lockup.
  3.3806 -
  3.3807 -  Say Y if you have a broken bootloader.  Say N if you do not, or if
  3.3808 -  you wish to run on Wildfire.
  3.3809 -
  3.3810 -Large VMALLOC support
  3.3811 -CONFIG_ALPHA_LARGE_VMALLOC
  3.3812 -  Process creation and other aspects of virtual memory management can
  3.3813 -  be streamlined if we restrict the kernel to one PGD for all vmalloc
  3.3814 -  allocations.  This equates to about 8GB.
  3.3815 -
  3.3816 -  Under normal circumstances, this is so far and above what is needed
  3.3817 -  as to be laughable.  However, there are certain applications (such
  3.3818 -  as benchmark-grade in-kernel web serving) that can make use of as
  3.3819 -  much vmalloc space as is available.
  3.3820 -
  3.3821 -  Say N unless you know you need gobs and gobs of vmalloc space.
  3.3822 -
  3.3823 -Non-standard serial port support
  3.3824 -CONFIG_SERIAL_NONSTANDARD
  3.3825 -  Say Y here if you have any non-standard serial boards -- boards
  3.3826 -  which aren't supported using the standard "dumb" serial driver.
  3.3827 -  This includes intelligent serial boards such as Cyclades,
  3.3828 -  Digiboards, etc. These are usually used for systems that need many
  3.3829 -  serial ports because they serve many terminals or dial-in
  3.3830 -  connections.
  3.3831 -
  3.3832 -  Note that the answer to this question won't directly affect the
  3.3833 -  kernel: saying N will just cause the configurator to skip all
  3.3834 -  the questions about non-standard serial boards.
  3.3835 -
  3.3836 -  Most people can say N here.
  3.3837 -
  3.3838 -Extended dumb serial driver options
  3.3839 -CONFIG_SERIAL_EXTENDED
  3.3840 -  If you wish to use any non-standard features of the standard "dumb"
  3.3841 -  driver, say Y here. This includes HUB6 support, shared serial
  3.3842 -  interrupts, special multiport support, support for more than the
  3.3843 -  four COM 1/2/3/4 boards, etc.
  3.3844 -
  3.3845 -  Note that the answer to this question won't directly affect the
  3.3846 -  kernel: saying N will just cause the configurator to skip all
  3.3847 -  the questions about serial driver options. If unsure, say N.
  3.3848 -
  3.3849 -Support more than 4 serial ports
  3.3850 -CONFIG_SERIAL_MANY_PORTS
  3.3851 -  Say Y here if you have dumb serial boards other than the four
  3.3852 -  standard COM 1/2/3/4 ports. This may happen if you have an AST
  3.3853 -  FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
  3.3854 -  from <http://www.tldp.org/docs.html#howto>), or other custom
  3.3855 -  serial port hardware which acts similar to standard serial port
  3.3856 -  hardware. If you only use the standard COM 1/2/3/4 ports, you can
  3.3857 -  say N here to save some memory. You can also say Y if you have an
  3.3858 -  "intelligent" multiport card such as Cyclades, Digiboards, etc.
  3.3859 -
  3.3860 -Support for sharing serial interrupts
  3.3861 -CONFIG_SERIAL_SHARE_IRQ
  3.3862 -  Some serial boards have hardware support which allows multiple dumb
  3.3863 -  serial ports on the same board to share a single IRQ. To enable
  3.3864 -  support for this in the serial driver, say Y here.
  3.3865 -
  3.3866 -Auto-detect IRQ on standard ports (unsafe)
  3.3867 -CONFIG_SERIAL_DETECT_IRQ
  3.3868 -  Say Y here if you want the kernel to try to guess which IRQ
  3.3869 -  to use for your serial port.
  3.3870 -
  3.3871 -  This is considered unsafe; it is far better to configure the IRQ in
  3.3872 -  a boot script using the setserial command.
  3.3873 -
  3.3874 -  If unsure, say N.
  3.3875 -
  3.3876 -Support special multiport boards
  3.3877 -CONFIG_SERIAL_MULTIPORT
  3.3878 -  Some multiport serial ports have special ports which are used to
  3.3879 -  signal when there are any serial ports on the board which need
  3.3880 -  servicing. Say Y here to enable the serial driver to take advantage
  3.3881 -  of those special I/O ports.
  3.3882 -
  3.3883 -SGI IP22 Zilog85C30 serial support
  3.3884 -CONFIG_IP22_SERIAL
  3.3885 -  If you want to use your IP22's built-in serial ports under Linux,
  3.3886 -  answer Y.
  3.3887 -
  3.3888 -SGI Newport Console support
  3.3889 -CONFIG_SGI_NEWPORT_CONSOLE
  3.3890 -  Say Y here if you want the console on the Newport aka XL graphics
  3.3891 -  card of your Indy.  Most people say Y here.
  3.3892 -
  3.3893 -SGI DS1286 RTC support
  3.3894 -CONFIG_SGI_DS1286
  3.3895 -  If you say Y here and create a character special file /dev/rtc with
  3.3896 -  major number 10 and minor number 135 using mknod ("man mknod"), you
  3.3897 -  will get access to the real time clock built into your computer.
  3.3898 -  Every SGI has such a clock built in. It reports status information
  3.3899 -  via the file /proc/rtc and its behaviour is set by various ioctls on
  3.3900 -  /dev/rtc.
  3.3901 -
  3.3902 -Indy/I2 Hardware Watchdog
  3.3903 -CONFIG_INDYDOG
  3.3904 -  Hardwaredriver for the Indy's/I2's watchdog. This is a
  3.3905 -  watchdog timer that will reboot the machine after a 60 second 
  3.3906 -  timer expired and no process has written to /dev/watchdog during
  3.3907 -  that time.
  3.3908 -
  3.3909 -Support the Bell Technologies HUB6 card
  3.3910 -CONFIG_HUB6
  3.3911 -  Say Y here to enable support in the dumb serial driver to support
  3.3912 -  the HUB6 card.
  3.3913 -
  3.3914 -PCMCIA serial device support
  3.3915 -CONFIG_PCMCIA_SERIAL_CS
  3.3916 -  Say Y here to enable support for 16-bit PCMCIA serial devices,
  3.3917 -  including serial port cards, modems, and the modem functions of
  3.3918 -  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
  3.3919 -  credit-card size devices often used with laptops.)
  3.3920 -
  3.3921 -  This driver is also available as a module ( = code which can be
  3.3922 -  inserted in and removed from the running kernel whenever you want).
  3.3923 -  The module will be called serial_cs.o.  If you want to compile it as
  3.3924 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.3925 -  If unsure, say N.
  3.3926 -
  3.3927 -CONFIG_SYNCLINK_CS
  3.3928 -  Enable support for the SyncLink PC Card serial adapter, running
  3.3929 -  asynchronous and HDLC communications up to 512Kbps. The port is
  3.3930 -  selectable for RS-232, V.35, RS-449, RS-530, and X.21
  3.3931 -
  3.3932 -  This driver may be built as a module ( = code which can be
  3.3933 -  inserted in and removed from the running kernel whenever you want).
  3.3934 -  The module will be called synclinkmp.o.  If you want to do that, say M
  3.3935 -  here.
  3.3936 -
  3.3937 -ACP Modem (Mwave) support
  3.3938 -CONFIG_MWAVE
  3.3939 -  The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
  3.3940 -  kernel driver and a user level application. Together these components
  3.3941 -  support direct attachment to public switched telephone networks (PSTNs)
  3.3942 -  and support selected world wide countries.
  3.3943 -
  3.3944 -  This version of the ACP Modem driver supports the IBM Thinkpad 600E,
  3.3945 -  600, and 770 that include on board ACP modem hardware.
  3.3946 -
  3.3947 -  The modem also supports the standard communications port interface
  3.3948 -  (ttySx) and is compatible with the Hayes AT Command Set.
  3.3949 -
  3.3950 -  The user level application needed to use this driver can be found at
  3.3951 -  the IBM Linux Technology Center (LTC) web site:
  3.3952 -  <http://www.ibm.com/linux/ltc/>.
  3.3953 -
  3.3954 -  If you own one of the above IBM Thinkpads which has the Mwave chipset
  3.3955 -  in it, say Y.
  3.3956 -
  3.3957 -  This driver is also available as a module ( = code which can be
  3.3958 -  inserted in and removed from the running kernel whenever you want).
  3.3959 -  The module will be called mwave.o. If you want to compile it as
  3.3960 -  a module, say M here and read Documentation/modules.txt.
  3.3961 -
  3.3962 -/dev/agpgart (AGP Support)
  3.3963 -CONFIG_AGP
  3.3964 -  AGP (Accelerated Graphics Port) is a bus system mainly used to
  3.3965 -  connect graphics cards to the rest of the system.
  3.3966 -
  3.3967 -  If you have an AGP system and you say Y here, it will be possible to
  3.3968 -  use the AGP features of your 3D rendering video card. This code acts
  3.3969 -  as a sort of "AGP driver" for the motherboard's chipset.
  3.3970 -
  3.3971 -  If you need more texture memory than you can get with the AGP GART
  3.3972 -  (theoretically up to 256 MB, but in practice usually 64 or 128 MB
  3.3973 -  due to kernel allocation issues), you could use PCI accesses
  3.3974 -  and have up to a couple gigs of texture space.
  3.3975 -
  3.3976 -  Note that this is the only means to have XFree4/GLX use
  3.3977 -  write-combining with MTRR support on the AGP bus. Without it, OpenGL
  3.3978 -  direct rendering will be a lot slower but still faster than PIO.
  3.3979 -
  3.3980 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.3981 -  use GLX or DRI.  If unsure, say N.
  3.3982 -
  3.3983 -  This driver is available as a module.  If you want to compile it as
  3.3984 -  a module, say M here and read <file:Documentation/modules.txt>.  The
  3.3985 -  module will be called agpgart.o.
  3.3986 -
  3.3987 -Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
  3.3988 -CONFIG_AGP_INTEL
  3.3989 -  This option gives you AGP support for the GLX component of the
  3.3990 -  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
  3.3991 -
  3.3992 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.3993 -  use GLX or DRI.  If unsure, say N.
  3.3994 -
  3.3995 -Intel 460GX support
  3.3996 -CONFIG_AGP_I460
  3.3997 -  This option gives you AGP support for the Intel 460GX chipset.  This
  3.3998 -  chipset, the first to support Intel Itanium processors, is new and
  3.3999 -  this option is correspondingly a little experimental.
  3.4000 -
  3.4001 -  If you don't have a 460GX based machine (such as BigSur) with an AGP 
  3.4002 -  slot then this option isn't going to do you much good.  If you're
  3.4003 -  dying to do Direct Rendering on IA-64, this is what you're looking for.
  3.4004 -
  3.4005 -Intel I810/I815 DC100/I810e support
  3.4006 -CONFIG_AGP_I810
  3.4007 -  This option gives you AGP support for the Xserver on the Intel 810
  3.4008 -  815 and 830m chipset boards for their on-board integrated graphics. This
  3.4009 -  is required to do any useful video modes with these boards.
  3.4010 -
  3.4011 -VIA chipset support
  3.4012 -CONFIG_AGP_VIA
  3.4013 -  This option gives you AGP support for the GLX component of the
  3.4014 -  XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
  3.4015 -
  3.4016 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4017 -  use GLX or DRI.  If unsure, say N.
  3.4018 -
  3.4019 -AMD Irongate, 761, and 762 support
  3.4020 -CONFIG_AGP_AMD
  3.4021 -  This option gives you AGP support for the GLX component of the
  3.4022 -  XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
  3.4023 -
  3.4024 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4025 -  use GLX or DRI.  If unsure, say N.
  3.4026 -
  3.4027 -CONFIG_AGP_AMD_K8
  3.4028 -  This option gives you AGP support for the GLX component of
  3.4029 -  XFree86 on an AMD Opteron/Athlon64 using the on-CPU GART.
  3.4030 -
  3.4031 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4032 -  use GLX or DRI.  If unsure, say N.
  3.4033 -
  3.4034 -Generic SiS support
  3.4035 -CONFIG_AGP_SIS
  3.4036 -  This option gives you AGP support for the GLX component of
  3.4037 -  XFree86 4.x on Silicon Integrated Systems [SiS] chipsets.
  3.4038 -
  3.4039 -  Note that 5591/5592 AGP chipsets are NOT specifically supported;
  3.4040 -  However, the driver works well on these, too.
  3.4041 -
  3.4042 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4043 -  use GLX or DRI.  If unsure, say N.
  3.4044 -
  3.4045 -Serverworks LE/HE support
  3.4046 -CONFIG_AGP_SWORKS
  3.4047 -  Say Y here to support the Serverworks AGP card.  See
  3.4048 -  <http://www.serverworks.com/> for product descriptions and images.
  3.4049 -
  3.4050 -NVIDIA chipset support
  3.4051 -CONFIG_AGP_NVIDIA
  3.4052 -  This option gives you AGP support for the GLX component of the
  3.4053 -  XFree86 4.x on NVIDIA nForce/nForce2 chipsets.
  3.4054 -
  3.4055 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4056 -  use GLX or DRI.  If unsure, say N.
  3.4057 -
  3.4058 -ALI chipset support
  3.4059 -CONFIG_AGP_ALI
  3.4060 -  This option gives you AGP support for the GLX component of the
  3.4061 -  XFree86 4.x on the following ALi chipsets.  The supported chipsets
  3.4062 -  include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
  3.4063 -  For the ALi-chipset question, ALi suggests you refer to
  3.4064 -  <http://www.ali.com.tw/eng/support/index.shtml>.
  3.4065 -
  3.4066 -  The M1541 chipset can do AGP 1x and 2x, but note that there is an
  3.4067 -  acknowledged incompatibility with Matrox G200 cards. Due to
  3.4068 -  timing issues, this chipset cannot do AGP 2x with the G200.
  3.4069 -  This is a hardware limitation. AGP 1x seems to be fine, though.
  3.4070 -
  3.4071 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4072 -  use GLX or DRI.  If unsure, say N.
  3.4073 -
  3.4074 -CONFIG_AGP_HP_ZX1
  3.4075 -  This option gives you AGP GART support for the HP ZX1 chipset
  3.4076 -  for IA64 processors.
  3.4077 -
  3.4078 -CONFIG_AGP_ATI
  3.4079 -  This option gives you AGP support for the GLX component of
  3.4080 -  XFree86 4.x on the ATI RadeonIGP family of chipsets.
  3.4081 -
  3.4082 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  3.4083 -  use GLX or DRI.  If unsure, say N.
  3.4084 -
  3.4085 -Support for ISA-bus hardware
  3.4086 -CONFIG_ISA
  3.4087 -  Find out whether you have ISA slots on your motherboard.  ISA is the
  3.4088 -  name of a bus system, i.e. the way the CPU talks to the other stuff
  3.4089 -  inside your box.  Other bus systems are PCI, EISA, MicroChannel
  3.4090 -  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
  3.4091 -  newer boards don't support it.  If you have ISA, say Y, otherwise N.
  3.4092 -
  3.4093 -Support for PCI bus hardware
  3.4094 -CONFIG_PCI
  3.4095 -  Find out whether you have a PCI motherboard. PCI is the name of a
  3.4096 -  bus system, i.e. the way the CPU talks to the other stuff inside
  3.4097 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  3.4098 -  VESA. If you have PCI, say Y, otherwise N.
  3.4099 -
  3.4100 -  The PCI-HOWTO, available from
  3.4101 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  3.4102 -  information about which PCI hardware does work under Linux and which
  3.4103 -  doesn't.
  3.4104 -
  3.4105 -PCI support
  3.4106 -CONFIG_PCI_INTEGRATOR
  3.4107 -  Find out whether you have a PCI motherboard. PCI is the name of a
  3.4108 -  bus system, i.e. the way the CPU talks to the other stuff inside
  3.4109 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  3.4110 -  VESA. If you have PCI, say Y, otherwise N.
  3.4111 -
  3.4112 -  The PCI-HOWTO, available from
  3.4113 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  3.4114 -  information about which PCI hardware does work under Linux and which
  3.4115 -  doesn't.
  3.4116 -
  3.4117 -QSpan PCI
  3.4118 -CONFIG_PCI_QSPAN
  3.4119 -  Find out whether you have a PCI motherboard. PCI is the name of a
  3.4120 -  bus system, i.e. the way the CPU talks to the other stuff inside
  3.4121 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  3.4122 -  VESA. If you have PCI, say Y, otherwise N.
  3.4123 -
  3.4124 -  The PCI-HOWTO, available from
  3.4125 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  3.4126 -  information about which PCI hardware does work under Linux and which
  3.4127 -  doesn't.
  3.4128 -
  3.4129 -# Choice: pci_access
  3.4130 -PCI access mode
  3.4131 -CONFIG_PCI_GOBIOS
  3.4132 -  On PCI systems, the BIOS can be used to detect the PCI devices and
  3.4133 -  determine their configuration. However, some old PCI motherboards
  3.4134 -  have BIOS bugs and may crash if this is done. Also, some embedded
  3.4135 -  PCI-based systems don't have any BIOS at all. Linux can also try to
  3.4136 -  detect the PCI hardware directly without using the BIOS.
  3.4137 -
  3.4138 -  With this option, you can specify how Linux should detect the PCI
  3.4139 -  devices. If you choose "BIOS", the BIOS will be used, if you choose
  3.4140 -  "Direct", the BIOS won't be used, and if you choose "Any", the
  3.4141 -  kernel will try the direct access method and falls back to the BIOS
  3.4142 -  if that doesn't work. If unsure, go with the default, which is
  3.4143 -  "Any".
  3.4144 -
  3.4145 -PCI device name database
  3.4146 -CONFIG_PCI_NAMES
  3.4147 -  By default, the kernel contains a database of all known PCI device
  3.4148 -  names to make the information in /proc/pci, /proc/ioports and
  3.4149 -  similar files comprehensible to the user. This database increases
  3.4150 -  size of the kernel image by about 80KB, but it gets freed after the
  3.4151 -  system boots up, so it doesn't take up kernel memory. Anyway, if you
  3.4152 -  are building an installation floppy or kernel for an embedded system
  3.4153 -  where kernel image size really matters, you can disable this feature
  3.4154 -  and you'll get device ID numbers instead of names.
  3.4155 -
  3.4156 -  When in doubt, say Y.
  3.4157 -
  3.4158 -Generic PCI hotplug support
  3.4159 -CONFIG_HOTPLUG_PCI
  3.4160 -  Say Y here if you have a motherboard with a PCI Hotplug controller.
  3.4161 -  This allows you to add and remove PCI cards while the machine is
  3.4162 -  powered up and running.  The file system pcihpfs must be mounted
  3.4163 -  in order to interact with any PCI Hotplug controllers.
  3.4164 -
  3.4165 -  This code is also available as a module ( = code which can be
  3.4166 -  inserted in and removed from the running kernel whenever you want).
  3.4167 -  The module will be called pci_hotplug.o. If you want to compile it
  3.4168 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.4169 -
  3.4170 -  When in doubt, say N.
  3.4171 -
  3.4172 -Compaq PCI Hotplug driver
  3.4173 -CONFIG_HOTPLUG_PCI_COMPAQ
  3.4174 -  Say Y here if you have a motherboard with a Compaq PCI Hotplug
  3.4175 -  controller.
  3.4176 -
  3.4177 -  This code is also available as a module ( = code which can be
  3.4178 -  inserted in and removed from the running kernel whenever you want).
  3.4179 -  The module will be called cpqphp.o. If you want to compile it
  3.4180 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.4181 -
  3.4182 -  When in doubt, say N.
  3.4183 -
  3.4184 -PCI Compaq Hotplug controller NVRAM support
  3.4185 -CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
  3.4186 -  Say Y here if you have a Compaq server that has a PCI Hotplug
  3.4187 -  controller.  This will allow the PCI Hotplug driver to store the PCI
  3.4188 -  system configuration options in NVRAM.
  3.4189 -
  3.4190 -  When in doubt, say N.
  3.4191 -
  3.4192 -ACPI PCI Hotplug driver
  3.4193 -CONFIG_HOTPLUG_PCI_ACPI
  3.4194 -  Say Y here if you have a system that supports PCI Hotplug using
  3.4195 -  ACPI.
  3.4196 -
  3.4197 -  This code is also available as a module ( = code which can be
  3.4198 -  inserted in and removed from the running kernel whenever you want).
  3.4199 -  The module will be called acpiphp.o. If you want to compile it
  3.4200 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.4201 -
  3.4202 -MCA support
  3.4203 -CONFIG_MCA
  3.4204 -  MicroChannel Architecture is found in some IBM PS/2 machines and
  3.4205 -  laptops.  It is a bus system similar to PCI or ISA. See
  3.4206 -  <file:Documentation/mca.txt> (and especially the web page given
  3.4207 -  there) before attempting to build an MCA bus kernel.
  3.4208 -
  3.4209 -Support for EISA-bus hardware
  3.4210 -CONFIG_EISA
  3.4211 -  The Extended Industry Standard Architecture (EISA) bus was
  3.4212 -  developed as an open alternative to the IBM MicroChannel bus.
  3.4213 -
  3.4214 -  The EISA bus provided some of the features of the IBM MicroChannel
  3.4215 -  bus while maintaining backward compatibility with cards made for
  3.4216 -  the older ISA bus.  The EISA bus saw limited use between 1988 and
  3.4217 -  1995 when it was made obsolete by the PCI bus.
  3.4218 -
  3.4219 -  Say Y here if you are building a kernel for an EISA-based machine.
  3.4220 -
  3.4221 -  Otherwise, say N.
  3.4222 -
  3.4223 -SGI Visual Workstation support
  3.4224 -CONFIG_VISWS
  3.4225 -  The SGI Visual Workstation series is an IA32-based workstation
  3.4226 -  based on SGI systems chips with some legacy PC hardware attached.
  3.4227 -  Say Y here to create a kernel to run on the SGI 320 or 540.
  3.4228 -  A kernel compiled for the Visual Workstation will not run on other
  3.4229 -  PC boards and vice versa.
  3.4230 -  See <file:Documentation/sgi-visws.txt> for more.
  3.4231 -
  3.4232 -SGI Visual Workstation framebuffer support
  3.4233 -CONFIG_FB_SGIVW
  3.4234 -  SGI Visual Workstation support for framebuffer graphics.
  3.4235 -
  3.4236 -I2O support
  3.4237 -CONFIG_I2O
  3.4238 -  The Intelligent Input/Output (I2O) architecture allows hardware
  3.4239 -  drivers to be split into two parts: an operating system specific
  3.4240 -  module called the OSM and an hardware specific module called the
  3.4241 -  HDM. The OSM can talk to a whole range of HDM's, and ideally the
  3.4242 -  HDM's are not OS dependent. This allows for the same HDM driver to
  3.4243 -  be used under different operating systems if the relevant OSM is in
  3.4244 -  place. In order for this to work, you need to have an I2O interface
  3.4245 -  adapter card in your computer. This card contains a special I/O
  3.4246 -  processor (IOP), thus allowing high speeds since the CPU does not
  3.4247 -  have to deal with I/O.
  3.4248 -
  3.4249 -  If you say Y here, you will get a choice of interface adapter
  3.4250 -  drivers and OSM's with the following questions.
  3.4251 -
  3.4252 -  This support is also available as a module ( = code which can be
  3.4253 -  inserted in and removed from the running kernel whenever you want).
  3.4254 -  If you want to compile it as a module, say M here and read
  3.4255 -  <file:Documentation/modules.txt>.  You will get modules called
  3.4256 -  i2o_core.o and i2o_config.o.
  3.4257 -
  3.4258 -  If unsure, say N.
  3.4259 -
  3.4260 -I2O PCI support
  3.4261 -CONFIG_I2O_PCI
  3.4262 -  Say Y for support of PCI bus I2O interface adapters. Currently this
  3.4263 -  is the only variety supported, so you should say Y.
  3.4264 -
  3.4265 -  This support is also available as a module called i2o_pci.o ( = code
  3.4266 -  which can be inserted in and removed from the running kernel
  3.4267 -  whenever you want). If you want to compile it as a module, say M
  3.4268 -  here and read <file:Documentation/modules.txt>.
  3.4269 -
  3.4270 -I2O Block OSM
  3.4271 -CONFIG_I2O_BLOCK
  3.4272 -  Include support for the I2O Block OSM. The Block OSM presents disk
  3.4273 -  and other structured block devices to the operating system.
  3.4274 -
  3.4275 -  This support is also available as a module called i2o_block.o ( =
  3.4276 -  code which can be inserted in and removed from the running kernel
  3.4277 -  whenever you want). If you want to compile it as a module, say M
  3.4278 -  here and read <file:Documentation/modules.txt>.
  3.4279 -
  3.4280 -I2O LAN OSM
  3.4281 -CONFIG_I2O_LAN
  3.4282 -  Include support for the LAN OSM. You will also need to include
  3.4283 -  support for token ring or FDDI if you wish to use token ring or FDDI
  3.4284 -  I2O cards with this driver.
  3.4285 -
  3.4286 -  This support is also available as a module called i2o_lan.o ( = code
  3.4287 -  which can be inserted in and removed from the running kernel
  3.4288 -  whenever you want). If you want to compile it as a module, say M
  3.4289 -  here and read <file:Documentation/modules.txt>.
  3.4290 -
  3.4291 -I2O SCSI OSM
  3.4292 -CONFIG_I2O_SCSI
  3.4293 -  Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  3.4294 -  I2O controller. You can use both the SCSI and Block OSM together if
  3.4295 -  you wish.
  3.4296 -
  3.4297 -  This support is also available as a module called i2o_scsi.o ( =
  3.4298 -  code which can be inserted in and removed from the running kernel
  3.4299 -  whenever you want). If you want to compile it as a module, say M
  3.4300 -  here and read <file:Documentation/modules.txt>.
  3.4301 -
  3.4302 -I2O /proc support
  3.4303 -CONFIG_I2O_PROC
  3.4304 -  If you say Y here and to "/proc file system support", you will be
  3.4305 -  able to read I2O related information from the virtual directory
  3.4306 -  /proc/i2o.
  3.4307 -
  3.4308 -  This support is also available as a module called i2o_proc.o ( =
  3.4309 -  code which can be inserted in and removed from the running kernel
  3.4310 -  whenever you want). If you want to compile it as a module, say M
  3.4311 -  here and read <file:Documentation/modules.txt>.
  3.4312 -
  3.4313 -Plug and Play support
  3.4314 -CONFIG_PNP
  3.4315 -  Plug and Play (PnP) is a standard for peripherals which allows those
  3.4316 -  peripherals to be configured by software, e.g. assign IRQ's or other
  3.4317 -  parameters. No jumpers on the cards are needed, instead the values
  3.4318 -  are provided to the cards from the BIOS, from the operating system,
  3.4319 -  or using a user-space utility.
  3.4320 -
  3.4321 -  Say Y here if you would like Linux to configure your Plug and Play
  3.4322 -  devices. You should then also say Y to "ISA Plug and Play support",
  3.4323 -  below. Alternatively, you can say N here and configure your PnP
  3.4324 -  devices using the user space utilities contained in the isapnptools
  3.4325 -  package.
  3.4326 -
  3.4327 -  This support is also available as a module ( = code which can be
  3.4328 -  inserted in and removed from the running kernel whenever you want).
  3.4329 -  If you want to compile it as a module, say M here and read
  3.4330 -  <file:Documentation/modules.txt>.
  3.4331 -
  3.4332 -ISA Plug and Play support
  3.4333 -CONFIG_ISAPNP
  3.4334 -  Say Y here if you would like support for ISA Plug and Play devices.
  3.4335 -  Some information is in <file:Documentation/isapnp.txt>.
  3.4336 -
  3.4337 -  This support is also available as a module called isapnp.o ( =
  3.4338 -  code which can be inserted in and removed from the running kernel
  3.4339 -  whenever you want). If you want to compile it as a module, say M
  3.4340 -  here and read <file:Documentation/modules.txt>.
  3.4341 -
  3.4342 -  If unsure, say Y.
  3.4343 -
  3.4344 -PNPBIOS support
  3.4345 -CONFIG_PNPBIOS
  3.4346 -  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
  3.4347 -  Specification Version 1.0A May 5, 1994" to autodetect built-in
  3.4348 -  mainboard resources (e.g. parallel port resources).
  3.4349 -
  3.4350 -  Other features (e.g. change resources, ESCD, event notification,
  3.4351 -  Docking station information, ISAPNP services) are not used.
  3.4352 -
  3.4353 -  Note: ACPI is expected to supersede PNPBIOS some day, currently it
  3.4354 -  co-exists nicely.
  3.4355 -
  3.4356 -  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
  3.4357 -  or have a look at /proc/bus/pnp.
  3.4358 -
  3.4359 -  If unsure, say Y.
  3.4360 -
  3.4361 -Support for hot-pluggable devices
  3.4362 -CONFIG_HOTPLUG
  3.4363 -  Say Y here if you want to plug devices into your computer while
  3.4364 -  the system is running, and be able to use them quickly.  In many
  3.4365 -  cases, the devices can likewise be unplugged at any time too.
  3.4366 -
  3.4367 -  One well known example of this is PCMCIA- or PC-cards, credit-card
  3.4368 -  size devices such as network cards, modems or hard drives which are
  3.4369 -  plugged into slots found on all modern laptop computers.  Another
  3.4370 -  example, used on modern desktops as well as laptops, is USB.
  3.4371 -
  3.4372 -  Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
  3.4373 -  software (at <http://linux-hotplug.sourceforge.net/>) and install it.
  3.4374 -  Then your kernel will automatically call out to a user mode "policy
  3.4375 -  agent" (/sbin/hotplug) to load modules and set up software needed
  3.4376 -  to use devices as you hotplug them.
  3.4377 -
  3.4378 -PCMCIA/CardBus support
  3.4379 -CONFIG_PCMCIA
  3.4380 -  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  3.4381 -  computer.  These are credit-card size devices such as network cards,
  3.4382 -  modems or hard drives often used with laptops computers.  There are
  3.4383 -  actually two varieties of these cards: the older 16 bit PCMCIA cards
  3.4384 -  and the newer 32 bit CardBus cards.  If you want to use CardBus
  3.4385 -  cards, you need to say Y here and also to "CardBus support" below.
  3.4386 -
  3.4387 -  To use your PC-cards, you will need supporting software from David
  3.4388 -  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  3.4389 -  for location).  Please also read the PCMCIA-HOWTO, available from
  3.4390 -  <http://www.tldp.org/docs.html#howto>.
  3.4391 -
  3.4392 -  This driver is also available as a module ( = code which can be
  3.4393 -  inserted in and removed from the running kernel whenever you want).
  3.4394 -  When compiled this way, there will be modules called pcmcia_core.o
  3.4395 -  and ds.o.  If you want to compile it as a module, say M here and
  3.4396 -  read <file:Documentation/modules.txt>.
  3.4397 -
  3.4398 -CardBus card and (Yenta) bridge support
  3.4399 -CONFIG_CARDBUS
  3.4400 -  CardBus is a bus mastering architecture for PC-cards, which allows
  3.4401 -  for 32 bit PC-cards (the original PCMCIA standard specifies only
  3.4402 -  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  3.4403 -
  3.4404 -  This option enables support for CardBus PC Cards, as well as support
  3.4405 -  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
  3.4406 -  CardBus compatible.  A "bridge" is the hardware inside your computer
  3.4407 -  that PCMCIA cards are plugged into.
  3.4408 -
  3.4409 -  To use your PC-cards, you will need supporting software from David
  3.4410 -  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  3.4411 -  for location).
  3.4412 -
  3.4413 -  If unsure, say Y.
  3.4414 -
  3.4415 -i82092 compatible bridge support
  3.4416 -CONFIG_I82092
  3.4417 -  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  3.4418 -  found in some older laptops and more commonly in evaluation boards for the
  3.4419 -  chip.
  3.4420 -
  3.4421 -i82365 compatible host bridge support
  3.4422 -CONFIG_I82365
  3.4423 -  Say Y here to include support for ISA-bus PCMCIA host bridges that
  3.4424 -  are register compatible with the Intel i82365.  These are found on
  3.4425 -  older laptops and ISA-bus card readers for desktop systems.  A
  3.4426 -  "bridge" is the hardware inside your computer that PCMCIA cards are
  3.4427 -  plugged into. If unsure, say N.
  3.4428 -
  3.4429 -Databook TCIC host bridge support
  3.4430 -CONFIG_TCIC
  3.4431 -  Say Y here to include support for the Databook TCIC family of PCMCIA
  3.4432 -  host bridges. These are only found on a handful of old systems.
  3.4433 -  "Bridge" is the name used for the hardware inside your computer that
  3.4434 -  PCMCIA cards are plugged into. If unsure, say N.
  3.4435 -
  3.4436 -CONFIG_PCMCIA_SIBYTE
  3.4437 -  Say Y here to include support for the SiByte SOC's built-in PCMCIA
  3.4438 -  interface.  Only ATA cards and CompactFlash are currently
  3.4439 -  supported.
  3.4440 -
  3.4441 -System V IPC
  3.4442 -CONFIG_SYSVIPC
  3.4443 -  Inter Process Communication is a suite of library functions and
  3.4444 -  system calls which let processes (running programs) synchronize and
  3.4445 -  exchange information. It is generally considered to be a good thing,
  3.4446 -  and some programs won't run unless you say Y here. In particular, if
  3.4447 -  you want to run the DOS emulator dosemu under Linux (read the
  3.4448 -  DOSEMU-HOWTO, available from
  3.4449 -  <http://www.tldp.org/docs.html#howto>), you'll need to say Y
  3.4450 -  here.
  3.4451 -
  3.4452 -  You can find documentation about IPC with "info ipc" and also in
  3.4453 -  section 6.4 of the Linux Programmer's Guide, available from
  3.4454 -  <http://www.tldp.org/docs.html#guide>.
  3.4455 -
  3.4456 -BSD Process Accounting
  3.4457 -CONFIG_BSD_PROCESS_ACCT
  3.4458 -  If you say Y here, a user level program will be able to instruct the
  3.4459 -  kernel (via a special system call) to write process accounting
  3.4460 -  information to a file: whenever a process exits, information about
  3.4461 -  that process will be appended to the file by the kernel.  The
  3.4462 -  information includes things such as creation time, owning user,
  3.4463 -  command name, memory usage, controlling terminal etc. (the complete
  3.4464 -  list is in the struct acct in <file:include/linux/acct.h>).  It is
  3.4465 -  up to the user level program to do useful things with this
  3.4466 -  information.  This is generally a good idea, so say Y.
  3.4467 -
  3.4468 -Sysctl support
  3.4469 -CONFIG_SYSCTL
  3.4470 -  The sysctl interface provides a means of dynamically changing
  3.4471 -  certain kernel parameters and variables on the fly without requiring
  3.4472 -  a recompile of the kernel or reboot of the system.  The primary
  3.4473 -  interface consists of a system call, but if you say Y to "/proc
  3.4474 -  file system support", a tree of modifiable sysctl entries will be
  3.4475 -  generated beneath the /proc/sys directory. They are explained in the
  3.4476 -  files in <file:Documentation/sysctl/>.  Note that enabling this
  3.4477 -  option will enlarge the kernel by at least 8 KB.
  3.4478 -
  3.4479 -  As it is generally a good thing, you should say Y here unless
  3.4480 -  building a kernel for install/rescue disks or your system is very
  3.4481 -  limited in memory.
  3.4482 -
  3.4483 -# Choice: kcore
  3.4484 -Kernel core (/proc/kcore) format
  3.4485 -CONFIG_KCORE_ELF
  3.4486 -  If you enabled support for /proc file system then the file
  3.4487 -  /proc/kcore will contain the kernel core image. This can be used
  3.4488 -  in gdb:
  3.4489 -
  3.4490 -  $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
  3.4491 -
  3.4492 -  You have two choices here: ELF and A.OUT. Selecting ELF will make
  3.4493 -  /proc/kcore appear in ELF core format as defined by the Executable
  3.4494 -  and Linking Format specification. Selecting A.OUT will choose the
  3.4495 -  old "a.out" format which may be necessary for some old versions
  3.4496 -  of binutils or on some architectures.
  3.4497 -
  3.4498 -  This is especially useful if you have compiled the kernel with the
  3.4499 -  "-g" option to preserve debugging information. It is mainly used
  3.4500 -  for examining kernel data structures on the live kernel so if you
  3.4501 -  don't understand what this means or are not a kernel hacker, just
  3.4502 -  leave it at its default value ELF.
  3.4503 -
  3.4504 -Select a.out format for /proc/kcore
  3.4505 -CONFIG_KCORE_AOUT
  3.4506 -  Not necessary unless you're using a very out-of-date binutils
  3.4507 -  version.  You probably want KCORE_ELF.
  3.4508 -
  3.4509 -Kernel support for ELF binaries
  3.4510 -CONFIG_BINFMT_ELF
  3.4511 -  ELF (Executable and Linkable Format) is a format for libraries and
  3.4512 -  executables used across different architectures and operating
  3.4513 -  systems. Saying Y here will enable your kernel to run ELF binaries
  3.4514 -  and enlarge it by about 13 KB. ELF support under Linux has now all
  3.4515 -  but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  3.4516 -  because it is portable (this does *not* mean that you will be able
  3.4517 -  to run executables from different architectures or operating systems
  3.4518 -  however) and makes building run-time libraries very easy. Many new
  3.4519 -  executables are distributed solely in ELF format. You definitely
  3.4520 -  want to say Y here.
  3.4521 -
  3.4522 -  Information about ELF is contained in the ELF HOWTO available from
  3.4523 -  <http://www.tldp.org/docs.html#howto>.
  3.4524 -
  3.4525 -  If you find that after upgrading from Linux kernel 1.2 and saying Y
  3.4526 -  here, you still can't run any ELF binaries (they just crash), then
  3.4527 -  you'll have to install the newest ELF runtime libraries, including
  3.4528 -  ld.so (check the file <file:Documentation/Changes> for location and
  3.4529 -  latest version).
  3.4530 -
  3.4531 -  If you want to compile this as a module ( = code which can be
  3.4532 -  inserted in and removed from the running kernel whenever you want),
  3.4533 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.4534 -  will be called binfmt_elf.o. Saying M or N here is dangerous because
  3.4535 -  some crucial programs on your system might be in ELF format.
  3.4536 -
  3.4537 -Kernel support for a.out binaries
  3.4538 -CONFIG_BINFMT_AOUT
  3.4539 -  A.out (Assembler.OUTput) is a set of formats for libraries and
  3.4540 -  executables used in the earliest versions of UNIX. Linux used the
  3.4541 -  a.out formats QMAGIC and ZMAGIC until they were replaced with the
  3.4542 -  ELF format.
  3.4543 -
  3.4544 -  As more and more programs are converted to ELF, the use for a.out
  3.4545 -  will gradually diminish. If you disable this option it will reduce
  3.4546 -  your kernel by one page. This is not much and by itself does not
  3.4547 -  warrant removing support. However its removal is a good idea if you
  3.4548 -  wish to ensure that absolutely none of your programs will use this
  3.4549 -  older executable format. If you don't know what to answer at this
  3.4550 -  point then answer Y. If someone told you "You need a kernel with
  3.4551 -  QMAGIC support" then you'll have to say Y here. You may answer M to
  3.4552 -  compile a.out support as a module and later load the module when you
  3.4553 -  want to use a program or library in a.out format. The module will be
  3.4554 -  called binfmt_aout.o. Saying M or N here is dangerous though,
  3.4555 -  because some crucial programs on your system might still be in A.OUT
  3.4556 -  format.
  3.4557 -
  3.4558 -OSF/1 v4 readv/writev compatibility
  3.4559 -CONFIG_OSF4_COMPAT
  3.4560 -  Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  3.4561 -  with v4 shared libraries freely available from Compaq. If you're
  3.4562 -  going to use shared libraries from Tru64 version 5.0 or later, say N.
  3.4563 -
  3.4564 -Kernel support for Linux/Intel ELF binaries
  3.4565 -CONFIG_BINFMT_EM86
  3.4566 -  Say Y here if you want to be able to execute Linux/Intel ELF
  3.4567 -  binaries just like native Alpha binaries on your Alpha machine. For
  3.4568 -  this to work, you need to have the emulator /usr/bin/em86 in place.
  3.4569 -
  3.4570 -  You can get the same functionality by saying N here and saying Y to
  3.4571 -  "Kernel support for MISC binaries".
  3.4572 -
  3.4573 -  You may answer M to compile the emulation support as a module and
  3.4574 -  later load the module when you want to use a Linux/Intel binary. The
  3.4575 -  module will be called binfmt_em86.o. If unsure, say Y.
  3.4576 -
  3.4577 -Kernel support for SOM binaries
  3.4578 -CONFIG_BINFMT_SOM
  3.4579 -  SOM is a binary executable format inherited from HP/UX.  Say Y here
  3.4580 -  to be able to load and execute SOM binaries directly.
  3.4581 -
  3.4582 -Kernel support for MISC binaries
  3.4583 -CONFIG_BINFMT_MISC
  3.4584 -  If you say Y here, it will be possible to plug wrapper-driven binary
  3.4585 -  formats into the kernel. You will like this especially when you use
  3.4586 -  programs that need an interpreter to run like Java, Python or
  3.4587 -  Emacs-Lisp. It's also useful if you often run DOS executables under
  3.4588 -  the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  3.4589 -  <http://www.tldp.org/docs.html#howto>). Once you have
  3.4590 -  registered such a binary class with the kernel, you can start one of
  3.4591 -  those programs simply by typing in its name at a shell prompt; Linux
  3.4592 -  will automatically feed it to the correct interpreter.
  3.4593 -
  3.4594 -  You can do other nice things, too. Read the file
  3.4595 -  <file:Documentation/binfmt_misc.txt> to learn how to use this
  3.4596 -  feature, and <file:Documentation/java.txt> for information about how
  3.4597 -  to include Java support.
  3.4598 -
  3.4599 -  You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
  3.4600 -  use this part of the kernel.
  3.4601 -
  3.4602 -  You may say M here for module support and later load the module when
  3.4603 -  you have use for it; the module is called binfmt_misc.o. If you
  3.4604 -  don't know what to answer at this point, say Y.
  3.4605 -
  3.4606 -Kernel support for JAVA binaries
  3.4607 -CONFIG_BINFMT_JAVA
  3.4608 -  If you say Y here, the kernel will load and execute Java J-code
  3.4609 -  binaries directly.  Note: this option is obsolete and scheduled for
  3.4610 -  removal, use CONFIG_BINFMT_MISC instead.
  3.4611 -
  3.4612 -Solaris binary emulation
  3.4613 -CONFIG_SOLARIS_EMUL
  3.4614 -  This is experimental code which will enable you to run (many)
  3.4615 -  Solaris binaries on your SPARC Linux machine.
  3.4616 -
  3.4617 -  This code is also available as a module ( = code which can be
  3.4618 -  inserted in and removed from the running kernel whenever you want).
  3.4619 -  The module will be called solaris.o. If you want to compile it as a
  3.4620 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4621 -
  3.4622 -SUN SME environment monitoring
  3.4623 -CONFIG_ENVCTRL
  3.4624 -  Kernel support for temperature and fan monitoring on Sun SME
  3.4625 -  machines.
  3.4626 -
  3.4627 -  This code is also available as a module ( = code which can be
  3.4628 -  inserted in and removed from the running kernel whenever you want).
  3.4629 -  The module will be called envctrl.o. If you want to compile it as a
  3.4630 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4631 -
  3.4632 -# Choice: x86type
  3.4633 -Processor family
  3.4634 -CONFIG_M386
  3.4635 -  This is the processor type of your CPU. This information is used for
  3.4636 -  optimizing purposes. In order to compile a kernel that can run on
  3.4637 -  all x86 CPU types (albeit not optimally fast), you can specify
  3.4638 -  "386" here.
  3.4639 -
  3.4640 -  The kernel will not necessarily run on earlier architectures than
  3.4641 -  the one you have chosen, e.g. a Pentium optimized kernel will run on
  3.4642 -  a PPro, but not necessarily on a i486.
  3.4643 -
  3.4644 -  Here are the settings recommended for greatest speed:
  3.4645 -   - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
  3.4646 -     486DLC/DLC2, UMC 486SX-S and NexGen Nx586.  Only "386" kernels
  3.4647 -     will run on a 386 class machine.
  3.4648 -   - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
  3.4649 -     SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
  3.4650 -   - "586" for generic Pentium CPUs, possibly lacking the TSC
  3.4651 -     (time stamp counter) register.
  3.4652 -   - "Pentium-Classic" for the Intel Pentium.
  3.4653 -   - "Pentium-MMX" for the Intel Pentium MMX.
  3.4654 -   - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
  3.4655 -   - "Pentium-III" for the Intel Pentium III
  3.4656 -     and Celerons based on the Coppermine core.
  3.4657 -   - "Pentium-4" for the Intel Pentium 4.
  3.4658 -   - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
  3.4659 -   - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
  3.4660 -   - "Elan" for the AMD Elan family (Elan SC400/SC410).
  3.4661 -   - "Crusoe" for the Transmeta Crusoe series.
  3.4662 -   - "Winchip-C6" for original IDT Winchip.
  3.4663 -   - "Winchip-2" for IDT Winchip 2.
  3.4664 -   - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
  3.4665 -   - "CyrixIII" for VIA Cyrix III or VIA C3.
  3.4666 -   - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
  3.4667 -
  3.4668 -  If you don't know what to do, choose "386".
  3.4669 -
  3.4670 -486
  3.4671 -CONFIG_M486
  3.4672 -  Select this for a x486 processor, ether Intel or one of the
  3.4673 -  compatible processors from AMD, Cyrix, IBM, or Intel.  Includes DX,
  3.4674 -  DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
  3.4675 -  U5S.
  3.4676 -
  3.4677 -586/K5/5x86/6x86/6x86MX
  3.4678 -CONFIG_M586
  3.4679 -  Select this for an x586 or x686 processor such as the AMD K5, the
  3.4680 -  Intel 5x86 or 6x86, or the Intel 6x86MX.  This choice does not
  3.4681 -  assume the RDTSC instruction.
  3.4682 -
  3.4683 -Pentium Classic
  3.4684 -CONFIG_M586TSC
  3.4685 -  Select this for a Pentium Classic processor with the RDTSC (Read
  3.4686 -  Time Stamp Counter) instruction for benchmarking.
  3.4687 -
  3.4688 -VIA C3-2 (Nehemiah)
  3.4689 -CONFIG_MVIAC3_2
  3.4690 -  Select this for a VIA C3 "Nehemiah". Selecting this enables usage of SSE
  3.4691 -  and tells gcc to treat the CPU as a 686.
  3.4692 -
  3.4693 -  Note, this kernel will not boot on older (pre model 9) C3s.
  3.4694 -
  3.4695 -32-bit PDC
  3.4696 -CONFIG_PDC_NARROW
  3.4697 -  Saying Y here will allow developers with a C180, C200, C240, C360,
  3.4698 -  J200, J210, and/or a J2240 to test 64-bit kernels by providing a
  3.4699 -  wrapper for the 32-bit PDC calls.  Since the machines which require
  3.4700 -  this option do not support over 4G of RAM, this option is targeted
  3.4701 -  for developers of these machines wishing to test changes on both
  3.4702 -  32-bit and 64-bit configurations.
  3.4703 -
  3.4704 -  If unsure, say N.
  3.4705 -
  3.4706 -VGA text console
  3.4707 -CONFIG_VGA_CONSOLE
  3.4708 -  Saying Y here will allow you to use Linux in text mode through a
  3.4709 -  display that complies with the generic VGA standard. Virtually
  3.4710 -  everyone wants that.
  3.4711 -
  3.4712 -  The program SVGATextMode can be used to utilize SVGA video cards to
  3.4713 -  their full potential in text mode. Download it from
  3.4714 -  <ftp://ibiblio.org/pub/Linux/utils/console/>.
  3.4715 -
  3.4716 -  Say Y.
  3.4717 -
  3.4718 -Distribute interrupts on all CPUs by default
  3.4719 -CONFIG_IRQ_ALL_CPUS
  3.4720 -  This option gives the kernel permission to distribute IRQs across
  3.4721 -  multiple CPUs.  Saying N here will route all IRQs to the first
  3.4722 -  CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
  3.4723 -  Power3 boxes should say N for now.
  3.4724 -
  3.4725 -Video mode selection support
  3.4726 -CONFIG_VIDEO_SELECT
  3.4727 -  This enables support for text mode selection on kernel startup. If
  3.4728 -  you want to take advantage of some high-resolution text mode your
  3.4729 -  card's BIOS offers, but the traditional Linux utilities like
  3.4730 -  SVGATextMode don't, you can say Y here and set the mode using the
  3.4731 -  "vga=" option from your boot loader (lilo or loadlin) or set
  3.4732 -  "vga=ask" which brings up a video mode menu on kernel startup. (Try
  3.4733 -  "man bootparam" or see the documentation of your boot loader about
  3.4734 -  how to pass options to the kernel.)
  3.4735 -
  3.4736 -  Read the file <file:Documentation/svga.txt> for more information
  3.4737 -  about the Video mode selection support. If unsure, say N.
  3.4738 -
  3.4739 -Support for frame buffer devices
  3.4740 -CONFIG_FB
  3.4741 -  The frame buffer device provides an abstraction for the graphics
  3.4742 -  hardware. It represents the frame buffer of some video hardware and
  3.4743 -  allows application software to access the graphics hardware through
  3.4744 -  a well-defined interface, so the software doesn't need to know
  3.4745 -  anything about the low-level (hardware register) stuff.
  3.4746 -
  3.4747 -  Frame buffer devices work identically across the different
  3.4748 -  architectures supported by Linux and make the implementation of
  3.4749 -  application programs easier and more portable; at this point, an X
  3.4750 -  server exists which uses the frame buffer device exclusively.
  3.4751 -  On several non-X86 architectures, the frame buffer device is the
  3.4752 -  only way to use the graphics hardware.
  3.4753 -
  3.4754 -  The device is accessed through special device nodes, usually located
  3.4755 -  in the /dev directory, i.e. /dev/fb*.
  3.4756 -
  3.4757 -  You need an utility program called fbset to make full use of frame
  3.4758 -  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  3.4759 -  and the Framebuffer-HOWTO at
  3.4760 -  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  3.4761 -  information.
  3.4762 -
  3.4763 -  Say Y here and to the driver for your graphics board below if you
  3.4764 -  are compiling a kernel for a non-x86 architecture.
  3.4765 -
  3.4766 -  If you are compiling for the x86 architecture, you can say Y if you
  3.4767 -  want to play with it, but it is not essential. Please note that
  3.4768 -  running graphical applications that directly touch the hardware
  3.4769 -  (e.g. an accelerated X server) and that are not frame buffer
  3.4770 -  device-aware may cause unexpected results. If unsure, say N.
  3.4771 -
  3.4772 -Acorn VIDC support
  3.4773 -CONFIG_FB_ACORN
  3.4774 -  This is the frame buffer device driver for the Acorn VIDC graphics
  3.4775 -  hardware found in Acorn RISC PCs and other ARM-based machines.  If
  3.4776 -  unsure, say N.
  3.4777 -
  3.4778 -Permedia2 support
  3.4779 -CONFIG_FB_PM2
  3.4780 -  This is the frame buffer device driver for the Permedia2 AGP frame
  3.4781 -  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
  3.4782 -  product page at
  3.4783 -  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
  3.4784 -
  3.4785 -Enable FIFO disconnect feature
  3.4786 -CONFIG_FB_PM2_FIFO_DISCONNECT
  3.4787 -  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
  3.4788 -
  3.4789 -Generic Permedia2 PCI board support
  3.4790 -CONFIG_FB_PM2_PCI
  3.4791 -  Say Y to enable support for Permedia2 AGP frame buffer card from
  3.4792 -  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
  3.4793 -
  3.4794 -Phase5 CVisionPPC/BVisionPPC support
  3.4795 -CONFIG_FB_PM2_CVPPC
  3.4796 -  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
  3.4797 -  framebuffer cards.  Phase 5 is no longer with us, alas.
  3.4798 -
  3.4799 -Amiga native chipset support
  3.4800 -CONFIG_FB_AMIGA
  3.4801 -  This is the frame buffer device driver for the builtin graphics
  3.4802 -  chipset found in Amigas.
  3.4803 -
  3.4804 -  The driver is also available as a module ( = code which can be
  3.4805 -  inserted and removed from the running kernel whenever you want). The
  3.4806 -  module will be called amifb.o. If you want to compile it as a
  3.4807 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4808 -
  3.4809 -Amiga OCS chipset support
  3.4810 -CONFIG_FB_AMIGA_OCS
  3.4811 -  This enables support for the original Agnus and Denise video chips,
  3.4812 -  found in the Amiga 1000 and most A500's and A2000's. If you intend
  3.4813 -  to run Linux on any of these systems, say Y; otherwise say N.
  3.4814 -
  3.4815 -Amiga ECS chipset support
  3.4816 -CONFIG_FB_AMIGA_ECS
  3.4817 -  This enables support for the Enhanced Chip Set, found in later
  3.4818 -  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
  3.4819 -  you intend to run Linux on any of these systems, say Y; otherwise
  3.4820 -  say N.
  3.4821 -
  3.4822 -Amiga AGA chipset support
  3.4823 -CONFIG_FB_AMIGA_AGA
  3.4824 -  This enables support for the Advanced Graphics Architecture (also
  3.4825 -  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
  3.4826 -  and CD32. If you intend to run Linux on any of these systems, say Y;
  3.4827 -  otherwise say N.
  3.4828 -
  3.4829 -Amiga CyberVision support
  3.4830 -CONFIG_FB_CYBER
  3.4831 -  This enables support for the Cybervision 64 graphics card from
  3.4832 -  Phase5. Please note that its use is not all that intuitive (i.e. if
  3.4833 -  you have any questions, be sure to ask!). Say N unless you have a
  3.4834 -  Cybervision 64 or plan to get one before you next recompile the
  3.4835 -  kernel. Please note that this driver DOES NOT support the
  3.4836 -  Cybervision 64 3D card, as they use incompatible video chips.
  3.4837 -
  3.4838 -CyberPro 20x0 support
  3.4839 -CONFIG_FB_CYBER2000
  3.4840 -  This enables support for the Integraphics CyberPro 20x0 and 5000
  3.4841 -  VGA chips used in the Rebel.com Netwinder and other machines.
  3.4842 -  Say Y if you have a NetWinder or a graphics card containing this
  3.4843 -  device, otherwise say N.
  3.4844 -
  3.4845 -Amiga CyberVision3D support
  3.4846 -CONFIG_FB_VIRGE
  3.4847 -  This enables support for the Cybervision 64/3D graphics card from
  3.4848 -  Phase5. Please note that its use is not all that intuitive (i.e. if
  3.4849 -  you have any questions, be sure to ask!). Say N unless you have a
  3.4850 -  Cybervision 64/3D or plan to get one before you next recompile the
  3.4851 -  kernel. Please note that this driver DOES NOT support the older
  3.4852 -  Cybervision 64 card, as they use incompatible video chips.
  3.4853 -
  3.4854 -Amiga RetinaZ3 support
  3.4855 -CONFIG_FB_RETINAZ3
  3.4856 -  This enables support for the Retina Z3 graphics card. Say N unless
  3.4857 -  you have a Retina Z3 or plan to get one before you next recompile
  3.4858 -  the kernel.
  3.4859 -
  3.4860 -Cirrus Logic generic driver
  3.4861 -CONFIG_FB_CLGEN
  3.4862 -  This enables support for Cirrus Logic GD542x/543x based boards on
  3.4863 -  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
  3.4864 -
  3.4865 -  If you have a PCI-based system, this enables support for these
  3.4866 -  chips: GD-543x, GD-544x, GD-5480.
  3.4867 -
  3.4868 -  Please read the file <file:Documentation/fb/clgenfb.txt>.
  3.4869 -
  3.4870 -  Say N unless you have such a graphics board or plan to get one
  3.4871 -  before you next recompile the kernel.
  3.4872 -
  3.4873 -Apollo support
  3.4874 -CONFIG_APOLLO
  3.4875 -  Say Y here if you want to run Linux on an MC680x0-based Apollo
  3.4876 -  Domain workstation such as the DN3500.
  3.4877 -
  3.4878 -Apollo 3c505 "EtherLink Plus" support
  3.4879 -CONFIG_APOLLO_ELPLUS
  3.4880 -  Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
  3.4881 -  If you don't have one made for Apollos, you can use one from a PC,
  3.4882 -  except that your Apollo won't be able to boot from it (because the
  3.4883 -  code in the ROM will be for a PC).
  3.4884 -
  3.4885 -Atari native chipset support
  3.4886 -CONFIG_FB_ATARI
  3.4887 -  This is the frame buffer device driver for the builtin graphics
  3.4888 -  chipset found in Ataris.
  3.4889 -
  3.4890 -Amiga FrameMaster II/Rainbow II support
  3.4891 -CONFIG_FB_FM2
  3.4892 -  This is the frame buffer device driver for the Amiga FrameMaster
  3.4893 -  card from BSC (exhibited 1992 but not shipped as a CBM product).
  3.4894 -
  3.4895 -Open Firmware frame buffer device support
  3.4896 -CONFIG_FB_OF
  3.4897 -  Say Y if you want support with Open Firmware for your graphics
  3.4898 -  board.
  3.4899 -
  3.4900 -S3 Trio frame buffer device support
  3.4901 -CONFIG_FB_S3TRIO
  3.4902 -  If you have a S3 Trio say Y. Say N for S3 Virge.
  3.4903 -
  3.4904 -3Dfx Banshee/Voodoo3 display support
  3.4905 -CONFIG_FB_3DFX
  3.4906 -  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  3.4907 -  chips. Say Y if you have such a graphics board.
  3.4908 -
  3.4909 -  The driver is also available as a module ( = code which can be
  3.4910 -  inserted and removed from the running kernel whenever you want). The
  3.4911 -  module will be called tdfxfb.o. If you want to compile it as a
  3.4912 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4913 -
  3.4914 -nVidia Riva support
  3.4915 -CONFIG_FB_RIVA
  3.4916 -  This driver supports graphics boards with the nVidia Riva/Geforce
  3.4917 -  chips.
  3.4918 -  Say Y if you have such a graphics board.
  3.4919 -
  3.4920 -  The driver is also available as a module ( = code which can be
  3.4921 -  inserted and removed from the running kernel whenever you want). The
  3.4922 -  module will be called rivafb.o. If you want to compile it as a
  3.4923 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4924 -
  3.4925 -Trident Blade/Image support
  3.4926 -CONFIG_FB_TRIDENT
  3.4927 -  This driver is supposed to support graphics boards with the
  3.4928 -  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  3.4929 -  but also on some motherboards.Read <file:Documentation/fb/tridentfb.txt>
  3.4930 -
  3.4931 -  Say Y if you have such a graphics board.
  3.4932 -
  3.4933 -  The driver is also available as a module ( = code which can be
  3.4934 -  inserted and removed from the running kernel whenever you want). The
  3.4935 -  module will be called tridentfb.o. If you want to compile it as a
  3.4936 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4937 -
  3.4938 -ATI Mach64 display support
  3.4939 -CONFIG_FB_ATY
  3.4940 -  This driver supports graphics boards with the ATI Mach64 chips.
  3.4941 -  Say Y if you have such a graphics board.
  3.4942 -
  3.4943 -  The driver is also available as a module ( = code which can be
  3.4944 -  inserted and removed from the running kernel whenever you want). The
  3.4945 -  module will be called atyfb.o. If you want to compile it as a
  3.4946 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4947 -
  3.4948 -ATI Rage128 display support
  3.4949 -CONFIG_FB_ATY128
  3.4950 -  This driver supports graphics boards with the ATI Rage128 chips.
  3.4951 -  Say Y if you have such a graphics board and read
  3.4952 -  <file:Documentation/fb/aty128fb.txt>.
  3.4953 -
  3.4954 -  The driver is also available as a module ( = code which can be
  3.4955 -  inserted and removed from the running kernel whenever you want). The
  3.4956 -  module will be called aty128fb.o. If you want to compile it as a
  3.4957 -  module, say M here and read <file:Documentation/modules.txt>.
  3.4958 -
  3.4959 -Maxine (Personal DECstation) onboard framebuffer support
  3.4960 -CONFIG_FB_MAXINE
  3.4961 -  Support for the onboard framebuffer (1024x768x8) in the Personal
  3.4962 -  DECstation series (Personal DECstation 5000/20, /25, /33, /50,
  3.4963 -  Codename "Maxine").
  3.4964 -
  3.4965 -PMAG-BA TURBOchannel framebuffer support
  3.4966 -CONFIG_FB_PMAG_BA
  3.4967 -  Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
  3.4968 -  used mainly in the MIPS-based DECstation series.
  3.4969 -
  3.4970 -PMAGB-B TURBOchannel framebuffer support
  3.4971 -CONFIG_FB_PMAGB_B
  3.4972 -  Support for the PMAGB-B TURBOchannel framebuffer card used mainly
  3.4973 -  in the MIPS-based DECstation series. The card is currently only 
  3.4974 -  supported in 1280x1024x8 mode.  
  3.4975 -
  3.4976 -FutureTV PCI card
  3.4977 -CONFIG_ARCH_FTVPCI
  3.4978 -  Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
  3.4979 -  Electronics) StrongARM PCI card.
  3.4980 -
  3.4981 -ANAKIN Vehicle Telematics Platform
  3.4982 -CONFIG_ARCH_ANAKIN
  3.4983 -  The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
  3.4984 -  64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
  3.4985 -
  3.4986 -  On board peripherals:
  3.4987 -        * Front display: 400x234 16 bit TFT touchscreen
  3.4988 -        * External independent second screen interface
  3.4989 -        * CAN controller SJA1000
  3.4990 -        * USB host controller
  3.4991 -        * 6 channel video codec with hardware overlay
  3.4992 -        * Smartcard reader
  3.4993 -        * IrDa
  3.4994 -
  3.4995 -  Modules interfaced over the Multi Media Extension slots:
  3.4996 -        * A communication card
  3.4997 -                Wavecom GPRS modem
  3.4998 -                uBlock GPS
  3.4999 -                Bosch DAB module
  3.5000 -        * An audio card ( 4 * 40W, AC97 Codec, I2S)
  3.5001 -
  3.5002 -Altera Excalibur XA10 Dev Board
  3.5003 -ARCH_CAMELOT
  3.5004 -  This enables support for Altera's Excalibur XA10 development board.
  3.5005 -  If you would like to build your kernel to run on one of these boards
  3.5006 -  then you must say 'Y' here. Otherwise say 'N'
  3.5007 -
  3.5008 -Link-Up Systems LCD support
  3.5009 -CONFIG_FB_L7200
  3.5010 -  This driver supports the L7200 Color LCD.
  3.5011 -  Say Y if you want graphics support.
  3.5012 -
  3.5013 -NeoMagic display support (EXPERIMENTAL)
  3.5014 -CONFIG_FB_NEOMAGIC
  3.5015 -  This driver supports notebooks with NeoMagic PCI chips.
  3.5016 -  Say Y if you have such a graphics card. 
  3.5017 -
  3.5018 -  The driver is also available as a module ( = code which can be
  3.5019 -  inserted and removed from the running kernel whenever you want). The
  3.5020 -  module will be called neofb.o. If you want to compile it as a
  3.5021 -  module, say M here and read Documentation/modules.txt.
  3.5022 -
  3.5023 -PowerMac "control" frame buffer device support
  3.5024 -CONFIG_FB_CONTROL
  3.5025 -  This driver supports a frame buffer for the graphics adapter in the
  3.5026 -  Power Macintosh 7300 and others.
  3.5027 -
  3.5028 -PowerMac "platinum" frame buffer device support
  3.5029 -CONFIG_FB_PLATINUM
  3.5030 -  This driver supports a frame buffer for the "platinum" graphics
  3.5031 -  adapter in some Power Macintoshes.
  3.5032 -
  3.5033 -PowerMac "valkyrie" frame buffer device support
  3.5034 -CONFIG_FB_VALKYRIE
  3.5035 -  This driver supports a frame buffer for the "valkyrie" graphics
  3.5036 -  adapter in some Power Macintoshes.
  3.5037 -
  3.5038 -Chips 65550 display support
  3.5039 -CONFIG_FB_CT65550
  3.5040 -  This is the frame buffer device driver for the Chips & Technologies
  3.5041 -  65550 graphics chip in PowerBooks.
  3.5042 -
  3.5043 -TGA frame buffer support
  3.5044 -CONFIG_FB_TGA
  3.5045 -  This is the frame buffer device driver for generic TGA graphic
  3.5046 -  cards. Say Y if you have one of those.
  3.5047 -
  3.5048 -VESA VGA graphics console
  3.5049 -CONFIG_FB_VESA
  3.5050 -  This is the frame buffer device driver for generic VESA 2.0
  3.5051 -  compliant graphic cards. The older VESA 1.2 cards are not supported.
  3.5052 -  You will get a boot time penguin logo at no additional cost. Please
  3.5053 -  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
  3.5054 -
  3.5055 -VGA 16-color planar support
  3.5056 -CONFIG_FBCON_VGA_PLANES
  3.5057 -  This low level frame buffer console driver enable the kernel to use
  3.5058 -  the 16-color planar modes of the old VGA cards where the bits of
  3.5059 -  each pixel are separated into 4 planes.
  3.5060 -
  3.5061 -  Only answer Y here if you have a (very old) VGA card that isn't VESA
  3.5062 -  2 compatible.
  3.5063 -
  3.5064 -VGA 16-color graphics console
  3.5065 -CONFIG_FB_VGA16
  3.5066 -  This is the frame buffer device driver for VGA 16 color graphic
  3.5067 -  cards. Say Y if you have such a card.
  3.5068 -
  3.5069 -  This code is also available as a module. If you want to compile it
  3.5070 -  as a module ( = code which can be inserted in and removed from the
  3.5071 -  running kernel whenever you want), say M here and read
  3.5072 -  <file:Documentation/modules.txt>.  The module will be called
  3.5073 -  vga16fb.o.
  3.5074 -
  3.5075 -Generic STI frame buffer device support
  3.5076 -CONFIG_FB_STI
  3.5077 -  STI refers to the HP "Standard Text Interface" which is a set of
  3.5078 -  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
  3.5079 -  Enabling this option will implement the linux framebuffer device and
  3.5080 -  an fbcon color text console using calls to the STI BIOS routines.
  3.5081 -  The HP framebuffer device is sometimes planar, using a strange memory
  3.5082 -  layout, and changing the plane mask to create colored pixels
  3.5083 -  can require a call to the STI routines, so /dev/fb may not actually 
  3.5084 -  be useful.  However, on some systems packed pixel formats are supported.  
  3.5085 -  It is sufficient for basic text console functions, including fonts.
  3.5086 -
  3.5087 -  You should probably enable this option, unless you are having
  3.5088 -  trouble getting video when booting the kernel (make sure it isn't
  3.5089 -  just that you are running the console on the serial port, though).
  3.5090 -  Really old HP boxes may not have STI, and must use the PDC BIOS
  3.5091 -  console or the IODC BIOS.
  3.5092 -
  3.5093 -Select other compiled-in fonts
  3.5094 -CONFIG_FBCON_FONTS
  3.5095 -  Say Y here if you would like to use fonts other than the default
  3.5096 -  your frame buffer console usually use.
  3.5097 -
  3.5098 -  Note that the answer to this question won't directly affect the
  3.5099 -  kernel: saying N will just cause the configurator to skip all
  3.5100 -  the questions about foreign fonts.
  3.5101 -
  3.5102 -  If unsure, say N (the default choices are safe).
  3.5103 -
  3.5104 -VGA 8x16 font
  3.5105 -CONFIG_FONT_8x16
  3.5106 -  This is the "high resolution" font for the VGA frame buffer (the one
  3.5107 -  provided by the VGA text console 80x25 mode.
  3.5108 -
  3.5109 -  If unsure, say Y.
  3.5110 -
  3.5111 -Support only 8 pixels wide fonts
  3.5112 -CONFIG_FBCON_FONTWIDTH8_ONLY
  3.5113 -  Answer Y here will make the kernel provide only the 8x8 fonts (these
  3.5114 -  are the less readable).
  3.5115 -
  3.5116 -  If unsure, say N.
  3.5117 -
  3.5118 -Sparc console 8x16 font
  3.5119 -CONFIG_FONT_SUN8x16
  3.5120 -  This is the high resolution console font for Sun machines. Say Y.
  3.5121 -
  3.5122 -Sparc console 12x22 font (not supported by all drivers)
  3.5123 -CONFIG_FONT_SUN12x22
  3.5124 -  This is the high resolution console font for Sun machines with very
  3.5125 -  big letters (like the letters used in the SPARC PROM). If the
  3.5126 -  standard font is unreadable for you, say Y, otherwise say N.
  3.5127 -
  3.5128 -VGA 8x8 font
  3.5129 -CONFIG_FONT_8x8
  3.5130 -  This is the "high resolution" font for the VGA frame buffer (the one
  3.5131 -  provided by the text console 80x50 (and higher) modes).
  3.5132 -
  3.5133 -  Note that this is a poor quality font. The VGA 8x16 font is quite a
  3.5134 -  lot more readable.
  3.5135 -
  3.5136 -  Given the resolution provided by the frame buffer device, answer N
  3.5137 -  here is safe.
  3.5138 -
  3.5139 -Mac console 6x11 font (not supported by all drivers)
  3.5140 -CONFIG_FONT_6x11
  3.5141 -  Small console font with Macintosh-style high-half glyphs.  Some Mac
  3.5142 -  framebuffer drivers don't support this one at all.
  3.5143 -
  3.5144 -Pearl (old m68k) console 8x8 font
  3.5145 -CONFIG_FONT_PEARL_8x8
  3.5146 -  Small console font with PC-style control-character and high-half
  3.5147 -  glyphs.
  3.5148 -
  3.5149 -Acorn console 8x8 font
  3.5150 -CONFIG_FONT_ACORN_8x8
  3.5151 -  Small console font with PC-style control characters and high-half
  3.5152 -  glyphs.
  3.5153 -
  3.5154 -Backward compatibility mode for Xpmac
  3.5155 -CONFIG_FB_COMPAT_XPMAC
  3.5156 -  If you use the Xpmac X server (common with mklinux), you'll need to
  3.5157 -  say Y here to use X. You should consider changing to XFree86 which
  3.5158 -  includes a server that supports the frame buffer device directly
  3.5159 -  (XF68_FBDev).
  3.5160 -
  3.5161 -Hercules (HGA) mono graphics support
  3.5162 -CONFIG_FB_HGA
  3.5163 -  Say Y here if you have a Hercules mono graphics card.
  3.5164 -
  3.5165 -  This driver is also available as a module ( = code which can be
  3.5166 -  inserted and removed from the running kernel whenever you want).
  3.5167 -  The module will be called hgafb.o. If you want to compile it as
  3.5168 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.5169 -
  3.5170 -  As this card technology is 15 years old, most people will answer N
  3.5171 -  here.
  3.5172 -
  3.5173 -Epson 1355 framebuffer support
  3.5174 -CONFIG_FB_E1355
  3.5175 -  Build in support for the SED1355 Epson Research Embedded RAMDAC
  3.5176 -  LCD/CRT Controller (since redesignated as the S1D13505) as a
  3.5177 -  framebuffer.  Product specs at
  3.5178 -  <http://www.erd.epson.com/vdc/html/products.htm>.
  3.5179 -
  3.5180 -Dreamcast Frame Buffer support
  3.5181 -CONFIG_FB_DC
  3.5182 -  Say Y here to enable support for the framebuffer on the Sega
  3.5183 -  Dreamcast.  This driver is also available as a module, dcfb.o.
  3.5184 -
  3.5185 -Register Base Address
  3.5186 -CONFIG_E1355_REG_BASE
  3.5187 -  Epson SED1355/S1D13505 LCD/CRT controller register base address.
  3.5188 -  See the manuals at
  3.5189 -  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  3.5190 -  discussion.
  3.5191 -
  3.5192 -Framebuffer Base Address
  3.5193 -CONFIG_E1355_FB_BASE
  3.5194 -  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
  3.5195 -  the manuals at
  3.5196 -  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  3.5197 -  discussion.
  3.5198 -
  3.5199 -NEC PowerVR 2 display support
  3.5200 -CONFIG_FB_PVR2
  3.5201 -  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
  3.5202 -  run linux on your Dreamcast, you will have to say Y here.
  3.5203 -  This driver may or may not work on other PowerVR 2 cards, but is
  3.5204 -  totally untested.  Use at your own risk.  If unsure, say N.
  3.5205 -
  3.5206 -  This driver is also available as a module ( = code which can be
  3.5207 -  inserted and removed from the running kernel whenever you want).
  3.5208 -  The module will be called pvr2fb.o.  If you want to compile it as
  3.5209 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.5210 -
  3.5211 -  You can pass several parameters to the driver at boot time or at
  3.5212 -  module load time.  The parameters look like "video=pvr2:XXX", where
  3.5213 -  the meaning of XXX can be found at the end of the main source file
  3.5214 -  (<file:drivers/video/pvr2fb.c>). Please see the file
  3.5215 -  <file:Documentation/fb/pvr2fb.txt>.
  3.5216 -
  3.5217 -Debug pvr2fb
  3.5218 -CONFIG_FB_PVR2_DEBUG
  3.5219 -  Say Y here if you wish for the pvr2fb driver to print out debugging
  3.5220 -  messages. Most people will want to say N here. If unsure, you will
  3.5221 -  also want to say N.
  3.5222 -
  3.5223 -Matrox unified accelerated driver
  3.5224 -CONFIG_FB_MATROX
  3.5225 -  Say Y here if you have a Matrox Millennium, Millennium II, Mystique,
  3.5226 -  Mystique 220, Productiva G100, Mystique G200, Millennium G200,
  3.5227 -  Matrox G400, G450 or G550 card in your box. At this time, support for 
  3.5228 -  the G-series digital output is almost non-existant.
  3.5229 -
  3.5230 -  This driver is also available as a module ( = code which can be
  3.5231 -  inserted and removed from the running kernel whenever you want).
  3.5232 -  The module will be called matroxfb.o. If you want to compile it as
  3.5233 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.5234 -
  3.5235 -  You can pass several parameters to the driver at boot time or at
  3.5236 -  module load time. The parameters look like "video=matrox:XXX", and
  3.5237 -  are described in <file:Documentation/fb/matroxfb.txt>.
  3.5238 -
  3.5239 -Matrox Millennium I/II support
  3.5240 -CONFIG_FB_MATROX_MILLENIUM
  3.5241 -  Say Y here if you have a Matrox Millennium or Matrox Millennium II
  3.5242 -  video card. If you select "Advanced lowlevel driver options" below,
  3.5243 -  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
  3.5244 -  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
  3.5245 -  also use font widths different from 8.
  3.5246 -
  3.5247 -Matrox Mystique support
  3.5248 -CONFIG_FB_MATROX_MYSTIQUE
  3.5249 -  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
  3.5250 -  video card. If you select "Advanced lowlevel driver options" below,
  3.5251 -  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  3.5252 -  packed pixel and 32 bpp packed pixel. You can also use font widths
  3.5253 -  different from 8.
  3.5254 -
  3.5255 -CONFIG_FB_MATROX_G450
  3.5256 -  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
  3.5257 -  video card. If you select "Advanced lowlevel driver options", you
  3.5258 -  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
  3.5259 -  pixel and 32 bpp packed pixel. You can also use font widths
  3.5260 -  different from 8.
  3.5261 -
  3.5262 -  If you need support for G400 secondary head, you must first say Y to
  3.5263 -  "I2C support" and "I2C bit-banging support" in the character devices
  3.5264 -  section, and then to "Matrox I2C support" and "G400 second head
  3.5265 -  support" here in the framebuffer section. G450/G550 secondary head
  3.5266 -  and digital output are supported without additional modules.
  3.5267 -  
  3.5268 -  The driver starts in monitor mode. You must use the matroxset tool 
  3.5269 -  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
  3.5270 -  swap primary and secondary head outputs, or to change output mode.  
  3.5271 -  Secondary head driver always start in 640x480 resolution and you 
  3.5272 -  must use fbset to change it.
  3.5273 -
  3.5274 -  Do not forget that second head supports only 16 and 32 bpp
  3.5275 -  packed pixels, so it is a good idea to compile them into the kernel
  3.5276 -  too. You can use only some font widths, as the driver uses generic
  3.5277 -  painting procedures (the secondary head does not use acceleration
  3.5278 -  engine).
  3.5279 -  
  3.5280 -  G450/G550 hardware can display TV picture only from secondary CRTC,
  3.5281 -  and it performs no scaling, so picture must have 525 or 625 lines.
  3.5282 -
  3.5283 -CONFIG_FB_MATROX_G100A
  3.5284 -  Say Y here if you have a Matrox G100, G200 or G400 based
  3.5285 -  video card. If you select "Advanced lowlevel driver options", you
  3.5286 -  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
  3.5287 -  pixel and 32 bpp packed pixel. You can also use font widths
  3.5288 -  different from 8.
  3.5289 -
  3.5290 -  If you need support for G400 secondary head, you must first say Y to
  3.5291 -  "I2C support" and "I2C bit-banging support" in the character devices
  3.5292 -  section, and then to "Matrox I2C support" and "G400 second head
  3.5293 -  support" here in the framebuffer section.
  3.5294 -
  3.5295 -CONFIG_FB_MATROX_I2C
  3.5296 -  This drivers creates I2C buses which are needed for accessing the
  3.5297 -  DDC (I2C) bus present on all Matroxes, an I2C bus which
  3.5298 -  interconnects Matrox optional devices, like MGA-TVO on G200 and
  3.5299 -  G400, and the secondary head DDC bus, present on G400 only.
  3.5300 -
  3.5301 -  You can say Y or M here if you want to experiment with monitor
  3.5302 -  detection code. You must say Y or M here if you want to use either
  3.5303 -  second head of G400 or MGA-TVO on G200 or G400.
  3.5304 -
  3.5305 -  If you compile it as module, it will create a module named
  3.5306 -  i2c-matroxfb.o.
  3.5307 -
  3.5308 -Matrox G400 second head support
  3.5309 -CONFIG_FB_MATROX_MAVEN
  3.5310 -  WARNING !!! This support does not work with G450 !!!
  3.5311 -
  3.5312 -  Say Y or M here if you want to use a secondary head (meaning two
  3.5313 -  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
  3.5314 -  head is not compatible with accelerated XFree 3.3.x SVGA servers -
  3.5315 -  secondary head output is blanked while you are in X. With XFree
  3.5316 -  3.9.17 preview you can use both heads if you use SVGA over fbdev or
  3.5317 -  the fbdev driver on first head and the fbdev driver on second head.
  3.5318 -
  3.5319 -  If you compile it as module, two modules are created,
  3.5320 -  matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
  3.5321 -  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
  3.5322 -  also load i2c-matroxfb to get it to run.
  3.5323 -
  3.5324 -  The driver starts in monitor mode and you must use the matroxset
  3.5325 -  tool (available at
  3.5326 -  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
  3.5327 -  PAL or NTSC or to swap primary and secondary head outputs.
  3.5328 -  Secondary head driver also always start in 640x480 resolution, you
  3.5329 -  must use fbset to change it.
  3.5330 -
  3.5331 -  Also do not forget that second head supports only 16 and 32 bpp
  3.5332 -  packed pixels, so it is a good idea to compile them into the kernel
  3.5333 -  too.  You can use only some font widths, as the driver uses generic
  3.5334 -  painting procedures (the secondary head does not use acceleration
  3.5335 -  engine).
  3.5336 -
  3.5337 -CONFIG_FB_MATROX_PROC
  3.5338 -  Say Y or M here if you want to access some informations about driver
  3.5339 -  state through /proc interface.
  3.5340 -  
  3.5341 -  You should download matrox_pins tool (available at
  3.5342 -  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to get human
  3.5343 -  readable output.
  3.5344 -  
  3.5345 -CONFIG_FB_MATROX_MULTIHEAD
  3.5346 -  Say Y here if you have more than one (supported) Matrox device in
  3.5347 -  your computer and you want to use all of them for different monitors
  3.5348 -  ("multihead"). If you have only one device, you should say N because
  3.5349 -  the driver compiled with Y is larger and a bit slower, especially on
  3.5350 -  ia32 (ix86).
  3.5351 -
  3.5352 -  If you said M to "Matrox unified accelerated driver" and N here, you
  3.5353 -  will still be able to use several Matrox devices simultaneously:
  3.5354 -  insert several instances of the module matroxfb.o into the kernel
  3.5355 -  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
  3.5356 -  for the different Matrox devices. This method is slightly faster but
  3.5357 -  uses 40 KB of kernel memory per Matrox card.
  3.5358 -
  3.5359 -  There is no need for enabling 'Matrox multihead support' if you have
  3.5360 -  only one Matrox card in the box.
  3.5361 -
  3.5362 -3Dfx Voodoo Graphics / Voodoo2 frame buffer support
  3.5363 -CONFIG_FB_VOODOO1
  3.5364 -  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
  3.5365 -  Voodoo2 (cvg) based graphics card.
  3.5366 -
  3.5367 -  This driver is also available as a module ( = code which can be 
  3.5368 -  inserted and removed from the running kernel whenever you want).
  3.5369 -  The module will be called sstfb.o. If you want to compile it as
  3.5370 -  a module, say M here and read Documentation/modules.txt.
  3.5371 -
  3.5372 -  WARNING: Do not use any application that uses the 3D engine
  3.5373 -  (namely glide) while using this driver.
  3.5374 -  Please read the file Documentation/fb/README-sstfb.txt for supported
  3.5375 -  options and other important info  support.
  3.5376 -
  3.5377 -MDA text console (dual-headed)
  3.5378 -CONFIG_MDA_CONSOLE
  3.5379 -  Say Y here if you have an old MDA or monochrome Hercules graphics
  3.5380 -  adapter in your system acting as a second head ( = video card). You
  3.5381 -  will then be able to use two monitors with your Linux system. Do not
  3.5382 -  say Y here if your MDA card is the primary card in your system; the
  3.5383 -  normal VGA driver will handle it.
  3.5384 -
  3.5385 -  This driver is also available as a module ( = code which can be
  3.5386 -  inserted and removed from the running kernel whenever you want).
  3.5387 -  The module will be called mdacon.o. If you want to compile it as
  3.5388 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.5389 -
  3.5390 -  If unsure, say N.
  3.5391 -
  3.5392 -SBUS and UPA framebuffers
  3.5393 -CONFIG_FB_SBUS
  3.5394 -  Say Y if you want support for SBUS or UPA based frame buffer device.
  3.5395 -
  3.5396 -Creator/Creator3D support
  3.5397 -CONFIG_FB_CREATOR
  3.5398 -  This is the frame buffer device driver for the Creator and Creator3D
  3.5399 -  graphics boards.
  3.5400 -
  3.5401 -CGsix (GX,TurboGX) support
  3.5402 -CONFIG_FB_CGSIX
  3.5403 -  This is the frame buffer device driver for the CGsix (GX, TurboGX)
  3.5404 -  frame buffer.
  3.5405 -
  3.5406 -BWtwo support
  3.5407 -CONFIG_FB_BWTWO
  3.5408 -  This is the frame buffer device driver for the BWtwo frame buffer.
  3.5409 -
  3.5410 -CGthree support
  3.5411 -CONFIG_FB_CGTHREE
  3.5412 -  This is the frame buffer device driver for the CGthree frame buffer.
  3.5413 -
  3.5414 -CGfourteen (SX) support
  3.5415 -CONFIG_FB_CGFOURTEEN
  3.5416 -  This is the frame buffer device driver for the CGfourteen frame
  3.5417 -  buffer on Desktop SPARCsystems with the SX graphics option.
  3.5418 -
  3.5419 -P9100 (Sparcbook 3 only) support
  3.5420 -CONFIG_FB_P9100
  3.5421 -  This is the frame buffer device driver for the P9100 card
  3.5422 -  supported on Sparcbook 3 machines.
  3.5423 -
  3.5424 -Leo (ZX) support
  3.5425 -CONFIG_FB_LEO
  3.5426 -  This is the frame buffer device driver for the SBUS-based Sun ZX
  3.5427 -  (leo) frame buffer cards.
  3.5428 -
  3.5429 -IGA 168x display support
  3.5430 -CONFIG_FB_IGA
  3.5431 -  This is the framebuffer device for the INTERGRAPHICS 1680 and
  3.5432 -  successor frame buffer cards.
  3.5433 -
  3.5434 -TCX (SS4/SS5 only) support
  3.5435 -CONFIG_FB_TCX
  3.5436 -  This is the frame buffer device driver for the TCX 24/8bit frame
  3.5437 -  buffer.
  3.5438 -
  3.5439 -HD64461 Frame Buffer support
  3.5440 -CONFIG_FB_HIT
  3.5441 -  This is the frame buffer device driver for the Hitachi HD64461 LCD
  3.5442 -  frame buffer card.
  3.5443 -
  3.5444 -SIS display support
  3.5445 -CONFIG_FB_SIS
  3.5446 -  This is the frame buffer device driver for the SiS 300, 315 and 330
  3.5447 -  series chipsets.  Documentation available at the maintainer's site
  3.5448 -  at <http://www.winischhofer.net/linuxsisvga.shtml>.
  3.5449 -
  3.5450 -SIS 300 series support
  3.5451 -CONFIG_FB_SIS_300
  3.5452 -  This enables support for SiS 300 series chipsets (300/305, 540, 630,
  3.5453 -  730).  Documentation available at the maintainer's website at
  3.5454 -   <http://www.winischhofer.net/linuxsisvga.shtml>.
  3.5455 -
  3.5456 -SIS 315/330 series support
  3.5457 -CONFIG_FB_SIS_315
  3.5458 -  This enables support for SiS 315/330 series chipsets (315, 550, 650,
  3.5459 -  M650, 651, 661FX, M661FX, 740, 741, 330). Documentation available at
  3.5460 -  the maintainer's site <http://www.winischhofer.net/linuxsisvga.shtml>.
  3.5461 -
  3.5462 -IMS Twin Turbo display support
  3.5463 -CONFIG_FB_IMSTT
  3.5464 -  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
  3.5465 -  many Macintosh and compatible computers.
  3.5466 -
  3.5467 -CONFIG_FB_TX3912
  3.5468 -  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core;
  3.5469 -  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  3.5470 -
  3.5471 -  Say Y here to enable kernel support for the on-board framebuffer.
  3.5472 -
  3.5473 -Virtual Frame Buffer support (ONLY FOR TESTING!)
  3.5474 -CONFIG_FB_VIRTUAL
  3.5475 -  This is a `virtual' frame buffer device. It operates on a chunk of
  3.5476 -  unswappable kernel memory instead of on the memory of a graphics
  3.5477 -  board. This means you cannot see any output sent to this frame
  3.5478 -  buffer device, while it does consume precious memory. The main use
  3.5479 -  of this frame buffer device is testing and debugging the frame
  3.5480 -  buffer subsystem. Do NOT enable it for normal systems! To protect
  3.5481 -  the innocent, it has to be enabled explicitly at boot time using the
  3.5482 -  kernel option `video=vfb:'.
  3.5483 -
  3.5484 -  This driver is also available as a module ( = code which can be
  3.5485 -  inserted and removed from the running kernel whenever you want). The
  3.5486 -  module will be called vfb.o. If you want to compile it as a module,
  3.5487 -  say M here and read <file:Documentation/modules.txt>.
  3.5488 -
  3.5489 -  If unsure, say N.
  3.5490 -
  3.5491 -Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
  3.5492 -CONFIG_FB_ATY_CT
  3.5493 -  Say Y here to support use of ATI's 64-bit Rage boards (or other
  3.5494 -  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
  3.5495 -  framebuffer device.  The ATI product support page for these boards
  3.5496 -  is at <http://support.ati.com/products/pc/mach64/>.
  3.5497 -
  3.5498 -Sony Vaio Picturebook laptop LCD panel support
  3.5499 -CONFIG_FB_ATY_CT_VAIO_LCD
  3.5500 -  Say Y here if you want to use the full width of the Sony Vaio 
  3.5501 -  Picturebook laptops LCD panels (you will get a 128x30 console).
  3.5502 -
  3.5503 -  Note that you need to activate this mode using the 'vga=0x301'
  3.5504 -  option from your boot loader (lilo or loadlin).  See the
  3.5505 -  documentation of your boot loader about how to pass options to the
  3.5506 -  kernel.
  3.5507 -  
  3.5508 -Mach64 GX support
  3.5509 -CONFIG_FB_ATY_GX
  3.5510 -  Say Y here to support use of the ATI Mach64 Graphics Expression
  3.5511 -  board (or other boards based on the Mach64 GX chipset) as a
  3.5512 -  framebuffer device.  The ATI product support page for these boards
  3.5513 -  is at
  3.5514 -  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  3.5515 -
  3.5516 -Mach64 Generic LCD support
  3.5517 -CONFIG_FB_ATY_GENERIC_LCD
  3.5518 -  Enabling this option enables the Atyfb driver to drive LCD panels. It
  3.5519 -  will autodetect the resulution and format of your display and emulate
  3.5520 -  other resolutions using the hardware stretcher on the chip.
  3.5521 -  Say Y here if you have computer with a Rage LT Pro, Rage Mobility M1,
  3.5522 -  Rage XC or Rage XL chip and a laptop LCD display or any other LCD display
  3.5523 -  that needs to be digitally driven. It is not necessary to enable this
  3.5524 -  option if you are using an LCD display with a normal VGA connector,
  3.5525 -  but it won't hurt if you do.
  3.5526 -
  3.5527 -ATI Radeon display support
  3.5528 -CONFIG_FB_RADEON
  3.5529 -  Choose this option if you want to use an ATI Radeon graphics card as
  3.5530 -  a framebuffer device.  There are both PCI and AGP versions.  You
  3.5531 -  don't need to choose this to run the Radeon in plain VGA mode.
  3.5532 -  There is a product page at
  3.5533 -  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
  3.5534 -
  3.5535 -SA-1100 LCD support
  3.5536 -CONFIG_FB_SA1100
  3.5537 -  This is a framebuffer device for the SA-1100 LCD Controller.
  3.5538 -  See <http://www.linux-fbdev.org/> for information on framebuffer
  3.5539 -  devices.
  3.5540 -
  3.5541 -  If you plan to use the LCD display with your SA-1100 system, say
  3.5542 -  Y here.
  3.5543 -
  3.5544 -Advanced low level driver options
  3.5545 -CONFIG_FBCON_ADVANCED
  3.5546 -  The frame buffer console uses character drawing routines that are
  3.5547 -  tailored to the specific organization of pixels in the memory of
  3.5548 -  your graphics hardware. These are called the low level frame buffer
  3.5549 -  console drivers. Note that they are used for text console output
  3.5550 -  only; they are NOT needed for graphical applications.
  3.5551 -
  3.5552 -  If you say N here, the needed low level drivers are automatically
  3.5553 -  enabled, depending on what frame buffer devices you selected above.
  3.5554 -  This is recommended for most users.
  3.5555 -
  3.5556 -  If you say Y here, you have more fine-grained control over which low
  3.5557 -  level drivers are enabled. You can e.g. leave out low level drivers
  3.5558 -  for color depths you do not intend to use for text consoles.
  3.5559 -
  3.5560 -  Low level frame buffer console drivers can be modules ( = code which
  3.5561 -  can be inserted and removed from the running kernel whenever you
  3.5562 -  want). The modules will be called fbcon-*.o. If you want to compile
  3.5563 -  (some of) them as modules, read <file:Documentation/modules.txt>.
  3.5564 -
  3.5565 -  If unsure, say N.
  3.5566 -
  3.5567 -Monochrome support
  3.5568 -CONFIG_FBCON_MFB
  3.5569 -  This is the low level frame buffer console driver for monochrome
  3.5570 -  (2 colors) packed pixels.
  3.5571 -
  3.5572 -2 bpp packed pixels support
  3.5573 -CONFIG_FBCON_CFB2
  3.5574 -  This is the low level frame buffer console driver for 2 bits per
  3.5575 -  pixel (4 colors) packed pixels.
  3.5576 -
  3.5577 -4 bpp packed pixels support
  3.5578 -CONFIG_FBCON_CFB4
  3.5579 -  This is the low level frame buffer console driver for 4 bits per
  3.5580 -  pixel (16 colors) packed pixels.
  3.5581 -
  3.5582 -8 bpp packed pixels support
  3.5583 -CONFIG_FBCON_CFB8
  3.5584 -  This is the low level frame buffer console driver for 8 bits per
  3.5585 -  pixel (256 colors) packed pixels.
  3.5586 -
  3.5587 -16 bpp packed pixels support
  3.5588 -CONFIG_FBCON_CFB16
  3.5589 -  This is the low level frame buffer console driver for 15 or 16 bits
  3.5590 -  per pixel (32K or 64K colors, also known as `hicolor') packed
  3.5591 -  pixels.
  3.5592 -
  3.5593 -24 bpp packed pixels support
  3.5594 -CONFIG_FBCON_CFB24
  3.5595 -  This is the low level frame buffer console driver for 24 bits per
  3.5596 -  pixel (16M colors, also known as `truecolor') packed pixels. It is
  3.5597 -  NOT for `sparse' 32 bits per pixel mode.
  3.5598 -
  3.5599 -32 bpp packed pixels support
  3.5600 -CONFIG_FBCON_CFB32
  3.5601 -  This is the low level frame buffer console driver for 32 bits per
  3.5602 -  pixel (16M colors, also known as `truecolor') sparse packed pixels.
  3.5603 -
  3.5604 -Amiga bitplanes support
  3.5605 -CONFIG_FBCON_AFB
  3.5606 -  This is the low level frame buffer console driver for 1 to 8
  3.5607 -  bitplanes (2 to 256 colors) on Amiga.
  3.5608 -
  3.5609 -Amiga interleaved bitplanes support
  3.5610 -CONFIG_FBCON_ILBM
  3.5611 -  This is the low level frame buffer console driver for 1 to 8
  3.5612 -  interleaved bitplanes (2 to 256 colors) on Amiga.
  3.5613 -
  3.5614 -Atari interleaved bitplanes (2 planes) support
  3.5615 -CONFIG_FBCON_IPLAN2P2
  3.5616 -  This is the low level frame buffer console driver for 2 interleaved
  3.5617 -  bitplanes (4 colors) on Atari.
  3.5618 -
  3.5619 -Atari interleaved bitplanes (4 planes) support
  3.5620 -CONFIG_FBCON_IPLAN2P4
  3.5621 -  This is the low level frame buffer console driver for 4 interleaved
  3.5622 -  bitplanes (16 colors) on Atari.
  3.5623 -
  3.5624 -Atari interleaved bitplanes (8 planes) support
  3.5625 -CONFIG_FBCON_IPLAN2P8
  3.5626 -  This is the low level frame buffer console driver for 8 interleaved
  3.5627 -  bitplanes (256 colors) on Atari.
  3.5628 -
  3.5629 -Mac variable bpp packed pixels support
  3.5630 -CONFIG_FBCON_MAC
  3.5631 -  This is the low level frame buffer console driver for 1/2/4/8/16/32
  3.5632 -  bits per pixel packed pixels on Mac. It supports variable font
  3.5633 -  widths for low resolution screens.
  3.5634 -
  3.5635 -Permedia3 support (EXPERIMENTAL)
  3.5636 -CONFIG_FB_PM3
  3.5637 -  This is the frame buffer device driver for the 3DLabs Permedia3
  3.5638 -  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  3.5639 -  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  3.5640 -  and maybe other boards.
  3.5641 -
  3.5642 -HGA monochrome support
  3.5643 -CONFIG_FBCON_HGA
  3.5644 -  This is the low level frame buffer console driver for Hercules mono
  3.5645 -  graphics cards.
  3.5646 -
  3.5647 -VGA characters/attributes support
  3.5648 -CONFIG_FBCON_VGA
  3.5649 -  This is the low level frame buffer console driver for VGA text mode;
  3.5650 -  it is used by frame buffer device drivers that support VGA text
  3.5651 -  mode.
  3.5652 -
  3.5653 -Parallel-port support
  3.5654 -CONFIG_PARPORT
  3.5655 -  If you want to use devices connected to your machine's parallel port
  3.5656 -  (the connector at the computer with 25 holes), e.g. printer, ZIP
  3.5657 -  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
  3.5658 -  create a mini network by connecting the parallel ports of two local
  3.5659 -  machines) etc., then you need to say Y here; please read
  3.5660 -  <file:Documentation/parport.txt> and
  3.5661 -  <file:drivers/parport/BUGS-parport>.
  3.5662 -
  3.5663 -  For extensive information about drivers for many devices attaching
  3.5664 -  to the parallel port see <http://www.torque.net/linux-pp.html> on
  3.5665 -  the WWW.
  3.5666 -
  3.5667 -  It is possible to share a single parallel port among several devices
  3.5668 -  and it is safe to compile all the corresponding drivers into the
  3.5669 -  kernel.  If you want to compile parallel port support as a module
  3.5670 -  ( = code which can be inserted in and removed from the running
  3.5671 -  kernel whenever you want), say M here and read
  3.5672 -  <file:Documentation/modules.txt>.  The module will be called
  3.5673 -  parport.o.  If you have more than one parallel port and want to
  3.5674 -  specify which port and IRQ to be used by this driver at module load
  3.5675 -  time, take a look at <file:Documentation/parport.txt>.
  3.5676 -
  3.5677 -  If unsure, say Y.
  3.5678 -
  3.5679 -PC-style hardware
  3.5680 -CONFIG_PARPORT_PC
  3.5681 -  You should say Y here if you have a PC-style parallel port. All IBM
  3.5682 -  PC compatible computers and some Alphas have PC-style parallel
  3.5683 -  ports.
  3.5684 -
  3.5685 -  This code is also available as a module.  If you want to compile it
  3.5686 -  as a module ( = code which can be inserted in and removed from the
  3.5687 -  running kernel whenever you want), say M here and read
  3.5688 -  <file:Documentation/modules.txt>.  The module will be called
  3.5689 -  parport_pc.o.
  3.5690 -
  3.5691 -  If unsure, say Y.
  3.5692 -
  3.5693 -Parallel+serial PCI multi-IO card support
  3.5694 -CONFIG_PARPORT_SERIAL
  3.5695 -  This adds support for multi-IO PCI cards that have parallel and
  3.5696 -  serial ports.  You should say Y or M here.  If you say M, the module
  3.5697 -  will be called parport_serial.o.
  3.5698 -
  3.5699 -Use FIFO/DMA if available
  3.5700 -CONFIG_PARPORT_PC_FIFO
  3.5701 -  Many parallel port chipsets provide hardware that can speed up
  3.5702 -  printing. Say Y here if you want to take advantage of that.
  3.5703 -
  3.5704 -  As well as actually having a FIFO, or DMA capability, the kernel
  3.5705 -  will need to know which IRQ the parallel port has.  By default,
  3.5706 -  parallel port interrupts will not be used, and so neither will the
  3.5707 -  FIFO.  See <file:Documentation/parport.txt> to find out how to
  3.5708 -  specify which IRQ/DMA to use.
  3.5709 -
  3.5710 -SuperIO chipset support
  3.5711 -CONFIG_PARPORT_PC_SUPERIO
  3.5712 -  Saying Y here enables some probes for Super-IO chipsets in order to
  3.5713 -  find out things like base addresses, IRQ lines and DMA channels.  It
  3.5714 -  is safe to say N.
  3.5715 -
  3.5716 -Support for PCMCIA management for PC-style ports
  3.5717 -CONFIG_PARPORT_PC_PCMCIA
  3.5718 -  Say Y here if you need PCMCIA support for your PC-style parallel
  3.5719 -  ports. If unsure, say N.
  3.5720 -
  3.5721 -  This driver is also available as a module ( = code which can be
  3.5722 -  inserted in and removed from the running kernel whenever you want).
  3.5723 -  If you want to compile it as a module, say M here and read
  3.5724 -  <file:Documentation/modules.txt>. The module will be called
  3.5725 -  parport_cs.o
  3.5726 -
  3.5727 -Support foreign hardware
  3.5728 -CONFIG_PARPORT_OTHER
  3.5729 -  Say Y here if you want to be able to load driver modules to support
  3.5730 -  other non-standard types of parallel ports. This causes a
  3.5731 -  performance loss, so most people say N.
  3.5732 -
  3.5733 -Amiga built-in parallel port support
  3.5734 -CONFIG_PARPORT_AMIGA
  3.5735 -  Say Y here if you need support for the parallel port hardware on
  3.5736 -  Amiga machines. This code is also available as a module (say M),
  3.5737 -  called parport_amiga.o. If in doubt, saying N is the safe plan.
  3.5738 -
  3.5739 -Atari built-in parallel port support
  3.5740 -CONFIG_PARPORT_ATARI
  3.5741 -  Say Y here if you need support for the parallel port hardware on
  3.5742 -  Atari machines. This code is also available as a module (say M),
  3.5743 -  called parport_atari.o. If in doubt, saying N is the safe plan.
  3.5744 -
  3.5745 -Multiface III parallel port support
  3.5746 -CONFIG_PARPORT_MFC3
  3.5747 -  Say Y here if you need parallel port support for the MFC3 card.
  3.5748 -  This code is also available as a module (say M), called
  3.5749 -  parport_mfc3.o. If in doubt, saying N is the safe plan.
  3.5750 -
  3.5751 -Support IEEE 1284 status readback
  3.5752 -CONFIG_PRINTER_READBACK
  3.5753 -  If you have a device on your parallel port that support this
  3.5754 -  protocol, this option will allow the device to report its status. It
  3.5755 -  is safe to say Y.
  3.5756 -
  3.5757 -IEEE 1284 transfer modes
  3.5758 -CONFIG_PARPORT_1284
  3.5759 -  If you have a printer that supports status readback or device ID, or
  3.5760 -  want to use a device that uses enhanced parallel port transfer modes
  3.5761 -  such as EPP and ECP, say Y here to enable advanced IEEE 1284
  3.5762 -  transfer modes. Also say Y if you want device ID information to
  3.5763 -  appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
  3.5764 -
  3.5765 -Enable loadable module support
  3.5766 -CONFIG_MODULES
  3.5767 -  Kernel modules are small pieces of compiled code which can be
  3.5768 -  inserted in or removed from the running kernel, using the programs
  3.5769 -  insmod and rmmod. This is described in the file
  3.5770 -  <file:Documentation/modules.txt>, including the fact that you have
  3.5771 -  to say "make modules" in order to compile the modules that you chose
  3.5772 -  during kernel configuration.  Modules can be device drivers, file
  3.5773 -  systems, binary executable formats, and so on. If you think that you
  3.5774 -  may want to make use of modules with this kernel in the future, then
  3.5775 -  say Y here.  If unsure, say Y.
  3.5776 -
  3.5777 -Set version information on all symbols for modules
  3.5778 -CONFIG_MODVERSIONS
  3.5779 -  Usually, modules have to be recompiled whenever you switch to a new
  3.5780 -  kernel.  Saying Y here makes it possible, and safe, to use the
  3.5781 -  same modules even after compiling a new kernel; this requires the
  3.5782 -  program modprobe. All the software needed for module support is in
  3.5783 -  the modutils package (check the file <file:Documentation/Changes>
  3.5784 -  for location and latest version).  NOTE: if you say Y here but don't
  3.5785 -  have the program genksyms (which is also contained in the above
  3.5786 -  mentioned modutils package), then the building of your kernel will
  3.5787 -  fail.  If you are going to use modules that are generated from
  3.5788 -  non-kernel sources, you would benefit from this option.  Otherwise
  3.5789 -  it's not that important.  So, N ought to be a safe bet.
  3.5790 -
  3.5791 -Kernel module loader support
  3.5792 -CONFIG_KMOD
  3.5793 -  Normally when you have selected some drivers and/or file systems to
  3.5794 -  be created as loadable modules, you also have the responsibility to
  3.5795 -  load the corresponding modules (using the programs insmod or
  3.5796 -  modprobe) before you can use them. If you say Y here however, the
  3.5797 -  kernel will be able to load modules for itself: when a part of the
  3.5798 -  kernel needs a module, it runs modprobe with the appropriate
  3.5799 -  arguments, thereby loading the module if it is available. (This is a
  3.5800 -  replacement for kerneld.) Say Y here and read about configuring it
  3.5801 -  in <file:Documentation/kmod.txt>.
  3.5802 -
  3.5803 -ARP daemon support
  3.5804 -CONFIG_ARPD
  3.5805 -  Normally, the kernel maintains an internal cache which maps IP
  3.5806 -  addresses to hardware addresses on the local network, so that
  3.5807 -  Ethernet/Token Ring/ etc. frames are sent to the proper address on
  3.5808 -  the physical networking layer. For small networks having a few
  3.5809 -  hundred directly connected hosts or less, keeping this address
  3.5810 -  resolution (ARP) cache inside the kernel works well. However,
  3.5811 -  maintaining an internal ARP cache does not work well for very large
  3.5812 -  switched networks, and will use a lot of kernel memory if TCP/IP
  3.5813 -  connections are made to many machines on the network.
  3.5814 -
  3.5815 -  If you say Y here, the kernel's internal ARP cache will never grow
  3.5816 -  to more than 256 entries (the oldest entries are expired in a LIFO
  3.5817 -  manner) and communication will be attempted with the user space ARP
  3.5818 -  daemon arpd. Arpd then answers the address resolution request either
  3.5819 -  from its own cache or by asking the net.
  3.5820 -
  3.5821 -  This code is experimental and also obsolete. If you want to use it,
  3.5822 -  you need to find a version of the daemon arpd on the net somewhere,
  3.5823 -  and you should also say Y to "Kernel/User network link driver",
  3.5824 -  below. If unsure, say N.
  3.5825 -
  3.5826 -TCP/IP networking
  3.5827 -CONFIG_INET
  3.5828 -  These are the protocols used on the Internet and on most local
  3.5829 -  Ethernets. It is highly recommended to say Y here (this will enlarge
  3.5830 -  your kernel by about 144 KB), since some programs (e.g. the X window
  3.5831 -  system) use TCP/IP even if your machine is not connected to any
  3.5832 -  other computer. You will get the so-called loopback device which
  3.5833 -  allows you to ping yourself (great fun, that!).
  3.5834 -
  3.5835 -  For an excellent introduction to Linux networking, please read the
  3.5836 -  NET-3-HOWTO, available from
  3.5837 -  <http://www.tldp.org/docs.html#howto>.
  3.5838 -
  3.5839 -  This option is also necessary if you want to use the full power of
  3.5840 -  term (term is a program which gives you almost full Internet
  3.5841 -  connectivity if you have a regular dial up shell account on some
  3.5842 -  Internet connected Unix computer; for more information, read
  3.5843 -  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
  3.5844 -
  3.5845 -  If you say Y here and also to "/proc file system support" and
  3.5846 -  "Sysctl support" below, you can change various aspects of the
  3.5847 -  behaviour of the TCP/IP code by writing to the (virtual) files in
  3.5848 -  /proc/sys/net/ipv4/*; the options are explained in the file
  3.5849 -  <file:Documentation/networking/ip-sysctl.txt>.
  3.5850 -
  3.5851 -  Short answer: say Y.
  3.5852 -
  3.5853 -IP multicasting
  3.5854 -CONFIG_IP_MULTICAST
  3.5855 -  This is code for addressing several networked computers at once,
  3.5856 -  enlarging your kernel by about 2 KB. You need multicasting if you
  3.5857 -  intend to participate in the MBONE, a high bandwidth network on top
  3.5858 -  of the Internet which carries audio and video broadcasts. More
  3.5859 -  information about the MBONE is on the WWW at
  3.5860 -  <http://www-itg.lbl.gov/mbone/>. Information about the multicast
  3.5861 -  capabilities of the various network cards is contained in
  3.5862 -  <file:Documentation/networking/multicast.txt>. For most people, it's
  3.5863 -  safe to say N.
  3.5864 -
  3.5865 -Advanced router
  3.5866 -CONFIG_IP_ADVANCED_ROUTER
  3.5867 -  If you intend to run your Linux box mostly as a router, i.e. as a
  3.5868 -  computer that forwards and redistributes network packets, say Y; you
  3.5869 -  will then be presented with several options that allow more precise
  3.5870 -  control about the routing process.
  3.5871 -
  3.5872 -  The answer to this question won't directly affect the kernel:
  3.5873 -  answering N will just cause the configurator to skip all the
  3.5874 -  questions about advanced routing.
  3.5875 -
  3.5876 -  Note that your box can only act as a router if you enable IP
  3.5877 -  forwarding in your kernel; you can do that by saying Y to "/proc
  3.5878 -  file system support" and "Sysctl support" below and executing the
  3.5879 -  line
  3.5880 -
  3.5881 -    echo "1" > /proc/sys/net/ipv4/ip_forward
  3.5882 -
  3.5883 -  at boot time after the /proc file system has been mounted.
  3.5884 -
  3.5885 -  If you turn on IP forwarding, you will also get the rp_filter, which
  3.5886 -  automatically rejects incoming packets if the routing table entry
  3.5887 -  for their source address doesn't match the network interface they're
  3.5888 -  arriving on. This has security advantages because it prevents the
  3.5889 -  so-called IP spoofing, however it can pose problems if you use
  3.5890 -  asymmetric routing (packets from you to a host take a different path
  3.5891 -  than packets from that host to you) or if you operate a non-routing
  3.5892 -  host which has several IP addresses on different interfaces. To turn
  3.5893 -  rp_filter off use:
  3.5894 -
  3.5895 -        echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
  3.5896 -  or
  3.5897 -        echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
  3.5898 -
  3.5899 -  If unsure, say N here.
  3.5900 -
  3.5901 -Policy routing
  3.5902 -CONFIG_IP_MULTIPLE_TABLES
  3.5903 -  Normally, a router decides what to do with a received packet based
  3.5904 -  solely on the packet's final destination address. If you say Y here,
  3.5905 -  the Linux router will also be able to take the packet's source
  3.5906 -  address into account. Furthermore, if you also say Y to "Use TOS
  3.5907 -  value as routing key" below, the TOS (Type-Of-Service) field of the
  3.5908 -  packet can be used for routing decisions as well. In addition, if
  3.5909 -  you say Y here and to "Fast network address translation" below,
  3.5910 -  the router will also be able to modify source and destination
  3.5911 -  addresses of forwarded packets.
  3.5912 -
  3.5913 -  If you are interested in this, please see the preliminary
  3.5914 -  documentation at <http://www.compendium.com.ar/policy-routing.txt>
  3.5915 -  and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
  3.5916 -  You will need supporting software from
  3.5917 -  <ftp://ftp.inr.ac.ru/ip-routing/>.
  3.5918 -
  3.5919 -  If unsure, say N.
  3.5920 -
  3.5921 -Equal cost multipath
  3.5922 -CONFIG_IP_ROUTE_MULTIPATH
  3.5923 -  Normally, the routing tables specify a single action to be taken in
  3.5924 -  a deterministic manner for a given packet. If you say Y here
  3.5925 -  however, it becomes possible to attach several actions to a packet
  3.5926 -  pattern, in effect specifying several alternative paths to travel
  3.5927 -  for those packets. The router considers all these paths to be of
  3.5928 -  equal "cost" and chooses one of them in a non-deterministic fashion
  3.5929 -  if a matching packet arrives.
  3.5930 -
  3.5931 -Use TOS value as routing key
  3.5932 -CONFIG_IP_ROUTE_TOS
  3.5933 -  The header of every IP packet carries a TOS (Type Of Service) value
  3.5934 -  with which the packet requests a certain treatment, e.g. low
  3.5935 -  latency (for interactive traffic), high throughput, or high
  3.5936 -  reliability.  If you say Y here, you will be able to specify
  3.5937 -  different routes for packets with different TOS values.
  3.5938 -
  3.5939 -Use netfilter MARK value as routing key
  3.5940 -CONFIG_IP_ROUTE_FWMARK
  3.5941 -  If you say Y here, you will be able to specify different routes for
  3.5942 -  packets with different mark values (see iptables(8), MARK target).
  3.5943 -
  3.5944 -Verbose route monitoring
  3.5945 -CONFIG_IP_ROUTE_VERBOSE
  3.5946 -  If you say Y here, which is recommended, then the kernel will print
  3.5947 -  verbose messages regarding the routing, for example warnings about
  3.5948 -  received packets which look strange and could be evidence of an
  3.5949 -  attack or a misconfigured system somewhere. The information is
  3.5950 -  handled by the klogd daemon which is responsible for kernel messages
  3.5951 -  ("man klogd").
  3.5952 -
  3.5953 -Fast network address translation
  3.5954 -CONFIG_IP_ROUTE_NAT
  3.5955 -  If you say Y here, your router will be able to modify source and
  3.5956 -  destination addresses of packets that pass through it, in a manner
  3.5957 -  you specify.  General information about Network Address Translation
  3.5958 -  can be gotten from the document
  3.5959 -  <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
  3.5960 -
  3.5961 -Kernel level IP autoconfiguration
  3.5962 -CONFIG_IP_PNP
  3.5963 -  This enables automatic configuration of IP addresses of devices and
  3.5964 -  of the routing table during kernel boot, based on either information
  3.5965 -  supplied on the kernel command line or by BOOTP or RARP protocols.
  3.5966 -  You need to say Y only for diskless machines requiring network
  3.5967 -  access to boot (in which case you want to say Y to "Root file system
  3.5968 -  on NFS" as well), because all other machines configure the network
  3.5969 -  in their startup scripts.
  3.5970 -
  3.5971 -BOOTP support
  3.5972 -CONFIG_IP_PNP_BOOTP
  3.5973 -  If you want your Linux box to mount its whole root file system (the
  3.5974 -  one containing the directory /) from some other computer over the
  3.5975 -  net via NFS and you want the IP address of your computer to be
  3.5976 -  discovered automatically at boot time using the BOOTP protocol (a
  3.5977 -  special protocol designed for doing this job), say Y here. In case
  3.5978 -  the boot ROM of your network card was designed for booting Linux and
  3.5979 -  does BOOTP itself, providing all necessary information on the kernel
  3.5980 -  command line, you can say N here. If unsure, say Y. Note that if you
  3.5981 -  want to use BOOTP, a BOOTP server must be operating on your network.
  3.5982 -  Read <file:Documentation/nfsroot.txt> for details.
  3.5983 -
  3.5984 -DHCP support
  3.5985 -CONFIG_IP_PNP_DHCP
  3.5986 -  If you want your Linux box to mount its whole root file system (the
  3.5987 -  one containing the directory /) from some other computer over the
  3.5988 -  net via NFS and you want the IP address of your computer to be
  3.5989 -  discovered automatically at boot time using the DHCP protocol (a
  3.5990 -  special protocol designed for doing this job), say Y here. In case
  3.5991 -  the boot ROM of your network card was designed for booting Linux and
  3.5992 -  does DHCP itself, providing all necessary information on the kernel
  3.5993 -  command line, you can say N here.
  3.5994 -
  3.5995 -  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
  3.5996 -  must be operating on your network.  Read
  3.5997 -  <file:Documentation/nfsroot.txt> for details.
  3.5998 -
  3.5999 -RARP support
  3.6000 -CONFIG_IP_PNP_RARP
  3.6001 -  If you want your Linux box to mount its whole root file system (the
  3.6002 -  one containing the directory /) from some other computer over the
  3.6003 -  net via NFS and you want the IP address of your computer to be
  3.6004 -  discovered automatically at boot time using the RARP protocol (an
  3.6005 -  older protocol which is being obsoleted by BOOTP and DHCP), say Y
  3.6006 -  here. Note that if you want to use RARP, a RARP server must be
  3.6007 -  operating on your network. Read <file:Documentation/nfsroot.txt> for
  3.6008 -  details.
  3.6009 -
  3.6010 -IP tunneling
  3.6011 -CONFIG_NET_IPIP
  3.6012 -  Tunneling means encapsulating data of one protocol type within
  3.6013 -  another protocol and sending it over a channel that understands the
  3.6014 -  encapsulating protocol. This particular tunneling driver implements
  3.6015 -  encapsulation of IP within IP, which sounds kind of pointless, but
  3.6016 -  can be useful if you want to make your (or some other) machine
  3.6017 -  appear on a different network than it physically is, or to use
  3.6018 -  mobile-IP facilities (allowing laptops to seamlessly move between
  3.6019 -  networks without changing their IP addresses; check out
  3.6020 -  <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
  3.6021 -
  3.6022 -  Saying Y to this option will produce two modules ( = code which can
  3.6023 -  be inserted in and removed from the running kernel whenever you
  3.6024 -  want). Most people won't need this and can say N.
  3.6025 -
  3.6026 -  This driver is also available as a module ( = code which can be
  3.6027 -  inserted in and removed from the running kernel whenever you want).
  3.6028 -  If you want to compile it as a module, say M here and read
  3.6029 -  <file:Documentation/modules.txt>. The module will be called
  3.6030 -  ipip.o
  3.6031 -
  3.6032 -GRE tunnels over IP
  3.6033 -CONFIG_NET_IPGRE
  3.6034 -  Tunneling means encapsulating data of one protocol type within
  3.6035 -  another protocol and sending it over a channel that understands the
  3.6036 -  encapsulating protocol. This particular tunneling driver implements
  3.6037 -  GRE (Generic Routing Encapsulation) and at this time allows
  3.6038 -  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  3.6039 -  This driver is useful if the other endpoint is a Cisco router: Cisco
  3.6040 -  likes GRE much better than the other Linux tunneling driver ("IP
  3.6041 -  tunneling" above). In addition, GRE allows multicast redistribution
  3.6042 -  through the tunnel.
  3.6043 -
  3.6044 -  This driver is also available as a module ( = code which can be
  3.6045 -  inserted in and removed from the running kernel whenever you want).
  3.6046 -  If you want to compile it as a module, say M here and read
  3.6047 -  <file:Documentation/modules.txt>. The module will be called
  3.6048 -  ip_gre.o
  3.6049 -
  3.6050 -Broadcast GRE over IP
  3.6051 -CONFIG_NET_IPGRE_BROADCAST
  3.6052 -  One application of GRE/IP is to construct a broadcast WAN (Wide Area
  3.6053 -  Network), which looks like a normal Ethernet LAN (Local Area
  3.6054 -  Network), but can be distributed all over the Internet. If you want
  3.6055 -  to do that, say Y here and to "IP multicast routing" below.
  3.6056 -
  3.6057 -IP multicast routing
  3.6058 -CONFIG_IP_MROUTE
  3.6059 -  This is used if you want your machine to act as a router for IP
  3.6060 -  packets that have several destination addresses. It is needed on the
  3.6061 -  MBONE, a high bandwidth network on top of the Internet which carries
  3.6062 -  audio and video broadcasts. In order to do that, you would most
  3.6063 -  likely run the program mrouted. Information about the multicast
  3.6064 -  capabilities of the various network cards is contained in
  3.6065 -  <file:Documentation/networking/multicast.txt>. If you haven't heard
  3.6066 -  about it, you don't need it.
  3.6067 -
  3.6068 -PIM-SM version 1 support
  3.6069 -CONFIG_IP_PIMSM_V1
  3.6070 -  Kernel side support for Sparse Mode PIM (Protocol Independent
  3.6071 -  Multicast) version 1. This multicast routing protocol is used widely
  3.6072 -  because Cisco supports it. You need special software to use it
  3.6073 -  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
  3.6074 -  information about PIM.
  3.6075 -
  3.6076 -  Say Y if you want to use PIM-SM v1. Note that you can say N here if
  3.6077 -  you just want to use Dense Mode PIM.
  3.6078 -
  3.6079 -PIM-SM version 2 support
  3.6080 -CONFIG_IP_PIMSM_V2
  3.6081 -  Kernel side support for Sparse Mode PIM version 2. In order to use
  3.6082 -  this, you need an experimental routing daemon supporting it (pimd or
  3.6083 -  gated-5). This routing protocol is not used widely, so say N unless
  3.6084 -  you want to play with it.
  3.6085 -
  3.6086 -Unix domain sockets
  3.6087 -CONFIG_UNIX
  3.6088 -  If you say Y here, you will include support for Unix domain sockets;
  3.6089 -  sockets are the standard Unix mechanism for establishing and
  3.6090 -  accessing network connections.  Many commonly used programs such as
  3.6091 -  the X Window system and syslog use these sockets even if your
  3.6092 -  machine is not connected to any network.  Unless you are working on
  3.6093 -  an embedded system or something similar, you therefore definitely
  3.6094 -  want to say Y here.
  3.6095 -
  3.6096 -  However, the socket support is also available as a module ( = code
  3.6097 -  which can be inserted in and removed from the running kernel
  3.6098 -  whenever you want).  If you want to compile it as a module, say M
  3.6099 -  here and read <file:Documentation/modules.txt>. The module will be
  3.6100 -  called unix.o.  If you try building this as a module and you have
  3.6101 -  said Y to "Kernel module loader support" above, be sure to add
  3.6102 -  'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
  3.6103 -  several important services won't work correctly if you say M here
  3.6104 -  and then neglect to load the module.
  3.6105 -
  3.6106 -  Say Y unless you know what you are doing.
  3.6107 -
  3.6108 -The IPv6 protocol
  3.6109 -CONFIG_IPV6
  3.6110 -  This is experimental support for the next version of the Internet
  3.6111 -  Protocol: IP version 6 (also called IPng "IP next generation").
  3.6112 -  Features of this new protocol include: expanded address space,
  3.6113 -  authentication and privacy, and seamless interoperability with the
  3.6114 -  current version of IP (IP version 4). For general information about
  3.6115 -  IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
  3.6116 -  for specific information about IPv6 under Linux read the HOWTO at
  3.6117 -  <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
  3.6118 -  in the kernel source.
  3.6119 -
  3.6120 -  If you want to use IPv6, please upgrade to the newest net-tools as
  3.6121 -  given in <file:Documentation/Changes>. You will still be able to do
  3.6122 -  regular IPv4 networking as well.
  3.6123 -
  3.6124 -  This protocol support is also available as a module ( = code which
  3.6125 -  can be inserted in and removed from the running kernel whenever you
  3.6126 -  want). The module will be called ipv6.o. If you want to compile it
  3.6127 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.6128 -
  3.6129 -  It is safe to say N here for now.
  3.6130 -
  3.6131 -The SCTP Protocol (EXPERIMENTAL)
  3.6132 -CONFIG_IP_SCTP
  3.6133 -  Stream Control Transmission Protocol
  3.6134 -
  3.6135 -  From RFC 2960 (http://www.ietf.org/rfc/rfc2960.txt)
  3.6136 -
  3.6137 -  "SCTP is a reliable transport protocol operating on top of a
  3.6138 -  connectionless packet network such as IP.  It offers the following
  3.6139 -  services to its users:
  3.6140 -
  3.6141 -  -- acknowledged error-free non-duplicated transfer of user data,
  3.6142 -  -- data fragmentation to conform to discovered path MTU size,
  3.6143 -  -- sequenced delivery of user messages within multiple streams,
  3.6144 -  with an option for order-of-arrival delivery of individual user
  3.6145 -  messages,
  3.6146 -  -- optional bundling of multiple user messages into a single SCTP
  3.6147 -  packet, and
  3.6148 -  -- network-level fault tolerance through supporting of multi-
  3.6149 -  homing at either or both ends of an association."
  3.6150 -
  3.6151 -  This protocol support is also available as a module ( = code which
  3.6152 -  can be inserted in and removed from the running kernel whenever you
  3.6153 -  want). The module will be called sctp. If you want to compile it
  3.6154 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.6155 -
  3.6156 -  If in doubt, say N.
  3.6157 -
  3.6158 -SCTP: Use old checksum (Adler-32)
  3.6159 -CONFIG_SCTP_ADLER32
  3.6160 -  RCF2960 currently specifies the Adler-32 checksum algorithm for SCTP.
  3.6161 -  This has been deprecated and replaced by an algorithm now referred
  3.6162 -  to as crc32c.
  3.6163 -
  3.6164 -  If you say Y, this will use the Adler-32 algorithm, this might be 
  3.6165 -  useful for interoperation with downlevel peers. 
  3.6166 -
  3.6167 -  If unsure, say N.  
  3.6168 -
  3.6169 -SCTP: Debug messages
  3.6170 -CONFIG_SCTP_DBG_MSG
  3.6171 -  If you say Y, this will enable verbose debugging messages. 
  3.6172 -
  3.6173 -  If unsure, say N.  However, if you are running into problems, use 
  3.6174 -  this option to gather detailed trace information
  3.6175 -
  3.6176 -SCTP: Debug object counts
  3.6177 -CONFIG_SCTP_DBG_OBJCNT
  3.6178 -  If you say Y, this will enable debugging support for counting the 
  3.6179 -  type of objects that are currently allocated.  This is useful for 
  3.6180 -  identifying memory leaks.   If the /proc filesystem is enabled this 
  3.6181 -  debug information can be viewed by 
  3.6182 -  'cat /proc/net/sctp/sctp_dbg_objcnt'
  3.6183 -
  3.6184 -  If unsure, say N
  3.6185 -
  3.6186 -Kernel httpd acceleration
  3.6187 -CONFIG_KHTTPD
  3.6188 -  The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
  3.6189 -  server built into the kernel. It is limited since it can only serve
  3.6190 -  files from the file system and cannot deal with executable content
  3.6191 -  such as CGI scripts. Serving files is sped up if you use kHTTPd.
  3.6192 -  If kHTTPd is not able to fulfill a request, it can transparently
  3.6193 -  pass it through to a user space web server such as apache.
  3.6194 -
  3.6195 -  Saying "M" here builds the kHTTPd module; this is NOT enough to have
  3.6196 -  a working kHTTPd. For safety reasons, the module has to be activated
  3.6197 -  by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
  3.6198 -  module.
  3.6199 -
  3.6200 -  Before using this, read the README in net/khttpd !
  3.6201 -
  3.6202 -  The kHTTPd is experimental. Be careful when using it on a production
  3.6203 -  machine. Also note that kHTTPd doesn't support virtual servers yet.
  3.6204 -
  3.6205 -The IPX protocol
  3.6206 -CONFIG_IPX
  3.6207 -  This is support for the Novell networking protocol, IPX, commonly
  3.6208 -  used for local networks of Windows machines.  You need it if you
  3.6209 -  want to access Novell NetWare file or print servers using the Linux
  3.6210 -  Novell client ncpfs (available from
  3.6211 -  <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
  3.6212 -  within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
  3.6213 -  available from <http://www.tldp.org/docs.html#howto>).  In order
  3.6214 -  to do the former, you'll also have to say Y to "NCP file system
  3.6215 -  support", below.
  3.6216 -
  3.6217 -  IPX is similar in scope to IP, while SPX, which runs on top of IPX,
  3.6218 -  is similar to TCP. There is also experimental support for SPX in
  3.6219 -  Linux (see "SPX networking", below).
  3.6220 -
  3.6221 -  To turn your Linux box into a fully featured NetWare file server and
  3.6222 -  IPX router, say Y here and fetch either lwared from
  3.6223 -  <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
  3.6224 -  mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
  3.6225 -  information, read the IPX-HOWTO available from
  3.6226 -  <http://www.tldp.org/docs.html#howto>.
  3.6227 -
  3.6228 -  General information about how to connect Linux, Windows machines and
  3.6229 -  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  3.6230 -
  3.6231 -  The IPX driver would enlarge your kernel by about 16 KB. This driver
  3.6232 -  is also available as a module ( = code which can be inserted in and
  3.6233 -  removed from the running kernel whenever you want).  The module will
  3.6234 -  be called ipx.o.  If you want to compile it as a module, say M here
  3.6235 -  and read <file:Documentation/modules.txt>.  Unless you want to
  3.6236 -  integrate your Linux box with a local Novell network, say N.
  3.6237 -
  3.6238 -Full internal IPX network
  3.6239 -CONFIG_IPX_INTERN
  3.6240 -  Every IPX network has an address that identifies it. Sometimes it is
  3.6241 -  useful to give an IPX "network" address to your Linux box as well
  3.6242 -  (for example if your box is acting as a file server for different
  3.6243 -  IPX networks: it will then be accessible from everywhere using the
  3.6244 -  same address). The way this is done is to create a virtual internal
  3.6245 -  "network" inside your box and to assign an IPX address to this
  3.6246 -  network. Say Y here if you want to do this; read the IPX-HOWTO at
  3.6247 -  <http://www.tldp.org/docs.html#howto> for details.
  3.6248 -
  3.6249 -  The full internal IPX network enables you to allocate sockets on
  3.6250 -  different virtual nodes of the internal network. This is done by
  3.6251 -  evaluating the field sipx_node of the socket address given to the
  3.6252 -  bind call. So applications should always initialize the node field
  3.6253 -  to 0 when binding a socket on the primary network. In this case the
  3.6254 -  socket is assigned the default node that has been given to the
  3.6255 -  kernel when the internal network was created. By enabling the full
  3.6256 -  internal IPX network the cross-forwarding of packets targeted at
  3.6257 -  'special' sockets to sockets listening on the primary network is
  3.6258 -  disabled. This might break existing applications, especially RIP/SAP
  3.6259 -  daemons. A RIP/SAP daemon that works well with the full internal net
  3.6260 -  can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
  3.6261 -
  3.6262 -  If you don't know what you are doing, say N.
  3.6263 -
  3.6264 -#(We're told this will come back someday)
  3.6265 -
  3.6266 -SPX networking
  3.6267 -CONFIG_SPX
  3.6268 -  * Orphaned entry retained 20 April 2001 by Petr Vandrovec     *
  3.6269 -  * If you read this note from the configurator, please contact *
  3.6270 -  * the Configure.help maintainers.                             *
  3.6271 -  The Sequenced Packet eXchange protocol is a transport layer protocol
  3.6272 -  built on top of IPX. It is used in Novell NetWare systems for
  3.6273 -  client-server applications and is similar to TCP (which runs on top
  3.6274 -  of IP).
  3.6275 -
  3.6276 -  Note that Novell NetWare file sharing does not use SPX; it uses a
  3.6277 -  protocol called NCP, for which separate Linux support is available
  3.6278 -  ("NCP file system support" below for the client side, and the user
  3.6279 -  space programs lwared or mars_nwe for the server side).
  3.6280 -
  3.6281 -  Say Y here if you have use for SPX; read the IPX-HOWTO at
  3.6282 -  <http://www.tldp.org/docs.html#howto> for details.
  3.6283 -
  3.6284 -  This driver is also available as a module ( = code which can be
  3.6285 -  inserted in and removed from the running kernel whenever you want).
  3.6286 -  The module will be called af_spx.o. If you want to compile it as a
  3.6287 -  module, say M here and read <file:Documentation/modules.txt>.
  3.6288 -
  3.6289 -DECnet networking
  3.6290 -CONFIG_DECNET
  3.6291 -  The DECnet networking protocol was used in many products made by
  3.6292 -  Digital (now Compaq).  It provides reliable stream and sequenced
  3.6293 -  packet communications over which run a variety of services similar
  3.6294 -  to those which run over TCP/IP.
  3.6295 -
  3.6296 -  To find some tools to use with the kernel layer support, please
  3.6297 -  look at Patrick Caulfield's web site:
  3.6298 -  <http://linux.dreamtime.org/decnet/>.
  3.6299 -
  3.6300 -  More detailed documentation is available in
  3.6301 -  <file:Documentation/networking/decnet.txt>.
  3.6302 -
  3.6303 -  Be sure to say Y to "/proc file system support" and "Sysctl support"
  3.6304 -  below when using DECnet, since you will need sysctl support to aid
  3.6305 -  in configuration at run time.
  3.6306 -
  3.6307 -  The DECnet code is also available as a module ( = code which can be
  3.6308 -  inserted in and removed from the running kernel whenever you want).
  3.6309 -  The module is called decnet.o.
  3.6310 -
  3.6311 -DECnet SIOCFIGCONF support
  3.6312 -CONFIG_DECNET_SIOCGIFCONF
  3.6313 -  This option should only be turned on if you are really sure that
  3.6314 -  you know what you are doing. It can break other applications which
  3.6315 -  use this system call and the proper way to get the information
  3.6316 -  provided by this call is to use rtnetlink.
  3.6317 -
  3.6318 -  If unsure, say N.
  3.6319 -
  3.6320 -DECnet router support
  3.6321 -CONFIG_DECNET_ROUTER
  3.6322 -  Add support for turning your DECnet Endnode into a level 1 or 2
  3.6323 -  router.  This is an unfinished option for developers only.  If you
  3.6324 -  do say Y here, then make sure that you also say Y to "Kernel/User
  3.6325 -  network link driver", "Routing messages" and "Network packet
  3.6326 -  filtering".  The first two are required to allow configuration via
  3.6327 -  rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
  3.6328 -  from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
  3.6329 -  will be required for the forthcoming routing daemon to work.
  3.6330 -
  3.6331 -  See <file:Documentation/networking/decnet.txt> for more information.
  3.6332 -
  3.6333 -Use FWMARK value as DECnet routing key
  3.6334 -CONFIG_DECNET_ROUTE_FWMARK
  3.6335 -  If you say Y here, you will be able to specify different routes for
  3.6336 -  packets with different FWMARK ("firewalling mark") values
  3.6337 -  (see ipchains(8), "-m" argument).
  3.6338 -
  3.6339 -AppleTalk interfaces support
  3.6340 -CONFIG_DEV_APPLETALK
  3.6341 -  AppleTalk is the protocol that Apple computers can use to communicate
  3.6342 -  on a network.  If your Linux box is connected to such a network, and wish
  3.6343 -  to do IP over it, or you have a LocalTalk card and wish to use it to
  3.6344 -  connect to the AppleTalk network, say Y.
  3.6345 -
  3.6346 -AppleTalk protocol support
  3.6347 -CONFIG_ATALK
  3.6348 -  AppleTalk is the protocol that Apple computers can use to communicate
  3.6349 -  on a network.  If your Linux box is connected to such a network and you
  3.6350 -  wish to connect to it, say Y.  You will need to use the netatalk package
  3.6351 -  so that your Linux box can act as a print and file server for Macs as
  3.6352 -  well as access AppleTalk printers.  Check out
  3.6353 -  <http://www.zettabyte.net/netatalk/> on the WWW for details.
  3.6354 -  EtherTalk is the name used for AppleTalk over Ethernet and the
  3.6355 -  cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
  3.6356 -  network using serial links.  EtherTalk and LocalTalk are fully
  3.6357 -  supported by Linux.
  3.6358 -
  3.6359 -  General information about how to connect Linux, Windows machines and
  3.6360 -  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.  The
  3.6361 -  NET-3-HOWTO, available from
  3.6362 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  3.6363 -  information as well.
  3.6364 -
  3.6365 -  This driver is also available as a module ( = code which can be
  3.6366 -  inserted in and removed from the running kernel whenever you want).
  3.6367 -  The module is called appletalk.o.  If you want to compile it as a
  3.6368 -  module, say M here and read <file:Documentation/modules.txt>.  You
  3.6369 -  almost certainly want to compile it as a module so you can restart
  3.6370 -  your AppleTalk stack without rebooting your machine.  I hear that
  3.6371 -  the GNU boycott of Apple is over, so even politically correct people
  3.6372 -  are allowed to say Y here.
  3.6373 -
  3.6374 -AppleTalk-IP driver support
  3.6375 -CONFIG_IPDDP
  3.6376 -  This allows IP networking for users who only have AppleTalk
  3.6377 -  networking available. This feature is experimental. With this
  3.6378 -  driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
  3.6379 -  box is stuck on an AppleTalk only network) or decapsulate (e.g. if
  3.6380 -  you want your Linux box to act as an Internet gateway for a zoo of
  3.6381 -  AppleTalk connected Macs). Please see the file
  3.6382 -  <file:Documentation/networking/ipddp.txt> for more information.
  3.6383 -
  3.6384 -  If you say Y here, the AppleTalk-IP support will be compiled into
  3.6385 -  the kernel. In this case, you can either use encapsulation or
  3.6386 -  decapsulation, but not both. With the following two questions, you
  3.6387 -  decide which one you want.
  3.6388 -
  3.6389 -  If you say M here, the AppleTalk-IP support will be compiled as a
  3.6390 -  module ( = code which can be inserted in and removed from the
  3.6391 -  running kernel whenever you want, read
  3.6392 -  <file:Documentation/modules.txt>).  The module is called ipddp.o.
  3.6393 -  In this case, you will be able to use both encapsulation and
  3.6394 -  decapsulation simultaneously, by loading two copies of the module
  3.6395 -  and specifying different values for the module option ipddp_mode.
  3.6396 -
  3.6397 -IP to AppleTalk-IP Encapsulation support
  3.6398 -CONFIG_IPDDP_ENCAP
  3.6399 -  If you say Y here, the AppleTalk-IP code will be able to encapsulate
  3.6400 -  IP packets inside AppleTalk frames; this is useful if your Linux box
  3.6401 -  is stuck on an AppleTalk network (which hopefully contains a
  3.6402 -  decapsulator somewhere). Please see
  3.6403 -  <file:Documentation/networking/ipddp.txt> for more information. If
  3.6404 -  you said Y to "AppleTalk-IP driver support" above and you say Y
  3.6405 -  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
  3.6406 -  support", below.
  3.6407 -
  3.6408 -AppleTalk-IP to IP Decapsulation support
  3.6409 -CONFIG_IPDDP_DECAP
  3.6410 -  If you say Y here, the AppleTalk-IP code will be able to decapsulate
  3.6411 -  AppleTalk-IP frames to IP packets; this is useful if you want your
  3.6412 -  Linux box to act as an Internet gateway for an AppleTalk network.
  3.6413 -  Please see <file:Documentation/networking/ipddp.txt> for more
  3.6414 -  information.  If you said Y to "AppleTalk-IP driver support" above
  3.6415 -  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
  3.6416 -  Encapsulation support", above.
  3.6417 -
  3.6418 -Apple/Farallon LocalTalk PC card support
  3.6419 -CONFIG_LTPC
  3.6420 -  This allows you to use the AppleTalk PC card to connect to LocalTalk
  3.6421 -  networks. The card is also known as the Farallon PhoneNet PC card.
  3.6422 -  If you are in doubt, this card is the one with the 65C02 chip on it.
  3.6423 -  You also need version 1.3.3 or later of the netatalk package.
  3.6424 -  This driver is experimental, which means that it may not work.
  3.6425 -  See the file <file:Documentation/networking/ltpc.txt>.
  3.6426 -
  3.6427 -  This driver is also available as a module ( = code which can be
  3.6428 -  inserted in and removed from the running kernel whenever you want).
  3.6429 -  If you want to compile it as a module, say M here and read
  3.6430 -  <file:Documentation/modules.txt>. The module will be called
  3.6431 -  ltpc.o
  3.6432 -
  3.6433 -COPS LocalTalk PC card support
  3.6434 -CONFIG_COPS
  3.6435 -  This allows you to use COPS AppleTalk cards to connect to LocalTalk
  3.6436 -  networks. You also need version 1.3.3 or later of the netatalk
  3.6437 -  package. This driver is experimental, which means that it may not
  3.6438 -  work. This driver will only work if you choose "AppleTalk DDP"
  3.6439 -  networking support, above.
  3.6440 -  Please read the file <file:Documentation/networking/cops.txt>.
  3.6441 -
  3.6442 -  This driver is also available as a module ( = code which can be
  3.6443 -  inserted in and removed from the running kernel whenever you want).
  3.6444 -  If you want to compile it as a module, say M here and read
  3.6445 -  <file:Documentation/modules.txt>. The module will be called
  3.6446 -  cops.o
  3.6447 -
  3.6448 -Dayna firmware support
  3.6449 -CONFIG_COPS_DAYNA
  3.6450 -  Support COPS compatible cards with Dayna style firmware (Dayna
  3.6451 -  DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
  3.6452 -  III, Farallon PhoneNET PC II).
  3.6453 -
  3.6454 -Tangent firmware support
  3.6455 -CONFIG_COPS_TANGENT
  3.6456 -  Support COPS compatible cards with Tangent style firmware (Tangent
  3.6457 -  ATB_II, Novell NL-1000, Daystar Digital LT-200.
  3.6458 -
  3.6459 -Amateur Radio support
  3.6460 -CONFIG_HAMRADIO
  3.6461 -  If you want to connect your Linux box to an amateur radio, answer Y
  3.6462 -  here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
  3.6463 -  the AX25-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
  3.6464 -
  3.6465 -  Note that the answer to this question won't directly affect the
  3.6466 -  kernel: saying N will just cause the configurator to skip all
  3.6467 -  the questions about amateur radio.
  3.6468 -
  3.6469 -Amateur Radio AX.25 Level 2 protocol
  3.6470 -CONFIG_AX25
  3.6471 -  This is the protocol used for computer communication over amateur
  3.6472 -  radio. It is either used by itself for point-to-point links, or to
  3.6473 -  carry other protocols such as tcp/ip. To use it, you need a device
  3.6474 -  that connects your Linux box to your amateur radio. You can either
  3.6475 -  use a low speed TNC (a Terminal Node Controller acts as a kind of
  3.6476 -  modem connecting your computer's serial port to your radio's
  3.6477 -  microphone input and speaker output) supporting the KISS protocol or
  3.6478 -  one of the various SCC cards that are supported by the generic Z8530
  3.6479 -  or the DMA SCC driver. Another option are the Baycom modem serial
  3.6480 -  and parallel port hacks or the sound card modem (supported by their
  3.6481 -  own drivers). If you say Y here, you also have to say Y to one of
  3.6482 -  those drivers.
  3.6483 -
  3.6484 -  Information about where to get supporting software for Linux amateur
  3.6485 -  radio as well as information about how to configure an AX.25 port is
  3.6486 -  contained in the AX25-HOWTO, available from
  3.6487 -  <http://www.tldp.org/docs.html#howto>. You might also want to
  3.6488 -  check out the file <file:Documentation/networking/ax25.txt> in the
  3.6489 -  kernel source. More information about digital amateur radio in
  3.6490 -  general is on the WWW at
  3.6491 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  3.6492 -
  3.6493 -  This driver is also available as a module ( = code which can be
  3.6494 -  inserted in and removed from the running kernel whenever you want).
  3.6495 -  The module will be called ax25.o. If you want to compile it as a
  3.6496 -  module, say M here and read <file:Documentation/modules.txt>.
  3.6497 -
  3.6498 -AX.25 DAMA Slave support
  3.6499 -CONFIG_AX25_DAMA_SLAVE
  3.6500 -  DAMA is a mechanism to prevent collisions when doing AX.25
  3.6501 -  networking. A DAMA server (called "master") accepts incoming traffic
  3.6502 -  from clients (called "slaves") and redistributes it to other slaves.
  3.6503 -  If you say Y here, your Linux box will act as a DAMA slave; this is
  3.6504 -  transparent in that you don't have to do any special DAMA
  3.6505 -  configuration. (Linux cannot yet act as a DAMA server.) If unsure,
  3.6506 -  say N.
  3.6507 -
  3.6508 -AX.25 DAMA Master support
  3.6509 -CONFIG_AX25_DAMA_MASTER
  3.6510 -  DAMA is a mechanism to prevent collisions when doing AX.25
  3.6511 -  networking. A DAMA server (called "master") accepts incoming traffic
  3.6512 -  from clients (called "slaves") and redistributes it to other
  3.6513 -  slaves. If you say Y here, your Linux box will act as a DAMA server.
  3.6514 -  If unsure, say N.
  3.6515 -
  3.6516 -Amateur Radio NET/ROM support
  3.6517 -CONFIG_NETROM
  3.6518 -  NET/ROM is a network layer protocol on top of AX.25 useful for
  3.6519 -  routing.
  3.6520 -
  3.6521 -  A comprehensive listing of all the software for Linux amateur radio
  3.6522 -  users as well as information about how to configure an AX.25 port is
  3.6523 -  contained in the AX25-HOWTO, available from
  3.6524 -  <http://www.tldp.org/docs.html#howto>. You also might want to
  3.6525 -  check out the file <file:Documentation/networking/ax25.txt>. More
  3.6526 -  information about digital amateur radio in general is on the WWW at
  3.6527 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  3.6528 -
  3.6529 -  This driver is also available as a module ( = code which can be
  3.6530 -  inserted in and removed from the running kernel whenever you want).
  3.6531 -  The module will be called netrom.o. If you want to compile it as a
  3.6532 -  module, say M here and read <file:Documentation/modules.txt>.
  3.6533 -
  3.6534 -Amateur Radio X.25 PLP (Rose)
  3.6535 -CONFIG_ROSE
  3.6536 -  The Packet Layer Protocol (PLP) is a way to route packets over X.25
  3.6537 -  connections in general and amateur radio AX.25 connections in
  3.6538 -  particular, essentially an alternative to NET/ROM.
  3.6539 -
  3.6540 -  A comprehensive listing of all the software for Linux amateur radio
  3.6541 -  users as well as information about how to configure an AX.25 port is
  3.6542 -  contained in the AX25-HOWTO, available from
  3.6543 -  <http://www.tldp.org/docs.html#howto>.  You also might want to
  3.6544 -  check out the file <file:Documentation/networking/ax25.txt>. More
  3.6545 -  information about digital amateur radio in general is on the WWW at
  3.6546 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  3.6547 -
  3.6548 -  This driver is also available as a module ( = code which can be
  3.6549 -  inserted in and removed from the running kernel whenever you want).
  3.6550 -  The module will be called rose.o. If you want to compile it as a
  3.6551 -  module, say M here and read <file:Documentation/modules.txt>.
  3.6552 -
  3.6553 -Serial port KISS driver for AX.25
  3.6554 -CONFIG_MKISS
  3.6555 -  KISS is a protocol used for the exchange of data between a computer
  3.6556 -  and a Terminal Node Controller (a small embedded system commonly
  3.6557 -  used for networking over AX.25 amateur radio connections; it
  3.6558 -  connects the computer's serial port with the radio's microphone
  3.6559 -  input and speaker output).
  3.6560 -
  3.6561 -  Although KISS is less advanced than the 6pack protocol, it has
  3.6562 -  the advantage that it is already supported by most modern TNCs
  3.6563 -  without the need for a firmware upgrade.
  3.6564 -
  3.6565 -  If you want to compile this driver as a module ( = code which can be
  3.6566 -  inserted in and removed from the running kernel whenever you want),
  3.6567 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6568 -  will be called mkiss.o.
  3.6569 -
  3.6570 -Serial port 6PACK driver for AX.25
  3.6571 -CONFIG_6PACK
  3.6572 -  6pack is a transmission protocol for the data exchange between your
  3.6573 -  PC and your TNC (the Terminal Node Controller acts as a kind of
  3.6574 -  modem connecting your computer's serial port to your radio's
  3.6575 -  microphone input and speaker output). This protocol can be used as
  3.6576 -  an alternative to KISS for networking over AX.25 amateur radio
  3.6577 -  connections, but it has some extended functionality.
  3.6578 -
  3.6579 -  Note that this driver is still experimental and might cause
  3.6580 -  problems. For details about the features and the usage of the
  3.6581 -  driver, read <file:Documentation/networking/6pack.txt>.
  3.6582 -
  3.6583 -  If you want to compile this driver as a module ( = code which can be
  3.6584 -  inserted in and removed from the running kernel whenever you want),
  3.6585 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6586 -  will be called 6pack.o.
  3.6587 -
  3.6588 -BPQ Ethernet driver
  3.6589 -CONFIG_BPQETHER
  3.6590 -  AX.25 is the protocol used for computer communication over amateur
  3.6591 -  radio. If you say Y here, you will be able to send and receive AX.25
  3.6592 -  traffic over Ethernet (also called "BPQ AX.25"), which could be
  3.6593 -  useful if some other computer on your local network has a direct
  3.6594 -  amateur radio connection.
  3.6595 -
  3.6596 -  If you want to compile the driver as a module ( = code which can be
  3.6597 -  inserted in and removed from the running kernel whenever you want),
  3.6598 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6599 -  will be called bpqether.o.
  3.6600 -
  3.6601 -High-speed (DMA) SCC driver for AX.25
  3.6602 -CONFIG_DMASCC
  3.6603 -  This is a driver for high-speed SCC boards, i.e. those supporting
  3.6604 -  DMA on one port. You usually use those boards to connect your
  3.6605 -  computer to an amateur radio modem (such as the WA4DSY 56kbps
  3.6606 -  modem), in order to send and receive AX.25 packet radio network
  3.6607 -  traffic.
  3.6608 -
  3.6609 -  Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
  3.6610 -  PackeTwin, and S5SCC/DMA boards. They are detected automatically.
  3.6611 -  If you have one of these cards, say Y here and read the AX25-HOWTO,
  3.6612 -  available from <http://www.tldp.org/docs.html#howto>.
  3.6613 -
  3.6614 -  This driver can operate multiple boards simultaneously. If you
  3.6615 -  compile it as a module (by saying M instead of Y), it will be called
  3.6616 -  dmascc.o. If you don't pass any parameter to the driver, all
  3.6617 -  possible I/O addresses are probed. This could irritate other devices
  3.6618 -  that are currently not in use. You may specify the list of addresses
  3.6619 -  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
  3.6620 -  kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
  3.6621 -  network interfaces will be called dmascc0 and dmascc1 for the board
  3.6622 -  detected first, dmascc2 and dmascc3 for the second one, and so on.
  3.6623 -
  3.6624 -  Before you configure each interface with ifconfig, you MUST set
  3.6625 -  certain parameters, such as channel access timing, clock mode, and
  3.6626 -  DMA channel. This is accomplished with a small utility program,
  3.6627 -  dmascc_cfg, available at
  3.6628 -  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
  3.6629 -  at least version 1.27 of dmascc_cfg, as older versions will not
  3.6630 -  work with the current driver.
  3.6631 -
  3.6632 -Z8530 SCC driver for AX.25
  3.6633 -CONFIG_SCC
  3.6634 -  These cards are used to connect your Linux box to an amateur radio
  3.6635 -  in order to communicate with other computers. If you want to use
  3.6636 -  this, read <file:Documentation/networking/z8530drv.txt> and the
  3.6637 -  AX25-HOWTO, available from
  3.6638 -  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  3.6639 -  to "Amateur Radio AX.25 Level 2" support.
  3.6640 -
  3.6641 -  If you want to compile this as a module ( = code which can be
  3.6642 -  inserted in and removed from the running kernel whenever you want),
  3.6643 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6644 -  will be called scc.o.
  3.6645 -
  3.6646 -Support for TRX that feedback the tx signal to rx
  3.6647 -CONFIG_SCC_TRXECHO
  3.6648 -  Some transmitters feed the transmitted signal back to the receive
  3.6649 -  line.  Say Y here to foil this by explicitly disabling the receiver
  3.6650 -  during data transmission.  If in doubt, say Y.
  3.6651 -
  3.6652 -Additional delay for PA0HZP OptoSCC compatible boards
  3.6653 -CONFIG_SCC_DELAY
  3.6654 -  Say Y here if you experience problems with the SCC driver not
  3.6655 -  working properly; please read
  3.6656 -  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
  3.6657 -  say N.
  3.6658 -
  3.6659 -YAM driver for AX.25
  3.6660 -CONFIG_YAM
  3.6661 -  The YAM is a modem for packet radio which connects to the serial
  3.6662 -  port and includes some of the functions of a Terminal Node
  3.6663 -  Controller. If you have one of those, say Y here.
  3.6664 -
  3.6665 -  If you want to compile the driver as a module ( = code which can be
  3.6666 -  inserted in and removed from the running kernel whenever you want),
  3.6667 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6668 -  will be called yam.o.
  3.6669 -
  3.6670 -BAYCOM picpar and par96 driver for AX.25
  3.6671 -CONFIG_BAYCOM_PAR
  3.6672 -  This is a driver for Baycom style simple amateur radio modems that
  3.6673 -  connect to a parallel interface. The driver supports the picpar and
  3.6674 -  par96 designs. To configure the driver, use the sethdlc utility
  3.6675 -  available in the standard ax25 utilities package. For information on
  3.6676 -  the modems, see <http://www.baycom.de/> and the file
  3.6677 -  <file:Documentation/networking/baycom.txt>.
  3.6678 -
  3.6679 -  If you want to compile this driver as a module ( = code which can be
  3.6680 -  inserted in and removed from the running kernel whenever you want),
  3.6681 -  say M here and read <file:Documentation/modules.txt>.  This is
  3.6682 -  recommended.  The module will be called baycom_par.o.
  3.6683 -
  3.6684 -BAYCOM EPP driver for AX.25
  3.6685 -CONFIG_BAYCOM_EPP
  3.6686 -  This is a driver for Baycom style simple amateur radio modems that
  3.6687 -  connect to a parallel interface. The driver supports the EPP
  3.6688 -  designs. To configure the driver, use the sethdlc utility available
  3.6689 -  in the standard ax25 utilities package. For information on the
  3.6690 -  modems, see <http://www.baycom.de/> and the file
  3.6691 -  <file:Documentation/networking/baycom.txt>.
  3.6692 -
  3.6693 -  If you want to compile this driver as a module ( = code which can be
  3.6694 -  inserted in and removed from the running kernel whenever you want),
  3.6695 -  say M here and read <file:Documentation/modules.txt>.  This is
  3.6696 -  recommended.  The module will be called baycom_par.o.
  3.6697 -
  3.6698 -BAYCOM ser12 full-duplex driver for AX.25
  3.6699 -CONFIG_BAYCOM_SER_FDX
  3.6700 -  This is one of two drivers for Baycom style simple amateur radio
  3.6701 -  modems that connect to a serial interface. The driver supports the
  3.6702 -  ser12 design in full-duplex mode. In addition, it allows the
  3.6703 -  baudrate to be set between 300 and 4800 baud (however not all modems
  3.6704 -  support all baudrates). This is the preferred driver. The next
  3.6705 -  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
  3.6706 -  driver and still provided in case this driver does not work with
  3.6707 -  your serial interface chip. To configure the driver, use the sethdlc
  3.6708 -  utility available in the standard ax25 utilities package. For
  3.6709 -  information on the modems, see <http://www.baycom.de/> and
  3.6710 -  <file:Documentation/networking/baycom.txt>.
  3.6711 -
  3.6712 -  If you want to compile this driver as a module ( = code which can be
  3.6713 -  inserted in and removed from the running kernel whenever you want),
  3.6714 -  say M here and read <file:Documentation/modules.txt>.  This is
  3.6715 -  recommended.  The module will be called baycom_ser_fdx.o.
  3.6716 -
  3.6717 -BAYCOM ser12 half-duplex driver for AX.25
  3.6718 -CONFIG_BAYCOM_SER_HDX
  3.6719 -  This is one of two drivers for Baycom style simple amateur radio
  3.6720 -  modems that connect to a serial interface. The driver supports the
  3.6721 -  ser12 design in full-duplex mode. This is the old driver.  It is
  3.6722 -  still provided in case your serial interface chip does not work with
  3.6723 -  the full-duplex driver. This driver is depreciated.  To configure
  3.6724 -  the driver, use the sethdlc utility available in the standard ax25
  3.6725 -  utilities package. For information on the modems, see
  3.6726 -  <http://www.baycom.de/> and
  3.6727 -  <file:Documentation/networking/baycom.txt>.
  3.6728 -
  3.6729 -  If you want to compile this driver as a module ( = code which can be
  3.6730 -  inserted in and removed from the running kernel whenever you want),
  3.6731 -  say M here and read <file:Documentation/modules.txt>.  This is
  3.6732 -  recommended.  The module will be called baycom_ser_hdx.o.
  3.6733 -
  3.6734 -Sound card modem driver for AX.25
  3.6735 -CONFIG_SOUNDMODEM
  3.6736 -  This experimental driver allows a standard Sound Blaster or
  3.6737 -  WindowsSoundSystem compatible sound card to be used as a packet
  3.6738 -  radio modem (NOT as a telephone modem!), to send digital traffic
  3.6739 -  over amateur radio.
  3.6740 -
  3.6741 -  To configure the driver, use the sethdlc, smdiag and smmixer
  3.6742 -  utilities available in the standard ax25 utilities package. For
  3.6743 -  information on how to key the transmitter, see
  3.6744 -  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
  3.6745 -  <file:Documentation/networking/soundmodem.txt>.
  3.6746 -
  3.6747 -  If you want to compile this driver as a module ( = code which can be
  3.6748 -  inserted in and removed from the running kernel whenever you want),
  3.6749 -  say M here and read <file:Documentation/modules.txt>.  This is
  3.6750 -  recommended.  The module will be called soundmodem.o.
  3.6751 -
  3.6752 -Sound card modem support for Sound Blaster and compatible cards
  3.6753 -CONFIG_SOUNDMODEM_SBC
  3.6754 -  This option enables the soundmodem driver to use Sound Blaster and
  3.6755 -  compatible cards. If you have a dual mode card (i.e. a WSS cards
  3.6756 -  with a Sound Blaster emulation) you should say N here and Y to
  3.6757 -  "Sound card modem support for WSS and Crystal cards", below, because
  3.6758 -  this usually results in better performance. This option also
  3.6759 -  supports SB16/32/64 in full-duplex mode.
  3.6760 -
  3.6761 -Sound card modem support for WSS and Crystal cards
  3.6762 -CONFIG_SOUNDMODEM_WSS
  3.6763 -  This option enables the soundmodem driver to use WindowsSoundSystem
  3.6764 -  compatible cards. These cards feature a codec chip from either
  3.6765 -  Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
  3.6766 -  Semiconductors (such as CS4248, CS423x). This option also supports
  3.6767 -  the WSS full-duplex operation which currently works with Crystal
  3.6768 -  CS423x chips. If you don't need full-duplex operation, do not enable
  3.6769 -  it to save performance.
  3.6770 -
  3.6771 -Sound card modem support for 1200 baud AFSK modulation
  3.6772 -CONFIG_SOUNDMODEM_AFSK1200
  3.6773 -  This option enables the soundmodem driver 1200 baud AFSK modem,
  3.6774 -  compatible to popular modems using TCM3105 or AM7911. The
  3.6775 -  demodulator requires about 12% of the CPU power of a Pentium 75 CPU
  3.6776 -  per channel.
  3.6777 -
  3.6778 -Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
  3.6779 -CONFIG_SOUNDMODEM_AFSK2400_7
  3.6780 -  This option enables the soundmodem driver 2400 baud AFSK modem,
  3.6781 -  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
  3.6782 -  crystal. Note that the availability of this driver does _not_ imply
  3.6783 -  that I recommend building such links. It is only here since users
  3.6784 -  especially in eastern Europe have asked me to do so. In fact this
  3.6785 -  modulation scheme has many disadvantages, mainly its incompatibility
  3.6786 -  with many transceiver designs and the fact that the TCM3105 (if
  3.6787 -  used) is operated widely outside its specifications.
  3.6788 -
  3.6789 -Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
  3.6790 -CONFIG_SOUNDMODEM_AFSK2400_8
  3.6791 -  This option enables the soundmodem driver 2400 baud AFSK modem,
  3.6792 -  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
  3.6793 -  Note that the availability of this driver does _not_ imply that I
  3.6794 -  recommend building such links. It is only here since users
  3.6795 -  especially in eastern Europe have asked me to do so. In fact this
  3.6796 -  modulation scheme has many disadvantages, mainly its incompatibility
  3.6797 -  with many transceiver designs and the fact that the TCM3105 (if
  3.6798 -  used) is operated widely outside its specifications.
  3.6799 -
  3.6800 -Sound card modem support for 2666 baud AFSK modulation
  3.6801 -CONFIG_SOUNDMODEM_AFSK2666
  3.6802 -  This option enables the soundmodem driver 2666 baud AFSK modem.
  3.6803 -  This modem is experimental, and not compatible to anything
  3.6804 -  else I know of.
  3.6805 -
  3.6806 -Sound card modem support for 4800 baud 8PSK modulation
  3.6807 -CONFIG_SOUNDMODEM_PSK4800
  3.6808 -  This option enables the soundmodem driver 4800 baud 8PSK modem.
  3.6809 -  This modem is experimental, and not compatible to anything
  3.6810 -  else I know of.
  3.6811 -
  3.6812 -Sound card modem support for 4800 baud HAPN-1 modulation
  3.6813 -CONFIG_SOUNDMODEM_HAPN4800
  3.6814 -  This option enables the soundmodem driver 4800 baud HAPN-1
  3.6815 -  compatible modem. This modulation seems to be widely used 'down
  3.6816 -  under' and in the Netherlands. Here, nobody uses it, so I could not
  3.6817 -  test if it works. It is compatible to itself, however :-)
  3.6818 -
  3.6819 -Sound card modem support for 9600 baud FSK G3RUH modulation
  3.6820 -CONFIG_SOUNDMODEM_FSK9600
  3.6821 -  This option enables the soundmodem driver 9600 baud FSK modem,
  3.6822 -  compatible to the G3RUH standard. The demodulator requires about 4%
  3.6823 -  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
  3.6824 -  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
  3.6825 -  can only use one protocol at a time, depending on what the other end
  3.6826 -  can understand).
  3.6827 -
  3.6828 -CCITT X.25 Packet Layer
  3.6829 -CONFIG_X25
  3.6830 -  X.25 is a set of standardized network protocols, similar in scope to
  3.6831 -  frame relay; the one physical line from your box to the X.25 network
  3.6832 -  entry point can carry several logical point-to-point connections
  3.6833 -  (called "virtual circuits") to other computers connected to the X.25
  3.6834 -  network. Governments, banks, and other organizations tend to use it
  3.6835 -  to connect to each other or to form Wide Area Networks (WANs). Many
  3.6836 -  countries have public X.25 networks. X.25 consists of two
  3.6837 -  protocols: the higher level Packet Layer Protocol (PLP) (say Y here
  3.6838 -  if you want that) and the lower level data link layer protocol LAPB
  3.6839 -  (say Y to "LAPB Data Link Driver" below if you want that).
  3.6840 -
  3.6841 -  You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
  3.6842 -  <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
  3.6843 -  Information about X.25 for Linux is contained in the files
  3.6844 -  <file:Documentation/networking/x25.txt> and
  3.6845 -  <file:Documentation/networking/x25-iface.txt>.
  3.6846 -
  3.6847 -  One connects to an X.25 network either with a dedicated network card
  3.6848 -  using the X.21 protocol (not yet supported by Linux) or one can do
  3.6849 -  X.25 over a standard telephone line using an ordinary modem (say Y
  3.6850 -  to "X.25 async driver" below) or over Ethernet using an ordinary
  3.6851 -  Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
  3.6852 -  LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
  3.6853 -  and "LAPB over Ethernet driver" below).
  3.6854 -
  3.6855 -  If you want to compile this driver as a module ( = code which can be
  3.6856 -  inserted in and removed from the running kernel whenever you want),
  3.6857 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6858 -  will be called x25.o. If unsure, say N.
  3.6859 -
  3.6860 -LAPB Data Link Driver
  3.6861 -CONFIG_LAPB
  3.6862 -  Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
  3.6863 -  the lower) part of the X.25 protocol. It offers a reliable
  3.6864 -  connection service to exchange data frames with one other host, and
  3.6865 -  it is used to transport higher level protocols (mostly X.25 Packet
  3.6866 -  Layer, the higher part of X.25, but others are possible as well).
  3.6867 -  Usually, LAPB is used with specialized X.21 network cards, but Linux
  3.6868 -  currently supports LAPB only over Ethernet connections. If you want
  3.6869 -  to use LAPB connections over Ethernet, say Y here and to "LAPB over
  3.6870 -  Ethernet driver" below. Read
  3.6871 -  <file:Documentation/networking/lapb-module.txt> for technical
  3.6872 -  details.
  3.6873 -
  3.6874 -  If you want to compile this driver as a module though ( = code which
  3.6875 -  can be inserted in and removed from the running kernel whenever you
  3.6876 -  want), say M here and read <file:Documentation/modules.txt>.  The
  3.6877 -  module will be called lapb.o.  If unsure, say N.
  3.6878 -
  3.6879 -802.2 LLC
  3.6880 -CONFIG_LLC
  3.6881 -  This is a Logical Link Layer protocol used for X.25 connections over
  3.6882 -  Ethernet, using ordinary Ethernet cards.
  3.6883 -
  3.6884 -Frame Diverter
  3.6885 -CONFIG_NET_DIVERT
  3.6886 -  The Frame Diverter allows you to divert packets from the
  3.6887 -  network, that are not aimed at the interface receiving it (in
  3.6888 -  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
  3.6889 -  with the Frames Diverter on, can do some *really* transparent www
  3.6890 -  caching using a Squid proxy for example.
  3.6891 -
  3.6892 -  This is very useful when you don't want to change your router's
  3.6893 -  config (or if you simply don't have access to it).
  3.6894 -
  3.6895 -  The other possible usages of diverting Ethernet Frames are
  3.6896 -  numberous:
  3.6897 -   - reroute smtp traffic to another interface
  3.6898 -   - traffic-shape certain network streams
  3.6899 -   - transparently proxy smtp connections
  3.6900 -   - etc...
  3.6901 -
  3.6902 -  For more informations, please refer to:
  3.6903 -    <http://diverter.sourceforge.net/>
  3.6904 -    <http://perso.wanadoo.fr/magpie/EtherDivert.html>
  3.6905 -
  3.6906 -  If unsure, say N.
  3.6907 -
  3.6908 -802.1d Ethernet Bridging
  3.6909 -CONFIG_BRIDGE
  3.6910 -  If you say Y here, then your Linux box will be able to act as an
  3.6911 -  Ethernet bridge, which means that the different Ethernet segments it
  3.6912 -  is connected to will appear as one Ethernet to the participants.
  3.6913 -  Several such bridges can work together to create even larger
  3.6914 -  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  3.6915 -  As this is a standard, Linux bridges will cooperate properly with
  3.6916 -  other third party bridge products.
  3.6917 -
  3.6918 -  In order to use the Ethernet bridge, you'll need the bridge
  3.6919 -  configuration tools; see <file:Documentation/networking/bridge.txt>
  3.6920 -  for location. Please read the Bridge mini-HOWTO for more
  3.6921 -  information.
  3.6922 -
  3.6923 -  Note that if your box acts as a bridge, it probably contains several
  3.6924 -  Ethernet devices, but the kernel is not able to recognize more than
  3.6925 -  one at boot time without help; for details read the Ethernet-HOWTO,
  3.6926 -  available from in <http://www.tldp.org/docs.html#howto>.
  3.6927 -
  3.6928 -  If you want to compile this code as a module ( = code which can be
  3.6929 -  inserted in and removed from the running kernel whenever you want),
  3.6930 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.6931 -  will be called bridge.o.
  3.6932 -
  3.6933 -  If unsure, say N.
  3.6934 -
  3.6935 -Packet socket
  3.6936 -CONFIG_PACKET
  3.6937 -  The Packet protocol is used by applications which communicate
  3.6938 -  directly with network devices without an intermediate network
  3.6939 -  protocol implemented in the kernel, e.g. tcpdump.  If you want them
  3.6940 -  to work, choose Y.
  3.6941 -
  3.6942 -  This driver is also available as a module called af_packet.o ( =
  3.6943 -  code which can be inserted in and removed from the running kernel
  3.6944 -  whenever you want).  If you want to compile it as a module, say M
  3.6945 -  here and read <file:Documentation/modules.txt>; if you use modprobe
  3.6946 -  or kmod, you may also want to add "alias net-pf-17 af_packet" to
  3.6947 -  /etc/modules.conf.
  3.6948 -
  3.6949 -  If unsure, say Y.
  3.6950 -
  3.6951 -Packet socket: mmapped IO
  3.6952 -CONFIG_PACKET_MMAP
  3.6953 -  If you say Y here, the Packet protocol driver will use an IO
  3.6954 -  mechanism that results in faster communication.
  3.6955 -
  3.6956 -  If unsure, say N.
  3.6957 -
  3.6958 -Netlink device emulation
  3.6959 -CONFIG_NETLINK_DEV
  3.6960 -  This option will be removed soon. Any programs that want to use
  3.6961 -  character special nodes like /dev/tap0 or /dev/route (all with major
  3.6962 -  number 36) need this option, and need to be rewritten soon to use
  3.6963 -  the real netlink socket.
  3.6964 -  This is a backward compatibility option, choose Y for now.
  3.6965 -
  3.6966 -  This driver is also available as a module ( = code which can be
  3.6967 -  inserted in and removed from the running kernel whenever you want).
  3.6968 -  If you want to compile it as a module, say M here and read
  3.6969 -  <file:Documentation/modules.txt>. The module will be called
  3.6970 -  netlink_dev.o
  3.6971 -
  3.6972 -Asynchronous Transfer Mode (ATM)
  3.6973 -CONFIG_ATM
  3.6974 -  ATM is a high-speed networking technology for Local Area Networks
  3.6975 -  and Wide Area Networks.  It uses a fixed packet size and is
  3.6976 -  connection oriented, allowing for the negotiation of minimum
  3.6977 -  bandwidth requirements.
  3.6978 -
  3.6979 -  In order to participate in an ATM network, your Linux box needs an
  3.6980 -  ATM networking card. If you have that, say Y here and to the driver
  3.6981 -  of your ATM card below.
  3.6982 -
  3.6983 -  Note that you need a set of user-space programs to actually make use
  3.6984 -  of ATM.  See the file <file:Documentation/networking/atm.txt> for
  3.6985 -  further details.
  3.6986 -
  3.6987 -Classical IP over ATM
  3.6988 -CONFIG_ATM_CLIP
  3.6989 -  Classical IP over ATM for PVCs and SVCs, supporting InARP and
  3.6990 -  ATMARP. If you want to communication with other IP hosts on your ATM
  3.6991 -  network, you will typically either say Y here or to "LAN Emulation
  3.6992 -  (LANE)" below.
  3.6993 -
  3.6994 -Do NOT send ICMP if no neighbour
  3.6995 -CONFIG_ATM_CLIP_NO_ICMP
  3.6996 -  Normally, an "ICMP host unreachable" message is sent if a neighbour
  3.6997 -  cannot be reached because there is no VC to it in the kernel's
  3.6998 -  ATMARP table. This may cause problems when ATMARP table entries are
  3.6999 -  briefly removed during revalidation. If you say Y here, packets to
  3.7000 -  such neighbours are silently discarded instead.
  3.7001 -
  3.7002 -RFC1483/2684 Bridged protocols
  3.7003 -CONFIG_ATM_BR2684
  3.7004 -  ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
  3.7005 -  This device will act like an ethernet from the kernels point of view,
  3.7006 -  with the traffic being carried by ATM PVCs (currently 1 PVC/device).
  3.7007 -  This is sometimes used over DSL lines.  If in doubt, say N.
  3.7008 -
  3.7009 -Per-VC IP filter kludge
  3.7010 -CONFIG_ATM_BR2684_IPFILTER
  3.7011 -  This is an experimental mechanism for users who need to terminating a
  3.7012 -  large number of IP-only vcc's.  Do not enable this unless you are sure
  3.7013 -  you know what you are doing.
  3.7014 -
  3.7015 -LAN Emulation (LANE) support
  3.7016 -CONFIG_ATM_LANE
  3.7017 -  LAN Emulation emulates services of existing LANs across an ATM
  3.7018 -  network. Besides operating as a normal ATM end station client, Linux
  3.7019 -  LANE client can also act as an proxy client bridging packets between
  3.7020 -  ELAN and Ethernet segments. You need LANE if you want to try MPOA.
  3.7021 -
  3.7022 -Multi-Protocol Over ATM (MPOA) support
  3.7023 -CONFIG_ATM_MPOA
  3.7024 -  Multi-Protocol Over ATM allows ATM edge devices such as routers,
  3.7025 -  bridges and ATM attached hosts establish direct ATM VCs across
  3.7026 -  subnetwork boundaries. These shortcut connections bypass routers
  3.7027 -  enhancing overall network performance.
  3.7028 -
  3.7029 -ATM over TCP
  3.7030 -CONFIG_ATM_TCP
  3.7031 -  ATM over TCP driver. Useful mainly for development and for
  3.7032 -  experiments. If unsure, say N.
  3.7033 -
  3.7034 -Efficient Networks ENI155P
  3.7035 -CONFIG_ATM_ENI
  3.7036 -  Driver for the Efficient Networks ENI155p series and SMC ATM
  3.7037 -  Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
  3.7038 -  2MB on-board RAM (Efficient calls them "C" and "S", respectively),
  3.7039 -  and the FPGA and the ASIC Tonga versions of the board are supported.
  3.7040 -  The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
  3.7041 -  adapters.
  3.7042 -
  3.7043 -  This driver is also available as a module.  If you want to compile
  3.7044 -  it as a module, say M here and read
  3.7045 -  <file:Documentation/modules.txt>.  The module will be called eni.o.
  3.7046 -
  3.7047 -Enable extended debugging
  3.7048 -CONFIG_ATM_ENI_DEBUG
  3.7049 -  Extended debugging records various events and displays that list
  3.7050 -  when an inconsistency is detected. This mechanism is faster than
  3.7051 -  generally using printks, but still has some impact on performance.
  3.7052 -  Note that extended debugging may create certain race conditions
  3.7053 -  itself. Enable this ONLY if you suspect problems with the driver.
  3.7054 -
  3.7055 -Fine-tune burst settings
  3.7056 -CONFIG_ATM_ENI_TUNE_BURST
  3.7057 -  In order to obtain good throughput, the ENI NIC can transfer
  3.7058 -  multiple words of data per PCI bus access cycle. Such a multi-word
  3.7059 -  transfer is called a burst.
  3.7060 -
  3.7061 -  The default settings for the burst sizes are suitable for most PCI
  3.7062 -  chipsets. However, in some cases, large bursts may overrun buffers
  3.7063 -  in the PCI chipset and cause data corruption. In such cases, large
  3.7064 -  bursts must be disabled and only (slower) small bursts can be used.
  3.7065 -  The burst sizes can be set independently in the send (TX) and
  3.7066 -  receive (RX) direction.
  3.7067 -
  3.7068 -  Note that enabling many different burst sizes in the same direction
  3.7069 -  may increase the cost of setting up a transfer such that the
  3.7070 -  resulting throughput is lower than when using only the largest
  3.7071 -  available burst size.
  3.7072 -
  3.7073 -  Also, sometimes larger bursts lead to lower throughput, e.g. on an
  3.7074 -  Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
  3.7075 -  when going from 8W to 16W bursts.
  3.7076 -
  3.7077 -Enable 16W TX bursts (discouraged)
  3.7078 -CONFIG_ATM_ENI_BURST_TX_16W
  3.7079 -  Burst sixteen words at once in the send direction. This may work
  3.7080 -  with recent PCI chipsets, but is known to fail with older chipsets.
  3.7081 -
  3.7082 -Enable 8W TX bursts (recommended)
  3.7083 -CONFIG_ATM_ENI_BURST_TX_8W
  3.7084 -  Burst eight words at once in the send direction. This is the default
  3.7085 -  setting.
  3.7086 -
  3.7087 -Enable 4W TX bursts (optional)
  3.7088 -CONFIG_ATM_ENI_BURST_TX_4W
  3.7089 -  Burst four words at once in the send direction. You may want to try
  3.7090 -  this if you have disabled 8W bursts. Enabling 4W if 8W is also set
  3.7091 -  may or may not improve throughput.
  3.7092 -
  3.7093 -Enable 2W TX bursts (optional)
  3.7094 -CONFIG_ATM_ENI_BURST_TX_2W
  3.7095 -  Burst two words at once in the send direction. You may want to try
  3.7096 -  this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
  3.7097 -  are also set may or may not improve throughput.
  3.7098 -
  3.7099 -Enable 16W RX bursts (discouraged)
  3.7100 -CONFIG_ATM_ENI_BURST_RX_16W
  3.7101 -  Burst sixteen words at once in the receive direction. This may work
  3.7102 -  with recent PCI chipsets, but is known to fail with older chipsets.
  3.7103 -
  3.7104 -Enable 8W RX bursts (discouraged)
  3.7105 -CONFIG_ATM_ENI_BURST_RX_8W
  3.7106 -  Burst eight words at once in the receive direction. This may work
  3.7107 -  with recent PCI chipsets, but is known to fail with older chipsets,
  3.7108 -  such as the Intel Neptune series.
  3.7109 -
  3.7110 -Enable 4W RX bursts (recommended)
  3.7111 -CONFIG_ATM_ENI_BURST_RX_4W
  3.7112 -  Burst four words at once in the receive direction. This is the
  3.7113 -  default setting. Enabling 4W if 8W is also set may or may not
  3.7114 -  improve throughput.
  3.7115 -
  3.7116 -Enable 2W RX bursts (optional)
  3.7117 -CONFIG_ATM_ENI_BURST_RX_2W
  3.7118 -  Burst two words at once in the receive direction. You may want to
  3.7119 -  try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
  3.7120 -  8W are also set may or may not improve throughput.
  3.7121 -
  3.7122 -ZeitNet ZN1221/ZN1225
  3.7123 -CONFIG_ATM_ZATM
  3.7124 -  Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
  3.7125 -  adapters.
  3.7126 -
  3.7127 -  This driver is also available as a module.  If you want to compile
  3.7128 -  it as a module, say M here and read
  3.7129 -  <file:Documentation/modules.txt>.  The module will be called zatm.o.
  3.7130 -
  3.7131 -Enable extended debugging
  3.7132 -CONFIG_ATM_ZATM_DEBUG
  3.7133 -  Extended debugging records various events and displays that list
  3.7134 -  when an inconsistency is detected. This mechanism is faster than
  3.7135 -  generally using printks, but still has some impact on performance.
  3.7136 -  Note that extended debugging may create certain race conditions
  3.7137 -  itself. Enable this ONLY if you suspect problems with the driver.
  3.7138 -
  3.7139 -Fujitsu FireStream (FS50/FS155)
  3.7140 -CONFIG_ATM_FIRESTREAM
  3.7141 -  Driver for the Fujitsu FireStream 155 (MB86697) and
  3.7142 -  FireStream 50 (MB86695) ATM PCI chips.
  3.7143 -
  3.7144 -  This driver is also available as a module.  If you want to compile
  3.7145 -  it as a module, say M here and read
  3.7146 -  <file:Documentation/modules.txt>.  The module will be called
  3.7147 -  firestream.o.
  3.7148 -
  3.7149 -Enable usec resolution timestamps
  3.7150 -CONFIG_ATM_ZATM_EXACT_TS
  3.7151 -  The uPD98401 SAR chip supports a high-resolution timer (approx. 30
  3.7152 -  MHz) that is used for very accurate reception timestamps. Because
  3.7153 -  that timer overflows after 140 seconds, and also to avoid timer
  3.7154 -  drift, time measurements need to be periodically synchronized with
  3.7155 -  the normal system time. Enabling this feature will add some general
  3.7156 -  overhead for timer synchronization and also per-packet overhead for
  3.7157 -  time conversion.
  3.7158 -
  3.7159 -IDT 77201/11 (NICStAR) (ForeRunnerLE)
  3.7160 -CONFIG_ATM_NICSTAR
  3.7161 -  The NICStAR chipset family is used in a large number of ATM NICs for
  3.7162 -  25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
  3.7163 -  series. Say Y if you have one of those.
  3.7164 -
  3.7165 -  This driver is also available as a module.  If you want to compile
  3.7166 -  it as a module, say M here and read
  3.7167 -  <file:Documentation/modules.txt>. The module will be called
  3.7168 -  nicstar.o.
  3.7169 -
  3.7170 -Use suni PHY driver (155Mbps)
  3.7171 -CONFIG_ATM_NICSTAR_USE_SUNI
  3.7172 -  Support for the S-UNI and compatible PHYsical layer chips. These are
  3.7173 -  found in most 155Mbps NICStAR based ATM cards, namely in the
  3.7174 -  ForeRunner LE155 cards. This driver provides detection of cable~
  3.7175 -  removal and reinsertion and provides some statistics. This driver
  3.7176 -  doesn't have removal capability when compiled as a module, so if you
  3.7177 -  need that capability don't include S-UNI support (it's not needed to
  3.7178 -  make the card work).
  3.7179 -
  3.7180 -Use IDT77015 PHY driver (25Mbps)
  3.7181 -CONFIG_ATM_NICSTAR_USE_IDT77105
  3.7182 -  Support for the PHYsical layer chip in ForeRunner LE25 cards. In
  3.7183 -  addition to cable removal/reinsertion detection, this driver allows
  3.7184 -  you to control the loopback mode of the chip via a dedicated IOCTL.
  3.7185 -  This driver is required for proper handling of temporary carrier
  3.7186 -  loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
  3.7187 -
  3.7188 -IDT 77252 (NICStAR II)
  3.7189 -CONFIG_ATM_IDT77252
  3.7190 -  Driver for the IDT 77252 ATM PCI chips.
  3.7191 -
  3.7192 -  This driver is also available as a module.  If you want to compile
  3.7193 -  it as a module, say M here and read
  3.7194 -  <file:Documentation/modules.txt>. The module will be called idt77252.o
  3.7195 -
  3.7196 -Enable debugging messages
  3.7197 -CONFIG_ATM_IDT77252_DEBUG
  3.7198 -  Somewhat useful debugging messages are available. The choice of
  3.7199 -  messages is controlled by a bitmap.  This may be specified as a
  3.7200 -  module argument.  See the file <file:drivers/atm/idt77252.h> for
  3.7201 -  the meanings of the bits in the mask.
  3.7202 -
  3.7203 -  When active, these messages can have a significant impact on the
  3.7204 -  speed of the driver, and the size of your syslog files! When
  3.7205 -  inactive, they will have only a modest impact on performance.
  3.7206 -
  3.7207 -Receive ALL cells in raw queue
  3.7208 -CONFIG_ATM_IDT77252_RCV_ALL
  3.7209 -  Enable receiving of all cells on the ATM link, that do not match
  3.7210 -  an open connection in the raw cell queue of the driver.  Useful
  3.7211 -  for debugging or special applications only, so the safe answer is N.
  3.7212 -
  3.7213 -Madge Ambassador (Collage PCI 155 Server)
  3.7214 -CONFIG_ATM_AMBASSADOR
  3.7215 -  This is a driver for ATMizer based ATM card produced by Madge
  3.7216 -  Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
  3.7217 -  here if you have one of these cards.
  3.7218 -
  3.7219 -Enable debugging messages
  3.7220 -CONFIG_ATM_AMBASSADOR_DEBUG
  3.7221 -  Somewhat useful debugging messages are available. The choice of
  3.7222 -  messages is controlled by a bitmap.  This may be specified as a
  3.7223 -  module argument (kernel command line argument as well?), changed
  3.7224 -  dynamically using an ioctl (not yet) or changed by sending the
  3.7225 -  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  3.7226 -  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
  3.7227 -  mask.
  3.7228 -
  3.7229 -  When active, these messages can have a significant impact on the
  3.7230 -  speed of the driver, and the size of your syslog files! When
  3.7231 -  inactive, they will have only a modest impact on performance.
  3.7232 -
  3.7233 -Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
  3.7234 -CONFIG_ATM_HORIZON
  3.7235 -  This is a driver for the Horizon chipset ATM adapter cards once
  3.7236 -  produced by Madge Networks Ltd. Say Y (or M to compile as a module
  3.7237 -  named horizon.o) here if you have one of these cards.
  3.7238 -
  3.7239 -Enable debugging messages
  3.7240 -CONFIG_ATM_HORIZON_DEBUG
  3.7241 -  Somewhat useful debugging messages are available. The choice of
  3.7242 -  messages is controlled by a bitmap.  This may be specified as a
  3.7243 -  module argument (kernel command line argument as well?), changed
  3.7244 -  dynamically using an ioctl (not yet) or changed by sending the
  3.7245 -  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  3.7246 -  <file:drivers/atm/horizon.h> for the meanings of the bits in the
  3.7247 -  mask.
  3.7248 -
  3.7249 -  When active, these messages can have a significant impact on the
  3.7250 -  speed of the driver, and the size of your syslog files! When
  3.7251 -  inactive, they will have only a modest impact on performance.
  3.7252 -
  3.7253 -Interphase ATM PCI x575/x525/x531
  3.7254 -CONFIG_ATM_IA
  3.7255 -  This is a driver for the Interphase (i)ChipSAR adapter cards
  3.7256 -  which include a variety of variants in term of the size of the
  3.7257 -  control memory (128K-1KVC, 512K-4KVC), the size of the packet
  3.7258 -  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
  3.7259 -  UTP155, UTP25, DS3 and E3). Go to:
  3.7260 -  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
  3.7261 -  for more info about the cards. Say Y (or M to compile as a module
  3.7262 -  named iphase.o) here if you have one of these cards.
  3.7263 -
  3.7264 -  See the file <file:Documentation/networking/iphase.txt> for further
  3.7265 -  details.
  3.7266 -
  3.7267 -Enable debugging messages
  3.7268 -CONFIG_ATM_IA_DEBUG
  3.7269 -  Somewhat useful debugging messages are available. The choice of
  3.7270 -  messages is controlled by a bitmap. This may be specified as a
  3.7271 -  module argument (kernel command line argument as well?), changed
  3.7272 -  dynamically using an ioctl (Get the debug utility, iadbg, from
  3.7273 -  <ftp://ftp.iphase.com/pub/atm/pci/>).
  3.7274 -
  3.7275 -  See the file <file:drivers/atm/iphase.h> for the meanings of the
  3.7276 -  bits in the mask.
  3.7277 -
  3.7278 -  When active, these messages can have a significant impact on the
  3.7279 -  speed of the driver, and the size of your syslog files! When
  3.7280 -  inactive, they will have only a modest impact on performance.
  3.7281 -
  3.7282 -Efficient Networks Speedstream 3010
  3.7283 -CONFIG_ATM_LANAI
  3.7284 -  Supports ATM cards based on the Efficient Networks "Lanai"
  3.7285 -  chipset such as the Speedstream 3010 and the ENI-25p.  The
  3.7286 -  Speedstream 3060 is currently not supported since we don't
  3.7287 -  have the code to drive the on-board Alcatel DSL chipset (yet).
  3.7288 -
  3.7289 -Linux telephony support
  3.7290 -CONFIG_PHONE
  3.7291 -  Say Y here if you have a telephony card, which for example allows
  3.7292 -  you to use a regular phone for voice-over-IP applications.
  3.7293 -
  3.7294 -  Note: this has nothing to do with modems.  You do not need to say Y
  3.7295 -  here in order to be able to use a modem under Linux.
  3.7296 -
  3.7297 -  This support is also available as a module.  If you want to compile
  3.7298 -  it as a module, say M here and read
  3.7299 -  <file:Documentation/modules.txt>.  The module will be called
  3.7300 -  phonedev.o.
  3.7301 -
  3.7302 -Compaq Smart Array support
  3.7303 -CONFIG_BLK_CPQ_CISS_DA
  3.7304 -  This is the driver for Compaq Smart Array 5xxx controllers.
  3.7305 -  Everyone using these boards should say Y here.
  3.7306 -  See <file:Documentation/cciss.txt> for the current list of
  3.7307 -  boards supported by this driver, and for further information
  3.7308 -  on the use of this driver.
  3.7309 -
  3.7310 -  This driver is also available as a module ( = code which can be
  3.7311 -  inserted in and removed from the running kernel whenever you want).
  3.7312 -  If you want to compile it as a module, say M here and read
  3.7313 -  <file:Documentation/modules.txt>. The module will be called
  3.7314 -  cciss.o
  3.7315 -
  3.7316 -SCSI tape drive support for Smart Array 5xxx
  3.7317 -CONFIG_CISS_SCSI_TAPE
  3.7318 -  When enabled (Y), this option allows SCSI tape drives and SCSI medium
  3.7319 -  changers (tape robots) to be accessed via a Compaq 5xxx array
  3.7320 -  controller.  (See <file:Documentation/cciss.txt> for more details.)
  3.7321 -
  3.7322 -  "SCSI support" and "SCSI tape support" must also be enabled for this
  3.7323 -  option to work.
  3.7324 -
  3.7325 -  When this option is disabled (N), the SCSI portion of the driver
  3.7326 -  is not compiled.
  3.7327 -
  3.7328 -Enable monitor thread
  3.7329 -CONFIG_CISS_MONITOR_THREAD
  3.7330 -  Intended for use with multipath configurations (see the md driver).
  3.7331 -  This option allows a per-adapter monitoring thread to periodically
  3.7332 -  poll the adapter to detect failure modes in which the processor
  3.7333 -  is unable to receive interrupts from the adapter, thus enabling 
  3.7334 -  fail-over to an alternate adapter in such situations.  See 
  3.7335 -  <file:Documentation/cciss.txt> for more details.
  3.7336 -
  3.7337 -QuickNet Internet LineJack/PhoneJack support
  3.7338 -CONFIG_PHONE_IXJ
  3.7339 -  Say M if you have a telephony card manufactured by Quicknet
  3.7340 -  Technologies, Inc.  These include the Internet PhoneJACK and
  3.7341 -  Internet LineJACK Telephony Cards. You will get a module called
  3.7342 -  ixj.o.
  3.7343 -
  3.7344 -  For the ISA versions of these products, you can configure the
  3.7345 -  cards using the isapnp tools (pnpdump/isapnp) or you can use the
  3.7346 -  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
  3.7347 -
  3.7348 -  For more information on these cards, see Quicknet's web site at:
  3.7349 -  <http://www.quicknet.net/>.
  3.7350 -
  3.7351 -  If you do not have any Quicknet telephony cards, you can safely
  3.7352 -  say N here.
  3.7353 -
  3.7354 -QuickNet Internet LineJack/PhoneJack PCMCIA support
  3.7355 -CONFIG_PHONE_IXJ_PCMCIA
  3.7356 -  Say Y here to configure in PCMCIA service support for the Quicknet
  3.7357 -  cards manufactured by Quicknet Technologies, Inc.  This builds an
  3.7358 -  additional support module for the PCMCIA version of the card.
  3.7359 -
  3.7360 -FORE Systems 200E-series
  3.7361 -CONFIG_ATM_FORE200E_MAYBE
  3.7362 -  This is a driver for the FORE Systems 200E-series ATM adapter
  3.7363 -  cards. It simultaneously supports PCA-200E and SBA-200E models
  3.7364 -  on PCI and SBUS hosts. Say Y (or M to compile as a module
  3.7365 -  named fore_200e.o) here if you have one of these ATM adapters.
  3.7366 -
  3.7367 -  Note that the driver will actually be compiled only if you
  3.7368 -  additionally enable the support for PCA-200E and/or SBA-200E
  3.7369 -  cards.
  3.7370 -
  3.7371 -  See the file <file:Documentation/networking/fore200e.txt> for
  3.7372 -  further details.
  3.7373 -
  3.7374 -Enable PCA-200E card support on PCI-based hosts
  3.7375 -CONFIG_ATM_FORE200E_PCA
  3.7376 -  Say Y here if you want your PCA-200E cards to be probed.
  3.7377 -
  3.7378 -Use default PCA-200E firmware
  3.7379 -CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
  3.7380 -  Use the default PCA-200E firmware data shipped with the driver.
  3.7381 -
  3.7382 -  Normal users do not have to deal with the firmware stuff, so
  3.7383 -  they should say Y here.
  3.7384 -
  3.7385 -Pathname of user-supplied binary firmware
  3.7386 -CONFIG_ATM_FORE200E_PCA_FW
  3.7387 -  This defines the pathname of an alternative PCA-200E binary
  3.7388 -  firmware image supplied by the user. This pathname may be
  3.7389 -  absolute or relative to the drivers/atm directory.
  3.7390 -
  3.7391 -  The driver comes with an adequate firmware image, so normal users do
  3.7392 -  not have to supply an alternative one. They just say Y to "Use
  3.7393 -  default PCA-200E firmware" instead.
  3.7394 -
  3.7395 -Enable SBA-200E card support on SBUS-based hosts
  3.7396 -CONFIG_ATM_FORE200E_SBA
  3.7397 -  Say Y here if you want your SBA-200E cards to be probed.
  3.7398 -
  3.7399 -Use default SBA-200E firmware
  3.7400 -CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
  3.7401 -  Use the default SBA-200E firmware data shipped with the driver.
  3.7402 -
  3.7403 -  Normal users do not have to deal with the firmware stuff, so
  3.7404 -  they should say Y here.
  3.7405 -
  3.7406 -Pathname of user-supplied binary firmware
  3.7407 -CONFIG_ATM_FORE200E_SBA_FW
  3.7408 -  This defines the pathname of an alternative SBA-200E binary
  3.7409 -  firmware image supplied by the user. This pathname may be
  3.7410 -  absolute or relative to the drivers/atm directory.
  3.7411 -
  3.7412 -  The driver comes with an adequate firmware image, so normal users do
  3.7413 -  not have to supply an alternative one. They just say Y to "Use
  3.7414 -  default SBA-200E firmware", above.
  3.7415 -
  3.7416 -Maximum number of tx retries
  3.7417 -CONFIG_ATM_FORE200E_TX_RETRY
  3.7418 -  Specifies the number of times the driver attempts to transmit
  3.7419 -  a message before giving up, if the transmit queue of the ATM card
  3.7420 -  is transiently saturated.
  3.7421 -
  3.7422 -  Saturation of the transmit queue may occur only under extreme
  3.7423 -  conditions, e.g. when a fast host continuously submits very small
  3.7424 -  frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
  3.7425 -
  3.7426 -  Note that under common conditions, it is unlikely that you encounter
  3.7427 -  a saturation of the transmit queue, so the retry mechanism never
  3.7428 -  comes into play.
  3.7429 -
  3.7430 -Debugging level (0-3)
  3.7431 -CONFIG_ATM_FORE200E_DEBUG
  3.7432 -  Specifies the level of debugging messages issued by the driver.
  3.7433 -  The verbosity of the driver increases with the value of this
  3.7434 -  parameter.
  3.7435 -
  3.7436 -  When active, these messages can have a significant impact on
  3.7437 -  the performances of the driver, and the size of your syslog files!
  3.7438 -  Keep the debugging level to 0 during normal operations.
  3.7439 -
  3.7440 -ForeRunner HE Series
  3.7441 -CONFIG_ATM_HE
  3.7442 -  This is a driver for the Marconi ForeRunner HE-series ATM adapter
  3.7443 -  cards. It simultaneously supports the 155 and 622 versions.
  3.7444 -
  3.7445 -Use S/UNI PHY driver
  3.7446 -  Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
  3.7447 -  HE cards.  This driver provides carrier detection some statistics.
  3.7448 -
  3.7449 -PPP over ATM
  3.7450 -CONFIG_PPPOATM
  3.7451 -  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  3.7452 -  This implementation does not yet comply with section 8 of RFC2364,
  3.7453 -  which can lead to bad results idf the ATM peer loses state and 
  3.7454 -  changes its encapsulation unilaterally.
  3.7455 -
  3.7456 -Fusion MPT device support
  3.7457 -CONFIG_FUSION
  3.7458 -  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
  3.7459 -  provides high performance SCSI host initiator, and LAN [1] interface
  3.7460 -  services to a host system.  The Fusion architecture is capable of
  3.7461 -  duplexing these protocols on high-speed Fibre Channel
  3.7462 -  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
  3.7463 -  physical medium.
  3.7464 -
  3.7465 -          [1] LAN is not supported on parallel SCSI medium.
  3.7466 -
  3.7467 -  These drivers require a Fusion MPT compatible PCI adapter installed
  3.7468 -  in the host system.  MPT adapters contain specialized I/O processors
  3.7469 -  to handle I/O workload, and more importantly to offload this work
  3.7470 -  from the host CPU(s).
  3.7471 -
  3.7472 -  If you have Fusion MPT hardware and want to use it, you can say
  3.7473 -  Y or M here to add MPT (base + ScsiHost) drivers.
  3.7474 -    <Y> = build lib (fusion.o), and link [static] into the kernel [2]
  3.7475 -          proper
  3.7476 -    <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
  3.7477 -          mptscsih.o)
  3.7478 -
  3.7479 -          [2] In order enable capability to boot the linux kernel
  3.7480 -              natively from a Fusion MPT target device, you MUST
  3.7481 -               answer Y here! (currently requires CONFIG_BLK_DEV_SD)
  3.7482 -          [3] This support is also available as a module ( = code
  3.7483 -              which can be inserted in and removed from the running
  3.7484 -              kernel whenever you want).  If you want to compile as
  3.7485 -              modules, say M here and read
  3.7486 -              <file:Documentation/modules.txt>.
  3.7487 -
  3.7488 -  If unsure, say N.
  3.7489 -
  3.7490 -  If you say Y or M here you will get a choice of these
  3.7491 -  additional protocol and support module options:         Module Name:
  3.7492 -    <M>   Enhanced SCSI error reporting                     (isense.o)
  3.7493 -    <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
  3.7494 -    <M>   Fusion MPT LAN driver                             (mptlan.o)
  3.7495 -
  3.7496 -  ---
  3.7497 -  Fusion MPT is trademark of LSI Logic Corporation, and its
  3.7498 -  architecture is based on LSI Logic's Message Passing Interface (MPI)
  3.7499 -  specification.
  3.7500 -
  3.7501 -Maximum number of scatter gather entries
  3.7502 -CONFIG_FUSION_MAX_SGE
  3.7503 -  This option allows you to specify the maximum number of scatter-
  3.7504 -  gather entries per I/O. The driver defaults to 40, a reasonable number
  3.7505 -  for most systems. However, the user may increase this up to 128.
  3.7506 -  Increasing this parameter will require significantly more memory
  3.7507 -  on a per controller instance. Increasing the parameter is not
  3.7508 -  necessary (or recommended) unless the user will be running
  3.7509 -  large I/O's via the raw interface.
  3.7510 -
  3.7511 -Fusion MPT enhanced SCSI error reporting [optional] module
  3.7512 -CONFIG_FUSION_ISENSE
  3.7513 -  The isense module (roughly stands for Interpret SENSE data) is
  3.7514 -  completely optional.  It simply provides extra English readable
  3.7515 -  strings in SCSI Error Report(s) that might be generated from the
  3.7516 -  Fusion MPT SCSI Host driver, for example when a target device
  3.7517 -  returns a SCSI check condition on a I/O.  Without this module
  3.7518 -  loaded you might see:
  3.7519 -
  3.7520 -    SCSI Error Report =-=-= (ioc0,scsi5:0)
  3.7521 -      SCSI_Status=02h (CHECK_CONDITION)
  3.7522 -      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
  3.7523 -      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  3.7524 -      SenseKey=2h (NOT READY); FRU=02h
  3.7525 -      ASC/ASCQ=29h/00h
  3.7526 -
  3.7527 -  Where otherwise, if this module had been loaded, you would see:
  3.7528 -
  3.7529 -    SCSI Error Report =-=-= (ioc0,scsi5:0)
  3.7530 -      SCSI_Status=02h (CHECK_CONDITION)
  3.7531 -      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
  3.7532 -      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  3.7533 -      SenseKey=2h (NOT READY); FRU=02h
  3.7534 -      ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
  3.7535 -
  3.7536 -  Say M for "Enhanced SCSI error reporting" to compile this optional module,
  3.7537 -  creating a driver named: isense.o.
  3.7538 -
  3.7539 -  NOTE: Support for building this feature into the kernel is not
  3.7540 -  available, due to kernel size considerations.
  3.7541 -
  3.7542 -Fusion MPT misc device (ioctl) driver [optional] module
  3.7543 -CONFIG_FUSION_CTL
  3.7544 -  The Fusion MPT misc device driver provides specialized control
  3.7545 -  of MPT adapters via system ioctl calls.  Use of ioctl calls to
  3.7546 -  the MPT driver requires that you create and use a misc device
  3.7547 -  node ala:
  3.7548 -    mknod /dev/mptctl c 10 240
  3.7549 -
  3.7550 -  One use of this ioctl interface is to perform an upgrade (reflash)
  3.7551 -  of the MPT adapter firmware.  Refer to readme file(s) distributed
  3.7552 -  with the Fusion MPT linux driver for additional details.
  3.7553 -
  3.7554 -  If enabled by saying M to this, a driver named: mptctl.o
  3.7555 -  will be compiled.
  3.7556 -
  3.7557 -  If unsure whether you really want or need this, say N.
  3.7558 -
  3.7559 -Fusion MPT LAN driver [optional]
  3.7560 -CONFIG_FUSION_LAN
  3.7561 -  This module supports LAN IP traffic over Fibre Channel port(s)
  3.7562 -  on Fusion MPT compatible hardware (LSIFC9xx chips).
  3.7563 -  The physical interface used is defined in RFC 2625.
  3.7564 -  Please refer to that document for details.
  3.7565 -
  3.7566 -  Installing this driver requires the knowledge to configure and
  3.7567 -  activate a new network interface, "fc0", using standard Linux tools.
  3.7568 -
  3.7569 -  If enabled by saying M to this, a driver named: mptlan.o
  3.7570 -  will be compiled.
  3.7571 -
  3.7572 -  If unsure whether you really want or need this, say N.
  3.7573 -
  3.7574 -  NOTES: This feature is NOT available nor supported for linux-2.2.x
  3.7575 -  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
  3.7576 -  in order to configure this option.
  3.7577 -  Support for building this feature into the linux kernel is not
  3.7578 -  yet available.
  3.7579 -
  3.7580 -SCSI support
  3.7581 -CONFIG_SCSI
  3.7582 -  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  3.7583 -  any other SCSI device under Linux, say Y and make sure that you know
  3.7584 -  the name of your SCSI host adapter (the card inside your computer
  3.7585 -  that "speaks" the SCSI protocol, also called SCSI controller),
  3.7586 -  because you will be asked for it.
  3.7587 -
  3.7588 -  You also need to say Y here if you want support for the parallel
  3.7589 -  port version of the 100 MB IOMEGA ZIP drive.
  3.7590 -
  3.7591 -  This driver is also available as a module ( = code which can be
  3.7592 -  inserted in and removed from the running kernel whenever you want).
  3.7593 -  The module will be called scsi_mod.o.  If you want to compile it as
  3.7594 -  a module, say M here and read <file:Documentation/modules.txt> and
  3.7595 -  <file:Documentation/scsi.txt>.  However, do not compile this as a
  3.7596 -  module if your root file system (the one containing the directory /)
  3.7597 -  is located on a SCSI device.
  3.7598 -
  3.7599 -SCSI disk support
  3.7600 -CONFIG_BLK_DEV_SD
  3.7601 -  If you want to use a SCSI hard disk or the SCSI or parallel port
  3.7602 -  version of the IOMEGA ZIP drive under Linux, say Y and read the
  3.7603 -  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  3.7604 -  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  3.7605 -  CD-ROMs.
  3.7606 -
  3.7607 -  This driver is also available as a module ( = code which can be
  3.7608 -  inserted in and removed from the running kernel whenever you want).
  3.7609 -  The module will be called sd_mod.o.  If you want to compile it as a
  3.7610 -  module, say M here and read <file:Documentation/modules.txt> and
  3.7611 -  <file:Documentation/scsi.txt>.  Do not compile this driver as a
  3.7612 -  module if your root file system (the one containing the directory /)
  3.7613 -  is located on a SCSI disk. In this case, do not compile the driver
  3.7614 -  for your SCSI host adapter (below) as a module either.
  3.7615 -
  3.7616 -Maximum number of SCSI disks that can be loaded as modules
  3.7617 -CONFIG_SD_EXTRA_DEVS
  3.7618 -  This controls the amount of additional space allocated in tables for
  3.7619 -  drivers that are loaded as modules after the kernel is booted.  In
  3.7620 -  the event that the SCSI core itself was loaded as a module, this
  3.7621 -  value is the number of additional disks that can be loaded after the
  3.7622 -  first host driver is loaded.
  3.7623 -
  3.7624 -  Admittedly this isn't pretty, but there are tons of race conditions
  3.7625 -  involved with resizing the internal arrays on the fly.  Someday this
  3.7626 -  flag will go away, and everything will work automatically.
  3.7627 -
  3.7628 -  If you don't understand what's going on, go with the default.
  3.7629 -
  3.7630 -Maximum number of SCSI tapes that can be loaded as modules
  3.7631 -CONFIG_ST_EXTRA_DEVS
  3.7632 -  This controls the amount of additional space allocated in tables for
  3.7633 -  drivers that are loaded as modules after the kernel is booted.  In
  3.7634 -  the event that the SCSI core itself was loaded as a module, this
  3.7635 -  value is the number of additional tapes that can be loaded after the
  3.7636 -  first host driver is loaded.
  3.7637 -
  3.7638 -  Admittedly this isn't pretty, but there are tons of race conditions
  3.7639 -  involved with resizing the internal arrays on the fly.  Someday this
  3.7640 -  flag will go away, and everything will work automatically.
  3.7641 -
  3.7642 -  If you don't understand what's going on, go with the default.
  3.7643 -
  3.7644 -SCSI tape support
  3.7645 -CONFIG_CHR_DEV_ST
  3.7646 -  If you want to use a SCSI tape drive under Linux, say Y and read the
  3.7647 -  SCSI-HOWTO, available from
  3.7648 -  <http://www.tldp.org/docs.html#howto>, and
  3.7649 -  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
  3.7650 -  SCSI CD-ROMs.
  3.7651 -
  3.7652 -  This driver is also available as a module ( = code which can be
  3.7653 -  inserted in and removed from the running kernel whenever you want).
  3.7654 -  The module will be called st.o. If you want to compile it as a
  3.7655 -  module, say M here and read <file:Documentation/modules.txt> and
  3.7656 -  <file:Documentation/scsi.txt>.
  3.7657 -
  3.7658 -OnStream SC-x0 SCSI tape support
  3.7659 -CONFIG_CHR_DEV_OSST
  3.7660 -  The OnStream SC-x0 SCSI tape drives can not be driven by the
  3.7661 -  standard st driver, but instead need this special osst driver and
  3.7662 -  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
  3.7663 -  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
  3.7664 -  as well.  Note that there is also a second generation of OnStream
  3.7665 -  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
  3.7666 -  tapes (QIC-157) and can be driven by the standard driver st.
  3.7667 -  For more information, you may have a look at the SCSI-HOWTO
  3.7668 -  <http://www.tldp.org/docs.html#howto>  and
  3.7669 -  <file:drivers/scsi/README.osst>  in the kernel source.
  3.7670 -  More info on the OnStream driver may be found on
  3.7671 -  <http://linux1.onstream.nl/test/>
  3.7672 -  Please also have a look at the standard st docu, as most of it
  3.7673 -  applies to osst as well.
  3.7674 -
  3.7675 -  This driver is also available as a module ( = code which can be
  3.7676 -  inserted in and removed from the running kernel whenever you want).
  3.7677 -  The module will be called osst.o. If you want to compile it as a
  3.7678 -  module, say M here and read <file:Documentation/modules.txt> and
  3.7679 -  <file:Documentation/scsi.txt>.
  3.7680 -
  3.7681 -SCSI CD-ROM support
  3.7682 -CONFIG_BLK_DEV_SR
  3.7683 -  If you want to use a SCSI CD-ROM under Linux, say Y and read the
  3.7684 -  SCSI-HOWTO and the CD-ROM-HOWTO at
  3.7685 -  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  3.7686 -  or M to "ISO 9660 CD-ROM file system support" later.
  3.7687 -
  3.7688 -  This driver is also available as a module ( = code which can be
  3.7689 -  inserted in and removed from the running kernel whenever you want).
  3.7690 -  The module will be called sr_mod.o. If you want to compile it as a
  3.7691 -  module, say M here and read <file:Documentation/modules.txt> and
  3.7692 -  <file:Documentation/scsi.txt>.
  3.7693 -
  3.7694 -Maximum number of CD-ROM devices that can be loaded as modules
  3.7695 -CONFIG_SR_EXTRA_DEVS
  3.7696 -  This controls the amount of additional space allocated in tables for
  3.7697 -  drivers that are loaded as modules after the kernel is booted. In
  3.7698 -  the event that the SCSI core itself was loaded as a module, this
  3.7699 -  value is the number of additional CD-ROMs that can be loaded after
  3.7700 -  the first host driver is loaded.
  3.7701 -
  3.7702 -  Admittedly this isn't pretty, but there are tons of race conditions
  3.7703 -  involved with resizing the internal arrays on the fly.  Someday this
  3.7704 -  flag will go away, and everything will work automatically.
  3.7705 -
  3.7706 -  If you don't understand what's going on, go with the default.
  3.7707 -
  3.7708 -Enable vendor-specific extensions (for SCSI CD-ROM)
  3.7709 -CONFIG_BLK_DEV_SR_VENDOR
  3.7710 -  This enables the usage of vendor specific SCSI commands. This is
  3.7711 -  required to support multisession CDs with old NEC/TOSHIBA cdrom
  3.7712 -  drives (and HP Writers). If you have such a drive and get the first
  3.7713 -  session only, try saying Y here; everybody else says N.
  3.7714 -
  3.7715 -SCSI generic support
  3.7716 -CONFIG_CHR_DEV_SG
  3.7717 -  If you want to use SCSI scanners, synthesizers or CD-writers or just
  3.7718 -  about anything having "SCSI" in its name other than hard disks,
  3.7719 -  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
  3.7720 -  directly, so you need some additional software which knows how to
  3.7721 -  talk to these devices using the SCSI protocol:
  3.7722 -
  3.7723 -  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
  3.7724 -  writer software look at Cdrtools
  3.7725 -  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
  3.7726 -  and for burning a "disk at once": CDRDAO
  3.7727 -  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
  3.7728 -  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
  3.7729 -  For other devices, it's possible that you'll have to write the
  3.7730 -  driver software yourself. Please read the file
  3.7731 -  <file:Documentation/scsi-generic.txt> for more information.
  3.7732 -
  3.7733 -  If you want to compile this as a module ( = code which can be
  3.7734 -  inserted in and removed from the running kernel whenever you want),
  3.7735 -  say M here and read <file:Documentation/modules.txt> and
  3.7736 -  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
  3.7737 -  say N.
  3.7738 -
  3.7739 -Probe all LUNs on each SCSI device
  3.7740 -CONFIG_SCSI_MULTI_LUN
  3.7741 -  If you have a SCSI device that supports more than one LUN (Logical
  3.7742 -  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
  3.7743 -  can say Y here to force the SCSI driver to probe for multiple LUNs.
  3.7744 -  A SCSI device with multiple LUNs acts logically like multiple SCSI
  3.7745 -  devices. The vast majority of SCSI devices have only one LUN, and
  3.7746 -  so most people can say N here and should in fact do so, because it
  3.7747 -  is safer.
  3.7748 -
  3.7749 -Verbose SCSI error reporting (kernel size +=12K)
  3.7750 -CONFIG_SCSI_CONSTANTS
  3.7751 -  The error messages regarding your SCSI hardware will be easier to
  3.7752 -  understand if you say Y here; it will enlarge your kernel by about
  3.7753 -  12 KB. If in doubt, say Y.
  3.7754 -
  3.7755 -SCSI logging facility
  3.7756 -CONFIG_SCSI_LOGGING
  3.7757 -  This turns on a logging facility that can be used to debug a number
  3.7758 -  of SCSI related problems.
  3.7759 -
  3.7760 -  If you say Y here, no logging output will appear by default, but you
  3.7761 -  can enable logging by saying Y to "/proc file system support" and
  3.7762 -  "Sysctl support" below and executing the command
  3.7763 -
  3.7764 -     echo "scsi log token [level]" > /proc/scsi/scsi
  3.7765 -
  3.7766 -  at boot time after the /proc file system has been mounted.
  3.7767 -
  3.7768 -  There are a number of things that can be used for 'token' (you can
  3.7769 -  find them in the source: <file:drivers/scsi/scsi.c>), and this
  3.7770 -  allows you to select the types of information you want, and the
  3.7771 -  level allows you to select the level of verbosity.
  3.7772 -
  3.7773 -  If you say N here, it may be harder to track down some types of SCSI
  3.7774 -  problems. If you say Y here your kernel will be somewhat larger, but
  3.7775 -  there should be no noticeable performance impact as long as you have
  3.7776 -  logging turned off.
  3.7777 -
  3.7778 -QDIO base support for IBM S/390 and zSeries
  3.7779 -CONFIG_QDIO
  3.7780 -  This driver provides the Queued Direct I/O base support for the
  3.7781 -  IBM S/390 (G5 and G6) and eServer zSeries (z800 and z900).
  3.7782 -
  3.7783 -  For details please refer to the documentation provided by IBM at
  3.7784 -  <http://www10.software.ibm.com/developerworks/opensource/linux390>
  3.7785 -
  3.7786 -  This driver is also available as a module ( = code which can be
  3.7787 -  inserted in and removed from the running kernel whenever you want).
  3.7788 -  The module will be called qdio.o. If you want to compile it as a
  3.7789 -  module, say M here and read <file:Documentation/modules.txt>.
  3.7790 -
  3.7791 -  If unsure, say Y.
  3.7792 -
  3.7793 -Performance statistics for QDIO base support
  3.7794 -CONFIG_QDIO_PERF_STATS
  3.7795 -  Say Y here to get performance statistics in /proc/qdio_perf
  3.7796 -
  3.7797 -  If unsure, say N.
  3.7798 -
  3.7799 -SGI WD93C93 SCSI Driver
  3.7800 -CONFIG_SCSI_SGIWD93
  3.7801 -  Say Y here to support the on-board WD93C93 SCSI controller found (a)
  3.7802 -  on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
  3.7803 -  ARM-based machines.
  3.7804 -
  3.7805 -DEC NCR53C94 SCSI Driver
  3.7806 -CONFIG_SCSI_DECNCR
  3.7807 -  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
  3.7808 -  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
  3.7809 -
  3.7810 -AdvanSys SCSI support
  3.7811 -CONFIG_SCSI_ADVANSYS
  3.7812 -  This is a driver for all SCSI host adapters manufactured by
  3.7813 -  AdvanSys. It is documented in the kernel source in
  3.7814 -  <file:drivers/scsi/advansys.c>.
  3.7815 -
  3.7816 -  This driver is also available as a module ( = code which can be
  3.7817 -  inserted in and removed from the running kernel whenever you want).
  3.7818 -  If you want to compile it as a module, say M here and read
  3.7819 -  <file:Documentation/modules.txt>.  The module will be called
  3.7820 -  advansys.o.
  3.7821 -
  3.7822 -Adaptec AHA152X/2825 support
  3.7823 -CONFIG_SCSI_AHA152X
  3.7824 -  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
  3.7825 -  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
  3.7826 -  must be manually specified in this case.
  3.7827 -
  3.7828 -  It is explained in section 3.3 of the SCSI-HOWTO, available from
  3.7829 -  <http://www.tldp.org/docs.html#howto>. You might also want to
  3.7830 -  read the file <file:drivers/scsi/README.aha152x>.
  3.7831 -
  3.7832 -  This driver is also available as a module ( = code which can be
  3.7833 -  inserted in and removed from the running kernel whenever you want).
  3.7834 -  The module will be called aha152x.o. If you want to compile it as a
  3.7835 -  module, say M here and read <file:Documentation/modules.txt>.
  3.7836 -
  3.7837 -Adaptec AHA1542 support
  3.7838 -CONFIG_SCSI_AHA1542
  3.7839 -  This is support for a SCSI host adapter.  It is explained in section
  3.7840 -  3.4 of the SCSI-HOWTO, available from
  3.7841 -  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
  3.7842 -  purchased by Adaptec, and some former Trantor products are being
  3.7843 -  sold under the Adaptec name.  If it doesn't work out of the box, you
  3.7844 -  may have to change some settings in <file:drivers/scsi/aha1542.h>.
  3.7845 -
  3.7846 -  If you want to compile this as a module ( = code which can be
  3.7847 -  inserted in and removed from the running kernel whenever you want),
  3.7848 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.7849 -  will be called aha1542.o.
  3.7850 -
  3.7851 -Adaptec AHA1740 support
  3.7852 -CONFIG_SCSI_AHA1740
  3.7853 -  This is support for a SCSI host adapter.  It is explained in section
  3.7854 -  3.5 of the SCSI-HOWTO, available from
  3.7855 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  3.7856 -  of the box, you may have to change some settings in
  3.7857 -  <file:drivers/scsi/aha1740.h>.
  3.7858 -
  3.7859 -  This driver is also available as a module ( = code which can be
  3.7860 -  inserted in and removed from the running kernel whenever you want).
  3.7861 -  The module will be called aha1740.o.  If you want to compile it as a
  3.7862 -  module, say M here and read <file:Documentation/modules.txt>.
  3.7863 -
  3.7864 -Adaptec AIC7xxx support
  3.7865 -CONFIG_SCSI_AIC7XXX
  3.7866 -  This driver supports all of Adaptec's Fast through Ultra 160 PCI
  3.7867 -  based SCSI controllers as well as the aic7770 based EISA and VLB
  3.7868 -  SCSI controllers (the 274x and 284x series).  For AAA and ARO based
  3.7869 -  configurations, only SCSI functionality is provided.
  3.7870 -
  3.7871 -  If you want to compile the driver as a module ( = code which can be
  3.7872 -  inserted in and removed from the running kernel whenever you want),
  3.7873 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.7874 -  will be called aic7xxx.o.
  3.7875 -
  3.7876 -Maximum number of TCQ commands per device
  3.7877 -CONFIG_AIC7XXX_CMDS_PER_DEVICE
  3.7878 -  Specify the number of commands you would like to allocate per SCSI
  3.7879 -  device when Tagged Command Queueing (TCQ) is enabled on that device.
  3.7880 -
  3.7881 -  This is an upper bound value for the number of tagged transactions
  3.7882 -  to be used for any device.  The aic7xxx driver will automatically
  3.7883 -  vary this number based on device behavior.  For devices with a
  3.7884 -  fixed maximum, the driver will eventually lock to this maximum
  3.7885 -  and display a console message indicating this value.
  3.7886 -
  3.7887 -  Due to resource allocation issues in the Linux SCSI mid-layer, using
  3.7888 -  a high number of commands per device may result in memory allocation
  3.7889 -  failures when many devices are attached to the system.  For this reason,
  3.7890 -  the default is set to 32.  Higher values may result in higer performance
  3.7891 -  on some devices.  The upper bound is 253. 0 disables tagged queueing.
  3.7892 -
  3.7893 -  Per device tag depth can be controlled via the kernel command line
  3.7894 -  "tag_info" option.  See drivers/scsi/aic7xxx/README.aic7xxx
  3.7895 -  for details.
  3.7896 -
  3.7897 -  Default: 32
  3.7898 -
  3.7899 -Initial bus reset delay in milli-seconds
  3.7900 -CONFIG_AIC7XXX_RESET_DELAY_MS
  3.7901 -  The number of milliseconds to delay after an initial bus reset.
  3.7902 -  The bus settle delay following all error recovery actions is
  3.7903 -  dictated by the SCSI layer and is not affected by this value.
  3.7904 -
  3.7905 -  Default: 15000 (15 seconds)
  3.7906 -
  3.7907 -Probe for EISA and VL AIC7XXX Adapters
  3.7908 -CONFIG_AIC7XXX_PROBE_EISA_VL
  3.7909 -   Probe for EISA and VLB Aic7xxx controllers.  In many newer systems,
  3.7910 -   the invasive probes necessary to detect these controllers can cause
  3.7911 -   other devices to fail.  For this reason, the non-PCI probe code is
  3.7912 -   disabled by default.  The current value of this option can be "toggled"
  3.7913 -   via the no_probe kernel command line option.
  3.7914 -
  3.7915 -CONFIG_AIC7XXX_BUILD_FIRMWARE
  3.7916 -  This option should only be enabled if you are modifying the firmware
  3.7917 -  source to the aic7xxx driver and wish to have the generated firmware
  3.7918 -  include files updated during a normal kernel build.  The assembler
  3.7919 -  for the firmware requires lex and yacc or their equivalents, as well
  3.7920 -  as the db v1 library.  You may have to install additional packages
  3.7921 -  or modify the assembler Makefile or the files it includes if your
  3.7922 -  build environment is different than that of the author.
  3.7923 -
  3.7924 -Compile in Debugging Code
  3.7925 -CONFIG_AIC7XXX_DEBUG_ENABLE
  3.7926 -  Compile in aic7xxx debugging code that can be useful in diagnosing
  3.7927 -  driver errors.
  3.7928 -
  3.7929 -Debug code enable mask (2048 for all debugging)
  3.7930 -CONFIG_AIC7XXX_DEBUG_MASK
  3.7931 -  Bit mask of debug options that is only valid if the
  3.7932 -  CONFIG_AIC7XXX_DEBUG_ENBLE option is enabled.  The bits in this mask
  3.7933 -  are defined in the drivers/scsi/aic7xxx/aic7xxx.h - search for the
  3.7934 -  variable ahc_debug in that file to find them.
  3.7935 -
  3.7936 -  Default: 0
  3.7937 -
  3.7938 -Decode registers during diagnostics
  3.7939 -CONFIG_AIC7XXX_REG_PRETTY_PRINT
  3.7940 -  Compile in register value tables for the output of expanded register
  3.7941 -  contents in diagnostics.  This make it much easier to understand debug
  3.7942 -  output without having to refer to a data book and/or the aic7xxx.reg file.
  3.7943 -
  3.7944 -Old Adaptec AIC7xxx support
  3.7945 -CONFIG_SCSI_AIC7XXX_OLD
  3.7946 -  WARNING This driver is an older aic7xxx driver and is no longer
  3.7947 -  under active development.  Adaptec, Inc. is writing a new driver to
  3.7948 -  take the place of this one, and it is recommended that whenever
  3.7949 -  possible, people should use the new Adaptec written driver instead
  3.7950 -  of this one.  This driver will eventually be phased out entirely.
  3.7951 -
  3.7952 -  This is support for the various aic7xxx based Adaptec SCSI
  3.7953 -  controllers. These include the 274x EISA cards; 284x VLB cards;
  3.7954 -  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
  3.7955 -  motherboard based SCSI controllers from Adaptec. It does not support
  3.7956 -  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
  3.7957 -  support them. It does not support the 2920 cards from Adaptec that
  3.7958 -  use the Future Domain SCSI controller chip. For those cards, you
  3.7959 -  need the "Future Domain 16xx SCSI support" driver.
  3.7960 -
  3.7961 -  In general, if the controller is based on an Adaptec SCSI controller
  3.7962 -  chip from the aic777x series or the aic78xx series, this driver
  3.7963 -  should work. The only exception is the 7810 which is specifically
  3.7964 -  not supported (that's the RAID controller chip on the AAA-13x
  3.7965 -  cards).
  3.7966 -
  3.7967 -  Note that the AHA2920 SCSI host adapter is *not* supported by this
  3.7968 -  driver; choose "Future Domain 16xx SCSI support" instead if you have
  3.7969 -  one of those.
  3.7970 -
  3.7971 -  Information on the configuration options for this controller can be
  3.7972 -  found by checking the help file for each of the available
  3.7973 -  configuration options. You should read
  3.7974 -  <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
  3.7975 -  contacting the maintainer with any questions.  The SCSI-HOWTO,
  3.7976 -  available from <http://www.tldp.org/docs.html#howto>, can also
  3.7977 -  be of great help.
  3.7978 -
  3.7979 -  If you want to compile this driver as a module ( = code which can be
  3.7980 -  inserted in and removed from the running kernel whenever you want),
  3.7981 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.7982 -  will be called aic7xxx_old.o.
  3.7983 -
  3.7984 -Enable tagged command queueing (TCQ) by default
  3.7985 -CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
  3.7986 -  This option causes the aic7xxx driver to attempt to use Tagged
  3.7987 -  Command Queueing (TCQ) on all devices that claim to support it.
  3.7988 -
  3.7989 -  TCQ is a feature of SCSI-2 which improves performance: the host
  3.7990 -  adapter can send several SCSI commands to a device's queue even if
  3.7991 -  previous commands haven't finished yet.  Because the device is
  3.7992 -  intelligent, it can optimize its operations (like head positioning)
  3.7993 -  based on its own request queue.  Not all devices implement this
  3.7994 -  correctly.
  3.7995 -
  3.7996 -  If you say Y here, you can still turn off TCQ on troublesome devices
  3.7997 -  with the use of the tag_info boot parameter.  See the file
  3.7998 -  <file:drivers/scsi/README.aic7xxx> for more information on that and
  3.7999 -  other aic7xxx setup commands.  If this option is turned off, you may
  3.8000 -  still enable TCQ on known good devices by use of the tag_info boot
  3.8001 -  parameter.
  3.8002 -
  3.8003 -  If you are unsure about your devices then it is safest to say N
  3.8004 -  here.
  3.8005 -
  3.8006 -  However, TCQ can increase performance on some hard drives by as much
  3.8007 -  as 50% or more, so it is recommended that if you say N here, you
  3.8008 -  should at least read the <file:drivers/scsi/README.aic7xxx> file so
  3.8009 -  you will know how to enable this option manually should your drives
  3.8010 -  prove to be safe in regards to TCQ.
  3.8011 -
  3.8012 -  Conversely, certain drives are known to lock up or cause bus resets
  3.8013 -  when TCQ is enabled on them.  If you have a Western Digital
  3.8014 -  Enterprise SCSI drive for instance, then don't even bother to enable
  3.8015 -  TCQ on it as the drive will become unreliable, and it will actually
  3.8016 -  reduce performance.
  3.8017 -
  3.8018 -Default number of TCQ commands per device
  3.8019 -CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
  3.8020 -  Specify the number of commands you would like to allocate per SCSI
  3.8021 -  device when Tagged Command Queueing (TCQ) is enabled on that device.
  3.8022 -
  3.8023 -  Reasonable figures are in the range of 8 to 24 commands per device,
  3.8024 -  but depending on hardware could be increased or decreased from that
  3.8025 -  figure. If the number is too high for any particular device, the
  3.8026 -  driver will automatically compensate usually after only 10 minutes
  3.8027 -  of uptime. It will not hinder performance if some of your devices
  3.8028 -  eventually have their command depth reduced, but is a waste of
  3.8029 -  memory if all of your devices end up reducing this number down to a
  3.8030 -  more reasonable figure.
  3.8031 -
  3.8032 -  NOTE: Certain very broken drives are known to lock up when given
  3.8033 -  more commands than they like to deal with. Quantum Fireball drives
  3.8034 -  are the most common in this category. For the Quantum Fireball
  3.8035 -  drives it is suggested to use no more than 8 commands per device.
  3.8036 -
  3.8037 -  Default: 8
  3.8038 -
  3.8039 -Collect statistics to report in /proc
  3.8040 -CONFIG_AIC7XXX_OLD_PROC_STATS
  3.8041 -  This option tells the driver to keep track of how many commands have
  3.8042 -  been sent to each particular device and report that information to
  3.8043 -  the user via the /proc/scsi/aic7xxx/n file, where n is the number of
  3.8044 -  the aic7xxx controller you want the information on. This adds a
  3.8045 -  small amount of overhead to each and every SCSI command the aic7xxx
  3.8046 -  driver handles, so if you aren't really interested in this
  3.8047 -  information, it is best to leave it disabled. This will only work if
  3.8048 -  you also say Y to "/proc file system support", below.
  3.8049 -
  3.8050 -  If unsure, say N.
  3.8051 -
  3.8052 -CONFIG_SCSI_AIC79XX
  3.8053 -  This driver supports all of Adaptec's Ultra 320 PCI-X based SCSI controllers.
  3.8054 -
  3.8055 -CONFIG_AIC79XX_CMDS_PER_DEVICE 32
  3.8056 -  Specify the number of commands you would like to allocate per SCSI
  3.8057 -  device when Tagged Command Queueing (TCQ) is enabled on that device.
  3.8058 -
  3.8059 -  This is an upper bound value for the number of tagged transactions
  3.8060 -  to be used for any device.  The aic7xxx driver will automatically
  3.8061 -  vary this number based on device behavior.  For devices with a
  3.8062 -  fixed maximum, the driver will eventually lock to this maximum
  3.8063 -  and display a console message indicating this value.
  3.8064 -
  3.8065 -  Due to resource allocation issues in the Linux SCSI mid-layer, using
  3.8066 -  a high number of commands per device may result in memory allocation
  3.8067 -  failures when many devices are attached to the system.  For this reason,
  3.8068 -  the default is set to 32.  Higher values may result in higer performance
  3.8069 -  on some devices.  The upper bound is 253.
  3.8070 -
  3.8071 -  Per device tag depth can be controlled via the kernel command line
  3.8072 -  "tag_info" option.  See drivers/scsi/aic7xxx/README.aic79xx
  3.8073 -  for details.
  3.8074 -
  3.8075 -  Default: 32
  3.8076 -
  3.8077 -CONFIG_AIC79XX_RESET_DELAY_MS 15000
  3.8078 -  The number of milliseconds to delay after an initial bus reset.
  3.8079 -  The bus settle delay following all error recovery actions is
  3.8080 -  dictated by the SCSI layer and is not affected by this value.
  3.8081 -
  3.8082 -  Default: 15000 (15 seconds)
  3.8083 -
  3.8084 -CONFIG_AIC79XX_BUILD_FIRMWARE
  3.8085 -  This option should only be enabled if you are modifying the firmware
  3.8086 -  source to the aic7xxx driver and wish to have the generated firmware
  3.8087 -  include files updated during a normal kernel build.  The assembler
  3.8088 -  for the firmware requires lex and yacc or their equivalents, as well
  3.8089 -  as the db v1 library.  You may have to install additional packages
  3.8090 -  or modify the assembler Makefile or the files it includes if your
  3.8091 -  build environment is different than that of the author.
  3.8092 -
  3.8093 -CONFIG_AIC79XX_ENABLE_RD_STRM
  3.8094 -  Read Streaming is a U320 protocol option that should enhance performance.
  3.8095 -  Early U320 drive firmware actually performs slower with read streaming
  3.8096 -  enabled so it is disabled by default.  Read Streaming can be configured
  3.8097 -  in much the same way as tagged queueing using the "rd_strm" command line
  3.8098 -  option.  See drivers/scsi/aic7xxx/README.aic79xx for details.
  3.8099 -
  3.8100 -CONFIG_AIC79XX_DEBUG_ENABLE
  3.8101 -  Compile in aic79xx debugging code that can be useful in diagnosing
  3.8102 -  driver errors.
  3.8103 -
  3.8104 -CONFIG_AIC79XX_DEBUG_MASK
  3.8105 -  Bit mask of debug options that is only valid if the
  3.8106 -  CONFIG_AIC79XX_DEBUG_ENBLE option is enabled.  The bits in this mask
  3.8107 -  are defined in the drivers/scsi/aic7xxx/aic79xx.h - search for the
  3.8108 -  variable ahd_debug in that file to find them.
  3.8109 -
  3.8110 -  Default: 0
  3.8111 -
  3.8112 -CONFIG_AIC79XX_REG_PRETTY_PRINT
  3.8113 -  Compile in register value tables for the output of expanded register
  3.8114 -  contents in diagnostics.  This make it much easier to understand debug
  3.8115 -  output without having to refer to a data book and/or the aic7xxx.reg file.
  3.8116 -
  3.8117 -Adaptec I2O RAID support
  3.8118 -CONFIG_SCSI_DPT_I2O
  3.8119 -  This driver supports all of Adaptec's I2O based RAID controllers as 
  3.8120 -  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
  3.8121 -  driver by Deanna Bonds.  See <file:drivers/scsi/README.dpti>.
  3.8122 -
  3.8123 -  This driver is also available as a module ( = code which can be
  3.8124 -  inserted in and removed from the running kernel whenever you want).
  3.8125 -  If you want to compile it as a module, say M here and read
  3.8126 -  <file:Documentation/modules.txt>.  The module will be called
  3.8127 -  dpt_i2o.o.
  3.8128 -
  3.8129 -IBM ServeRAID support
  3.8130 -CONFIG_SCSI_IPS
  3.8131 -  This is support for the IBM ServeRAID hardware RAID controllers.
  3.8132 -  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
  3.8133 -  for more information.  If this driver does not work correctly
  3.8134 -  without modification please contact the author by email at
  3.8135 -  ipslinux@us.ibm.com.
  3.8136 -
  3.8137 -  You can build this driver as a module ( = code which can be
  3.8138 -  inserted in and removed from the running kernel whenever you want),
  3.8139 -  but only a single instance may be loaded. If you want to compile it
  3.8140 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.8141 -  The module will be called ips.o.
  3.8142 -
  3.8143 -BusLogic SCSI support
  3.8144 -CONFIG_SCSI_BUSLOGIC
  3.8145 -  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
  3.8146 -  Adapters. Consult the SCSI-HOWTO, available from
  3.8147 -  <http://www.tldp.org/docs.html#howto>, and the files
  3.8148 -  <file:drivers/scsi/README.BusLogic> and
  3.8149 -  <file:drivers/scsi/README.FlashPoint> for more information. If this
  3.8150 -  driver does not work correctly without modification, please contact
  3.8151 -  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
  3.8152 -
  3.8153 -  You can also build this driver as a module ( = code which can be
  3.8154 -  inserted in and removed from the running kernel whenever you want),
  3.8155 -  but only a single instance may be loaded. If you want to compile it
  3.8156 -  as a module, say M here and read <file:Documentation/modules.txt>.
  3.8157 -  The module will be called BusLogic.o.
  3.8158 -
  3.8159 -Omit BusLogic SCSI FlashPoint support
  3.8160 -CONFIG_SCSI_OMIT_FLASHPOINT
  3.8161 -  This option allows you to omit the FlashPoint support from the
  3.8162 -  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
  3.8163 -  substantial, so users of MultiMaster Host Adapters may wish to omit
  3.8164 -  it.
  3.8165 -
  3.8166 -Compaq Fibre Channel 64-bit/66Mhz HBA support
  3.8167 -CONFIG_SCSI_CPQFCTS
  3.8168 -  Say Y here to compile in support for the Compaq StorageWorks Fibre
  3.8169 -  Channel 64-bit/66Mhz Host Bus Adapter.
  3.8170 -
  3.8171 -  If you want to compile the driver as a module ( = code which can be
  3.8172 -  inserted in and removed from the running kernel whenever you want),
  3.8173 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.8174 -  will be called cpqfc.o.
  3.8175 -
  3.8176 -DMX3191D SCSI support
  3.8177 -CONFIG_SCSI_DMX3191D
  3.8178 -  This is support for Domex DMX3191D SCSI Host Adapters.
  3.8179 -
  3.8180 -  This driver is also available as a module ( = code which can be
  3.8181 -  inserted in and removed from the running kernel whenever you want).
  3.8182 -  The module will be called dmx3191d.o.  If you want to compile it as
  3.8183 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.8184 -
  3.8185 -DTC3180/3280 SCSI support
  3.8186 -CONFIG_SCSI_DTC3280
  3.8187 -  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
  3.8188 -  the SCSI-HOWTO, available from
  3.8189 -  <http://www.tldp.org/docs.html#howto>, and the file
  3.8190 -  <file:drivers/scsi/README.dtc3x80>.
  3.8191 -
  3.8192 -  This driver is also available as a module ( = code which can be
  3.8193 -  inserted in and removed from the running kernel whenever you want).
  3.8194 -  The module will be called dtc.o.  If you want to compile it as a
  3.8195 -  module, say M here and read <file:Documentation/modules.txt>.
  3.8196 -
  3.8197 -EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
  3.8198 -CONFIG_SCSI_EATA_DMA
  3.8199 -  This is support for the EATA-DMA protocol compliant SCSI Host
  3.8200 -  Adapters like the SmartCache III/IV, SmartRAID controller families
  3.8201 -  and the DPT PM2011B and PM2012B controllers.
  3.8202 -
  3.8203 -  Note that this driver is obsolete; if you have one of the above
  3.8204 -  SCSI Host Adapters, you should normally say N here and Y to "EATA
  3.8205 -  ISA/EISA/PCI support", below.  Please read the SCSI-HOWTO, available
  3.8206 -  from <http://www.tldp.org/docs.html#howto>.
  3.8207 -
  3.8208 -  This driver is also available as a module ( = code which can be
  3.8209 -  inserted in and removed from the running kernel whenever you want).
  3.8210 -  The module will be called eata_dma.o.  If you want to compile it as
  3.8211 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.8212 -
  3.8213 -EATA-PIO (old DPT PM2001, PM2012A) support
  3.8214 -CONFIG_SCSI_EATA_PIO
  3.8215 -  This driver supports all EATA-PIO protocol compliant SCSI Host
  3.8216 -  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
  3.8217 -  host adapters could also use this driver but are discouraged from
  3.8218 -  doing so, since this driver only supports hard disks and lacks
  3.8219 -  numerous features.  You might want to have a look at the SCSI-HOWTO,
  3.8220 -  available from <http://www.tldp.org/docs.html#howto>.
  3.8221 -
  3.8222 -  If you want to compile this as a module ( = code which can be
  3.8223 -  inserted in and removed from the running kernel whenever you want),
  3.8224 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.8225 -  will be called eata_pio.o.
  3.8226 -
  3.8227 -UltraStor 14F/34F support
  3.8228 -CONFIG_SCSI_U14_34F
  3.8229 -  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
  3.8230 -  The source at <file:drivers/scsi/u14-34f.c> contains some
  3.8231 -  information about this hardware.  If the driver doesn't work out of
  3.8232 -  the box, you may have to change some settings in
  3.8233 -  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
  3.8234 -  <http://www.tldp.org/docs.html#howto>.  Note that there is also
  3.8235 -  another driver for the same hardware: "UltraStor SCSI support",
  3.8236 -  below.  You should say Y to both only if you want 24F support as
  3.8237 -  well.
  3.8238 -
  3.8239 -  This driver is also available as a module ( = code which can be
  3.8240 -  inserted in and removed from the running kernel whenever you want).
  3.8241 -  The module will be called u14-34f.o.  If you want to compile it as a
  3.8242 -  module, say M here and read <file:Documentation/modules.txt>.
  3.8243 -
  3.8244 -enable elevator sorting
  3.8245 -CONFIG_SCSI_U14_34F_LINKED_COMMANDS
  3.8246 -  This option enables elevator sorting for all probed SCSI disks and
  3.8247 -  CD-ROMs. It definitely reduces the average seek distance when doing
  3.8248 -  random seeks, but this does not necessarily result in a noticeable
  3.8249 -  performance improvement: your mileage may vary...
  3.8250 -
  3.8251 -  The safe answer is N.
  3.8252 -
  3.8253 -maximum number of queued commands
  3.8254 -CONFIG_SCSI_U14_34F_MAX_TAGS
  3.8255 -  This specifies how many SCSI commands can be maximally queued for
  3.8256 -  each probed SCSI device. You should reduce the default value of 8
  3.8257 -  only if you have disks with buggy or limited tagged command support.
  3.8258 -  Minimum is 2 and maximum is 14. This value is also the window size
  3.8259 -  used by the elevator sorting option above. The effective value used
  3.8260 -  by the driver for each probed SCSI device is reported at boot time.
  3.8261 -
  3.8262 -Future Domain 16xx SCSI/AHA-2920A support
  3.8263 -CONFIG_SCSI_FUTURE_DOMAIN
  3.8264 -  This is support for Future Domain's 16-bit SCSI host adapters
  3.8265 -  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
  3.8266 -  other adapters based on the Future Domain chipsets (Quantum
  3.8267 -  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
  3.8268 -  It is explained in section 3.7 of the SCSI-HOWTO, available from
  3.8269 -  <http://www.tldp.org/docs.html#howto>.
  3.8270 -
  3.8271 -  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
  3.8272 -  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
  3.8273 -  controller support"). This Future Domain driver works with the older
  3.8274 -  Adaptec AHA-2920A boards with a Future Domain chip on them.
  3.8275 -
  3.8276 -  This driver is also available as a module ( = code which can be
  3.8277 -  inserted in and removed from the running kernel whenever you want).
  3.8278 -  The module will be called fdomain.o. If you want to compile it as a
  3.8279 -  module, say M here and read <file:Documentation/modules.txt>.
  3.8280 -
  3.8281 -Future Domain MCS-600/700 SCSI support
  3.8282 -CONFIG_SCSI_FD_MCS
  3.8283 -  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
  3.8284 -  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
  3.8285 -  is identical to the MCS 700 and hence also supported by this driver.
  3.8286 -  This driver also supports the Reply SB16/SCSI card (the SCSI part).
  3.8287 -  It supports multiple adapters in the same system.
  3.8288 -
  3.8289 -  This driver is also available as a module ( = code which can be
  3.8290 -  inserted in and removed from the running kernel whenever you want).
  3.8291 -  The module will be called fd_mcs.o. If you want to compile it as a
  3.8292 -  module, say M here and read <file:Documentation/modules.txt>.
  3.8293 -
  3.8294 -Generic NCR5380/53c400 SCSI support
  3.8295 -CONFIG_SCSI_GENERIC_NCR5380
  3.8296 -  This is the generic NCR family of SCSI controllers, not to be
  3.8297 -  confused with the NCR 53c7 or 8xx controllers.  It is explained in
  3.8298 -  section 3.8 of the SCSI-HOWTO, available from
  3.8299 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  3.8300 -  of the box, you may have to change some settings in
  3.8301 -  <file:drivers/scsi/g_NCR5380.h>.
  3.8302 -
  3.8303 -  This driver is also available as a module ( = code which can be
  3.8304 -  inserted in and removed from the running kernel whenever you want).
  3.8305 -  The module will be called g_NCR5380.o.  If you want to compile it as
  3.8306 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.8307 -
  3.8308 -Enable NCR53c400 extensions
  3.8309 -CONFIG_SCSI_GENERIC_NCR53C400
  3.8310 -  This enables certain optimizations for the NCR53c400 SCSI cards.
  3.8311 -  You might as well try it out.  Note that this driver will only probe
  3.8312 -  for the Trantor T130B in its default configuration; you might have
  3.8313 -  to pass a command line option to the kernel at boot time if it does
  3.8314 -  not detect your card.  See the file
  3.8315 -  <file:drivers/scsi/README.g_NCR5380> for details.
  3.8316 -
  3.8317 -# Choice: ncr5380
  3.8318 -NCR5380/53c400 mapping method (use Port for T130B)
  3.8319 -CONFIG_SCSI_G_NCR5380_PORT
  3.8320 -  The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
  3.8321 -  port or memory mapped. You should know what you have. The most
  3.8322 -  common card, Trantor T130B, uses port mapped mode.
  3.8323 -
  3.8324 -NCR Dual 700 MCA SCSI support
  3.8325 -CONFIG_SCSI_NCR_D700
  3.8326 -  This is a driver for the MicroChannel Dual 700 card produced by
  3.8327 -  NCR and commonly used in 345x/35xx/4100 class machines.  It always
  3.8328 -  tries to negotiate sync and uses tag command queueing.
  3.8329 -
  3.8330 -  Unless you have an NCR manufactured machine, the chances are that
  3.8331 -  you do not have this SCSI card, so say N.
  3.8332 -
  3.8333 -  If you want to compile the driver as a module ( = code which can be
  3.8334 -  inserted in and removed from the running kernel whenever you want),
  3.8335 -  say M here and read <file:Documentation/modules.txt>.  The module
  3.8336 -  will be called NCR_D700.o.
  3.8337 -
  3.8338 -HP LASI SCSI support for 53c700/710
  3.8339 -CONFIG_SCSI_LASI700
  3.8340 -  This is a driver for the lasi baseboard in some parisc machines
  3.8341 -  which is based on the 53c700 chip.  Will also support LASI subsystems
  3.8342 -  based on the 710 chip using 700 emulation mode.
  3.8343 -
  3.8344 -  Unless you know you have a 53c700 or 53c710 based lasi, say N here
  3.8345 -
  3.8346 -NCR53c7,8xx SCSI support
  3.8347 -CONFIG_SCSI_NCR53C7xx
  3.8348 -  This is a driver for the 53c7 and 8xx NCR family of SCSI
  3.8349 -  controllers, not to be confused with the NCR 5380 controllers.  It
  3.8350 -  is explained in section 3.8 of the SCSI-HOWTO, available from
  3.8351 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  3.8352 -  of the box, you may have to change some settings in
  3.8353 -  <file:drivers/scsi/53c7,8xx.h>.  Please read
  3.8354 -  <file:drivers/scsi/README.ncr53c7xx> for the available boot time
  3.8355 -  command line options.
  3.8356 -
  3.8357 -  Note: there is another driver for the 53c8xx family of controllers
  3.8358 -  ("NCR53C8XX SCSI support" below).  If you want to use them both, you
  3.8359 -  need to say M to both and build them as modules, but only one may be
  3.8360 -  active at a time. If you have a 53c8xx board, it's better to use the
  3.8361 -  other driver.
  3.8362 -
  3.8363 -  This driver is also available as a module ( = code which can be
  3.8364 -  inserted in and removed from the running kernel whenever you want).
  3.8365 -  The module will be called 53c7,8xx.o.  If you want to compile it as
  3.8366 -  a module, say M here and read <file:Documentation/modules.txt>.
  3.8367 -
  3.8368 -Always negotiate synchronous transfers
  3.8369 -CONFIG_SCSI_NCR53C7xx_sync
  3.8370 -  In general, this is good; however, it is a bit dangerous since there
  3.8371 -  are some broken SCSI devices out there. Take your chances. Safe bet
  3.8372 -  is N.
  3.8373 -
  3.8374 -Allow FAST-SCSI [10MHz]
  3.8375 -CONFIG_SCSI_NCR53C7xx_FAST
  3.8376 -  This will enable 10MHz FAST-SCSI transfers with your host
  3.8377 -  adapter. Some systems have problems with that speed, so it's safest
  3.8378 -  to say N here.
  3.8379 -
  3.8380 -Allow DISCONNECT
  3.8381 -CONFIG_SCSI_NCR53C7xx_DISCONNECT
  3.8382 -  This enables the disconnect/reconnect feature of the NCR SCSI
  3.8383 -  controller. When you say Y here, a slow SCSI device will not lock
  3.8384 -  the SCSI bus while processing a request, allowing simultaneous use
  3.8385 -  of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
  3.8386 -  providing much better performance when using slow and fast SCSI
  3.8387 -  devices at the same time. Some devices, however, do not operate
  3.8388 -  properly with this option enabled, and will cause your SCSI system
  3.8389