1.1 --- a/.rootkeys	Fri Sep 05 09:33:55 2003 +0000
     1.2 +++ b/.rootkeys	Sat Sep 06 00:40:18 2003 +0000
     1.3 @@ -508,91 +508,91 @@ 3eb3c87fPL2T_zBb0bHlbZY-ACEKRw xen/tools
     1.4  3eb3c87fmKYTC5GCh_rydFakZp9ayw xen/tools/figlet/README
     1.5  3eb3c87fdQKQ5OBGbM-KjZfi9Us4ng xen/tools/figlet/figlet.c
     1.6  3eb3c87fS7DNbg0i6yhFs28UIqAK5g xen/tools/figlet/xen.flf
     1.7 -3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.21-sparse/Documentation/Configure.help
     1.8 -3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.21-sparse/Makefile
     1.9 -3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.21-sparse/arch/xeno/Makefile
    1.10 -3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.21-sparse/arch/xeno/boot/Makefile
    1.11 -3e5a4e65OV_j_DBtjzt5vej771AJsA xenolinux-2.4.21-sparse/arch/xeno/config.in
    1.12 -3e5a4e65TNEycLeXqPSXQJQm_xGecA xenolinux-2.4.21-sparse/arch/xeno/defconfig
    1.13 -3e6377f5xwPfYZkPHPrDbEq1PRN7uQ xenolinux-2.4.21-sparse/arch/xeno/drivers/balloon/Makefile
    1.14 -3e6377f8Me8IqtvEhb70XFgOvqQH7A xenolinux-2.4.21-sparse/arch/xeno/drivers/balloon/balloon.c
    1.15 -3e6377fbMjXWAQd0XN0FWv4fDEo6fg xenolinux-2.4.21-sparse/arch/xeno/drivers/balloon/dom_mem_ops.h
    1.16 -3e5a4e65iHEuC5sjFhj42XALYbLVRw xenolinux-2.4.21-sparse/arch/xeno/drivers/block/Makefile
    1.17 -3e5a4e65pP5spJErBW69pJxSSdK9RA xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_block.c
    1.18 -3e67f822FOPwqHiaRKbrskgWgoNL5g xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_block.h
    1.19 -3e677190SjkzJIvFifRVeYpIZOCtYA xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_ide.c
    1.20 -3e677193nOKKTLJzcAu4SYdbZaia8g xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_scsi.c
    1.21 -3e676eb5RXnHzSHgA1BvM0B1aIm4qg xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_segment.c
    1.22 -3e5d129aDldt6geU2-2SzBae34sQzg xenolinux-2.4.21-sparse/arch/xeno/drivers/block/xl_segment_proc.c
    1.23 -3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ xenolinux-2.4.21-sparse/arch/xeno/drivers/console/Makefile
    1.24 -3e5a4e651TH-SXHoufurnWjgl5bfOA xenolinux-2.4.21-sparse/arch/xeno/drivers/console/console.c
    1.25 -3e5a4e656nfFISThfbyXQOA6HN6YHw xenolinux-2.4.21-sparse/arch/xeno/drivers/dom0/Makefile
    1.26 -3e5a4e65BXtftInNHUC2PjDfPhdZZA xenolinux-2.4.21-sparse/arch/xeno/drivers/dom0/dom0_core.c
    1.27 -3e5a4e65gfn_ltB8ujHMVFApnTTNRQ xenolinux-2.4.21-sparse/arch/xeno/drivers/dom0/vfr.c
    1.28 -3e5a4e65gZBRBB6RsSVg1c9iahigAw xenolinux-2.4.21-sparse/arch/xeno/drivers/network/Makefile
    1.29 -3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ xenolinux-2.4.21-sparse/arch/xeno/drivers/network/network.c
    1.30 -3e5a4e65lWzkiPXsZdzPt2RNnJGG1g xenolinux-2.4.21-sparse/arch/xeno/kernel/Makefile
    1.31 -3e5a4e65_hqfuxtGG8IUy6wRM86Ecg xenolinux-2.4.21-sparse/arch/xeno/kernel/entry.S
    1.32 -3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg xenolinux-2.4.21-sparse/arch/xeno/kernel/head.S
    1.33 -3e5a4e65ibVQmwlOn0j3sVH_j_6hAg xenolinux-2.4.21-sparse/arch/xeno/kernel/hypervisor.c
    1.34 -3e5a4e65RMGcuA-HCn3-wNx3fFQwdg xenolinux-2.4.21-sparse/arch/xeno/kernel/i386_ksyms.c
    1.35 -3e5a4e65MEvZhlr070sK5JsfAQlv7Q xenolinux-2.4.21-sparse/arch/xeno/kernel/ioport.c
    1.36 -3e5a4e653U6cELGv528IxOLHvCq8iA xenolinux-2.4.21-sparse/arch/xeno/kernel/irq.c
    1.37 -3e5a4e65muT6SU3ck47IP87Q7Ti5hA xenolinux-2.4.21-sparse/arch/xeno/kernel/ldt.c
    1.38 -3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ xenolinux-2.4.21-sparse/arch/xeno/kernel/process.c
    1.39 -3e5a4e66tR-qJMLj3MppcKqmvuI2XQ xenolinux-2.4.21-sparse/arch/xeno/kernel/setup.c
    1.40 -3e5a4e66fWSTagLGU2P8BGFGRjhDiw xenolinux-2.4.21-sparse/arch/xeno/kernel/signal.c
    1.41 -3e5a4e66N__lUXNwzQ-eADRzK9LXuQ xenolinux-2.4.21-sparse/arch/xeno/kernel/time.c
    1.42 -3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ xenolinux-2.4.21-sparse/arch/xeno/kernel/traps.c
    1.43 -3e5a4e66-9_NczrVMbuQkoSLyXckIw xenolinux-2.4.21-sparse/arch/xeno/lib/Makefile
    1.44 -3e5a4e6637ZDk0BvFEC-aFQs599-ng xenolinux-2.4.21-sparse/arch/xeno/lib/delay.c
    1.45 -3e5a4e66croVgpcJyJuF2ycQw0HuJw xenolinux-2.4.21-sparse/arch/xeno/mm/Makefile
    1.46 -3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg xenolinux-2.4.21-sparse/arch/xeno/mm/fault.c
    1.47 -3e5a4e668SE9rixq4ahho9rNhLUUFQ xenolinux-2.4.21-sparse/arch/xeno/mm/hypervisor.c
    1.48 -3e5a4e661gLzzff25pJooKIIWe7IWg xenolinux-2.4.21-sparse/arch/xeno/mm/init.c
    1.49 -3f0bed43UUdQichXAiVNrjV-y2Kzcg xenolinux-2.4.21-sparse/arch/xeno/mm/ioremap.c
    1.50 -3e5a4e66qRlSTcjafidMB6ulECADvg xenolinux-2.4.21-sparse/arch/xeno/vmlinux.lds
    1.51 -3ea53c6em6uzVHSiGqrbbAVofyRY_g xenolinux-2.4.21-sparse/drivers/block/genhd.c
    1.52 -3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.21-sparse/drivers/block/ll_rw_blk.c
    1.53 -3f108aeaLcGDgQdFAANLTUEid0a05w xenolinux-2.4.21-sparse/drivers/char/mem.c
    1.54 -3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.21-sparse/drivers/char/tty_io.c
    1.55 -3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.21-sparse/fs/exec.c
    1.56 -3f05a939l8s0eQb_fpMvYiI06cTGlA xenolinux-2.4.21-sparse/fs/partitions/Config.in
    1.57 -3f05a939W65febbeWrBtuQgsQDK2Bg xenolinux-2.4.21-sparse/fs/partitions/Makefile
    1.58 -3f05a939phguW4R5PelNQZ8o_EcYZA xenolinux-2.4.21-sparse/fs/partitions/check.c
    1.59 -3f05a939ZSKN7gX2sfTLzPcYJvPkcQ xenolinux-2.4.21-sparse/fs/partitions/xeno.c
    1.60 -3f05a939_I9vPADPgyVBwUDUxtoeOQ xenolinux-2.4.21-sparse/fs/partitions/xeno.h
    1.61 -3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.21-sparse/include/asm-xeno/bugs.h
    1.62 -3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.21-sparse/include/asm-xeno/desc.h
    1.63 -3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.21-sparse/include/asm-xeno/fixmap.h
    1.64 -3e5a4e67w_DWgjIJ17Tlossu1LGujQ xenolinux-2.4.21-sparse/include/asm-xeno/highmem.h
    1.65 -3e5a4e67YtcyDLQsShhCfQwPSELfvA xenolinux-2.4.21-sparse/include/asm-xeno/hw_irq.h
    1.66 -3e5a4e677VBavzM1UZIEcH1B-RlXMA xenolinux-2.4.21-sparse/include/asm-xeno/hypervisor.h
    1.67 -3e5a4e673p7PEOyHFm3nHkYX6HQYBg xenolinux-2.4.21-sparse/include/asm-xeno/irq.h
    1.68 -3ead095db_LRUXnxaqs0dA1DWhPoQQ xenolinux-2.4.21-sparse/include/asm-xeno/keyboard.h
    1.69 -3e5a4e678ddsQOpbSiRdy1GRcDc9WA xenolinux-2.4.21-sparse/include/asm-xeno/mmu_context.h
    1.70 -3e7270deQqtGPSnFxcW4AvJZuTUWfg xenolinux-2.4.21-sparse/include/asm-xeno/multicall.h
    1.71 -3e5a4e67mnQfh-R8KcQCaVo2Oho6yg xenolinux-2.4.21-sparse/include/asm-xeno/page.h
    1.72 -3e5a4e67uTYU5oEnIDjxuaez8njjqg xenolinux-2.4.21-sparse/include/asm-xeno/pgalloc.h
    1.73 -3e5a4e67X7JyupgdYkgDX19Huj2sAw xenolinux-2.4.21-sparse/include/asm-xeno/pgtable-2level.h
    1.74 -3e5a4e67gr4NLGtQ5CvSLimMYZlkOA xenolinux-2.4.21-sparse/include/asm-xeno/pgtable.h
    1.75 -3f108af1qNv8DVSGPv4zpqIU1txCkg xenolinux-2.4.21-sparse/include/asm-xeno/proc_cmd.h
    1.76 -3e5a4e676uK4xErTBDH6XJREn9LSyg xenolinux-2.4.21-sparse/include/asm-xeno/processor.h
    1.77 -3e5a4e67AJPjW-zL7p-xWuA6IVeH1g xenolinux-2.4.21-sparse/include/asm-xeno/ptrace.h
    1.78 -3e5a4e68uJz-xI0IBVMD7xRLQKJDFg xenolinux-2.4.21-sparse/include/asm-xeno/segment.h
    1.79 -3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA xenolinux-2.4.21-sparse/include/asm-xeno/smp.h
    1.80 -3e5a4e68mTr0zcp9SXDbnd-XLrrfxw xenolinux-2.4.21-sparse/include/asm-xeno/system.h
    1.81 -3f1056a9L_kqHcFheV00KbKBzv9j5w xenolinux-2.4.21-sparse/include/asm-xeno/vga.h
    1.82 -3f056927gMHl7mWB89rb73JahbhQIA xenolinux-2.4.21-sparse/include/linux/blk.h
    1.83 -3e5a4e68WLX3B8owTvktP3HHOtznPQ xenolinux-2.4.21-sparse/include/linux/major.h
    1.84 -3e5a4e686V0nioX2ZpFf056sgvdiQw xenolinux-2.4.21-sparse/include/linux/sunrpc/debug.h
    1.85 -3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ xenolinux-2.4.21-sparse/init/do_mounts.c
    1.86 -3e5a4e68TJJavrunYwTAnLRSBxSYqQ xenolinux-2.4.21-sparse/kernel/panic.c
    1.87 -3f1056a9LXNTgSzITNh1mb-MIKV1Ng xenolinux-2.4.21-sparse/kernel/printk.c
    1.88 -3eba8f878XjouY21EkQBXwYBsPsipQ xenolinux-2.4.21-sparse/lndir-rel
    1.89 -3e6e7c1efbQe93xCvOpOVCnXTMmQ5w xenolinux-2.4.21-sparse/mkbuildtree
    1.90 -3e5a4e68GxCIaFH4sy01v1wjapetaA xenolinux-2.4.21-sparse/mm/memory.c
    1.91 -3f108af5VxPkLv13tXpXgoRKALQtXQ xenolinux-2.4.21-sparse/mm/mprotect.c
    1.92 -3e5a4e681xMPdF9xCMwpyfuYMySU5g xenolinux-2.4.21-sparse/mm/mremap.c
    1.93 -3e5a4e683HKVU-sxtagrDasRB8eBVw xenolinux-2.4.21-sparse/mm/swapfile.c
    1.94 -3f108af81Thhb242EmKjGCYkjx-GJA xenolinux-2.4.21-sparse/mm/vmalloc.c
    1.95 +3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.22-sparse/Documentation/Configure.help
    1.96 +3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.22-sparse/Makefile
    1.97 +3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.22-sparse/arch/xeno/Makefile
    1.98 +3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.22-sparse/arch/xeno/boot/Makefile
    1.99 +3e5a4e65OV_j_DBtjzt5vej771AJsA xenolinux-2.4.22-sparse/arch/xeno/config.in
   1.100 +3e5a4e65TNEycLeXqPSXQJQm_xGecA xenolinux-2.4.22-sparse/arch/xeno/defconfig
   1.101 +3e6377f5xwPfYZkPHPrDbEq1PRN7uQ xenolinux-2.4.22-sparse/arch/xeno/drivers/balloon/Makefile
   1.102 +3e6377f8Me8IqtvEhb70XFgOvqQH7A xenolinux-2.4.22-sparse/arch/xeno/drivers/balloon/balloon.c
   1.103 +3e6377fbMjXWAQd0XN0FWv4fDEo6fg xenolinux-2.4.22-sparse/arch/xeno/drivers/balloon/dom_mem_ops.h
   1.104 +3e5a4e65iHEuC5sjFhj42XALYbLVRw xenolinux-2.4.22-sparse/arch/xeno/drivers/block/Makefile
   1.105 +3e5a4e65pP5spJErBW69pJxSSdK9RA xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_block.c
   1.106 +3e67f822FOPwqHiaRKbrskgWgoNL5g xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_block.h
   1.107 +3e677190SjkzJIvFifRVeYpIZOCtYA xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_ide.c
   1.108 +3e677193nOKKTLJzcAu4SYdbZaia8g xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_scsi.c
   1.109 +3e676eb5RXnHzSHgA1BvM0B1aIm4qg xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_segment.c
   1.110 +3e5d129aDldt6geU2-2SzBae34sQzg xenolinux-2.4.22-sparse/arch/xeno/drivers/block/xl_segment_proc.c
   1.111 +3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ xenolinux-2.4.22-sparse/arch/xeno/drivers/console/Makefile
   1.112 +3e5a4e651TH-SXHoufurnWjgl5bfOA xenolinux-2.4.22-sparse/arch/xeno/drivers/console/console.c
   1.113 +3e5a4e656nfFISThfbyXQOA6HN6YHw xenolinux-2.4.22-sparse/arch/xeno/drivers/dom0/Makefile
   1.114 +3e5a4e65BXtftInNHUC2PjDfPhdZZA xenolinux-2.4.22-sparse/arch/xeno/drivers/dom0/dom0_core.c
   1.115 +3e5a4e65gfn_ltB8ujHMVFApnTTNRQ xenolinux-2.4.22-sparse/arch/xeno/drivers/dom0/vfr.c
   1.116 +3e5a4e65gZBRBB6RsSVg1c9iahigAw xenolinux-2.4.22-sparse/arch/xeno/drivers/network/Makefile
   1.117 +3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ xenolinux-2.4.22-sparse/arch/xeno/drivers/network/network.c
   1.118 +3e5a4e65lWzkiPXsZdzPt2RNnJGG1g xenolinux-2.4.22-sparse/arch/xeno/kernel/Makefile
   1.119 +3e5a4e65_hqfuxtGG8IUy6wRM86Ecg xenolinux-2.4.22-sparse/arch/xeno/kernel/entry.S
   1.120 +3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg xenolinux-2.4.22-sparse/arch/xeno/kernel/head.S
   1.121 +3e5a4e65ibVQmwlOn0j3sVH_j_6hAg xenolinux-2.4.22-sparse/arch/xeno/kernel/hypervisor.c
   1.122 +3e5a4e65RMGcuA-HCn3-wNx3fFQwdg xenolinux-2.4.22-sparse/arch/xeno/kernel/i386_ksyms.c
   1.123 +3e5a4e65MEvZhlr070sK5JsfAQlv7Q xenolinux-2.4.22-sparse/arch/xeno/kernel/ioport.c
   1.124 +3e5a4e653U6cELGv528IxOLHvCq8iA xenolinux-2.4.22-sparse/arch/xeno/kernel/irq.c
   1.125 +3e5a4e65muT6SU3ck47IP87Q7Ti5hA xenolinux-2.4.22-sparse/arch/xeno/kernel/ldt.c
   1.126 +3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ xenolinux-2.4.22-sparse/arch/xeno/kernel/process.c
   1.127 +3e5a4e66tR-qJMLj3MppcKqmvuI2XQ xenolinux-2.4.22-sparse/arch/xeno/kernel/setup.c
   1.128 +3e5a4e66fWSTagLGU2P8BGFGRjhDiw xenolinux-2.4.22-sparse/arch/xeno/kernel/signal.c
   1.129 +3e5a4e66N__lUXNwzQ-eADRzK9LXuQ xenolinux-2.4.22-sparse/arch/xeno/kernel/time.c
   1.130 +3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ xenolinux-2.4.22-sparse/arch/xeno/kernel/traps.c
   1.131 +3e5a4e66-9_NczrVMbuQkoSLyXckIw xenolinux-2.4.22-sparse/arch/xeno/lib/Makefile
   1.132 +3e5a4e6637ZDk0BvFEC-aFQs599-ng xenolinux-2.4.22-sparse/arch/xeno/lib/delay.c
   1.133 +3e5a4e66croVgpcJyJuF2ycQw0HuJw xenolinux-2.4.22-sparse/arch/xeno/mm/Makefile
   1.134 +3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg xenolinux-2.4.22-sparse/arch/xeno/mm/fault.c
   1.135 +3e5a4e668SE9rixq4ahho9rNhLUUFQ xenolinux-2.4.22-sparse/arch/xeno/mm/hypervisor.c
   1.136 +3e5a4e661gLzzff25pJooKIIWe7IWg xenolinux-2.4.22-sparse/arch/xeno/mm/init.c
   1.137 +3f0bed43UUdQichXAiVNrjV-y2Kzcg xenolinux-2.4.22-sparse/arch/xeno/mm/ioremap.c
   1.138 +3e5a4e66qRlSTcjafidMB6ulECADvg xenolinux-2.4.22-sparse/arch/xeno/vmlinux.lds
   1.139 +3ea53c6em6uzVHSiGqrbbAVofyRY_g xenolinux-2.4.22-sparse/drivers/block/genhd.c
   1.140 +3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.22-sparse/drivers/block/ll_rw_blk.c
   1.141 +3f108aeaLcGDgQdFAANLTUEid0a05w xenolinux-2.4.22-sparse/drivers/char/mem.c
   1.142 +3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.22-sparse/drivers/char/tty_io.c
   1.143 +3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.22-sparse/fs/exec.c
   1.144 +3f05a939l8s0eQb_fpMvYiI06cTGlA xenolinux-2.4.22-sparse/fs/partitions/Config.in
   1.145 +3f05a939W65febbeWrBtuQgsQDK2Bg xenolinux-2.4.22-sparse/fs/partitions/Makefile
   1.146 +3f05a939phguW4R5PelNQZ8o_EcYZA xenolinux-2.4.22-sparse/fs/partitions/check.c
   1.147 +3f05a939ZSKN7gX2sfTLzPcYJvPkcQ xenolinux-2.4.22-sparse/fs/partitions/xeno.c
   1.148 +3f05a939_I9vPADPgyVBwUDUxtoeOQ xenolinux-2.4.22-sparse/fs/partitions/xeno.h
   1.149 +3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.22-sparse/include/asm-xeno/bugs.h
   1.150 +3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.22-sparse/include/asm-xeno/desc.h
   1.151 +3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.22-sparse/include/asm-xeno/fixmap.h
   1.152 +3e5a4e67w_DWgjIJ17Tlossu1LGujQ xenolinux-2.4.22-sparse/include/asm-xeno/highmem.h
   1.153 +3e5a4e67YtcyDLQsShhCfQwPSELfvA xenolinux-2.4.22-sparse/include/asm-xeno/hw_irq.h
   1.154 +3e5a4e677VBavzM1UZIEcH1B-RlXMA xenolinux-2.4.22-sparse/include/asm-xeno/hypervisor.h
   1.155 +3e5a4e673p7PEOyHFm3nHkYX6HQYBg xenolinux-2.4.22-sparse/include/asm-xeno/irq.h
   1.156 +3ead095db_LRUXnxaqs0dA1DWhPoQQ xenolinux-2.4.22-sparse/include/asm-xeno/keyboard.h
   1.157 +3e5a4e678ddsQOpbSiRdy1GRcDc9WA xenolinux-2.4.22-sparse/include/asm-xeno/mmu_context.h
   1.158 +3e7270deQqtGPSnFxcW4AvJZuTUWfg xenolinux-2.4.22-sparse/include/asm-xeno/multicall.h
   1.159 +3e5a4e67mnQfh-R8KcQCaVo2Oho6yg xenolinux-2.4.22-sparse/include/asm-xeno/page.h
   1.160 +3e5a4e67uTYU5oEnIDjxuaez8njjqg xenolinux-2.4.22-sparse/include/asm-xeno/pgalloc.h
   1.161 +3e5a4e67X7JyupgdYkgDX19Huj2sAw xenolinux-2.4.22-sparse/include/asm-xeno/pgtable-2level.h
   1.162 +3e5a4e67gr4NLGtQ5CvSLimMYZlkOA xenolinux-2.4.22-sparse/include/asm-xeno/pgtable.h
   1.163 +3f108af1qNv8DVSGPv4zpqIU1txCkg xenolinux-2.4.22-sparse/include/asm-xeno/proc_cmd.h
   1.164 +3e5a4e676uK4xErTBDH6XJREn9LSyg xenolinux-2.4.22-sparse/include/asm-xeno/processor.h
   1.165 +3e5a4e67AJPjW-zL7p-xWuA6IVeH1g xenolinux-2.4.22-sparse/include/asm-xeno/ptrace.h
   1.166 +3e5a4e68uJz-xI0IBVMD7xRLQKJDFg xenolinux-2.4.22-sparse/include/asm-xeno/segment.h
   1.167 +3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA xenolinux-2.4.22-sparse/include/asm-xeno/smp.h
   1.168 +3e5a4e68mTr0zcp9SXDbnd-XLrrfxw xenolinux-2.4.22-sparse/include/asm-xeno/system.h
   1.169 +3f1056a9L_kqHcFheV00KbKBzv9j5w xenolinux-2.4.22-sparse/include/asm-xeno/vga.h
   1.170 +3f056927gMHl7mWB89rb73JahbhQIA xenolinux-2.4.22-sparse/include/linux/blk.h
   1.171 +3e5a4e68WLX3B8owTvktP3HHOtznPQ xenolinux-2.4.22-sparse/include/linux/major.h
   1.172 +3e5a4e686V0nioX2ZpFf056sgvdiQw xenolinux-2.4.22-sparse/include/linux/sunrpc/debug.h
   1.173 +3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ xenolinux-2.4.22-sparse/init/do_mounts.c
   1.174 +3e5a4e68TJJavrunYwTAnLRSBxSYqQ xenolinux-2.4.22-sparse/kernel/panic.c
   1.175 +3f1056a9LXNTgSzITNh1mb-MIKV1Ng xenolinux-2.4.22-sparse/kernel/printk.c
   1.176 +3eba8f878XjouY21EkQBXwYBsPsipQ xenolinux-2.4.22-sparse/lndir-rel
   1.177 +3e6e7c1efbQe93xCvOpOVCnXTMmQ5w xenolinux-2.4.22-sparse/mkbuildtree
   1.178 +3e5a4e68GxCIaFH4sy01v1wjapetaA xenolinux-2.4.22-sparse/mm/memory.c
   1.179 +3f108af5VxPkLv13tXpXgoRKALQtXQ xenolinux-2.4.22-sparse/mm/mprotect.c
   1.180 +3e5a4e681xMPdF9xCMwpyfuYMySU5g xenolinux-2.4.22-sparse/mm/mremap.c
   1.181 +3e5a4e683HKVU-sxtagrDasRB8eBVw xenolinux-2.4.22-sparse/mm/swapfile.c
   1.182 +3f108af81Thhb242EmKjGCYkjx-GJA xenolinux-2.4.22-sparse/mm/vmalloc.c

     2.1 --- a/xenolinux-2.4.21-sparse/Documentation/Configure.help	Fri Sep 05 09:33:55 2003 +0000
     2.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.3 @@ -1,26994 +0,0 @@
     2.4 -# Maintained by:
     2.5 -#	Eric S. Raymond <mailto:esr@thyrsus.com>
     2.6 -#	Steven Cole <mailto:elenstev@mesatop.com>
     2.7 -#
     2.8 -# Version 3.01: current with 2.4.19+
     2.9 -#
    2.10 -# Translations of this file available on the WWW:
    2.11 -#
    2.12 -#   - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
    2.13 -#     <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
    2.14 -#   - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
    2.15 -#     <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
    2.16 -#   - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
    2.17 -#     <http://www.traduc.org/kernelfr/>
    2.18 -#   - Polish, by Dominik Mierzejewski <mailto:dmierzej@elka.pw.edu.pl>, at
    2.19 -#     <http://home.elka.pw.edu.pl/~dmierzej/linux/kernel/>
    2.20 -#   - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
    2.21 -#     also includes infrastructure to support different languages.
    2.22 -#   - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
    2.23 -#     <http://www.terra.es/personal7/bella5/traduccions.htm>
    2.24 -#
    2.25 -# To access a document on the WWW, you need to have a direct Internet
    2.26 -# connection and a browser program such as netscape or lynx. If you
    2.27 -# only have email access, you can still use FTP and WWW servers: send
    2.28 -# an email to <mailto:mail-server@rtfm.mit.edu> with the text
    2.29 -#   send usenet/news.answers/internet-services/access-via-email
    2.30 -# in the body of the message.
    2.31 -#
    2.32 -# Information about what a kernel is, what it does, how to patch and
    2.33 -# compile it and much more is contained in the Kernel-HOWTO, available
    2.34 -# at <http://www.tldp.org/docs.html#howto>. Before you start
    2.35 -# compiling, make sure that you have the necessary versions of all
    2.36 -# programs and libraries required to compile and run this kernel; they
    2.37 -# are listed in the <file:Documentation/Changes>. Make sure to read the
    2.38 -# toplevel kernel README file as well.
    2.39 -#
    2.40 -# Format of this file: description<nl>variable<nl>help text<nl><nl>.
    2.41 -# The help texts may contain empty lines, but every non-empty line must
    2.42 -# be indented two positions.  Order of the help texts does not matter,
    2.43 -# however, no variable should be documented twice: if it is, only the
    2.44 -# first occurrence will be used. We try to keep the help texts of related
    2.45 -# variables close together. Lines starting with `#' are ignored. To be
    2.46 -# nice to menuconfig, limit your line length to 70 characters. Use emacs'
    2.47 -# kfill.el to edit and ispell.el to spell check this file or you lose.
    2.48 -#
    2.49 -# Comments of the form "# Choice:" followed by a menu name are used
    2.50 -# internally by the maintainers' consistency-checking tools.
    2.51 -#
    2.52 -# If you add a help text to this file, please try to be as gentle as
    2.53 -# possible. Don't use unexplained acronyms and generally write for the
    2.54 -# hypothetical ignorant but intelligent user who has just bought a PC,
    2.55 -# removed Windows, installed Linux and is now recompiling the kernel
    2.56 -# for the first time. Tell them what to do if they're unsure. Technical
    2.57 -# information should go in a README in the Documentation directory.
    2.58 -#
    2.59 -# Mention all the relevant READMEs and HOWTOs in the help text.
    2.60 -# Make them file URLs relative to the top level of the source tree so
    2.61 -# that help browsers can turn them into hotlinks.  All URLs should be
    2.62 -# surrounded by <>.
    2.63 -#
    2.64 -# Repetitions are fine since the help texts are not meant to be read
    2.65 -# in sequence.  It is good style to include URLs pointing to more
    2.66 -# detailed technical information, pictures of the hardware, etc.
    2.67 -#
    2.68 -# The most important thing to include in a help entry is *motivation*.
    2.69 -# Explain why someone configuring a kernel might want to select your
    2.70 -# option.
    2.71 -#
    2.72 -# All this was shamelessly stolen from numerous different sources. Many
    2.73 -# thanks to all the contributors. Feel free to use these help texts in
    2.74 -# your own kernel configuration tools. The texts are copyrighted (c)
    2.75 -# 1995-2000 by Axel Boldt and many others and are governed by the GNU
    2.76 -# General Public License.
    2.77 -
    2.78 -Prompt for development and/or incomplete code/drivers
    2.79 -CONFIG_EXPERIMENTAL
    2.80 -  Some of the various things that Linux supports (such as network
    2.81 -  drivers, file systems, network protocols, etc.) can be in a state
    2.82 -  of development where the functionality, stability, or the level of
    2.83 -  testing is not yet high enough for general use. This is usually
    2.84 -  known as the "alpha-test" phase among developers. If a feature is
    2.85 -  currently in alpha-test, then the developers usually discourage
    2.86 -  uninformed widespread use of this feature by the general public to
    2.87 -  avoid "Why doesn't this work?" type mail messages. However, active
    2.88 -  testing and use of these systems is welcomed. Just be aware that it
    2.89 -  may not meet the normal level of reliability or it may fail to work
    2.90 -  in some special cases. Detailed bug reports from people familiar
    2.91 -  with the kernel internals are usually welcomed by the developers
    2.92 -  (before submitting bug reports, please read the documents
    2.93 -  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
    2.94 -  <file:Documentation/BUG-HUNTING>, and
    2.95 -  <file:Documentation/oops-tracing.txt> in the kernel source).
    2.96 -
    2.97 -  This option will also make obsoleted drivers available. These are
    2.98 -  drivers that have been replaced by something else, and/or are
    2.99 -  scheduled to be removed in a future kernel release.
   2.100 -
   2.101 -  Unless you intend to help test and develop a feature or driver that
   2.102 -  falls into this category, or you have a situation that requires
   2.103 -  using these features, you should probably say N here, which will
   2.104 -  cause the configurator to present you with fewer choices. If
   2.105 -  you say Y here, you will be offered the choice of using features or
   2.106 -  drivers that are currently considered to be in the alpha-test phase.
   2.107 -
   2.108 -Prompt for drivers for obsolete features and hardware
   2.109 -CONFIG_OBSOLETE
   2.110 -  Obsolete drivers have usually been replaced by more recent software
   2.111 -  that can talk to the same hardware.  Obsolete hardware is things
   2.112 -  like MGA monitors that you are very unlikely to see on today's
   2.113 -  systems.
   2.114 -
   2.115 -Symmetric Multi-Processing support
   2.116 -CONFIG_SMP
   2.117 -  This enables support for systems with more than one CPU. If you have
   2.118 -  a system with only one CPU, like most personal computers, say N. If
   2.119 -  you have a system with more than one CPU, say Y.
   2.120 -
   2.121 -  If you say N here, the kernel will run on single and multiprocessor
   2.122 -  machines, but will use only one CPU of a multiprocessor machine. If
   2.123 -  you say Y here, the kernel will run on many, but not all,
   2.124 -  single machines. On a singleprocessor machine, the kernel
   2.125 -  will run faster if you say N here.
   2.126 -
   2.127 -  Note that if you say Y here and choose architecture "586" or
   2.128 -  "Pentium" under "Processor family", the kernel will not work on 486
   2.129 -  architectures. Similarly, multiprocessor kernels for the "PPro"
   2.130 -  architecture may not work on all Pentium based boards.
   2.131 -
   2.132 -  People using multiprocessor machines who say Y here should also say
   2.133 -  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
   2.134 -  Management" code will be disabled if you say Y here.
   2.135 -
   2.136 -  See also the <file:Documentation/smp.tex>,
   2.137 -  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
   2.138 -  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
   2.139 -  <http://www.tldp.org/docs.html#howto>.
   2.140 -
   2.141 -  If you don't know what to do here, say N.
   2.142 -
   2.143 -Intel or compatible 80x86 processor
   2.144 -CONFIG_X86
   2.145 -  This is Linux's home port.  Linux was originally native to the Intel
   2.146 -  386, and runs on all the later x86 processors including the Intel
   2.147 -  486, 586, Pentiums, and various instruction-set-compatible chips by
   2.148 -  AMD, Cyrix, and others.
   2.149 -
   2.150 -Alpha processor
   2.151 -CONFIG_ALPHA
   2.152 -  The Alpha is a 64-bit general-purpose processor designed and
   2.153 -  marketed by the Digital Equipment Corporation of blessed memory, now
   2.154 -  Compaq.  Alpha Linux dates from 1995-1996 and was the first non-x86
   2.155 -  port. The Alpha Linux project has a home page at
   2.156 -  <http://www.alphalinux.org/>.
   2.157 -
   2.158 -32-bit Sun Sparc
   2.159 -CONFIG_SPARC32
   2.160 -  SPARC is a family of RISC microprocessors designed and marketed by
   2.161 -  Sun Microsystems, incorporated.  They are very widely found in Sun
   2.162 -  workstations and clones. This port covers the original 32-bit SPARC;
   2.163 -  it is old and stable and usually considered one of the "big three"
   2.164 -  along with the Intel and Alpha ports.  The UltraLinux project
   2.165 -  maintains both the SPARC32 and SPARC64 ports; its web page is
   2.166 -  available at <http://www.ultralinux.org/>.
   2.167 -
   2.168 -64-bit Sun Sparc
   2.169 -CONFIG_SPARC64
   2.170 -  SPARC is a family of RISC microprocessors designed and marketed by
   2.171 -  Sun Microsystems, incorporated.  This port covers the newer 64-bit
   2.172 -  UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
   2.173 -  SPARC64 ports; its web page is available at
   2.174 -  <http://www.ultralinux.org/>.
   2.175 -
   2.176 -Power PC processor
   2.177 -CONFIG_PPC
   2.178 -  The PowerPC is a very capable 32-bit RISC processor from Motorola,
   2.179 -  the successor to their 68000 and 88000 series.  It powers recent
   2.180 -  Macintoshes and also a widely-used series of single-board computers
   2.181 -  from Motorola.  The Linux PowerPC port has a home page at
   2.182 -  <http://penguinppc.org/>.
   2.183 -
   2.184 -Motorola 68K processors
   2.185 -CONFIG_M68K
   2.186 -  The Motorola 68K microprocessors are now obsolete, having been
   2.187 -  superseded by the PowerPC line also from Motorola.  But they powered
   2.188 -  the first wave of workstation hardware in the 1980s, including Sun
   2.189 -  workstations; they were also the basis of the original Amiga and
   2.190 -  later Atari personal computers.  A lot of this hardware is still
   2.191 -  around.  The m68k project has a home page at
   2.192 -  <http://www.linux-m68k.org/>.
   2.193 -
   2.194 -ARM processors
   2.195 -CONFIG_ARM
   2.196 -  The ARM series is a line of low-power-consumption RISC chip designs
   2.197 -  licensed by ARM ltd and targeted at embedded applications and
   2.198 -  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
   2.199 -  manufactured, but  legacy ARM-based PC hardware remains popular in
   2.200 -  Europe.  There is an ARM Linux project with a web page at
   2.201 -  <http://www.arm.linux.org.uk/>.
   2.202 -
   2.203 -SuperH processors
   2.204 -CONFIG_SUPERH
   2.205 -  The SuperH is a RISC processor targeted for use in embedded systems
   2.206 -  and consumer electronics; it was also used in the Sega Dreamcast
   2.207 -  gaming console.  The SuperH port has a home page at
   2.208 -  <http://www.sh-linux.org/>.
   2.209 -
   2.210 -IA64 processors, including Intel Itanium
   2.211 -CONFIG_IA64
   2.212 -  The Itanium is Intel's 64-bit successor to the 32-bit X86 line.  As
   2.213 -  of early 2001 it is not yet in widespread production use.  The Linux
   2.214 -  IA-64 project has a home page at <http://www.linuxia64.org/>.
   2.215 -
   2.216 -HP PA-RISC processor
   2.217 -CONFIG_PARISC
   2.218 -  The PA-RISC microprocessor is a RISC chip designed by
   2.219 -  Hewlett-Packard and used in their line of workstations.  The PA-RISC
   2.220 -  Linux project has a home page at <www.parisc-linux.org>.
   2.221 -
   2.222 -IBM System/390
   2.223 -CONFIG_S390
   2.224 -  Linux now runs on the venerable System/390 mainframe from IBM, in a
   2.225 -  guest partition under VM.  In fact, over 40,000 simultaneous Linux
   2.226 -  images have been run on a single mainframe!  The S390 Linux project
   2.227 -  has a home page at <http://linux.s390.org/>.
   2.228 -
   2.229 -Axis Communications ETRAX 100LX embedded network CPU
   2.230 -CONFIG_CRIS
   2.231 -  Linux has been ported to run on the Axis Communications ETRAX 100LX
   2.232 -  CPU and the single-board computers built around it, targeted for
   2.233 -  network and embedded applications.  For more information see the
   2.234 -  Axis Communication site, <http://developer.axis.com/>.
   2.235 -
   2.236 -Unsynced TSC support
   2.237 -CONFIG_X86_TSC_DISABLE
   2.238 -  This option is used for getting Linux to run on a NUMA multi-node 
   2.239 -  boxes, laptops and other systems suffering from unsynced TSCs or 
   2.240 -  TSC drift, which can cause gettimeofday to return non-monotonic values. 
   2.241 -  Choosing this option will disable the CONFIG_X86_TSC optimization,
   2.242 -  and allows you to then specify "notsc" as a boot option regardless of 
   2.243 -  which processor you have compiled for. 
   2.244 -  
   2.245 -  NOTE: If your system hangs when init should run, you are probably
   2.246 -  using a i686 compiled glibc which reads the TSC without checking for 
   2.247 -  availability. Boot without "notsc" and install a i386 compiled glibc 
   2.248 -  to solve the problem.
   2.249 -
   2.250 -  If unsure, say N.
   2.251 -
   2.252 -Multiquad support for NUMAQ systems
   2.253 -CONFIG_X86_NUMAQ
   2.254 -  This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
   2.255 -  multiquad box. This changes the way that processors are bootstrapped,
   2.256 -  and uses Clustered Logical APIC addressing mode instead of Flat Logical.
   2.257 -  You will need a new lynxer.elf file to flash your firmware with - send
   2.258 -  email to Martin.Bligh@us.ibm.com
   2.259 -
   2.260 -Support for IBM Summit (EXA) systems
   2.261 -CONFIG_X86_SUMMIT
   2.262 -  This option is needed for IBM systems that use the Summit/EXA chipset.
   2.263 -  (EXA: Extendable Xseries Architecture)In particular, it is needed for 
   2.264 -  the x440 (even for the 4-CPU model).
   2.265 -
   2.266 -  If you don't have this computer, you may safely say N.
   2.267 -
   2.268 -IO-APIC support on uniprocessors
   2.269 -CONFIG_X86_UP_IOAPIC
   2.270 -  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
   2.271 -  SMP-capable replacement for PC-style interrupt controllers. Most
   2.272 -  SMP systems and a small number of uniprocessor systems have one.
   2.273 -  If you have a single-CPU system with an IO-APIC, you can say Y here
   2.274 -  to use it. If you say Y here even though your machine doesn't have
   2.275 -  an IO-APIC, then the kernel will still run with no slowdown at all.
   2.276 -
   2.277 -  If you have a system with several CPUs, you do not need to say Y
   2.278 -  here: the IO-APIC will be used automatically.
   2.279 -
   2.280 -Local APIC Support on Uniprocessors
   2.281 -CONFIG_X86_UP_APIC
   2.282 -  A local APIC (Advanced Programmable Interrupt Controller) is an
   2.283 -  integrated interrupt controller in the CPU. If you have a single-CPU
   2.284 -  system which has a processor with a local APIC, you can say Y here to
   2.285 -  enable and use it. If you say Y here even though your machine doesn't
   2.286 -  have a local APIC, then the kernel will still run with no slowdown at
   2.287 -  all. The local APIC supports CPU-generated self-interrupts (timer,
   2.288 -  performance counters), and the NMI watchdog which detects hard lockups.
   2.289 -
   2.290 -  If you have a system with several CPUs, you do not need to say Y
   2.291 -  here: the local APIC will be used automatically.
   2.292 -
   2.293 -Kernel math emulation
   2.294 -CONFIG_MATH_EMULATION
   2.295 -  Linux can emulate a math coprocessor (used for floating point
   2.296 -  operations) if you don't have one. 486DX and Pentium processors have
   2.297 -  a math coprocessor built in, 486SX and 386 do not, unless you added
   2.298 -  a 487DX or 387, respectively. (The messages during boot time can
   2.299 -  give you some hints here ["man dmesg"].) Everyone needs either a
   2.300 -  coprocessor or this emulation.
   2.301 -
   2.302 -  If you don't have a math coprocessor, you need to say Y here; if you
   2.303 -  say Y here even though you have a coprocessor, the coprocessor will
   2.304 -  be used nevertheless. (This behaviour can be changed with the kernel
   2.305 -  command line option "no387", which comes handy if your coprocessor
   2.306 -  is broken. Try "man bootparam" or see the documentation of your boot
   2.307 -  loader (lilo or loadlin) about how to pass options to the kernel at
   2.308 -  boot time.) This means that it is a good idea to say Y here if you
   2.309 -  intend to use this kernel on different machines.
   2.310 -
   2.311 -  More information about the internals of the Linux math coprocessor
   2.312 -  emulation can be found in <file:arch/i386/math-emu/README>.
   2.313 -
   2.314 -  If you are not sure, say Y; apart from resulting in a 66 KB bigger
   2.315 -  kernel, it won't hurt.
   2.316 -
   2.317 -Timer and CPU usage LEDs
   2.318 -CONFIG_LEDS
   2.319 -  If you say Y here, the LEDs on your machine will be used
   2.320 -  to provide useful information about your current system status.
   2.321 -
   2.322 -  If you are compiling a kernel for a NetWinder or EBSA-285, you will
   2.323 -  be able to select which LEDs are active using the options below. If
   2.324 -  you are compiling a kernel for the EBSA-110 or the LART however, the
   2.325 -  red LED will simply flash regularly to indicate that the system is
   2.326 -  still functional. It is safe to say Y here if you have a CATS
   2.327 -  system, but the driver will do nothing.
   2.328 -
   2.329 -Timer LED
   2.330 -CONFIG_LEDS_TIMER
   2.331 -  If you say Y here, one of the system LEDs (the green one on the
   2.332 -  NetWinder, the amber one on the EBSA285, or the red one on the LART)
   2.333 -  will flash regularly to indicate that the system is still
   2.334 -  operational. This is mainly useful to kernel hackers who are
   2.335 -  debugging unstable kernels.
   2.336 -
   2.337 -  The LART uses the same LED for both Timer LED and CPU usage LED
   2.338 -  functions. You may choose to use both, but the Timer LED function
   2.339 -  will overrule the CPU usage LED.
   2.340 -
   2.341 -CPU usage LED
   2.342 -CONFIG_LEDS_CPU
   2.343 -  If you say Y here, the red LED will be used to give a good real
   2.344 -  time indication of CPU usage, by lighting whenever the idle task
   2.345 -  is not currently executing.
   2.346 -
   2.347 -  The LART uses the same LED for both Timer LED and CPU usage LED
   2.348 -  functions. You may choose to use both, but the Timer LED function
   2.349 -  will overrule the CPU usage LED.
   2.350 -
   2.351 -Kernel FP software completion
   2.352 -CONFIG_MATHEMU
   2.353 -  This option is required for IEEE compliant floating point arithmetic
   2.354 -  on the Alpha. The only time you would ever not say Y is to say M in
   2.355 -  order to debug the code. Say Y unless you know what you are doing.
   2.356 -
   2.357 -# Choice: himem
   2.358 -High Memory support
   2.359 -CONFIG_NOHIGHMEM
   2.360 -  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
   2.361 -  However, the address space of 32-bit x86 processors is only 4
   2.362 -  Gigabytes large. That means that, if you have a large amount of
   2.363 -  physical memory, not all of it can be "permanently mapped" by the
   2.364 -  kernel. The physical memory that's not permanently mapped is called
   2.365 -  "high memory".
   2.366 -
   2.367 -  If you are compiling a kernel which will never run on a machine with
   2.368 -  more than 960 megabytes of total physical RAM, answer "off" here (default
   2.369 -  choice and suitable for most users). This will result in a "3GB/1GB"
   2.370 -  split: 3GB are mapped so that each process sees a 3GB virtual memory
   2.371 -  space and the remaining part of the 4GB virtual memory space is used
   2.372 -  by the kernel to permanently map as much physical memory as
   2.373 -  possible.
   2.374 -
   2.375 -  If the machine has between 1 and 4 Gigabytes physical RAM, then
   2.376 -  answer "4GB" here.
   2.377 -
   2.378 -  If more than 4 Gigabytes is used then answer "64GB" here. This
   2.379 -  selection turns Intel PAE (Physical Address Extension) mode on.
   2.380 -  PAE implements 3-level paging on IA32 processors. PAE is fully
   2.381 -  supported by Linux, PAE mode is implemented on all recent Intel
   2.382 -  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
   2.383 -  then the kernel will not boot on CPUs that don't support PAE!
   2.384 -
   2.385 -  The actual amount of total physical memory will either be auto
   2.386 -  detected or can be forced by using a kernel command line option such
   2.387 -  as "mem=256M". (Try "man bootparam" or see the documentation of your
   2.388 -  boot loader (grub, lilo or loadlin) about how to pass options to the
   2.389 -  kernel at boot time.)
   2.390 -
   2.391 -  If unsure, say "off".
   2.392 -
   2.393 -4GB
   2.394 -CONFIG_HIGHMEM4G
   2.395 -  Select this if you have a 32-bit processor and between 1 and 4
   2.396 -  gigabytes of physical RAM.
   2.397 -
   2.398 -64GB
   2.399 -CONFIG_HIGHMEM64G
   2.400 -  Select this if you have a 32-bit processor and more than 4
   2.401 -  gigabytes of physical RAM.
   2.402 -
   2.403 -HIGHMEM I/O support
   2.404 -CONFIG_HIGHIO
   2.405 -  If you want to be able to do I/O to high memory pages, say Y.
   2.406 -  Otherwise low memory pages are used as bounce buffers causing a
   2.407 -  degrade in performance.
   2.408 -
   2.409 -Normal floppy disk support
   2.410 -CONFIG_BLK_DEV_FD
   2.411 -  If you want to use the floppy disk drive(s) of your PC under Linux,
   2.412 -  say Y. Information about this driver, especially important for IBM
   2.413 -  Thinkpad users, is contained in <file:Documentation/floppy.txt>.
   2.414 -  That file also contains the location of the Floppy driver FAQ as
   2.415 -  well as location of the fdutils package used to configure additional
   2.416 -  parameters of the driver at run time.
   2.417 -
   2.418 -  This driver is also available as a module ( = code which can be
   2.419 -  inserted in and removed from the running kernel whenever you want).
   2.420 -  The module will be called floppy.o. If you want to compile it as a
   2.421 -  module, say M here and read <file:Documentation/modules.txt>.
   2.422 -
   2.423 -iSeries Virtual I/O Disk Support
   2.424 -CONFIG_VIODASD
   2.425 -  If you are running on an iSeries system and you want to use
   2.426 -  virtual disks created and managed by OS/400, say Y.
   2.427 -
   2.428 -iSeries Virtual I/O Disk IDE Emulation
   2.429 -CONFIG_VIODASD_IDE
   2.430 -  This causes the iSeries virtual disks to look like IDE disks.
   2.431 -  If you have programs or utilities that only support certain
   2.432 -  kinds of disks, this option will cause iSeries virtual disks
   2.433 -  to pretend to be IDE disks, which may satisfy the program.
   2.434 -
   2.435 -Support for PowerMac floppy
   2.436 -CONFIG_MAC_FLOPPY
   2.437 -  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
   2.438 -  floppy controller, say Y here. Most commonly found in PowerMacs.
   2.439 -
   2.440 -RAM disk support
   2.441 -CONFIG_BLK_DEV_RAM
   2.442 -  Saying Y here will allow you to use a portion of your RAM memory as
   2.443 -  a block device, so that you can make file systems on it, read and
   2.444 -  write to it and do all the other things that you can do with normal
   2.445 -  block devices (such as hard drives). It is usually used to load and
   2.446 -  store a copy of a minimal root file system off of a floppy into RAM
   2.447 -  during the initial install of Linux.
   2.448 -
   2.449 -  Note that the kernel command line option "ramdisk=XX" is now
   2.450 -  obsolete. For details, read <file:Documentation/ramdisk.txt>.
   2.451 -
   2.452 -  If you want to compile this as a module ( = code which can be
   2.453 -  inserted in and removed from the running kernel whenever you want),
   2.454 -  say M and read <file:Documentation/modules.txt>. The module will be
   2.455 -  called rd.o.
   2.456 -
   2.457 -  Most normal users won't need the RAM disk functionality, and can
   2.458 -  thus say N here.
   2.459 -
   2.460 -Default RAM disk size
   2.461 -CONFIG_BLK_DEV_RAM_SIZE
   2.462 -  The default value is 4096. Only change this if you know what are
   2.463 -  you doing. If you are using IBM S/390, then set this to 8192.
   2.464 -
   2.465 -Initial RAM disk (initrd) support
   2.466 -CONFIG_BLK_DEV_INITRD
   2.467 -  The initial RAM disk is a RAM disk that is loaded by the boot loader
   2.468 -  (loadlin or lilo) and that is mounted as root before the normal boot
   2.469 -  procedure. It is typically used to load modules needed to mount the
   2.470 -  "real" root file system, etc. See <file:Documentation/initrd.txt>
   2.471 -  for details.
   2.472 -
   2.473 -Loopback device support
   2.474 -CONFIG_BLK_DEV_LOOP
   2.475 -  Saying Y here will allow you to use a regular file as a block
   2.476 -  device; you can then create a file system on that block device and
   2.477 -  mount it just as you would mount other block devices such as hard
   2.478 -  drive partitions, CD-ROM drives or floppy drives. The loop devices
   2.479 -  are block special device files with major number 7 and typically
   2.480 -  called /dev/loop0, /dev/loop1 etc.
   2.481 -
   2.482 -  This is useful if you want to check an ISO 9660 file system before
   2.483 -  burning the CD, or if you want to use floppy images without first
   2.484 -  writing them to floppy. Furthermore, some Linux distributions avoid
   2.485 -  the need for a dedicated Linux partition by keeping their complete
   2.486 -  root file system inside a DOS FAT file using this loop device
   2.487 -  driver.
   2.488 -
   2.489 -  The loop device driver can also be used to "hide" a file system in a
   2.490 -  disk partition, floppy, or regular file, either using encryption
   2.491 -  (scrambling the data) or steganography (hiding the data in the low
   2.492 -  bits of, say, a sound file). This is also safe if the file resides
   2.493 -  on a remote file server. If you want to do this, you will first have
   2.494 -  to acquire and install a kernel patch from
   2.495 -  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
   2.496 -  say Y to this option.
   2.497 -
   2.498 -  Note that alternative ways to use encrypted file systems are
   2.499 -  provided by the cfs package, which can be gotten from
   2.500 -  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
   2.501 -  package, available at <http://tcfs.dia.unisa.it/>. You do not need
   2.502 -  to say Y here if you want to use one of these. However, using cfs
   2.503 -  requires saying Y to "NFS file system support" below while using
   2.504 -  tcfs requires applying a kernel patch. An alternative steganography
   2.505 -  solution is provided by StegFS, also available from
   2.506 -  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
   2.507 -
   2.508 -  To use the loop device, you need the losetup utility and a recent
   2.509 -  version of the mount program, both contained in the util-linux
   2.510 -  package. The location and current version number of util-linux is
   2.511 -  contained in the file <file:Documentation/Changes>.
   2.512 -
   2.513 -  Note that this loop device has nothing to do with the loopback
   2.514 -  device used for network connections from the machine to itself.
   2.515 -
   2.516 -  If you want to compile this driver as a module ( = code which can be
   2.517 -  inserted in and removed from the running kernel whenever you want),
   2.518 -  say M here and read <file:Documentation/modules.txt>. The module
   2.519 -  will be called loop.o.
   2.520 -
   2.521 -  Most users will answer N here.
   2.522 -
   2.523 -Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
   2.524 -CONFIG_BLK_DEV_UMEM
   2.525 -  Saying Y here will include support for the MM5415 family of
   2.526 -  battery backed (Non-volatile) RAM cards.
   2.527 -  <http://www.umem.com/>
   2.528 -
   2.529 -  The cards appear as block devices that can be partitioned into
   2.530 -  as many as 15 partitions.
   2.531 -
   2.532 -  If you want to compile this driver as a module ( = code which can be
   2.533 -  inserted in and removed from the running kernel whenever you want),
   2.534 -  say M here and read Documentation/modules.txt. The module will be
   2.535 -  called umem.o.
   2.536 -
   2.537 -  The umem driver has been allocated block major number 116.
   2.538 -  See Documentation/devices.txt for recommended device naming.
   2.539 -
   2.540 -Network block device support
   2.541 -CONFIG_BLK_DEV_NBD
   2.542 -  Saying Y here will allow your computer to be a client for network
   2.543 -  block devices, i.e. it will be able to use block devices exported by
   2.544 -  servers (mount file systems on them etc.). Communication between
   2.545 -  client and server works over TCP/IP networking, but to the client
   2.546 -  program this is hidden: it looks like a regular local file access to
   2.547 -  a block device special file such as /dev/nd0.
   2.548 -
   2.549 -  Network block devices also allows you to run a block-device in
   2.550 -  userland (making server and client physically the same computer,
   2.551 -  communicating using the loopback network device).
   2.552 -
   2.553 -  Read <file:Documentation/nbd.txt> for more information, especially
   2.554 -  about where to find the server code, which runs in user space and
   2.555 -  does not need special kernel support.
   2.556 -
   2.557 -  Note that this has nothing to do with the network file systems NFS
   2.558 -  or Coda; you can say N here even if you intend to use NFS or Coda.
   2.559 -
   2.560 -  If you want to compile this driver as a module ( = code which can be
   2.561 -  inserted in and removed from the running kernel whenever you want),
   2.562 -  say M here and read <file:Documentation/modules.txt>. The module
   2.563 -  will be called nbd.o.
   2.564 -
   2.565 -  If unsure, say N.
   2.566 -
   2.567 -XenoLinux virtual block device support
   2.568 -CONFIG_XENOLINUX_BLOCK
   2.569 -  Xen can export virtual block devices which map back to extents of
   2.570 -  blocks on the physical partitions.  This option is needed for
   2.571 -  xenolinux to make use of such devices when running as a Xen guest.
   2.572 -
   2.573 -  If unsure, say Y.
   2.574 -
   2.575 -Per partition statistics in /proc/partitions
   2.576 -CONFIG_BLK_STATS
   2.577 -  If you say yes here, your kernel will keep statistical information
   2.578 -  for every partition. The information includes things as numbers of
   2.579 -  read and write accesses, the number of merged requests etc.
   2.580 -
   2.581 -  This is required for the full functionality of sar(8) and interesting
   2.582 -  if you want to do performance tuning, by tweaking the elevator, e.g.
   2.583 -
   2.584 -  If unsure, say N.
   2.585 -
   2.586 -ATA/IDE/MFM/RLL support
   2.587 -CONFIG_IDE
   2.588 -  If you say Y here, your kernel will be able to manage low cost mass
   2.589 -  storage units such as ATA/(E)IDE and ATAPI units. The most common
   2.590 -  cases are IDE hard drives and ATAPI CD-ROM drives.
   2.591 -
   2.592 -  If your system is pure SCSI and doesn't use these interfaces, you
   2.593 -  can say N here.
   2.594 -
   2.595 -  Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
   2.596 -  for mass storage units such as hard disks. It was designed by
   2.597 -  Western Digital and Compaq Computer in 1984. It was then named
   2.598 -  ST506. Quite a number of disks use the IDE interface.
   2.599 -
   2.600 -  AT Attachment (ATA) is the superset of the IDE specifications.
   2.601 -  ST506 was also called ATA-1.
   2.602 -
   2.603 -  Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
   2.604 -  ATA-3. It provides support for larger disks (up to 8.4GB by means of
   2.605 -  the LBA standard), more disks (4 instead of 2) and for other mass
   2.606 -  storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
   2.607 -  ATA-4 and provides faster (and more CPU friendly) transfer modes
   2.608 -  than previous PIO (Programmed processor Input/Output) from previous
   2.609 -  ATA/IDE standards by means of fast DMA controllers.
   2.610 -
   2.611 -  ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
   2.612 -  CD-ROM drives, similar in many respects to the SCSI protocol.
   2.613 -
   2.614 -  SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
   2.615 -  designed in order to prevent data corruption and disk crash by
   2.616 -  detecting pre hardware failure conditions (heat, access time, and
   2.617 -  the like...). Disks built since June 1995 may follow this standard.
   2.618 -  The kernel itself don't manage this; however there are quite a
   2.619 -  number of user programs such as smart that can query the status of
   2.620 -  SMART parameters disk.
   2.621 -
   2.622 -  If you want to compile this driver as a module ( = code which can be
   2.623 -  inserted in and removed from the running kernel whenever you want),
   2.624 -  say M here and read <file:Documentation/modules.txt>. The module
   2.625 -  will be called ide.o.
   2.626 -
   2.627 -  For further information, please read <file:Documentation/ide.txt>.
   2.628 -
   2.629 -  If unsure, say Y.
   2.630 -
   2.631 -Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
   2.632 -CONFIG_BLK_DEV_IDE
   2.633 -  If you say Y here, you will use the full-featured IDE driver to
   2.634 -  control up to ten ATA/IDE interfaces, each being able to serve a
   2.635 -  "master" and a "slave" device, for a total of up to twenty ATA/IDE
   2.636 -  disk/cdrom/tape/floppy drives.
   2.637 -
   2.638 -  Useful information about large (>540 MB) IDE disks, multiple
   2.639 -  interfaces, what to do if ATA/IDE devices are not automatically
   2.640 -  detected, sound card ATA/IDE ports, module support, and other
   2.641 -  topics, is contained in <file:Documentation/ide.txt>. For detailed
   2.642 -  information about hard drives, consult the Disk-HOWTO and the
   2.643 -  Multi-Disk-HOWTO, available from
   2.644 -  <http://www.tldp.org/docs.html#howto>.
   2.645 -
   2.646 -  To fine-tune ATA/IDE drive/interface parameters for improved
   2.647 -  performance, look for the hdparm package at
   2.648 -  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   2.649 -
   2.650 -  If you want to compile this driver as a module ( = code which can be
   2.651 -  inserted in and removed from the running kernel whenever you want),
   2.652 -  say M here and read <file:Documentation/modules.txt> and
   2.653 -  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
   2.654 -  Do not compile this driver as a module if your root file system (the
   2.655 -  one containing the directory /) is located on an IDE device.
   2.656 -
   2.657 -  If you have one or more IDE drives, say Y or M here. If your system
   2.658 -  has no IDE drives, or if memory requirements are really tight, you
   2.659 -  could say N here, and select the "Old hard disk driver" below
   2.660 -  instead to save about 13 KB of memory in the kernel.
   2.661 -
   2.662 -Old hard disk (MFM/RLL/IDE) driver
   2.663 -CONFIG_BLK_DEV_HD_ONLY
   2.664 -  There are two drivers for MFM/RLL/IDE hard disks. Most people use
   2.665 -  the newer enhanced driver, but this old one is still around for two
   2.666 -  reasons. Some older systems have strange timing problems and seem to
   2.667 -  work only with the old driver (which itself does not work with some
   2.668 -  newer systems). The other reason is that the old driver is smaller,
   2.669 -  since it lacks the enhanced functionality of the new one. This makes
   2.670 -  it a good choice for systems with very tight memory restrictions, or
   2.671 -  for systems with only older MFM/RLL/ESDI drives. Choosing the old
   2.672 -  driver can save 13 KB or so of kernel memory.
   2.673 -
   2.674 -  If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
   2.675 -  instead of this one. For more detailed information, read the
   2.676 -  Disk-HOWTO, available from
   2.677 -  <http://www.tldp.org/docs.html#howto>.
   2.678 -
   2.679 -Use old disk-only driver on primary interface
   2.680 -CONFIG_BLK_DEV_HD_IDE
   2.681 -  There are two drivers for MFM/RLL/IDE disks.  Most people use just
   2.682 -  the new enhanced driver by itself.  This option however installs the
   2.683 -  old hard disk driver to control the primary IDE/disk interface in
   2.684 -  the system, leaving the new enhanced IDE driver to take care of only
   2.685 -  the 2nd/3rd/4th IDE interfaces.  Doing this will prevent you from
   2.686 -  having an IDE/ATAPI CD-ROM or tape drive connected to the primary
   2.687 -  IDE interface.  Choosing this option may be useful for older systems
   2.688 -  which have MFM/RLL/ESDI controller+drives at the primary port
   2.689 -  address (0x1f0), along with IDE drives at the secondary/3rd/4th port
   2.690 -  addresses.
   2.691 -
   2.692 -  Normally, just say N here; you will then use the new driver for all
   2.693 -  4 interfaces.
   2.694 -
   2.695 -Include IDE/ATA-2 DISK support
   2.696 -CONFIG_BLK_DEV_IDEDISK
   2.697 -  This will include enhanced support for MFM/RLL/IDE hard disks.  If
   2.698 -  you have a MFM/RLL/IDE disk, and there is no special reason to use
   2.699 -  the old hard disk driver instead, say Y.  If you have an SCSI-only
   2.700 -  system, you can say N here.
   2.701 -
   2.702 -  If you want to compile this driver as a module ( = code which can be
   2.703 -  inserted in and removed from the running kernel whenever you want),
   2.704 -  say M here and read <file:Documentation/modules.txt>.  The module
   2.705 -  will be called ide-disk.o.  Do not compile this driver as a module
   2.706 -  if your root file system (the one containing the directory /) is
   2.707 -  located on the IDE disk. If unsure, say Y.
   2.708 -
   2.709 -Use multi-mode by default
   2.710 -CONFIG_IDEDISK_MULTI_MODE
   2.711 -  If you get this error, try to say Y here:
   2.712 -
   2.713 -  hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
   2.714 -  hda: set_multmode: error=0x04 { DriveStatusError }
   2.715 -
   2.716 -  If in doubt, say N.
   2.717 -
   2.718 -PCMCIA IDE support
   2.719 -CONFIG_BLK_DEV_IDECS
   2.720 -  Support for outboard IDE disks, tape drives, and CD-ROM drives
   2.721 -  connected through a  PCMCIA card.
   2.722 -
   2.723 -  This driver is also available as a module ( = code which can be
   2.724 -  inserted in and removed from the running kernel whenever you want).
   2.725 -  If you want to compile it as a module, say M here and read
   2.726 -  <file:Documentation/modules.txt>. The module will be called
   2.727 -  ide-cs.o
   2.728 -
   2.729 -Include IDE/ATAPI CD-ROM support
   2.730 -CONFIG_BLK_DEV_IDECD
   2.731 -  If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
   2.732 -  a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
   2.733 -  SCSI protocol. Most new CD-ROM drives use ATAPI, including the
   2.734 -  NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
   2.735 -  double(2X) or better speed drives.
   2.736 -
   2.737 -  If you say Y here, the CD-ROM drive will be identified at boot time
   2.738 -  along with other IDE devices, as "hdb" or "hdc", or something
   2.739 -  similar (check the boot messages with dmesg). If this is your only
   2.740 -  CD-ROM drive, you can say N to all other CD-ROM options, but be sure
   2.741 -  to say Y or M to "ISO 9660 CD-ROM file system support".
   2.742 -
   2.743 -  Note that older versions of LILO (LInux LOader) cannot properly deal
   2.744 -  with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
   2.745 -  <ftp://brun.dyndns.org/pub/linux/lilo/>.
   2.746 -
   2.747 -  If you want to compile the driver as a module ( = code which can be
   2.748 -  inserted in and removed from the running kernel whenever you want),
   2.749 -  say M here and read <file:Documentation/modules.txt>.  The module
   2.750 -  will be called ide-cd.o.
   2.751 -
   2.752 -Include IDE/ATAPI TAPE support
   2.753 -CONFIG_BLK_DEV_IDETAPE
   2.754 -  If you have an IDE tape drive using the ATAPI protocol, say Y.
   2.755 -  ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
   2.756 -  similar to the SCSI protocol.  If you have an SCSI tape drive
   2.757 -  however, you can say N here.
   2.758 -
   2.759 -  You should also say Y if you have an OnStream DI-30 tape drive; this
   2.760 -  will not work with the SCSI protocol, until there is support for the
   2.761 -  SC-30 and SC-50 versions.
   2.762 -
   2.763 -  If you say Y here, the tape drive will be identified at boot time
   2.764 -  along with other IDE devices, as "hdb" or "hdc", or something
   2.765 -  similar, and will be mapped to a character device such as "ht0"
   2.766 -  (check the boot messages with dmesg).  Be sure to consult the
   2.767 -  <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
   2.768 -  for usage information.
   2.769 -
   2.770 -  If you want to compile the driver as a module ( = code which can be
   2.771 -  inserted in and removed from the running kernel whenever you want),
   2.772 -  say M here and read <file:Documentation/modules.txt>.  The module
   2.773 -  will be called ide-tape.o.
   2.774 -
   2.775 -Include IDE/ATAPI FLOPPY support
   2.776 -CONFIG_BLK_DEV_IDEFLOPPY
   2.777 -  If you have an IDE floppy drive which uses the ATAPI protocol,
   2.778 -  answer Y.  ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
   2.779 -  drives, similar to the SCSI protocol.
   2.780 -
   2.781 -  The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
   2.782 -  this driver. For information about jumper settings and the question
   2.783 -  of when a ZIP drive uses a partition table, see
   2.784 -  <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
   2.785 -  (ATAPI PD-CD/CDR drives are not supported by this driver; support
   2.786 -  for PD-CD/CDR drives is available if you answer Y to
   2.787 -  "SCSI emulation support", below).
   2.788 -
   2.789 -  If you say Y here, the FLOPPY drive will be identified along with
   2.790 -  other IDE devices, as "hdb" or "hdc", or something similar (check
   2.791 -  the boot messages with dmesg).
   2.792 -
   2.793 -  If you want to compile the driver as a module ( = code which can be
   2.794 -  inserted in and removed from the running kernel whenever you want),
   2.795 -  say M here and read <file:Documentation/modules.txt>.  The module
   2.796 -  will be called ide-floppy.o.
   2.797 -
   2.798 -AWARD Bios Work-Around
   2.799 -CONFIG_IDEDISK_STROKE
   2.800 -  Should you have a system w/ an AWARD Bios and your drives are larger
   2.801 -  than 32GB and it will not boot, one is required to perform a few OEM
   2.802 -  operations first.  The option is called "STROKE" because it allows
   2.803 -  one to "soft clip" the drive to work around a barrier limit.  For
   2.804 -  Maxtor drives it is called "jumpon.exe".  Please search Maxtor's
   2.805 -  web-site for "JUMPON.EXE".  IBM has a similar tool at:
   2.806 -  <http://www.storage.ibm.com/hdd/support/download.htm>.
   2.807 -
   2.808 -  If you are unsure, say N here.
   2.809 -
   2.810 -Raw Access to Media
   2.811 -CONFIG_IDE_TASK_IOCTL
   2.812 -  This is a direct raw access to the media.  It is a complex but
   2.813 -  elegant solution to test and validate the domain of the hardware and
   2.814 -  perform below the driver data recover if needed.  This is the most
   2.815 -  basic form of media-forensics.
   2.816 -
   2.817 -  If you are unsure, say N here.
   2.818 -
   2.819 -Use Taskfile I/O
   2.820 -CONFIG_IDE_TASKFILE_IO
   2.821 -  This is the "Jewel" of the patch.  It will go away and become the new
   2.822 -  driver core.  Since all the chipsets/host side hardware deal w/ their
   2.823 -  exceptions in "their local code" currently, adoption of a
   2.824 -  standardized data-transport is the only logical solution.
   2.825 -  Additionally we packetize the requests and gain rapid performance and
   2.826 -  a reduction in system latency.  Additionally by using a memory struct
   2.827 -  for the commands we can redirect to a MMIO host hardware in the next
   2.828 -  generation of controllers, specifically second generation Ultra133
   2.829 -  and Serial ATA.
   2.830 -
   2.831 -  Since this is a major transition, it was deemed necessary to make the
   2.832 -  driver paths buildable in separate models.  Therefore if using this
   2.833 -  option fails for your arch then we need to address the needs for that
   2.834 -  arch.
   2.835 -
   2.836 -  If you want to test this functionality, say Y here.
   2.837 -
   2.838 -Force DMA
   2.839 -CONFIG_BLK_DEV_IDEDMA_FORCED
   2.840 -  This is an old piece of lost code from Linux 2.0 Kernels.
   2.841 -
   2.842 -  Generally say N here.
   2.843 -
   2.844 -DMA Only on Disks
   2.845 -CONFIG_IDEDMA_ONLYDISK
   2.846 -  This is used if you know your ATAPI Devices are going to fail DMA
   2.847 -  Transfers.
   2.848 -
   2.849 -  Generally say N here.
   2.850 -
   2.851 -SCSI emulation support
   2.852 -CONFIG_BLK_DEV_IDESCSI
   2.853 -  This will provide SCSI host adapter emulation for IDE ATAPI devices,
   2.854 -  and will allow you to use a SCSI device driver instead of a native
   2.855 -  ATAPI driver.
   2.856 -
   2.857 -  This is useful if you have an ATAPI device for which no native
   2.858 -  driver has been written (for example, an ATAPI PD-CD or CDR drive);
   2.859 -  you can then use this emulation together with an appropriate SCSI
   2.860 -  device driver. In order to do this, say Y here and to "SCSI support"
   2.861 -  and "SCSI generic support", below. You must then provide the kernel
   2.862 -  command line "hdx=scsi" (try "man bootparam" or see the
   2.863 -  documentation of your boot loader (lilo or loadlin) about how to
   2.864 -  pass options to the kernel at boot time) for devices if you want the
   2.865 -  native EIDE sub-drivers to skip over the native support, so that
   2.866 -  this SCSI emulation can be used instead. This is required for use of
   2.867 -  CD-RW's.
   2.868 -
   2.869 -  Note that this option does NOT allow you to attach SCSI devices to a
   2.870 -  box that doesn't have a SCSI host adapter installed.
   2.871 -
   2.872 -  If both this SCSI emulation and native ATAPI support are compiled
   2.873 -  into the kernel, the native support will be used.
   2.874 -
   2.875 -  This driver is also available as a module ( = code which can be
   2.876 -  inserted in and removed from the running kernel whenever you want).
   2.877 -  If you want to compile it as a module, say M here and read
   2.878 -  <file:Documentation/modules.txt>. The module will be called
   2.879 -  ide-scsi.o
   2.880 -
   2.881 -Use the NOOP Elevator (WARNING)
   2.882 -CONFIG_BLK_DEV_ELEVATOR_NOOP
   2.883 -  If you are using a raid class top-level driver above the ATA/IDE core,
   2.884 -  one may find a performance boost by preventing a merging and re-sorting
   2.885 -  of the new requests.
   2.886 -
   2.887 -  If unsure, say N.
   2.888 -
   2.889 -ISA-PNP EIDE support
   2.890 -CONFIG_BLK_DEV_ISAPNP
   2.891 -  If you have an ISA EIDE card that is PnP (Plug and Play) and
   2.892 -  requires setup first before scanning for devices, say Y here.
   2.893 -
   2.894 -  If unsure, say N.
   2.895 -
   2.896 -CMD640 chipset bugfix/support
   2.897 -CONFIG_BLK_DEV_CMD640
   2.898 -  The CMD-Technologies CMD640 IDE chip is used on many common 486 and
   2.899 -  Pentium motherboards, usually in combination with a "Neptune" or
   2.900 -  "SiS" chipset. Unfortunately, it has a number of rather nasty
   2.901 -  design flaws that can cause severe data corruption under many common
   2.902 -  conditions. Say Y here to include code which tries to automatically
   2.903 -  detect and correct the problems under Linux. This option also
   2.904 -  enables access to the secondary IDE ports in some CMD640 based
   2.905 -  systems.
   2.906 -
   2.907 -  This driver will work automatically in PCI based systems (most new
   2.908 -  systems have PCI slots). But if your system uses VESA local bus
   2.909 -  (VLB) instead of PCI, you must also supply a kernel boot parameter
   2.910 -  to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
   2.911 -  bootparam" or see the documentation of your boot loader about how to
   2.912 -  pass options to the kernel.)
   2.913 -
   2.914 -  The CMD640 chip is also used on add-in cards by Acculogic, and on
   2.915 -  the "CSA-6400E PCI to IDE controller" that some people have. For
   2.916 -  details, read <file:Documentation/ide.txt>.
   2.917 -
   2.918 -CMD640 enhanced support
   2.919 -CONFIG_BLK_DEV_CMD640_ENHANCED
   2.920 -  This option includes support for setting/autotuning PIO modes and
   2.921 -  prefetch on CMD640 IDE interfaces.  For details, read
   2.922 -  <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
   2.923 -  and your BIOS does not already do this for you, then say Y here.
   2.924 -  Otherwise say N.
   2.925 -
   2.926 -RZ1000 chipset bugfix/support
   2.927 -CONFIG_BLK_DEV_RZ1000
   2.928 -  The PC-Technologies RZ1000 IDE chip is used on many common 486 and
   2.929 -  Pentium motherboards, usually along with the "Neptune" chipset.
   2.930 -  Unfortunately, it has a rather nasty design flaw that can cause
   2.931 -  severe data corruption under many conditions. Say Y here to include
   2.932 -  code which automatically detects and corrects the problem under
   2.933 -  Linux. This may slow disk throughput by a few percent, but at least
   2.934 -  things will operate 100% reliably.
   2.935 -
   2.936 -Generic PCI IDE chipset support
   2.937 -CONFIG_BLK_DEV_IDEPCI
   2.938 -  Say Y here for PCI systems which use IDE drive(s).
   2.939 -  This option helps the IDE driver to automatically detect and
   2.940 -  configure all PCI-based IDE interfaces in your system.
   2.941 -
   2.942 -Support for sharing PCI IDE interrupts
   2.943 -CONFIG_IDEPCI_SHARE_IRQ
   2.944 -  Some ATA/IDE chipsets have hardware support which allows for
   2.945 -  sharing a single IRQ with other cards. To enable support for
   2.946 -  this in the ATA/IDE driver, say Y here.
   2.947 -
   2.948 -  It is safe to say Y to this question, in most cases.
   2.949 -  If unsure, say N.
   2.950 -
   2.951 -Generic PCI bus-master DMA support
   2.952 -CONFIG_BLK_DEV_IDEDMA_PCI
   2.953 -  If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
   2.954 -  is capable of bus-master DMA operation (most Pentium PCI systems),
   2.955 -  you will want to say Y here to reduce CPU overhead. You can then use
   2.956 -  the "hdparm" utility to enable DMA for drives for which it was not
   2.957 -  enabled automatically. By default, DMA is not enabled automatically
   2.958 -  for these drives, but you can change that by saying Y to the
   2.959 -  following question "Use DMA by default when available". You can get
   2.960 -  the latest version of the hdparm utility from
   2.961 -  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   2.962 -
   2.963 -  Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
   2.964 -  and the file <file:Documentation/ide.txt> for more information.
   2.965 -
   2.966 -  It is safe to say Y to this question.
   2.967 -
   2.968 -Good-Bad DMA Model-Firmware (WIP)
   2.969 -CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
   2.970 -  If you say Y here, the model and firmware revision of your drive
   2.971 -  will be compared against a blacklist of buggy drives that claim to
   2.972 -  be (U)DMA capable but aren't. This is a blanket on/off test with no
   2.973 -  speed limit options.
   2.974 -
   2.975 -  Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
   2.976 -  whereas, many versions of EGCS have a problem and miscompile if you
   2.977 -  say Y here.
   2.978 -
   2.979 -  If in doubt, say N.
   2.980 -
   2.981 -Attempt to HACK around Chipsets that TIMEOUT (WIP)
   2.982 -CONFIG_BLK_DEV_IDEDMA_TIMEOUT
   2.983 -  If you say Y here, this is a NASTY UGLY HACK!
   2.984 -
   2.985 -  We have to issue an abort and requeue the request DMA engine got
   2.986 -  turned off by a goofy ASIC, and we have to clean up the mess, and
   2.987 -  here is as good as any.  Do it globally for all chipsets.
   2.988 -
   2.989 -  If in doubt, say N.
   2.990 -
   2.991 -Boot off-board chipsets first support
   2.992 -CONFIG_BLK_DEV_OFFBOARD
   2.993 -  Normally, IDE controllers built into the motherboard (on-board
   2.994 -  controllers) are assigned to ide0 and ide1 while those on add-in PCI
   2.995 -  cards (off-board controllers) are relegated to ide2 and ide3.
   2.996 -  Answering Y here will allow you to reverse the situation, with
   2.997 -  off-board controllers on ide0/1 and on-board controllers on ide2/3.
   2.998 -  This can improve the usability of some boot managers such as lilo
   2.999 -  when booting from a drive on an off-board controller.
  2.1000 -
  2.1001 -  If you say Y here, and you actually want to reverse the device scan
  2.1002 -  order as explained above, you also need to issue the kernel command
  2.1003 -  line option "ide=reverse". (Try "man bootparam" or see the
  2.1004 -  documentation of your boot loader (lilo or loadlin) about how to
  2.1005 -  pass options to the kernel at boot time.)
  2.1006 -
  2.1007 -  Note that, if you do this, the order of the hd* devices will be
  2.1008 -  rearranged which may require modification of fstab and other files.
  2.1009 -
  2.1010 -  If in doubt, say N.
  2.1011 -
  2.1012 -Use PCI DMA by default when available
  2.1013 -CONFIG_IDEDMA_PCI_AUTO
  2.1014 -  Prior to kernel version 2.1.112, Linux used to automatically use
  2.1015 -  DMA for IDE drives and chipsets which support it. Due to concerns
  2.1016 -  about a couple of cases where buggy hardware may have caused damage,
  2.1017 -  the default is now to NOT use DMA automatically. To revert to the
  2.1018 -  previous behaviour, say Y to this question.
  2.1019 -
  2.1020 -  If you suspect your hardware is at all flakey, say N here.
  2.1021 -  Do NOT email the IDE kernel people regarding this issue!
  2.1022 -
  2.1023 -  It is normally safe to answer Y to this question unless your
  2.1024 -  motherboard uses a VIA VP2 chipset, in which case you should say N.
  2.1025 -
  2.1026 -IGNORE word93 Validation BITS
  2.1027 -CONFIG_IDEDMA_IVB
  2.1028 -  There are unclear terms in ATA-4 and ATA-5 standards how certain
  2.1029 -  hardware (an 80c ribbon) should be detected. Different interpretations
  2.1030 -  of the standards have been released in hardware. This causes problems:
  2.1031 -  for example, a host with Ultra Mode 4 (or higher) will not run
  2.1032 -  in that mode with an 80c ribbon.
  2.1033 -
  2.1034 -  If you are experiencing compatibility or performance problems, you
  2.1035 -  MAY try to answering Y here. However, it does not necessarily solve
  2.1036 -  any of your problems, it could even cause more of them.
  2.1037 -
  2.1038 -  It is normally safe to answer Y; however, the default is N.
  2.1039 -
  2.1040 -ATA Work(s) In Progress (EXPERIMENTAL)
  2.1041 -CONFIG_IDEDMA_PCI_WIP
  2.1042 -  If you enable this you will be able to use and test highly
  2.1043 -  developmental projects. If you say N, the configurator will
  2.1044 -  simply skip those options.
  2.1045 -
  2.1046 -  It is SAFEST to say N to this question.
  2.1047 -
  2.1048 -Asynchronous DMA support (EXPERIMENTAL)
  2.1049 -CONFIG_BLK_DEV_ADMA
  2.1050 -  Please read the comments at the top of
  2.1051 -  <file:drivers/ide/ide-adma.c>.
  2.1052 -
  2.1053 -Pacific Digital A-DMA support (EXPERIMENTAL)
  2.1054 -CONFIG_BLK_DEV_PDC_ADMA
  2.1055 -  Please read the comments at the top of <file:drivers/ide/setup-pci.c>.
  2.1056 -
  2.1057 -3ware Hardware ATA-RAID support
  2.1058 -CONFIG_BLK_DEV_3W_XXXX_RAID
  2.1059 -  3ware is the only hardware ATA-Raid product in Linux to date.
  2.1060 -  This card is 2,4, or 8 channel master mode support only.
  2.1061 -  SCSI support required!!!
  2.1062 -
  2.1063 -  <http://www.3ware.com/>
  2.1064 -
  2.1065 -  Please read the comments at the top of
  2.1066 -  <file:drivers/scsi/3w-xxxx.c>.
  2.1067 -
  2.1068 -  If you want to compile the driver as a module ( = code which can be
  2.1069 -  inserted in and removed from the running kernel whenever you want),
  2.1070 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.1071 -  will be called 3w-xxxx.o.
  2.1072 -
  2.1073 -AEC62XX chipset support
  2.1074 -CONFIG_BLK_DEV_AEC62XX
  2.1075 -  This driver adds up to 4 more EIDE devices sharing a single
  2.1076 -  interrupt. This add-on card is a bootable PCI UDMA controller. In
  2.1077 -  order to get this card to initialize correctly in some cases, you
  2.1078 -  should say Y here, and preferably also to "Use DMA by default when
  2.1079 -  available".
  2.1080 -
  2.1081 -  The ATP850U/UF is an UltraDMA 33 chipset base.
  2.1082 -  The ATP860 is an UltraDMA 66 chipset base.
  2.1083 -  The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
  2.1084 -
  2.1085 -  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  2.1086 -  If you say Y here, then say Y to "Use DMA by default when available"
  2.1087 -  as well.
  2.1088 -
  2.1089 -AEC62XX Tuning support
  2.1090 -CONFIG_AEC62XX_TUNING
  2.1091 -  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  2.1092 -  If unsure, say N.
  2.1093 -
  2.1094 -ALI M15x3 chipset support
  2.1095 -CONFIG_BLK_DEV_ALI15X3
  2.1096 -  This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
  2.1097 -  onboard chipsets.  It also tests for Simplex mode and enables
  2.1098 -  normal dual channel support.
  2.1099 -
  2.1100 -  If you say Y here, you also need to say Y to "Use DMA by default
  2.1101 -  when available", above.  Please read the comments at the top of
  2.1102 -  <file:drivers/ide/pci/alim15x3.c>.
  2.1103 -
  2.1104 -  If unsure, say N.
  2.1105 -
  2.1106 -ALI M15x3 WDC support (DANGEROUS)
  2.1107 -CONFIG_WDC_ALI15X3
  2.1108 -  This allows for UltraDMA support for WDC drives that ignore CRC
  2.1109 -  checking. You are a fool for enabling this option, but there have
  2.1110 -  been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
  2.1111 -  YOU ENABLE THIS! No one will listen, just laugh for ignoring this
  2.1112 -  SERIOUS WARNING.
  2.1113 -
  2.1114 -  Using this option can allow WDC drives to run at ATA-4/5 transfer
  2.1115 -  rates with only an ATA-2 support structure.
  2.1116 -
  2.1117 -  SAY N!
  2.1118 -
  2.1119 -AMD and nVidia IDE support
  2.1120 -CONFIG_BLK_DEV_AMD74XX
  2.1121 -  This driver adds explicit support for AMD-7xx and AMD-8111 chips
  2.1122 -  and also for the nVidia nForce chip.  This allows the kernel to
  2.1123 -  change PIO, DMA and UDMA speeds and to configure the chip to
  2.1124 -  optimum performance.
  2.1125 -
  2.1126 -  If you say Y here, you also need to say Y to "Use DMA by default
  2.1127 -  when available", above.
  2.1128 -  Please read the comments at the top of <file:drivers/ide/pci/amd74xx.c>.
  2.1129 -
  2.1130 -  If unsure, say N.
  2.1131 -
  2.1132 -AMD Viper ATA-66 Override support (WIP)
  2.1133 -CONFIG_AMD74XX_OVERRIDE
  2.1134 -  This option auto-forces the ata66 flag.
  2.1135 -  This effect can be also invoked by calling "idex=ata66"
  2.1136 -  If unsure, say N.
  2.1137 -
  2.1138 -CMD64X/CMD680 chipset support
  2.1139 -CONFIG_BLK_DEV_CMD64X
  2.1140 -  Say Y here if you have an IDE controller which uses any of these
  2.1141 -  chipsets: CMD643, CMD646 and CMD648.
  2.1142 -
  2.1143 -CY82C693 chipset support
  2.1144 -CONFIG_BLK_DEV_CY82C693
  2.1145 -  This driver adds detection and support for the CY82C693 chipset
  2.1146 -  used on Digital's PC-Alpha 164SX boards.
  2.1147 -
  2.1148 -  If you say Y here, you need to say Y to "Use DMA by default
  2.1149 -  when available" as well.
  2.1150 -
  2.1151 -Cyrix CS5530 MediaGX chipset support
  2.1152 -CONFIG_BLK_DEV_CS5530
  2.1153 -  Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
  2.1154 -  will automatically be detected and configured if found.
  2.1155 -
  2.1156 -  It is safe to say Y to this question.
  2.1157 -
  2.1158 -  People with SCSI-only systems should say N here. If unsure, say Y.
  2.1159 -
  2.1160 -HPT34X chipset support
  2.1161 -CONFIG_BLK_DEV_HPT34X
  2.1162 -  This driver adds up to 4 more EIDE devices sharing a single
  2.1163 -  interrupt. The HPT343 chipset in its current form is a non-bootable
  2.1164 -  controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
  2.1165 -  PCI UDMA controllers. This driver requires dynamic tuning of the
  2.1166 -  chipset during the ide-probe at boot time. It is reported to support
  2.1167 -  DVD II drives, by the manufacturer.
  2.1168 -
  2.1169 -HPT34X AUTODMA support (WIP)
  2.1170 -CONFIG_HPT34X_AUTODMA
  2.1171 -  This is a dangerous thing to attempt currently! Please read the
  2.1172 -  comments at the top of <file:drivers/ide/pci/hpt34x.c>.  If you say Y
  2.1173 -  here, then say Y to "Use DMA by default when available" as well.
  2.1174 -
  2.1175 -  If unsure, say N.
  2.1176 -
  2.1177 -HPT36X/37X chipset support
  2.1178 -CONFIG_BLK_DEV_HPT366
  2.1179 -  HPT366 is an Ultra DMA chipset for ATA-66.
  2.1180 -  HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
  2.1181 -  HPT370 is an Ultra DMA chipset for ATA-100.
  2.1182 -  HPT372 is an Ultra DMA chipset for ATA-133.
  2.1183 -  HPT374 is an Ultra DMA chipset for ATA-133.
  2.1184 -
  2.1185 -  This driver adds up to 4 more EIDE devices sharing a single
  2.1186 -  interrupt.
  2.1187 -
  2.1188 -  The HPT366 chipset in its current form is bootable. One solution
  2.1189 -  for this problem are special LILO commands for redirecting the
  2.1190 -  reference to device 0x80. The other solution is to say Y to "Boot
  2.1191 -  off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
  2.1192 -  your mother board has the chipset natively mounted. Regardless one
  2.1193 -  should use the fore mentioned option and call at LILO or include
  2.1194 -  "ide=reverse" in LILO's append-line.
  2.1195 -
  2.1196 -  This driver requires dynamic tuning of the chipset during the
  2.1197 -  ide-probe at boot. It is reported to support DVD II drives, by the
  2.1198 -  manufacturer.
  2.1199 -
  2.1200 -NS87415 chipset support (EXPERIMENTAL)
  2.1201 -CONFIG_BLK_DEV_NS87415
  2.1202 -  This driver adds detection and support for the NS87415 chip
  2.1203 -  (used in SPARC64, among others).
  2.1204 -
  2.1205 -  Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
  2.1206 -
  2.1207 -OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
  2.1208 -CONFIG_BLK_DEV_OPTI621
  2.1209 -  This is a driver for the OPTi 82C621 EIDE controller.
  2.1210 -  Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
  2.1211 -
  2.1212 -ServerWorks OSB4/CSB5 chipset support
  2.1213 -CONFIG_BLK_DEV_SVWKS
  2.1214 -  This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
  2.1215 -  chipsets.
  2.1216 -
  2.1217 -Intel PIIXn chipsets support
  2.1218 -CONFIG_BLK_DEV_PIIX
  2.1219 -  This driver adds PIO mode setting and tuning for all PIIX IDE
  2.1220 -  controllers by Intel.  Since the BIOS can sometimes improperly tune
  2.1221 -  PIO 0-4 mode settings, this allows dynamic tuning of the chipset
  2.1222 -  via the standard end-user tool 'hdparm'.
  2.1223 -
  2.1224 -  Please read the comments at the top of <file:drivers/ide/pci/piix.c>.
  2.1225 -
  2.1226 -  If you say Y here, you should also say Y to "PIIXn Tuning support",
  2.1227 -  below.
  2.1228 -
  2.1229 -  If unsure, say N.
  2.1230 -
  2.1231 -PIIXn Tuning support
  2.1232 -CONFIG_PIIX_TUNING
  2.1233 -  This driver extension adds DMA mode setting and tuning for all PIIX
  2.1234 -  IDE controllers by Intel. Since the BIOS can sometimes improperly
  2.1235 -  set up the device/adapter combination and speed limits, it has
  2.1236 -  become a necessity to back/forward speed devices as needed.
  2.1237 -
  2.1238 -  Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
  2.1239 -  2 if the BIOS can not perform this task at initialization.
  2.1240 -
  2.1241 -  If unsure, say N.
  2.1242 -
  2.1243 -PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
  2.1244 -CONFIG_BLK_DEV_PDC202XX_OLD
  2.1245 -  Promise Ultra33 or PDC20246
  2.1246 -  Promise Ultra66 or PDC20262
  2.1247 -  Promise Ultra100 or PDC20265/PDC20267/PDC20268
  2.1248 -
  2.1249 -  This driver adds up to 4 more EIDE devices sharing a single
  2.1250 -  interrupt. This add-on card is a bootable PCI UDMA controller. Since
  2.1251 -  multiple cards can be installed and there are BIOS ROM problems that
  2.1252 -  happen if the BIOS revisions of all installed cards (three-max) do
  2.1253 -  not match, the driver attempts to do dynamic tuning of the chipset
  2.1254 -  at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
  2.1255 -  for more than one card. This card may require that you say Y to
  2.1256 -  "Special UDMA Feature".
  2.1257 -
  2.1258 -  If you say Y here, you need to say Y to "Use DMA by default when
  2.1259 -  available" as well.
  2.1260 -
  2.1261 -  Please read the comments at the top of
  2.1262 -  <file:drivers/ide/pci/pdc202xx_old.c>.
  2.1263 -
  2.1264 -  If unsure, say N.
  2.1265 -
  2.1266 -Special UDMA Feature
  2.1267 -CONFIG_PDC202XX_BURST
  2.1268 -  This option causes the pdc202xx driver to enable UDMA modes on the
  2.1269 -  PDC202xx even when the PDC202xx BIOS has not done so.
  2.1270 -
  2.1271 -  It was originally designed for the PDC20246/Ultra33, whose BIOS will
  2.1272 -  only setup UDMA on the first two PDC20246 cards.  It has also been
  2.1273 -  used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
  2.1274 -  when the PDC20265 BIOS has been disabled (for faster boot up).
  2.1275 -
  2.1276 -  Please read the comments at the top of
  2.1277 -  <file:drivers/ide/pci/pdc202xx_old.c>.
  2.1278 -
  2.1279 -  If unsure, say N.
  2.1280 -
  2.1281 -Special FastTrak Feature
  2.1282 -CONFIG_PDC202XX_FORCE
  2.1283 -  For FastTrak enable overriding BIOS.
  2.1284 -
  2.1285 -SiS5513 chipset support
  2.1286 -CONFIG_BLK_DEV_SIS5513
  2.1287 -  This driver ensures (U)DMA support for SIS5513 chipset family based
  2.1288 -  mainboards.
  2.1289 -
  2.1290 -  The following chipsets are supported:
  2.1291 -  ATA16:  SiS5511, SiS5513
  2.1292 -  ATA33:  SiS5591, SiS5597, SiS5598, SiS5600
  2.1293 -  ATA66:  SiS530, SiS540, SiS620, SiS630, SiS640
  2.1294 -  ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
  2.1295 -          SiS745, SiS750
  2.1296 -
  2.1297 -  If you say Y here, you need to say Y to "Use DMA by default when
  2.1298 -  available" as well.
  2.1299 -
  2.1300 -  Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
  2.1301 -
  2.1302 -Silicon Image chipset support
  2.1303 -CONFIG_BLK_DEV_SIIMAGE
  2.1304 -  This driver provides (U)DMA support for the SII3112 SATA controllers and
  2.1305 -  for the CMD/SI680 UDMA/DMA ATA controller.
  2.1306 -
  2.1307 -SLC90E66 chipset support
  2.1308 -CONFIG_BLK_DEV_SLC90E66
  2.1309 -  This driver ensures (U)DMA support for Victroy66 SouthBridges for
  2.1310 -  SMsC with Intel NorthBridges.  This is an Ultra66 based chipset.
  2.1311 -  The nice thing about it is that you can mix Ultra/DMA/PIO devices
  2.1312 -  and it will handle timing cycles.  Since this is an improved
  2.1313 -  look-a-like to the PIIX4 it should be a nice addition.
  2.1314 -
  2.1315 -  If you say Y here, you need to say Y to "Use DMA by default when
  2.1316 -  available" as well.
  2.1317 -
  2.1318 -  Please read the comments at the top of
  2.1319 -  <file:drivers/ide/pci/slc90e66.c>.
  2.1320 -
  2.1321 -Winbond SL82c105 support
  2.1322 -CONFIG_BLK_DEV_SL82C105
  2.1323 -  If you have a Winbond SL82c105 IDE controller, say Y here to enable
  2.1324 -  special configuration for this chip. This is common on various CHRP
  2.1325 -  motherboards, but could be used elsewhere. If in doubt, say Y.
  2.1326 -
  2.1327 -Tekram TRM290 chipset support
  2.1328 -CONFIG_BLK_DEV_TRM290
  2.1329 -  This driver adds support for bus master DMA transfers
  2.1330 -  using the Tekram TRM290 PCI IDE chip. Volunteers are
  2.1331 -  needed for further tweaking and development.
  2.1332 -  Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
  2.1333 -
  2.1334 -VIA82CXXX chipset support
  2.1335 -CONFIG_BLK_DEV_VIA82CXXX
  2.1336 -  This allows you to configure your chipset for a better use while
  2.1337 -  running PIO/(U)DMA, it will allow you to enable efficiently the
  2.1338 -  second channel dma usage, as it may not be set by BIOS.  It will try
  2.1339 -  to set fifo configuration at its best.  It will allow you to get
  2.1340 -  information from /proc/ide/via provided you enabled "/proc file
  2.1341 -  system" support.
  2.1342 -
  2.1343 -  Please read the comments at the top of
  2.1344 -  <file:drivers/ide/pci/via82cxxx.c>.
  2.1345 -
  2.1346 -  If you say Y here, then say Y to "Use DMA by default when available"
  2.1347 -  as well.
  2.1348 -
  2.1349 -  If unsure, say N.
  2.1350 -
  2.1351 -RapIDE interface support
  2.1352 -CONFIG_BLK_DEV_IDE_RAPIDE
  2.1353 -  Say Y here if you want to support the Yellowstone RapIDE controller
  2.1354 -  manufactured for use with Acorn computers.
  2.1355 -
  2.1356 -Other IDE chipset support
  2.1357 -CONFIG_IDE_CHIPSETS
  2.1358 -  Say Y here if you want to include enhanced support for various IDE
  2.1359 -  interface chipsets used on motherboards and add-on cards. You can
  2.1360 -  then pick your particular IDE chip from among the following options.
  2.1361 -  This enhanced support may be necessary for Linux to be able to
  2.1362 -  access the 3rd/4th drives in some systems. It may also enable
  2.1363 -  setting of higher speed I/O rates to improve system performance with
  2.1364 -  these chipsets. Most of these also require special kernel boot
  2.1365 -  parameters to actually turn on the support at runtime; you can find
  2.1366 -  a list of these in the file <file:Documentation/ide.txt>.
  2.1367 -
  2.1368 -  People with SCSI-only systems can say N here.
  2.1369 -
  2.1370 -Generic 4 drives/port support
  2.1371 -CONFIG_BLK_DEV_4DRIVES
  2.1372 -  Certain older chipsets, including the Tekram 690CD, use a single set
  2.1373 -  of I/O ports at 0x1f0 to control up to four drives, instead of the
  2.1374 -  customary two drives per port. Support for this can be enabled at
  2.1375 -  runtime using the "ide0=four" kernel boot parameter if you say Y
  2.1376 -  here.
  2.1377 -
  2.1378 -ALI M14xx support
  2.1379 -CONFIG_BLK_DEV_ALI14XX
  2.1380 -  This driver is enabled at runtime using the "ide0=ali14xx" kernel
  2.1381 -  boot parameter.  It enables support for the secondary IDE interface
  2.1382 -  of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
  2.1383 -  I/O speeds to be set as well.  See the files
  2.1384 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
  2.1385 -  more info.
  2.1386 -
  2.1387 -DTC-2278 support
  2.1388 -CONFIG_BLK_DEV_DTC2278
  2.1389 -  This driver is enabled at runtime using the "ide0=dtc2278" kernel
  2.1390 -  boot parameter. It enables support for the secondary IDE interface
  2.1391 -  of the DTC-2278 card, and permits faster I/O speeds to be set as
  2.1392 -  well. See the <file:Documentation/ide.txt> and
  2.1393 -  <file:drivers/ide/legacy/dtc2278.c> files for more info.
  2.1394 -
  2.1395 -Holtek HT6560B support
  2.1396 -CONFIG_BLK_DEV_HT6560B
  2.1397 -  This driver is enabled at runtime using the "ide0=ht6560b" kernel
  2.1398 -  boot parameter. It enables support for the secondary IDE interface
  2.1399 -  of the Holtek card, and permits faster I/O speeds to be set as well.
  2.1400 -  See the <file:Documentation/ide.txt> and
  2.1401 -  <file:drivers/ide/legacy/ht6560b.c> files for more info.
  2.1402 -
  2.1403 -PROMISE DC4030 support (EXPERIMENTAL)
  2.1404 -CONFIG_BLK_DEV_PDC4030
  2.1405 -  This driver provides support for the secondary IDE interface and
  2.1406 -  cache of Promise IDE chipsets, e.g. DC4030 and DC5030.  This driver
  2.1407 -  is known to incur timeouts/retries during heavy I/O to drives
  2.1408 -  attached to the secondary interface.  CD-ROM and TAPE devices are
  2.1409 -  not supported yet.  This driver is enabled at runtime using the
  2.1410 -  "ide0=dc4030" kernel boot parameter.  See the
  2.1411 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/pdc4030.c> files
  2.1412 -  for more info.
  2.1413 -
  2.1414 -QDI QD65XX support
  2.1415 -CONFIG_BLK_DEV_QD65XX
  2.1416 -  This driver is enabled at runtime using the "ide0=qd65xx" kernel
  2.1417 -  boot parameter.  It permits faster I/O speeds to be set.  See the
  2.1418 -  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
  2.1419 -  more info.
  2.1420 -
  2.1421 -UMC 8672 support
  2.1422 -CONFIG_BLK_DEV_UMC8672
  2.1423 -  This driver is enabled at runtime using the "ide0=umc8672" kernel
  2.1424 -  boot parameter. It enables support for the secondary IDE interface
  2.1425 -  of the UMC-8672, and permits faster I/O speeds to be set as well.
  2.1426 -  See the files <file:Documentation/ide.txt> and
  2.1427 -  <file:drivers/ide/legacy/umc8672.c> for more info.
  2.1428 -
  2.1429 -Amiga Gayle IDE interface support
  2.1430 -CONFIG_BLK_DEV_GAYLE
  2.1431 -  This is the IDE driver for the builtin IDE interface on some Amiga
  2.1432 -  models. It supports both the `A1200 style' (used in A600 and A1200)
  2.1433 -  and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
  2.1434 -  interface. Say Y if you have such an Amiga model and want to use IDE
  2.1435 -  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  2.1436 -  builtin IDE interface.
  2.1437 -
  2.1438 -Falcon IDE interface support
  2.1439 -CONFIG_BLK_DEV_FALCON_IDE
  2.1440 -  This is the IDE driver for the builtin IDE interface on the Atari
  2.1441 -  Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
  2.1442 -  disks, CD-ROM drives, etc.) that are connected to the builtin IDE
  2.1443 -  interface.
  2.1444 -
  2.1445 -Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
  2.1446 -CONFIG_BLK_DEV_BUDDHA
  2.1447 -  This is the IDE driver for the IDE interfaces on the Buddha, 
  2.1448 -  Catweasel and X-Surf expansion boards.  It supports up to two interfaces 
  2.1449 -  on the Buddha, three on the Catweasel and two on the X-Surf.
  2.1450 -
  2.1451 -  Say Y if you have a Buddha or Catweasel expansion board and want to
  2.1452 -  use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
  2.1453 -  to one of its IDE interfaces.
  2.1454 -
  2.1455 -Amiga IDE Doubler support (EXPERIMENTAL)
  2.1456 -CONFIG_BLK_DEV_IDEDOUBLER
  2.1457 -  This driver provides support for the so-called `IDE doublers' (made
  2.1458 -  by various manufacturers, e.g. Eyetech) that can be connected to the
  2.1459 -  builtin IDE interface of some Amiga models. Using such an IDE
  2.1460 -  doubler, you can connect up to four instead of two IDE devices on
  2.1461 -  the Amiga's builtin IDE interface.
  2.1462 -
  2.1463 -  Note that the normal Amiga Gayle IDE driver may not work correctly
  2.1464 -  if you have an IDE doubler and don't enable this driver!
  2.1465 -
  2.1466 -  Say Y if you have an IDE doubler.  The driver is enabled at kernel
  2.1467 -  runtime using the "ide=doubler" kernel boot parameter.
  2.1468 -
  2.1469 -WarpEngine SCSI support
  2.1470 -CONFIG_WARPENGINE_SCSI
  2.1471 -  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
  2.1472 -  controller. Info at
  2.1473 -  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
  2.1474 -
  2.1475 -Builtin PowerMac IDE support
  2.1476 -CONFIG_BLK_DEV_IDE_PMAC
  2.1477 -  This driver provides support for the built-in IDE controller on
  2.1478 -  most of the recent Apple Power Macintoshes and PowerBooks.
  2.1479 -  If unsure, say Y.
  2.1480 -
  2.1481 -PowerMac IDE DMA support
  2.1482 -CONFIG_BLK_DEV_IDEDMA_PMAC
  2.1483 -  This option allows the driver for the built-in IDE controller on
  2.1484 -  Power Macintoshes and PowerBooks to use DMA (direct memory access)
  2.1485 -  to transfer data to and from memory.  Saying Y is safe and improves
  2.1486 -  performance.
  2.1487 -
  2.1488 -Use DMA by default
  2.1489 -CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
  2.1490 -  This option allows the driver for the built-in IDE controller on
  2.1491 -  Power Macintoshes and PowerBooks to use DMA automatically, without
  2.1492 -  it having to be explicitly enabled.  This option is provided because
  2.1493 -  of concerns about a couple of cases where using DMA on buggy PC
  2.1494 -  hardware may have caused damage.  Saying Y should be safe on all
  2.1495 -  Apple machines.
  2.1496 -
  2.1497 -Macintosh Quadra/Powerbook IDE interface support
  2.1498 -CONFIG_BLK_DEV_MAC_IDE
  2.1499 -  This is the IDE driver for the builtin IDE interface on some m68k
  2.1500 -  Macintosh models. It supports both the `Quadra style' (used in
  2.1501 -  Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
  2.1502 -  (used in the Powerbook 150 and 190 models) IDE interface.
  2.1503 -
  2.1504 -  Say Y if you have such an Macintosh model and want to use IDE
  2.1505 -  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  2.1506 -  builtin IDE interface.
  2.1507 -
  2.1508 -ICS IDE interface support
  2.1509 -CONFIG_BLK_DEV_IDE_ICSIDE
  2.1510 -  On Acorn systems, say Y here if you wish to use the ICS IDE
  2.1511 -  interface card.  This is not required for ICS partition support.
  2.1512 -  If you are unsure, say N to this.
  2.1513 -
  2.1514 -ICS DMA support
  2.1515 -CONFIG_BLK_DEV_IDEDMA_ICS
  2.1516 -  Say Y here if you want to add DMA (Direct Memory Access) support to
  2.1517 -  the ICS IDE driver.
  2.1518 -
  2.1519 -Use ICS DMA by default
  2.1520 -CONFIG_IDEDMA_ICS_AUTO
  2.1521 -  Prior to kernel version 2.1.112, Linux used to automatically use
  2.1522 -  DMA for IDE drives and chipsets which support it. Due to concerns
  2.1523 -  about a couple of cases where buggy hardware may have caused damage,
  2.1524 -  the default is now to NOT use DMA automatically. To revert to the
  2.1525 -  previous behaviour, say Y to this question.
  2.1526 -
  2.1527 -  If you suspect your hardware is at all flakey, say N here.
  2.1528 -  Do NOT email the IDE kernel people regarding this issue!
  2.1529 -
  2.1530 -XT hard disk support
  2.1531 -CONFIG_BLK_DEV_XD
  2.1532 -  Very old 8 bit hard disk controllers used in the IBM XT computer
  2.1533 -  will be supported if you say Y here.
  2.1534 -
  2.1535 -  If you want to compile the driver as a module ( = code which can be
  2.1536 -  inserted in and removed from the running kernel whenever you want),
  2.1537 -  say M here and read <file:Documentation/modules.txt>. The module
  2.1538 -  will be called xd.o.
  2.1539 -
  2.1540 -  It's pretty unlikely that you have one of these: say N.
  2.1541 -
  2.1542 -PS/2 ESDI hard disk support
  2.1543 -CONFIG_BLK_DEV_PS2
  2.1544 -  Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  2.1545 -  hard disk.
  2.1546 -
  2.1547 -  If you want to compile the driver as a module ( = code which can be
  2.1548 -  inserted in and removed from the running kernel whenever you want),
  2.1549 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.1550 -  will be called ps2esdi.o.
  2.1551 -
  2.1552 -Mylex DAC960/DAC1100 PCI RAID Controller support
  2.1553 -CONFIG_BLK_DEV_DAC960
  2.1554 -  This driver adds support for the Mylex DAC960, AcceleRAID, and
  2.1555 -  eXtremeRAID PCI RAID controllers.  See the file
  2.1556 -  <file:Documentation/README.DAC960> for further information about
  2.1557 -  this driver.
  2.1558 -
  2.1559 -  If you want to compile the driver as a module ( = code which can be
  2.1560 -  inserted in and removed from the running kernel whenever you want),
  2.1561 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.1562 -  will be called DAC960.o.
  2.1563 -
  2.1564 -Parallel port IDE device support
  2.1565 -CONFIG_PARIDE
  2.1566 -  There are many external CD-ROM and disk devices that connect through
  2.1567 -  your computer's parallel port. Most of them are actually IDE devices
  2.1568 -  using a parallel port IDE adapter. This option enables the PARIDE
  2.1569 -  subsystem which contains drivers for many of these external drives.
  2.1570 -  Read <file:Documentation/paride.txt> for more information.
  2.1571 -
  2.1572 -  If you have said Y to the "Parallel-port support" configuration
  2.1573 -  option, you may share a single port between your printer and other
  2.1574 -  parallel port devices. Answer Y to build PARIDE support into your
  2.1575 -  kernel, or M if you would like to build it as a loadable module. If
  2.1576 -  your parallel port support is in a loadable module, you must build
  2.1577 -  PARIDE as a module. If you built PARIDE support into your kernel,
  2.1578 -  you may still build the individual protocol modules and high-level
  2.1579 -  drivers as loadable modules. If you build this support as a module,
  2.1580 -  it will be called paride.o.
  2.1581 -
  2.1582 -  To use the PARIDE support, you must say Y or M here and also to at
  2.1583 -  least one high-level driver (e.g. "Parallel port IDE disks",
  2.1584 -  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  2.1585 -  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  2.1586 -  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  2.1587 -  etc.).
  2.1588 -
  2.1589 -Parallel port IDE disks
  2.1590 -CONFIG_PARIDE_PD
  2.1591 -  This option enables the high-level driver for IDE-type disk devices
  2.1592 -  connected through a parallel port. If you chose to build PARIDE
  2.1593 -  support into your kernel, you may answer Y here to build in the
  2.1594 -  parallel port IDE driver, otherwise you should answer M to build
  2.1595 -  it as a loadable module. The module will be called pd.o. You
  2.1596 -  must also have at least one parallel port protocol driver in your
  2.1597 -  system. Among the devices supported by this driver are the SyQuest
  2.1598 -  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
  2.1599 -  hard drives from MicroSolutions.
  2.1600 -
  2.1601 -Parallel port ATAPI CD-ROMs
  2.1602 -CONFIG_PARIDE_PCD
  2.1603 -  This option enables the high-level driver for ATAPI CD-ROM devices
  2.1604 -  connected through a parallel port. If you chose to build PARIDE
  2.1605 -  support into your kernel, you may answer Y here to build in the
  2.1606 -  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
  2.1607 -  build it as a loadable module. The module will be called pcd.o. You
  2.1608 -  must also have at least one parallel port protocol driver in your
  2.1609 -  system. Among the devices supported by this driver are the
  2.1610 -  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
  2.1611 -  you have such a CD-ROM drive, you should also say Y or M to "ISO
  2.1612 -  9660 CD-ROM file system support" below, because that's the file
  2.1613 -  system used on CD-ROMs.
  2.1614 -
  2.1615 -Parallel port ATAPI disks
  2.1616 -CONFIG_PARIDE_PF
  2.1617 -  This option enables the high-level driver for ATAPI disk devices
  2.1618 -  connected through a parallel port. If you chose to build PARIDE
  2.1619 -  support into your kernel, you may answer Y here to build in the
  2.1620 -  parallel port ATAPI disk driver, otherwise you should answer M
  2.1621 -  to build it as a loadable module. The module will be called pf.o.
  2.1622 -  You must also have at least one parallel port protocol driver in
  2.1623 -  your system. Among the devices supported by this driver are the
  2.1624 -  MicroSolutions backpack PD/CD drive and the Imation Superdisk
  2.1625 -  LS-120 drive.
  2.1626 -
  2.1627 -Parallel port ATAPI tapes
  2.1628 -CONFIG_PARIDE_PT
  2.1629 -  This option enables the high-level driver for ATAPI tape devices
  2.1630 -  connected through a parallel port. If you chose to build PARIDE
  2.1631 -  support into your kernel, you may answer Y here to build in the
  2.1632 -  parallel port ATAPI disk driver, otherwise you should answer M
  2.1633 -  to build it as a loadable module. The module will be called pt.o.
  2.1634 -  You must also have at least one parallel port protocol driver in
  2.1635 -  your system. Among the devices supported by this driver is the
  2.1636 -  parallel port version of the HP 5GB drive.
  2.1637 -
  2.1638 -Parallel port generic ATAPI devices
  2.1639 -CONFIG_PARIDE_PG
  2.1640 -  This option enables a special high-level driver for generic ATAPI
  2.1641 -  devices connected through a parallel port. The driver allows user
  2.1642 -  programs, such as cdrtools, to send ATAPI commands directly to a
  2.1643 -  device.
  2.1644 -
  2.1645 -  If you chose to build PARIDE support into your kernel, you may
  2.1646 -  answer Y here to build in the parallel port generic ATAPI driver,
  2.1647 -  otherwise you should answer M to build it as a loadable module. The
  2.1648 -  module will be called pg.o.
  2.1649 -
  2.1650 -  You must also have at least one parallel port protocol driver in
  2.1651 -  your system.
  2.1652 -
  2.1653 -  This driver implements an API loosely related to the generic SCSI
  2.1654 -  driver. See <file:include/linux/pg.h>. for details.
  2.1655 -
  2.1656 -  You can obtain the most recent version of cdrtools from
  2.1657 -  <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
  2.1658 -  later fully support this driver.
  2.1659 -
  2.1660 -ATEN EH-100 protocol
  2.1661 -CONFIG_PARIDE_ATEN
  2.1662 -  This option enables support for the ATEN EH-100 parallel port IDE
  2.1663 -  protocol. This protocol is used in some inexpensive low performance
  2.1664 -  parallel port kits made in Hong Kong. If you chose to build PARIDE
  2.1665 -  support into your kernel, you may answer Y here to build in the
  2.1666 -  protocol driver, otherwise you should answer M to build it as a
  2.1667 -  loadable module. The module will be called aten.o. You must also
  2.1668 -  have a high-level driver for the type of device that you want to
  2.1669 -  support.
  2.1670 -
  2.1671 -Micro Solutions BACKPACK Series 5 protocol
  2.1672 -CONFIG_PARIDE_BPCK
  2.1673 -  This option enables support for the Micro Solutions BACKPACK
  2.1674 -  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
  2.1675 -  before 1999 were Series 5) Series 5 drives will NOT always have the
  2.1676 -  Series noted on the bottom of the drive. Series 6 drivers will.
  2.1677 -
  2.1678 -  In other words, if your BACKPACK drive dosen't say "Series 6" on the
  2.1679 -  bottom, enable this option.
  2.1680 -
  2.1681 -  If you chose to build PARIDE support into your kernel, you may
  2.1682 -  answer Y here to build in the protocol driver, otherwise you should
  2.1683 -  answer M to build it as a loadable module.  The module will be
  2.1684 -  called bpck.o.  You must also have a high-level driver for the type
  2.1685 -  of device that you want to support.
  2.1686 -
  2.1687 -Micro Solutions BACKPACK Series 6 protocol
  2.1688 -CONFIG_PARIDE_BPCK6
  2.1689 -  This option enables support for the Micro Solutions BACKPACK
  2.1690 -  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
  2.1691 -  after 1999 were Series 6) Series 6 drives will have the Series noted
  2.1692 -  on the bottom of the drive.  Series 5 drivers don't always have it
  2.1693 -  noted.
  2.1694 -
  2.1695 -  In other words, if your BACKPACK drive says "Series 6" on the
  2.1696 -  bottom, enable this option.
  2.1697 -
  2.1698 -  If you chose to build PARIDE support into your kernel, you may
  2.1699 -  answer Y here to build in the protocol driver, otherwise you should
  2.1700 -  answer M to build it as a loadable module.  The module will be
  2.1701 -  called bpck6.o.  You must also have a high-level driver for the type
  2.1702 -  of device that you want to support.
  2.1703 -
  2.1704 -DataStor Commuter protocol
  2.1705 -CONFIG_PARIDE_COMM
  2.1706 -  This option enables support for the Commuter parallel port IDE
  2.1707 -  protocol from DataStor. If you chose to build PARIDE support
  2.1708 -  into your kernel, you may answer Y here to build in the protocol
  2.1709 -  driver, otherwise you should answer M to build it as a loadable
  2.1710 -  module. The module will be called comm.o. You must also have
  2.1711 -  a high-level driver for the type of device that you want to support.
  2.1712 -
  2.1713 -DataStor EP-2000 protocol
  2.1714 -CONFIG_PARIDE_DSTR
  2.1715 -  This option enables support for the EP-2000 parallel port IDE
  2.1716 -  protocol from DataStor. If you chose to build PARIDE support
  2.1717 -  into your kernel, you may answer Y here to build in the protocol
  2.1718 -  driver, otherwise you should answer M to build it as a loadable
  2.1719 -  module. The module will be called dstr.o. You must also have
  2.1720 -  a high-level driver for the type of device that you want to support.
  2.1721 -
  2.1722 -Shuttle EPAT/EPEZ protocol
  2.1723 -CONFIG_PARIDE_EPAT
  2.1724 -  This option enables support for the EPAT parallel port IDE protocol.
  2.1725 -  EPAT is a parallel port IDE adapter manufactured by Shuttle
  2.1726 -  Technology and widely used in devices from major vendors such as
  2.1727 -  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
  2.1728 -  PARIDE support into your kernel, you may answer Y here to build in
  2.1729 -  the protocol driver, otherwise you should answer M to build it as a
  2.1730 -  loadable module. The module will be called epat.o. You must also
  2.1731 -  have a high-level driver for the type of device that you want to
  2.1732 -  support.
  2.1733 -
  2.1734 -Shuttle EPAT c7/c8 extension
  2.1735 -CONFIG_PARIDE_EPATC8
  2.1736 -  This option enables support for the newer Shuttle EP1284 (aka c7 and
  2.1737 -  c8) chip. You need this if you are using any recent Imation SuperDisk
  2.1738 -  (LS-120) drive.
  2.1739 -
  2.1740 -Shuttle EPIA protocol
  2.1741 -CONFIG_PARIDE_EPIA
  2.1742 -  This option enables support for the (obsolete) EPIA parallel port
  2.1743 -  IDE protocol from Shuttle Technology. This adapter can still be
  2.1744 -  found in some no-name kits. If you chose to build PARIDE support
  2.1745 -  into your kernel, you may answer Y here to build in the protocol
  2.1746 -  driver, otherwise you should answer M to build it as a loadable
  2.1747 -  module. The module will be called epia.o. You must also have a
  2.1748 -  high-level driver for the type of device that you want to support.
  2.1749 -
  2.1750 -FIT TD-2000 protocol
  2.1751 -CONFIG_PARIDE_FIT2
  2.1752 -  This option enables support for the TD-2000 parallel port IDE
  2.1753 -  protocol from Fidelity International Technology. This is a simple
  2.1754 -  (low speed) adapter that is used in some portable hard drives. If
  2.1755 -  you chose to build PARIDE support into your kernel, you may answer Y
  2.1756 -  here to build in the protocol driver, otherwise you should answer M
  2.1757 -  to build it as a loadable module. The module will be called fit2.o.
  2.1758 -  You must also have a high-level driver for the type of device that
  2.1759 -  you want to support.
  2.1760 -
  2.1761 -FIT TD-3000 protocol
  2.1762 -CONFIG_PARIDE_FIT3
  2.1763 -  This option enables support for the TD-3000 parallel port IDE
  2.1764 -  protocol from Fidelity International Technology. This protocol is
  2.1765 -  used in newer models of their portable disk, CD-ROM and PD/CD
  2.1766 -  devices. If you chose to build PARIDE support into your kernel, you
  2.1767 -  may answer Y here to build in the protocol driver, otherwise you
  2.1768 -  should answer M to build it as a loadable module. The module will be
  2.1769 -  called fit3.o. You must also have a high-level driver for the type
  2.1770 -  of device that you want to support.
  2.1771 -
  2.1772 -Freecom IQ ASIC-2 protocol
  2.1773 -CONFIG_PARIDE_FRIQ
  2.1774 -  This option enables support for version 2 of the Freecom IQ parallel
  2.1775 -  port IDE adapter.  This adapter is used by the Maxell Superdisk
  2.1776 -  drive.  If you chose to build PARIDE support into your kernel, you
  2.1777 -  may answer Y here to build in the protocol driver, otherwise you
  2.1778 -  should answer M to build it as a loadable module. The module will be
  2.1779 -  called friq.o. You must also have a high-level driver for the type
  2.1780 -  of device that you want to support.
  2.1781 -
  2.1782 -FreeCom power protocol
  2.1783 -CONFIG_PARIDE_FRPW
  2.1784 -  This option enables support for the Freecom power parallel port IDE
  2.1785 -  protocol. If you chose to build PARIDE support into your kernel, you
  2.1786 -  may answer Y here to build in the protocol driver, otherwise you
  2.1787 -  should answer M to build it as a loadable module. The module will be
  2.1788 -  called frpw.o. You must also have a high-level driver for the type
  2.1789 -  of device that you want to support.
  2.1790 -
  2.1791 -KingByte KBIC-951A/971A protocols
  2.1792 -CONFIG_PARIDE_KBIC
  2.1793 -  This option enables support for the KBIC-951A and KBIC-971A parallel
  2.1794 -  port IDE protocols from KingByte Information Corp. KingByte's
  2.1795 -  adapters appear in many no-name portable disk and CD-ROM products,
  2.1796 -  especially in Europe. If you chose to build PARIDE support into your
  2.1797 -  kernel, you may answer Y here to build in the protocol driver,
  2.1798 -  otherwise you should answer M to build it as a loadable module. The
  2.1799 -  module will be called kbic.o. You must also have a high-level driver
  2.1800 -  for the type of device that you want to support.
  2.1801 -
  2.1802 -KT PHd protocol
  2.1803 -CONFIG_PARIDE_KTTI
  2.1804 -  This option enables support for the "PHd" parallel port IDE protocol
  2.1805 -  from KT Technology. This is a simple (low speed) adapter that is
  2.1806 -  used in some 2.5" portable hard drives. If you chose to build PARIDE
  2.1807 -  support into your kernel, you may answer Y here to build in the
  2.1808 -  protocol driver, otherwise you should answer M to build it as a
  2.1809 -  loadable module. The module will be called ktti.o. You must also
  2.1810 -  have a high-level driver for the type of device that you want to
  2.1811 -  support.
  2.1812 -
  2.1813 -OnSpec 90c20 protocol
  2.1814 -CONFIG_PARIDE_ON20
  2.1815 -  This option enables support for the (obsolete) 90c20 parallel port
  2.1816 -  IDE protocol from OnSpec (often marketed under the ValuStore brand
  2.1817 -  name). If you chose to build PARIDE support into your kernel, you
  2.1818 -  may answer Y here to build in the protocol driver, otherwise you
  2.1819 -  should answer M to build it as a loadable module. The module will
  2.1820 -  be called on20.o. You must also have a high-level driver for the
  2.1821 -  type of device that you want to support.
  2.1822 -
  2.1823 -OnSpec 90c26 protocol
  2.1824 -CONFIG_PARIDE_ON26
  2.1825 -  This option enables support for the 90c26 parallel port IDE protocol
  2.1826 -  from OnSpec Electronics (often marketed under the ValuStore brand
  2.1827 -  name). If you chose to build PARIDE support into your kernel, you
  2.1828 -  may answer Y here to build in the protocol driver, otherwise you
  2.1829 -  should answer M to build it as a loadable module. The module will be
  2.1830 -  called on26.o. You must also have a high-level driver for the type
  2.1831 -  of device that you want to support.
  2.1832 -
  2.1833 -Logical Volume Manager (LVM) support
  2.1834 -CONFIG_BLK_DEV_LVM
  2.1835 -  This driver lets you combine several hard disks, hard disk
  2.1836 -  partitions, multiple devices or even loop devices (for evaluation
  2.1837 -  purposes) into a volume group.  Imagine a volume group as a kind of
  2.1838 -  virtual disk. Logical volumes, which can be thought of as virtual
  2.1839 -  partitions, can be created in the volume group.  You can resize
  2.1840 -  volume groups and logical volumes after creation time, corresponding
  2.1841 -  to new capacity needs.  Logical volumes are accessed as block
  2.1842 -  devices named /dev/VolumeGroupName/LogicalVolumeName.
  2.1843 -
  2.1844 -  For details see <file:Documentation/LVM-HOWTO>.  You will need
  2.1845 -  supporting user space software; location is in
  2.1846 -  <file:Documentation/Changes>.
  2.1847 -
  2.1848 -  If you want to compile this support as a module ( = code which can
  2.1849 -  be inserted in and removed from the running kernel whenever you
  2.1850 -  want), say M here and read <file:Documentation/modules.txt>.  The
  2.1851 -  module will be called lvm-mod.o.
  2.1852 -
  2.1853 -Multiple devices driver support (RAID and LVM)
  2.1854 -CONFIG_MD
  2.1855 -  Support multiple physical spindles through a single logical device.
  2.1856 -  Required for RAID and logical volume management (LVM).
  2.1857 -
  2.1858 -Multiple devices driver support
  2.1859 -CONFIG_BLK_DEV_MD
  2.1860 -  This driver lets you combine several hard disk partitions into one
  2.1861 -  logical block device. This can be used to simply append one
  2.1862 -  partition to another one or to combine several redundant hard disks
  2.1863 -  into a RAID1/4/5 device so as to provide protection against hard
  2.1864 -  disk failures. This is called "Software RAID" since the combining of
  2.1865 -  the partitions is done by the kernel. "Hardware RAID" means that the
  2.1866 -  combining is done by a dedicated controller; if you have such a
  2.1867 -  controller, you do not need to say Y here.
  2.1868 -
  2.1869 -  More information about Software RAID on Linux is contained in the
  2.1870 -  Software RAID mini-HOWTO, available from
  2.1871 -  <http://www.tldp.org/docs.html#howto>. There you will also learn
  2.1872 -  where to get the supporting user space utilities raidtools.
  2.1873 -
  2.1874 -  This driver is also available as a module ( = code which can be
  2.1875 -  inserted in and removed from the running kernel whenever you want).
  2.1876 -  If you want to compile it as a module, say M here and read
  2.1877 -  <file:Documentation/modules.txt>. The module will be called
  2.1878 -  md.o
  2.1879 -
  2.1880 -  If unsure, say N.
  2.1881 -
  2.1882 -Linear (append) mode
  2.1883 -CONFIG_MD_LINEAR
  2.1884 -  If you say Y here, then your multiple devices driver will be able to
  2.1885 -  use the so-called linear mode, i.e. it will combine the hard disk
  2.1886 -  partitions by simply appending one to the other.
  2.1887 -
  2.1888 -  If you want to compile this as a module ( = code which can be
  2.1889 -  inserted in and removed from the running kernel whenever you want),
  2.1890 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.1891 -  will be called linear.o.
  2.1892 -
  2.1893 -  If unsure, say Y.
  2.1894 -
  2.1895 -RAID-0 (striping) mode
  2.1896 -CONFIG_MD_RAID0
  2.1897 -  If you say Y here, then your multiple devices driver will be able to
  2.1898 -  use the so-called raid0 mode, i.e. it will combine the hard disk
  2.1899 -  partitions into one logical device in such a fashion as to fill them
  2.1900 -  up evenly, one chunk here and one chunk there. This will increase
  2.1901 -  the throughput rate if the partitions reside on distinct disks.
  2.1902 -
  2.1903 -  Information about Software RAID on Linux is contained in the
  2.1904 -  Software-RAID mini-HOWTO, available from
  2.1905 -  <http://www.tldp.org/docs.html#howto>. There you will also
  2.1906 -  learn where to get the supporting user space utilities raidtools.
  2.1907 -
  2.1908 -  If you want to compile this as a module ( = code which can be
  2.1909 -  inserted in and removed from the running kernel whenever you want),
  2.1910 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.1911 -  will be called raid0.o.
  2.1912 -
  2.1913 -  If unsure, say Y.
  2.1914 -
  2.1915 -RAID-1 (mirroring) mode
  2.1916 -CONFIG_MD_RAID1
  2.1917 -  A RAID-1 set consists of several disk drives which are exact copies
  2.1918 -  of each other.  In the event of a mirror failure, the RAID driver
  2.1919 -  will continue to use the operational mirrors in the set, providing
  2.1920 -  an error free MD (multiple device) to the higher levels of the
  2.1921 -  kernel.  In a set with N drives, the available space is the capacity
  2.1922 -  of a single drive, and the set protects against a failure of (N - 1)
  2.1923 -  drives.
  2.1924 -
  2.1925 -  Information about Software RAID on Linux is contained in the
  2.1926 -  Software-RAID mini-HOWTO, available from
  2.1927 -  <http://www.tldp.org/docs.html#howto>.  There you will also
  2.1928 -  learn where to get the supporting user space utilities raidtools.
  2.1929 -
  2.1930 -  If you want to use such a RAID-1 set, say Y. This code is also
  2.1931 -  available as a module called raid1.o ( = code which can be inserted
  2.1932 -  in and removed from the running kernel whenever you want).  If you
  2.1933 -  want to compile it as a module, say M here and read
  2.1934 -  <file:Documentation/modules.txt>.
  2.1935 -
  2.1936 -  If unsure, say Y.
  2.1937 -
  2.1938 -RAID-4/RAID-5 mode
  2.1939 -CONFIG_MD_RAID5
  2.1940 -  A RAID-5 set of N drives with a capacity of C MB per drive provides
  2.1941 -  the capacity of C * (N - 1) MB, and protects against a failure
  2.1942 -  of a single drive. For a given sector (row) number, (N - 1) drives
  2.1943 -  contain data sectors, and one drive contains the parity protection.
  2.1944 -  For a RAID-4 set, the parity blocks are present on a single drive,
  2.1945 -  while a RAID-5 set distributes the parity across the drives in one
  2.1946 -  of the available parity distribution methods.
  2.1947 -
  2.1948 -  Information about Software RAID on Linux is contained in the
  2.1949 -  Software-RAID mini-HOWTO, available from
  2.1950 -  <http://www.tldp.org/docs.html#howto>. There you will also
  2.1951 -  learn where to get the supporting user space utilities raidtools.
  2.1952 -
  2.1953 -  If you want to use such a RAID-4/RAID-5 set, say Y. This code is
  2.1954 -  also available as a module called raid5.o ( = code which can be
  2.1955 -  inserted in and removed from the running kernel whenever you want).
  2.1956 -  If you want to compile it as a module, say M here and read
  2.1957 -  <file:Documentation/modules.txt>.
  2.1958 -
  2.1959 -  If unsure, say Y.
  2.1960 -
  2.1961 -Multipath I/O support
  2.1962 -CONFIG_MD_MULTIPATH
  2.1963 -  Multipath-IO is the ability of certain devices to address the same
  2.1964 -  physical disk over multiple 'IO paths'. The code ensures that such
  2.1965 -  paths can be defined and handled at runtime, and ensures that a
  2.1966 -  transparent failover to the backup path(s) happens if a IO errors
  2.1967 -  arrives on the primary path.
  2.1968 -
  2.1969 -  This driver is also available as a module ( = code which can be
  2.1970 -  inserted in and removed from the running kernel whenever you want).
  2.1971 -  If you want to compile it as a module, say M here and read
  2.1972 -  <file:Documentation/modules.txt>. The module will be called
  2.1973 -  multipath.o
  2.1974 -
  2.1975 -  If unsure, say N.
  2.1976 -
  2.1977 -Support for IDE Raid controllers
  2.1978 -CONFIG_BLK_DEV_ATARAID
  2.1979 -  Say Y or M if you have an IDE Raid controller and want linux
  2.1980 -  to use its softwareraid feature.  You must also select an
  2.1981 -  appropriate for your board low-level driver below.
  2.1982 -
  2.1983 -  Note, that Linux does not use the Raid implementation in BIOS, and
  2.1984 -  the main purpose for this feature is to retain compatibility and
  2.1985 -  data integrity with other OS-es, using the same disk array. Linux
  2.1986 -  has its own Raid drivers, which you should use if you need better
  2.1987 -  performance.
  2.1988 -
  2.1989 -  This driver is also available as a module ( = code which can be
  2.1990 -  inserted in and removed from the running kernel whenever you want).
  2.1991 -  If you want to compile it as a module, say M here and read
  2.1992 -  <file:Documentation/modules.txt>. The module will be called
  2.1993 -  ataraid.o
  2.1994 -
  2.1995 -Support Promise software RAID (Fasttrak(tm))
  2.1996 -CONFIG_BLK_DEV_ATARAID_PDC
  2.1997 -  Say Y or M if you have a Promise Fasttrak (tm) Raid controller
  2.1998 -  and want linux to use the softwareraid feature of this card.
  2.1999 -  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  2.2000 -  names.
  2.2001 -
  2.2002 -  If you choose to compile this as a module, the module will be called
  2.2003 -  pdcraid.o.
  2.2004 -
  2.2005 -Highpoint 370 software RAID
  2.2006 -CONFIG_BLK_DEV_ATARAID_HPT
  2.2007 -  Say Y or M if you have a Highpoint HPT 370 Raid controller
  2.2008 -  and want linux to use the softwareraid feature of this card.
  2.2009 -  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  2.2010 -  names.
  2.2011 -
  2.2012 -  If you choose to compile this as a module, the module will be called
  2.2013 -  hptraid.o.
  2.2014 -
  2.2015 -Support for Acer PICA 1 chipset
  2.2016 -CONFIG_ACER_PICA_61
  2.2017 -  This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
  2.2018 -  kernel that runs on these, say Y here. For details about Linux on
  2.2019 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  2.2020 -  <http://oss.sgi.com/mips/>.
  2.2021 -
  2.2022 -Support for Algorithmics P4032 (EXPERIMENTAL)
  2.2023 -CONFIG_ALGOR_P4032
  2.2024 -  This is an evaluation board of the British company Algorithmics.
  2.2025 -  The board uses the R4300 and a R5230 CPUs.  For more information
  2.2026 -  about this board see <http://www.algor.co.uk/>.
  2.2027 -
  2.2028 -Support for BAGET MIPS series
  2.2029 -CONFIG_BAGET_MIPS
  2.2030 -  This enables support for the Baget, a Russian embedded system.  For
  2.2031 -  more details about the Baget see the Linux/MIPS FAQ on
  2.2032 -  <http://oss.sgi.com/mips/>.
  2.2033 -
  2.2034 -Baget AMD LANCE support
  2.2035 -CONFIG_BAGETLANCE
  2.2036 -  Say Y to enable kernel support for AMD Lance Ethernet cards on the
  2.2037 -  MIPS-32-based Baget embedded system.  This chipset is better known
  2.2038 -  via the NE2100 cards.
  2.2039 -
  2.2040 -Support for DECstations
  2.2041 -CONFIG_DECSTATION
  2.2042 -  This enables support for DEC's MIPS based workstations.  For details
  2.2043 -  see the Linux/MIPS FAQ on <http://oss.sgi.com/mips/> and the
  2.2044 -  DECstation porting pages on <http://decstation.unix-ag.org/>.
  2.2045 -
  2.2046 -  If you have one of the following DECstation Models you definitely
  2.2047 -  want to choose R4xx0 for the CPU Type:
  2.2048 -
  2.2049 -	DECstation 5000/50
  2.2050 -	DECstation 5000/150
  2.2051 -	DECstation 5000/260
  2.2052 -	DECsystem 5900/260
  2.2053 -
  2.2054 -  otherwise choose R3000.
  2.2055 -
  2.2056 -Support for Cobalt Micro Server
  2.2057 -CONFIG_COBALT_MICRO_SERVER
  2.2058 -  Support for MIPS-based Cobalt boxes (they have been bought by Sun
  2.2059 -  and are now the "Server Appliance Business Unit") including the 2700
  2.2060 -  series -- versions 1 of the Qube and Raq.  To compile a Linux kernel
  2.2061 -  for this hardware, say Y here.
  2.2062 -
  2.2063 -Support for Cobalt 2800
  2.2064 -CONFIG_COBALT_28
  2.2065 -  Support for the second generation of MIPS-based Cobalt boxes (they
  2.2066 -  have been bought by Sun and are now the "Server Appliance Business
  2.2067 -  Unit") including the 2800 series -- versions 2 of the Qube and Raq.
  2.2068 -  To compile a Linux kernel for this hardware, say Y here.
  2.2069 -
  2.2070 -Support for the Momentum Computer Ocelot SBC
  2.2071 -CONFIG_MOMENCO_OCELOT
  2.2072 -  The Ocelot is a MIPS-based Single Board Computer (SBC) made by
  2.2073 -  Momentum Computer <http://www.momenco.com/>.
  2.2074 -
  2.2075 -Support for NEC DDB Vrc-5074
  2.2076 -CONFIG_DDB5074
  2.2077 -  This enables support for the VR5000-based NEC DDB Vrc-5074
  2.2078 -  evaluation board.
  2.2079 -
  2.2080 -Support for NEC DDB Vrc-5476
  2.2081 -CONFIG_DDB5476
  2.2082 -  This enables support for the R5432-based NEC DDB Vrc-5476
  2.2083 -  evaluation board.
  2.2084 -
  2.2085 -  Features : kernel debugging, serial terminal, NFS root fs, on-board
  2.2086 -  ether port (Need an additional patch at <http://linux.junsun.net/>),
  2.2087 -  USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
  2.2088 -  PS2 keyboard, PS2 mouse, etc.
  2.2089 -
  2.2090 -Support for NEC DDB Vrc-5477
  2.2091 -CONFIG_DDB5477
  2.2092 -  This enables support for the R5432-based NEC DDB Vrc-5477
  2.2093 -  evaluation board.
  2.2094 -
  2.2095 -  Features : kernel debugging, serial terminal, NFS root fs, on-board
  2.2096 -  ether port (Need an additional patch at <http://linux.junsun.net/>),
  2.2097 -  USB, AC97, PCI, etc.
  2.2098 -
  2.2099 -Support for MIPS Atlas board
  2.2100 -CONFIG_MIPS_ATLAS
  2.2101 -  This enables support for the QED R5231-based MIPS Atlas evaluation
  2.2102 -  board.
  2.2103 -
  2.2104 -Support for MIPS Malta board
  2.2105 -CONFIG_MIPS_MALTA
  2.2106 -  This enables support for the VR5000-based MIPS Malta evaluation
  2.2107 -  board.
  2.2108 -
  2.2109 -Support for Galileo Evaluation board or CoSine Orion
  2.2110 -CONFIG_ORION
  2.2111 -  Say Y if configuring for the Galileo evaluation board
  2.2112 -  or CoSine Orion.  More information is available at
  2.2113 -  <http://tochna.technion.ac.il/project/linux/html/linux.html>.
  2.2114 -
  2.2115 -  Otherwise, say N.
  2.2116 -
  2.2117 -Support for Mips Magnum 4000
  2.2118 -CONFIG_MIPS_MAGNUM_4000
  2.2119 -  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  2.2120 -  kernel that runs on these, say Y here. For details about Linux on
  2.2121 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  2.2122 -  <http://oss.sgi.com/mips/>.
  2.2123 -
  2.2124 -Enable Qtronix 990P Keyboard Support
  2.2125 -CONFIG_QTRONIX_KEYBOARD
  2.2126 -  Images of Qtronix keyboards are at
  2.2127 -  <http://www.qtronix.com/keyboard.html>.
  2.2128 -
  2.2129 -Support for Olivetti M700
  2.2130 -CONFIG_OLIVETTI_M700
  2.2131 -  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  2.2132 -  kernel that runs on these, say Y here. For details about Linux on
  2.2133 -  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  2.2134 -  <http://oss.sgi.com/mips/>.
  2.2135 -
  2.2136 -Support for SNI RM200 PCI
  2.2137 -CONFIG_SNI_RM200_PCI
  2.2138 -  The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
  2.2139 -  Nixdorf Informationssysteme (SNI), parent company of Pyramid
  2.2140 -  Technology and now in turn merged with Fujitsu.  Say Y here to
  2.2141 -  support this machine type.
  2.2142 -
  2.2143 -Support for SGI-IP22 (Indy/Indigo2)
  2.2144 -CONFIG_SGI_IP22
  2.2145 -  This are the SGI Indy, Challenge S and Indigo2, as well as certain
  2.2146 -  OEM variants like the Tandem CMN B006S. To compile a Linux kernel
  2.2147 -  that runs on these, say Y here.
  2.2148 -
  2.2149 -Support for SGI IP27 (Origin200/2000)
  2.2150 -CONFIG_SGI_IP27
  2.2151 -  This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
  2.2152 -  workstations.  To compile a Linux kernel that runs on these, say Y
  2.2153 -  here.
  2.2154 -
  2.2155 -IP27 N-Mode
  2.2156 -CONFIG_SGI_SN0_N_MODE
  2.2157 -  The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
  2.2158 -  configured in either N-Modes which allows for more nodes or M-Mode
  2.2159 -  which allows for more memory.  Your system is most probably
  2.2160 -  running in M-Mode, so you should say N here.
  2.2161 -
  2.2162 -Lasi Ethernet
  2.2163 -CONFIG_LASI_82596
  2.2164 -  Say Y here to support the on-board Intel 82596 ethernet controller
  2.2165 -  built into Hewlett-Packard PA-RISC machines.
  2.2166 -
  2.2167 -MIPS JAZZ onboard SONIC Ethernet support
  2.2168 -CONFIG_MIPS_JAZZ_SONIC
  2.2169 -  This is the driver for the onboard card of MIPS Magnum 4000,
  2.2170 -  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
  2.2171 -
  2.2172 -MIPS JAZZ FAS216 SCSI support
  2.2173 -CONFIG_JAZZ_ESP
  2.2174 -  This is the driver for the onboard SCSI host adapter of MIPS Magnum
  2.2175 -  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
  2.2176 -  systems.
  2.2177 -
  2.2178 -MIPS GT96100 support
  2.2179 -CONFIG_MIPS_GT96100
  2.2180 -  Say Y here to support the Galileo Technology GT96100 communications
  2.2181 -  controller card.  There is a web page at <http://www.galileot.com/>.
  2.2182 -
  2.2183 -MIPS GT96100 Ethernet support
  2.2184 -CONFIG_MIPS_GT96100ETH
  2.2185 -  Say Y here to support the Ethernet subsystem on your GT96100 card.
  2.2186 -
  2.2187 -Zalon SCSI support
  2.2188 -CONFIG_SCSI_ZALON
  2.2189 -  The Zalon is an interface chip that sits between the PA-RISC
  2.2190 -  processor and the NCR 53c720 SCSI controller on K-series PA-RISC
  2.2191 -  boards (these are used, among other places, on some HP 780
  2.2192 -  workstations).  Say Y here to make sure it gets initialized
  2.2193 -  correctly before the Linux kernel tries to talk to the controller.
  2.2194 -
  2.2195 -Kernel floating-point instruction emulation
  2.2196 -CONFIG_MIPS_FPU_EMULATOR
  2.2197 -  This option enables the MIPS software floating support.  Due to
  2.2198 -  the way floating point works you should always enable this option
  2.2199 -  unless you exactly know what you're doing.
  2.2200 -
  2.2201 -SGI PROM Console Support
  2.2202 -CONFIG_SGI_PROM_CONSOLE
  2.2203 -  Say Y here to set up the boot console on serial port 0.
  2.2204 -
  2.2205 -DZ11 Serial Support
  2.2206 -CONFIG_DZ
  2.2207 -  DZ11-family serial controllers for VAXstations, including the
  2.2208 -  DC7085, M7814, and M7819.
  2.2209 -
  2.2210 -TURBOchannel support
  2.2211 -CONFIG_TC
  2.2212 -  TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
  2.2213 -  Documentation on writing device drivers for TurboChannel is available at:
  2.2214 -  <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
  2.2215 -
  2.2216 -# Choice: galileo_clock
  2.2217 -75
  2.2218 -CONFIG_SYSCLK_75
  2.2219 -  Configure the kernel for clock speed of your Galileo board.  
  2.2220 -  The choices are 75MHz, 83.3MHz, and 100MHz.
  2.2221 -
  2.2222 -83.3
  2.2223 -CONFIG_SYSCLK_83
  2.2224 -  Configure the Galileo kernel for a clock speed of 83.3 MHz.
  2.2225 -
  2.2226 -100
  2.2227 -CONFIG_SYSCLK_100
  2.2228 -  Configure the Galileo kernel for a clock speed of 100 MHz.
  2.2229 -
  2.2230 -Z85C30 Serial Support
  2.2231 -CONFIG_ZS
  2.2232 -  Documentation on the Zilog 85C350 serial communications controller
  2.2233 -  is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
  2.2234 -
  2.2235 -PCMCIA SCSI adapter support
  2.2236 -CONFIG_SCSI_PCMCIA
  2.2237 -  Say Y here if you intend to attach a PCMCIA or CardBus card to your
  2.2238 -  computer which acts as a SCSI host adapter. These are credit card
  2.2239 -  size devices often used with laptops.
  2.2240 -
  2.2241 -  Note that the answer to this question won't directly affect the
  2.2242 -  kernel: saying N will just cause the configurator to skip all
  2.2243 -  the questions PCMCIA SCSI host adapters.
  2.2244 -
  2.2245 -Adaptec APA1480 CardBus support
  2.2246 -CONFIG_PCMCIA_APA1480
  2.2247 -  Say Y here if you intend to attach this type of CardBus SCSI host
  2.2248 -  adapter to your computer.
  2.2249 -
  2.2250 -  This driver is also available as a module called apa1480_cb.o ( =
  2.2251 -  code which can be inserted in and removed from the running kernel
  2.2252 -  whenever you want). If you want to compile it as a module, say M
  2.2253 -  here and read <file:Documentation/modules.txt>.
  2.2254 -
  2.2255 -NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
  2.2256 -CONFIG_PCMCIA_NINJA_SCSI
  2.2257 -  If you intend to attach this type of PCMCIA SCSI host adapter to
  2.2258 -  your computer, say Y here and read
  2.2259 -  <file:Documentation/README.nsp_cs.eng>.
  2.2260 -
  2.2261 -  This driver is also available as a module called nsp_cs.o ( =
  2.2262 -  code which can be inserted in and removed from the running kernel
  2.2263 -  whenever you want). If you want to compile it as a module, say M
  2.2264 -  here and read <file:Documentation/modules.txt>.
  2.2265 -
  2.2266 -Adaptec AHA152X PCMCIA support
  2.2267 -CONFIG_PCMCIA_AHA152X
  2.2268 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  2.2269 -  adapter to your computer.
  2.2270 -
  2.2271 -  This driver is also available as a module called aha152x_cs.o ( =
  2.2272 -  code which can be inserted in and removed from the running kernel
  2.2273 -  whenever you want). If you want to compile it as a module, say M
  2.2274 -  here and read <file:Documentation/modules.txt>.
  2.2275 -
  2.2276 -Qlogic PCMCIA support
  2.2277 -CONFIG_PCMCIA_QLOGIC
  2.2278 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  2.2279 -  adapter to your computer.
  2.2280 -
  2.2281 -  This driver is also available as a module called qlogic_cs.o ( =
  2.2282 -  code which can be inserted in and removed from the running kernel
  2.2283 -  whenever you want).  If you want to compile it as a module, say M
  2.2284 -  here and read <file:Documentation/modules.txt>.
  2.2285 -
  2.2286 -Future Domain PCMCIA support
  2.2287 -CONFIG_PCMCIA_FDOMAIN
  2.2288 -  Say Y here if you intend to attach this type of PCMCIA SCSI host
  2.2289 -  adapter to your computer.
  2.2290 -
  2.2291 -  This driver is also available as a module called fdomain_cs.o ( =
  2.2292 -  code which can be inserted in and removed from the running kernel
  2.2293 -  whenever you want).  If you want to compile it as a module, say M
  2.2294 -  here and read <file:Documentation/modules.txt>.
  2.2295 -
  2.2296 -# Choice: mipstype
  2.2297 -CPU type
  2.2298 -CONFIG_CPU_R3000
  2.2299 -  Please make sure to pick the right CPU type. Linux/MIPS is not
  2.2300 -  designed to be generic, i.e. Kernels compiled for R3000 CPUs will
  2.2301 -  *not* work on R4000 machines and vice versa.  However, since most
  2.2302 -  of the supported machines have an R4000 (or similar) CPU, R4x00
  2.2303 -  might be a safe bet.  If the resulting kernel does not work,
  2.2304 -  try to recompile with R3000.
  2.2305 -
  2.2306 -  R3000    MIPS Technologies R3000-series processors,
  2.2307 -           including the 3041, 3051, and 3081.
  2.2308 -
  2.2309 -  R6000    MIPS Technologies R6000-series processors,
  2.2310 -           including the 64474, 64475, 64574 and 64575.
  2.2311 -
  2.2312 -  R4300    MIPS Technologies R4300-series processors.
  2.2313 -
  2.2314 -  R4x00    MIPS Technologies R4000-series processors other than 4300,
  2.2315 -           including the 4640, 4650, and 4700.
  2.2316 -
  2.2317 -  R5000    MIPS Technologies R5000-series processors other than the
  2.2318 -           Nevada.
  2.2319 -
  2.2320 -  R52xx    MIPS Technologies R52xx-series ("Nevada") processors.
  2.2321 -
  2.2322 -  R10000   MIPS Technologies R10000-series processors.
  2.2323 -
  2.2324 -R6000
  2.2325 -CONFIG_CPU_R6000
  2.2326 -  MIPS Technologies R6000-series processors, including the 64474,
  2.2327 -  64475, 64574 and 64575.
  2.2328 -
  2.2329 -R4300
  2.2330 -CONFIG_CPU_R4300
  2.2331 -  MIPS Technologies R4300-series processors.
  2.2332 -
  2.2333 -R4x00
  2.2334 -CONFIG_CPU_R4X00
  2.2335 -  MIPS Technologies R4000-series processors other than 4300, including
  2.2336 -  the 4640, 4650, and 4700.
  2.2337 -
  2.2338 -R5000
  2.2339 -CONFIG_CPU_R5000
  2.2340 -  MIPS Technologies R5000-series processors other than the Nevada.
  2.2341 -
  2.2342 -R52x0
  2.2343 -CONFIG_CPU_NEVADA
  2.2344 -  MIPS Technologies R52x0-series ("Nevada") processors.
  2.2345 -
  2.2346 -R8000
  2.2347 -CONFIG_CPU_R8000
  2.2348 -  MIPS Technologies R8000-series processors.
  2.2349 -
  2.2350 -R10000
  2.2351 -CONFIG_CPU_R10000
  2.2352 -  MIPS Technologies R10000-series processors.
  2.2353 -
  2.2354 -Discontiguous Memory Support
  2.2355 -CONFIG_DISCONTIGMEM
  2.2356 -  Say Y to support efficient handling of discontiguous physical memory,
  2.2357 -  for architectures which are either NUMA (Non-Uniform Memory Access)
  2.2358 -  or have huge holes in the physical address space for other reasons.
  2.2359 -  See <file:Documentation/vm/numa> for more.
  2.2360 -
  2.2361 -Mapped kernel support
  2.2362 -CONFIG_MAPPED_KERNEL
  2.2363 -  Change the way a Linux kernel is loaded unto memory on a MIPS64
  2.2364 -  machine.  This is required in order to support text replication and
  2.2365 -  NUMA.  If you need to understand it, read the source code.
  2.2366 -
  2.2367 -Kernel text replication support
  2.2368 -CONFIG_REPLICATE_KTEXT
  2.2369 -  Say Y here to enable replicating the kernel text across multiple
  2.2370 -  nodes in a NUMA cluster.  This trades memory for speed.
  2.2371 -
  2.2372 -Exception handler replication support
  2.2373 -CONFIG_REPLICATE_EXHANDLERS
  2.2374 -  Say Y here to enable replicating the kernel exception handlers
  2.2375 -  across multiple nodes in a NUMA cluster. This trades memory for
  2.2376 -  speed.
  2.2377 -
  2.2378 -NUMA support?
  2.2379 -CONFIG_NUMA
  2.2380 -  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
  2.2381 -  Access).  This option is for configuring high-end multiprocessor
  2.2382 -  server machines.  If in doubt, say N.
  2.2383 -
  2.2384 -R41xx
  2.2385 -CONFIG_CPU_VR41XX
  2.2386 -  The options selects support for the NEC VR41xx series of processors.
  2.2387 -  Only choose this option if you have one of these processors as a
  2.2388 -  kernel built with this option will not run on any other type of
  2.2389 -  processor or vice versa.
  2.2390 -
  2.2391 -CPU feature configuration
  2.2392 -CONFIG_CPU_ADVANCED
  2.2393 -  Saying yes here allows you to select support for various features
  2.2394 -  your CPU may or may not have.  Most people should say N here.
  2.2395 -
  2.2396 -ll and sc instructions available
  2.2397 -CONFIG_CPU_HAS_LLSC
  2.2398 -  MIPS R4000 series and later provide the Load Linked (ll)
  2.2399 -  and Store Conditional (sc) instructions. More information is
  2.2400 -  available at <http://www.go-ecs.com/mips/miptek1.htm>.
  2.2401 -
  2.2402 -  Say Y here if your CPU has the ll and sc instructions.  Say Y here
  2.2403 -  for better performance, N if you don't know.  You must say Y here
  2.2404 -  for multiprocessor machines.
  2.2405 -
  2.2406 -lld and scd instructions available
  2.2407 -CONFIG_CPU_HAS_LLDSCD
  2.2408 -  Say Y here if your CPU has the lld and scd instructions, the 64-bit
  2.2409 -  equivalents of ll and sc.  Say Y here for better performance, N if
  2.2410 -  you don't know.  You must say Y here for multiprocessor machines.
  2.2411 -
  2.2412 -Writeback Buffer available
  2.2413 -CONFIG_CPU_HAS_WB
  2.2414 -  Say N here for slightly better performance.  You must say Y here for
  2.2415 -  machines which require flushing of write buffers in software.  Saying
  2.2416 -  Y is the safe option; N may result in kernel malfunction and crashes.
  2.2417 -
  2.2418 -Support for large 64-bit configurations
  2.2419 -CONFIG_MIPS_INSANE_LARGE
  2.2420 -  MIPS R10000 does support a 44 bit / 16TB address space as opposed to
  2.2421 -  previous 64-bit processors which only supported 40 bit / 1TB. If you
  2.2422 -  need processes of more than 1TB virtual address space, say Y here.
  2.2423 -  This will result in additional memory usage, so it is not
  2.2424 -  recommended for normal users.
  2.2425 -
  2.2426 -Generate little endian code
  2.2427 -CONFIG_CPU_LITTLE_ENDIAN
  2.2428 -  Some MIPS machines can be configured for either little or big endian
  2.2429 -  byte order. These modes require different kernels. Say Y if your
  2.2430 -  machine is little endian, N if it's a big endian machine.
  2.2431 -
  2.2432 -Use power LED as a heartbeat
  2.2433 -CONFIG_HEARTBEAT
  2.2434 -  Use the power-on LED on your machine as a load meter.  The exact
  2.2435 -  behaviour is platform-dependent, but normally the flash frequency is
  2.2436 -  a hyperbolic function of the 5-minute load average.
  2.2437 -
  2.2438 -Networking support
  2.2439 -CONFIG_NET
  2.2440 -  Unless you really know what you are doing, you should say Y here.
  2.2441 -  The reason is that some programs need kernel networking support even
  2.2442 -  when running on a stand-alone machine that isn't connected to any
  2.2443 -  other computer. If you are upgrading from an older kernel, you
  2.2444 -  should consider updating your networking tools too because changes
  2.2445 -  in the kernel and the tools often go hand in hand. The tools are
  2.2446 -  contained in the package net-tools, the location and version number
  2.2447 -  of which are given in <file:Documentation/Changes>.
  2.2448 -
  2.2449 -  For a general introduction to Linux networking, it is highly
  2.2450 -  recommended to read the NET-HOWTO, available from
  2.2451 -  <http://www.tldp.org/docs.html#howto>.
  2.2452 -
  2.2453 -Socket filtering
  2.2454 -CONFIG_FILTER
  2.2455 -  The Linux Socket Filter is derived from the Berkeley Packet Filter.
  2.2456 -  If you say Y here, user-space programs can attach a filter to any
  2.2457 -  socket and thereby tell the kernel that it should allow or disallow
  2.2458 -  certain types of data to get through the socket.  Linux Socket
  2.2459 -  Filtering works on all socket types except TCP for now.  See the
  2.2460 -  text file <file:Documentation/networking/filter.txt> for more
  2.2461 -  information.
  2.2462 -
  2.2463 -  You need to say Y here if you want to use PPP packet filtering
  2.2464 -  (see the CONFIG_PPP_FILTER option below).
  2.2465 -
  2.2466 -  If unsure, say N.
  2.2467 -
  2.2468 -Network packet filtering (replaces ipchains)
  2.2469 -CONFIG_NETFILTER
  2.2470 -  Netfilter is a framework for filtering and mangling network packets
  2.2471 -  that pass through your Linux box.
  2.2472 -
  2.2473 -  The most common use of packet filtering is to run your Linux box as
  2.2474 -  a firewall protecting a local network from the Internet. The type of
  2.2475 -  firewall provided by this kernel support is called a "packet
  2.2476 -  filter", which means that it can reject individual network packets
  2.2477 -  based on type, source, destination etc. The other kind of firewall,
  2.2478 -  a "proxy-based" one, is more secure but more intrusive and more
  2.2479 -  bothersome to set up; it inspects the network traffic much more
  2.2480 -  closely, modifies it and has knowledge about the higher level
  2.2481 -  protocols, which a packet filter lacks. Moreover, proxy-based
  2.2482 -  firewalls often require changes to the programs running on the local
  2.2483 -  clients. Proxy-based firewalls don't need support by the kernel, but
  2.2484 -  they are often combined with a packet filter, which only works if
  2.2485 -  you say Y here.
  2.2486 -
  2.2487 -  You should also say Y here if you intend to use your Linux box as
  2.2488 -  the gateway to the Internet for a local network of machines without
  2.2489 -  globally valid IP addresses. This is called "masquerading": if one
  2.2490 -  of the computers on your local network wants to send something to
  2.2491 -  the outside, your box can "masquerade" as that computer, i.e. it
  2.2492 -  forwards the traffic to the intended outside destination, but
  2.2493 -  modifies the packets to make it look like they came from the
  2.2494 -  firewall box itself. It works both ways: if the outside host
  2.2495 -  replies, the Linux box will silently forward the traffic to the
  2.2496 -  correct local computer. This way, the computers on your local net
  2.2497 -  are completely invisible to the outside world, even though they can
  2.2498 -  reach the outside and can receive replies. It is even possible to
  2.2499 -  run globally visible servers from within a masqueraded local network
  2.2500 -  using a mechanism called portforwarding. Masquerading is also often
  2.2501 -  called NAT (Network Address Translation).
  2.2502 -
  2.2503 -  Another use of Netfilter is in transparent proxying: if a machine on
  2.2504 -  the local network tries to connect to an outside host, your Linux
  2.2505 -  box can transparently forward the traffic to a local server,
  2.2506 -  typically a caching proxy server.
  2.2507 -
  2.2508 -  Various modules exist for netfilter which replace the previous
  2.2509 -  masquerading (ipmasqadm), packet filtering (ipchains), transparent
  2.2510 -  proxying, and portforwarding mechanisms. Please see
  2.2511 -  <file:Documentation/Changes> under "iptables" for the location of
  2.2512 -  these packages.
  2.2513 -
  2.2514 -  Make sure to say N to "Fast switching" below if you intend to say Y
  2.2515 -  here, as Fast switching currently bypasses netfilter.
  2.2516 -
  2.2517 -  Chances are that you should say Y here if you compile a kernel which
  2.2518 -  will run as a router and N for regular hosts. If unsure, say N.
  2.2519 -
  2.2520 -Network packet filtering debugging
  2.2521 -CONFIG_NETFILTER_DEBUG
  2.2522 -  You can say Y here if you want to get additional messages useful in
  2.2523 -  debugging the netfilter code.
  2.2524 -
  2.2525 -Connection tracking (required for masq/NAT)
  2.2526 -CONFIG_IP_NF_CONNTRACK
  2.2527 -  Connection tracking keeps a record of what packets have passed
  2.2528 -  through your machine, in order to figure out how they are related
  2.2529 -  into connections.
  2.2530 -
  2.2531 -  This is required to do Masquerading or other kinds of Network
  2.2532 -  Address Translation (except for Fast NAT).  It can also be used to
  2.2533 -  enhance packet filtering (see `Connection state match support'
  2.2534 -  below).
  2.2535 -
  2.2536 -  If you want to compile it as a module, say M here and read
  2.2537 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2538 -
  2.2539 -Amanda protocol support
  2.2540 -CONFIG_IP_NF_AMANDA
  2.2541 -  If you are running the Amanda backup package (http://www.amanda.org/)
  2.2542 -  on this machine or machines that will be MASQUERADED through this
  2.2543 -  machine, then you may want to enable this feature.  This allows the
  2.2544 -  connection tracking and natting code to allow the sub-channels that
  2.2545 -  Amanda requires for communication of the backup data, messages and
  2.2546 -  index.
  2.2547 -
  2.2548 -  If you want to compile it as a module, say M here and read
  2.2549 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2550 -
  2.2551 -
  2.2552 -IRC Send/Chat protocol support
  2.2553 -CONFIG_IP_NF_IRC
  2.2554 -  There is a commonly-used extension to IRC called
  2.2555 -  Direct Client-to-Client Protocol (DCC).  This enables users to send
  2.2556 -  files to each other, and also chat to each other without the need
  2.2557 -  of a server.  DCC Sending is used anywhere you send files over IRC,
  2.2558 -  and DCC Chat is most commonly used by Eggdrop bots.  If you are
  2.2559 -  using NAT, this extension will enable you to send files and initiate
  2.2560 -  chats.  Note that you do NOT need this extension to get files or
  2.2561 -  have others initiate chats, or everything else in IRC.
  2.2562 -
  2.2563 -  If you want to compile it as a module, say 'M' here and read
  2.2564 -  Documentation/modules.txt.  If unsure, say 'N'.
  2.2565 -
  2.2566 -TFTP protocol support
  2.2567 -CONFIG_IP_NF_TFTP
  2.2568 -  TFTP connection tracking helper, this is required depending
  2.2569 -  on how restrictive your ruleset is.
  2.2570 -  If you are using a tftp client behind -j SNAT or -j MASQUERADING
  2.2571 -  you will need this.
  2.2572 -
  2.2573 -  If you want to compile it as a module, say M here and read
  2.2574 -  Documentation/modules.txt.  If unsure, say `Y'.
  2.2575 -
  2.2576 -FTP protocol support
  2.2577 -CONFIG_IP_NF_FTP
  2.2578 -  Tracking FTP connections is problematic: special helpers are
  2.2579 -  required for tracking them, and doing masquerading and other forms
  2.2580 -  of Network Address Translation on them.
  2.2581 -
  2.2582 -  If you want to compile it as a module, say M here and read
  2.2583 -  <file:Documentation/modules.txt>.  If unsure, say `Y'.
  2.2584 -
  2.2585 -User space queueing via NETLINK
  2.2586 -CONFIG_IP_NF_QUEUE
  2.2587 -  Netfilter has the ability to queue packets to user space: the
  2.2588 -  netlink device can be used to access them using this driver.
  2.2589 -
  2.2590 -  If you want to compile it as a module, say M here and read
  2.2591 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2592 -
  2.2593 -IP tables support (required for filtering/masq/NAT)
  2.2594 -CONFIG_IP_NF_IPTABLES
  2.2595 -  iptables is a general, extensible packet identification framework.
  2.2596 -  The packet filtering and full NAT (masquerading, port forwarding,
  2.2597 -  etc) subsystems now use this: say `Y' or `M' here if you want to use
  2.2598 -  either of those.
  2.2599 -
  2.2600 -  If you want to compile it as a module, say M here and read
  2.2601 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2602 -
  2.2603 -limit match support
  2.2604 -CONFIG_IP_NF_MATCH_LIMIT
  2.2605 -  limit matching allows you to control the rate at which a rule can be
  2.2606 -  matched: mainly useful in combination with the LOG target ("LOG
  2.2607 -  target support", below) and to avoid some Denial of Service attacks.
  2.2608 -
  2.2609 -  If you want to compile it as a module, say M here and read
  2.2610 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2611 -
  2.2612 -skb->pkt_type packet match support
  2.2613 -CONFIG_IP_NF_MATCH_PKTTYPE
  2.2614 -  This patch allows you to match packet in accrodance
  2.2615 -  to its "class", eg. BROADCAST, MULTICAST, ...
  2.2616 -  
  2.2617 -  Typical usage:
  2.2618 -  iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  2.2619 -  
  2.2620 -  If you want to compile it as a module, say M here and read
  2.2621 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2622 -
  2.2623 -MAC address match support
  2.2624 -CONFIG_IP_NF_MATCH_MAC
  2.2625 -  MAC matching allows you to match packets based on the source
  2.2626 -  Ethernet address of the packet.
  2.2627 -
  2.2628 -  If you want to compile it as a module, say M here and read
  2.2629 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2630 -
  2.2631 -Netfilter MARK match support
  2.2632 -CONFIG_IP_NF_MATCH_MARK
  2.2633 -  Netfilter mark matching allows you to match packets based on the
  2.2634 -  `nfmark' value in the packet.  This can be set by the MARK target
  2.2635 -  (see below).
  2.2636 -
  2.2637 -  If you want to compile it as a module, say M here and read
  2.2638 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2639 -
  2.2640 -Multiple port match support
  2.2641 -CONFIG_IP_NF_MATCH_MULTIPORT
  2.2642 -  Multiport matching allows you to match TCP or UDP packets based on
  2.2643 -  a series of source or destination ports: normally a rule can only
  2.2644 -  match a single range of ports.
  2.2645 -
  2.2646 -  If you want to compile it as a module, say M here and read
  2.2647 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2648 -
  2.2649 -TTL match support
  2.2650 -CONFIG_IP_NF_MATCH_TTL
  2.2651 -  This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
  2.2652 -  to match packets by their TTL value.
  2.2653 -
  2.2654 -  If you want to compile it as a module, say M here and read
  2.2655 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2656 -
  2.2657 -LENGTH match support
  2.2658 -CONFIG_IP_NF_MATCH_LENGTH
  2.2659 -  This option allows you to match the length of a packet against a
  2.2660 -  specific value or range of values.
  2.2661 -
  2.2662 -  If you want to compile it as a module, say M here and read
  2.2663 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2664 -
  2.2665 -AH/ESP match support
  2.2666 -CONFIG_IP_NF_MATCH_AH_ESP
  2.2667 -  These two match extensions (`ah' and `esp') allow you to match a
  2.2668 -  range of SPIs inside AH or ESP headers of IPSec packets.
  2.2669 -
  2.2670 -  If you want to compile it as a module, say M here and read
  2.2671 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2672 -
  2.2673 -DSCP match support
  2.2674 -CONFIG_IP_NF_MATCH_DSCP
  2.2675 -  This option adds a `DSCP' match, which allows you to match against
  2.2676 -  the IPv4 header DSCP field (DSCP codepoint).
  2.2677 -
  2.2678 -  The DSCP codepoint can have any value between 0x0 and 0x4f.
  2.2679 -
  2.2680 -  If you want to compile it as a module, say M here and read
  2.2681 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2682 -
  2.2683 - 
  2.2684 -
  2.2685 -ECN match support
  2.2686 -CONFIG_IP_NF_MATCH_ECN
  2.2687 -  This option adds a `ECN' match, which allows you to match against
  2.2688 -  the IPv4 and TCP header ECN fields.
  2.2689 -
  2.2690 -  If you want to compile it as a module, say M here and read
  2.2691 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2692 -
  2.2693 - 
  2.2694 -
  2.2695 -TOS match support
  2.2696 -CONFIG_IP_NF_MATCH_TOS
  2.2697 -  TOS matching allows you to match packets based on the Type Of
  2.2698 -  Service fields of the IP packet.
  2.2699 -
  2.2700 -  If you want to compile it as a module, say M here and read
  2.2701 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2702 -
  2.2703 -conntrack match support
  2.2704 -CONFIG_IP_NF_MATCH_CONNTRACK
  2.2705 -  This is a general conntrack match module, a superset of the state match.
  2.2706 -
  2.2707 -  It allows matching on additional conntrack information, which is
  2.2708 -  useful in complex configurations, such as NAT gateways with multiple
  2.2709 -  internet links or tunnels.
  2.2710 -
  2.2711 -  If you want to compile it as a module, say M here and read
  2.2712 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2713 -
  2.2714 -
  2.2715 -Connection state match support
  2.2716 -CONFIG_IP_NF_MATCH_STATE
  2.2717 -  Connection state matching allows you to match packets based on their
  2.2718 -  relationship to a tracked connection (ie. previous packets).  This
  2.2719 -  is a powerful tool for packet classification.
  2.2720 -
  2.2721 -  If you want to compile it as a module, say M here and read
  2.2722 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2723 -
  2.2724 -Unclean match support
  2.2725 -CONFIG_IP_NF_MATCH_UNCLEAN
  2.2726 -  Unclean packet matching matches any strange or invalid packets, by
  2.2727 -  looking at a series of fields in the IP, TCP, UDP and ICMP headers.
  2.2728 -
  2.2729 -  If you want to compile it as a module, say M here and read
  2.2730 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2731 -
  2.2732 -Owner match support
  2.2733 -CONFIG_IP_NF_MATCH_OWNER
  2.2734 -  Packet owner matching allows you to match locally-generated packets
  2.2735 -  based on who created them: the user, group, process or session.
  2.2736 -
  2.2737 -  If you want to compile it as a module, say M here and read
  2.2738 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2739 -
  2.2740 -Packet filtering
  2.2741 -CONFIG_IP_NF_FILTER
  2.2742 -  Packet filtering defines a table `filter', which has a series of
  2.2743 -  rules for simple packet filtering at local input, forwarding and
  2.2744 -  local output.  See the man page for iptables(8).
  2.2745 -
  2.2746 -  If you want to compile it as a module, say M here and read
  2.2747 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2748 -
  2.2749 -REJECT target support
  2.2750 -CONFIG_IP_NF_TARGET_REJECT
  2.2751 -  The REJECT target allows a filtering rule to specify that an ICMP
  2.2752 -  error should be issued in response to an incoming packet, rather
  2.2753 -  than silently being dropped.
  2.2754 -
  2.2755 -  If you want to compile it as a module, say M here and read
  2.2756 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2757 -
  2.2758 -MIRROR target support
  2.2759 -CONFIG_IP_NF_TARGET_MIRROR
  2.2760 -  The MIRROR target allows a filtering rule to specify that an
  2.2761 -  incoming packet should be bounced back to the sender.
  2.2762 -
  2.2763 -  If you want to compile it as a module, say M here and read
  2.2764 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2765 -
  2.2766 -Local NAT support
  2.2767 -CONFIG_IP_NF_NAT_LOCAL
  2.2768 -  This option enables support for NAT of locally originated connections. 
  2.2769 -  Enable this if you need to use destination NAT on connections
  2.2770 -  originating from local processes on the nat box itself.
  2.2771 -
  2.2772 -  Please note that you will need a recent version (>= 1.2.6a)
  2.2773 -  of the iptables userspace program in order to use this feature.
  2.2774 -  See <http://www.iptables.org/> for download instructions.
  2.2775 -
  2.2776 -  If unsure, say 'N'.
  2.2777 -
  2.2778 -
  2.2779 -Full NAT (Network Address Translation)
  2.2780 -CONFIG_IP_NF_NAT
  2.2781 -  The Full NAT option allows masquerading, port forwarding and other
  2.2782 -  forms of full Network Address Port Translation.  It is controlled by
  2.2783 -  the `nat' table in iptables: see the man page for iptables(8).
  2.2784 -
  2.2785 -  If you want to compile it as a module, say M here and read
  2.2786 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2787 -
  2.2788 -MASQUERADE target support
  2.2789 -CONFIG_IP_NF_TARGET_MASQUERADE
  2.2790 -  Masquerading is a special case of NAT: all outgoing connections are
  2.2791 -  changed to seem to come from a particular interface's address, and
  2.2792 -  if the interface goes down, those connections are lost.  This is
  2.2793 -  only useful for dialup accounts with dynamic IP address (ie. your IP
  2.2794 -  address will be different on next dialup).
  2.2795 -
  2.2796 -  If you want to compile it as a module, say M here and read
  2.2797 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2798 -
  2.2799 -Basic SNMP-ALG support
  2.2800 -CONFIG_IP_NF_NAT_SNMP_BASIC
  2.2801 -
  2.2802 -  This module implements an Application Layer Gateway (ALG) for
  2.2803 -  SNMP payloads.  In conjunction with NAT, it allows a network
  2.2804 -  management system to access multiple private networks with
  2.2805 -  conflicting addresses.  It works by modifying IP addresses
  2.2806 -  inside SNMP payloads to match IP-layer NAT mapping.
  2.2807 -
  2.2808 -  This is the "basic" form of SNMP-ALG, as described in RFC 2962
  2.2809 -
  2.2810 -  If you want to compile it as a module, say M here and read
  2.2811 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2812 -
  2.2813 -REDIRECT target support
  2.2814 -CONFIG_IP_NF_TARGET_REDIRECT
  2.2815 -  REDIRECT is a special case of NAT: all incoming connections are
  2.2816 -  mapped onto the incoming interface's address, causing the packets to
  2.2817 -  come to the local machine instead of passing through.  This is
  2.2818 -  useful for transparent proxies.
  2.2819 -
  2.2820 -  If you want to compile it as a module, say M here and read
  2.2821 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2822 -
  2.2823 -Packet mangling
  2.2824 -CONFIG_IP_NF_MANGLE
  2.2825 -  This option adds a `mangle' table to iptables: see the man page for
  2.2826 -  iptables(8).  This table is used for various packet alterations
  2.2827 -  which can effect how the packet is routed.
  2.2828 -
  2.2829 -  If you want to compile it as a module, say M here and read
  2.2830 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2831 -
  2.2832 -DSCP target support
  2.2833 -CONFIG_IP_NF_TARGET_DSCP
  2.2834 -  This option adds a `DSCP' target, which allows you to create rules in
  2.2835 -  the iptables mangle table. The selected packet has the DSCP field set
  2.2836 -  to the hex value provided on the command line; unlike the TOS target
  2.2837 -  which will only set the legal values within ip.h.
  2.2838 -
  2.2839 -  The DSCP field can be set to any value between 0x0 and 0x4f. It does
  2.2840 -  take into account that bits 6 and 7 are used by ECN.
  2.2841 -
  2.2842 -  If you want to compile it as a module, say M here and read
  2.2843 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2844 -
  2.2845 - 
  2.2846 -
  2.2847 -ECN target support
  2.2848 -CONFIG_IP_NF_TARGET_ECN
  2.2849 -  This option adds a `ECN' target, which can be used in the iptables mangle
  2.2850 -  table.  
  2.2851 -
  2.2852 -  You can use this target to remove the ECN bits from the IPv4 header of
  2.2853 -  an IP packet.  This is particularly useful, if you need to work around
  2.2854 -  existing ECN blackholes on the internet, but don't want to disable
  2.2855 -  ECN support in general.
  2.2856 -
  2.2857 -  If you want to compile it as a module, say M here and read
  2.2858 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2859 -
  2.2860 - 
  2.2861 -
  2.2862 -TOS target support
  2.2863 -CONFIG_IP_NF_TARGET_TOS
  2.2864 -  This option adds a `TOS' target, which allows you to create rules in
  2.2865 -  the `mangle' table which alter the Type Of Service field of an IP
  2.2866 -  packet prior to routing.
  2.2867 -
  2.2868 -  If you want to compile it as a module, say M here and read
  2.2869 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2870 -
  2.2871 -MARK target support
  2.2872 -CONFIG_IP_NF_TARGET_MARK
  2.2873 -  This option adds a `MARK' target, which allows you to create rules
  2.2874 -  in the `mangle' table which alter the netfilter mark (nfmark) field
  2.2875 -  associated with the packet prior to routing. This can change
  2.2876 -  the routing method (see `Use netfilter MARK value as routing
  2.2877 -  key') and can also be used by other subsystems to change their
  2.2878 -  behaviour.
  2.2879 -
  2.2880 -  If you want to compile it as a module, say M here and read
  2.2881 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2882 -
  2.2883 -TCPMSS target support
  2.2884 -CONFIG_IP_NF_TARGET_TCPMSS
  2.2885 -  This option adds a `TCPMSS' target, which allows you to alter the
  2.2886 -  MSS value of TCP SYN packets, to control the maximum size for that
  2.2887 -  connection (usually limiting it to your outgoing interface's MTU
  2.2888 -  minus 40).
  2.2889 -
  2.2890 -  This is used to overcome criminally braindead ISPs or servers which
  2.2891 -  block ICMP Fragmentation Needed packets.  The symptoms of this
  2.2892 -  problem are that everything works fine from your Linux
  2.2893 -  firewall/router, but machines behind it can never exchange large
  2.2894 -  packets:
  2.2895 -	1) Web browsers connect, then hang with no data received.
  2.2896 -	2) Small mail works fine, but large emails hang.
  2.2897 -	3) ssh works fine, but scp hangs after initial handshaking.
  2.2898 -
  2.2899 -  Workaround: activate this option and add a rule to your firewall
  2.2900 -  configuration like:
  2.2901 -
  2.2902 -        iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  2.2903 -		 -j TCPMSS --clamp-mss-to-pmtu
  2.2904 -
  2.2905 -  If you want to compile it as a module, say M here and read
  2.2906 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2907 -
  2.2908 -Helper match support
  2.2909 -CONFIG_IP_NF_MATCH_HELPER
  2.2910 -  Helper matching allows you to match packets in dynamic connections
  2.2911 -  tracked by a conntrack-helper, ie. ip_conntrack_ftp
  2.2912 -
  2.2913 -  If you want to compile it as a module, say M here and read
  2.2914 -  Documentation/modules.txt.  If unsure, say `Y'.
  2.2915 -
  2.2916 -TCPMSS match support
  2.2917 -CONFIG_IP_NF_MATCH_TCPMSS
  2.2918 -  This option adds a `tcpmss' match, which allows you to examine the
  2.2919 -  MSS value of TCP SYN packets, which control the maximum packet size
  2.2920 -  for that connection.
  2.2921 -
  2.2922 -  If you want to compile it as a module, say M here and read
  2.2923 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2924 -
  2.2925 -ULOG target support
  2.2926 -CONFIG_IP_NF_TARGET_ULOG
  2.2927 -  This option adds a `ULOG' target, which allows you to create rules in
  2.2928 -  any iptables table. The packet is passed to a userspace logging
  2.2929 -  daemon using netlink multicast sockets; unlike the LOG target
  2.2930 -  which can only be viewed through syslog.
  2.2931 -
  2.2932 -  The appropriate userspace logging daemon (ulogd) may be obtained from
  2.2933 -  <http://www.gnumonks.org/projects/ulogd>
  2.2934 -
  2.2935 -  If you want to compile it as a module, say M here and read
  2.2936 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2937 -
  2.2938 -LOG target support
  2.2939 -CONFIG_IP_NF_TARGET_LOG
  2.2940 -  This option adds a `LOG' target, which allows you to create rules in
  2.2941 -  any iptables table which records the packet header to the syslog.
  2.2942 -
  2.2943 -  If you want to compile it as a module, say M here and read
  2.2944 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2945 -
  2.2946 -ipchains (2.2-style) support
  2.2947 -CONFIG_IP_NF_COMPAT_IPCHAINS
  2.2948 -  This option places ipchains (with masquerading and redirection
  2.2949 -  support) back into the kernel, using the new netfilter
  2.2950 -  infrastructure.  It is not recommended for new installations (see
  2.2951 -  `Packet filtering').  With this enabled, you should be able to use
  2.2952 -  the ipchains tool exactly as in 2.2 kernels.
  2.2953 -
  2.2954 -  If you want to compile it as a module, say M here and read
  2.2955 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2956 -
  2.2957 -ipfwadm (2.0-style) support
  2.2958 -CONFIG_IP_NF_COMPAT_IPFWADM
  2.2959 -  This option places ipfwadm (with masquerading and redirection
  2.2960 -  support) back into the kernel, using the new netfilter
  2.2961 -  infrastructure.  It is not recommended for new installations (see
  2.2962 -  `Packet filtering').  With this enabled, you should be able to use
  2.2963 -  the ipfwadm tool exactly as in 2.0 kernels.
  2.2964 -
  2.2965 -  If you want to compile it as a module, say M here and read
  2.2966 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2967 -
  2.2968 -EUI64 address check (EXPERIMENTAL)
  2.2969 -CONFIG_IP6_NF_MATCH_EUI64
  2.2970 -  This module performs checking on the IPv6 source address
  2.2971 -  Compares the last 64 bits with the EUI64 (delivered
  2.2972 -  from the MAC address) address
  2.2973 -
  2.2974 -  If you want to compile it as a module, say M here and read
  2.2975 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2976 -
  2.2977 -MAC address match support
  2.2978 -CONFIG_IP6_NF_MATCH_MAC
  2.2979 -  mac matching allows you to match packets based on the source
  2.2980 -  Ethernet address of the packet.
  2.2981 -
  2.2982 -  If you want to compile it as a module, say M here and read
  2.2983 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.2984 -
  2.2985 -length match support
  2.2986 -CONFIG_IP6_NF_MATCH_LENGTH
  2.2987 -  This option allows you to match the length of a packet against a
  2.2988 -  specific value or range of values.
  2.2989 -
  2.2990 -  If you want to compile it as a module, say M here and read
  2.2991 -  Documentation/modules.txt.  If unsure, say `N'.
  2.2992 -
  2.2993 -Netfilter MARK match support
  2.2994 -CONFIG_IP6_NF_MATCH_MARK
  2.2995 -  Netfilter mark matching allows you to match packets based on the
  2.2996 -  `nfmark' value in the packet.  This can be set by the MARK target
  2.2997 -  (see below).
  2.2998 -
  2.2999 -  If you want to compile it as a module, say M here and read
  2.3000 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3001 -
  2.3002 -Multiple port match support
  2.3003 -CONFIG_IP6_NF_MATCH_MULTIPORT
  2.3004 -  Multiport matching allows you to match TCP or UDP packets based on
  2.3005 -  a series of source or destination ports: normally a rule can only
  2.3006 -  match a single range of ports.
  2.3007 -
  2.3008 -  If you want to compile it as a module, say M here and read
  2.3009 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3010 -
  2.3011 -IPV6 queue handler (EXPERIMENTAL)
  2.3012 -CONFIG_IP6_NF_QUEUE
  2.3013 -
  2.3014 -  This option adds a queue handler to the kernel for IPv6
  2.3015 -  packets which lets us to receive the filtered packets
  2.3016 -  with QUEUE target using libiptc as we can do with
  2.3017 -  the IPv4 now.
  2.3018 -
  2.3019 -  (C) Fernando Anton 2001
  2.3020 -  IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
  2.3021 -  Universidad Carlos III de Madrid
  2.3022 -  Universidad Politecnica de Alcala de Henares
  2.3023 -  email: fanton@it.uc3m.es
  2.3024 -
  2.3025 -  If you want to compile it as a module, say M here and read
  2.3026 -  Documentation/modules.txt. If unsure, say `N'.
  2.3027 -
  2.3028 -Owner match support
  2.3029 -CONFIG_IP6_NF_MATCH_OWNER
  2.3030 -  Packet owner matching allows you to match locally-generated packets
  2.3031 -  based on who created them: the user, group, process or session.
  2.3032 -
  2.3033 -  If you want to compile it as a module, say M here and read
  2.3034 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3035 -
  2.3036 -Packet filtering
  2.3037 -CONFIG_IP6_NF_FILTER
  2.3038 -  Packet filtering defines a table `filter', which has a series of
  2.3039 -  rules for simple packet filtering at local input, forwarding and
  2.3040 -  local output.  See the man page for iptables(8).
  2.3041 -
  2.3042 -  If you want to compile it as a module, say M here and read
  2.3043 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3044 -
  2.3045 -Packet mangling
  2.3046 -CONFIG_IP6_NF_MANGLE
  2.3047 -  This option adds a `mangle' table to iptables: see the man page for
  2.3048 -  iptables(8).  This table is used for various packet alterations
  2.3049 -  which can effect how the packet is routed.
  2.3050 -
  2.3051 -  If you want to compile it as a module, say M here and read
  2.3052 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3053 -
  2.3054 -MARK target support
  2.3055 -CONFIG_IP6_NF_TARGET_MARK
  2.3056 -  This option adds a `MARK' target, which allows you to create rules
  2.3057 -  in the `mangle' table which alter the netfilter mark (nfmark) field
  2.3058 -  associated with the packet packet prior to routing. This can change
  2.3059 -  the routing method (see `Use netfilter MARK value as routing
  2.3060 -  key') and can also be used by other subsystems to change their
  2.3061 -  behaviour.
  2.3062 -
  2.3063 -  If you want to compile it as a module, say M here and read
  2.3064 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3065 -
  2.3066 -TCP Explicit Congestion Notification support
  2.3067 -CONFIG_INET_ECN
  2.3068 -  Explicit Congestion Notification (ECN) allows routers to notify
  2.3069 -  clients about network congestion, resulting in fewer dropped packets
  2.3070 -  and increased network performance.  This option adds ECN support to
  2.3071 -  the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
  2.3072 -  which allows ECN support to be disabled at runtime.
  2.3073 -
  2.3074 -  Note that, on the Internet, there are many broken firewalls which
  2.3075 -  refuse connections from ECN-enabled machines, and it may be a while
  2.3076 -  before these firewalls are fixed.  Until then, to access a site
  2.3077 -  behind such a firewall (some of which are major sites, at the time
  2.3078 -  of this writing) you will have to disable this option, either by
  2.3079 -  saying N now or by using the sysctl.
  2.3080 -
  2.3081 -  If in doubt, say N.
  2.3082 -
  2.3083 -IPv6 tables support (required for filtering/masq/NAT)
  2.3084 -CONFIG_IP6_NF_IPTABLES
  2.3085 -  ip6tables is a general, extensible packet identification framework.
  2.3086 -  Currently only the packet filtering and packet mangling subsystem
  2.3087 -  for IPv6 use this, but connection tracking is going to follow.
  2.3088 -  Say 'Y' or 'M' here if you want to use either of those.
  2.3089 -
  2.3090 -  If you want to compile it as a module, say M here and read
  2.3091 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3092 -
  2.3093 -IPv6 limit match support
  2.3094 -CONFIG_IP6_NF_MATCH_LIMIT
  2.3095 -  limit matching allows you to control the rate at which a rule can be
  2.3096 -  matched: mainly useful in combination with the LOG target ("LOG
  2.3097 -  target support", below) and to avoid some Denial of Service attacks.
  2.3098 -
  2.3099 -  If you want to compile it as a module, say M here and read
  2.3100 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3101 -
  2.3102 -LOG target support
  2.3103 -CONFIG_IP6_NF_TARGET_LOG
  2.3104 -  This option adds a `LOG' target, which allows you to create rules in
  2.3105 -  any iptables table which records the packet header to the syslog.
  2.3106 -
  2.3107 -  If you want to compile it as a module, say M here and read
  2.3108 -  <file:Documentation/modules.txt>.  If unsure, say `N'.
  2.3109 -
  2.3110 -SYN flood protection
  2.3111 -CONFIG_SYN_COOKIES
  2.3112 -  Normal TCP/IP networking is open to an attack known as "SYN
  2.3113 -  flooding". This denial-of-service attack prevents legitimate remote
  2.3114 -  users from being able to connect to your computer during an ongoing
  2.3115 -  attack and requires very little work from the attacker, who can
  2.3116 -  operate from anywhere on the Internet.
  2.3117 -
  2.3118 -  SYN cookies provide protection against this type of attack. If you
  2.3119 -  say Y here, the TCP/IP stack will use a cryptographic challenge
  2.3120 -  protocol known as "SYN cookies" to enable legitimate users to
  2.3121 -  continue to connect, even when your machine is under attack. There
  2.3122 -  is no need for the legitimate users to change their TCP/IP software;
  2.3123 -  SYN cookies work transparently to them. For technical information
  2.3124 -  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
  2.3125 -
  2.3126 -  If you are SYN flooded, the source address reported by the kernel is
  2.3127 -  likely to have been forged by the attacker; it is only reported as
  2.3128 -  an aid in tracing the packets to their actual source and should not
  2.3129 -  be taken as absolute truth.
  2.3130 -
  2.3131 -  SYN cookies may prevent correct error reporting on clients when the
  2.3132 -  server is really overloaded. If this happens frequently better turn
  2.3133 -  them off.
  2.3134 -
  2.3135 -  If you say Y here, note that SYN cookies aren't enabled by default;
  2.3136 -  you can enable them by saying Y to "/proc file system support" and
  2.3137 -  "Sysctl support" below and executing the command
  2.3138 -
  2.3139 -    echo 1 >/proc/sys/net/ipv4/tcp_syncookies
  2.3140 -
  2.3141 -  at boot time after the /proc file system has been mounted.
  2.3142 -
  2.3143 -  If unsure, say N.
  2.3144 -
  2.3145 -# Choice: alphatype
  2.3146 -Alpha system type
  2.3147 -CONFIG_ALPHA_GENERIC
  2.3148 -  This is the system type of your hardware.  A "generic" kernel will
  2.3149 -  run on any supported Alpha system. However, if you configure a
  2.3150 -  kernel for your specific system, it will be faster and smaller.
  2.3151 -
  2.3152 -  To find out what type of Alpha system you have, you may want to
  2.3153 -  check out the Linux/Alpha FAQ, accessible on the WWW from
  2.3154 -  <http://www.alphalinux.org/>. In summary:
  2.3155 -
  2.3156 -  Alcor/Alpha-XLT     AS 600
  2.3157 -  Alpha-XL            XL-233, XL-266
  2.3158 -  AlphaBook1          Alpha laptop
  2.3159 -  Avanti              AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
  2.3160 -  Cabriolet           AlphaPC64, AlphaPCI64
  2.3161 -  DP264               DP264
  2.3162 -  EB164               EB164 21164 evaluation board
  2.3163 -  EB64+               EB64+ 21064 evaluation board
  2.3164 -  EB66                EB66 21066 evaluation board
  2.3165 -  EB66+               EB66+ 21066 evaluation board
  2.3166 -  Jensen              DECpc 150, DEC 2000 model 300,
  2.3167 -                      DEC 2000 model 500
  2.3168 -  LX164               AlphaPC164-LX
  2.3169 -  Miata               Personal Workstation 433a, 433au, 500a,
  2.3170 -                      500au, 600a, or 600au
  2.3171 -  Mikasa              AS 1000
  2.3172 -  Noname              AXPpci33, UDB (Multia)
  2.3173 -  Noritake            AS 1000A, AS 600A, AS 800
  2.3174 -  PC164               AlphaPC164
  2.3175 -  Rawhide             AS 1200, AS 4000, AS 4100
  2.3176 -  Ruffian             RPX164-2, AlphaPC164-UX, AlphaPC164-BX
  2.3177 -  SX164               AlphaPC164-SX
  2.3178 -  Sable               AS 2000, AS 2100
  2.3179 -  Shark		      DS 20L
  2.3180 -  Takara              Takara
  2.3181 -  Titan               Privateer
  2.3182 -  Wildfire            AlphaServer GS 40/80/160/320
  2.3183 -
  2.3184 -  If you don't know what to do, choose "generic".
  2.3185 -
  2.3186 -# Most of the information on these variants is from
  2.3187 -# <http://www.alphalinux.org/docs/alpha-howto.html>
  2.3188 -Alcor/Alpha-XLT
  2.3189 -CONFIG_ALPHA_ALCOR
  2.3190 -  For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
  2.3191 -  slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
  2.3192 -  Address, CIA) - a 383 pin plastic PGA).  It provides a DRAM
  2.3193 -  controller (256-bit memory bus) and a PCI interface.  It also does
  2.3194 -  all the work required to support an external Bcache and to maintain
  2.3195 -  memory coherence when a PCI device DMAs into (or out of) memory.
  2.3196 -
  2.3197 -Alpha-XL
  2.3198 -CONFIG_ALPHA_XL
  2.3199 -  XL-233 and XL-266-based Alpha systems.
  2.3200 -
  2.3201 -AlphaBook1
  2.3202 -CONFIG_ALPHA_BOOK1
  2.3203 -  Dec AlphaBook1/Burns Alpha-based laptops.
  2.3204 -
  2.3205 -Avanti
  2.3206 -CONFIG_ALPHA_AVANTI
  2.3207 -  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
  2.3208 -  Alphas. Info at
  2.3209 -  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
  2.3210 -
  2.3211 -Cabriolet
  2.3212 -CONFIG_ALPHA_CABRIOLET
  2.3213 -  Cabriolet AlphaPC64, AlphaPCI64 systems.  Derived from EB64+ but now
  2.3214 -  baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
  2.3215 -  slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
  2.3216 -  Bcache SIMMs.  Requires power supply with 3.3V output.
  2.3217 -
  2.3218 -DP264
  2.3219 -CONFIG_ALPHA_DP264
  2.3220 -  Various 21264 systems with the tsunami core logic chipset.
  2.3221 -  API Networks: 264DP, UP2000(+), CS20;
  2.3222 -  Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
  2.3223 -
  2.3224 -EB164
  2.3225 -CONFIG_ALPHA_EB164
  2.3226 -  EB164 21164 evaluation board from DEC.  Uses 21164 and ALCOR.  Has
  2.3227 -  ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
  2.3228 -  shared with an ISA slot) and 2 32-bit PCI slots.  Uses plus-in
  2.3229 -  Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
  2.3230 -  MOUSE (PS2 style), RTC/NVRAM.  Boot ROM is Flash.  PC-AT-sized
  2.3231 -  motherboard.  Requires power supply with 3.3V output.
  2.3232 -
  2.3233 -EB64+
  2.3234 -CONFIG_ALPHA_EB64P
  2.3235 -  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,
  2.3236 -  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
  2.3237 -  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
  2.3238 -  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
  2.3239 -  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.
  2.3240 -  Runs from standard PC power supply.
  2.3241 -
  2.3242 -EB66
  2.3243 -CONFIG_ALPHA_EB66
  2.3244 -  A Digital DS group board.  Uses 21066 or 21066A.  I/O sub-system is
  2.3245 -  identical to EB64+.  Baby PC-AT size.  Runs from standard PC power
  2.3246 -  supply.  The EB66 schematic was published as a marketing poster
  2.3247 -  advertising the 21066 as "the first microprocessor in the world with
  2.3248 -  embedded PCI".
  2.3249 -
  2.3250 -EB66+
  2.3251 -CONFIG_ALPHA_EB66P
  2.3252 -  Later variant of the EB66 board.
  2.3253 -
  2.3254 -Eiger
  2.3255 -CONFIG_ALPHA_EIGER
  2.3256 -  Apparently an obscure OEM single-board computer based on the
  2.3257 -  Typhoon/Tsunami chipset family. Information on it is scanty.
  2.3258 -
  2.3259 -Jensen
  2.3260 -CONFIG_ALPHA_JENSEN
  2.3261 -  DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
  2.3262 -  of the first-generation Alpha systems. A number of these systems
  2.3263 -  seem to be available on the second- hand market. The Jensen is a
  2.3264 -  floor-standing tower system which originally used a 150MHz 21064 It
  2.3265 -  used programmable logic to interface a 486 EISA I/O bridge to the
  2.3266 -  CPU.
  2.3267 -
  2.3268 -LX164
  2.3269 -CONFIG_ALPHA_LX164
  2.3270 -  A technical overview of this board is available at
  2.3271 -  <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
  2.3272 -
  2.3273 -Miata
  2.3274 -CONFIG_ALPHA_MIATA
  2.3275 -  The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
  2.3276 -  or 600au).  There is an Installation HOWTO for this hardware at
  2.3277 -  <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
  2.3278 -
  2.3279 -Mikasa
  2.3280 -CONFIG_ALPHA_MIKASA
  2.3281 -  AlphaServer 1000-based Alpha systems.
  2.3282 -
  2.3283 -Nautilus
  2.3284 -CONFIG_ALPHA_NAUTILUS
  2.3285 -  Alpha systems based on the AMD 751 & ALI 1543C chipsets.
  2.3286 -
  2.3287 -Noname
  2.3288 -CONFIG_ALPHA_NONAME
  2.3289 -  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
  2.3290 -  UDB).  This design was produced by Digital's Technical OEM (TOEM)
  2.3291 -  group. It uses the 21066 processor running at 166MHz or 233MHz. It
  2.3292 -  is a baby-AT size, and runs from a standard PC power supply. It has
  2.3293 -  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
  2.3294 -  2 versions, with either PS/2 or large DIN connectors for the
  2.3295 -  keyboard.
  2.3296 -
  2.3297 -Noritake
  2.3298 -CONFIG_ALPHA_NORITAKE
  2.3299 -  AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
  2.3300 -  systems.
  2.3301 -
  2.3302 -Rawhide
  2.3303 -CONFIG_ALPHA_RAWHIDE
  2.3304 -  AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
  2.3305 -  See HOWTO at
  2.3306 -  <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
  2.3307 -
  2.3308 -Ruffian
  2.3309 -CONFIG_ALPHA_RUFFIAN
  2.3310 -  Samsung APC164UX.  There is a page on known problems and workarounds
  2.3311 -  at <http://www.alphalinux.org/faq/FAQ-11.html>.
  2.3312 -
  2.3313 -Sable
  2.3314 -CONFIG_ALPHA_SABLE
  2.3315 -  Digital AlphaServer 2000 and 2100-based systems.
  2.3316 -
  2.3317 -Takara
  2.3318 -CONFIG_ALPHA_TAKARA
  2.3319 -  Alpha 11164-based OEM single-board computer.
  2.3320 -
  2.3321 -Wildfire
  2.3322 -CONFIG_ALPHA_WILDFIRE
  2.3323 -  AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
  2.3324 -
  2.3325 -EV5 CPU daughtercard (model 5/xxx)
  2.3326 -CONFIG_ALPHA_PRIMO
  2.3327 -  Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
  2.3328 -
  2.3329 -EV5 CPU(s) (model 5/xxx)
  2.3330 -CONFIG_ALPHA_GAMMA
  2.3331 -  Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
  2.3332 -
  2.3333 -EV67 (or later) CPU (speed > 600MHz)?
  2.3334 -CONFIG_ALPHA_EV67
  2.3335 -  Is this a machine based on the EV67 core?  If in doubt, select N here
  2.3336 -  and the machine will be treated as an EV6.
  2.3337 -
  2.3338 -Use SRM as bootloader
  2.3339 -CONFIG_ALPHA_SRM
  2.3340 -  There are two different types of booting firmware on Alphas: SRM,
  2.3341 -  which is command line driven, and ARC, which uses menus and arrow
  2.3342 -  keys. Details about the Linux/Alpha booting process are contained in
  2.3343 -  the Linux/Alpha FAQ, accessible on the WWW from
  2.3344 -  <http://www.alphalinux.org/>.
  2.3345 -
  2.3346 -  The usual way to load Linux on an Alpha machine is to use MILO
  2.3347 -  (a bootloader that lets you pass command line parameters to the
  2.3348 -  kernel just like lilo does for the x86 architecture) which can be
  2.3349 -  loaded either from ARC or can be installed directly as a permanent
  2.3350 -  firmware replacement from floppy (which requires changing a certain
  2.3351 -  jumper on the motherboard). If you want to do either of these, say N
  2.3352 -  here. If MILO doesn't work on your system (true for Jensen
  2.3353 -  motherboards), you can bypass it altogether and boot Linux directly
  2.3354 -  from an SRM console; say Y here in order to do that. Note that you
  2.3355 -  won't be able to boot from an IDE disk using SRM.
  2.3356 -
  2.3357 -  If unsure, say N.
  2.3358 -
  2.3359 -Legacy kernel start address
  2.3360 -CONFIG_ALPHA_LEGACY_START_ADDRESS
  2.3361 -  The 2.4 kernel changed the kernel start address from 0x310000
  2.3362 -  to 0x810000 to make room for the Wildfire's larger SRM console.
  2.3363 -
  2.3364 -  If you're using aboot 0.7 or later, the bootloader will examine the
  2.3365 -  ELF headers to determine where to transfer control. Unfortunately,
  2.3366 -  most older bootloaders -- APB or MILO -- hardcoded the kernel start
  2.3367 -  address rather than examining the ELF headers, and the result is a
  2.3368 -  hard lockup.
  2.3369 -
  2.3370 -  Say Y if you have a broken bootloader.  Say N if you do not, or if
  2.3371 -  you wish to run on Wildfire.
  2.3372 -
  2.3373 -Large VMALLOC support
  2.3374 -CONFIG_ALPHA_LARGE_VMALLOC
  2.3375 -  Process creation and other aspects of virtual memory management can
  2.3376 -  be streamlined if we restrict the kernel to one PGD for all vmalloc
  2.3377 -  allocations.  This equates to about 8GB.
  2.3378 -
  2.3379 -  Under normal circumstances, this is so far and above what is needed
  2.3380 -  as to be laughable.  However, there are certain applications (such
  2.3381 -  as benchmark-grade in-kernel web serving) that can make use of as
  2.3382 -  much vmalloc space as is available.
  2.3383 -
  2.3384 -  Say N unless you know you need gobs and gobs of vmalloc space.
  2.3385 -
  2.3386 -Non-standard serial port support
  2.3387 -CONFIG_SERIAL_NONSTANDARD
  2.3388 -  Say Y here if you have any non-standard serial boards -- boards
  2.3389 -  which aren't supported using the standard "dumb" serial driver.
  2.3390 -  This includes intelligent serial boards such as Cyclades,
  2.3391 -  Digiboards, etc. These are usually used for systems that need many
  2.3392 -  serial ports because they serve many terminals or dial-in
  2.3393 -  connections.
  2.3394 -
  2.3395 -  Note that the answer to this question won't directly affect the
  2.3396 -  kernel: saying N will just cause the configurator to skip all
  2.3397 -  the questions about non-standard serial boards.
  2.3398 -
  2.3399 -  Most people can say N here.
  2.3400 -
  2.3401 -Extended dumb serial driver options
  2.3402 -CONFIG_SERIAL_EXTENDED
  2.3403 -  If you wish to use any non-standard features of the standard "dumb"
  2.3404 -  driver, say Y here. This includes HUB6 support, shared serial
  2.3405 -  interrupts, special multiport support, support for more than the
  2.3406 -  four COM 1/2/3/4 boards, etc.
  2.3407 -
  2.3408 -  Note that the answer to this question won't directly affect the
  2.3409 -  kernel: saying N will just cause the configurator to skip all
  2.3410 -  the questions about serial driver options. If unsure, say N.
  2.3411 -
  2.3412 -Support more than 4 serial ports
  2.3413 -CONFIG_SERIAL_MANY_PORTS
  2.3414 -  Say Y here if you have dumb serial boards other than the four
  2.3415 -  standard COM 1/2/3/4 ports. This may happen if you have an AST
  2.3416 -  FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
  2.3417 -  from <http://www.tldp.org/docs.html#howto>), or other custom
  2.3418 -  serial port hardware which acts similar to standard serial port
  2.3419 -  hardware. If you only use the standard COM 1/2/3/4 ports, you can
  2.3420 -  say N here to save some memory. You can also say Y if you have an
  2.3421 -  "intelligent" multiport card such as Cyclades, Digiboards, etc.
  2.3422 -
  2.3423 -Support for sharing serial interrupts
  2.3424 -CONFIG_SERIAL_SHARE_IRQ
  2.3425 -  Some serial boards have hardware support which allows multiple dumb
  2.3426 -  serial ports on the same board to share a single IRQ. To enable
  2.3427 -  support for this in the serial driver, say Y here.
  2.3428 -
  2.3429 -Auto-detect IRQ on standard ports (unsafe)
  2.3430 -CONFIG_SERIAL_DETECT_IRQ
  2.3431 -  Say Y here if you want the kernel to try to guess which IRQ
  2.3432 -  to use for your serial port.
  2.3433 -
  2.3434 -  This is considered unsafe; it is far better to configure the IRQ in
  2.3435 -  a boot script using the setserial command.
  2.3436 -
  2.3437 -  If unsure, say N.
  2.3438 -
  2.3439 -Support special multiport boards
  2.3440 -CONFIG_SERIAL_MULTIPORT
  2.3441 -  Some multiport serial ports have special ports which are used to
  2.3442 -  signal when there are any serial ports on the board which need
  2.3443 -  servicing. Say Y here to enable the serial driver to take advantage
  2.3444 -  of those special I/O ports.
  2.3445 -
  2.3446 -SGI Zilog85C30 serial support
  2.3447 -CONFIG_SGI_SERIAL
  2.3448 -  If you want to use your SGI's built-in serial ports under Linux,
  2.3449 -  answer Y.
  2.3450 -
  2.3451 -SGI Newport Graphics support
  2.3452 -CONFIG_SGI_NEWPORT_GFX
  2.3453 -  If you have an SGI machine and you want to compile the graphics
  2.3454 -  drivers, say Y here. This will include the code for the
  2.3455 -  /dev/graphics and /dev/gfx drivers into the kernel for supporting
  2.3456 -  virtualized access to your graphics hardware.
  2.3457 -
  2.3458 -SGI Newport Console support
  2.3459 -CONFIG_SGI_NEWPORT_CONSOLE
  2.3460 -  Say Y here if you want the console on the Newport aka XL graphics
  2.3461 -  card of your Indy.  Most people say Y here.
  2.3462 -
  2.3463 -SGI DS1286 RTC support
  2.3464 -CONFIG_SGI_DS1286
  2.3465 -  If you say Y here and create a character special file /dev/rtc with
  2.3466 -  major number 10 and minor number 135 using mknod ("man mknod"), you
  2.3467 -  will get access to the real time clock built into your computer.
  2.3468 -  Every SGI has such a clock built in. It reports status information
  2.3469 -  via the file /proc/rtc and its behaviour is set by various ioctls on
  2.3470 -  /dev/rtc.
  2.3471 -
  2.3472 -Indy/I2 Hardware Watchdog
  2.3473 -CONFIG_INDYDOG
  2.3474 -  Hardwaredriver for the Indy's/I2's watchdog. This is a
  2.3475 -  watchdog timer that will reboot the machine after a 60 second 
  2.3476 -  timer expired and no process has written to /dev/watchdog during
  2.3477 -  that time.
  2.3478 -
  2.3479 -Support the Bell Technologies HUB6 card
  2.3480 -CONFIG_HUB6
  2.3481 -  Say Y here to enable support in the dumb serial driver to support
  2.3482 -  the HUB6 card.
  2.3483 -
  2.3484 -PCMCIA serial device support
  2.3485 -CONFIG_PCMCIA_SERIAL_CS
  2.3486 -  Say Y here to enable support for 16-bit PCMCIA serial devices,
  2.3487 -  including serial port cards, modems, and the modem functions of
  2.3488 -  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
  2.3489 -  credit-card size devices often used with laptops.)
  2.3490 -
  2.3491 -  This driver is also available as a module ( = code which can be
  2.3492 -  inserted in and removed from the running kernel whenever you want).
  2.3493 -  The module will be called serial_cs.o.  If you want to compile it as
  2.3494 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.3495 -  If unsure, say N.
  2.3496 -
  2.3497 -CONFIG_SYNCLINK_CS
  2.3498 -  Enable support for the SyncLink PC Card serial adapter, running
  2.3499 -  asynchronous and HDLC communications up to 512Kbps. The port is
  2.3500 -  selectable for RS-232, V.35, RS-449, RS-530, and X.21
  2.3501 -
  2.3502 -  This driver may be built as a module ( = code which can be
  2.3503 -  inserted in and removed from the running kernel whenever you want).
  2.3504 -  The module will be called synclinkmp.o.  If you want to do that, say M
  2.3505 -  here.
  2.3506 -
  2.3507 -ACP Modem (Mwave) support
  2.3508 -CONFIG_MWAVE
  2.3509 -  The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
  2.3510 -  kernel driver and a user level application. Together these components
  2.3511 -  support direct attachment to public switched telephone networks (PSTNs)
  2.3512 -  and support selected world wide countries.
  2.3513 -
  2.3514 -  This version of the ACP Modem driver supports the IBM Thinkpad 600E,
  2.3515 -  600, and 770 that include on board ACP modem hardware.
  2.3516 -
  2.3517 -  The modem also supports the standard communications port interface
  2.3518 -  (ttySx) and is compatible with the Hayes AT Command Set.
  2.3519 -
  2.3520 -  The user level application needed to use this driver can be found at
  2.3521 -  the IBM Linux Technology Center (LTC) web site:
  2.3522 -  <http://www.ibm.com/linux/ltc/>.
  2.3523 -
  2.3524 -  If you own one of the above IBM Thinkpads which has the Mwave chipset
  2.3525 -  in it, say Y.
  2.3526 -
  2.3527 -  This driver is also available as a module ( = code which can be
  2.3528 -  inserted in and removed from the running kernel whenever you want).
  2.3529 -  The module will be called mwave.o. If you want to compile it as
  2.3530 -  a module, say M here and read Documentation/modules.txt.
  2.3531 -
  2.3532 -/dev/agpgart (AGP Support)
  2.3533 -CONFIG_AGP
  2.3534 -  AGP (Accelerated Graphics Port) is a bus system mainly used to
  2.3535 -  connect graphics cards to the rest of the system.
  2.3536 -
  2.3537 -  If you have an AGP system and you say Y here, it will be possible to
  2.3538 -  use the AGP features of your 3D rendering video card. This code acts
  2.3539 -  as a sort of "AGP driver" for the motherboard's chipset.
  2.3540 -
  2.3541 -  If you need more texture memory than you can get with the AGP GART
  2.3542 -  (theoretically up to 256 MB, but in practice usually 64 or 128 MB
  2.3543 -  due to kernel allocation issues), you could use PCI accesses
  2.3544 -  and have up to a couple gigs of texture space.
  2.3545 -
  2.3546 -  Note that this is the only means to have XFree4/GLX use
  2.3547 -  write-combining with MTRR support on the AGP bus. Without it, OpenGL
  2.3548 -  direct rendering will be a lot slower but still faster than PIO.
  2.3549 -
  2.3550 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3551 -  use GLX or DRI.  If unsure, say N.
  2.3552 -
  2.3553 -  This driver is available as a module.  If you want to compile it as
  2.3554 -  a module, say M here and read <file:Documentation/modules.txt>.  The
  2.3555 -  module will be called agpgart.o.
  2.3556 -
  2.3557 -Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
  2.3558 -CONFIG_AGP_INTEL
  2.3559 -  This option gives you AGP support for the GLX component of the
  2.3560 -  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
  2.3561 -
  2.3562 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3563 -  use GLX or DRI.  If unsure, say N.
  2.3564 -
  2.3565 -Intel 460GX support
  2.3566 -CONFIG_AGP_I460
  2.3567 -  This option gives you AGP support for the Intel 460GX chipset.  This
  2.3568 -  chipset, the first to support Intel Itanium processors, is new and
  2.3569 -  this option is correspondingly a little experimental.
  2.3570 -
  2.3571 -  If you don't have a 460GX based machine (such as BigSur) with an AGP 
  2.3572 -  slot then this option isn't going to do you much good.  If you're
  2.3573 -  dying to do Direct Rendering on IA-64, this is what you're looking for.
  2.3574 -
  2.3575 -Intel I810/I815 DC100/I810e support
  2.3576 -CONFIG_AGP_I810
  2.3577 -  This option gives you AGP support for the Xserver on the Intel 810
  2.3578 -  815 and 830m chipset boards for their on-board integrated graphics. This
  2.3579 -  is required to do any useful video modes with these boards.
  2.3580 -
  2.3581 -VIA chipset support
  2.3582 -CONFIG_AGP_VIA
  2.3583 -  This option gives you AGP support for the GLX component of the
  2.3584 -  XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
  2.3585 -
  2.3586 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3587 -  use GLX or DRI.  If unsure, say N.
  2.3588 -
  2.3589 -AMD Irongate, 761, and 762 support
  2.3590 -CONFIG_AGP_AMD
  2.3591 -  This option gives you AGP support for the GLX component of the
  2.3592 -  XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
  2.3593 -
  2.3594 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3595 -  use GLX or DRI.  If unsure, say N.
  2.3596 -
  2.3597 -CONFIG_AGP_AMD_8151
  2.3598 -  This option gives you AGP support for the GLX component of
  2.3599 -  XFree86 on AMD K8 with an AGP 8151 chipset.
  2.3600 -
  2.3601 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3602 -  use GLX or DRI.  If unsure, say N.
  2.3603 -
  2.3604 -Generic SiS support
  2.3605 -CONFIG_AGP_SIS
  2.3606 -  This option gives you AGP support for the GLX component of the "soon
  2.3607 -  to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
  2.3608 -  chipsets.
  2.3609 -
  2.3610 -  Note that 5591/5592 AGP chipsets are NOT supported.
  2.3611 -
  2.3612 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3613 -  use GLX or DRI.  If unsure, say N.
  2.3614 -
  2.3615 -Serverworks LE/HE support
  2.3616 -CONFIG_AGP_SWORKS
  2.3617 -  Say Y here to support the Serverworks AGP card.  See 
  2.3618 -  <http://www.serverworks.com/> for product descriptions and images.
  2.3619 -
  2.3620 -ALI chipset support
  2.3621 -CONFIG_AGP_ALI
  2.3622 -  This option gives you AGP support for the GLX component of the
  2.3623 -  XFree86 4.x on the following ALi chipsets.  The supported chipsets
  2.3624 -  include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
  2.3625 -  For the ALi-chipset question, ALi suggests you refer to
  2.3626 -  <http://www.ali.com.tw/eng/support/index.shtml>.
  2.3627 -
  2.3628 -  The M1541 chipset can do AGP 1x and 2x, but note that there is an
  2.3629 -  acknowledged incompatibility with Matrox G200 cards. Due to
  2.3630 -  timing issues, this chipset cannot do AGP 2x with the G200.
  2.3631 -  This is a hardware limitation. AGP 1x seems to be fine, though.
  2.3632 -
  2.3633 -  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  2.3634 -  use GLX or DRI.  If unsure, say N.
  2.3635 -
  2.3636 -CONFIG_AGP_HP_ZX1
  2.3637 -  This option gives you AGP GART support for the HP ZX1 chipset
  2.3638 -  for IA64 processors.
  2.3639 -
  2.3640 -Support for ISA-bus hardware
  2.3641 -CONFIG_ISA
  2.3642 -  Find out whether you have ISA slots on your motherboard.  ISA is the
  2.3643 -  name of a bus system, i.e. the way the CPU talks to the other stuff
  2.3644 -  inside your box.  Other bus systems are PCI, EISA, MicroChannel
  2.3645 -  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
  2.3646 -  newer boards don't support it.  If you have ISA, say Y, otherwise N.
  2.3647 -
  2.3648 -Support for PCI bus hardware
  2.3649 -CONFIG_PCI
  2.3650 -  Find out whether you have a PCI motherboard. PCI is the name of a
  2.3651 -  bus system, i.e. the way the CPU talks to the other stuff inside
  2.3652 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  2.3653 -  VESA. If you have PCI, say Y, otherwise N.
  2.3654 -
  2.3655 -  The PCI-HOWTO, available from
  2.3656 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  2.3657 -  information about which PCI hardware does work under Linux and which
  2.3658 -  doesn't.
  2.3659 -
  2.3660 -PCI support
  2.3661 -CONFIG_PCI_INTEGRATOR
  2.3662 -  Find out whether you have a PCI motherboard. PCI is the name of a
  2.3663 -  bus system, i.e. the way the CPU talks to the other stuff inside
  2.3664 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  2.3665 -  VESA. If you have PCI, say Y, otherwise N.
  2.3666 -
  2.3667 -  The PCI-HOWTO, available from
  2.3668 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  2.3669 -  information about which PCI hardware does work under Linux and which
  2.3670 -  doesn't.
  2.3671 -
  2.3672 -QSpan PCI
  2.3673 -CONFIG_PCI_QSPAN
  2.3674 -  Find out whether you have a PCI motherboard. PCI is the name of a
  2.3675 -  bus system, i.e. the way the CPU talks to the other stuff inside
  2.3676 -  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  2.3677 -  VESA. If you have PCI, say Y, otherwise N.
  2.3678 -
  2.3679 -  The PCI-HOWTO, available from
  2.3680 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  2.3681 -  information about which PCI hardware does work under Linux and which
  2.3682 -  doesn't.
  2.3683 -
  2.3684 -# Choice: pci_access
  2.3685 -PCI access mode
  2.3686 -CONFIG_PCI_GOBIOS
  2.3687 -  On PCI systems, the BIOS can be used to detect the PCI devices and
  2.3688 -  determine their configuration. However, some old PCI motherboards
  2.3689 -  have BIOS bugs and may crash if this is done. Also, some embedded
  2.3690 -  PCI-based systems don't have any BIOS at all. Linux can also try to
  2.3691 -  detect the PCI hardware directly without using the BIOS.
  2.3692 -
  2.3693 -  With this option, you can specify how Linux should detect the PCI
  2.3694 -  devices. If you choose "BIOS", the BIOS will be used, if you choose
  2.3695 -  "Direct", the BIOS won't be used, and if you choose "Any", the
  2.3696 -  kernel will try the direct access method and falls back to the BIOS
  2.3697 -  if that doesn't work. If unsure, go with the default, which is
  2.3698 -  "Any".
  2.3699 -
  2.3700 -PCI device name database
  2.3701 -CONFIG_PCI_NAMES
  2.3702 -  By default, the kernel contains a database of all known PCI device
  2.3703 -  names to make the information in /proc/pci, /proc/ioports and
  2.3704 -  similar files comprehensible to the user. This database increases
  2.3705 -  size of the kernel image by about 80KB, but it gets freed after the
  2.3706 -  system boots up, so it doesn't take up kernel memory. Anyway, if you
  2.3707 -  are building an installation floppy or kernel for an embedded system
  2.3708 -  where kernel image size really matters, you can disable this feature
  2.3709 -  and you'll get device ID numbers instead of names.
  2.3710 -
  2.3711 -  When in doubt, say Y.
  2.3712 -
  2.3713 -Generic PCI hotplug support
  2.3714 -CONFIG_HOTPLUG_PCI
  2.3715 -  Say Y here if you have a motherboard with a PCI Hotplug controller.
  2.3716 -  This allows you to add and remove PCI cards while the machine is
  2.3717 -  powered up and running.  The file system pcihpfs must be mounted
  2.3718 -  in order to interact with any PCI Hotplug controllers.
  2.3719 -
  2.3720 -  This code is also available as a module ( = code which can be
  2.3721 -  inserted in and removed from the running kernel whenever you want).
  2.3722 -  The module will be called pci_hotplug.o. If you want to compile it
  2.3723 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.3724 -
  2.3725 -  When in doubt, say N.
  2.3726 -
  2.3727 -Compaq PCI Hotplug driver
  2.3728 -CONFIG_HOTPLUG_PCI_COMPAQ
  2.3729 -  Say Y here if you have a motherboard with a Compaq PCI Hotplug
  2.3730 -  controller.
  2.3731 -
  2.3732 -  This code is also available as a module ( = code which can be
  2.3733 -  inserted in and removed from the running kernel whenever you want).
  2.3734 -  The module will be called cpqphp.o. If you want to compile it
  2.3735 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.3736 -
  2.3737 -  When in doubt, say N.
  2.3738 -
  2.3739 -PCI Compaq Hotplug controller NVRAM support
  2.3740 -CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
  2.3741 -  Say Y here if you have a Compaq server that has a PCI Hotplug
  2.3742 -  controller.  This will allow the PCI Hotplug driver to store the PCI
  2.3743 -  system configuration options in NVRAM.
  2.3744 -
  2.3745 -  When in doubt, say N.
  2.3746 -
  2.3747 -ACPI PCI Hotplug driver
  2.3748 -CONFIG_HOTPLUG_PCI_ACPI
  2.3749 -  Say Y here if you have a system that supports PCI Hotplug using
  2.3750 -  ACPI.
  2.3751 -
  2.3752 -  This code is also available as a module ( = code which can be
  2.3753 -  inserted in and removed from the running kernel whenever you want).
  2.3754 -  The module will be called acpiphp.o. If you want to compile it
  2.3755 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.3756 -
  2.3757 -MCA support
  2.3758 -CONFIG_MCA
  2.3759 -  MicroChannel Architecture is found in some IBM PS/2 machines and
  2.3760 -  laptops.  It is a bus system similar to PCI or ISA. See
  2.3761 -  <file:Documentation/mca.txt> (and especially the web page given
  2.3762 -  there) before attempting to build an MCA bus kernel.
  2.3763 -
  2.3764 -Support for EISA-bus hardware
  2.3765 -CONFIG_EISA
  2.3766 -  The Extended Industry Standard Architecture (EISA) bus was
  2.3767 -  developed as an open alternative to the IBM MicroChannel bus.
  2.3768 -
  2.3769 -  The EISA bus provided some of the features of the IBM MicroChannel
  2.3770 -  bus while maintaining backward compatibility with cards made for
  2.3771 -  the older ISA bus.  The EISA bus saw limited use between 1988 and
  2.3772 -  1995 when it was made obsolete by the PCI bus.
  2.3773 -
  2.3774 -  Say Y here if you are building a kernel for an EISA-based machine.
  2.3775 -
  2.3776 -  Otherwise, say N.
  2.3777 -
  2.3778 -SGI Visual Workstation support
  2.3779 -CONFIG_VISWS
  2.3780 -  The SGI Visual Workstation series is an IA32-based workstation
  2.3781 -  based on SGI systems chips with some legacy PC hardware attached.
  2.3782 -  Say Y here to create a kernel to run on the SGI 320 or 540.
  2.3783 -  A kernel compiled for the Visual Workstation will not run on other
  2.3784 -  PC boards and vice versa.
  2.3785 -  See <file:Documentation/sgi-visws.txt> for more.
  2.3786 -
  2.3787 -SGI Visual Workstation framebuffer support
  2.3788 -CONFIG_FB_SGIVW
  2.3789 -  SGI Visual Workstation support for framebuffer graphics.
  2.3790 -
  2.3791 -I2O support
  2.3792 -CONFIG_I2O
  2.3793 -  The Intelligent Input/Output (I2O) architecture allows hardware
  2.3794 -  drivers to be split into two parts: an operating system specific
  2.3795 -  module called the OSM and an hardware specific module called the
  2.3796 -  HDM. The OSM can talk to a whole range of HDM's, and ideally the
  2.3797 -  HDM's are not OS dependent. This allows for the same HDM driver to
  2.3798 -  be used under different operating systems if the relevant OSM is in
  2.3799 -  place. In order for this to work, you need to have an I2O interface
  2.3800 -  adapter card in your computer. This card contains a special I/O
  2.3801 -  processor (IOP), thus allowing high speeds since the CPU does not
  2.3802 -  have to deal with I/O.
  2.3803 -
  2.3804 -  If you say Y here, you will get a choice of interface adapter
  2.3805 -  drivers and OSM's with the following questions.
  2.3806 -
  2.3807 -  This support is also available as a module ( = code which can be
  2.3808 -  inserted in and removed from the running kernel whenever you want).
  2.3809 -  If you want to compile it as a module, say M here and read
  2.3810 -  <file:Documentation/modules.txt>.  You will get modules called
  2.3811 -  i2o_core.o and i2o_config.o.
  2.3812 -
  2.3813 -  If unsure, say N.
  2.3814 -
  2.3815 -I2O PCI support
  2.3816 -CONFIG_I2O_PCI
  2.3817 -  Say Y for support of PCI bus I2O interface adapters. Currently this
  2.3818 -  is the only variety supported, so you should say Y.
  2.3819 -
  2.3820 -  This support is also available as a module called i2o_pci.o ( = code
  2.3821 -  which can be inserted in and removed from the running kernel
  2.3822 -  whenever you want). If you want to compile it as a module, say M
  2.3823 -  here and read <file:Documentation/modules.txt>.
  2.3824 -
  2.3825 -I2O Block OSM
  2.3826 -CONFIG_I2O_BLOCK
  2.3827 -  Include support for the I2O Block OSM. The Block OSM presents disk
  2.3828 -  and other structured block devices to the operating system.
  2.3829 -
  2.3830 -  This support is also available as a module called i2o_block.o ( =
  2.3831 -  code which can be inserted in and removed from the running kernel
  2.3832 -  whenever you want). If you want to compile it as a module, say M
  2.3833 -  here and read <file:Documentation/modules.txt>.
  2.3834 -
  2.3835 -I2O LAN OSM
  2.3836 -CONFIG_I2O_LAN
  2.3837 -  Include support for the LAN OSM. You will also need to include
  2.3838 -  support for token ring or FDDI if you wish to use token ring or FDDI
  2.3839 -  I2O cards with this driver.
  2.3840 -
  2.3841 -  This support is also available as a module called i2o_lan.o ( = code
  2.3842 -  which can be inserted in and removed from the running kernel
  2.3843 -  whenever you want). If you want to compile it as a module, say M
  2.3844 -  here and read <file:Documentation/modules.txt>.
  2.3845 -
  2.3846 -I2O SCSI OSM
  2.3847 -CONFIG_I2O_SCSI
  2.3848 -  Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  2.3849 -  I2O controller. You can use both the SCSI and Block OSM together if
  2.3850 -  you wish.
  2.3851 -
  2.3852 -  This support is also available as a module called i2o_scsi.o ( =
  2.3853 -  code which can be inserted in and removed from the running kernel
  2.3854 -  whenever you want). If you want to compile it as a module, say M
  2.3855 -  here and read <file:Documentation/modules.txt>.
  2.3856 -
  2.3857 -I2O /proc support
  2.3858 -CONFIG_I2O_PROC
  2.3859 -  If you say Y here and to "/proc file system support", you will be
  2.3860 -  able to read I2O related information from the virtual directory
  2.3861 -  /proc/i2o.
  2.3862 -
  2.3863 -  This support is also available as a module called i2o_proc.o ( =
  2.3864 -  code which can be inserted in and removed from the running kernel
  2.3865 -  whenever you want). If you want to compile it as a module, say M
  2.3866 -  here and read <file:Documentation/modules.txt>.
  2.3867 -
  2.3868 -Plug and Play support
  2.3869 -CONFIG_PNP
  2.3870 -  Plug and Play (PnP) is a standard for peripherals which allows those
  2.3871 -  peripherals to be configured by software, e.g. assign IRQ's or other
  2.3872 -  parameters. No jumpers on the cards are needed, instead the values
  2.3873 -  are provided to the cards from the BIOS, from the operating system,
  2.3874 -  or using a user-space utility.
  2.3875 -
  2.3876 -  Say Y here if you would like Linux to configure your Plug and Play
  2.3877 -  devices. You should then also say Y to "ISA Plug and Play support",
  2.3878 -  below. Alternatively, you can say N here and configure your PnP
  2.3879 -  devices using the user space utilities contained in the isapnptools
  2.3880 -  package.
  2.3881 -
  2.3882 -  This support is also available as a module ( = code which can be
  2.3883 -  inserted in and removed from the running kernel whenever you want).
  2.3884 -  If you want to compile it as a module, say M here and read
  2.3885 -  <file:Documentation/modules.txt>.
  2.3886 -
  2.3887 -ISA Plug and Play support
  2.3888 -CONFIG_ISAPNP
  2.3889 -  Say Y here if you would like support for ISA Plug and Play devices.
  2.3890 -  Some information is in <file:Documentation/isapnp.txt>.
  2.3891 -
  2.3892 -  This support is also available as a module called isapnp.o ( =
  2.3893 -  code which can be inserted in and removed from the running kernel
  2.3894 -  whenever you want). If you want to compile it as a module, say M
  2.3895 -  here and read <file:Documentation/modules.txt>.
  2.3896 -
  2.3897 -  If unsure, say Y.
  2.3898 -
  2.3899 -PNPBIOS support
  2.3900 -CONFIG_PNPBIOS
  2.3901 -  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
  2.3902 -  Specification Version 1.0A May 5, 1994" to autodetect built-in
  2.3903 -  mainboard resources (e.g. parallel port resources).
  2.3904 -
  2.3905 -  Other features (e.g. change resources, ESCD, event notification,
  2.3906 -  Docking station information, ISAPNP services) are not used.
  2.3907 -
  2.3908 -  Note: ACPI is expected to supersede PNPBIOS some day, currently it
  2.3909 -  co-exists nicely.
  2.3910 -
  2.3911 -  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
  2.3912 -  or have a look at /proc/bus/pnp.
  2.3913 -
  2.3914 -  If unsure, say Y.
  2.3915 -
  2.3916 -Support for hot-pluggable devices
  2.3917 -CONFIG_HOTPLUG
  2.3918 -  Say Y here if you want to plug devices into your computer while
  2.3919 -  the system is running, and be able to use them quickly.  In many
  2.3920 -  cases, the devices can likewise be unplugged at any time too.
  2.3921 -
  2.3922 -  One well known example of this is PCMCIA- or PC-cards, credit-card
  2.3923 -  size devices such as network cards, modems or hard drives which are
  2.3924 -  plugged into slots found on all modern laptop computers.  Another
  2.3925 -  example, used on modern desktops as well as laptops, is USB.
  2.3926 -
  2.3927 -  Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
  2.3928 -  software (at <http://linux-hotplug.sourceforge.net/>) and install it.
  2.3929 -  Then your kernel will automatically call out to a user mode "policy
  2.3930 -  agent" (/sbin/hotplug) to load modules and set up software needed
  2.3931 -  to use devices as you hotplug them.
  2.3932 -
  2.3933 -PCMCIA/CardBus support
  2.3934 -CONFIG_PCMCIA
  2.3935 -  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  2.3936 -  computer.  These are credit-card size devices such as network cards,
  2.3937 -  modems or hard drives often used with laptops computers.  There are
  2.3938 -  actually two varieties of these cards: the older 16 bit PCMCIA cards
  2.3939 -  and the newer 32 bit CardBus cards.  If you want to use CardBus
  2.3940 -  cards, you need to say Y here and also to "CardBus support" below.
  2.3941 -
  2.3942 -  To use your PC-cards, you will need supporting software from David
  2.3943 -  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  2.3944 -  for location).  Please also read the PCMCIA-HOWTO, available from
  2.3945 -  <http://www.tldp.org/docs.html#howto>.
  2.3946 -
  2.3947 -  This driver is also available as a module ( = code which can be
  2.3948 -  inserted in and removed from the running kernel whenever you want).
  2.3949 -  When compiled this way, there will be modules called pcmcia_core.o
  2.3950 -  and ds.o.  If you want to compile it as a module, say M here and
  2.3951 -  read <file:Documentation/modules.txt>.
  2.3952 -
  2.3953 -CardBus card and (Yenta) bridge support
  2.3954 -CONFIG_CARDBUS
  2.3955 -  CardBus is a bus mastering architecture for PC-cards, which allows
  2.3956 -  for 32 bit PC-cards (the original PCMCIA standard specifies only
  2.3957 -  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  2.3958 -
  2.3959 -  This option enables support for CardBus PC Cards, as well as support
  2.3960 -  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
  2.3961 -  CardBus compatible.  A "bridge" is the hardware inside your computer
  2.3962 -  that PCMCIA cards are plugged into.
  2.3963 -
  2.3964 -  To use your PC-cards, you will need supporting software from David
  2.3965 -  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  2.3966 -  for location).
  2.3967 -
  2.3968 -  If unsure, say Y.
  2.3969 -
  2.3970 -i82092 compatible bridge support
  2.3971 -CONFIG_I82092
  2.3972 -  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  2.3973 -  found in some older laptops and more commonly in evaluation boards for the
  2.3974 -  chip.
  2.3975 -
  2.3976 -i82365 compatible host bridge support
  2.3977 -CONFIG_I82365
  2.3978 -  Say Y here to include support for ISA-bus PCMCIA host bridges that
  2.3979 -  are register compatible with the Intel i82365.  These are found on
  2.3980 -  older laptops and ISA-bus card readers for desktop systems.  A
  2.3981 -  "bridge" is the hardware inside your computer that PCMCIA cards are
  2.3982 -  plugged into. If unsure, say N.
  2.3983 -
  2.3984 -Databook TCIC host bridge support
  2.3985 -CONFIG_TCIC
  2.3986 -  Say Y here to include support for the Databook TCIC family of PCMCIA
  2.3987 -  host bridges. These are only found on a handful of old systems.
  2.3988 -  "Bridge" is the name used for the hardware inside your computer that
  2.3989 -  PCMCIA cards are plugged into. If unsure, say N.
  2.3990 -
  2.3991 -System V IPC
  2.3992 -CONFIG_SYSVIPC
  2.3993 -  Inter Process Communication is a suite of library functions and
  2.3994 -  system calls which let processes (running programs) synchronize and
  2.3995 -  exchange information. It is generally considered to be a good thing,
  2.3996 -  and some programs won't run unless you say Y here. In particular, if
  2.3997 -  you want to run the DOS emulator dosemu under Linux (read the
  2.3998 -  DOSEMU-HOWTO, available from
  2.3999 -  <http://www.tldp.org/docs.html#howto>), you'll need to say Y
  2.4000 -  here.
  2.4001 -
  2.4002 -  You can find documentation about IPC with "info ipc" and also in
  2.4003 -  section 6.4 of the Linux Programmer's Guide, available from
  2.4004 -  <http://www.tldp.org/docs.html#guide>.
  2.4005 -
  2.4006 -BSD Process Accounting
  2.4007 -CONFIG_BSD_PROCESS_ACCT
  2.4008 -  If you say Y here, a user level program will be able to instruct the
  2.4009 -  kernel (via a special system call) to write process accounting
  2.4010 -  information to a file: whenever a process exits, information about
  2.4011 -  that process will be appended to the file by the kernel.  The
  2.4012 -  information includes things such as creation time, owning user,
  2.4013 -  command name, memory usage, controlling terminal etc. (the complete
  2.4014 -  list is in the struct acct in <file:include/linux/acct.h>).  It is
  2.4015 -  up to the user level program to do useful things with this
  2.4016 -  information.  This is generally a good idea, so say Y.
  2.4017 -
  2.4018 -Sysctl support
  2.4019 -CONFIG_SYSCTL
  2.4020 -  The sysctl interface provides a means of dynamically changing
  2.4021 -  certain kernel parameters and variables on the fly without requiring
  2.4022 -  a recompile of the kernel or reboot of the system.  The primary
  2.4023 -  interface consists of a system call, but if you say Y to "/proc
  2.4024 -  file system support", a tree of modifiable sysctl entries will be
  2.4025 -  generated beneath the /proc/sys directory. They are explained in the
  2.4026 -  files in <file:Documentation/sysctl/>.  Note that enabling this
  2.4027 -  option will enlarge the kernel by at least 8 KB.
  2.4028 -
  2.4029 -  As it is generally a good thing, you should say Y here unless
  2.4030 -  building a kernel for install/rescue disks or your system is very
  2.4031 -  limited in memory.
  2.4032 -
  2.4033 -# Choice: kcore
  2.4034 -Kernel core (/proc/kcore) format
  2.4035 -CONFIG_KCORE_ELF
  2.4036 -  If you enabled support for /proc file system then the file
  2.4037 -  /proc/kcore will contain the kernel core image. This can be used
  2.4038 -  in gdb:
  2.4039 -
  2.4040 -  $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
  2.4041 -
  2.4042 -  You have two choices here: ELF and A.OUT. Selecting ELF will make
  2.4043 -  /proc/kcore appear in ELF core format as defined by the Executable
  2.4044 -  and Linking Format specification. Selecting A.OUT will choose the
  2.4045 -  old "a.out" format which may be necessary for some old versions
  2.4046 -  of binutils or on some architectures.
  2.4047 -
  2.4048 -  This is especially useful if you have compiled the kernel with the
  2.4049 -  "-g" option to preserve debugging information. It is mainly used
  2.4050 -  for examining kernel data structures on the live kernel so if you
  2.4051 -  don't understand what this means or are not a kernel hacker, just
  2.4052 -  leave it at its default value ELF.
  2.4053 -
  2.4054 -Select a.out format for /proc/kcore
  2.4055 -CONFIG_KCORE_AOUT
  2.4056 -  Not necessary unless you're using a very out-of-date binutils
  2.4057 -  version.  You probably want KCORE_ELF.
  2.4058 -
  2.4059 -Kernel support for ELF binaries
  2.4060 -CONFIG_BINFMT_ELF
  2.4061 -  ELF (Executable and Linkable Format) is a format for libraries and
  2.4062 -  executables used across different architectures and operating
  2.4063 -  systems. Saying Y here will enable your kernel to run ELF binaries
  2.4064 -  and enlarge it by about 13 KB. ELF support under Linux has now all
  2.4065 -  but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  2.4066 -  because it is portable (this does *not* mean that you will be able
  2.4067 -  to run executables from different architectures or operating systems
  2.4068 -  however) and makes building run-time libraries very easy. Many new
  2.4069 -  executables are distributed solely in ELF format. You definitely
  2.4070 -  want to say Y here.
  2.4071 -
  2.4072 -  Information about ELF is contained in the ELF HOWTO available from
  2.4073 -  <http://www.tldp.org/docs.html#howto>.
  2.4074 -
  2.4075 -  If you find that after upgrading from Linux kernel 1.2 and saying Y
  2.4076 -  here, you still can't run any ELF binaries (they just crash), then
  2.4077 -  you'll have to install the newest ELF runtime libraries, including
  2.4078 -  ld.so (check the file <file:Documentation/Changes> for location and
  2.4079 -  latest version).
  2.4080 -
  2.4081 -  If you want to compile this as a module ( = code which can be
  2.4082 -  inserted in and removed from the running kernel whenever you want),
  2.4083 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.4084 -  will be called binfmt_elf.o. Saying M or N here is dangerous because
  2.4085 -  some crucial programs on your system might be in ELF format.
  2.4086 -
  2.4087 -Kernel support for a.out binaries
  2.4088 -CONFIG_BINFMT_AOUT
  2.4089 -  A.out (Assembler.OUTput) is a set of formats for libraries and
  2.4090 -  executables used in the earliest versions of UNIX. Linux used the
  2.4091 -  a.out formats QMAGIC and ZMAGIC until they were replaced with the
  2.4092 -  ELF format.
  2.4093 -
  2.4094 -  As more and more programs are converted to ELF, the use for a.out
  2.4095 -  will gradually diminish. If you disable this option it will reduce
  2.4096 -  your kernel by one page. This is not much and by itself does not
  2.4097 -  warrant removing support. However its removal is a good idea if you
  2.4098 -  wish to ensure that absolutely none of your programs will use this
  2.4099 -  older executable format. If you don't know what to answer at this
  2.4100 -  point then answer Y. If someone told you "You need a kernel with
  2.4101 -  QMAGIC support" then you'll have to say Y here. You may answer M to
  2.4102 -  compile a.out support as a module and later load the module when you
  2.4103 -  want to use a program or library in a.out format. The module will be
  2.4104 -  called binfmt_aout.o. Saying M or N here is dangerous though,
  2.4105 -  because some crucial programs on your system might still be in A.OUT
  2.4106 -  format.
  2.4107 -
  2.4108 -OSF/1 v4 readv/writev compatibility
  2.4109 -CONFIG_OSF4_COMPAT
  2.4110 -  Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  2.4111 -  with v4 shared libraries freely available from Compaq. If you're
  2.4112 -  going to use shared libraries from Tru64 version 5.0 or later, say N.
  2.4113 -
  2.4114 -Kernel support for Linux/Intel ELF binaries
  2.4115 -CONFIG_BINFMT_EM86
  2.4116 -  Say Y here if you want to be able to execute Linux/Intel ELF
  2.4117 -  binaries just like native Alpha binaries on your Alpha machine. For
  2.4118 -  this to work, you need to have the emulator /usr/bin/em86 in place.
  2.4119 -
  2.4120 -  You can get the same functionality by saying N here and saying Y to
  2.4121 -  "Kernel support for MISC binaries".
  2.4122 -
  2.4123 -  You may answer M to compile the emulation support as a module and
  2.4124 -  later load the module when you want to use a Linux/Intel binary. The
  2.4125 -  module will be called binfmt_em86.o. If unsure, say Y.
  2.4126 -
  2.4127 -Kernel support for SOM binaries
  2.4128 -CONFIG_BINFMT_SOM
  2.4129 -  SOM is a binary executable format inherited from HP/UX.  Say Y here
  2.4130 -  to be able to load and execute SOM binaries directly.
  2.4131 -
  2.4132 -Kernel support for MISC binaries
  2.4133 -CONFIG_BINFMT_MISC
  2.4134 -  If you say Y here, it will be possible to plug wrapper-driven binary
  2.4135 -  formats into the kernel. You will like this especially when you use
  2.4136 -  programs that need an interpreter to run like Java, Python or
  2.4137 -  Emacs-Lisp. It's also useful if you often run DOS executables under
  2.4138 -  the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  2.4139 -  <http://www.tldp.org/docs.html#howto>). Once you have
  2.4140 -  registered such a binary class with the kernel, you can start one of
  2.4141 -  those programs simply by typing in its name at a shell prompt; Linux
  2.4142 -  will automatically feed it to the correct interpreter.
  2.4143 -
  2.4144 -  You can do other nice things, too. Read the file
  2.4145 -  <file:Documentation/binfmt_misc.txt> to learn how to use this
  2.4146 -  feature, and <file:Documentation/java.txt> for information about how
  2.4147 -  to include Java support.
  2.4148 -
  2.4149 -  You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
  2.4150 -  use this part of the kernel.
  2.4151 -
  2.4152 -  You may say M here for module support and later load the module when
  2.4153 -  you have use for it; the module is called binfmt_misc.o. If you
  2.4154 -  don't know what to answer at this point, say Y.
  2.4155 -
  2.4156 -Kernel support for JAVA binaries
  2.4157 -CONFIG_BINFMT_JAVA
  2.4158 -  If you say Y here, the kernel will load and execute Java J-code
  2.4159 -  binaries directly.  Note: this option is obsolete and scheduled for
  2.4160 -  removal, use CONFIG_BINFMT_MISC instead.
  2.4161 -
  2.4162 -Solaris binary emulation
  2.4163 -CONFIG_SOLARIS_EMUL
  2.4164 -  This is experimental code which will enable you to run (many)
  2.4165 -  Solaris binaries on your SPARC Linux machine.
  2.4166 -
  2.4167 -  This code is also available as a module ( = code which can be
  2.4168 -  inserted in and removed from the running kernel whenever you want).
  2.4169 -  The module will be called solaris.o. If you want to compile it as a
  2.4170 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4171 -
  2.4172 -SUN SME environment monitoring
  2.4173 -CONFIG_ENVCTRL
  2.4174 -  Kernel support for temperature and fan monitoring on Sun SME
  2.4175 -  machines.
  2.4176 -
  2.4177 -  This code is also available as a module ( = code which can be
  2.4178 -  inserted in and removed from the running kernel whenever you want).
  2.4179 -  The module will be called envctrl.o. If you want to compile it as a
  2.4180 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4181 -
  2.4182 -# Choice: x86type
  2.4183 -Processor family
  2.4184 -CONFIG_M386
  2.4185 -  This is the processor type of your CPU. This information is used for
  2.4186 -  optimizing purposes. In order to compile a kernel that can run on
  2.4187 -  all x86 CPU types (albeit not optimally fast), you can specify
  2.4188 -  "386" here.
  2.4189 -
  2.4190 -  The kernel will not necessarily run on earlier architectures than
  2.4191 -  the one you have chosen, e.g. a Pentium optimized kernel will run on
  2.4192 -  a PPro, but not necessarily on a i486.
  2.4193 -
  2.4194 -  Here are the settings recommended for greatest speed:
  2.4195 -   - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
  2.4196 -     486DLC/DLC2, UMC 486SX-S and NexGen Nx586.  Only "386" kernels
  2.4197 -     will run on a 386 class machine.
  2.4198 -   - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
  2.4199 -     SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
  2.4200 -   - "586" for generic Pentium CPUs, possibly lacking the TSC
  2.4201 -     (time stamp counter) register.
  2.4202 -   - "Pentium-Classic" for the Intel Pentium.
  2.4203 -   - "Pentium-MMX" for the Intel Pentium MMX.
  2.4204 -   - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
  2.4205 -   - "Pentium-III" for the Intel Pentium III
  2.4206 -     and Celerons based on the Coppermine core.
  2.4207 -   - "Pentium-4" for the Intel Pentium 4.
  2.4208 -   - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
  2.4209 -   - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
  2.4210 -   - "Elan" for the AMD Elan family (Elan SC400/SC410).
  2.4211 -   - "Crusoe" for the Transmeta Crusoe series.
  2.4212 -   - "Winchip-C6" for original IDT Winchip.
  2.4213 -   - "Winchip-2" for IDT Winchip 2.
  2.4214 -   - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
  2.4215 -   - "CyrixIII" for VIA Cyrix III or VIA C3.
  2.4216 -   - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
  2.4217 -
  2.4218 -  If you don't know what to do, choose "386".
  2.4219 -
  2.4220 -486
  2.4221 -CONFIG_M486
  2.4222 -  Select this for a x486 processor, ether Intel or one of the
  2.4223 -  compatible processors from AMD, Cyrix, IBM, or Intel.  Includes DX,
  2.4224 -  DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
  2.4225 -  U5S.
  2.4226 -
  2.4227 -586/K5/5x86/6x86/6x86MX
  2.4228 -CONFIG_M586
  2.4229 -  Select this for an x586 or x686 processor such as the AMD K5, the
  2.4230 -  Intel 5x86 or 6x86, or the Intel 6x86MX.  This choice does not
  2.4231 -  assume the RDTSC instruction.
  2.4232 -
  2.4233 -Pentium Classic
  2.4234 -CONFIG_M586TSC
  2.4235 -  Select this for a Pentium Classic processor with the RDTSC (Read
  2.4236 -  Time Stamp Counter) instruction for benchmarking.
  2.4237 -
  2.4238 -VIA C3-2 (Nehemiah)
  2.4239 -CONFIG_MVIAC3_2
  2.4240 -  Select this for a VIA C3 "Nehemiah". Selecting this enables usage of SSE
  2.4241 -  and tells gcc to treat the CPU as a 686.
  2.4242 -
  2.4243 -  Note, this kernel will not boot on older (pre model 9) C3s.
  2.4244 -
  2.4245 -32-bit PDC
  2.4246 -CONFIG_PDC_NARROW
  2.4247 -  Saying Y here will allow developers with a C180, C200, C240, C360,
  2.4248 -  J200, J210, and/or a J2240 to test 64-bit kernels by providing a
  2.4249 -  wrapper for the 32-bit PDC calls.  Since the machines which require
  2.4250 -  this option do not support over 4G of RAM, this option is targeted
  2.4251 -  for developers of these machines wishing to test changes on both
  2.4252 -  32-bit and 64-bit configurations.
  2.4253 -
  2.4254 -  If unsure, say N.
  2.4255 -
  2.4256 -VGA text console
  2.4257 -CONFIG_VGA_CONSOLE
  2.4258 -  Saying Y here will allow you to use Linux in text mode through a
  2.4259 -  display that complies with the generic VGA standard. Virtually
  2.4260 -  everyone wants that.
  2.4261 -
  2.4262 -  The program SVGATextMode can be used to utilize SVGA video cards to
  2.4263 -  their full potential in text mode. Download it from
  2.4264 -  <ftp://ibiblio.org/pub/Linux/utils/console/>.
  2.4265 -
  2.4266 -  Say Y.
  2.4267 -
  2.4268 -Distribute interrupts on all CPUs by default
  2.4269 -CONFIG_IRQ_ALL_CPUS
  2.4270 -  This option gives the kernel permission to distribute IRQs across
  2.4271 -  multiple CPUs.  Saying N here will route all IRQs to the first
  2.4272 -  CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
  2.4273 -  Power3 boxes should say N for now.
  2.4274 -
  2.4275 -Video mode selection support
  2.4276 -CONFIG_VIDEO_SELECT
  2.4277 -  This enables support for text mode selection on kernel startup. If
  2.4278 -  you want to take advantage of some high-resolution text mode your
  2.4279 -  card's BIOS offers, but the traditional Linux utilities like
  2.4280 -  SVGATextMode don't, you can say Y here and set the mode using the
  2.4281 -  "vga=" option from your boot loader (lilo or loadlin) or set
  2.4282 -  "vga=ask" which brings up a video mode menu on kernel startup. (Try
  2.4283 -  "man bootparam" or see the documentation of your boot loader about
  2.4284 -  how to pass options to the kernel.)
  2.4285 -
  2.4286 -  Read the file <file:Documentation/svga.txt> for more information
  2.4287 -  about the Video mode selection support. If unsure, say N.
  2.4288 -
  2.4289 -Support for frame buffer devices
  2.4290 -CONFIG_FB
  2.4291 -  The frame buffer device provides an abstraction for the graphics
  2.4292 -  hardware. It represents the frame buffer of some video hardware and
  2.4293 -  allows application software to access the graphics hardware through
  2.4294 -  a well-defined interface, so the software doesn't need to know
  2.4295 -  anything about the low-level (hardware register) stuff.
  2.4296 -
  2.4297 -  Frame buffer devices work identically across the different
  2.4298 -  architectures supported by Linux and make the implementation of
  2.4299 -  application programs easier and more portable; at this point, an X
  2.4300 -  server exists which uses the frame buffer device exclusively.
  2.4301 -  On several non-X86 architectures, the frame buffer device is the
  2.4302 -  only way to use the graphics hardware.
  2.4303 -
  2.4304 -  The device is accessed through special device nodes, usually located
  2.4305 -  in the /dev directory, i.e. /dev/fb*.
  2.4306 -
  2.4307 -  You need an utility program called fbset to make full use of frame
  2.4308 -  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  2.4309 -  and the Framebuffer-HOWTO at
  2.4310 -  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  2.4311 -  information.
  2.4312 -
  2.4313 -  Say Y here and to the driver for your graphics board below if you
  2.4314 -  are compiling a kernel for a non-x86 architecture.
  2.4315 -
  2.4316 -  If you are compiling for the x86 architecture, you can say Y if you
  2.4317 -  want to play with it, but it is not essential. Please note that
  2.4318 -  running graphical applications that directly touch the hardware
  2.4319 -  (e.g. an accelerated X server) and that are not frame buffer
  2.4320 -  device-aware may cause unexpected results. If unsure, say N.
  2.4321 -
  2.4322 -Acorn VIDC support
  2.4323 -CONFIG_FB_ACORN
  2.4324 -  This is the frame buffer device driver for the Acorn VIDC graphics
  2.4325 -  hardware found in Acorn RISC PCs and other ARM-based machines.  If
  2.4326 -  unsure, say N.
  2.4327 -
  2.4328 -Permedia2 support
  2.4329 -CONFIG_FB_PM2
  2.4330 -  This is the frame buffer device driver for the Permedia2 AGP frame
  2.4331 -  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
  2.4332 -  product page at
  2.4333 -  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
  2.4334 -
  2.4335 -Enable FIFO disconnect feature
  2.4336 -CONFIG_FB_PM2_FIFO_DISCONNECT
  2.4337 -  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
  2.4338 -
  2.4339 -Generic Permedia2 PCI board support
  2.4340 -CONFIG_FB_PM2_PCI
  2.4341 -  Say Y to enable support for Permedia2 AGP frame buffer card from
  2.4342 -  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
  2.4343 -
  2.4344 -Phase5 CVisionPPC/BVisionPPC support
  2.4345 -CONFIG_FB_PM2_CVPPC
  2.4346 -  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
  2.4347 -  framebuffer cards.  Phase 5 is no longer with us, alas.
  2.4348 -
  2.4349 -Amiga native chipset support
  2.4350 -CONFIG_FB_AMIGA
  2.4351 -  This is the frame buffer device driver for the builtin graphics
  2.4352 -  chipset found in Amigas.
  2.4353 -
  2.4354 -  The driver is also available as a module ( = code which can be
  2.4355 -  inserted and removed from the running kernel whenever you want). The
  2.4356 -  module will be called amifb.o. If you want to compile it as a
  2.4357 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4358 -
  2.4359 -Amiga OCS chipset support
  2.4360 -CONFIG_FB_AMIGA_OCS
  2.4361 -  This enables support for the original Agnus and Denise video chips,
  2.4362 -  found in the Amiga 1000 and most A500's and A2000's. If you intend
  2.4363 -  to run Linux on any of these systems, say Y; otherwise say N.
  2.4364 -
  2.4365 -Amiga ECS chipset support
  2.4366 -CONFIG_FB_AMIGA_ECS
  2.4367 -  This enables support for the Enhanced Chip Set, found in later
  2.4368 -  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
  2.4369 -  you intend to run Linux on any of these systems, say Y; otherwise
  2.4370 -  say N.
  2.4371 -
  2.4372 -Amiga AGA chipset support
  2.4373 -CONFIG_FB_AMIGA_AGA
  2.4374 -  This enables support for the Advanced Graphics Architecture (also
  2.4375 -  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
  2.4376 -  and CD32. If you intend to run Linux on any of these systems, say Y;
  2.4377 -  otherwise say N.
  2.4378 -
  2.4379 -Amiga CyberVision support
  2.4380 -CONFIG_FB_CYBER
  2.4381 -  This enables support for the Cybervision 64 graphics card from
  2.4382 -  Phase5. Please note that its use is not all that intuitive (i.e. if
  2.4383 -  you have any questions, be sure to ask!). Say N unless you have a
  2.4384 -  Cybervision 64 or plan to get one before you next recompile the
  2.4385 -  kernel. Please note that this driver DOES NOT support the
  2.4386 -  Cybervision 64 3D card, as they use incompatible video chips.
  2.4387 -
  2.4388 -CyberPro 20x0 support
  2.4389 -CONFIG_FB_CYBER2000
  2.4390 -  This enables support for the Integraphics CyberPro 20x0 and 5000
  2.4391 -  VGA chips used in the Rebel.com Netwinder and other machines.
  2.4392 -  Say Y if you have a NetWinder or a graphics card containing this
  2.4393 -  device, otherwise say N.
  2.4394 -
  2.4395 -Amiga CyberVision3D support
  2.4396 -CONFIG_FB_VIRGE
  2.4397 -  This enables support for the Cybervision 64/3D graphics card from
  2.4398 -  Phase5. Please note that its use is not all that intuitive (i.e. if
  2.4399 -  you have any questions, be sure to ask!). Say N unless you have a
  2.4400 -  Cybervision 64/3D or plan to get one before you next recompile the
  2.4401 -  kernel. Please note that this driver DOES NOT support the older
  2.4402 -  Cybervision 64 card, as they use incompatible video chips.
  2.4403 -
  2.4404 -Amiga RetinaZ3 support
  2.4405 -CONFIG_FB_RETINAZ3
  2.4406 -  This enables support for the Retina Z3 graphics card. Say N unless
  2.4407 -  you have a Retina Z3 or plan to get one before you next recompile
  2.4408 -  the kernel.
  2.4409 -
  2.4410 -Cirrus Logic generic driver
  2.4411 -CONFIG_FB_CLGEN
  2.4412 -  This enables support for Cirrus Logic GD542x/543x based boards on
  2.4413 -  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
  2.4414 -
  2.4415 -  If you have a PCI-based system, this enables support for these
  2.4416 -  chips: GD-543x, GD-544x, GD-5480.
  2.4417 -
  2.4418 -  Please read the file <file:Documentation/fb/clgenfb.txt>.
  2.4419 -
  2.4420 -  Say N unless you have such a graphics board or plan to get one
  2.4421 -  before you next recompile the kernel.
  2.4422 -
  2.4423 -Apollo support
  2.4424 -CONFIG_APOLLO
  2.4425 -  Say Y here if you want to run Linux on an MC680x0-based Apollo
  2.4426 -  Domain workstation such as the DN3500.
  2.4427 -
  2.4428 -Apollo 3c505 "EtherLink Plus" support
  2.4429 -CONFIG_APOLLO_ELPLUS
  2.4430 -  Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
  2.4431 -  If you don't have one made for Apollos, you can use one from a PC,
  2.4432 -  except that your Apollo won't be able to boot from it (because the
  2.4433 -  code in the ROM will be for a PC).
  2.4434 -
  2.4435 -Atari native chipset support
  2.4436 -CONFIG_FB_ATARI
  2.4437 -  This is the frame buffer device driver for the builtin graphics
  2.4438 -  chipset found in Ataris.
  2.4439 -
  2.4440 -Amiga FrameMaster II/Rainbow II support
  2.4441 -CONFIG_FB_FM2
  2.4442 -  This is the frame buffer device driver for the Amiga FrameMaster
  2.4443 -  card from BSC (exhibited 1992 but not shipped as a CBM product).
  2.4444 -
  2.4445 -Open Firmware frame buffer device support
  2.4446 -CONFIG_FB_OF
  2.4447 -  Say Y if you want support with Open Firmware for your graphics
  2.4448 -  board.
  2.4449 -
  2.4450 -S3 Trio frame buffer device support
  2.4451 -CONFIG_FB_S3TRIO
  2.4452 -  If you have a S3 Trio say Y. Say N for S3 Virge.
  2.4453 -
  2.4454 -3Dfx Banshee/Voodoo3 display support
  2.4455 -CONFIG_FB_3DFX
  2.4456 -  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  2.4457 -  chips. Say Y if you have such a graphics board.
  2.4458 -
  2.4459 -  The driver is also available as a module ( = code which can be
  2.4460 -  inserted and removed from the running kernel whenever you want). The
  2.4461 -  module will be called tdfxfb.o. If you want to compile it as a
  2.4462 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4463 -
  2.4464 -nVidia Riva support
  2.4465 -CONFIG_FB_RIVA
  2.4466 -  This driver supports graphics boards with the nVidia Riva/Geforce
  2.4467 -  chips.
  2.4468 -  Say Y if you have such a graphics board.
  2.4469 -
  2.4470 -  The driver is also available as a module ( = code which can be
  2.4471 -  inserted and removed from the running kernel whenever you want). The
  2.4472 -  module will be called rivafb.o. If you want to compile it as a
  2.4473 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4474 -
  2.4475 -Trident Blade/Image support
  2.4476 -CONFIG_FB_TRIDENT
  2.4477 -  This driver is supposed to support graphics boards with the
  2.4478 -  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  2.4479 -  but also on some motherboards.Read <file:Documentation/fb/tridentfb.txt>
  2.4480 -
  2.4481 -  Say Y if you have such a graphics board.
  2.4482 -
  2.4483 -  The driver is also available as a module ( = code which can be
  2.4484 -  inserted and removed from the running kernel whenever you want). The
  2.4485 -  module will be called tridentfb.o. If you want to compile it as a
  2.4486 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4487 -
  2.4488 -ATI Mach64 display support
  2.4489 -CONFIG_FB_ATY
  2.4490 -  This driver supports graphics boards with the ATI Mach64 chips.
  2.4491 -  Say Y if you have such a graphics board.
  2.4492 -
  2.4493 -  The driver is also available as a module ( = code which can be
  2.4494 -  inserted and removed from the running kernel whenever you want). The
  2.4495 -  module will be called atyfb.o. If you want to compile it as a
  2.4496 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4497 -
  2.4498 -ATI Rage128 display support
  2.4499 -CONFIG_FB_ATY128
  2.4500 -  This driver supports graphics boards with the ATI Rage128 chips.
  2.4501 -  Say Y if you have such a graphics board and read
  2.4502 -  <file:Documentation/fb/aty128fb.txt>.
  2.4503 -
  2.4504 -  The driver is also available as a module ( = code which can be
  2.4505 -  inserted and removed from the running kernel whenever you want). The
  2.4506 -  module will be called aty128fb.o. If you want to compile it as a
  2.4507 -  module, say M here and read <file:Documentation/modules.txt>.
  2.4508 -
  2.4509 -Maxine (Personal DECstation) onboard framebuffer support
  2.4510 -CONFIG_FB_MAXINE
  2.4511 -  Say Y here to directly support the on-board framebuffer in the
  2.4512 -  Maxine (5000/20, /25, /33) version of the DECstation.  There is a
  2.4513 -  page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
  2.4514 -
  2.4515 -PMAG-BA TURBOchannel framebuffer support
  2.4516 -CONFIG_FB_PMAG_BA
  2.4517 -  Say Y here to directly support the on-board PMAG-BA framebuffer in
  2.4518 -  the 5000/1xx versions of the DECstation.  There is a page dedicated
  2.4519 -  to Linux on DECstations at <http://decstation.unix-ag.org/>.
  2.4520 -
  2.4521 -PMAGB-B TURBOchannel framebuffer support
  2.4522 -CONFIG_FB_PMAGB_B
  2.4523 -  Say Y here to directly support the on-board PMAGB-B framebuffer in
  2.4524 -  the 5000/1xx versions of the DECstation.  There is a page dedicated
  2.4525 -  to Linux on DECstations at <http://decstation.unix-ag.org/>.
  2.4526 -
  2.4527 -FutureTV PCI card
  2.4528 -CONFIG_ARCH_FTVPCI
  2.4529 -  Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
  2.4530 -  Electronics) StrongARM PCI card.
  2.4531 -
  2.4532 -ANAKIN Vehicle Telematics Platform
  2.4533 -CONFIG_ARCH_ANAKIN
  2.4534 -  The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
  2.4535 -  64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
  2.4536 -
  2.4537 -  On board peripherals:
  2.4538 -        * Front display: 400x234 16 bit TFT touchscreen
  2.4539 -        * External independent second screen interface
  2.4540 -        * CAN controller SJA1000
  2.4541 -        * USB host controller
  2.4542 -        * 6 channel video codec with hardware overlay
  2.4543 -        * Smartcard reader
  2.4544 -        * IrDa
  2.4545 -
  2.4546 -  Modules interfaced over the Multi Media Extension slots:
  2.4547 -        * A communication card
  2.4548 -                Wavecom GPRS modem
  2.4549 -                uBlock GPS
  2.4550 -                Bosch DAB module
  2.4551 -        * An audio card ( 4 * 40W, AC97 Codec, I2S)
  2.4552 -
  2.4553 -Altera Excalibur XA10 Dev Board
  2.4554 -ARCH_CAMELOT
  2.4555 -  This enables support for Altera's Excalibur XA10 development board.
  2.4556 -  If you would like to build your kernel to run on one of these boards
  2.4557 -  then you must say 'Y' here. Otherwise say 'N'
  2.4558 -
  2.4559 -Link-Up Systems LCD support
  2.4560 -CONFIG_FB_L7200
  2.4561 -  This driver supports the L7200 Color LCD.
  2.4562 -  Say Y if you want graphics support.
  2.4563 -
  2.4564 -NeoMagic display support (EXPERIMENTAL)
  2.4565 -CONFIG_FB_NEOMAGIC
  2.4566 -  This driver supports notebooks with NeoMagic PCI chips.
  2.4567 -  Say Y if you have such a graphics card. 
  2.4568 -
  2.4569 -  The driver is also available as a module ( = code which can be
  2.4570 -  inserted and removed from the running kernel whenever you want). The
  2.4571 -  module will be called neofb.o. If you want to compile it as a
  2.4572 -  module, say M here and read Documentation/modules.txt.
  2.4573 -
  2.4574 -PowerMac "control" frame buffer device support
  2.4575 -CONFIG_FB_CONTROL
  2.4576 -  This driver supports a frame buffer for the graphics adapter in the
  2.4577 -  Power Macintosh 7300 and others.
  2.4578 -
  2.4579 -PowerMac "platinum" frame buffer device support
  2.4580 -CONFIG_FB_PLATINUM
  2.4581 -  This driver supports a frame buffer for the "platinum" graphics
  2.4582 -  adapter in some Power Macintoshes.
  2.4583 -
  2.4584 -PowerMac "valkyrie" frame buffer device support
  2.4585 -CONFIG_FB_VALKYRIE
  2.4586 -  This driver supports a frame buffer for the "valkyrie" graphics
  2.4587 -  adapter in some Power Macintoshes.
  2.4588 -
  2.4589 -Chips 65550 display support
  2.4590 -CONFIG_FB_CT65550
  2.4591 -  This is the frame buffer device driver for the Chips & Technologies
  2.4592 -  65550 graphics chip in PowerBooks.
  2.4593 -
  2.4594 -TGA frame buffer support
  2.4595 -CONFIG_FB_TGA
  2.4596 -  This is the frame buffer device driver for generic TGA graphic
  2.4597 -  cards. Say Y if you have one of those.
  2.4598 -
  2.4599 -VESA VGA graphics console
  2.4600 -CONFIG_FB_VESA
  2.4601 -  This is the frame buffer device driver for generic VESA 2.0
  2.4602 -  compliant graphic cards. The older VESA 1.2 cards are not supported.
  2.4603 -  You will get a boot time penguin logo at no additional cost. Please
  2.4604 -  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
  2.4605 -
  2.4606 -VGA 16-color planar support
  2.4607 -CONFIG_FBCON_VGA_PLANES
  2.4608 -  This low level frame buffer console driver enable the kernel to use
  2.4609 -  the 16-color planar modes of the old VGA cards where the bits of
  2.4610 -  each pixel are separated into 4 planes.
  2.4611 -
  2.4612 -  Only answer Y here if you have a (very old) VGA card that isn't VESA
  2.4613 -  2 compatible.
  2.4614 -
  2.4615 -VGA 16-color graphics console
  2.4616 -CONFIG_FB_VGA16
  2.4617 -  This is the frame buffer device driver for VGA 16 color graphic
  2.4618 -  cards. Say Y if you have such a card.
  2.4619 -
  2.4620 -  This code is also available as a module. If you want to compile it
  2.4621 -  as a module ( = code which can be inserted in and removed from the
  2.4622 -  running kernel whenever you want), say M here and read
  2.4623 -  <file:Documentation/modules.txt>.  The module will be called
  2.4624 -  vga16fb.o.
  2.4625 -
  2.4626 -Generic STI frame buffer device support
  2.4627 -CONFIG_FB_STI
  2.4628 -  STI refers to the HP "Standard Text Interface" which is a set of
  2.4629 -  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
  2.4630 -  Enabling this option will implement the linux framebuffer device and
  2.4631 -  an fbcon color text console using calls to the STI BIOS routines.
  2.4632 -  The HP framebuffer device is sometimes planar, using a strange memory
  2.4633 -  layout, and changing the plane mask to create colored pixels
  2.4634 -  can require a call to the STI routines, so /dev/fb may not actually 
  2.4635 -  be useful.  However, on some systems packed pixel formats are supported.  
  2.4636 -  It is sufficient for basic text console functions, including fonts.
  2.4637 -
  2.4638 -  You should probably enable this option, unless you are having
  2.4639 -  trouble getting video when booting the kernel (make sure it isn't
  2.4640 -  just that you are running the console on the serial port, though).
  2.4641 -  Really old HP boxes may not have STI, and must use the PDC BIOS
  2.4642 -  console or the IODC BIOS.
  2.4643 -
  2.4644 -Select other compiled-in fonts
  2.4645 -CONFIG_FBCON_FONTS
  2.4646 -  Say Y here if you would like to use fonts other than the default
  2.4647 -  your frame buffer console usually use.
  2.4648 -
  2.4649 -  Note that the answer to this question won't directly affect the
  2.4650 -  kernel: saying N will just cause the configurator to skip all
  2.4651 -  the questions about foreign fonts.
  2.4652 -
  2.4653 -  If unsure, say N (the default choices are safe).
  2.4654 -
  2.4655 -VGA 8x16 font
  2.4656 -CONFIG_FONT_8x16
  2.4657 -  This is the "high resolution" font for the VGA frame buffer (the one
  2.4658 -  provided by the VGA text console 80x25 mode.
  2.4659 -
  2.4660 -  If unsure, say Y.
  2.4661 -
  2.4662 -Support only 8 pixels wide fonts
  2.4663 -CONFIG_FBCON_FONTWIDTH8_ONLY
  2.4664 -  Answer Y here will make the kernel provide only the 8x8 fonts (these
  2.4665 -  are the less readable).
  2.4666 -
  2.4667 -  If unsure, say N.
  2.4668 -
  2.4669 -Sparc console 8x16 font
  2.4670 -CONFIG_FONT_SUN8x16
  2.4671 -  This is the high resolution console font for Sun machines. Say Y.
  2.4672 -
  2.4673 -Sparc console 12x22 font (not supported by all drivers)
  2.4674 -CONFIG_FONT_SUN12x22
  2.4675 -  This is the high resolution console font for Sun machines with very
  2.4676 -  big letters (like the letters used in the SPARC PROM). If the
  2.4677 -  standard font is unreadable for you, say Y, otherwise say N.
  2.4678 -
  2.4679 -VGA 8x8 font
  2.4680 -CONFIG_FONT_8x8
  2.4681 -  This is the "high resolution" font for the VGA frame buffer (the one
  2.4682 -  provided by the text console 80x50 (and higher) modes).
  2.4683 -
  2.4684 -  Note that this is a poor quality font. The VGA 8x16 font is quite a
  2.4685 -  lot more readable.
  2.4686 -
  2.4687 -  Given the resolution provided by the frame buffer device, answer N
  2.4688 -  here is safe.
  2.4689 -
  2.4690 -Mac console 6x11 font (not supported by all drivers)
  2.4691 -CONFIG_FONT_6x11
  2.4692 -  Small console font with Macintosh-style high-half glyphs.  Some Mac
  2.4693 -  framebuffer drivers don't support this one at all.
  2.4694 -
  2.4695 -Pearl (old m68k) console 8x8 font
  2.4696 -CONFIG_FONT_PEARL_8x8
  2.4697 -  Small console font with PC-style control-character and high-half
  2.4698 -  glyphs.
  2.4699 -
  2.4700 -Acorn console 8x8 font
  2.4701 -CONFIG_FONT_ACORN_8x8
  2.4702 -  Small console font with PC-style control characters and high-half
  2.4703 -  glyphs.
  2.4704 -
  2.4705 -Backward compatibility mode for Xpmac
  2.4706 -CONFIG_FB_COMPAT_XPMAC
  2.4707 -  If you use the Xpmac X server (common with mklinux), you'll need to
  2.4708 -  say Y here to use X. You should consider changing to XFree86 which
  2.4709 -  includes a server that supports the frame buffer device directly
  2.4710 -  (XF68_FBDev).
  2.4711 -
  2.4712 -Hercules (HGA) mono graphics support
  2.4713 -CONFIG_FB_HGA
  2.4714 -  Say Y here if you have a Hercules mono graphics card.
  2.4715 -
  2.4716 -  This driver is also available as a module ( = code which can be
  2.4717 -  inserted and removed from the running kernel whenever you want).
  2.4718 -  The module will be called hgafb.o. If you want to compile it as
  2.4719 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.4720 -
  2.4721 -  As this card technology is 15 years old, most people will answer N
  2.4722 -  here.
  2.4723 -
  2.4724 -Epson 1355 framebuffer support
  2.4725 -CONFIG_FB_E1355
  2.4726 -  Build in support for the SED1355 Epson Research Embedded RAMDAC
  2.4727 -  LCD/CRT Controller (since redesignated as the S1D13505) as a
  2.4728 -  framebuffer.  Product specs at
  2.4729 -  <http://www.erd.epson.com/vdc/html/products.htm>.
  2.4730 -
  2.4731 -Dreamcast Frame Buffer support
  2.4732 -CONFIG_FB_DC
  2.4733 -  Say Y here to enable support for the framebuffer on the Sega
  2.4734 -  Dreamcast.  This driver is also available as a module, dcfb.o.
  2.4735 -
  2.4736 -Register Base Address
  2.4737 -CONFIG_E1355_REG_BASE
  2.4738 -  Epson SED1355/S1D13505 LCD/CRT controller register base address.
  2.4739 -  See the manuals at
  2.4740 -  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  2.4741 -  discussion.
  2.4742 -
  2.4743 -Framebuffer Base Address
  2.4744 -CONFIG_E1355_FB_BASE
  2.4745 -  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
  2.4746 -  the manuals at
  2.4747 -  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  2.4748 -  discussion.
  2.4749 -
  2.4750 -NEC PowerVR 2 display support
  2.4751 -CONFIG_FB_PVR2
  2.4752 -  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
  2.4753 -  run linux on your Dreamcast, you will have to say Y here.
  2.4754 -  This driver may or may not work on other PowerVR 2 cards, but is
  2.4755 -  totally untested.  Use at your own risk.  If unsure, say N.
  2.4756 -
  2.4757 -  This driver is also available as a module ( = code which can be
  2.4758 -  inserted and removed from the running kernel whenever you want).
  2.4759 -  The module will be called pvr2fb.o.  If you want to compile it as
  2.4760 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.4761 -
  2.4762 -  You can pass several parameters to the driver at boot time or at
  2.4763 -  module load time.  The parameters look like "video=pvr2:XXX", where
  2.4764 -  the meaning of XXX can be found at the end of the main source file
  2.4765 -  (<file:drivers/video/pvr2fb.c>). Please see the file
  2.4766 -  <file:Documentation/fb/pvr2fb.txt>.
  2.4767 -
  2.4768 -Debug pvr2fb
  2.4769 -CONFIG_FB_PVR2_DEBUG
  2.4770 -  Say Y here if you wish for the pvr2fb driver to print out debugging
  2.4771 -  messages. Most people will want to say N here. If unsure, you will
  2.4772 -  also want to say N.
  2.4773 -
  2.4774 -Matrox unified accelerated driver
  2.4775 -CONFIG_FB_MATROX
  2.4776 -  Say Y here if you have a Matrox Millennium, Millennium II, Mystique,
  2.4777 -  Mystique 220, Productiva G100, Mystique G200, Millennium G200,
  2.4778 -  Matrox G400, G450 or G550 card in your box. At this time, support for 
  2.4779 -  the G-series digital output is almost non-existant.
  2.4780 -
  2.4781 -  This driver is also available as a module ( = code which can be
  2.4782 -  inserted and removed from the running kernel whenever you want).
  2.4783 -  The module will be called matroxfb.o. If you want to compile it as
  2.4784 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.4785 -
  2.4786 -  You can pass several parameters to the driver at boot time or at
  2.4787 -  module load time. The parameters look like "video=matrox:XXX", and
  2.4788 -  are described in <file:Documentation/fb/matroxfb.txt>.
  2.4789 -
  2.4790 -Matrox Millennium I/II support
  2.4791 -CONFIG_FB_MATROX_MILLENIUM
  2.4792 -  Say Y here if you have a Matrox Millennium or Matrox Millennium II
  2.4793 -  video card. If you select "Advanced lowlevel driver options" below,
  2.4794 -  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
  2.4795 -  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
  2.4796 -  also use font widths different from 8.
  2.4797 -
  2.4798 -Matrox Mystique support
  2.4799 -CONFIG_FB_MATROX_MYSTIQUE
  2.4800 -  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
  2.4801 -  video card. If you select "Advanced lowlevel driver options" below,
  2.4802 -  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  2.4803 -  packed pixel and 32 bpp packed pixel. You can also use font widths
  2.4804 -  different from 8.
  2.4805 -
  2.4806 -Matrox G100/G200/G400/G450/G550 support
  2.4807 -CONFIG_FB_MATROX_G100
  2.4808 -  Say Y here if you have a Matrox G100, G200, G400, G450, or G550
  2.4809 -  based video card. If you select "Advanced lowlevel driver options",
  2.4810 -  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  2.4811 -  packed pixel and 32 bpp packed pixel. You can also use font widths
  2.4812 -  different from 8.
  2.4813 -
  2.4814 -  If you need support for G400 secondary head, you must first say Y to
  2.4815 -  "I2C support" and "I2C bit-banging support" in the character devices
  2.4816 -  section, and then to "Matrox I2C support" and "G400 second head
  2.4817 -  support" here in the framebuffer section.
  2.4818 -  
  2.4819 -  If you have G550, you must also compile support for G450/G550 secondary
  2.4820 -  head into kernel, otherwise picture will be shown only on the output you
  2.4821 -  are probably not using...
  2.4822 -
  2.4823 -  If you need support for G450 or G550 secondary head, say Y to
  2.4824 -  "Matrox G450/G550 second head support" below.
  2.4825 -
  2.4826 -Matrox I2C support
  2.4827 -CONFIG_FB_MATROX_I2C
  2.4828 -  This drivers creates I2C buses which are needed for accessing the
  2.4829 -  DDC (I2C) bus present on all Matroxes, an I2C bus which
  2.4830 -  interconnects Matrox optional devices, like MGA-TVO on G200 and
  2.4831 -  G400, and the secondary head DDC bus, present on G400 only.
  2.4832 -
  2.4833 -  You can say Y or M here if you want to experiment with monitor
  2.4834 -  detection code. You must say Y or M here if you want to use either
  2.4835 -  second head of G400 or MGA-TVO on G200 or G400.
  2.4836 -
  2.4837 -  If you compile it as module, it will create a module named
  2.4838 -  i2c-matroxfb.o.
  2.4839 -
  2.4840 -Matrox G400 second head support
  2.4841 -CONFIG_FB_MATROX_MAVEN
  2.4842 -  WARNING !!! This support does not work with G450 !!!
  2.4843 -
  2.4844 -  Say Y or M here if you want to use a secondary head (meaning two
  2.4845 -  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
  2.4846 -  head is not compatible with accelerated XFree 3.3.x SVGA servers -
  2.4847 -  secondary head output is blanked while you are in X. With XFree
  2.4848 -  3.9.17 preview you can use both heads if you use SVGA over fbdev or
  2.4849 -  the fbdev driver on first head and the fbdev driver on second head.
  2.4850 -
  2.4851 -  If you compile it as module, two modules are created,
  2.4852 -  matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
  2.4853 -  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
  2.4854 -  also load i2c-matroxfb to get it to run.
  2.4855 -
  2.4856 -  The driver starts in monitor mode and you must use the matroxset
  2.4857 -  tool (available at
  2.4858 -  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
  2.4859 -  PAL or NTSC or to swap primary and secondary head outputs.
  2.4860 -  Secondary head driver also always start in 640x480 resolution, you
  2.4861 -  must use fbset to change it.
  2.4862 -
  2.4863 -  Also do not forget that second head supports only 16 and 32 bpp
  2.4864 -  packed pixels, so it is a good idea to compile them into the kernel
  2.4865 -  too.  You can use only some font widths, as the driver uses generic
  2.4866 -  painting procedures (the secondary head does not use acceleration
  2.4867 -  engine).
  2.4868 -
  2.4869 -Matrox G450 second head support
  2.4870 -CONFIG_FB_MATROX_G450
  2.4871 -  Say Y or M here if you want to use a secondary head (meaning two
  2.4872 -  monitors in parallel) on G450, or if you are using analog output
  2.4873 -  of G550.
  2.4874 -
  2.4875 -  If you compile it as module, two modules are created,
  2.4876 -  matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you
  2.4877 -  want two independent display devices.
  2.4878 -
  2.4879 -  The driver starts in monitor mode and currently does not support
  2.4880 -  output in TV modes.  You must use the matroxset tool (available
  2.4881 -  at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to swap
  2.4882 -  primary and secondary head outputs.  Secondary head driver always
  2.4883 -  start in 640x480 resolution and you must use fbset to change it.
  2.4884 -
  2.4885 -  Note on most G550 cards the analog output is the secondary head,
  2.4886 -  so you will need to say Y here to use it.
  2.4887 -
  2.4888 -  Also do not forget that second head supports only 16 and 32 bpp
  2.4889 -  packed pixels, so it is a good idea to compile them into the kernel
  2.4890 -  too. You can use only some font widths, as the driver uses generic
  2.4891 -  painting procedures (the secondary head does not use acceleration
  2.4892 -  engine).
  2.4893 -
  2.4894 -Matrox unified driver multihead support
  2.4895 -CONFIG_FB_MATROX_MULTIHEAD
  2.4896 -  Say Y here if you have more than one (supported) Matrox device in
  2.4897 -  your computer and you want to use all of them for different monitors
  2.4898 -  ("multihead"). If you have only one device, you should say N because
  2.4899 -  the driver compiled with Y is larger and a bit slower, especially on
  2.4900 -  ia32 (ix86).
  2.4901 -
  2.4902 -  If you said M to "Matrox unified accelerated driver" and N here, you
  2.4903 -  will still be able to use several Matrox devices simultaneously:
  2.4904 -  insert several instances of the module matroxfb.o into the kernel
  2.4905 -  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
  2.4906 -  for the different Matrox devices. This method is slightly faster but
  2.4907 -  uses 40 KB of kernel memory per Matrox card.
  2.4908 -
  2.4909 -  There is no need for enabling 'Matrox multihead support' if you have
  2.4910 -  only one Matrox card in the box.
  2.4911 -
  2.4912 -3Dfx Voodoo Graphics / Voodoo2 frame buffer support
  2.4913 -CONFIG_FB_VOODOO1
  2.4914 -  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
  2.4915 -  Voodoo2 (cvg) based graphics card.
  2.4916 -
  2.4917 -  This driver is also available as a module ( = code which can be 
  2.4918 -  inserted and removed from the running kernel whenever you want).
  2.4919 -  The module will be called sstfb.o. If you want to compile it as
  2.4920 -  a module, say M here and read Documentation/modules.txt.
  2.4921 -
  2.4922 -  WARNING: Do not use any application that uses the 3D engine
  2.4923 -  (namely glide) while using this driver.
  2.4924 -  Please read the file Documentation/fb/README-sstfb.txt for supported
  2.4925 -  options and other important info  support.
  2.4926 -
  2.4927 -MDA text console (dual-headed)
  2.4928 -CONFIG_MDA_CONSOLE
  2.4929 -  Say Y here if you have an old MDA or monochrome Hercules graphics
  2.4930 -  adapter in your system acting as a second head ( = video card). You
  2.4931 -  will then be able to use two monitors with your Linux system. Do not
  2.4932 -  say Y here if your MDA card is the primary card in your system; the
  2.4933 -  normal VGA driver will handle it.
  2.4934 -
  2.4935 -  This driver is also available as a module ( = code which can be
  2.4936 -  inserted and removed from the running kernel whenever you want).
  2.4937 -  The module will be called mdacon.o. If you want to compile it as
  2.4938 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.4939 -
  2.4940 -  If unsure, say N.
  2.4941 -
  2.4942 -SBUS and UPA framebuffers
  2.4943 -CONFIG_FB_SBUS
  2.4944 -  Say Y if you want support for SBUS or UPA based frame buffer device.
  2.4945 -
  2.4946 -Creator/Creator3D support
  2.4947 -CONFIG_FB_CREATOR
  2.4948 -  This is the frame buffer device driver for the Creator and Creator3D
  2.4949 -  graphics boards.
  2.4950 -
  2.4951 -CGsix (GX,TurboGX) support
  2.4952 -CONFIG_FB_CGSIX
  2.4953 -  This is the frame buffer device driver for the CGsix (GX, TurboGX)
  2.4954 -  frame buffer.
  2.4955 -
  2.4956 -BWtwo support
  2.4957 -CONFIG_FB_BWTWO
  2.4958 -  This is the frame buffer device driver for the BWtwo frame buffer.
  2.4959 -
  2.4960 -CGthree support
  2.4961 -CONFIG_FB_CGTHREE
  2.4962 -  This is the frame buffer device driver for the CGthree frame buffer.
  2.4963 -
  2.4964 -CGfourteen (SX) support
  2.4965 -CONFIG_FB_CGFOURTEEN
  2.4966 -  This is the frame buffer device driver for the CGfourteen frame
  2.4967 -  buffer on Desktop SPARCsystems with the SX graphics option.
  2.4968 -
  2.4969 -P9100 (Sparcbook 3 only) support
  2.4970 -CONFIG_FB_P9100
  2.4971 -  This is the frame buffer device driver for the P9100 card
  2.4972 -  supported on Sparcbook 3 machines.
  2.4973 -
  2.4974 -Leo (ZX) support
  2.4975 -CONFIG_FB_LEO
  2.4976 -  This is the frame buffer device driver for the SBUS-based Sun ZX
  2.4977 -  (leo) frame buffer cards.
  2.4978 -
  2.4979 -IGA 168x display support
  2.4980 -CONFIG_FB_IGA
  2.4981 -  This is the framebuffer device for the INTERGRAPHICS 1680 and
  2.4982 -  successor frame buffer cards.
  2.4983 -
  2.4984 -TCX (SS4/SS5 only) support
  2.4985 -CONFIG_FB_TCX
  2.4986 -  This is the frame buffer device driver for the TCX 24/8bit frame
  2.4987 -  buffer.
  2.4988 -
  2.4989 -HD64461 Frame Buffer support
  2.4990 -CONFIG_FB_HIT
  2.4991 -  This is the frame buffer device driver for the Hitachi HD64461 LCD
  2.4992 -  frame buffer card.
  2.4993 -
  2.4994 -SIS acceleration
  2.4995 -CONFIG_FB_SIS
  2.4996 -  This is the frame buffer device driver for the SiS 630 and 640 Super
  2.4997 -  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.
  2.4998 -
  2.4999 -SIS 630/540/730 support
  2.5000 -CONFIG_FB_SIS_300
  2.5001 -  This is the frame buffer device driver for the SiS 630 and related
  2.5002 -  Super Socket 7 UMA cards.  Specs available at
  2.5003 -  <http://www.sis.com.tw/>.
  2.5004 -
  2.5005 -SIS 315H/315 support
  2.5006 -CONFIG_FB_SIS_315
  2.5007 -  This is the frame buffer device driver for the SiS 315 graphics
  2.5008 -  card.  Specs available at <http://www.sis.com.tw/>.
  2.5009 -
  2.5010 -IMS Twin Turbo display support
  2.5011 -CONFIG_FB_IMSTT
  2.5012 -  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
  2.5013 -  many Macintosh and compatible computers.
  2.5014 -
  2.5015 -CONFIG_FB_TX3912
  2.5016 -  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core;
  2.5017 -  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  2.5018 -
  2.5019 -  Say Y here to enable kernel support for the on-board framebuffer.
  2.5020 -
  2.5021 -Virtual Frame Buffer support (ONLY FOR TESTING!)
  2.5022 -CONFIG_FB_VIRTUAL
  2.5023 -  This is a `virtual' frame buffer device. It operates on a chunk of
  2.5024 -  unswappable kernel memory instead of on the memory of a graphics
  2.5025 -  board. This means you cannot see any output sent to this frame
  2.5026 -  buffer device, while it does consume precious memory. The main use
  2.5027 -  of this frame buffer device is testing and debugging the frame
  2.5028 -  buffer subsystem. Do NOT enable it for normal systems! To protect
  2.5029 -  the innocent, it has to be enabled explicitly at boot time using the
  2.5030 -  kernel option `video=vfb:'.
  2.5031 -
  2.5032 -  This driver is also available as a module ( = code which can be
  2.5033 -  inserted and removed from the running kernel whenever you want). The
  2.5034 -  module will be called vfb.o. If you want to compile it as a module,
  2.5035 -  say M here and read <file:Documentation/modules.txt>.
  2.5036 -
  2.5037 -  If unsure, say N.
  2.5038 -
  2.5039 -Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
  2.5040 -CONFIG_FB_ATY_CT
  2.5041 -  Say Y here to support use of ATI's 64-bit Rage boards (or other
  2.5042 -  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
  2.5043 -  framebuffer device.  The ATI product support page for these boards
  2.5044 -  is at <http://support.ati.com/products/pc/mach64/>.
  2.5045 -
  2.5046 -Sony Vaio Picturebook laptop LCD panel support
  2.5047 -CONFIG_FB_ATY_CT_VAIO_LCD
  2.5048 -  Say Y here if you want to use the full width of the Sony Vaio 
  2.5049 -  Picturebook laptops LCD panels (you will get a 128x30 console).
  2.5050 -
  2.5051 -  Note that you need to activate this mode using the 'vga=0x301'
  2.5052 -  option from your boot loader (lilo or loadlin).  See the
  2.5053 -  documentation of your boot loader about how to pass options to the
  2.5054 -  kernel.
  2.5055 -  
  2.5056 -Mach64 GX support
  2.5057 -CONFIG_FB_ATY_GX
  2.5058 -  Say Y here to support use of the ATI Mach64 Graphics Expression
  2.5059 -  board (or other boards based on the Mach64 GX chipset) as a
  2.5060 -  framebuffer device.  The ATI product support page for these boards
  2.5061 -  is at
  2.5062 -  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  2.5063 -
  2.5064 -ATI Radeon display support
  2.5065 -CONFIG_FB_RADEON
  2.5066 -  Choose this option if you want to use an ATI Radeon graphics card as
  2.5067 -  a framebuffer device.  There are both PCI and AGP versions.  You
  2.5068 -  don't need to choose this to run the Radeon in plain VGA mode.
  2.5069 -  There is a product page at
  2.5070 -  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
  2.5071 -
  2.5072 -SA-1100 LCD support
  2.5073 -CONFIG_FB_SA1100
  2.5074 -  This is a framebuffer device for the SA-1100 LCD Controller.
  2.5075 -  See <http://www.linux-fbdev.org/> for information on framebuffer
  2.5076 -  devices.
  2.5077 -
  2.5078 -  If you plan to use the LCD display with your SA-1100 system, say
  2.5079 -  Y here.
  2.5080 -
  2.5081 -Advanced low level driver options
  2.5082 -CONFIG_FBCON_ADVANCED
  2.5083 -  The frame buffer console uses character drawing routines that are
  2.5084 -  tailored to the specific organization of pixels in the memory of
  2.5085 -  your graphics hardware. These are called the low level frame buffer
  2.5086 -  console drivers. Note that they are used for text console output
  2.5087 -  only; they are NOT needed for graphical applications.
  2.5088 -
  2.5089 -  If you say N here, the needed low level drivers are automatically
  2.5090 -  enabled, depending on what frame buffer devices you selected above.
  2.5091 -  This is recommended for most users.
  2.5092 -
  2.5093 -  If you say Y here, you have more fine-grained control over which low
  2.5094 -  level drivers are enabled. You can e.g. leave out low level drivers
  2.5095 -  for color depths you do not intend to use for text consoles.
  2.5096 -
  2.5097 -  Low level frame buffer console drivers can be modules ( = code which
  2.5098 -  can be inserted and removed from the running kernel whenever you
  2.5099 -  want). The modules will be called fbcon-*.o. If you want to compile
  2.5100 -  (some of) them as modules, read <file:Documentation/modules.txt>.
  2.5101 -
  2.5102 -  If unsure, say N.
  2.5103 -
  2.5104 -Monochrome support
  2.5105 -CONFIG_FBCON_MFB
  2.5106 -  This is the low level frame buffer console driver for monochrome
  2.5107 -  (2 colors) packed pixels.
  2.5108 -
  2.5109 -2 bpp packed pixels support
  2.5110 -CONFIG_FBCON_CFB2
  2.5111 -  This is the low level frame buffer console driver for 2 bits per
  2.5112 -  pixel (4 colors) packed pixels.
  2.5113 -
  2.5114 -4 bpp packed pixels support
  2.5115 -CONFIG_FBCON_CFB4
  2.5116 -  This is the low level frame buffer console driver for 4 bits per
  2.5117 -  pixel (16 colors) packed pixels.
  2.5118 -
  2.5119 -8 bpp packed pixels support
  2.5120 -CONFIG_FBCON_CFB8
  2.5121 -  This is the low level frame buffer console driver for 8 bits per
  2.5122 -  pixel (256 colors) packed pixels.
  2.5123 -
  2.5124 -16 bpp packed pixels support
  2.5125 -CONFIG_FBCON_CFB16
  2.5126 -  This is the low level frame buffer console driver for 15 or 16 bits
  2.5127 -  per pixel (32K or 64K colors, also known as `hicolor') packed
  2.5128 -  pixels.
  2.5129 -
  2.5130 -24 bpp packed pixels support
  2.5131 -CONFIG_FBCON_CFB24
  2.5132 -  This is the low level frame buffer console driver for 24 bits per
  2.5133 -  pixel (16M colors, also known as `truecolor') packed pixels. It is
  2.5134 -  NOT for `sparse' 32 bits per pixel mode.
  2.5135 -
  2.5136 -32 bpp packed pixels support
  2.5137 -CONFIG_FBCON_CFB32
  2.5138 -  This is the low level frame buffer console driver for 32 bits per
  2.5139 -  pixel (16M colors, also known as `truecolor') sparse packed pixels.
  2.5140 -
  2.5141 -Amiga bitplanes support
  2.5142 -CONFIG_FBCON_AFB
  2.5143 -  This is the low level frame buffer console driver for 1 to 8
  2.5144 -  bitplanes (2 to 256 colors) on Amiga.
  2.5145 -
  2.5146 -Amiga interleaved bitplanes support
  2.5147 -CONFIG_FBCON_ILBM
  2.5148 -  This is the low level frame buffer console driver for 1 to 8
  2.5149 -  interleaved bitplanes (2 to 256 colors) on Amiga.
  2.5150 -
  2.5151 -Atari interleaved bitplanes (2 planes) support
  2.5152 -CONFIG_FBCON_IPLAN2P2
  2.5153 -  This is the low level frame buffer console driver for 2 interleaved
  2.5154 -  bitplanes (4 colors) on Atari.
  2.5155 -
  2.5156 -Atari interleaved bitplanes (4 planes) support
  2.5157 -CONFIG_FBCON_IPLAN2P4
  2.5158 -  This is the low level frame buffer console driver for 4 interleaved
  2.5159 -  bitplanes (16 colors) on Atari.
  2.5160 -
  2.5161 -Atari interleaved bitplanes (8 planes) support
  2.5162 -CONFIG_FBCON_IPLAN2P8
  2.5163 -  This is the low level frame buffer console driver for 8 interleaved
  2.5164 -  bitplanes (256 colors) on Atari.
  2.5165 -
  2.5166 -Mac variable bpp packed pixels support
  2.5167 -CONFIG_FBCON_MAC
  2.5168 -  This is the low level frame buffer console driver for 1/2/4/8/16/32
  2.5169 -  bits per pixel packed pixels on Mac. It supports variable font
  2.5170 -  widths for low resolution screens.
  2.5171 -
  2.5172 -Permedia3 support (EXPERIMENTAL)
  2.5173 -CONFIG_FB_PM3
  2.5174 -  This is the frame buffer device driver for the 3DLabs Permedia3
  2.5175 -  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  2.5176 -  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  2.5177 -  and maybe other boards.
  2.5178 -
  2.5179 -HGA monochrome support
  2.5180 -CONFIG_FBCON_HGA
  2.5181 -  This is the low level frame buffer console driver for Hercules mono
  2.5182 -  graphics cards.
  2.5183 -
  2.5184 -VGA characters/attributes support
  2.5185 -CONFIG_FBCON_VGA
  2.5186 -  This is the low level frame buffer console driver for VGA text mode;
  2.5187 -  it is used by frame buffer device drivers that support VGA text
  2.5188 -  mode.
  2.5189 -
  2.5190 -Parallel-port support
  2.5191 -CONFIG_PARPORT
  2.5192 -  If you want to use devices connected to your machine's parallel port
  2.5193 -  (the connector at the computer with 25 holes), e.g. printer, ZIP
  2.5194 -  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
  2.5195 -  create a mini network by connecting the parallel ports of two local
  2.5196 -  machines) etc., then you need to say Y here; please read
  2.5197 -  <file:Documentation/parport.txt> and
  2.5198 -  <file:drivers/parport/BUGS-parport>.
  2.5199 -
  2.5200 -  For extensive information about drivers for many devices attaching
  2.5201 -  to the parallel port see <http://www.torque.net/linux-pp.html> on
  2.5202 -  the WWW.
  2.5203 -
  2.5204 -  It is possible to share a single parallel port among several devices
  2.5205 -  and it is safe to compile all the corresponding drivers into the
  2.5206 -  kernel.  If you want to compile parallel port support as a module
  2.5207 -  ( = code which can be inserted in and removed from the running
  2.5208 -  kernel whenever you want), say M here and read
  2.5209 -  <file:Documentation/modules.txt>.  The module will be called
  2.5210 -  parport.o.  If you have more than one parallel port and want to
  2.5211 -  specify which port and IRQ to be used by this driver at module load
  2.5212 -  time, take a look at <file:Documentation/parport.txt>.
  2.5213 -
  2.5214 -  If unsure, say Y.
  2.5215 -
  2.5216 -PC-style hardware
  2.5217 -CONFIG_PARPORT_PC
  2.5218 -  You should say Y here if you have a PC-style parallel port. All IBM
  2.5219 -  PC compatible computers and some Alphas have PC-style parallel
  2.5220 -  ports.
  2.5221 -
  2.5222 -  This code is also available as a module.  If you want to compile it
  2.5223 -  as a module ( = code which can be inserted in and removed from the
  2.5224 -  running kernel whenever you want), say M here and read
  2.5225 -  <file:Documentation/modules.txt>.  The module will be called
  2.5226 -  parport_pc.o.
  2.5227 -
  2.5228 -  If unsure, say Y.
  2.5229 -
  2.5230 -Parallel+serial PCI multi-IO card support
  2.5231 -CONFIG_PARPORT_SERIAL
  2.5232 -  This adds support for multi-IO PCI cards that have parallel and
  2.5233 -  serial ports.  You should say Y or M here.  If you say M, the module
  2.5234 -  will be called parport_serial.o.
  2.5235 -
  2.5236 -Use FIFO/DMA if available
  2.5237 -CONFIG_PARPORT_PC_FIFO
  2.5238 -  Many parallel port chipsets provide hardware that can speed up
  2.5239 -  printing. Say Y here if you want to take advantage of that.
  2.5240 -
  2.5241 -  As well as actually having a FIFO, or DMA capability, the kernel
  2.5242 -  will need to know which IRQ the parallel port has.  By default,
  2.5243 -  parallel port interrupts will not be used, and so neither will the
  2.5244 -  FIFO.  See <file:Documentation/parport.txt> to find out how to
  2.5245 -  specify which IRQ/DMA to use.
  2.5246 -
  2.5247 -SuperIO chipset support
  2.5248 -CONFIG_PARPORT_PC_SUPERIO
  2.5249 -  Saying Y here enables some probes for Super-IO chipsets in order to
  2.5250 -  find out things like base addresses, IRQ lines and DMA channels.  It
  2.5251 -  is safe to say N.
  2.5252 -
  2.5253 -Support for PCMCIA management for PC-style ports
  2.5254 -CONFIG_PARPORT_PC_PCMCIA
  2.5255 -  Say Y here if you need PCMCIA support for your PC-style parallel
  2.5256 -  ports. If unsure, say N.
  2.5257 -
  2.5258 -  This driver is also available as a module ( = code which can be
  2.5259 -  inserted in and removed from the running kernel whenever you want).
  2.5260 -  If you want to compile it as a module, say M here and read
  2.5261 -  <file:Documentation/modules.txt>. The module will be called
  2.5262 -  parport_cs.o
  2.5263 -
  2.5264 -Support foreign hardware
  2.5265 -CONFIG_PARPORT_OTHER
  2.5266 -  Say Y here if you want to be able to load driver modules to support
  2.5267 -  other non-standard types of parallel ports. This causes a
  2.5268 -  performance loss, so most people say N.
  2.5269 -
  2.5270 -Amiga built-in parallel port support
  2.5271 -CONFIG_PARPORT_AMIGA
  2.5272 -  Say Y here if you need support for the parallel port hardware on
  2.5273 -  Amiga machines. This code is also available as a module (say M),
  2.5274 -  called parport_amiga.o. If in doubt, saying N is the safe plan.
  2.5275 -
  2.5276 -Atari built-in parallel port support
  2.5277 -CONFIG_PARPORT_ATARI
  2.5278 -  Say Y here if you need support for the parallel port hardware on
  2.5279 -  Atari machines. This code is also available as a module (say M),
  2.5280 -  called parport_atari.o. If in doubt, saying N is the safe plan.
  2.5281 -
  2.5282 -Multiface III parallel port support
  2.5283 -CONFIG_PARPORT_MFC3
  2.5284 -  Say Y here if you need parallel port support for the MFC3 card.
  2.5285 -  This code is also available as a module (say M), called
  2.5286 -  parport_mfc3.o. If in doubt, saying N is the safe plan.
  2.5287 -
  2.5288 -Support IEEE 1284 status readback
  2.5289 -CONFIG_PRINTER_READBACK
  2.5290 -  If you have a device on your parallel port that support this
  2.5291 -  protocol, this option will allow the device to report its status. It
  2.5292 -  is safe to say Y.
  2.5293 -
  2.5294 -IEEE 1284 transfer modes
  2.5295 -CONFIG_PARPORT_1284
  2.5296 -  If you have a printer that supports status readback or device ID, or
  2.5297 -  want to use a device that uses enhanced parallel port transfer modes
  2.5298 -  such as EPP and ECP, say Y here to enable advanced IEEE 1284
  2.5299 -  transfer modes. Also say Y if you want device ID information to
  2.5300 -  appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
  2.5301 -
  2.5302 -Enable loadable module support
  2.5303 -CONFIG_MODULES
  2.5304 -  Kernel modules are small pieces of compiled code which can be
  2.5305 -  inserted in or removed from the running kernel, using the programs
  2.5306 -  insmod and rmmod. This is described in the file
  2.5307 -  <file:Documentation/modules.txt>, including the fact that you have
  2.5308 -  to say "make modules" in order to compile the modules that you chose
  2.5309 -  during kernel configuration.  Modules can be device drivers, file
  2.5310 -  systems, binary executable formats, and so on. If you think that you
  2.5311 -  may want to make use of modules with this kernel in the future, then
  2.5312 -  say Y here.  If unsure, say Y.
  2.5313 -
  2.5314 -Set version information on all symbols for modules
  2.5315 -CONFIG_MODVERSIONS
  2.5316 -  Usually, modules have to be recompiled whenever you switch to a new
  2.5317 -  kernel.  Saying Y here makes it possible, and safe, to use the
  2.5318 -  same modules even after compiling a new kernel; this requires the
  2.5319 -  program modprobe. All the software needed for module support is in
  2.5320 -  the modutils package (check the file <file:Documentation/Changes>
  2.5321 -  for location and latest version).  NOTE: if you say Y here but don't
  2.5322 -  have the program genksyms (which is also contained in the above
  2.5323 -  mentioned modutils package), then the building of your kernel will
  2.5324 -  fail.  If you are going to use modules that are generated from
  2.5325 -  non-kernel sources, you would benefit from this option.  Otherwise
  2.5326 -  it's not that important.  So, N ought to be a safe bet.
  2.5327 -
  2.5328 -Kernel module loader support
  2.5329 -CONFIG_KMOD
  2.5330 -  Normally when you have selected some drivers and/or file systems to
  2.5331 -  be created as loadable modules, you also have the responsibility to
  2.5332 -  load the corresponding modules (using the programs insmod or
  2.5333 -  modprobe) before you can use them. If you say Y here however, the
  2.5334 -  kernel will be able to load modules for itself: when a part of the
  2.5335 -  kernel needs a module, it runs modprobe with the appropriate
  2.5336 -  arguments, thereby loading the module if it is available. (This is a
  2.5337 -  replacement for kerneld.) Say Y here and read about configuring it
  2.5338 -  in <file:Documentation/kmod.txt>.
  2.5339 -
  2.5340 -ARP daemon support
  2.5341 -CONFIG_ARPD
  2.5342 -  Normally, the kernel maintains an internal cache which maps IP
  2.5343 -  addresses to hardware addresses on the local network, so that
  2.5344 -  Ethernet/Token Ring/ etc. frames are sent to the proper address on
  2.5345 -  the physical networking layer. For small networks having a few
  2.5346 -  hundred directly connected hosts or less, keeping this address
  2.5347 -  resolution (ARP) cache inside the kernel works well. However,
  2.5348 -  maintaining an internal ARP cache does not work well for very large
  2.5349 -  switched networks, and will use a lot of kernel memory if TCP/IP
  2.5350 -  connections are made to many machines on the network.
  2.5351 -
  2.5352 -  If you say Y here, the kernel's internal ARP cache will never grow
  2.5353 -  to more than 256 entries (the oldest entries are expired in a LIFO
  2.5354 -  manner) and communication will be attempted with the user space ARP
  2.5355 -  daemon arpd. Arpd then answers the address resolution request either
  2.5356 -  from its own cache or by asking the net.
  2.5357 -
  2.5358 -  This code is experimental and also obsolete. If you want to use it,
  2.5359 -  you need to find a version of the daemon arpd on the net somewhere,
  2.5360 -  and you should also say Y to "Kernel/User network link driver",
  2.5361 -  below. If unsure, say N.
  2.5362 -
  2.5363 -TCP/IP networking
  2.5364 -CONFIG_INET
  2.5365 -  These are the protocols used on the Internet and on most local
  2.5366 -  Ethernets. It is highly recommended to say Y here (this will enlarge
  2.5367 -  your kernel by about 144 KB), since some programs (e.g. the X window
  2.5368 -  system) use TCP/IP even if your machine is not connected to any
  2.5369 -  other computer. You will get the so-called loopback device which
  2.5370 -  allows you to ping yourself (great fun, that!).
  2.5371 -
  2.5372 -  For an excellent introduction to Linux networking, please read the
  2.5373 -  NET-3-HOWTO, available from
  2.5374 -  <http://www.tldp.org/docs.html#howto>.
  2.5375 -
  2.5376 -  This option is also necessary if you want to use the full power of
  2.5377 -  term (term is a program which gives you almost full Internet
  2.5378 -  connectivity if you have a regular dial up shell account on some
  2.5379 -  Internet connected Unix computer; for more information, read
  2.5380 -  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
  2.5381 -
  2.5382 -  If you say Y here and also to "/proc file system support" and
  2.5383 -  "Sysctl support" below, you can change various aspects of the
  2.5384 -  behaviour of the TCP/IP code by writing to the (virtual) files in
  2.5385 -  /proc/sys/net/ipv4/*; the options are explained in the file
  2.5386 -  <file:Documentation/networking/ip-sysctl.txt>.
  2.5387 -
  2.5388 -  Short answer: say Y.
  2.5389 -
  2.5390 -IP multicasting
  2.5391 -CONFIG_IP_MULTICAST
  2.5392 -  This is code for addressing several networked computers at once,
  2.5393 -  enlarging your kernel by about 2 KB. You need multicasting if you
  2.5394 -  intend to participate in the MBONE, a high bandwidth network on top
  2.5395 -  of the Internet which carries audio and video broadcasts. More
  2.5396 -  information about the MBONE is on the WWW at
  2.5397 -  <http://www-itg.lbl.gov/mbone/>. Information about the multicast
  2.5398 -  capabilities of the various network cards is contained in
  2.5399 -  <file:Documentation/networking/multicast.txt>. For most people, it's
  2.5400 -  safe to say N.
  2.5401 -
  2.5402 -Advanced router
  2.5403 -CONFIG_IP_ADVANCED_ROUTER
  2.5404 -  If you intend to run your Linux box mostly as a router, i.e. as a
  2.5405 -  computer that forwards and redistributes network packets, say Y; you
  2.5406 -  will then be presented with several options that allow more precise
  2.5407 -  control about the routing process.
  2.5408 -
  2.5409 -  The answer to this question won't directly affect the kernel:
  2.5410 -  answering N will just cause the configurator to skip all the
  2.5411 -  questions about advanced routing.
  2.5412 -
  2.5413 -  Note that your box can only act as a router if you enable IP
  2.5414 -  forwarding in your kernel; you can do that by saying Y to "/proc
  2.5415 -  file system support" and "Sysctl support" below and executing the
  2.5416 -  line
  2.5417 -
  2.5418 -    echo "1" > /proc/sys/net/ipv4/ip_forward
  2.5419 -
  2.5420 -  at boot time after the /proc file system has been mounted.
  2.5421 -
  2.5422 -  If you turn on IP forwarding, you will also get the rp_filter, which
  2.5423 -  automatically rejects incoming packets if the routing table entry
  2.5424 -  for their source address doesn't match the network interface they're
  2.5425 -  arriving on. This has security advantages because it prevents the
  2.5426 -  so-called IP spoofing, however it can pose problems if you use
  2.5427 -  asymmetric routing (packets from you to a host take a different path
  2.5428 -  than packets from that host to you) or if you operate a non-routing
  2.5429 -  host which has several IP addresses on different interfaces. To turn
  2.5430 -  rp_filter off use:
  2.5431 -
  2.5432 -        echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
  2.5433 -  or
  2.5434 -        echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
  2.5435 -
  2.5436 -  If unsure, say N here.
  2.5437 -
  2.5438 -Policy routing
  2.5439 -CONFIG_IP_MULTIPLE_TABLES
  2.5440 -  Normally, a router decides what to do with a received packet based
  2.5441 -  solely on the packet's final destination address. If you say Y here,
  2.5442 -  the Linux router will also be able to take the packet's source
  2.5443 -  address into account. Furthermore, if you also say Y to "Use TOS
  2.5444 -  value as routing key" below, the TOS (Type-Of-Service) field of the
  2.5445 -  packet can be used for routing decisions as well. In addition, if
  2.5446 -  you say Y here and to "Fast network address translation" below,
  2.5447 -  the router will also be able to modify source and destination
  2.5448 -  addresses of forwarded packets.
  2.5449 -
  2.5450 -  If you are interested in this, please see the preliminary
  2.5451 -  documentation at <http://www.compendium.com.ar/policy-routing.txt>
  2.5452 -  and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
  2.5453 -  You will need supporting software from
  2.5454 -  <ftp://ftp.inr.ac.ru/ip-routing/>.
  2.5455 -
  2.5456 -  If unsure, say N.
  2.5457 -
  2.5458 -Equal cost multipath
  2.5459 -CONFIG_IP_ROUTE_MULTIPATH
  2.5460 -  Normally, the routing tables specify a single action to be taken in
  2.5461 -  a deterministic manner for a given packet. If you say Y here
  2.5462 -  however, it becomes possible to attach several actions to a packet
  2.5463 -  pattern, in effect specifying several alternative paths to travel
  2.5464 -  for those packets. The router considers all these paths to be of
  2.5465 -  equal "cost" and chooses one of them in a non-deterministic fashion
  2.5466 -  if a matching packet arrives.
  2.5467 -
  2.5468 -Use TOS value as routing key
  2.5469 -CONFIG_IP_ROUTE_TOS
  2.5470 -  The header of every IP packet carries a TOS (Type Of Service) value
  2.5471 -  with which the packet requests a certain treatment, e.g. low
  2.5472 -  latency (for interactive traffic), high throughput, or high
  2.5473 -  reliability.  If you say Y here, you will be able to specify
  2.5474 -  different routes for packets with different TOS values.
  2.5475 -
  2.5476 -Use netfilter MARK value as routing key
  2.5477 -CONFIG_IP_ROUTE_FWMARK
  2.5478 -  If you say Y here, you will be able to specify different routes for
  2.5479 -  packets with different mark values (see iptables(8), MARK target).
  2.5480 -
  2.5481 -Verbose route monitoring
  2.5482 -CONFIG_IP_ROUTE_VERBOSE
  2.5483 -  If you say Y here, which is recommended, then the kernel will print
  2.5484 -  verbose messages regarding the routing, for example warnings about
  2.5485 -  received packets which look strange and could be evidence of an
  2.5486 -  attack or a misconfigured system somewhere. The information is
  2.5487 -  handled by the klogd daemon which is responsible for kernel messages
  2.5488 -  ("man klogd").
  2.5489 -
  2.5490 -Large routing tables
  2.5491 -CONFIG_IP_ROUTE_LARGE_TABLES
  2.5492 -  If you have routing zones that grow to more than about 64 entries,
  2.5493 -  you may want to say Y here to speed up the routing process.
  2.5494 -
  2.5495 -Fast network address translation
  2.5496 -CONFIG_IP_ROUTE_NAT
  2.5497 -  If you say Y here, your router will be able to modify source and
  2.5498 -  destination addresses of packets that pass through it, in a manner
  2.5499 -  you specify.  General information about Network Address Translation
  2.5500 -  can be gotten from the document
  2.5501 -  <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
  2.5502 -
  2.5503 -Kernel level IP autoconfiguration
  2.5504 -CONFIG_IP_PNP
  2.5505 -  This enables automatic configuration of IP addresses of devices and
  2.5506 -  of the routing table during kernel boot, based on either information
  2.5507 -  supplied on the kernel command line or by BOOTP or RARP protocols.
  2.5508 -  You need to say Y only for diskless machines requiring network
  2.5509 -  access to boot (in which case you want to say Y to "Root file system
  2.5510 -  on NFS" as well), because all other machines configure the network
  2.5511 -  in their startup scripts.
  2.5512 -
  2.5513 -BOOTP support
  2.5514 -CONFIG_IP_PNP_BOOTP
  2.5515 -  If you want your Linux box to mount its whole root file system (the
  2.5516 -  one containing the directory /) from some other computer over the
  2.5517 -  net via NFS and you want the IP address of your computer to be
  2.5518 -  discovered automatically at boot time using the BOOTP protocol (a
  2.5519 -  special protocol designed for doing this job), say Y here. In case
  2.5520 -  the boot ROM of your network card was designed for booting Linux and
  2.5521 -  does BOOTP itself, providing all necessary information on the kernel
  2.5522 -  command line, you can say N here. If unsure, say Y. Note that if you
  2.5523 -  want to use BOOTP, a BOOTP server must be operating on your network.
  2.5524 -  Read <file:Documentation/nfsroot.txt> for details.
  2.5525 -
  2.5526 -DHCP support
  2.5527 -CONFIG_IP_PNP_DHCP
  2.5528 -  If you want your Linux box to mount its whole root file system (the
  2.5529 -  one containing the directory /) from some other computer over the
  2.5530 -  net via NFS and you want the IP address of your computer to be
  2.5531 -  discovered automatically at boot time using the DHCP protocol (a
  2.5532 -  special protocol designed for doing this job), say Y here. In case
  2.5533 -  the boot ROM of your network card was designed for booting Linux and
  2.5534 -  does DHCP itself, providing all necessary information on the kernel
  2.5535 -  command line, you can say N here.
  2.5536 -
  2.5537 -  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
  2.5538 -  must be operating on your network.  Read
  2.5539 -  <file:Documentation/nfsroot.txt> for details.
  2.5540 -
  2.5541 -RARP support
  2.5542 -CONFIG_IP_PNP_RARP
  2.5543 -  If you want your Linux box to mount its whole root file system (the
  2.5544 -  one containing the directory /) from some other computer over the
  2.5545 -  net via NFS and you want the IP address of your computer to be
  2.5546 -  discovered automatically at boot time using the RARP protocol (an
  2.5547 -  older protocol which is being obsoleted by BOOTP and DHCP), say Y
  2.5548 -  here. Note that if you want to use RARP, a RARP server must be
  2.5549 -  operating on your network. Read <file:Documentation/nfsroot.txt> for
  2.5550 -  details.
  2.5551 -
  2.5552 -IP tunneling
  2.5553 -CONFIG_NET_IPIP
  2.5554 -  Tunneling means encapsulating data of one protocol type within
  2.5555 -  another protocol and sending it over a channel that understands the
  2.5556 -  encapsulating protocol. This particular tunneling driver implements
  2.5557 -  encapsulation of IP within IP, which sounds kind of pointless, but
  2.5558 -  can be useful if you want to make your (or some other) machine
  2.5559 -  appear on a different network than it physically is, or to use
  2.5560 -  mobile-IP facilities (allowing laptops to seamlessly move between
  2.5561 -  networks without changing their IP addresses; check out
  2.5562 -  <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
  2.5563 -
  2.5564 -  Saying Y to this option will produce two modules ( = code which can
  2.5565 -  be inserted in and removed from the running kernel whenever you
  2.5566 -  want). Most people won't need this and can say N.
  2.5567 -
  2.5568 -  This driver is also available as a module ( = code which can be
  2.5569 -  inserted in and removed from the running kernel whenever you want).
  2.5570 -  If you want to compile it as a module, say M here and read
  2.5571 -  <file:Documentation/modules.txt>. The module will be called
  2.5572 -  ipip.o
  2.5573 -
  2.5574 -GRE tunnels over IP
  2.5575 -CONFIG_NET_IPGRE
  2.5576 -  Tunneling means encapsulating data of one protocol type within
  2.5577 -  another protocol and sending it over a channel that understands the
  2.5578 -  encapsulating protocol. This particular tunneling driver implements
  2.5579 -  GRE (Generic Routing Encapsulation) and at this time allows
  2.5580 -  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  2.5581 -  This driver is useful if the other endpoint is a Cisco router: Cisco
  2.5582 -  likes GRE much better than the other Linux tunneling driver ("IP
  2.5583 -  tunneling" above). In addition, GRE allows multicast redistribution
  2.5584 -  through the tunnel.
  2.5585 -
  2.5586 -  This driver is also available as a module ( = code which can be
  2.5587 -  inserted in and removed from the running kernel whenever you want).
  2.5588 -  If you want to compile it as a module, say M here and read
  2.5589 -  <file:Documentation/modules.txt>. The module will be called
  2.5590 -  ip_gre.o
  2.5591 -
  2.5592 -Broadcast GRE over IP
  2.5593 -CONFIG_NET_IPGRE_BROADCAST
  2.5594 -  One application of GRE/IP is to construct a broadcast WAN (Wide Area
  2.5595 -  Network), which looks like a normal Ethernet LAN (Local Area
  2.5596 -  Network), but can be distributed all over the Internet. If you want
  2.5597 -  to do that, say Y here and to "IP multicast routing" below.
  2.5598 -
  2.5599 -IP multicast routing
  2.5600 -CONFIG_IP_MROUTE
  2.5601 -  This is used if you want your machine to act as a router for IP
  2.5602 -  packets that have several destination addresses. It is needed on the
  2.5603 -  MBONE, a high bandwidth network on top of the Internet which carries
  2.5604 -  audio and video broadcasts. In order to do that, you would most
  2.5605 -  likely run the program mrouted. Information about the multicast
  2.5606 -  capabilities of the various network cards is contained in
  2.5607 -  <file:Documentation/networking/multicast.txt>. If you haven't heard
  2.5608 -  about it, you don't need it.
  2.5609 -
  2.5610 -PIM-SM version 1 support
  2.5611 -CONFIG_IP_PIMSM_V1
  2.5612 -  Kernel side support for Sparse Mode PIM (Protocol Independent
  2.5613 -  Multicast) version 1. This multicast routing protocol is used widely
  2.5614 -  because Cisco supports it. You need special software to use it
  2.5615 -  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
  2.5616 -  information about PIM.
  2.5617 -
  2.5618 -  Say Y if you want to use PIM-SM v1. Note that you can say N here if
  2.5619 -  you just want to use Dense Mode PIM.
  2.5620 -
  2.5621 -PIM-SM version 2 support
  2.5622 -CONFIG_IP_PIMSM_V2
  2.5623 -  Kernel side support for Sparse Mode PIM version 2. In order to use
  2.5624 -  this, you need an experimental routing daemon supporting it (pimd or
  2.5625 -  gated-5). This routing protocol is not used widely, so say N unless
  2.5626 -  you want to play with it.
  2.5627 -
  2.5628 -Unix domain sockets
  2.5629 -CONFIG_UNIX
  2.5630 -  If you say Y here, you will include support for Unix domain sockets;
  2.5631 -  sockets are the standard Unix mechanism for establishing and
  2.5632 -  accessing network connections.  Many commonly used programs such as
  2.5633 -  the X Window system and syslog use these sockets even if your
  2.5634 -  machine is not connected to any network.  Unless you are working on
  2.5635 -  an embedded system or something similar, you therefore definitely
  2.5636 -  want to say Y here.
  2.5637 -
  2.5638 -  However, the socket support is also available as a module ( = code
  2.5639 -  which can be inserted in and removed from the running kernel
  2.5640 -  whenever you want).  If you want to compile it as a module, say M
  2.5641 -  here and read <file:Documentation/modules.txt>. The module will be
  2.5642 -  called unix.o.  If you try building this as a module and you have
  2.5643 -  said Y to "Kernel module loader support" above, be sure to add
  2.5644 -  'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
  2.5645 -  several important services won't work correctly if you say M here
  2.5646 -  and then neglect to load the module.
  2.5647 -
  2.5648 -  Say Y unless you know what you are doing.
  2.5649 -
  2.5650 -The IPv6 protocol
  2.5651 -CONFIG_IPV6
  2.5652 -  This is experimental support for the next version of the Internet
  2.5653 -  Protocol: IP version 6 (also called IPng "IP next generation").
  2.5654 -  Features of this new protocol include: expanded address space,
  2.5655 -  authentication and privacy, and seamless interoperability with the
  2.5656 -  current version of IP (IP version 4). For general information about
  2.5657 -  IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
  2.5658 -  for specific information about IPv6 under Linux read the HOWTO at
  2.5659 -  <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
  2.5660 -  in the kernel source.
  2.5661 -
  2.5662 -  If you want to use IPv6, please upgrade to the newest net-tools as
  2.5663 -  given in <file:Documentation/Changes>. You will still be able to do
  2.5664 -  regular IPv4 networking as well.
  2.5665 -
  2.5666 -  This protocol support is also available as a module ( = code which
  2.5667 -  can be inserted in and removed from the running kernel whenever you
  2.5668 -  want). The module will be called ipv6.o. If you want to compile it
  2.5669 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.5670 -
  2.5671 -  It is safe to say N here for now.
  2.5672 -
  2.5673 -Kernel httpd acceleration
  2.5674 -CONFIG_KHTTPD
  2.5675 -  The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
  2.5676 -  server built into the kernel. It is limited since it can only serve
  2.5677 -  files from the file system and cannot deal with executable content
  2.5678 -  such as CGI scripts. Serving files is sped up if you use kHTTPd.
  2.5679 -  If kHTTPd is not able to fulfill a request, it can transparently
  2.5680 -  pass it through to a user space web server such as apache.
  2.5681 -
  2.5682 -  Saying "M" here builds the kHTTPd module; this is NOT enough to have
  2.5683 -  a working kHTTPd. For safety reasons, the module has to be activated
  2.5684 -  by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
  2.5685 -  module.
  2.5686 -
  2.5687 -  Before using this, read the README in net/khttpd !
  2.5688 -
  2.5689 -  The kHTTPd is experimental. Be careful when using it on a production
  2.5690 -  machine. Also note that kHTTPd doesn't support virtual servers yet.
  2.5691 -
  2.5692 -The IPX protocol
  2.5693 -CONFIG_IPX
  2.5694 -  This is support for the Novell networking protocol, IPX, commonly
  2.5695 -  used for local networks of Windows machines.  You need it if you
  2.5696 -  want to access Novell NetWare file or print servers using the Linux
  2.5697 -  Novell client ncpfs (available from
  2.5698 -  <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
  2.5699 -  within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
  2.5700 -  available from <http://www.tldp.org/docs.html#howto>).  In order
  2.5701 -  to do the former, you'll also have to say Y to "NCP file system
  2.5702 -  support", below.
  2.5703 -
  2.5704 -  IPX is similar in scope to IP, while SPX, which runs on top of IPX,
  2.5705 -  is similar to TCP. There is also experimental support for SPX in
  2.5706 -  Linux (see "SPX networking", below).
  2.5707 -
  2.5708 -  To turn your Linux box into a fully featured NetWare file server and
  2.5709 -  IPX router, say Y here and fetch either lwared from
  2.5710 -  <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
  2.5711 -  mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
  2.5712 -  information, read the IPX-HOWTO available from
  2.5713 -  <http://www.tldp.org/docs.html#howto>.
  2.5714 -
  2.5715 -  General information about how to connect Linux, Windows machines and
  2.5716 -  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  2.5717 -
  2.5718 -  The IPX driver would enlarge your kernel by about 16 KB. This driver
  2.5719 -  is also available as a module ( = code which can be inserted in and
  2.5720 -  removed from the running kernel whenever you want).  The module will
  2.5721 -  be called ipx.o.  If you want to compile it as a module, say M here
  2.5722 -  and read <file:Documentation/modules.txt>.  Unless you want to
  2.5723 -  integrate your Linux box with a local Novell network, say N.
  2.5724 -
  2.5725 -Full internal IPX network
  2.5726 -CONFIG_IPX_INTERN
  2.5727 -  Every IPX network has an address that identifies it. Sometimes it is
  2.5728 -  useful to give an IPX "network" address to your Linux box as well
  2.5729 -  (for example if your box is acting as a file server for different
  2.5730 -  IPX networks: it will then be accessible from everywhere using the
  2.5731 -  same address). The way this is done is to create a virtual internal
  2.5732 -  "network" inside your box and to assign an IPX address to this
  2.5733 -  network. Say Y here if you want to do this; read the IPX-HOWTO at
  2.5734 -  <http://www.tldp.org/docs.html#howto> for details.
  2.5735 -
  2.5736 -  The full internal IPX network enables you to allocate sockets on
  2.5737 -  different virtual nodes of the internal network. This is done by
  2.5738 -  evaluating the field sipx_node of the socket address given to the
  2.5739 -  bind call. So applications should always initialize the node field
  2.5740 -  to 0 when binding a socket on the primary network. In this case the
  2.5741 -  socket is assigned the default node that has been given to the
  2.5742 -  kernel when the internal network was created. By enabling the full
  2.5743 -  internal IPX network the cross-forwarding of packets targeted at
  2.5744 -  'special' sockets to sockets listening on the primary network is
  2.5745 -  disabled. This might break existing applications, especially RIP/SAP
  2.5746 -  daemons. A RIP/SAP daemon that works well with the full internal net
  2.5747 -  can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
  2.5748 -
  2.5749 -  If you don't know what you are doing, say N.
  2.5750 -
  2.5751 -#(We're told this will come back someday)
  2.5752 -
  2.5753 -SPX networking
  2.5754 -CONFIG_SPX
  2.5755 -  * Orphaned entry retained 20 April 2001 by Petr Vandrovec     *
  2.5756 -  * If you read this note from the configurator, please contact *
  2.5757 -  * the Configure.help maintainers.                             *
  2.5758 -  The Sequenced Packet eXchange protocol is a transport layer protocol
  2.5759 -  built on top of IPX. It is used in Novell NetWare systems for
  2.5760 -  client-server applications and is similar to TCP (which runs on top
  2.5761 -  of IP).
  2.5762 -
  2.5763 -  Note that Novell NetWare file sharing does not use SPX; it uses a
  2.5764 -  protocol called NCP, for which separate Linux support is available
  2.5765 -  ("NCP file system support" below for the client side, and the user
  2.5766 -  space programs lwared or mars_nwe for the server side).
  2.5767 -
  2.5768 -  Say Y here if you have use for SPX; read the IPX-HOWTO at
  2.5769 -  <http://www.tldp.org/docs.html#howto> for details.
  2.5770 -
  2.5771 -  This driver is also available as a module ( = code which can be
  2.5772 -  inserted in and removed from the running kernel whenever you want).
  2.5773 -  The module will be called af_spx.o. If you want to compile it as a
  2.5774 -  module, say M here and read <file:Documentation/modules.txt>.
  2.5775 -
  2.5776 -DECnet networking
  2.5777 -CONFIG_DECNET
  2.5778 -  The DECnet networking protocol was used in many products made by
  2.5779 -  Digital (now Compaq).  It provides reliable stream and sequenced
  2.5780 -  packet communications over which run a variety of services similar
  2.5781 -  to those which run over TCP/IP.
  2.5782 -
  2.5783 -  To find some tools to use with the kernel layer support, please
  2.5784 -  look at Patrick Caulfield's web site:
  2.5785 -  <http://linux.dreamtime.org/decnet/>.
  2.5786 -
  2.5787 -  More detailed documentation is available in
  2.5788 -  <file:Documentation/networking/decnet.txt>.
  2.5789 -
  2.5790 -  Be sure to say Y to "/proc file system support" and "Sysctl support"
  2.5791 -  below when using DECnet, since you will need sysctl support to aid
  2.5792 -  in configuration at run time.
  2.5793 -
  2.5794 -  The DECnet code is also available as a module ( = code which can be
  2.5795 -  inserted in and removed from the running kernel whenever you want).
  2.5796 -  The module is called decnet.o.
  2.5797 -
  2.5798 -DECnet SIOCFIGCONF support
  2.5799 -CONFIG_DECNET_SIOCGIFCONF
  2.5800 -  This option should only be turned on if you are really sure that
  2.5801 -  you know what you are doing. It can break other applications which
  2.5802 -  use this system call and the proper way to get the information
  2.5803 -  provided by this call is to use rtnetlink.
  2.5804 -
  2.5805 -  If unsure, say N.
  2.5806 -
  2.5807 -DECnet router support
  2.5808 -CONFIG_DECNET_ROUTER
  2.5809 -  Add support for turning your DECnet Endnode into a level 1 or 2
  2.5810 -  router.  This is an unfinished option for developers only.  If you
  2.5811 -  do say Y here, then make sure that you also say Y to "Kernel/User
  2.5812 -  network link driver", "Routing messages" and "Network packet
  2.5813 -  filtering".  The first two are required to allow configuration via
  2.5814 -  rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
  2.5815 -  from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
  2.5816 -  will be required for the forthcoming routing daemon to work.
  2.5817 -
  2.5818 -  See <file:Documentation/networking/decnet.txt> for more information.
  2.5819 -
  2.5820 -Use FWMARK value as DECnet routing key
  2.5821 -CONFIG_DECNET_ROUTE_FWMARK
  2.5822 -  If you say Y here, you will be able to specify different routes for
  2.5823 -  packets with different FWMARK ("firewalling mark") values
  2.5824 -  (see ipchains(8), "-m" argument).
  2.5825 -
  2.5826 -AppleTalk interfaces support
  2.5827 -CONFIG_DEV_APPLETALK
  2.5828 -  AppleTalk is the protocol that Apple computers can use to communicate
  2.5829 -  on a network.  If your Linux box is connected to such a network, and wish
  2.5830 -  to do IP over it, or you have a LocalTalk card and wish to use it to
  2.5831 -  connect to the AppleTalk network, say Y.
  2.5832 -
  2.5833 -AppleTalk protocol support
  2.5834 -CONFIG_ATALK
  2.5835 -  AppleTalk is the protocol that Apple computers can use to communicate
  2.5836 -  on a network.  If your Linux box is connected to such a network and you
  2.5837 -  wish to connect to it, say Y.  You will need to use the netatalk package
  2.5838 -  so that your Linux box can act as a print and file server for Macs as
  2.5839 -  well as access AppleTalk printers.  Check out
  2.5840 -  <http://www.zettabyte.net/netatalk/> on the WWW for details.
  2.5841 -  EtherTalk is the name used for AppleTalk over Ethernet and the
  2.5842 -  cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
  2.5843 -  network using serial links.  EtherTalk and LocalTalk are fully
  2.5844 -  supported by Linux.
  2.5845 -
  2.5846 -  General information about how to connect Linux, Windows machines and
  2.5847 -  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.  The
  2.5848 -  NET-3-HOWTO, available from
  2.5849 -  <http://www.tldp.org/docs.html#howto>, contains valuable
  2.5850 -  information as well.
  2.5851 -
  2.5852 -  This driver is also available as a module ( = code which can be
  2.5853 -  inserted in and removed from the running kernel whenever you want).
  2.5854 -  The module is called appletalk.o.  If you want to compile it as a
  2.5855 -  module, say M here and read <file:Documentation/modules.txt>.  You
  2.5856 -  almost certainly want to compile it as a module so you can restart
  2.5857 -  your AppleTalk stack without rebooting your machine.  I hear that
  2.5858 -  the GNU boycott of Apple is over, so even politically correct people
  2.5859 -  are allowed to say Y here.
  2.5860 -
  2.5861 -AppleTalk-IP driver support
  2.5862 -CONFIG_IPDDP
  2.5863 -  This allows IP networking for users who only have AppleTalk
  2.5864 -  networking available. This feature is experimental. With this
  2.5865 -  driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
  2.5866 -  box is stuck on an AppleTalk only network) or decapsulate (e.g. if
  2.5867 -  you want your Linux box to act as an Internet gateway for a zoo of
  2.5868 -  AppleTalk connected Macs). Please see the file
  2.5869 -  <file:Documentation/networking/ipddp.txt> for more information.
  2.5870 -
  2.5871 -  If you say Y here, the AppleTalk-IP support will be compiled into
  2.5872 -  the kernel. In this case, you can either use encapsulation or
  2.5873 -  decapsulation, but not both. With the following two questions, you
  2.5874 -  decide which one you want.
  2.5875 -
  2.5876 -  If you say M here, the AppleTalk-IP support will be compiled as a
  2.5877 -  module ( = code which can be inserted in and removed from the
  2.5878 -  running kernel whenever you want, read
  2.5879 -  <file:Documentation/modules.txt>).  The module is called ipddp.o.
  2.5880 -  In this case, you will be able to use both encapsulation and
  2.5881 -  decapsulation simultaneously, by loading two copies of the module
  2.5882 -  and specifying different values for the module option ipddp_mode.
  2.5883 -
  2.5884 -IP to AppleTalk-IP Encapsulation support
  2.5885 -CONFIG_IPDDP_ENCAP
  2.5886 -  If you say Y here, the AppleTalk-IP code will be able to encapsulate
  2.5887 -  IP packets inside AppleTalk frames; this is useful if your Linux box
  2.5888 -  is stuck on an AppleTalk network (which hopefully contains a
  2.5889 -  decapsulator somewhere). Please see
  2.5890 -  <file:Documentation/networking/ipddp.txt> for more information. If
  2.5891 -  you said Y to "AppleTalk-IP driver support" above and you say Y
  2.5892 -  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
  2.5893 -  support", below.
  2.5894 -
  2.5895 -AppleTalk-IP to IP Decapsulation support
  2.5896 -CONFIG_IPDDP_DECAP
  2.5897 -  If you say Y here, the AppleTalk-IP code will be able to decapsulate
  2.5898 -  AppleTalk-IP frames to IP packets; this is useful if you want your
  2.5899 -  Linux box to act as an Internet gateway for an AppleTalk network.
  2.5900 -  Please see <file:Documentation/networking/ipddp.txt> for more
  2.5901 -  information.  If you said Y to "AppleTalk-IP driver support" above
  2.5902 -  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
  2.5903 -  Encapsulation support", above.
  2.5904 -
  2.5905 -Apple/Farallon LocalTalk PC card support
  2.5906 -CONFIG_LTPC
  2.5907 -  This allows you to use the AppleTalk PC card to connect to LocalTalk
  2.5908 -  networks. The card is also known as the Farallon PhoneNet PC card.
  2.5909 -  If you are in doubt, this card is the one with the 65C02 chip on it.
  2.5910 -  You also need version 1.3.3 or later of the netatalk package.
  2.5911 -  This driver is experimental, which means that it may not work.
  2.5912 -  See the file <file:Documentation/networking/ltpc.txt>.
  2.5913 -
  2.5914 -  This driver is also available as a module ( = code which can be
  2.5915 -  inserted in and removed from the running kernel whenever you want).
  2.5916 -  If you want to compile it as a module, say M here and read
  2.5917 -  <file:Documentation/modules.txt>. The module will be called
  2.5918 -  ltpc.o
  2.5919 -
  2.5920 -COPS LocalTalk PC card support
  2.5921 -CONFIG_COPS
  2.5922 -  This allows you to use COPS AppleTalk cards to connect to LocalTalk
  2.5923 -  networks. You also need version 1.3.3 or later of the netatalk
  2.5924 -  package. This driver is experimental, which means that it may not
  2.5925 -  work. This driver will only work if you choose "AppleTalk DDP"
  2.5926 -  networking support, above.
  2.5927 -  Please read the file <file:Documentation/networking/cops.txt>.
  2.5928 -
  2.5929 -  This driver is also available as a module ( = code which can be
  2.5930 -  inserted in and removed from the running kernel whenever you want).
  2.5931 -  If you want to compile it as a module, say M here and read
  2.5932 -  <file:Documentation/modules.txt>. The module will be called
  2.5933 -  cops.o
  2.5934 -
  2.5935 -Dayna firmware support
  2.5936 -CONFIG_COPS_DAYNA
  2.5937 -  Support COPS compatible cards with Dayna style firmware (Dayna
  2.5938 -  DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
  2.5939 -  III, Farallon PhoneNET PC II).
  2.5940 -
  2.5941 -Tangent firmware support
  2.5942 -CONFIG_COPS_TANGENT
  2.5943 -  Support COPS compatible cards with Tangent style firmware (Tangent
  2.5944 -  ATB_II, Novell NL-1000, Daystar Digital LT-200.
  2.5945 -
  2.5946 -Amateur Radio support
  2.5947 -CONFIG_HAMRADIO
  2.5948 -  If you want to connect your Linux box to an amateur radio, answer Y
  2.5949 -  here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
  2.5950 -  the AX25-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
  2.5951 -
  2.5952 -  Note that the answer to this question won't directly affect the
  2.5953 -  kernel: saying N will just cause the configurator to skip all
  2.5954 -  the questions about amateur radio.
  2.5955 -
  2.5956 -Amateur Radio AX.25 Level 2 protocol
  2.5957 -CONFIG_AX25
  2.5958 -  This is the protocol used for computer communication over amateur
  2.5959 -  radio. It is either used by itself for point-to-point links, or to
  2.5960 -  carry other protocols such as tcp/ip. To use it, you need a device
  2.5961 -  that connects your Linux box to your amateur radio. You can either
  2.5962 -  use a low speed TNC (a Terminal Node Controller acts as a kind of
  2.5963 -  modem connecting your computer's serial port to your radio's
  2.5964 -  microphone input and speaker output) supporting the KISS protocol or
  2.5965 -  one of the various SCC cards that are supported by the generic Z8530
  2.5966 -  or the DMA SCC driver. Another option are the Baycom modem serial
  2.5967 -  and parallel port hacks or the sound card modem (supported by their
  2.5968 -  own drivers). If you say Y here, you also have to say Y to one of
  2.5969 -  those drivers.
  2.5970 -
  2.5971 -  Information about where to get supporting software for Linux amateur
  2.5972 -  radio as well as information about how to configure an AX.25 port is
  2.5973 -  contained in the AX25-HOWTO, available from
  2.5974 -  <http://www.tldp.org/docs.html#howto>. You might also want to
  2.5975 -  check out the file <file:Documentation/networking/ax25.txt> in the
  2.5976 -  kernel source. More information about digital amateur radio in
  2.5977 -  general is on the WWW at
  2.5978 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  2.5979 -
  2.5980 -  This driver is also available as a module ( = code which can be
  2.5981 -  inserted in and removed from the running kernel whenever you want).
  2.5982 -  The module will be called ax25.o. If you want to compile it as a
  2.5983 -  module, say M here and read <file:Documentation/modules.txt>.
  2.5984 -
  2.5985 -AX.25 DAMA Slave support
  2.5986 -CONFIG_AX25_DAMA_SLAVE
  2.5987 -  DAMA is a mechanism to prevent collisions when doing AX.25
  2.5988 -  networking. A DAMA server (called "master") accepts incoming traffic
  2.5989 -  from clients (called "slaves") and redistributes it to other slaves.
  2.5990 -  If you say Y here, your Linux box will act as a DAMA slave; this is
  2.5991 -  transparent in that you don't have to do any special DAMA
  2.5992 -  configuration. (Linux cannot yet act as a DAMA server.) If unsure,
  2.5993 -  say N.
  2.5994 -
  2.5995 -AX.25 DAMA Master support
  2.5996 -CONFIG_AX25_DAMA_MASTER
  2.5997 -  DAMA is a mechanism to prevent collisions when doing AX.25
  2.5998 -  networking. A DAMA server (called "master") accepts incoming traffic
  2.5999 -  from clients (called "slaves") and redistributes it to other
  2.6000 -  slaves. If you say Y here, your Linux box will act as a DAMA server.
  2.6001 -  If unsure, say N.
  2.6002 -
  2.6003 -Amateur Radio NET/ROM support
  2.6004 -CONFIG_NETROM
  2.6005 -  NET/ROM is a network layer protocol on top of AX.25 useful for
  2.6006 -  routing.
  2.6007 -
  2.6008 -  A comprehensive listing of all the software for Linux amateur radio
  2.6009 -  users as well as information about how to configure an AX.25 port is
  2.6010 -  contained in the AX25-HOWTO, available from
  2.6011 -  <http://www.tldp.org/docs.html#howto>. You also might want to
  2.6012 -  check out the file <file:Documentation/networking/ax25.txt>. More
  2.6013 -  information about digital amateur radio in general is on the WWW at
  2.6014 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  2.6015 -
  2.6016 -  This driver is also available as a module ( = code which can be
  2.6017 -  inserted in and removed from the running kernel whenever you want).
  2.6018 -  The module will be called netrom.o. If you want to compile it as a
  2.6019 -  module, say M here and read <file:Documentation/modules.txt>.
  2.6020 -
  2.6021 -Amateur Radio X.25 PLP (Rose)
  2.6022 -CONFIG_ROSE
  2.6023 -  The Packet Layer Protocol (PLP) is a way to route packets over X.25
  2.6024 -  connections in general and amateur radio AX.25 connections in
  2.6025 -  particular, essentially an alternative to NET/ROM.
  2.6026 -
  2.6027 -  A comprehensive listing of all the software for Linux amateur radio
  2.6028 -  users as well as information about how to configure an AX.25 port is
  2.6029 -  contained in the AX25-HOWTO, available from
  2.6030 -  <http://www.tldp.org/docs.html#howto>.  You also might want to
  2.6031 -  check out the file <file:Documentation/networking/ax25.txt>. More
  2.6032 -  information about digital amateur radio in general is on the WWW at
  2.6033 -  <http://www.tapr.org/tapr/html/pkthome.html>.
  2.6034 -
  2.6035 -  This driver is also available as a module ( = code which can be
  2.6036 -  inserted in and removed from the running kernel whenever you want).
  2.6037 -  The module will be called rose.o. If you want to compile it as a
  2.6038 -  module, say M here and read <file:Documentation/modules.txt>.
  2.6039 -
  2.6040 -Serial port KISS driver for AX.25
  2.6041 -CONFIG_MKISS
  2.6042 -  KISS is a protocol used for the exchange of data between a computer
  2.6043 -  and a Terminal Node Controller (a small embedded system commonly
  2.6044 -  used for networking over AX.25 amateur radio connections; it
  2.6045 -  connects the computer's serial port with the radio's microphone
  2.6046 -  input and speaker output).
  2.6047 -
  2.6048 -  Although KISS is less advanced than the 6pack protocol, it has
  2.6049 -  the advantage that it is already supported by most modern TNCs
  2.6050 -  without the need for a firmware upgrade.
  2.6051 -
  2.6052 -  If you want to compile this driver as a module ( = code which can be
  2.6053 -  inserted in and removed from the running kernel whenever you want),
  2.6054 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6055 -  will be called mkiss.o.
  2.6056 -
  2.6057 -Serial port 6PACK driver for AX.25
  2.6058 -CONFIG_6PACK
  2.6059 -  6pack is a transmission protocol for the data exchange between your
  2.6060 -  PC and your TNC (the Terminal Node Controller acts as a kind of
  2.6061 -  modem connecting your computer's serial port to your radio's
  2.6062 -  microphone input and speaker output). This protocol can be used as
  2.6063 -  an alternative to KISS for networking over AX.25 amateur radio
  2.6064 -  connections, but it has some extended functionality.
  2.6065 -
  2.6066 -  Note that this driver is still experimental and might cause
  2.6067 -  problems. For details about the features and the usage of the
  2.6068 -  driver, read <file:Documentation/networking/6pack.txt>.
  2.6069 -
  2.6070 -  If you want to compile this driver as a module ( = code which can be
  2.6071 -  inserted in and removed from the running kernel whenever you want),
  2.6072 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6073 -  will be called 6pack.o.
  2.6074 -
  2.6075 -BPQ Ethernet driver
  2.6076 -CONFIG_BPQETHER
  2.6077 -  AX.25 is the protocol used for computer communication over amateur
  2.6078 -  radio. If you say Y here, you will be able to send and receive AX.25
  2.6079 -  traffic over Ethernet (also called "BPQ AX.25"), which could be
  2.6080 -  useful if some other computer on your local network has a direct
  2.6081 -  amateur radio connection.
  2.6082 -
  2.6083 -  If you want to compile the driver as a module ( = code which can be
  2.6084 -  inserted in and removed from the running kernel whenever you want),
  2.6085 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6086 -  will be called bpqether.o.
  2.6087 -
  2.6088 -High-speed (DMA) SCC driver for AX.25
  2.6089 -CONFIG_DMASCC
  2.6090 -  This is a driver for high-speed SCC boards, i.e. those supporting
  2.6091 -  DMA on one port. You usually use those boards to connect your
  2.6092 -  computer to an amateur radio modem (such as the WA4DSY 56kbps
  2.6093 -  modem), in order to send and receive AX.25 packet radio network
  2.6094 -  traffic.
  2.6095 -
  2.6096 -  Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
  2.6097 -  PackeTwin, and S5SCC/DMA boards. They are detected automatically.
  2.6098 -  If you have one of these cards, say Y here and read the AX25-HOWTO,
  2.6099 -  available from <http://www.tldp.org/docs.html#howto>.
  2.6100 -
  2.6101 -  This driver can operate multiple boards simultaneously. If you
  2.6102 -  compile it as a module (by saying M instead of Y), it will be called
  2.6103 -  dmascc.o. If you don't pass any parameter to the driver, all
  2.6104 -  possible I/O addresses are probed. This could irritate other devices
  2.6105 -  that are currently not in use. You may specify the list of addresses
  2.6106 -  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
  2.6107 -  kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
  2.6108 -  network interfaces will be called dmascc0 and dmascc1 for the board
  2.6109 -  detected first, dmascc2 and dmascc3 for the second one, and so on.
  2.6110 -
  2.6111 -  Before you configure each interface with ifconfig, you MUST set
  2.6112 -  certain parameters, such as channel access timing, clock mode, and
  2.6113 -  DMA channel. This is accomplished with a small utility program,
  2.6114 -  dmascc_cfg, available at
  2.6115 -  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
  2.6116 -  at least version 1.27 of dmascc_cfg, as older versions will not
  2.6117 -  work with the current driver.
  2.6118 -
  2.6119 -Z8530 SCC driver for AX.25
  2.6120 -CONFIG_SCC
  2.6121 -  These cards are used to connect your Linux box to an amateur radio
  2.6122 -  in order to communicate with other computers. If you want to use
  2.6123 -  this, read <file:Documentation/networking/z8530drv.txt> and the
  2.6124 -  AX25-HOWTO, available from
  2.6125 -  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  2.6126 -  to "Amateur Radio AX.25 Level 2" support.
  2.6127 -
  2.6128 -  If you want to compile this as a module ( = code which can be
  2.6129 -  inserted in and removed from the running kernel whenever you want),
  2.6130 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6131 -  will be called scc.o.
  2.6132 -
  2.6133 -Support for TRX that feedback the tx signal to rx
  2.6134 -CONFIG_SCC_TRXECHO
  2.6135 -  Some transmitters feed the transmitted signal back to the receive
  2.6136 -  line.  Say Y here to foil this by explicitly disabling the receiver
  2.6137 -  during data transmission.  If in doubt, say Y.
  2.6138 -
  2.6139 -Additional delay for PA0HZP OptoSCC compatible boards
  2.6140 -CONFIG_SCC_DELAY
  2.6141 -  Say Y here if you experience problems with the SCC driver not
  2.6142 -  working properly; please read
  2.6143 -  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
  2.6144 -  say N.
  2.6145 -
  2.6146 -YAM driver for AX.25
  2.6147 -CONFIG_YAM
  2.6148 -  The YAM is a modem for packet radio which connects to the serial
  2.6149 -  port and includes some of the functions of a Terminal Node
  2.6150 -  Controller. If you have one of those, say Y here.
  2.6151 -
  2.6152 -  If you want to compile the driver as a module ( = code which can be
  2.6153 -  inserted in and removed from the running kernel whenever you want),
  2.6154 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6155 -  will be called yam.o.
  2.6156 -
  2.6157 -BAYCOM picpar and par96 driver for AX.25
  2.6158 -CONFIG_BAYCOM_PAR
  2.6159 -  This is a driver for Baycom style simple amateur radio modems that
  2.6160 -  connect to a parallel interface. The driver supports the picpar and
  2.6161 -  par96 designs. To configure the driver, use the sethdlc utility
  2.6162 -  available in the standard ax25 utilities package. For information on
  2.6163 -  the modems, see <http://www.baycom.de/> and the file
  2.6164 -  <file:Documentation/networking/baycom.txt>.
  2.6165 -
  2.6166 -  If you want to compile this driver as a module ( = code which can be
  2.6167 -  inserted in and removed from the running kernel whenever you want),
  2.6168 -  say M here and read <file:Documentation/modules.txt>.  This is
  2.6169 -  recommended.  The module will be called baycom_par.o.
  2.6170 -
  2.6171 -BAYCOM EPP driver for AX.25
  2.6172 -CONFIG_BAYCOM_EPP
  2.6173 -  This is a driver for Baycom style simple amateur radio modems that
  2.6174 -  connect to a parallel interface. The driver supports the EPP
  2.6175 -  designs. To configure the driver, use the sethdlc utility available
  2.6176 -  in the standard ax25 utilities package. For information on the
  2.6177 -  modems, see <http://www.baycom.de/> and the file
  2.6178 -  <file:Documentation/networking/baycom.txt>.
  2.6179 -
  2.6180 -  If you want to compile this driver as a module ( = code which can be
  2.6181 -  inserted in and removed from the running kernel whenever you want),
  2.6182 -  say M here and read <file:Documentation/modules.txt>.  This is
  2.6183 -  recommended.  The module will be called baycom_par.o.
  2.6184 -
  2.6185 -BAYCOM ser12 full-duplex driver for AX.25
  2.6186 -CONFIG_BAYCOM_SER_FDX
  2.6187 -  This is one of two drivers for Baycom style simple amateur radio
  2.6188 -  modems that connect to a serial interface. The driver supports the
  2.6189 -  ser12 design in full-duplex mode. In addition, it allows the
  2.6190 -  baudrate to be set between 300 and 4800 baud (however not all modems
  2.6191 -  support all baudrates). This is the preferred driver. The next
  2.6192 -  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
  2.6193 -  driver and still provided in case this driver does not work with
  2.6194 -  your serial interface chip. To configure the driver, use the sethdlc
  2.6195 -  utility available in the standard ax25 utilities package. For
  2.6196 -  information on the modems, see <http://www.baycom.de/> and
  2.6197 -  <file:Documentation/networking/baycom.txt>.
  2.6198 -
  2.6199 -  If you want to compile this driver as a module ( = code which can be
  2.6200 -  inserted in and removed from the running kernel whenever you want),
  2.6201 -  say M here and read <file:Documentation/modules.txt>.  This is
  2.6202 -  recommended.  The module will be called baycom_ser_fdx.o.
  2.6203 -
  2.6204 -BAYCOM ser12 half-duplex driver for AX.25
  2.6205 -CONFIG_BAYCOM_SER_HDX
  2.6206 -  This is one of two drivers for Baycom style simple amateur radio
  2.6207 -  modems that connect to a serial interface. The driver supports the
  2.6208 -  ser12 design in full-duplex mode. This is the old driver.  It is
  2.6209 -  still provided in case your serial interface chip does not work with
  2.6210 -  the full-duplex driver. This driver is depreciated.  To configure
  2.6211 -  the driver, use the sethdlc utility available in the standard ax25
  2.6212 -  utilities package. For information on the modems, see
  2.6213 -  <http://www.baycom.de/> and
  2.6214 -  <file:Documentation/networking/baycom.txt>.
  2.6215 -
  2.6216 -  If you want to compile this driver as a module ( = code which can be
  2.6217 -  inserted in and removed from the running kernel whenever you want),
  2.6218 -  say M here and read <file:Documentation/modules.txt>.  This is
  2.6219 -  recommended.  The module will be called baycom_ser_hdx.o.
  2.6220 -
  2.6221 -Sound card modem driver for AX.25
  2.6222 -CONFIG_SOUNDMODEM
  2.6223 -  This experimental driver allows a standard Sound Blaster or
  2.6224 -  WindowsSoundSystem compatible sound card to be used as a packet
  2.6225 -  radio modem (NOT as a telephone modem!), to send digital traffic
  2.6226 -  over amateur radio.
  2.6227 -
  2.6228 -  To configure the driver, use the sethdlc, smdiag and smmixer
  2.6229 -  utilities available in the standard ax25 utilities package. For
  2.6230 -  information on how to key the transmitter, see
  2.6231 -  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
  2.6232 -  <file:Documentation/networking/soundmodem.txt>.
  2.6233 -
  2.6234 -  If you want to compile this driver as a module ( = code which can be
  2.6235 -  inserted in and removed from the running kernel whenever you want),
  2.6236 -  say M here and read <file:Documentation/modules.txt>.  This is
  2.6237 -  recommended.  The module will be called soundmodem.o.
  2.6238 -
  2.6239 -Sound card modem support for Sound Blaster and compatible cards
  2.6240 -CONFIG_SOUNDMODEM_SBC
  2.6241 -  This option enables the soundmodem driver to use Sound Blaster and
  2.6242 -  compatible cards. If you have a dual mode card (i.e. a WSS cards
  2.6243 -  with a Sound Blaster emulation) you should say N here and Y to
  2.6244 -  "Sound card modem support for WSS and Crystal cards", below, because
  2.6245 -  this usually results in better performance. This option also
  2.6246 -  supports SB16/32/64 in full-duplex mode.
  2.6247 -
  2.6248 -Sound card modem support for WSS and Crystal cards
  2.6249 -CONFIG_SOUNDMODEM_WSS
  2.6250 -  This option enables the soundmodem driver to use WindowsSoundSystem
  2.6251 -  compatible cards. These cards feature a codec chip from either
  2.6252 -  Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
  2.6253 -  Semiconductors (such as CS4248, CS423x). This option also supports
  2.6254 -  the WSS full-duplex operation which currently works with Crystal
  2.6255 -  CS423x chips. If you don't need full-duplex operation, do not enable
  2.6256 -  it to save performance.
  2.6257 -
  2.6258 -Sound card modem support for 1200 baud AFSK modulation
  2.6259 -CONFIG_SOUNDMODEM_AFSK1200
  2.6260 -  This option enables the soundmodem driver 1200 baud AFSK modem,
  2.6261 -  compatible to popular modems using TCM3105 or AM7911. The
  2.6262 -  demodulator requires about 12% of the CPU power of a Pentium 75 CPU
  2.6263 -  per channel.
  2.6264 -
  2.6265 -Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
  2.6266 -CONFIG_SOUNDMODEM_AFSK2400_7
  2.6267 -  This option enables the soundmodem driver 2400 baud AFSK modem,
  2.6268 -  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
  2.6269 -  crystal. Note that the availability of this driver does _not_ imply
  2.6270 -  that I recommend building such links. It is only here since users
  2.6271 -  especially in eastern Europe have asked me to do so. In fact this
  2.6272 -  modulation scheme has many disadvantages, mainly its incompatibility
  2.6273 -  with many transceiver designs and the fact that the TCM3105 (if
  2.6274 -  used) is operated widely outside its specifications.
  2.6275 -
  2.6276 -Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
  2.6277 -CONFIG_SOUNDMODEM_AFSK2400_8
  2.6278 -  This option enables the soundmodem driver 2400 baud AFSK modem,
  2.6279 -  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
  2.6280 -  Note that the availability of this driver does _not_ imply that I
  2.6281 -  recommend building such links. It is only here since users
  2.6282 -  especially in eastern Europe have asked me to do so. In fact this
  2.6283 -  modulation scheme has many disadvantages, mainly its incompatibility
  2.6284 -  with many transceiver designs and the fact that the TCM3105 (if
  2.6285 -  used) is operated widely outside its specifications.
  2.6286 -
  2.6287 -Sound card modem support for 2666 baud AFSK modulation
  2.6288 -CONFIG_SOUNDMODEM_AFSK2666
  2.6289 -  This option enables the soundmodem driver 2666 baud AFSK modem.
  2.6290 -  This modem is experimental, and not compatible to anything
  2.6291 -  else I know of.
  2.6292 -
  2.6293 -Sound card modem support for 4800 baud 8PSK modulation
  2.6294 -CONFIG_SOUNDMODEM_PSK4800
  2.6295 -  This option enables the soundmodem driver 4800 baud 8PSK modem.
  2.6296 -  This modem is experimental, and not compatible to anything
  2.6297 -  else I know of.
  2.6298 -
  2.6299 -Sound card modem support for 4800 baud HAPN-1 modulation
  2.6300 -CONFIG_SOUNDMODEM_HAPN4800
  2.6301 -  This option enables the soundmodem driver 4800 baud HAPN-1
  2.6302 -  compatible modem. This modulation seems to be widely used 'down
  2.6303 -  under' and in the Netherlands. Here, nobody uses it, so I could not
  2.6304 -  test if it works. It is compatible to itself, however :-)
  2.6305 -
  2.6306 -Sound card modem support for 9600 baud FSK G3RUH modulation
  2.6307 -CONFIG_SOUNDMODEM_FSK9600
  2.6308 -  This option enables the soundmodem driver 9600 baud FSK modem,
  2.6309 -  compatible to the G3RUH standard. The demodulator requires about 4%
  2.6310 -  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
  2.6311 -  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
  2.6312 -  can only use one protocol at a time, depending on what the other end
  2.6313 -  can understand).
  2.6314 -
  2.6315 -CCITT X.25 Packet Layer
  2.6316 -CONFIG_X25
  2.6317 -  X.25 is a set of standardized network protocols, similar in scope to
  2.6318 -  frame relay; the one physical line from your box to the X.25 network
  2.6319 -  entry point can carry several logical point-to-point connections
  2.6320 -  (called "virtual circuits") to other computers connected to the X.25
  2.6321 -  network. Governments, banks, and other organizations tend to use it
  2.6322 -  to connect to each other or to form Wide Area Networks (WANs). Many
  2.6323 -  countries have public X.25 networks. X.25 consists of two
  2.6324 -  protocols: the higher level Packet Layer Protocol (PLP) (say Y here
  2.6325 -  if you want that) and the lower level data link layer protocol LAPB
  2.6326 -  (say Y to "LAPB Data Link Driver" below if you want that).
  2.6327 -
  2.6328 -  You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
  2.6329 -  <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
  2.6330 -  Information about X.25 for Linux is contained in the files
  2.6331 -  <file:Documentation/networking/x25.txt> and
  2.6332 -  <file:Documentation/networking/x25-iface.txt>.
  2.6333 -
  2.6334 -  One connects to an X.25 network either with a dedicated network card
  2.6335 -  using the X.21 protocol (not yet supported by Linux) or one can do
  2.6336 -  X.25 over a standard telephone line using an ordinary modem (say Y
  2.6337 -  to "X.25 async driver" below) or over Ethernet using an ordinary
  2.6338 -  Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
  2.6339 -  LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
  2.6340 -  and "LAPB over Ethernet driver" below).
  2.6341 -
  2.6342 -  If you want to compile this driver as a module ( = code which can be
  2.6343 -  inserted in and removed from the running kernel whenever you want),
  2.6344 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6345 -  will be called x25.o. If unsure, say N.
  2.6346 -
  2.6347 -LAPB Data Link Driver
  2.6348 -CONFIG_LAPB
  2.6349 -  Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
  2.6350 -  the lower) part of the X.25 protocol. It offers a reliable
  2.6351 -  connection service to exchange data frames with one other host, and
  2.6352 -  it is used to transport higher level protocols (mostly X.25 Packet
  2.6353 -  Layer, the higher part of X.25, but others are possible as well).
  2.6354 -  Usually, LAPB is used with specialized X.21 network cards, but Linux
  2.6355 -  currently supports LAPB only over Ethernet connections. If you want
  2.6356 -  to use LAPB connections over Ethernet, say Y here and to "LAPB over
  2.6357 -  Ethernet driver" below. Read
  2.6358 -  <file:Documentation/networking/lapb-module.txt> for technical
  2.6359 -  details.
  2.6360 -
  2.6361 -  If you want to compile this driver as a module though ( = code which
  2.6362 -  can be inserted in and removed from the running kernel whenever you
  2.6363 -  want), say M here and read <file:Documentation/modules.txt>.  The
  2.6364 -  module will be called lapb.o.  If unsure, say N.
  2.6365 -
  2.6366 -802.2 LLC
  2.6367 -CONFIG_LLC
  2.6368 -  This is a Logical Link Layer protocol used for X.25 connections over
  2.6369 -  Ethernet, using ordinary Ethernet cards.
  2.6370 -
  2.6371 -Frame Diverter
  2.6372 -CONFIG_NET_DIVERT
  2.6373 -  The Frame Diverter allows you to divert packets from the
  2.6374 -  network, that are not aimed at the interface receiving it (in
  2.6375 -  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
  2.6376 -  with the Frames Diverter on, can do some *really* transparent www
  2.6377 -  caching using a Squid proxy for example.
  2.6378 -
  2.6379 -  This is very useful when you don't want to change your router's
  2.6380 -  config (or if you simply don't have access to it).
  2.6381 -
  2.6382 -  The other possible usages of diverting Ethernet Frames are
  2.6383 -  numberous:
  2.6384 -   - reroute smtp traffic to another interface
  2.6385 -   - traffic-shape certain network streams
  2.6386 -   - transparently proxy smtp connections
  2.6387 -   - etc...
  2.6388 -
  2.6389 -  For more informations, please refer to:
  2.6390 -    <http://diverter.sourceforge.net/>
  2.6391 -    <http://perso.wanadoo.fr/magpie/EtherDivert.html>
  2.6392 -
  2.6393 -  If unsure, say N.
  2.6394 -
  2.6395 -802.1d Ethernet Bridging
  2.6396 -CONFIG_BRIDGE
  2.6397 -  If you say Y here, then your Linux box will be able to act as an
  2.6398 -  Ethernet bridge, which means that the different Ethernet segments it
  2.6399 -  is connected to will appear as one Ethernet to the participants.
  2.6400 -  Several such bridges can work together to create even larger
  2.6401 -  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  2.6402 -  As this is a standard, Linux bridges will cooperate properly with
  2.6403 -  other third party bridge products.
  2.6404 -
  2.6405 -  In order to use the Ethernet bridge, you'll need the bridge
  2.6406 -  configuration tools; see <file:Documentation/networking/bridge.txt>
  2.6407 -  for location. Please read the Bridge mini-HOWTO for more
  2.6408 -  information.
  2.6409 -
  2.6410 -  Note that if your box acts as a bridge, it probably contains several
  2.6411 -  Ethernet devices, but the kernel is not able to recognize more than
  2.6412 -  one at boot time without help; for details read the Ethernet-HOWTO,
  2.6413 -  available from in <http://www.tldp.org/docs.html#howto>.
  2.6414 -
  2.6415 -  If you want to compile this code as a module ( = code which can be
  2.6416 -  inserted in and removed from the running kernel whenever you want),
  2.6417 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.6418 -  will be called bridge.o.
  2.6419 -
  2.6420 -  If unsure, say N.
  2.6421 -
  2.6422 -Packet socket
  2.6423 -CONFIG_PACKET
  2.6424 -  The Packet protocol is used by applications which communicate
  2.6425 -  directly with network devices without an intermediate network
  2.6426 -  protocol implemented in the kernel, e.g. tcpdump.  If you want them
  2.6427 -  to work, choose Y.
  2.6428 -
  2.6429 -  This driver is also available as a module called af_packet.o ( =
  2.6430 -  code which can be inserted in and removed from the running kernel
  2.6431 -  whenever you want).  If you want to compile it as a module, say M
  2.6432 -  here and read <file:Documentation/modules.txt>; if you use modprobe
  2.6433 -  or kmod, you may also want to add "alias net-pf-17 af_packet" to
  2.6434 -  /etc/modules.conf.
  2.6435 -
  2.6436 -  If unsure, say Y.
  2.6437 -
  2.6438 -Packet socket: mmapped IO
  2.6439 -CONFIG_PACKET_MMAP
  2.6440 -  If you say Y here, the Packet protocol driver will use an IO
  2.6441 -  mechanism that results in faster communication.
  2.6442 -
  2.6443 -  If unsure, say N.
  2.6444 -
  2.6445 -Netlink device emulation
  2.6446 -CONFIG_NETLINK_DEV
  2.6447 -  This option will be removed soon. Any programs that want to use
  2.6448 -  character special nodes like /dev/tap0 or /dev/route (all with major
  2.6449 -  number 36) need this option, and need to be rewritten soon to use
  2.6450 -  the real netlink socket.
  2.6451 -  This is a backward compatibility option, choose Y for now.
  2.6452 -
  2.6453 -  This driver is also available as a module ( = code which can be
  2.6454 -  inserted in and removed from the running kernel whenever you want).
  2.6455 -  If you want to compile it as a module, say M here and read
  2.6456 -  <file:Documentation/modules.txt>. The module will be called
  2.6457 -  netlink_dev.o
  2.6458 -
  2.6459 -Asynchronous Transfer Mode (ATM)
  2.6460 -CONFIG_ATM
  2.6461 -  ATM is a high-speed networking technology for Local Area Networks
  2.6462 -  and Wide Area Networks.  It uses a fixed packet size and is
  2.6463 -  connection oriented, allowing for the negotiation of minimum
  2.6464 -  bandwidth requirements.
  2.6465 -
  2.6466 -  In order to participate in an ATM network, your Linux box needs an
  2.6467 -  ATM networking card. If you have that, say Y here and to the driver
  2.6468 -  of your ATM card below.
  2.6469 -
  2.6470 -  Note that you need a set of user-space programs to actually make use
  2.6471 -  of ATM.  See the file <file:Documentation/networking/atm.txt> for
  2.6472 -  further details.
  2.6473 -
  2.6474 -Classical IP over ATM
  2.6475 -CONFIG_ATM_CLIP
  2.6476 -  Classical IP over ATM for PVCs and SVCs, supporting InARP and
  2.6477 -  ATMARP. If you want to communication with other IP hosts on your ATM
  2.6478 -  network, you will typically either say Y here or to "LAN Emulation
  2.6479 -  (LANE)" below.
  2.6480 -
  2.6481 -Do NOT send ICMP if no neighbour
  2.6482 -CONFIG_ATM_CLIP_NO_ICMP
  2.6483 -  Normally, an "ICMP host unreachable" message is sent if a neighbour
  2.6484 -  cannot be reached because there is no VC to it in the kernel's
  2.6485 -  ATMARP table. This may cause problems when ATMARP table entries are
  2.6486 -  briefly removed during revalidation. If you say Y here, packets to
  2.6487 -  such neighbours are silently discarded instead.
  2.6488 -
  2.6489 -RFC1483/2684 Bridged protocols
  2.6490 -CONFIG_ATM_BR2684
  2.6491 -  ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
  2.6492 -  This device will act like an ethernet from the kernels point of view,
  2.6493 -  with the traffic being carried by ATM PVCs (currently 1 PVC/device).
  2.6494 -  This is sometimes used over DSL lines.  If in doubt, say N.
  2.6495 -
  2.6496 -Per-VC IP filter kludge
  2.6497 -CONFIG_ATM_BR2684_IPFILTER
  2.6498 -  This is an experimental mechanism for users who need to terminating a
  2.6499 -  large number of IP-only vcc's.  Do not enable this unless you are sure
  2.6500 -  you know what you are doing.
  2.6501 -
  2.6502 -LAN Emulation (LANE) support
  2.6503 -CONFIG_ATM_LANE
  2.6504 -  LAN Emulation emulates services of existing LANs across an ATM
  2.6505 -  network. Besides operating as a normal ATM end station client, Linux
  2.6506 -  LANE client can also act as an proxy client bridging packets between
  2.6507 -  ELAN and Ethernet segments. You need LANE if you want to try MPOA.
  2.6508 -
  2.6509 -Multi-Protocol Over ATM (MPOA) support
  2.6510 -CONFIG_ATM_MPOA
  2.6511 -  Multi-Protocol Over ATM allows ATM edge devices such as routers,
  2.6512 -  bridges and ATM attached hosts establish direct ATM VCs across
  2.6513 -  subnetwork boundaries. These shortcut connections bypass routers
  2.6514 -  enhancing overall network performance.
  2.6515 -
  2.6516 -ATM over TCP
  2.6517 -CONFIG_ATM_TCP
  2.6518 -  ATM over TCP driver. Useful mainly for development and for
  2.6519 -  experiments. If unsure, say N.
  2.6520 -
  2.6521 -Efficient Networks ENI155P
  2.6522 -CONFIG_ATM_ENI
  2.6523 -  Driver for the Efficient Networks ENI155p series and SMC ATM
  2.6524 -  Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
  2.6525 -  2MB on-board RAM (Efficient calls them "C" and "S", respectively),
  2.6526 -  and the FPGA and the ASIC Tonga versions of the board are supported.
  2.6527 -  The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
  2.6528 -  adapters.
  2.6529 -
  2.6530 -  This driver is also available as a module.  If you want to compile
  2.6531 -  it as a module, say M here and read
  2.6532 -  <file:Documentation/modules.txt>.  The module will be called eni.o.
  2.6533 -
  2.6534 -Enable extended debugging
  2.6535 -CONFIG_ATM_ENI_DEBUG
  2.6536 -  Extended debugging records various events and displays that list
  2.6537 -  when an inconsistency is detected. This mechanism is faster than
  2.6538 -  generally using printks, but still has some impact on performance.
  2.6539 -  Note that extended debugging may create certain race conditions
  2.6540 -  itself. Enable this ONLY if you suspect problems with the driver.
  2.6541 -
  2.6542 -Fine-tune burst settings
  2.6543 -CONFIG_ATM_ENI_TUNE_BURST
  2.6544 -  In order to obtain good throughput, the ENI NIC can transfer
  2.6545 -  multiple words of data per PCI bus access cycle. Such a multi-word
  2.6546 -  transfer is called a burst.
  2.6547 -
  2.6548 -  The default settings for the burst sizes are suitable for most PCI
  2.6549 -  chipsets. However, in some cases, large bursts may overrun buffers
  2.6550 -  in the PCI chipset and cause data corruption. In such cases, large
  2.6551 -  bursts must be disabled and only (slower) small bursts can be used.
  2.6552 -  The burst sizes can be set independently in the send (TX) and
  2.6553 -  receive (RX) direction.
  2.6554 -
  2.6555 -  Note that enabling many different burst sizes in the same direction
  2.6556 -  may increase the cost of setting up a transfer such that the
  2.6557 -  resulting throughput is lower than when using only the largest
  2.6558 -  available burst size.
  2.6559 -
  2.6560 -  Also, sometimes larger bursts lead to lower throughput, e.g. on an
  2.6561 -  Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
  2.6562 -  when going from 8W to 16W bursts.
  2.6563 -
  2.6564 -Enable 16W TX bursts (discouraged)
  2.6565 -CONFIG_ATM_ENI_BURST_TX_16W
  2.6566 -  Burst sixteen words at once in the send direction. This may work
  2.6567 -  with recent PCI chipsets, but is known to fail with older chipsets.
  2.6568 -
  2.6569 -Enable 8W TX bursts (recommended)
  2.6570 -CONFIG_ATM_ENI_BURST_TX_8W
  2.6571 -  Burst eight words at once in the send direction. This is the default
  2.6572 -  setting.
  2.6573 -
  2.6574 -Enable 4W TX bursts (optional)
  2.6575 -CONFIG_ATM_ENI_BURST_TX_4W
  2.6576 -  Burst four words at once in the send direction. You may want to try
  2.6577 -  this if you have disabled 8W bursts. Enabling 4W if 8W is also set
  2.6578 -  may or may not improve throughput.
  2.6579 -
  2.6580 -Enable 2W TX bursts (optional)
  2.6581 -CONFIG_ATM_ENI_BURST_TX_2W
  2.6582 -  Burst two words at once in the send direction. You may want to try
  2.6583 -  this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
  2.6584 -  are also set may or may not improve throughput.
  2.6585 -
  2.6586 -Enable 16W RX bursts (discouraged)
  2.6587 -CONFIG_ATM_ENI_BURST_RX_16W
  2.6588 -  Burst sixteen words at once in the receive direction. This may work
  2.6589 -  with recent PCI chipsets, but is known to fail with older chipsets.
  2.6590 -
  2.6591 -Enable 8W RX bursts (discouraged)
  2.6592 -CONFIG_ATM_ENI_BURST_RX_8W
  2.6593 -  Burst eight words at once in the receive direction. This may work
  2.6594 -  with recent PCI chipsets, but is known to fail with older chipsets,
  2.6595 -  such as the Intel Neptune series.
  2.6596 -
  2.6597 -Enable 4W RX bursts (recommended)
  2.6598 -CONFIG_ATM_ENI_BURST_RX_4W
  2.6599 -  Burst four words at once in the receive direction. This is the
  2.6600 -  default setting. Enabling 4W if 8W is also set may or may not
  2.6601 -  improve throughput.
  2.6602 -
  2.6603 -Enable 2W RX bursts (optional)
  2.6604 -CONFIG_ATM_ENI_BURST_RX_2W
  2.6605 -  Burst two words at once in the receive direction. You may want to
  2.6606 -  try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
  2.6607 -  8W are also set may or may not improve throughput.
  2.6608 -
  2.6609 -ZeitNet ZN1221/ZN1225
  2.6610 -CONFIG_ATM_ZATM
  2.6611 -  Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
  2.6612 -  adapters.
  2.6613 -
  2.6614 -  This driver is also available as a module.  If you want to compile
  2.6615 -  it as a module, say M here and read
  2.6616 -  <file:Documentation/modules.txt>.  The module will be called zatm.o.
  2.6617 -
  2.6618 -Enable extended debugging
  2.6619 -CONFIG_ATM_ZATM_DEBUG
  2.6620 -  Extended debugging records various events and displays that list
  2.6621 -  when an inconsistency is detected. This mechanism is faster than
  2.6622 -  generally using printks, but still has some impact on performance.
  2.6623 -  Note that extended debugging may create certain race conditions
  2.6624 -  itself. Enable this ONLY if you suspect problems with the driver.
  2.6625 -
  2.6626 -Fujitsu FireStream (FS50/FS155)
  2.6627 -CONFIG_ATM_FIRESTREAM
  2.6628 -  Driver for the Fujitsu FireStream 155 (MB86697) and
  2.6629 -  FireStream 50 (MB86695) ATM PCI chips.
  2.6630 -
  2.6631 -  This driver is also available as a module.  If you want to compile
  2.6632 -  it as a module, say M here and read
  2.6633 -  <file:Documentation/modules.txt>.  The module will be called
  2.6634 -  firestream.o.
  2.6635 -
  2.6636 -Enable usec resolution timestamps
  2.6637 -CONFIG_ATM_ZATM_EXACT_TS
  2.6638 -  The uPD98401 SAR chip supports a high-resolution timer (approx. 30
  2.6639 -  MHz) that is used for very accurate reception timestamps. Because
  2.6640 -  that timer overflows after 140 seconds, and also to avoid timer
  2.6641 -  drift, time measurements need to be periodically synchronized with
  2.6642 -  the normal system time. Enabling this feature will add some general
  2.6643 -  overhead for timer synchronization and also per-packet overhead for
  2.6644 -  time conversion.
  2.6645 -
  2.6646 -IDT 77201/11 (NICStAR) (ForeRunnerLE)
  2.6647 -CONFIG_ATM_NICSTAR
  2.6648 -  The NICStAR chipset family is used in a large number of ATM NICs for
  2.6649 -  25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
  2.6650 -  series. Say Y if you have one of those.
  2.6651 -
  2.6652 -  This driver is also available as a module.  If you want to compile
  2.6653 -  it as a module, say M here and read
  2.6654 -  <file:Documentation/modules.txt>. The module will be called
  2.6655 -  nicstar.o.
  2.6656 -
  2.6657 -Use suni PHY driver (155Mbps)
  2.6658 -CONFIG_ATM_NICSTAR_USE_SUNI
  2.6659 -  Support for the S-UNI and compatible PHYsical layer chips. These are
  2.6660 -  found in most 155Mbps NICStAR based ATM cards, namely in the
  2.6661 -  ForeRunner LE155 cards. This driver provides detection of cable~
  2.6662 -  removal and reinsertion and provides some statistics. This driver
  2.6663 -  doesn't have removal capability when compiled as a module, so if you
  2.6664 -  need that capability don't include S-UNI support (it's not needed to
  2.6665 -  make the card work).
  2.6666 -
  2.6667 -Use IDT77015 PHY driver (25Mbps)
  2.6668 -CONFIG_ATM_NICSTAR_USE_IDT77105
  2.6669 -  Support for the PHYsical layer chip in ForeRunner LE25 cards. In
  2.6670 -  addition to cable removal/reinsertion detection, this driver allows
  2.6671 -  you to control the loopback mode of the chip via a dedicated IOCTL.
  2.6672 -  This driver is required for proper handling of temporary carrier
  2.6673 -  loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
  2.6674 -
  2.6675 -IDT 77252 (NICStAR II)
  2.6676 -CONFIG_ATM_IDT77252
  2.6677 -  Driver for the IDT 77252 ATM PCI chips.
  2.6678 -
  2.6679 -  This driver is also available as a module.  If you want to compile
  2.6680 -  it as a module, say M here and read
  2.6681 -  <file:Documentation/modules.txt>. The module will be called idt77252.o
  2.6682 -
  2.6683 -Enable debugging messages
  2.6684 -CONFIG_ATM_IDT77252_DEBUG
  2.6685 -  Somewhat useful debugging messages are available. The choice of
  2.6686 -  messages is controlled by a bitmap.  This may be specified as a
  2.6687 -  module argument.  See the file <file:drivers/atm/idt77252.h> for
  2.6688 -  the meanings of the bits in the mask.
  2.6689 -
  2.6690 -  When active, these messages can have a significant impact on the
  2.6691 -  speed of the driver, and the size of your syslog files! When
  2.6692 -  inactive, they will have only a modest impact on performance.
  2.6693 -
  2.6694 -Receive ALL cells in raw queue
  2.6695 -CONFIG_ATM_IDT77252_RCV_ALL
  2.6696 -  Enable receiving of all cells on the ATM link, that do not match
  2.6697 -  an open connection in the raw cell queue of the driver.  Useful
  2.6698 -  for debugging or special applications only, so the safe answer is N.
  2.6699 -
  2.6700 -Madge Ambassador (Collage PCI 155 Server)
  2.6701 -CONFIG_ATM_AMBASSADOR
  2.6702 -  This is a driver for ATMizer based ATM card produced by Madge
  2.6703 -  Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
  2.6704 -  here if you have one of these cards.
  2.6705 -
  2.6706 -Enable debugging messages
  2.6707 -CONFIG_ATM_AMBASSADOR_DEBUG
  2.6708 -  Somewhat useful debugging messages are available. The choice of
  2.6709 -  messages is controlled by a bitmap.  This may be specified as a
  2.6710 -  module argument (kernel command line argument as well?), changed
  2.6711 -  dynamically using an ioctl (not yet) or changed by sending the
  2.6712 -  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  2.6713 -  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
  2.6714 -  mask.
  2.6715 -
  2.6716 -  When active, these messages can have a significant impact on the
  2.6717 -  speed of the driver, and the size of your syslog files! When
  2.6718 -  inactive, they will have only a modest impact on performance.
  2.6719 -
  2.6720 -Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
  2.6721 -CONFIG_ATM_HORIZON
  2.6722 -  This is a driver for the Horizon chipset ATM adapter cards once
  2.6723 -  produced by Madge Networks Ltd. Say Y (or M to compile as a module
  2.6724 -  named horizon.o) here if you have one of these cards.
  2.6725 -
  2.6726 -Enable debugging messages
  2.6727 -CONFIG_ATM_HORIZON_DEBUG
  2.6728 -  Somewhat useful debugging messages are available. The choice of
  2.6729 -  messages is controlled by a bitmap.  This may be specified as a
  2.6730 -  module argument (kernel command line argument as well?), changed
  2.6731 -  dynamically using an ioctl (not yet) or changed by sending the
  2.6732 -  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  2.6733 -  <file:drivers/atm/horizon.h> for the meanings of the bits in the
  2.6734 -  mask.
  2.6735 -
  2.6736 -  When active, these messages can have a significant impact on the
  2.6737 -  speed of the driver, and the size of your syslog files! When
  2.6738 -  inactive, they will have only a modest impact on performance.
  2.6739 -
  2.6740 -Interphase ATM PCI x575/x525/x531
  2.6741 -CONFIG_ATM_IA
  2.6742 -  This is a driver for the Interphase (i)ChipSAR adapter cards
  2.6743 -  which include a variety of variants in term of the size of the
  2.6744 -  control memory (128K-1KVC, 512K-4KVC), the size of the packet
  2.6745 -  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
  2.6746 -  UTP155, UTP25, DS3 and E3). Go to:
  2.6747 -  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
  2.6748 -  for more info about the cards. Say Y (or M to compile as a module
  2.6749 -  named iphase.o) here if you have one of these cards.
  2.6750 -
  2.6751 -  See the file <file:Documentation/networking/iphase.txt> for further
  2.6752 -  details.
  2.6753 -
  2.6754 -Enable debugging messages
  2.6755 -CONFIG_ATM_IA_DEBUG
  2.6756 -  Somewhat useful debugging messages are available. The choice of
  2.6757 -  messages is controlled by a bitmap. This may be specified as a
  2.6758 -  module argument (kernel command line argument as well?), changed
  2.6759 -  dynamically using an ioctl (Get the debug utility, iadbg, from
  2.6760 -  <ftp://ftp.iphase.com/pub/atm/pci/>).
  2.6761 -
  2.6762 -  See the file <file:drivers/atm/iphase.h> for the meanings of the
  2.6763 -  bits in the mask.
  2.6764 -
  2.6765 -  When active, these messages can have a significant impact on the
  2.6766 -  speed of the driver, and the size of your syslog files! When
  2.6767 -  inactive, they will have only a modest impact on performance.
  2.6768 -
  2.6769 -Efficient Networks Speedstream 3010
  2.6770 -CONFIG_ATM_LANAI
  2.6771 -  Supports ATM cards based on the Efficient Networks "Lanai"
  2.6772 -  chipset such as the Speedstream 3010 and the ENI-25p.  The
  2.6773 -  Speedstream 3060 is currently not supported since we don't
  2.6774 -  have the code to drive the on-board Alcatel DSL chipset (yet).
  2.6775 -
  2.6776 -Linux telephony support
  2.6777 -CONFIG_PHONE
  2.6778 -  Say Y here if you have a telephony card, which for example allows
  2.6779 -  you to use a regular phone for voice-over-IP applications.
  2.6780 -
  2.6781 -  Note: this has nothing to do with modems.  You do not need to say Y
  2.6782 -  here in order to be able to use a modem under Linux.
  2.6783 -
  2.6784 -  This support is also available as a module.  If you want to compile
  2.6785 -  it as a module, say M here and read
  2.6786 -  <file:Documentation/modules.txt>.  The module will be called
  2.6787 -  phonedev.o.
  2.6788 -
  2.6789 -Compaq Smart Array support
  2.6790 -CONFIG_BLK_CPQ_CISS_DA
  2.6791 -  This is the driver for Compaq Smart Array 5xxx controllers.
  2.6792 -  Everyone using these boards should say Y here.
  2.6793 -  See <file:Documentation/cciss.txt> for the current list of
  2.6794 -  boards supported by this driver, and for further information
  2.6795 -  on the use of this driver.
  2.6796 -
  2.6797 -  This driver is also available as a module ( = code which can be
  2.6798 -  inserted in and removed from the running kernel whenever you want).
  2.6799 -  If you want to compile it as a module, say M here and read
  2.6800 -  <file:Documentation/modules.txt>. The module will be called
  2.6801 -  cciss.o
  2.6802 -
  2.6803 -SCSI tape drive support for Smart Array 5xxx
  2.6804 -CONFIG_CISS_SCSI_TAPE
  2.6805 -  When enabled (Y), this option allows SCSI tape drives and SCSI medium
  2.6806 -  changers (tape robots) to be accessed via a Compaq 5xxx array
  2.6807 -  controller.  (See Documentation/cciss.txt for more details.)
  2.6808 -
  2.6809 -  "SCSI support" and "SCSI tape support" must also be enabled for this
  2.6810 -  option to work.
  2.6811 -
  2.6812 -  When this option is disabled (N), the SCSI portion of the driver
  2.6813 -  is not compiled.
  2.6814 -
  2.6815 -QuickNet Internet LineJack/PhoneJack support
  2.6816 -CONFIG_PHONE_IXJ
  2.6817 -  Say M if you have a telephony card manufactured by Quicknet
  2.6818 -  Technologies, Inc.  These include the Internet PhoneJACK and
  2.6819 -  Internet LineJACK Telephony Cards. You will get a module called
  2.6820 -  ixj.o.
  2.6821 -
  2.6822 -  For the ISA versions of these products, you can configure the
  2.6823 -  cards using the isapnp tools (pnpdump/isapnp) or you can use the
  2.6824 -  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
  2.6825 -
  2.6826 -  For more information on these cards, see Quicknet's web site at:
  2.6827 -  <http://www.quicknet.net/>.
  2.6828 -
  2.6829 -  If you do not have any Quicknet telephony cards, you can safely
  2.6830 -  say N here.
  2.6831 -
  2.6832 -QuickNet Internet LineJack/PhoneJack PCMCIA support
  2.6833 -CONFIG_PHONE_IXJ_PCMCIA
  2.6834 -  Say Y here to configure in PCMCIA service support for the Quicknet
  2.6835 -  cards manufactured by Quicknet Technologies, Inc.  This builds an
  2.6836 -  additional support module for the PCMCIA version of the card.
  2.6837 -
  2.6838 -FORE Systems 200E-series
  2.6839 -CONFIG_ATM_FORE200E_MAYBE
  2.6840 -  This is a driver for the FORE Systems 200E-series ATM adapter
  2.6841 -  cards. It simultaneously supports PCA-200E and SBA-200E models
  2.6842 -  on PCI and SBUS hosts. Say Y (or M to compile as a module
  2.6843 -  named fore_200e.o) here if you have one of these ATM adapters.
  2.6844 -
  2.6845 -  Note that the driver will actually be compiled only if you
  2.6846 -  additionally enable the support for PCA-200E and/or SBA-200E
  2.6847 -  cards.
  2.6848 -
  2.6849 -  See the file <file:Documentation/networking/fore200e.txt> for
  2.6850 -  further details.
  2.6851 -
  2.6852 -Enable PCA-200E card support on PCI-based hosts
  2.6853 -CONFIG_ATM_FORE200E_PCA
  2.6854 -  Say Y here if you want your PCA-200E cards to be probed.
  2.6855 -
  2.6856 -Use default PCA-200E firmware
  2.6857 -CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
  2.6858 -  Use the default PCA-200E firmware data shipped with the driver.
  2.6859 -
  2.6860 -  Normal users do not have to deal with the firmware stuff, so
  2.6861 -  they should say Y here.
  2.6862 -
  2.6863 -Pathname of user-supplied binary firmware
  2.6864 -CONFIG_ATM_FORE200E_PCA_FW
  2.6865 -  This defines the pathname of an alternative PCA-200E binary
  2.6866 -  firmware image supplied by the user. This pathname may be
  2.6867 -  absolute or relative to the drivers/atm directory.
  2.6868 -
  2.6869 -  The driver comes with an adequate firmware image, so normal users do
  2.6870 -  not have to supply an alternative one. They just say Y to "Use
  2.6871 -  default PCA-200E firmware" instead.
  2.6872 -
  2.6873 -Enable SBA-200E card support on SBUS-based hosts
  2.6874 -CONFIG_ATM_FORE200E_SBA
  2.6875 -  Say Y here if you want your SBA-200E cards to be probed.
  2.6876 -
  2.6877 -Use default SBA-200E firmware
  2.6878 -CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
  2.6879 -  Use the default SBA-200E firmware data shipped with the driver.
  2.6880 -
  2.6881 -  Normal users do not have to deal with the firmware stuff, so
  2.6882 -  they should say Y here.
  2.6883 -
  2.6884 -Pathname of user-supplied binary firmware
  2.6885 -CONFIG_ATM_FORE200E_SBA_FW
  2.6886 -  This defines the pathname of an alternative SBA-200E binary
  2.6887 -  firmware image supplied by the user. This pathname may be
  2.6888 -  absolute or relative to the drivers/atm directory.
  2.6889 -
  2.6890 -  The driver comes with an adequate firmware image, so normal users do
  2.6891 -  not have to supply an alternative one. They just say Y to "Use
  2.6892 -  default SBA-200E firmware", above.
  2.6893 -
  2.6894 -Maximum number of tx retries
  2.6895 -CONFIG_ATM_FORE200E_TX_RETRY
  2.6896 -  Specifies the number of times the driver attempts to transmit
  2.6897 -  a message before giving up, if the transmit queue of the ATM card
  2.6898 -  is transiently saturated.
  2.6899 -
  2.6900 -  Saturation of the transmit queue may occur only under extreme
  2.6901 -  conditions, e.g. when a fast host continuously submits very small
  2.6902 -  frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
  2.6903 -
  2.6904 -  Note that under common conditions, it is unlikely that you encounter
  2.6905 -  a saturation of the transmit queue, so the retry mechanism never
  2.6906 -  comes into play.
  2.6907 -
  2.6908 -Debugging level (0-3)
  2.6909 -CONFIG_ATM_FORE200E_DEBUG
  2.6910 -  Specifies the level of debugging messages issued by the driver.
  2.6911 -  The verbosity of the driver increases with the value of this
  2.6912 -  parameter.
  2.6913 -
  2.6914 -  When active, these messages can have a significant impact on
  2.6915 -  the performances of the driver, and the size of your syslog files!
  2.6916 -  Keep the debugging level to 0 during normal operations.
  2.6917 -
  2.6918 -PPP over ATM
  2.6919 -CONFIG_PPPOATM
  2.6920 -  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  2.6921 -  This implementation does not yet comply with section 8 of RFC2364,
  2.6922 -  which can lead to bad results idf the ATM peer loses state and 
  2.6923 -  changes its encapsulation unilaterally.
  2.6924 -
  2.6925 -Fusion MPT device support
  2.6926 -CONFIG_FUSION
  2.6927 -  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
  2.6928 -  provides high performance SCSI host initiator, and LAN [1] interface
  2.6929 -  services to a host system.  The Fusion architecture is capable of
  2.6930 -  duplexing these protocols on high-speed Fibre Channel
  2.6931 -  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
  2.6932 -  physical medium.
  2.6933 -
  2.6934 -          [1] LAN is not supported on parallel SCSI medium.
  2.6935 -
  2.6936 -  These drivers require a Fusion MPT compatible PCI adapter installed
  2.6937 -  in the host system.  MPT adapters contain specialized I/O processors
  2.6938 -  to handle I/O workload, and more importantly to offload this work
  2.6939 -  from the host CPU(s).
  2.6940 -
  2.6941 -  If you have Fusion MPT hardware and want to use it, you can say
  2.6942 -  Y or M here to add MPT (base + ScsiHost) drivers.
  2.6943 -    <Y> = build lib (fusion.o), and link [static] into the kernel [2]
  2.6944 -          proper
  2.6945 -    <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
  2.6946 -          mptscsih.o)
  2.6947 -
  2.6948 -          [2] In order enable capability to boot the linux kernel
  2.6949 -              natively from a Fusion MPT target device, you MUST
  2.6950 -               answer Y here! (currently requires CONFIG_BLK_DEV_SD)
  2.6951 -          [3] This support is also available as a module ( = code
  2.6952 -              which can be inserted in and removed from the running
  2.6953 -              kernel whenever you want).  If you want to compile as
  2.6954 -              modules, say M here and read
  2.6955 -              <file:Documentation/modules.txt>.
  2.6956 -
  2.6957 -  If unsure, say N.
  2.6958 -
  2.6959 -  If you say Y or M here you will get a choice of these
  2.6960 -  additional protocol and support module options:         Module Name:
  2.6961 -    <M>   Enhanced SCSI error reporting                     (isense.o)
  2.6962 -    <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
  2.6963 -    <M>   Fusion MPT LAN driver                             (mptlan.o)
  2.6964 -
  2.6965 -  ---
  2.6966 -  Fusion MPT is trademark of LSI Logic Corporation, and its
  2.6967 -  architecture is based on LSI Logic's Message Passing Interface (MPI)
  2.6968 -  specification.
  2.6969 -
  2.6970 -Fusion MPT enhanced SCSI error reporting [optional] module
  2.6971 -CONFIG_FUSION_ISENSE
  2.6972 -  The isense module (roughly stands for Interpret SENSE data) is
  2.6973 -  completely optional.  It simply provides extra English readable
  2.6974 -  strings in SCSI Error Report(s) that might be generated from the
  2.6975 -  Fusion MPT SCSI Host driver, for example when a target device
  2.6976 -  returns a SCSI check condition on a I/O.  Without this module
  2.6977 -  loaded you might see:
  2.6978 -
  2.6979 -    SCSI Error Report =-=-= (ioc0,scsi5:0)
  2.6980 -      SCSI_Status=02h (CHECK_CONDITION)
  2.6981 -      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
  2.6982 -      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  2.6983 -      SenseKey=2h (NOT READY); FRU=02h
  2.6984 -      ASC/ASCQ=29h/00h
  2.6985 -
  2.6986 -  Where otherwise, if this module had been loaded, you would see:
  2.6987 -
  2.6988 -    SCSI Error Report =-=-= (ioc0,scsi5:0)
  2.6989 -      SCSI_Status=02h (CHECK_CONDITION)
  2.6990 -      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
  2.6991 -      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  2.6992 -      SenseKey=2h (NOT READY); FRU=02h
  2.6993 -      ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
  2.6994 -
  2.6995 -  Say M for "Enhanced SCSI error reporting" to compile this optional module,
  2.6996 -  creating a driver named: isense.o.
  2.6997 -
  2.6998 -  NOTE: Support for building this feature into the kernel is not
  2.6999 -  available, due to kernel size considerations.
  2.7000 -
  2.7001 -Fusion MPT misc device (ioctl) driver [optional] module
  2.7002 -CONFIG_FUSION_CTL
  2.7003 -  The Fusion MPT misc device driver provides specialized control
  2.7004 -  of MPT adapters via system ioctl calls.  Use of ioctl calls to
  2.7005 -  the MPT driver requires that you create and use a misc device
  2.7006 -  node ala:
  2.7007 -    mknod /dev/mptctl c 10 240
  2.7008 -
  2.7009 -  One use of this ioctl interface is to perform an upgrade (reflash)
  2.7010 -  of the MPT adapter firmware.  Refer to readme file(s) distributed
  2.7011 -  with the Fusion MPT linux driver for additional details.
  2.7012 -
  2.7013 -  If enabled by saying M to this, a driver named: mptctl.o
  2.7014 -  will be compiled.
  2.7015 -
  2.7016 -  If unsure whether you really want or need this, say N.
  2.7017 -
  2.7018 -Fusion MPT LAN driver [optional]
  2.7019 -CONFIG_FUSION_LAN
  2.7020 -  This module supports LAN IP traffic over Fibre Channel port(s)
  2.7021 -  on Fusion MPT compatible hardware (LSIFC9xx chips).
  2.7022 -  The physical interface used is defined in RFC 2625.
  2.7023 -  Please refer to that document for details.
  2.7024 -
  2.7025 -  Installing this driver requires the knowledge to configure and
  2.7026 -  activate a new network interface, "fc0", using standard Linux tools.
  2.7027 -
  2.7028 -  If enabled by saying M to this, a driver named: mptlan.o
  2.7029 -  will be compiled.
  2.7030 -
  2.7031 -  If unsure whether you really want or need this, say N.
  2.7032 -
  2.7033 -  NOTES: This feature is NOT available nor supported for linux-2.2.x
  2.7034 -  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
  2.7035 -  in order to configure this option.
  2.7036 -  Support for building this feature into the linux kernel is not
  2.7037 -  yet available.
  2.7038 -
  2.7039 -SCSI support
  2.7040 -CONFIG_SCSI
  2.7041 -  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  2.7042 -  any other SCSI device under Linux, say Y and make sure that you know
  2.7043 -  the name of your SCSI host adapter (the card inside your computer
  2.7044 -  that "speaks" the SCSI protocol, also called SCSI controller),
  2.7045 -  because you will be asked for it.
  2.7046 -
  2.7047 -  You also need to say Y here if you want support for the parallel
  2.7048 -  port version of the 100 MB IOMEGA ZIP drive.
  2.7049 -
  2.7050 -  This driver is also available as a module ( = code which can be
  2.7051 -  inserted in and removed from the running kernel whenever you want).
  2.7052 -  The module will be called scsi_mod.o.  If you want to compile it as
  2.7053 -  a module, say M here and read <file:Documentation/modules.txt> and
  2.7054 -  <file:Documentation/scsi.txt>.  However, do not compile this as a
  2.7055 -  module if your root file system (the one containing the directory /)
  2.7056 -  is located on a SCSI device.
  2.7057 -
  2.7058 -SCSI disk support
  2.7059 -CONFIG_BLK_DEV_SD
  2.7060 -  If you want to use a SCSI hard disk or the SCSI or parallel port
  2.7061 -  version of the IOMEGA ZIP drive under Linux, say Y and read the
  2.7062 -  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  2.7063 -  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  2.7064 -  CD-ROMs.
  2.7065 -
  2.7066 -  This driver is also available as a module ( = code which can be
  2.7067 -  inserted in and removed from the running kernel whenever you want).
  2.7068 -  The module will be called sd_mod.o.  If you want to compile it as a
  2.7069 -  module, say M here and read <file:Documentation/modules.txt> and
  2.7070 -  <file:Documentation/scsi.txt>.  Do not compile this driver as a
  2.7071 -  module if your root file system (the one containing the directory /)
  2.7072 -  is located on a SCSI disk. In this case, do not compile the driver
  2.7073 -  for your SCSI host adapter (below) as a module either.
  2.7074 -
  2.7075 -Maximum number of SCSI disks that can be loaded as modules
  2.7076 -CONFIG_SD_EXTRA_DEVS
  2.7077 -  This controls the amount of additional space allocated in tables for
  2.7078 -  drivers that are loaded as modules after the kernel is booted.  In
  2.7079 -  the event that the SCSI core itself was loaded as a module, this
  2.7080 -  value is the number of additional disks that can be loaded after the
  2.7081 -  first host driver is loaded.
  2.7082 -
  2.7083 -  Admittedly this isn't pretty, but there are tons of race conditions
  2.7084 -  involved with resizing the internal arrays on the fly.  Someday this
  2.7085 -  flag will go away, and everything will work automatically.
  2.7086 -
  2.7087 -  If you don't understand what's going on, go with the default.
  2.7088 -
  2.7089 -Maximum number of SCSI tapes that can be loaded as modules
  2.7090 -CONFIG_ST_EXTRA_DEVS
  2.7091 -  This controls the amount of additional space allocated in tables for
  2.7092 -  drivers that are loaded as modules after the kernel is booted.  In
  2.7093 -  the event that the SCSI core itself was loaded as a module, this
  2.7094 -  value is the number of additional tapes that can be loaded after the
  2.7095 -  first host driver is loaded.
  2.7096 -
  2.7097 -  Admittedly this isn't pretty, but there are tons of race conditions
  2.7098 -  involved with resizing the internal arrays on the fly.  Someday this
  2.7099 -  flag will go away, and everything will work automatically.
  2.7100 -
  2.7101 -  If you don't understand what's going on, go with the default.
  2.7102 -
  2.7103 -SCSI tape support
  2.7104 -CONFIG_CHR_DEV_ST
  2.7105 -  If you want to use a SCSI tape drive under Linux, say Y and read the
  2.7106 -  SCSI-HOWTO, available from
  2.7107 -  <http://www.tldp.org/docs.html#howto>, and
  2.7108 -  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
  2.7109 -  SCSI CD-ROMs.
  2.7110 -
  2.7111 -  This driver is also available as a module ( = code which can be
  2.7112 -  inserted in and removed from the running kernel whenever you want).
  2.7113 -  The module will be called st.o. If you want to compile it as a
  2.7114 -  module, say M here and read <file:Documentation/modules.txt> and
  2.7115 -  <file:Documentation/scsi.txt>.
  2.7116 -
  2.7117 -OnStream SC-x0 SCSI tape support
  2.7118 -CONFIG_CHR_DEV_OSST
  2.7119 -  The OnStream SC-x0 SCSI tape drives can not be driven by the
  2.7120 -  standard st driver, but instead need this special osst driver and
  2.7121 -  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
  2.7122 -  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
  2.7123 -  as well.  Note that there is also a second generation of OnStream
  2.7124 -  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
  2.7125 -  tapes (QIC-157) and can be driven by the standard driver st.
  2.7126 -  For more information, you may have a look at the SCSI-HOWTO
  2.7127 -  <http://www.tldp.org/docs.html#howto>  and
  2.7128 -  <file:drivers/scsi/README.osst>  in the kernel source.
  2.7129 -  More info on the OnStream driver may be found on
  2.7130 -  <http://linux1.onstream.nl/test/>
  2.7131 -  Please also have a look at the standard st docu, as most of it
  2.7132 -  applies to osst as well.
  2.7133 -
  2.7134 -  This driver is also available as a module ( = code which can be
  2.7135 -  inserted in and removed from the running kernel whenever you want).
  2.7136 -  The module will be called osst.o. If you want to compile it as a
  2.7137 -  module, say M here and read <file:Documentation/modules.txt> and
  2.7138 -  <file:Documentation/scsi.txt>.
  2.7139 -
  2.7140 -SCSI CD-ROM support
  2.7141 -CONFIG_BLK_DEV_SR
  2.7142 -  If you want to use a SCSI CD-ROM under Linux, say Y and read the
  2.7143 -  SCSI-HOWTO and the CD-ROM-HOWTO at
  2.7144 -  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  2.7145 -  or M to "ISO 9660 CD-ROM file system support" later.
  2.7146 -
  2.7147 -  This driver is also available as a module ( = code which can be
  2.7148 -  inserted in and removed from the running kernel whenever you want).
  2.7149 -  The module will be called sr_mod.o. If you want to compile it as a
  2.7150 -  module, say M here and read <file:Documentation/modules.txt> and
  2.7151 -  <file:Documentation/scsi.txt>.
  2.7152 -
  2.7153 -Maximum number of CD-ROM devices that can be loaded as modules
  2.7154 -CONFIG_SR_EXTRA_DEVS
  2.7155 -  This controls the amount of additional space allocated in tables for
  2.7156 -  drivers that are loaded as modules after the kernel is booted. In
  2.7157 -  the event that the SCSI core itself was loaded as a module, this
  2.7158 -  value is the number of additional CD-ROMs that can be loaded after
  2.7159 -  the first host driver is loaded.
  2.7160 -
  2.7161 -  Admittedly this isn't pretty, but there are tons of race conditions
  2.7162 -  involved with resizing the internal arrays on the fly.  Someday this
  2.7163 -  flag will go away, and everything will work automatically.
  2.7164 -
  2.7165 -  If you don't understand what's going on, go with the default.
  2.7166 -
  2.7167 -Enable vendor-specific extensions (for SCSI CD-ROM)
  2.7168 -CONFIG_BLK_DEV_SR_VENDOR
  2.7169 -  This enables the usage of vendor specific SCSI commands. This is
  2.7170 -  required to support multisession CDs with old NEC/TOSHIBA cdrom
  2.7171 -  drives (and HP Writers). If you have such a drive and get the first
  2.7172 -  session only, try saying Y here; everybody else says N.
  2.7173 -
  2.7174 -SCSI generic support
  2.7175 -CONFIG_CHR_DEV_SG
  2.7176 -  If you want to use SCSI scanners, synthesizers or CD-writers or just
  2.7177 -  about anything having "SCSI" in its name other than hard disks,
  2.7178 -  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
  2.7179 -  directly, so you need some additional software which knows how to
  2.7180 -  talk to these devices using the SCSI protocol:
  2.7181 -
  2.7182 -  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
  2.7183 -  writer software look at Cdrtools
  2.7184 -  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
  2.7185 -  and for burning a "disk at once": CDRDAO
  2.7186 -  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
  2.7187 -  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
  2.7188 -  For other devices, it's possible that you'll have to write the
  2.7189 -  driver software yourself. Please read the file
  2.7190 -  <file:Documentation/scsi-generic.txt> for more information.
  2.7191 -
  2.7192 -  If you want to compile this as a module ( = code which can be
  2.7193 -  inserted in and removed from the running kernel whenever you want),
  2.7194 -  say M here and read <file:Documentation/modules.txt> and
  2.7195 -  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
  2.7196 -  say N.
  2.7197 -
  2.7198 -Probe all LUNs on each SCSI device
  2.7199 -CONFIG_SCSI_MULTI_LUN
  2.7200 -  If you have a SCSI device that supports more than one LUN (Logical
  2.7201 -  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
  2.7202 -  can say Y here to force the SCSI driver to probe for multiple LUNs.
  2.7203 -  A SCSI device with multiple LUNs acts logically like multiple SCSI
  2.7204 -  devices. The vast majority of SCSI devices have only one LUN, and
  2.7205 -  so most people can say N here and should in fact do so, because it
  2.7206 -  is safer.
  2.7207 -
  2.7208 -Verbose SCSI error reporting (kernel size +=12K)
  2.7209 -CONFIG_SCSI_CONSTANTS
  2.7210 -  The error messages regarding your SCSI hardware will be easier to
  2.7211 -  understand if you say Y here; it will enlarge your kernel by about
  2.7212 -  12 KB. If in doubt, say Y.
  2.7213 -
  2.7214 -SCSI logging facility
  2.7215 -CONFIG_SCSI_LOGGING
  2.7216 -  This turns on a logging facility that can be used to debug a number
  2.7217 -  of SCSI related problems.
  2.7218 -
  2.7219 -  If you say Y here, no logging output will appear by default, but you
  2.7220 -  can enable logging by saying Y to "/proc file system support" and
  2.7221 -  "Sysctl support" below and executing the command
  2.7222 -
  2.7223 -     echo "scsi log token [level]" > /proc/scsi/scsi
  2.7224 -
  2.7225 -  at boot time after the /proc file system has been mounted.
  2.7226 -
  2.7227 -  There are a number of things that can be used for 'token' (you can
  2.7228 -  find them in the source: <file:drivers/scsi/scsi.c>), and this
  2.7229 -  allows you to select the types of information you want, and the
  2.7230 -  level allows you to select the level of verbosity.
  2.7231 -
  2.7232 -  If you say N here, it may be harder to track down some types of SCSI
  2.7233 -  problems. If you say Y here your kernel will be somewhat larger, but
  2.7234 -  there should be no noticeable performance impact as long as you have
  2.7235 -  logging turned off.
  2.7236 -
  2.7237 -SGI WD93C93 SCSI Driver
  2.7238 -CONFIG_SCSI_SGIWD93
  2.7239 -  Say Y here to support the on-board WD93C93 SCSI controller found (a)
  2.7240 -  on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
  2.7241 -  ARM-based machines.
  2.7242 -
  2.7243 -DEC NCR53C94 SCSI Driver
  2.7244 -CONFIG_SCSI_DECNCR
  2.7245 -  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
  2.7246 -  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
  2.7247 -
  2.7248 -AdvanSys SCSI support
  2.7249 -CONFIG_SCSI_ADVANSYS
  2.7250 -  This is a driver for all SCSI host adapters manufactured by
  2.7251 -  AdvanSys. It is documented in the kernel source in
  2.7252 -  <file:drivers/scsi/advansys.c>.
  2.7253 -
  2.7254 -  This driver is also available as a module ( = code which can be
  2.7255 -  inserted in and removed from the running kernel whenever you want).
  2.7256 -  If you want to compile it as a module, say M here and read
  2.7257 -  <file:Documentation/modules.txt>.  The module will be called
  2.7258 -  advansys.o.
  2.7259 -
  2.7260 -Adaptec AHA152X/2825 support
  2.7261 -CONFIG_SCSI_AHA152X
  2.7262 -  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
  2.7263 -  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
  2.7264 -  must be manually specified in this case.
  2.7265 -
  2.7266 -  It is explained in section 3.3 of the SCSI-HOWTO, available from
  2.7267 -  <http://www.tldp.org/docs.html#howto>. You might also want to
  2.7268 -  read the file <file:drivers/scsi/README.aha152x>.
  2.7269 -
  2.7270 -  This driver is also available as a module ( = code which can be
  2.7271 -  inserted in and removed from the running kernel whenever you want).
  2.7272 -  The module will be called aha152x.o. If you want to compile it as a
  2.7273 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7274 -
  2.7275 -Adaptec AHA1542 support
  2.7276 -CONFIG_SCSI_AHA1542
  2.7277 -  This is support for a SCSI host adapter.  It is explained in section
  2.7278 -  3.4 of the SCSI-HOWTO, available from
  2.7279 -  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
  2.7280 -  purchased by Adaptec, and some former Trantor products are being
  2.7281 -  sold under the Adaptec name.  If it doesn't work out of the box, you
  2.7282 -  may have to change some settings in <file:drivers/scsi/aha1542.h>.
  2.7283 -
  2.7284 -  If you want to compile this as a module ( = code which can be
  2.7285 -  inserted in and removed from the running kernel whenever you want),
  2.7286 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7287 -  will be called aha1542.o.
  2.7288 -
  2.7289 -Adaptec AHA1740 support
  2.7290 -CONFIG_SCSI_AHA1740
  2.7291 -  This is support for a SCSI host adapter.  It is explained in section
  2.7292 -  3.5 of the SCSI-HOWTO, available from
  2.7293 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.7294 -  of the box, you may have to change some settings in
  2.7295 -  <file:drivers/scsi/aha1740.h>.
  2.7296 -
  2.7297 -  This driver is also available as a module ( = code which can be
  2.7298 -  inserted in and removed from the running kernel whenever you want).
  2.7299 -  The module will be called aha1740.o.  If you want to compile it as a
  2.7300 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7301 -
  2.7302 -Adaptec AIC7xxx support
  2.7303 -CONFIG_SCSI_AIC7XXX
  2.7304 -  This driver supports all of Adaptec's PCI based SCSI controllers
  2.7305 -  (not the hardware RAID controllers though) as well as the aic7770
  2.7306 -  based EISA and VLB SCSI controllers (the 274x and 284x series).
  2.7307 -  This is an Adaptec sponsored driver written by Justin Gibbs.  It is
  2.7308 -  intended to replace the previous aic7xxx driver maintained by Doug
  2.7309 -  Ledford since Doug is no longer maintaining that driver.
  2.7310 -
  2.7311 -  If you want to compile the driver as a module ( = code which can be
  2.7312 -  inserted in and removed from the running kernel whenever you want),
  2.7313 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7314 -  will be called aic7xxx.o.
  2.7315 -
  2.7316 -Adaptec I2O RAID support
  2.7317 -CONFIG_SCSI_DPT_I2O
  2.7318 -  This driver supports all of Adaptec's I2O based RAID controllers as 
  2.7319 -  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
  2.7320 -  driver by Deanna Bonds.  See <file:drivers/scsi/README.dpti>.
  2.7321 -
  2.7322 -  This driver is also available as a module ( = code which can be
  2.7323 -  inserted in and removed from the running kernel whenever you want).
  2.7324 -  If you want to compile it as a module, say M here and read
  2.7325 -  <file:Documentation/modules.txt>.  The module will be called
  2.7326 -  dpt_i2o.o.
  2.7327 -
  2.7328 -Default number of TCQ commands per device
  2.7329 -CONFIG_AIC7XXX_CMDS_PER_DEVICE
  2.7330 -  Specify the number of commands you would like to allocate per SCSI
  2.7331 -  device when Tagged Command Queueing (TCQ) is enabled on that device.
  2.7332 -
  2.7333 -  This is an upper bound value for the number of tagged transactions
  2.7334 -  to be used for any device.  The aic7xxx driver will automatically
  2.7335 -  vary this number based on device behaviour.  For devices with a
  2.7336 -  fixed maximum, the driver will eventually lock to this maximum
  2.7337 -  and display a console message indicating this value.
  2.7338 -
  2.7339 -  Note: Unless you experience some type of device failure, the default
  2.7340 -	value, no enforced limit, should work for you.
  2.7341 -
  2.7342 -  Default: 253
  2.7343 -
  2.7344 -Delay in seconds after SCSI bus reset
  2.7345 -CONFIG_AIC7XXX_RESET_DELAY_MS
  2.7346 -  The number of milliseconds to delay after an initial bus reset.
  2.7347 -  The bus settle delay following all error recovery actions is
  2.7348 -  dictated by the SCSI layer and is not affected by this value.
  2.7349 -
  2.7350 -  Default: 15000 (15 seconds)
  2.7351 -
  2.7352 -Build Adapter Firmware with Kernel Build
  2.7353 -CONFIG_AIC7XXX_BUILD_FIRMWARE
  2.7354 -  This option should only be enabled if you are modifying the firmware
  2.7355 -  source to the aic7xxx driver and wish to have the generated firmware
  2.7356 -  include files updated during a normal kernel build.  The assembler
  2.7357 -  for the firmware requires lex and yacc or their equivalents, as well
  2.7358 -  as the db v1 library.  You may have to install additional packages
  2.7359 -  or modify the assembler make file or the files it includes if your
  2.7360 -  build environment is different than that of the author.
  2.7361 -
  2.7362 -Old Adaptec AIC7xxx support
  2.7363 -CONFIG_SCSI_AIC7XXX_OLD
  2.7364 -  WARNING This driver is an older aic7xxx driver and is no longer
  2.7365 -  under active development.  Adaptec, Inc. is writing a new driver to
  2.7366 -  take the place of this one, and it is recommended that whenever
  2.7367 -  possible, people should use the new Adaptec written driver instead
  2.7368 -  of this one.  This driver will eventually be phased out entirely.
  2.7369 -
  2.7370 -  This is support for the various aic7xxx based Adaptec SCSI
  2.7371 -  controllers. These include the 274x EISA cards; 284x VLB cards;
  2.7372 -  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
  2.7373 -  motherboard based SCSI controllers from Adaptec. It does not support
  2.7374 -  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
  2.7375 -  support them. It does not support the 2920 cards from Adaptec that
  2.7376 -  use the Future Domain SCSI controller chip. For those cards, you
  2.7377 -  need the "Future Domain 16xx SCSI support" driver.
  2.7378 -
  2.7379 -  In general, if the controller is based on an Adaptec SCSI controller
  2.7380 -  chip from the aic777x series or the aic78xx series, this driver
  2.7381 -  should work. The only exception is the 7810 which is specifically
  2.7382 -  not supported (that's the RAID controller chip on the AAA-13x
  2.7383 -  cards).
  2.7384 -
  2.7385 -  Note that the AHA2920 SCSI host adapter is *not* supported by this
  2.7386 -  driver; choose "Future Domain 16xx SCSI support" instead if you have
  2.7387 -  one of those.
  2.7388 -
  2.7389 -  Information on the configuration options for this controller can be
  2.7390 -  found by checking the help file for each of the available
  2.7391 -  configuration options. You should read
  2.7392 -  <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
  2.7393 -  contacting the maintainer with any questions.  The SCSI-HOWTO,
  2.7394 -  available from <http://www.tldp.org/docs.html#howto>, can also
  2.7395 -  be of great help.
  2.7396 -
  2.7397 -  If you want to compile this driver as a module ( = code which can be
  2.7398 -  inserted in and removed from the running kernel whenever you want),
  2.7399 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7400 -  will be called aic7xxx_old.o.
  2.7401 -
  2.7402 -Enable tagged command queueing (TCQ) by default
  2.7403 -CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
  2.7404 -  This option causes the aic7xxx driver to attempt to use Tagged
  2.7405 -  Command Queueing (TCQ) on all devices that claim to support it.
  2.7406 -
  2.7407 -  TCQ is a feature of SCSI-2 which improves performance: the host
  2.7408 -  adapter can send several SCSI commands to a device's queue even if
  2.7409 -  previous commands haven't finished yet.  Because the device is
  2.7410 -  intelligent, it can optimize its operations (like head positioning)
  2.7411 -  based on its own request queue.  Not all devices implement this
  2.7412 -  correctly.
  2.7413 -
  2.7414 -  If you say Y here, you can still turn off TCQ on troublesome devices
  2.7415 -  with the use of the tag_info boot parameter.  See the file
  2.7416 -  <file:drivers/scsi/README.aic7xxx> for more information on that and
  2.7417 -  other aic7xxx setup commands.  If this option is turned off, you may
  2.7418 -  still enable TCQ on known good devices by use of the tag_info boot
  2.7419 -  parameter.
  2.7420 -
  2.7421 -  If you are unsure about your devices then it is safest to say N
  2.7422 -  here.
  2.7423 -
  2.7424 -  However, TCQ can increase performance on some hard drives by as much
  2.7425 -  as 50% or more, so it is recommended that if you say N here, you
  2.7426 -  should at least read the <file:drivers/scsi/README.aic7xxx> file so
  2.7427 -  you will know how to enable this option manually should your drives
  2.7428 -  prove to be safe in regards to TCQ.
  2.7429 -
  2.7430 -  Conversely, certain drives are known to lock up or cause bus resets
  2.7431 -  when TCQ is enabled on them.  If you have a Western Digital
  2.7432 -  Enterprise SCSI drive for instance, then don't even bother to enable
  2.7433 -  TCQ on it as the drive will become unreliable, and it will actually
  2.7434 -  reduce performance.
  2.7435 -
  2.7436 -Default number of TCQ commands per device
  2.7437 -CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
  2.7438 -  Specify the number of commands you would like to allocate per SCSI
  2.7439 -  device when Tagged Command Queueing (TCQ) is enabled on that device.
  2.7440 -
  2.7441 -  Reasonable figures are in the range of 8 to 24 commands per device,
  2.7442 -  but depending on hardware could be increased or decreased from that
  2.7443 -  figure. If the number is too high for any particular device, the
  2.7444 -  driver will automatically compensate usually after only 10 minutes
  2.7445 -  of uptime. It will not hinder performance if some of your devices
  2.7446 -  eventually have their command depth reduced, but is a waste of
  2.7447 -  memory if all of your devices end up reducing this number down to a
  2.7448 -  more reasonable figure.
  2.7449 -
  2.7450 -  NOTE: Certain very broken drives are known to lock up when given
  2.7451 -  more commands than they like to deal with. Quantum Fireball drives
  2.7452 -  are the most common in this category. For the Quantum Fireball
  2.7453 -  drives it is suggested to use no more than 8 commands per device.
  2.7454 -
  2.7455 -  Default: 8
  2.7456 -
  2.7457 -Collect statistics to report in /proc
  2.7458 -CONFIG_AIC7XXX_OLD_PROC_STATS
  2.7459 -  This option tells the driver to keep track of how many commands have
  2.7460 -  been sent to each particular device and report that information to
  2.7461 -  the user via the /proc/scsi/aic7xxx/n file, where n is the number of
  2.7462 -  the aic7xxx controller you want the information on. This adds a
  2.7463 -  small amount of overhead to each and every SCSI command the aic7xxx
  2.7464 -  driver handles, so if you aren't really interested in this
  2.7465 -  information, it is best to leave it disabled. This will only work if
  2.7466 -  you also say Y to "/proc file system support", below.
  2.7467 -
  2.7468 -  If unsure, say N.
  2.7469 -
  2.7470 -IBM ServeRAID support
  2.7471 -CONFIG_SCSI_IPS
  2.7472 -  This is support for the IBM ServeRAID hardware RAID controllers.
  2.7473 -  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
  2.7474 -  for more information.  If this driver does not work correctly
  2.7475 -  without modification please contact the author by email at
  2.7476 -  ipslinux@us.ibm.com.
  2.7477 -
  2.7478 -  You can build this driver as a module ( = code which can be
  2.7479 -  inserted in and removed from the running kernel whenever you want),
  2.7480 -  but only a single instance may be loaded. If you want to compile it
  2.7481 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.7482 -  The module will be called ips.o.
  2.7483 -
  2.7484 -BusLogic SCSI support
  2.7485 -CONFIG_SCSI_BUSLOGIC
  2.7486 -  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
  2.7487 -  Adapters. Consult the SCSI-HOWTO, available from
  2.7488 -  <http://www.tldp.org/docs.html#howto>, and the files
  2.7489 -  <file:drivers/scsi/README.BusLogic> and
  2.7490 -  <file:drivers/scsi/README.FlashPoint> for more information. If this
  2.7491 -  driver does not work correctly without modification, please contact
  2.7492 -  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
  2.7493 -
  2.7494 -  You can also build this driver as a module ( = code which can be
  2.7495 -  inserted in and removed from the running kernel whenever you want),
  2.7496 -  but only a single instance may be loaded. If you want to compile it
  2.7497 -  as a module, say M here and read <file:Documentation/modules.txt>.
  2.7498 -  The module will be called BusLogic.o.
  2.7499 -
  2.7500 -Omit BusLogic SCSI FlashPoint support
  2.7501 -CONFIG_SCSI_OMIT_FLASHPOINT
  2.7502 -  This option allows you to omit the FlashPoint support from the
  2.7503 -  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
  2.7504 -  substantial, so users of MultiMaster Host Adapters may wish to omit
  2.7505 -  it.
  2.7506 -
  2.7507 -Compaq Fibre Channel 64-bit/66Mhz HBA support
  2.7508 -CONFIG_SCSI_CPQFCTS
  2.7509 -  Say Y here to compile in support for the Compaq StorageWorks Fibre
  2.7510 -  Channel 64-bit/66Mhz Host Bus Adapter.
  2.7511 -
  2.7512 -  If you want to compile the driver as a module ( = code which can be
  2.7513 -  inserted in and removed from the running kernel whenever you want),
  2.7514 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7515 -  will be called cpqfc.o.
  2.7516 -
  2.7517 -DMX3191D SCSI support
  2.7518 -CONFIG_SCSI_DMX3191D
  2.7519 -  This is support for Domex DMX3191D SCSI Host Adapters.
  2.7520 -
  2.7521 -  This driver is also available as a module ( = code which can be
  2.7522 -  inserted in and removed from the running kernel whenever you want).
  2.7523 -  The module will be called dmx3191d.o.  If you want to compile it as
  2.7524 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.7525 -
  2.7526 -DTC3180/3280 SCSI support
  2.7527 -CONFIG_SCSI_DTC3280
  2.7528 -  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
  2.7529 -  the SCSI-HOWTO, available from
  2.7530 -  <http://www.tldp.org/docs.html#howto>, and the file
  2.7531 -  <file:drivers/scsi/README.dtc3x80>.
  2.7532 -
  2.7533 -  This driver is also available as a module ( = code which can be
  2.7534 -  inserted in and removed from the running kernel whenever you want).
  2.7535 -  The module will be called dtc.o.  If you want to compile it as a
  2.7536 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7537 -
  2.7538 -EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
  2.7539 -CONFIG_SCSI_EATA_DMA
  2.7540 -  This is support for the EATA-DMA protocol compliant SCSI Host
  2.7541 -  Adapters like the SmartCache III/IV, SmartRAID controller families
  2.7542 -  and the DPT PM2011B and PM2012B controllers.
  2.7543 -
  2.7544 -  Note that this driver is obsolete; if you have one of the above
  2.7545 -  SCSI Host Adapters, you should normally say N here and Y to "EATA
  2.7546 -  ISA/EISA/PCI support", below.  Please read the SCSI-HOWTO, available
  2.7547 -  from <http://www.tldp.org/docs.html#howto>.
  2.7548 -
  2.7549 -  This driver is also available as a module ( = code which can be
  2.7550 -  inserted in and removed from the running kernel whenever you want).
  2.7551 -  The module will be called eata_dma.o.  If you want to compile it as
  2.7552 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.7553 -
  2.7554 -EATA-PIO (old DPT PM2001, PM2012A) support
  2.7555 -CONFIG_SCSI_EATA_PIO
  2.7556 -  This driver supports all EATA-PIO protocol compliant SCSI Host
  2.7557 -  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
  2.7558 -  host adapters could also use this driver but are discouraged from
  2.7559 -  doing so, since this driver only supports hard disks and lacks
  2.7560 -  numerous features.  You might want to have a look at the SCSI-HOWTO,
  2.7561 -  available from <http://www.tldp.org/docs.html#howto>.
  2.7562 -
  2.7563 -  If you want to compile this as a module ( = code which can be
  2.7564 -  inserted in and removed from the running kernel whenever you want),
  2.7565 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7566 -  will be called eata_pio.o.
  2.7567 -
  2.7568 -UltraStor 14F/34F support
  2.7569 -CONFIG_SCSI_U14_34F
  2.7570 -  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
  2.7571 -  The source at <file:drivers/scsi/u14-34f.c> contains some
  2.7572 -  information about this hardware.  If the driver doesn't work out of
  2.7573 -  the box, you may have to change some settings in
  2.7574 -  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
  2.7575 -  <http://www.tldp.org/docs.html#howto>.  Note that there is also
  2.7576 -  another driver for the same hardware: "UltraStor SCSI support",
  2.7577 -  below.  You should say Y to both only if you want 24F support as
  2.7578 -  well.
  2.7579 -
  2.7580 -  This driver is also available as a module ( = code which can be
  2.7581 -  inserted in and removed from the running kernel whenever you want).
  2.7582 -  The module will be called u14-34f.o.  If you want to compile it as a
  2.7583 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7584 -
  2.7585 -enable elevator sorting
  2.7586 -CONFIG_SCSI_U14_34F_LINKED_COMMANDS
  2.7587 -  This option enables elevator sorting for all probed SCSI disks and
  2.7588 -  CD-ROMs. It definitely reduces the average seek distance when doing
  2.7589 -  random seeks, but this does not necessarily result in a noticeable
  2.7590 -  performance improvement: your mileage may vary...
  2.7591 -
  2.7592 -  The safe answer is N.
  2.7593 -
  2.7594 -maximum number of queued commands
  2.7595 -CONFIG_SCSI_U14_34F_MAX_TAGS
  2.7596 -  This specifies how many SCSI commands can be maximally queued for
  2.7597 -  each probed SCSI device. You should reduce the default value of 8
  2.7598 -  only if you have disks with buggy or limited tagged command support.
  2.7599 -  Minimum is 2 and maximum is 14. This value is also the window size
  2.7600 -  used by the elevator sorting option above. The effective value used
  2.7601 -  by the driver for each probed SCSI device is reported at boot time.
  2.7602 -
  2.7603 -Future Domain 16xx SCSI/AHA-2920A support
  2.7604 -CONFIG_SCSI_FUTURE_DOMAIN
  2.7605 -  This is support for Future Domain's 16-bit SCSI host adapters
  2.7606 -  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
  2.7607 -  other adapters based on the Future Domain chipsets (Quantum
  2.7608 -  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
  2.7609 -  It is explained in section 3.7 of the SCSI-HOWTO, available from
  2.7610 -  <http://www.tldp.org/docs.html#howto>.
  2.7611 -
  2.7612 -  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
  2.7613 -  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
  2.7614 -  controller support"). This Future Domain driver works with the older
  2.7615 -  Adaptec AHA-2920A boards with a Future Domain chip on them.
  2.7616 -
  2.7617 -  This driver is also available as a module ( = code which can be
  2.7618 -  inserted in and removed from the running kernel whenever you want).
  2.7619 -  The module will be called fdomain.o. If you want to compile it as a
  2.7620 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7621 -
  2.7622 -Future Domain MCS-600/700 SCSI support
  2.7623 -CONFIG_SCSI_FD_MCS
  2.7624 -  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
  2.7625 -  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
  2.7626 -  is identical to the MCS 700 and hence also supported by this driver.
  2.7627 -  This driver also supports the Reply SB16/SCSI card (the SCSI part).
  2.7628 -  It supports multiple adapters in the same system.
  2.7629 -
  2.7630 -  This driver is also available as a module ( = code which can be
  2.7631 -  inserted in and removed from the running kernel whenever you want).
  2.7632 -  The module will be called fd_mcs.o. If you want to compile it as a
  2.7633 -  module, say M here and read <file:Documentation/modules.txt>.
  2.7634 -
  2.7635 -Generic NCR5380/53c400 SCSI support
  2.7636 -CONFIG_SCSI_GENERIC_NCR5380
  2.7637 -  This is the generic NCR family of SCSI controllers, not to be
  2.7638 -  confused with the NCR 53c7 or 8xx controllers.  It is explained in
  2.7639 -  section 3.8 of the SCSI-HOWTO, available from
  2.7640 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.7641 -  of the box, you may have to change some settings in
  2.7642 -  <file:drivers/scsi/g_NCR5380.h>.
  2.7643 -
  2.7644 -  This driver is also available as a module ( = code which can be
  2.7645 -  inserted in and removed from the running kernel whenever you want).
  2.7646 -  The module will be called g_NCR5380.o.  If you want to compile it as
  2.7647 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.7648 -
  2.7649 -Enable NCR53c400 extensions
  2.7650 -CONFIG_SCSI_GENERIC_NCR53C400
  2.7651 -  This enables certain optimizations for the NCR53c400 SCSI cards.
  2.7652 -  You might as well try it out.  Note that this driver will only probe
  2.7653 -  for the Trantor T130B in its default configuration; you might have
  2.7654 -  to pass a command line option to the kernel at boot time if it does
  2.7655 -  not detect your card.  See the file
  2.7656 -  <file:drivers/scsi/README.g_NCR5380> for details.
  2.7657 -
  2.7658 -# Choice: ncr5380
  2.7659 -NCR5380/53c400 mapping method (use Port for T130B)
  2.7660 -CONFIG_SCSI_G_NCR5380_PORT
  2.7661 -  The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
  2.7662 -  port or memory mapped. You should know what you have. The most
  2.7663 -  common card, Trantor T130B, uses port mapped mode.
  2.7664 -
  2.7665 -NCR Dual 700 MCA SCSI support
  2.7666 -CONFIG_SCSI_NCR_D700
  2.7667 -  This is a driver for the MicroChannel Dual 700 card produced by
  2.7668 -  NCR and commonly used in 345x/35xx/4100 class machines.  It always
  2.7669 -  tries to negotiate sync and uses tag command queueing.
  2.7670 -
  2.7671 -  Unless you have an NCR manufactured machine, the chances are that
  2.7672 -  you do not have this SCSI card, so say N.
  2.7673 -
  2.7674 -  If you want to compile the driver as a module ( = code which can be
  2.7675 -  inserted in and removed from the running kernel whenever you want),
  2.7676 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7677 -  will be called NCR_D700.o.
  2.7678 -
  2.7679 -HP LASI SCSI support for 53c700/710
  2.7680 -CONFIG_SCSI_LASI700
  2.7681 -  This is a driver for the lasi baseboard in some parisc machines
  2.7682 -  which is based on the 53c700 chip.  Will also support LASI subsystems
  2.7683 -  based on the 710 chip using 700 emulation mode.
  2.7684 -
  2.7685 -  Unless you know you have a 53c700 or 53c710 based lasi, say N here
  2.7686 -
  2.7687 -NCR53c7,8xx SCSI support
  2.7688 -CONFIG_SCSI_NCR53C7xx
  2.7689 -  This is a driver for the 53c7 and 8xx NCR family of SCSI
  2.7690 -  controllers, not to be confused with the NCR 5380 controllers.  It
  2.7691 -  is explained in section 3.8 of the SCSI-HOWTO, available from
  2.7692 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.7693 -  of the box, you may have to change some settings in
  2.7694 -  <file:drivers/scsi/53c7,8xx.h>.  Please read
  2.7695 -  <file:drivers/scsi/README.ncr53c7xx> for the available boot time
  2.7696 -  command line options.
  2.7697 -
  2.7698 -  Note: there is another driver for the 53c8xx family of controllers
  2.7699 -  ("NCR53C8XX SCSI support" below).  If you want to use them both, you
  2.7700 -  need to say M to both and build them as modules, but only one may be
  2.7701 -  active at a time. If you have a 53c8xx board, it's better to use the
  2.7702 -  other driver.
  2.7703 -
  2.7704 -  This driver is also available as a module ( = code which can be
  2.7705 -  inserted in and removed from the running kernel whenever you want).
  2.7706 -  The module will be called 53c7,8xx.o.  If you want to compile it as
  2.7707 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.7708 -
  2.7709 -Always negotiate synchronous transfers
  2.7710 -CONFIG_SCSI_NCR53C7xx_sync
  2.7711 -  In general, this is good; however, it is a bit dangerous since there
  2.7712 -  are some broken SCSI devices out there. Take your chances. Safe bet
  2.7713 -  is N.
  2.7714 -
  2.7715 -Allow FAST-SCSI [10MHz]
  2.7716 -CONFIG_SCSI_NCR53C7xx_FAST
  2.7717 -  This will enable 10MHz FAST-SCSI transfers with your host
  2.7718 -  adapter. Some systems have problems with that speed, so it's safest
  2.7719 -  to say N here.
  2.7720 -
  2.7721 -Allow DISCONNECT
  2.7722 -CONFIG_SCSI_NCR53C7xx_DISCONNECT
  2.7723 -  This enables the disconnect/reconnect feature of the NCR SCSI
  2.7724 -  controller. When you say Y here, a slow SCSI device will not lock
  2.7725 -  the SCSI bus while processing a request, allowing simultaneous use
  2.7726 -  of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
  2.7727 -  providing much better performance when using slow and fast SCSI
  2.7728 -  devices at the same time. Some devices, however, do not operate
  2.7729 -  properly with this option enabled, and will cause your SCSI system
  2.7730 -  to hang, which might cause a system crash. The safe answer
  2.7731 -  therefore is to say N.
  2.7732 -
  2.7733 -SYM53C8XX Version 2 SCSI support
  2.7734 -CONFIG_SCSI_SYM53C8XX_2
  2.7735 -  This driver supports the whole NCR53C8XX/SYM53C8XX family of 
  2.7736 -  PCI-SCSI controllers. It also supports the subset of LSI53C10XX 
  2.7737 -  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS 
  2.7738 -  language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI 
  2.7739 -  controllers.
  2.7740 -
  2.7741 -  If your system has problems using this new major version of the
  2.7742 -  SYM53C8XX driver, you may switch back to driver version 1.
  2.7743 -
  2.7744 -  Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
  2.7745 -  information.
  2.7746 -
  2.7747 -  If you want to compile the driver as a module ( = code which can be
  2.7748 -  inserted in and removed from the running kernel whenever you want),
  2.7749 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7750 -  will be called sym53c8xx.o.
  2.7751 -
  2.7752 -PCI DMA addressing mode
  2.7753 -CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
  2.7754 -  This option only applies to PCI-SCSI chip that are PCI DAC capable 
  2.7755 -  (875A, 895A, 896, 1010-33, 1010-66, 1000).
  2.7756 -
  2.7757 -  When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
  2.7758 -  When set to 1, 40 bit DMA addressing (with upper 24 bits of address 
  2.7759 -  set to zero) is supported. The addressable range is here 1 TB.
  2.7760 -  When set to 2, full 64 bits of address for DMA are supported, but only
  2.7761 -  16 segments of 4 GB can be addressed. The addressable range is so 
  2.7762 -  limited to 64 GB.
  2.7763 -
  2.7764 -  The safest value is 0 (32 bit DMA addressing) that is guessed to still 
  2.7765 -  fit most of real machines.
  2.7766 -
  2.7767 -  The preferred value 1 (40 bit DMA addressing) should make happy 
  2.7768 -  properly engineered PCI DAC capable host bridges. You may configure
  2.7769 -  this option for Intel platforms with more than 4 GB of memory.
  2.7770 -
  2.7771 -  The still experimental value 2 (64 bit DMA addressing with 16 x 4GB 
  2.7772 -  segments limitation) can be used on systems that require PCI address 
  2.7773 -  bits past bit 39 to be set for the addressing of memory using PCI 
  2.7774 -  DAC cycles.
  2.7775 -
  2.7776 -use normal IO
  2.7777 -CONFIG_SCSI_SYM53C8XX_IOMAPPED
  2.7778 -  If you say Y here, the driver will preferently use normal IO rather than 
  2.7779 -  memory mapped IO.
  2.7780 -
  2.7781 -maximum number of queued commands
  2.7782 -CONFIG_SCSI_SYM53C8XX_MAX_TAGS
  2.7783 -  This option allows you to specify the maximum number of commands
  2.7784 -  that can be queued to any device, when tagged command queuing is
  2.7785 -  possible. The driver supports up to 256 queued commands per device.
  2.7786 -  This value is used as a compiled-in hard limit.
  2.7787 -
  2.7788 -default tagged command queue depth
  2.7789 -CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS
  2.7790 -  This is the default value of the command queue depth the driver will 
  2.7791 -  announce to the generic SCSI layer for devices that support tagged 
  2.7792 -  command queueing. This value can be changed from the boot command line.
  2.7793 -  This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
  2.7794 -
  2.7795 -NCR53C8XX SCSI support
  2.7796 -CONFIG_SCSI_NCR53C8XX
  2.7797 -  This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
  2.7798 -  of PCI-SCSI controllers.  This driver supports parity checking,
  2.7799 -  tagged command queuing and fast synchronous data transfers up to 80
  2.7800 -  MB/s with wide FAST-40 LVD devices and controllers.
  2.7801 -
  2.7802 -  Recent versions of the 53C8XX chips are better supported by the
  2.7803 -  option "SYM53C8XX SCSI support", below.
  2.7804 -
  2.7805 -  Note: there is yet another driver for the 53c8xx family of
  2.7806 -  controllers ("NCR53c7,8xx SCSI support" above).  If you want to use
  2.7807 -  them both, you need to say M to both and build them as modules, but
  2.7808 -  only one may be active at a time.  If you have a 53c8xx board, you
  2.7809 -  probably do not want to use the "NCR53c7,8xx SCSI support".
  2.7810 -
  2.7811 -  Please read <file:drivers/scsi/README.ncr53c8xx> for more
  2.7812 -  information.
  2.7813 -
  2.7814 -  If you want to compile the driver as a module ( = code which can be
  2.7815 -  inserted in and removed from the running kernel whenever you want),
  2.7816 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7817 -  will be called ncr53c8xx.o.
  2.7818 -
  2.7819 -SYM53C8XX Version 1 SCSI support
  2.7820 -CONFIG_SCSI_SYM53C8XX
  2.7821 -  This driver supports all the features of recent 53C8XX chips (used
  2.7822 -  in PCI SCSI controllers), notably the hardware phase mismatch
  2.7823 -  feature of the SYM53C896.
  2.7824 -
  2.7825 -  Older versions of the 53C8XX chips are not supported by this
  2.7826 -  driver.  If your system uses either a 810 rev. < 16, a 815, or a 825
  2.7827 -  rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
  2.7828 -  driver ("NCR53C8XX SCSI support" above) or configure both the
  2.7829 -  NCR53C8XX and this SYM53C8XX drivers either as module or linked to
  2.7830 -  the kernel image.
  2.7831 -
  2.7832 -  When both drivers are linked into the kernel, the SYM53C8XX driver
  2.7833 -  is called first at initialization and you can use the 'excl=ioaddr'
  2.7834 -  driver boot option to exclude attachment of adapters by the
  2.7835 -  SYM53C8XX driver.  For example, entering
  2.7836 -  'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
  2.7837 -  adapters at io address 0xb400 and 0xc000 from being attached by the
  2.7838 -  SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
  2.7839 -  The 'excl' option is also supported by the NCR53C8XX driver.
  2.7840 -
  2.7841 -  Please read <file:drivers/scsi/README.ncr53c8xx> for more
  2.7842 -  information.
  2.7843 -
  2.7844 -  If you want to compile the driver as a module ( = code which can be
  2.7845 -  inserted in and removed from the running kernel whenever you want),
  2.7846 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7847 -  will be called sym53c8xx.o.
  2.7848 -
  2.7849 -Synchronous transfer frequency in MHz
  2.7850 -CONFIG_SCSI_NCR53C8XX_SYNC
  2.7851 -  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
  2.7852 -  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
  2.7853 -  are respectively the maximum data transfer rates in mega-transfers
  2.7854 -  per second for each class.  For example, a FAST-20 Wide 16 device is
  2.7855 -  able to transfer data at 20 million 16 bit packets per second for a
  2.7856 -  total rate of 40 MB/s.
  2.7857 -
  2.7858 -  You may specify 0 if you want to only use asynchronous data
  2.7859 -  transfers. This is the safest and slowest option. Otherwise, specify
  2.7860 -  a value between 5 and 80, depending on the capability of your SCSI
  2.7861 -  controller.  The higher the number, the faster the data transfer.
  2.7862 -  Note that 80 should normally be ok since the driver decreases the
  2.7863 -  value automatically according to the controller's capabilities.
  2.7864 -
  2.7865 -  Your answer to this question is ignored for controllers with NVRAM,
  2.7866 -  since the driver will get this information from the user set-up.  It
  2.7867 -  also can be overridden using a boot setup option, as follows
  2.7868 -  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
  2.7869 -  for FAST-20 synchronous data transfer (20 mega-transfers per
  2.7870 -  second).
  2.7871 -
  2.7872 -  The normal answer therefore is not to go with the default but to
  2.7873 -  select the maximum value 80 allowing the driver to use the maximum
  2.7874 -  value supported by each controller. If this causes problems with
  2.7875 -  your SCSI devices, you should come back and decrease the value.
  2.7876 -
  2.7877 -  There is no safe option other than using good cabling, right
  2.7878 -  terminations and SCSI conformant devices.
  2.7879 -
  2.7880 -Use normal IO
  2.7881 -CONFIG_SCSI_NCR53C8XX_IOMAPPED
  2.7882 -  If you say Y here, the driver will use normal IO, as opposed to
  2.7883 -  memory mapped IO. Memory mapped IO has less latency than normal IO
  2.7884 -  and works for most Intel-based hardware. Under Linux/Alpha only
  2.7885 -  normal IO is currently supported by the driver and so, this option
  2.7886 -  has no effect on those systems.
  2.7887 -
  2.7888 -  The normal answer therefore is N; try Y only if you encounter SCSI
  2.7889 -  related problems.
  2.7890 -
  2.7891 -Not allow targets to disconnect
  2.7892 -CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
  2.7893 -  This option is only provided for safety if you suspect some SCSI
  2.7894 -  device of yours to not support properly the target-disconnect
  2.7895 -  feature. In that case, you would say Y here. In general however, to
  2.7896 -  not allow targets to disconnect is not reasonable if there is more
  2.7897 -  than 1 device on a SCSI bus. The normal answer therefore is N.
  2.7898 -
  2.7899 -Default tagged command queue depth
  2.7900 -CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
  2.7901 -  "Tagged command queuing" is a feature of SCSI-2 which improves
  2.7902 -  performance: the host adapter can send several SCSI commands to a
  2.7903 -  device's queue even if previous commands haven't finished yet.
  2.7904 -  Because the device is intelligent, it can optimize its operations
  2.7905 -  (like head positioning) based on its own request queue. Some SCSI
  2.7906 -  devices don't implement this properly; if you want to disable this
  2.7907 -  feature, enter 0 or 1 here (it doesn't matter which).
  2.7908 -
  2.7909 -  The default value is 8 and should be supported by most hard disks.
  2.7910 -  This value can be overridden from the boot command line using the
  2.7911 -  'tags' option as follows (example):
  2.7912 -  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
  2.7913 -  4, set queue depth to 16 for target 2 and target 3 on controller 0
  2.7914 -  and set queue depth to 10 for target 0 / lun 2 on controller 1.
  2.7915 -
  2.7916 -  The normal answer therefore is to go with the default 8 and to use
  2.7917 -  a boot command line option for devices that need to use a different
  2.7918 -  command queue depth.
  2.7919 -
  2.7920 -  There is no safe option other than using good SCSI devices.
  2.7921 -
  2.7922 -Maximum number of queued commands
  2.7923 -CONFIG_SCSI_NCR53C8XX_MAX_TAGS
  2.7924 -  This option allows you to specify the maximum number of commands
  2.7925 -  that can be queued to any device, when tagged command queuing is
  2.7926 -  possible. The default value is 32. Minimum is 2, maximum is 64.
  2.7927 -  Modern hard disks are able to support 64 tags and even more, but
  2.7928 -  do not seem to be faster when more than 32 tags are being used.
  2.7929 -
  2.7930 -  So, the normal answer here is to go with the default value 32 unless
  2.7931 -  you are using very large hard disks with large cache (>= 1 MB) that
  2.7932 -  are able to take advantage of more than 32 tagged commands.
  2.7933 -
  2.7934 -  There is no safe option and the default answer is recommended.
  2.7935 -
  2.7936 -Assume boards are SYMBIOS compatible
  2.7937 -CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
  2.7938 -  This option allows you to enable some features depending on GPIO
  2.7939 -  wiring. These General Purpose Input/Output pins can be used for
  2.7940 -  vendor specific features or implementation of the standard SYMBIOS
  2.7941 -  features. Genuine SYMBIOS controllers use GPIO0 in output for
  2.7942 -  controller LED and GPIO3 bit as a flag indicating
  2.7943 -  singled-ended/differential interface. The Tekram DC-390U/F boards
  2.7944 -  uses a different GPIO wiring.
  2.7945 -
  2.7946 -  Your answer to this question is ignored if all your controllers have
  2.7947 -  NVRAM, since the driver is able to detect the board type from the
  2.7948 -  NVRAM format.
  2.7949 -
  2.7950 -  If all the controllers in your system are genuine SYMBIOS boards or
  2.7951 -  use BIOS and drivers from SYMBIOS, you would want to say Y here,
  2.7952 -  otherwise N. N is the safe answer.
  2.7953 -
  2.7954 -Enable traffic profiling
  2.7955 -CONFIG_SCSI_NCR53C8XX_PROFILE
  2.7956 -  This option allows you to enable profiling information gathering.
  2.7957 -  These statistics are not very accurate due to the low frequency
  2.7958 -  of the kernel clock (100 Hz on i386) and have performance impact
  2.7959 -  on systems that use very fast devices.
  2.7960 -
  2.7961 -  The normal answer therefore is N.
  2.7962 -
  2.7963 -Include support for the NCR PQS/PDS SCSI card
  2.7964 -CONFIG_SCSI_NCR53C8XX_PQS_PDS
  2.7965 -  Say Y here if you have a special SCSI adapter produced by NCR
  2.7966 -  corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
  2.7967 -  this if you do not have one of these adapters. However, since this
  2.7968 -  device is detected as a specific PCI device, this option is quite
  2.7969 -  safe.
  2.7970 -
  2.7971 -  The common answer here is N, but answering Y is safe.
  2.7972 -
  2.7973 -Workbit NinjaSCSI-32Bi/UDE support
  2.7974 -CONFIG_SCSI_NSP32
  2.7975 -  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
  2.7976 -  SCSI host adapter. Please read the SCSI-HOWTO, available from
  2.7977 -  <http://www.linuxdoc.org/docs.html#howto>.
  2.7978 -
  2.7979 -  If you want to compile this as a module ( = code which can be
  2.7980 -  inserted in and removed from the running kernel whenever you want),
  2.7981 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.7982 -  will be called nsp32.o.
  2.7983 -
  2.7984 -IBMMCA SCSI support
  2.7985 -CONFIG_SCSI_IBMMCA
  2.7986 -  This is support for the IBM SCSI adapter found in many of the PS/2
  2.7987 -  series computers.  These machines have an MCA bus, so you need to
  2.7988 -  answer Y to "MCA support" as well and read
  2.7989 -  <file:Documentation/mca.txt>.
  2.7990 -
  2.7991 -  If the adapter isn't found during boot (a common problem for models
  2.7992 -  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
  2.7993 -  option, where <pun> is the id of the SCSI subsystem (usually 7, but
  2.7994 -  if that doesn't work check your reference diskette).  Owners of
  2.7995 -  model 95 with a LED-matrix-display can in addition activate some
  2.7996 -  activity info like under OS/2, but more informative, by setting
  2.7997 -  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
  2.7998 -  bootparam" or see the documentation of your boot loader about how to
  2.7999 -  pass options to the kernel.
  2.8000 -
  2.8001 -  If you want to compile this driver as a module ( = code which can be
  2.8002 -  inserted in and removed from the running kernel whenever you want),
  2.8003 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8004 -  will be called ibmmca.o.
  2.8005 -
  2.8006 -Standard SCSI-order
  2.8007 -CONFIG_IBMMCA_SCSI_ORDER_STANDARD
  2.8008 -  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
  2.8009 -  are assigned to the drive letters, starting with the lowest SCSI-id
  2.8010 -  (physical number -- pun) to be drive C:, as seen from DOS and
  2.8011 -  similar operating systems. When looking into papers describing the
  2.8012 -  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
  2.8013 -  The SCSI-standard follows a hardware-hierarchy which says that id 7
  2.8014 -  has the highest priority and id 0 the lowest. Therefore, the host
  2.8015 -  adapters are still today everywhere placed as SCSI-id 7 by default.
  2.8016 -  In the SCSI-standard, the drive letters express the priority of the
  2.8017 -  disk. C: should be the hard disk, or a partition on it, with the
  2.8018 -  highest priority. This must therefore be the disk with the highest
  2.8019 -  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
  2.8020 -  original definition of the SCSI-standard as also industrial- and
  2.8021 -  process-control-machines, like VME-CPUs running under realtime-OSes
  2.8022 -  (e.g. LynxOS, OS9) do.
  2.8023 -
  2.8024 -  If you like to run Linux on your MCA-machine with the same
  2.8025 -  assignment of hard disks as seen from e.g. DOS or OS/2 on your
  2.8026 -  machine, which is in addition conformant to the SCSI-standard, you
  2.8027 -  must say Y here. This is also necessary for MCA-Linux users who want
  2.8028 -  to keep downward compatibility to older releases of the
  2.8029 -  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
  2.8030 -  June 1997).
  2.8031 -
  2.8032 -  If you like to have the lowest SCSI-id assigned as drive C:, as
  2.8033 -  modern SCSI-BIOSes do, which does not conform to the standard, but
  2.8034 -  is widespread and common in the PC-world of today, you must say N
  2.8035 -  here. If unsure, say Y.
  2.8036 -
  2.8037 -Reset SCSI-devices at boot time
  2.8038 -CONFIG_IBMMCA_SCSI_DEV_RESET
  2.8039 -  By default, SCSI-devices are reset when the machine is powered on.
  2.8040 -  However, some devices exist, like special-control-devices,
  2.8041 -  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
  2.8042 -  not reset when switched on. If you say Y here, each device connected
  2.8043 -  to your SCSI-bus will be issued a reset-command after it has been
  2.8044 -  probed, while the kernel is booting. This may cause problems with
  2.8045 -  more modern devices, like hard disks, which do not appreciate these
  2.8046 -  reset commands, and can cause your system to hang. So say Y only if
  2.8047 -  you know that one of your older devices needs it; N is the safe
  2.8048 -  answer.
  2.8049 -
  2.8050 -NCR MCA 53C9x SCSI support
  2.8051 -CONFIG_SCSI_MCA_53C9X
  2.8052 -  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
  2.8053 -  controller based on the NCR 53C94.  This driver will allow use of
  2.8054 -  the controller on the 3550, and very possibly others.
  2.8055 -
  2.8056 -  If you want to compile this as a module (= code which can be
  2.8057 -  inserted and removed from the running kernel whenever you want), say
  2.8058 -  M here and read <file:Documentation/modules.txt>.  The module will
  2.8059 -  be called mca_53c9x.o.
  2.8060 -
  2.8061 -Always IN2000 SCSI support
  2.8062 -CONFIG_SCSI_IN2000
  2.8063 -  This is support for an ISA bus SCSI host adapter.  You'll find more
  2.8064 -  information in <file:drivers/scsi/README.in2000>. If it doesn't work
  2.8065 -  out of the box, you may have to change the jumpers for IRQ or
  2.8066 -  address selection.
  2.8067 -
  2.8068 -  If you want to compile this as a module ( = code which can be
  2.8069 -  inserted in and removed from the running kernel whenever you want),
  2.8070 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8071 -  will be called in2000.o.
  2.8072 -
  2.8073 -Initio 91XXU(W) SCSI support
  2.8074 -CONFIG_SCSI_INITIO
  2.8075 -  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
  2.8076 -  read the SCSI-HOWTO, available from
  2.8077 -  <http://www.tldp.org/docs.html#howto>.
  2.8078 -
  2.8079 -  If you want to compile this as a module ( = code which can be
  2.8080 -  inserted in and removed from the running kernel whenever you want),
  2.8081 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8082 -  will be called initio.o.
  2.8083 -
  2.8084 -PAS16 SCSI support
  2.8085 -CONFIG_SCSI_PAS16
  2.8086 -  This is support for a SCSI host adapter.  It is explained in section
  2.8087 -  3.10 of the SCSI-HOWTO, available from
  2.8088 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.8089 -  of the box, you may have to change some settings in
  2.8090 -  <file:drivers/scsi/pas16.h>.
  2.8091 -
  2.8092 -  This driver is also available as a module ( = code which can be
  2.8093 -  inserted in and removed from the running kernel whenever you want).
  2.8094 -  The module will be called pas16.o.  If you want to compile it as a
  2.8095 -  module, say M here and read <file:Documentation/modules.txt>.
  2.8096 -
  2.8097 -Initio INI-A100U2W SCSI support
  2.8098 -CONFIG_SCSI_INIA100
  2.8099 -  This is support for the Initio INI-A100U2W SCSI host adapter.
  2.8100 -  Please read the SCSI-HOWTO, available from
  2.8101 -  <http://www.tldp.org/docs.html#howto>.
  2.8102 -
  2.8103 -  If you want to compile this as a module ( = code which can be
  2.8104 -  inserted in and removed from the running kernel whenever you want),
  2.8105 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8106 -  will be called a100u2w.o.
  2.8107 -
  2.8108 -PCI2000 support
  2.8109 -CONFIG_SCSI_PCI2000
  2.8110 -  This is support for the PCI2000I EIDE interface card which acts as a
  2.8111 -  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  2.8112 -  <http://www.tldp.org/docs.html#howto>.
  2.8113 -
  2.8114 -  This driver is also available as a module called pci2000.o ( = code
  2.8115 -  which can be inserted in and removed from the running kernel
  2.8116 -  whenever you want).  If you want to compile it as a module, say M
  2.8117 -  here and read <file:Documentation/modules.txt>.
  2.8118 -
  2.8119 -PCI2220i support
  2.8120 -CONFIG_SCSI_PCI2220I
  2.8121 -  This is support for the PCI2220i EIDE interface card which acts as a
  2.8122 -  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  2.8123 -  <http://www.tldp.org/docs.html#howto>.
  2.8124 -
  2.8125 -  This driver is also available as a module called pci2220i.o ( = code
  2.8126 -  which can be inserted in and removed from the running kernel
  2.8127 -  whenever you want).  If you want to compile it as a module, say M
  2.8128 -  here and read <file:Documentation/modules.txt>.
  2.8129 -
  2.8130 -PSI240i support
  2.8131 -CONFIG_SCSI_PSI240I
  2.8132 -  This is support for the PSI240i EIDE interface card which acts as a
  2.8133 -  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  2.8134 -  <http://www.tldp.org/docs.html#howto>.
  2.8135 -
  2.8136 -  This driver is also available as a module called psi240i.o ( = code
  2.8137 -  which can be inserted in and removed from the running kernel
  2.8138 -  whenever you want).  If you want to compile it as a module, say M
  2.8139 -  here and read <file:Documentation/modules.txt>.
  2.8140 -
  2.8141 -Qlogic FAS SCSI support
  2.8142 -CONFIG_SCSI_QLOGIC_FAS
  2.8143 -  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
  2.8144 -  FastSCSI! cards as well as any other card based on the FASXX chip
  2.8145 -  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
  2.8146 -
  2.8147 -  This driver does NOT support the PCI versions of these cards. The
  2.8148 -  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
  2.8149 -  SCSI support"), below.
  2.8150 -
  2.8151 -  Information about this driver is contained in
  2.8152 -  <file:drivers/scsi/README.qlogicfas>.  You should also read the
  2.8153 -  SCSI-HOWTO, available from
  2.8154 -  <http://www.tldp.org/docs.html#howto>.
  2.8155 -
  2.8156 -  This driver is also available as a module ( = code which can be
  2.8157 -  inserted in and removed from the running kernel whenever you want).
  2.8158 -  The module will be called qlogicfas.o. If you want to compile it as
  2.8159 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.8160 -
  2.8161 -Qlogic ISP SCSI support
  2.8162 -CONFIG_SCSI_QLOGIC_ISP
  2.8163 -  This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
  2.8164 -  IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card.  (This latter
  2.8165 -  card is supported by the "AM53/79C974 PCI SCSI" driver.)
  2.8166 -
  2.8167 -  If you say Y here, make sure to choose "BIOS" at the question "PCI
  2.8168 -  access mode".
  2.8169 -
  2.8170 -  Please read the file <file:drivers/scsi/README.qlogicisp>.  You
  2.8171 -  should also read the SCSI-HOWTO, available from
  2.8172 -  <http://www.tldp.org/docs.html#howto>.
  2.8173 -
  2.8174 -  This driver is also available as a module ( = code which can be
  2.8175 -  inserted in and removed from the running kernel whenever you want).
  2.8176 -  The module will be called qlogicisp.o.  If you want to compile it as
  2.8177 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.8178 -
  2.8179 -Qlogic ISP FC SCSI support
  2.8180 -CONFIG_SCSI_QLOGIC_FC
  2.8181 -  This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
  2.8182 -
  2.8183 -  This driver is also available as a module ( = code which can be
  2.8184 -  inserted in and removed from the running kernel whenever you want).
  2.8185 -  The module will be called qlogicfc.o.  If you want to compile it as
  2.8186 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.8187 -
  2.8188 -Include loadable firmware in driver
  2.8189 -CONFIG_SCSI_QLOGIC_FC_FIRMWARE
  2.8190 -  Say Y to include ISP2100 Fabric Initiator/Target Firmware, with
  2.8191 -  expanded LUN addressing and FcTape (FCP-2) support, in the
  2.8192 -  Qlogic QLA 1280 driver. This is required on some platforms.
  2.8193 -
  2.8194 -Qlogic QLA 1280 SCSI support
  2.8195 -CONFIG_SCSI_QLOGIC_1280
  2.8196 -  Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
  2.8197 -
  2.8198 -  This driver is also available as a module ( = code which can be
  2.8199 -  inserted in and removed from the running kernel whenever you want).
  2.8200 -  The module will be called qla1280.o. If you want to compile it as
  2.8201 -  a module, say M here and read <file:Documentation/modules.txt>.
  2.8202 -
  2.8203 -Seagate ST-02 and Future Domain TMC-8xx SCSI support
  2.8204 -CONFIG_SCSI_SEAGATE
  2.8205 -  These are 8-bit SCSI controllers; the ST-01 is also supported by
  2.8206 -  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
  2.8207 -  available from <http://www.tldp.org/docs.html#howto>.  If it
  2.8208 -  doesn't work out of the box, you may have to change some settings in
  2.8209 -  <file:drivers/scsi/seagate.h>.
  2.8210 -
  2.8211 -  This driver is also available as a module ( = code which can be
  2.8212 -  inserted in and removed from the running kernel whenever you want).
  2.8213 -  The module will be called seagate.o.  If you want to compile it as a
  2.8214 -  module, say M here and read <file:Documentation/modules.txt>.
  2.8215 -
  2.8216 -Trantor T128/T128F/T228 SCSI support
  2.8217 -CONFIG_SCSI_T128
  2.8218 -  This is support for a SCSI host adapter. It is explained in section
  2.8219 -  3.11 of the SCSI-HOWTO, available from
  2.8220 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.8221 -  of the box, you may have to change some settings in
  2.8222 -  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
  2.8223 -  Adaptec, and some former Trantor products are being sold under the
  2.8224 -  Adaptec name.
  2.8225 -
  2.8226 -  This driver is also available as a module ( = code which can be
  2.8227 -  inserted in and removed from the running kernel whenever you want).
  2.8228 -  The module will be called t128.o.  If you want to compile it as a
  2.8229 -  module, say M here and read <file:Documentation/modules.txt>.
  2.8230 -
  2.8231 -UltraStor SCSI support
  2.8232 -CONFIG_SCSI_ULTRASTOR
  2.8233 -  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
  2.8234 -  adapter family.  This driver is explained in section 3.12 of the
  2.8235 -  SCSI-HOWTO, available from
  2.8236 -  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  2.8237 -  of the box, you may have to change some settings in
  2.8238 -  <file:drivers/scsi/ultrastor.h>.
  2.8239 -
  2.8240 -  Note that there is also another driver for the same hardware:
  2.8241 -  "UltraStor 14F/34F support", above.
  2.8242 -
  2.8243 -  If you want to compile this as a module ( = code which can be
  2.8244 -  inserted in and removed from the running kernel whenever you want),
  2.8245 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8246 -  will be called ultrastor.o.
  2.8247 -
  2.8248 -7000FASST SCSI support
  2.8249 -CONFIG_SCSI_7000FASST
  2.8250 -  This driver supports the Western Digital 7000 SCSI host adapter
  2.8251 -  family.  Some information is in the source:
  2.8252 -  <file:drivers/scsi/wd7000.c>.
  2.8253 -
  2.8254 -  This driver is also available as a module ( = code which can be
  2.8255 -  inserted in and removed from the running kernel whenever you want).
  2.8256 -  The module will be called wd7000.o.  If you want to compile it as a
  2.8257 -  module, say M here and read <file:Documentation/modules.txt>.
  2.8258 -
  2.8259 -ACARD SCSI support
  2.8260 -CONFIG_SCSI_ACARD
  2.8261 -  This driver supports the ACARD 870U/W SCSI host adapter.
  2.8262 -
  2.8263 -  This driver is also available as a module ( = code which can be
  2.8264 -  inserted in and removed from the running kernel whenever you want).
  2.8265 -  The module will be called atp870u.o. If you want to compile it as a
  2.8266 -  module, say M here and read <file:Documentation/modules.txt>.
  2.8267 -
  2.8268 -EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
  2.8269 -CONFIG_SCSI_EATA
  2.8270 -  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
  2.8271 -  ISA and all EISA I/O addresses are probed looking for the "EATA"
  2.8272 -  signature.  If you chose "BIOS" at the question "PCI access mode",
  2.8273 -  the addresses of all the PCI SCSI controllers reported by the PCI
  2.8274 -  subsystem are probed as well.
  2.8275 -
  2.8276 -  You want to read the start of <file:drivers/scsi/eata.c> and the
  2.8277 -  SCSI-HOWTO, available from
  2.8278 -  <http://www.tldp.org/docs.html#howto>.
  2.8279 -
  2.8280 -  Note that there is also another driver for the same hardware
  2.8281 -  available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
  2.8282 -  Alphatronix) support". You should say Y to only one of them.
  2.8283 -
  2.8284 -  If you want to compile this as a module ( = code which can be
  2.8285 -  inserted in and removed from the running kernel whenever you want),
  2.8286 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8287 -  will be called eata.o.
  2.8288 -
  2.8289 -enable tagged command queueing
  2.8290 -CONFIG_SCSI_EATA_TAGGED_QUEUE
  2.8291 -  This is a feature of SCSI-2 which improves performance: the host
  2.8292 -  adapter can send several SCSI commands to a device's queue even if
  2.8293 -  previous commands haven't finished yet. Most EATA adapters negotiate
  2.8294 -  this feature automatically with the device, even if your answer is
  2.8295 -  N. The safe answer is N.
  2.8296 -
  2.8297 -enable elevator sorting
  2.8298 -CONFIG_SCSI_EATA_LINKED_COMMANDS
  2.8299 -  This option enables elevator sorting for all probed SCSI disks and
  2.8300 -  CD-ROMs. It definitely reduces the average seek distance when doing
  2.8301 -  random seeks, but this does not necessarily result in a noticeable
  2.8302 -  performance improvement: your mileage may vary...
  2.8303 -  The safe answer is N.
  2.8304 -
  2.8305 -maximum number of queued commands
  2.8306 -CONFIG_SCSI_EATA_MAX_TAGS
  2.8307 -  This specifies how many SCSI commands can be maximally queued for
  2.8308 -  each probed SCSI device. You should reduce the default value of 16
  2.8309 -  only if you have disks with buggy or limited tagged command support.
  2.8310 -  Minimum is 2 and maximum is 62. This value is also the window size
  2.8311 -  used by the elevator sorting option above. The effective value used
  2.8312 -  by the driver for each probed SCSI device is reported at boot time.
  2.8313 -
  2.8314 -NCR53c406a SCSI support
  2.8315 -CONFIG_SCSI_NCR53C406A
  2.8316 -  This is support for the NCR53c406a SCSI host adapter.  For user
  2.8317 -  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
  2.8318 -  in the kernel source.  Also read the SCSI-HOWTO, available from
  2.8319 -  <http://www.tldp.org/docs.html#howto>.
  2.8320 -
  2.8321 -  If you want to compile this driver as a module ( = code which can be
  2.8322 -  inserted in and removed from the running kernel whenever you want),
  2.8323 -  say M here and read <file:Documentation/modules.txt>.  The module
  2.8324 -  will be called NCR53c406.o.
  2.8325 -
  2.8326 -Symbios 53c416 SCSI support
  2.8327 -CONFIG_SCSI_SYM53C416
  2.8328 -  This is support for the sym53c416 SCSI host adapter, the SCSI
  2.8329 -  adapter that comes with some HP scanners. This driver requires that
  2.8330 -  the sym53c416 is configured first using some sort of PnP
  2.8331 -  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
  2.8332 -  are using isapnp then you need to compile this driver as a module
  2.8333 -  and then load it using insmod after isapnp has run. The parameters
  2.8334 -