ia64/xen-unstable

changeset 1446:f3123052268f

bitkeeper revision 1.946 (40c73c7805slPvnfEohXfQoiriAESg)

Rename Linux directories and upgrade build system.
author kaf24@scramble.cl.cam.ac.uk
date Wed Jun 09 16:36:08 2004 +0000 (2004-06-09)
parents 1d1e0a1795b8
children a956305055ae 5d1068f385df
files .bk-to-hg .hg-to-bk .rootkeys BitKeeper/etc/ignore Makefile linux-2.4.26-xen-sparse/Documentation/Configure.help linux-2.4.26-xen-sparse/Makefile linux-2.4.26-xen-sparse/arch/xen/Makefile linux-2.4.26-xen-sparse/arch/xen/boot/Makefile linux-2.4.26-xen-sparse/arch/xen/config.in linux-2.4.26-xen-sparse/arch/xen/defconfigs/dom0 linux-2.4.26-xen-sparse/arch/xen/defconfigs/unprivileged linux-2.4.26-xen-sparse/arch/xen/drivers/balloon/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/balloon/balloon.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/common.h linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/control.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/interface.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/main.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/vbd.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/blkif.h linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/common.h linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/main.c linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/vbd.c linux-2.4.26-xen-sparse/arch/xen/drivers/block/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/block/block.c linux-2.4.26-xen-sparse/arch/xen/drivers/block/block.h linux-2.4.26-xen-sparse/arch/xen/drivers/block/vbd.c linux-2.4.26-xen-sparse/arch/xen/drivers/console/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/console/console.c linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/core.c linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/vfr.c linux-2.4.26-xen-sparse/arch/xen/drivers/evtchn/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/evtchn/evtchn.c linux-2.4.26-xen-sparse/arch/xen/drivers/netif/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/common.h linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/control.c linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/interface.c linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/main.c linux-2.4.26-xen-sparse/arch/xen/drivers/netif/frontend/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/netif/frontend/main.c linux-2.4.26-xen-sparse/arch/xen/drivers/netif/netif.h linux-2.4.26-xen-sparse/arch/xen/drivers/network/Makefile linux-2.4.26-xen-sparse/arch/xen/drivers/network/network.c linux-2.4.26-xen-sparse/arch/xen/kernel/Makefile linux-2.4.26-xen-sparse/arch/xen/kernel/ctrl_if.c linux-2.4.26-xen-sparse/arch/xen/kernel/entry.S linux-2.4.26-xen-sparse/arch/xen/kernel/evtchn.c linux-2.4.26-xen-sparse/arch/xen/kernel/head.S linux-2.4.26-xen-sparse/arch/xen/kernel/i386_ksyms.c linux-2.4.26-xen-sparse/arch/xen/kernel/ioport.c linux-2.4.26-xen-sparse/arch/xen/kernel/irq.c linux-2.4.26-xen-sparse/arch/xen/kernel/ldt.c linux-2.4.26-xen-sparse/arch/xen/kernel/pci-dma.c linux-2.4.26-xen-sparse/arch/xen/kernel/pci-pc.c linux-2.4.26-xen-sparse/arch/xen/kernel/process.c linux-2.4.26-xen-sparse/arch/xen/kernel/setup.c linux-2.4.26-xen-sparse/arch/xen/kernel/signal.c linux-2.4.26-xen-sparse/arch/xen/kernel/time.c linux-2.4.26-xen-sparse/arch/xen/kernel/traps.c linux-2.4.26-xen-sparse/arch/xen/lib/Makefile linux-2.4.26-xen-sparse/arch/xen/lib/delay.c linux-2.4.26-xen-sparse/arch/xen/lib/xen_proc.c linux-2.4.26-xen-sparse/arch/xen/mm/Makefile linux-2.4.26-xen-sparse/arch/xen/mm/fault.c linux-2.4.26-xen-sparse/arch/xen/mm/hypervisor.c linux-2.4.26-xen-sparse/arch/xen/mm/init.c linux-2.4.26-xen-sparse/arch/xen/mm/ioremap.c linux-2.4.26-xen-sparse/arch/xen/vmlinux.lds linux-2.4.26-xen-sparse/drivers/block/ll_rw_blk.c linux-2.4.26-xen-sparse/drivers/char/mem.c linux-2.4.26-xen-sparse/drivers/char/tty_io.c linux-2.4.26-xen-sparse/fs/exec.c linux-2.4.26-xen-sparse/include/asm-xen/bugs.h linux-2.4.26-xen-sparse/include/asm-xen/ctrl_if.h linux-2.4.26-xen-sparse/include/asm-xen/desc.h linux-2.4.26-xen-sparse/include/asm-xen/evtchn.h linux-2.4.26-xen-sparse/include/asm-xen/fixmap.h linux-2.4.26-xen-sparse/include/asm-xen/highmem.h linux-2.4.26-xen-sparse/include/asm-xen/hw_irq.h linux-2.4.26-xen-sparse/include/asm-xen/hypervisor.h linux-2.4.26-xen-sparse/include/asm-xen/io.h linux-2.4.26-xen-sparse/include/asm-xen/irq.h linux-2.4.26-xen-sparse/include/asm-xen/keyboard.h linux-2.4.26-xen-sparse/include/asm-xen/mmu_context.h linux-2.4.26-xen-sparse/include/asm-xen/msr.h linux-2.4.26-xen-sparse/include/asm-xen/multicall.h linux-2.4.26-xen-sparse/include/asm-xen/page.h linux-2.4.26-xen-sparse/include/asm-xen/pci.h linux-2.4.26-xen-sparse/include/asm-xen/pgalloc.h linux-2.4.26-xen-sparse/include/asm-xen/pgtable-2level.h linux-2.4.26-xen-sparse/include/asm-xen/pgtable.h linux-2.4.26-xen-sparse/include/asm-xen/proc_cmd.h linux-2.4.26-xen-sparse/include/asm-xen/processor.h linux-2.4.26-xen-sparse/include/asm-xen/ptrace.h linux-2.4.26-xen-sparse/include/asm-xen/segment.h linux-2.4.26-xen-sparse/include/asm-xen/smp.h linux-2.4.26-xen-sparse/include/asm-xen/suspend.h linux-2.4.26-xen-sparse/include/asm-xen/synch_bitops.h linux-2.4.26-xen-sparse/include/asm-xen/system.h linux-2.4.26-xen-sparse/include/asm-xen/vga.h linux-2.4.26-xen-sparse/include/asm-xen/xen_proc.h linux-2.4.26-xen-sparse/include/asm-xen/xor.h linux-2.4.26-xen-sparse/include/linux/blk.h linux-2.4.26-xen-sparse/include/linux/major.h linux-2.4.26-xen-sparse/include/linux/sched.h linux-2.4.26-xen-sparse/include/linux/skbuff.h linux-2.4.26-xen-sparse/include/linux/sunrpc/debug.h linux-2.4.26-xen-sparse/include/linux/timer.h linux-2.4.26-xen-sparse/init/do_mounts.c linux-2.4.26-xen-sparse/kernel/time.c linux-2.4.26-xen-sparse/kernel/timer.c linux-2.4.26-xen-sparse/mkbuildtree linux-2.4.26-xen-sparse/mm/highmem.c linux-2.4.26-xen-sparse/mm/memory.c linux-2.4.26-xen-sparse/mm/mprotect.c linux-2.4.26-xen-sparse/mm/mremap.c linux-2.4.26-xen-sparse/mm/page_alloc.c linux-2.4.26-xen-sparse/mm/swapfile.c linux-2.4.26-xen-sparse/mm/vmalloc.c tools/misc/Makefile tools/xc/lib/Makefile tools/xend/setup.py tools/xentrace/Makefile xen/arch/i386/pdb-stub.c xenolinux-2.4.26-sparse/Documentation/Configure.help xenolinux-2.4.26-sparse/Makefile xenolinux-2.4.26-sparse/arch/xen/Makefile xenolinux-2.4.26-sparse/arch/xen/boot/Makefile xenolinux-2.4.26-sparse/arch/xen/config.in xenolinux-2.4.26-sparse/arch/xen/defconfig xenolinux-2.4.26-sparse/arch/xen/defconfig-physdev xenolinux-2.4.26-sparse/arch/xen/drivers/balloon/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/balloon/balloon.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/common.h xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/control.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/interface.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/main.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/vbd.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/blkif.h xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/common.h xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/main.c xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/vbd.c xenolinux-2.4.26-sparse/arch/xen/drivers/block/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/block/block.c xenolinux-2.4.26-sparse/arch/xen/drivers/block/block.h xenolinux-2.4.26-sparse/arch/xen/drivers/block/vbd.c xenolinux-2.4.26-sparse/arch/xen/drivers/console/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/console/console.c xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/core.c xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/vfr.c xenolinux-2.4.26-sparse/arch/xen/drivers/evtchn/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/evtchn/evtchn.c xenolinux-2.4.26-sparse/arch/xen/drivers/netif/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/common.h xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/control.c xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/interface.c xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/main.c xenolinux-2.4.26-sparse/arch/xen/drivers/netif/frontend/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/netif/frontend/main.c xenolinux-2.4.26-sparse/arch/xen/drivers/netif/netif.h xenolinux-2.4.26-sparse/arch/xen/drivers/network/Makefile xenolinux-2.4.26-sparse/arch/xen/drivers/network/network.c xenolinux-2.4.26-sparse/arch/xen/kernel/Makefile xenolinux-2.4.26-sparse/arch/xen/kernel/ctrl_if.c xenolinux-2.4.26-sparse/arch/xen/kernel/entry.S xenolinux-2.4.26-sparse/arch/xen/kernel/evtchn.c xenolinux-2.4.26-sparse/arch/xen/kernel/head.S xenolinux-2.4.26-sparse/arch/xen/kernel/i386_ksyms.c xenolinux-2.4.26-sparse/arch/xen/kernel/ioport.c xenolinux-2.4.26-sparse/arch/xen/kernel/irq.c xenolinux-2.4.26-sparse/arch/xen/kernel/ldt.c xenolinux-2.4.26-sparse/arch/xen/kernel/pci-dma.c xenolinux-2.4.26-sparse/arch/xen/kernel/pci-pc.c xenolinux-2.4.26-sparse/arch/xen/kernel/process.c xenolinux-2.4.26-sparse/arch/xen/kernel/setup.c xenolinux-2.4.26-sparse/arch/xen/kernel/signal.c xenolinux-2.4.26-sparse/arch/xen/kernel/time.c xenolinux-2.4.26-sparse/arch/xen/kernel/traps.c xenolinux-2.4.26-sparse/arch/xen/lib/Makefile xenolinux-2.4.26-sparse/arch/xen/lib/delay.c xenolinux-2.4.26-sparse/arch/xen/lib/xen_proc.c xenolinux-2.4.26-sparse/arch/xen/mm/Makefile xenolinux-2.4.26-sparse/arch/xen/mm/fault.c xenolinux-2.4.26-sparse/arch/xen/mm/hypervisor.c xenolinux-2.4.26-sparse/arch/xen/mm/init.c xenolinux-2.4.26-sparse/arch/xen/mm/ioremap.c xenolinux-2.4.26-sparse/arch/xen/vmlinux.lds xenolinux-2.4.26-sparse/drivers/block/ll_rw_blk.c xenolinux-2.4.26-sparse/drivers/char/mem.c xenolinux-2.4.26-sparse/drivers/char/tty_io.c xenolinux-2.4.26-sparse/fs/exec.c xenolinux-2.4.26-sparse/include/asm-xen/bugs.h xenolinux-2.4.26-sparse/include/asm-xen/ctrl_if.h xenolinux-2.4.26-sparse/include/asm-xen/desc.h xenolinux-2.4.26-sparse/include/asm-xen/evtchn.h xenolinux-2.4.26-sparse/include/asm-xen/fixmap.h xenolinux-2.4.26-sparse/include/asm-xen/highmem.h xenolinux-2.4.26-sparse/include/asm-xen/hw_irq.h xenolinux-2.4.26-sparse/include/asm-xen/hypervisor.h xenolinux-2.4.26-sparse/include/asm-xen/io.h xenolinux-2.4.26-sparse/include/asm-xen/irq.h xenolinux-2.4.26-sparse/include/asm-xen/keyboard.h xenolinux-2.4.26-sparse/include/asm-xen/mmu_context.h xenolinux-2.4.26-sparse/include/asm-xen/msr.h xenolinux-2.4.26-sparse/include/asm-xen/multicall.h xenolinux-2.4.26-sparse/include/asm-xen/page.h xenolinux-2.4.26-sparse/include/asm-xen/pci.h xenolinux-2.4.26-sparse/include/asm-xen/pgalloc.h xenolinux-2.4.26-sparse/include/asm-xen/pgtable-2level.h xenolinux-2.4.26-sparse/include/asm-xen/pgtable.h xenolinux-2.4.26-sparse/include/asm-xen/proc_cmd.h xenolinux-2.4.26-sparse/include/asm-xen/processor.h xenolinux-2.4.26-sparse/include/asm-xen/ptrace.h xenolinux-2.4.26-sparse/include/asm-xen/segment.h xenolinux-2.4.26-sparse/include/asm-xen/smp.h xenolinux-2.4.26-sparse/include/asm-xen/suspend.h xenolinux-2.4.26-sparse/include/asm-xen/synch_bitops.h xenolinux-2.4.26-sparse/include/asm-xen/system.h xenolinux-2.4.26-sparse/include/asm-xen/vga.h xenolinux-2.4.26-sparse/include/asm-xen/xen_proc.h xenolinux-2.4.26-sparse/include/asm-xen/xor.h xenolinux-2.4.26-sparse/include/linux/blk.h xenolinux-2.4.26-sparse/include/linux/major.h xenolinux-2.4.26-sparse/include/linux/sched.h xenolinux-2.4.26-sparse/include/linux/skbuff.h xenolinux-2.4.26-sparse/include/linux/sunrpc/debug.h xenolinux-2.4.26-sparse/include/linux/timer.h xenolinux-2.4.26-sparse/init/do_mounts.c xenolinux-2.4.26-sparse/kernel/time.c xenolinux-2.4.26-sparse/kernel/timer.c xenolinux-2.4.26-sparse/mkbuildtree xenolinux-2.4.26-sparse/mm/highmem.c xenolinux-2.4.26-sparse/mm/memory.c xenolinux-2.4.26-sparse/mm/mprotect.c xenolinux-2.4.26-sparse/mm/mremap.c xenolinux-2.4.26-sparse/mm/page_alloc.c xenolinux-2.4.26-sparse/mm/swapfile.c xenolinux-2.4.26-sparse/mm/vmalloc.c
line diff
     1.1 --- a/.bk-to-hg	Wed Jun 09 15:42:10 2004 +0000
     1.2 +++ b/.bk-to-hg	Wed Jun 09 16:36:08 2004 +0000
     1.3 @@ -1,6 +1,2 @@
     1.4 -#!/bin/sh -x
     1.5 -set -e
     1.6 -test -L xenolinux-sparse
     1.7 -rm      xenolinux-sparse
     1.8 -(find -depth -type d -print | xargs -r rmdir 2>/dev/null) || true
     1.9 +#!/bin/sh
    1.10  exit 0
     2.1 --- a/.hg-to-bk	Wed Jun 09 15:42:10 2004 +0000
     2.2 +++ b/.hg-to-bk	Wed Jun 09 16:36:08 2004 +0000
     2.3 @@ -1,5 +1,2 @@
     2.4 -#!/bin/sh -x
     2.5 -set -e
     2.6 -ln -s xenolinux-2.4.26-sparse xenolinux-sparse
     2.7 -(find -depth -type d -print | xargs -r rmdir 2>/dev/null) || true
     2.8 +#!/bin/sh
     2.9  exit 0
     3.1 --- a/.rootkeys	Wed Jun 09 15:42:10 2004 +0000
     3.2 +++ b/.rootkeys	Wed Jun 09 16:36:08 2004 +0000
     3.3 @@ -39,6 +39,125 @@ 3f815145AYE58Kpmsj5U7oHDpVDZJA extras/mi
     3.4  3f815145CB8XdPUqsmhAjSDFuwOoqA extras/mini-os/mm.c
     3.5  3f815145vGYx1WY79voKkZB9yKwJKQ extras/mini-os/time.c
     3.6  3f815145xlKBAQmal9oces3G_Mvxqw extras/mini-os/traps.c
     3.7 +3f05a939TA3SLPY7ZiScMotLjg9owQ linux-2.4.26-xen-sparse/Documentation/Configure.help
     3.8 +3e5a4e6589G-U42lFKs43plskXoFxQ linux-2.4.26-xen-sparse/Makefile
     3.9 +3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg linux-2.4.26-xen-sparse/arch/xen/Makefile
    3.10 +3e5a4e65n-KhsEAs-A4ULiStBp-r6w linux-2.4.26-xen-sparse/arch/xen/boot/Makefile
    3.11 +3e5a4e65OV_j_DBtjzt5vej771AJsA linux-2.4.26-xen-sparse/arch/xen/config.in
    3.12 +40648526SxcA4lGIHB_k7ID8VlRSzw linux-2.4.26-xen-sparse/arch/xen/defconfigs/dom0
    3.13 +40c73c77QesbL7eIvG-fJGAtVwhGRg linux-2.4.26-xen-sparse/arch/xen/defconfigs/unprivileged
    3.14 +3e6377f5xwPfYZkPHPrDbEq1PRN7uQ linux-2.4.26-xen-sparse/arch/xen/drivers/balloon/Makefile
    3.15 +3e6377f8Me8IqtvEhb70XFgOvqQH7A linux-2.4.26-xen-sparse/arch/xen/drivers/balloon/balloon.c
    3.16 +4083dc16z0jvZEH4PiVDbDRreaNp6w linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/Makefile
    3.17 +4083dc16KQus88a4U3uCV6qVCA6_8Q linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/Makefile
    3.18 +4087cf0dPeHOvzmZAazvwLslKEF93A linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/common.h
    3.19 +4087cf0da2cROOiybf9A-j4R_yHnjg linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/control.c
    3.20 +4087cf0dvXL1PKX23t_LvO1wVPb7OA linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/interface.c
    3.21 +4087cf0dkVF3I19gpT1cNubeJgQr7g linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/main.c
    3.22 +4087cf0dlv1Dw4MAbeRStPPG8IvPPg linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/backend/vbd.c
    3.23 +40880cc6hHg6s2cPHbqPNQxENefjoQ linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/blkif.h
    3.24 +4075806dI5kfeMD5RV-DA0PYoThx_w linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/Makefile
    3.25 +4075806d4-j7vN0Mn0bklI1cRUX1vQ linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/common.h
    3.26 +4075806d3fJqqDC1pYYPTZPc575iKg linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/main.c
    3.27 +4075806dibjCcfuXv6CINMhxWTw3jQ linux-2.4.26-xen-sparse/arch/xen/drivers/blkif/frontend/vbd.c
    3.28 +3e5a4e65iHEuC5sjFhj42XALYbLVRw linux-2.4.26-xen-sparse/arch/xen/drivers/block/Makefile
    3.29 +3e5a4e65pP5spJErBW69pJxSSdK9RA linux-2.4.26-xen-sparse/arch/xen/drivers/block/block.c
    3.30 +3e67f822FOPwqHiaRKbrskgWgoNL5g linux-2.4.26-xen-sparse/arch/xen/drivers/block/block.h
    3.31 +3e676eb5RXnHzSHgA1BvM0B1aIm4qg linux-2.4.26-xen-sparse/arch/xen/drivers/block/vbd.c
    3.32 +3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ linux-2.4.26-xen-sparse/arch/xen/drivers/console/Makefile
    3.33 +3e5a4e651TH-SXHoufurnWjgl5bfOA linux-2.4.26-xen-sparse/arch/xen/drivers/console/console.c
    3.34 +3e5a4e656nfFISThfbyXQOA6HN6YHw linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/Makefile
    3.35 +3e5a4e65BXtftInNHUC2PjDfPhdZZA linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/core.c
    3.36 +3e5a4e65gfn_ltB8ujHMVFApnTTNRQ linux-2.4.26-xen-sparse/arch/xen/drivers/dom0/vfr.c
    3.37 +40420a6ebRqDjufoN1WSJvolEW2Wjw linux-2.4.26-xen-sparse/arch/xen/drivers/evtchn/Makefile
    3.38 +40420a73Wou6JlsZDiu6YwjYomsm7A linux-2.4.26-xen-sparse/arch/xen/drivers/evtchn/evtchn.c
    3.39 +4083dc16-Kd5y9psK_yk161sme5j5Q linux-2.4.26-xen-sparse/arch/xen/drivers/netif/Makefile
    3.40 +4083dc16UmHXxS9g_UFVnkUpN-oP2Q linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/Makefile
    3.41 +4097ba83pPKYqMS3Gl-PVKIgYU1FZw linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/common.h
    3.42 +4097ba83glWYwQTkbPqgLIlYDOPVLg linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/control.c
    3.43 +4097ba837h2tuiweIWp-voNVzCRI6g linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/interface.c
    3.44 +4087cf0d5dudKw_DecIJgOhLlBF_0Q linux-2.4.26-xen-sparse/arch/xen/drivers/netif/backend/main.c
    3.45 +405853f2wg7JXZJNltspMwOZJklxgw linux-2.4.26-xen-sparse/arch/xen/drivers/netif/frontend/Makefile
    3.46 +405853f6nbeazrNyEWNHBuoSg2PiPA linux-2.4.26-xen-sparse/arch/xen/drivers/netif/frontend/main.c
    3.47 +4097ba83Qy2eafeFUhGhm6_4iMIIDw linux-2.4.26-xen-sparse/arch/xen/drivers/netif/netif.h
    3.48 +3e5a4e65gZBRBB6RsSVg1c9iahigAw linux-2.4.26-xen-sparse/arch/xen/drivers/network/Makefile
    3.49 +3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ linux-2.4.26-xen-sparse/arch/xen/drivers/network/network.c
    3.50 +3e5a4e65lWzkiPXsZdzPt2RNnJGG1g linux-2.4.26-xen-sparse/arch/xen/kernel/Makefile
    3.51 +4075806dE5mQwlVUf8-t3YXjiMMWDQ linux-2.4.26-xen-sparse/arch/xen/kernel/ctrl_if.c
    3.52 +3e5a4e65_hqfuxtGG8IUy6wRM86Ecg linux-2.4.26-xen-sparse/arch/xen/kernel/entry.S
    3.53 +3e5a4e65ibVQmwlOn0j3sVH_j_6hAg linux-2.4.26-xen-sparse/arch/xen/kernel/evtchn.c
    3.54 +3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg linux-2.4.26-xen-sparse/arch/xen/kernel/head.S
    3.55 +3e5a4e65RMGcuA-HCn3-wNx3fFQwdg linux-2.4.26-xen-sparse/arch/xen/kernel/i386_ksyms.c
    3.56 +3e5a4e65MEvZhlr070sK5JsfAQlv7Q linux-2.4.26-xen-sparse/arch/xen/kernel/ioport.c
    3.57 +3e5a4e653U6cELGv528IxOLHvCq8iA linux-2.4.26-xen-sparse/arch/xen/kernel/irq.c
    3.58 +3e5a4e65muT6SU3ck47IP87Q7Ti5hA linux-2.4.26-xen-sparse/arch/xen/kernel/ldt.c
    3.59 +4051db84bZeRX7a_Kh6VyyDuT5FOIg linux-2.4.26-xen-sparse/arch/xen/kernel/pci-dma.c
    3.60 +4051db95N9N99FjsRwi49YKUNHWI8A linux-2.4.26-xen-sparse/arch/xen/kernel/pci-pc.c
    3.61 +3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ linux-2.4.26-xen-sparse/arch/xen/kernel/process.c
    3.62 +3e5a4e66tR-qJMLj3MppcKqmvuI2XQ linux-2.4.26-xen-sparse/arch/xen/kernel/setup.c
    3.63 +3e5a4e66fWSTagLGU2P8BGFGRjhDiw linux-2.4.26-xen-sparse/arch/xen/kernel/signal.c
    3.64 +3e5a4e66N__lUXNwzQ-eADRzK9LXuQ linux-2.4.26-xen-sparse/arch/xen/kernel/time.c
    3.65 +3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ linux-2.4.26-xen-sparse/arch/xen/kernel/traps.c
    3.66 +3e5a4e66-9_NczrVMbuQkoSLyXckIw linux-2.4.26-xen-sparse/arch/xen/lib/Makefile
    3.67 +3e5a4e6637ZDk0BvFEC-aFQs599-ng linux-2.4.26-xen-sparse/arch/xen/lib/delay.c
    3.68 +3f68905cF5i8-NYpIhGjKmh0y8Gu5g linux-2.4.26-xen-sparse/arch/xen/lib/xen_proc.c
    3.69 +3e5a4e66croVgpcJyJuF2ycQw0HuJw linux-2.4.26-xen-sparse/arch/xen/mm/Makefile
    3.70 +3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg linux-2.4.26-xen-sparse/arch/xen/mm/fault.c
    3.71 +3e5a4e668SE9rixq4ahho9rNhLUUFQ linux-2.4.26-xen-sparse/arch/xen/mm/hypervisor.c
    3.72 +3e5a4e661gLzzff25pJooKIIWe7IWg linux-2.4.26-xen-sparse/arch/xen/mm/init.c
    3.73 +3f0bed43UUdQichXAiVNrjV-y2Kzcg linux-2.4.26-xen-sparse/arch/xen/mm/ioremap.c
    3.74 +3e5a4e66qRlSTcjafidMB6ulECADvg linux-2.4.26-xen-sparse/arch/xen/vmlinux.lds
    3.75 +3e5a4e66mrtlmV75L1tjKDg8RaM5gA linux-2.4.26-xen-sparse/drivers/block/ll_rw_blk.c
    3.76 +3f108aeaLcGDgQdFAANLTUEid0a05w linux-2.4.26-xen-sparse/drivers/char/mem.c
    3.77 +3e5a4e66rw65CxyolW9PKz4GG42RcA linux-2.4.26-xen-sparse/drivers/char/tty_io.c
    3.78 +3e5a4e669uzIE54VwucPYtGwXLAbzA linux-2.4.26-xen-sparse/fs/exec.c
    3.79 +3e5a4e66wbeCpsJgVf_U8Jde-CNcsA linux-2.4.26-xen-sparse/include/asm-xen/bugs.h
    3.80 +4048c0ddxnIa2GpBAVR-mY6mNSdeJg linux-2.4.26-xen-sparse/include/asm-xen/ctrl_if.h
    3.81 +3e5a4e66HdSkvIV6SJ1evG_xmTmXHA linux-2.4.26-xen-sparse/include/asm-xen/desc.h
    3.82 +4048c0e0_P2wUTiT6UqgPhn0s7yFcA linux-2.4.26-xen-sparse/include/asm-xen/evtchn.h
    3.83 +3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw linux-2.4.26-xen-sparse/include/asm-xen/fixmap.h
    3.84 +406aeeaaQvl4RNtmd9hDEugBURbFpQ linux-2.4.26-xen-sparse/include/asm-xen/highmem.h
    3.85 +3e5a4e67YtcyDLQsShhCfQwPSELfvA linux-2.4.26-xen-sparse/include/asm-xen/hw_irq.h
    3.86 +3e5a4e677VBavzM1UZIEcH1B-RlXMA linux-2.4.26-xen-sparse/include/asm-xen/hypervisor.h
    3.87 +4060044fVx7-tokvNLKBf_6qBB4lqQ linux-2.4.26-xen-sparse/include/asm-xen/io.h
    3.88 +3e5a4e673p7PEOyHFm3nHkYX6HQYBg linux-2.4.26-xen-sparse/include/asm-xen/irq.h
    3.89 +3ead095db_LRUXnxaqs0dA1DWhPoQQ linux-2.4.26-xen-sparse/include/asm-xen/keyboard.h
    3.90 +3e5a4e678ddsQOpbSiRdy1GRcDc9WA linux-2.4.26-xen-sparse/include/asm-xen/mmu_context.h
    3.91 +3f8707e7ZmZ6TxyX0ZUEfvhA2Pb_xQ linux-2.4.26-xen-sparse/include/asm-xen/msr.h
    3.92 +3e7270deQqtGPSnFxcW4AvJZuTUWfg linux-2.4.26-xen-sparse/include/asm-xen/multicall.h
    3.93 +3e5a4e67mnQfh-R8KcQCaVo2Oho6yg linux-2.4.26-xen-sparse/include/asm-xen/page.h
    3.94 +409ba2e7ZfV5hqTvIzxLtpClnxtIzg linux-2.4.26-xen-sparse/include/asm-xen/pci.h
    3.95 +3e5a4e67uTYU5oEnIDjxuaez8njjqg linux-2.4.26-xen-sparse/include/asm-xen/pgalloc.h
    3.96 +3e5a4e67X7JyupgdYkgDX19Huj2sAw linux-2.4.26-xen-sparse/include/asm-xen/pgtable-2level.h
    3.97 +3e5a4e67gr4NLGtQ5CvSLimMYZlkOA linux-2.4.26-xen-sparse/include/asm-xen/pgtable.h
    3.98 +3f108af1qNv8DVSGPv4zpqIU1txCkg linux-2.4.26-xen-sparse/include/asm-xen/proc_cmd.h
    3.99 +3e5a4e676uK4xErTBDH6XJREn9LSyg linux-2.4.26-xen-sparse/include/asm-xen/processor.h
   3.100 +3e5a4e67AJPjW-zL7p-xWuA6IVeH1g linux-2.4.26-xen-sparse/include/asm-xen/ptrace.h
   3.101 +3e5a4e68uJz-xI0IBVMD7xRLQKJDFg linux-2.4.26-xen-sparse/include/asm-xen/segment.h
   3.102 +3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA linux-2.4.26-xen-sparse/include/asm-xen/smp.h
   3.103 +3fa8e3f0kBLeE4To2vpdi3cpJbIkbQ linux-2.4.26-xen-sparse/include/asm-xen/suspend.h
   3.104 +4062f7e2PzFOUGT0PaE7A0VprTU3JQ linux-2.4.26-xen-sparse/include/asm-xen/synch_bitops.h
   3.105 +3e5a4e68mTr0zcp9SXDbnd-XLrrfxw linux-2.4.26-xen-sparse/include/asm-xen/system.h
   3.106 +3f1056a9L_kqHcFheV00KbKBzv9j5w linux-2.4.26-xen-sparse/include/asm-xen/vga.h
   3.107 +3f689063nhrIRsMMZjZxMFk7iEINqQ linux-2.4.26-xen-sparse/include/asm-xen/xen_proc.h
   3.108 +40659defgWA92arexpMGn8X3QMDj3w linux-2.4.26-xen-sparse/include/asm-xen/xor.h
   3.109 +3f056927gMHl7mWB89rb73JahbhQIA linux-2.4.26-xen-sparse/include/linux/blk.h
   3.110 +3e5a4e68WLX3B8owTvktP3HHOtznPQ linux-2.4.26-xen-sparse/include/linux/major.h
   3.111 +401c0590D_kwJDU59X8NyvqSv_Cl2A linux-2.4.26-xen-sparse/include/linux/sched.h
   3.112 +40a248afgI0_JKthdYAe8beVfXSTpQ linux-2.4.26-xen-sparse/include/linux/skbuff.h
   3.113 +3e5a4e686V0nioX2ZpFf056sgvdiQw linux-2.4.26-xen-sparse/include/linux/sunrpc/debug.h
   3.114 +401c0592pLrp_aCbQRo9GXiYQQaVVA linux-2.4.26-xen-sparse/include/linux/timer.h
   3.115 +3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ linux-2.4.26-xen-sparse/init/do_mounts.c
   3.116 +3f9d4b44247udoqWEgFkaHiWv6Uvyg linux-2.4.26-xen-sparse/kernel/time.c
   3.117 +401c059bjLBFYHRD4Py2uM3eA1D4zQ linux-2.4.26-xen-sparse/kernel/timer.c
   3.118 +3e6e7c1efbQe93xCvOpOVCnXTMmQ5w linux-2.4.26-xen-sparse/mkbuildtree
   3.119 +406aeeafkrnCuIVWLFv3kfn4uAD5Eg linux-2.4.26-xen-sparse/mm/highmem.c
   3.120 +3e5a4e68GxCIaFH4sy01v1wjapetaA linux-2.4.26-xen-sparse/mm/memory.c
   3.121 +3f108af5VxPkLv13tXpXgoRKALQtXQ linux-2.4.26-xen-sparse/mm/mprotect.c
   3.122 +3e5a4e681xMPdF9xCMwpyfuYMySU5g linux-2.4.26-xen-sparse/mm/mremap.c
   3.123 +409ba2e7akOFqQUg6Qyg2s28xcXiMg linux-2.4.26-xen-sparse/mm/page_alloc.c
   3.124 +3e5a4e683HKVU-sxtagrDasRB8eBVw linux-2.4.26-xen-sparse/mm/swapfile.c
   3.125 +3f108af81Thhb242EmKjGCYkjx-GJA linux-2.4.26-xen-sparse/mm/vmalloc.c
   3.126  3f776bd1Hy9rn69ntXBhPReUFw9IEA tools/Makefile
   3.127  3e6377b24eQqYMsDi9XrFkIgTzZ47A tools/balloon/Makefile
   3.128  3e6377d6eiFjF1hHIS6JEIOFk62xSA tools/balloon/README
   3.129 @@ -649,123 +768,3 @@ 3eb3c87fPL2T_zBb0bHlbZY-ACEKRw xen/tools
   3.130  3eb3c87fmKYTC5GCh_rydFakZp9ayw xen/tools/figlet/README
   3.131  3eb3c87fdQKQ5OBGbM-KjZfi9Us4ng xen/tools/figlet/figlet.c
   3.132  3eb3c87fS7DNbg0i6yhFs28UIqAK5g xen/tools/figlet/xen.flf
   3.133 -3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.26-sparse/Documentation/Configure.help
   3.134 -3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.26-sparse/Makefile
   3.135 -3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.26-sparse/arch/xen/Makefile
   3.136 -3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.26-sparse/arch/xen/boot/Makefile
   3.137 -3e5a4e65OV_j_DBtjzt5vej771AJsA xenolinux-2.4.26-sparse/arch/xen/config.in
   3.138 -3e5a4e65TNEycLeXqPSXQJQm_xGecA xenolinux-2.4.26-sparse/arch/xen/defconfig
   3.139 -40648526SxcA4lGIHB_k7ID8VlRSzw xenolinux-2.4.26-sparse/arch/xen/defconfig-physdev
   3.140 -3e6377f5xwPfYZkPHPrDbEq1PRN7uQ xenolinux-2.4.26-sparse/arch/xen/drivers/balloon/Makefile
   3.141 -3e6377f8Me8IqtvEhb70XFgOvqQH7A xenolinux-2.4.26-sparse/arch/xen/drivers/balloon/balloon.c
   3.142 -4083dc16z0jvZEH4PiVDbDRreaNp6w xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/Makefile
   3.143 -4083dc16KQus88a4U3uCV6qVCA6_8Q xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/Makefile
   3.144 -4087cf0dPeHOvzmZAazvwLslKEF93A xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/common.h
   3.145 -4087cf0da2cROOiybf9A-j4R_yHnjg xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/control.c
   3.146 -4087cf0dvXL1PKX23t_LvO1wVPb7OA xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/interface.c
   3.147 -4087cf0dkVF3I19gpT1cNubeJgQr7g xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/main.c
   3.148 -4087cf0dlv1Dw4MAbeRStPPG8IvPPg xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/backend/vbd.c
   3.149 -40880cc6hHg6s2cPHbqPNQxENefjoQ xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/blkif.h
   3.150 -4075806dI5kfeMD5RV-DA0PYoThx_w xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/Makefile
   3.151 -4075806d4-j7vN0Mn0bklI1cRUX1vQ xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/common.h
   3.152 -4075806d3fJqqDC1pYYPTZPc575iKg xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/main.c
   3.153 -4075806dibjCcfuXv6CINMhxWTw3jQ xenolinux-2.4.26-sparse/arch/xen/drivers/blkif/frontend/vbd.c
   3.154 -3e5a4e65iHEuC5sjFhj42XALYbLVRw xenolinux-2.4.26-sparse/arch/xen/drivers/block/Makefile
   3.155 -3e5a4e65pP5spJErBW69pJxSSdK9RA xenolinux-2.4.26-sparse/arch/xen/drivers/block/block.c
   3.156 -3e67f822FOPwqHiaRKbrskgWgoNL5g xenolinux-2.4.26-sparse/arch/xen/drivers/block/block.h
   3.157 -3e676eb5RXnHzSHgA1BvM0B1aIm4qg xenolinux-2.4.26-sparse/arch/xen/drivers/block/vbd.c
   3.158 -3e5a4e65G3e2s0ghPMgiJ-gBTUJ0uQ xenolinux-2.4.26-sparse/arch/xen/drivers/console/Makefile
   3.159 -3e5a4e651TH-SXHoufurnWjgl5bfOA xenolinux-2.4.26-sparse/arch/xen/drivers/console/console.c
   3.160 -3e5a4e656nfFISThfbyXQOA6HN6YHw xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/Makefile
   3.161 -3e5a4e65BXtftInNHUC2PjDfPhdZZA xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/core.c
   3.162 -3e5a4e65gfn_ltB8ujHMVFApnTTNRQ xenolinux-2.4.26-sparse/arch/xen/drivers/dom0/vfr.c
   3.163 -40420a6ebRqDjufoN1WSJvolEW2Wjw xenolinux-2.4.26-sparse/arch/xen/drivers/evtchn/Makefile
   3.164 -40420a73Wou6JlsZDiu6YwjYomsm7A xenolinux-2.4.26-sparse/arch/xen/drivers/evtchn/evtchn.c
   3.165 -4083dc16-Kd5y9psK_yk161sme5j5Q xenolinux-2.4.26-sparse/arch/xen/drivers/netif/Makefile
   3.166 -4083dc16UmHXxS9g_UFVnkUpN-oP2Q xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/Makefile
   3.167 -4097ba83pPKYqMS3Gl-PVKIgYU1FZw xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/common.h
   3.168 -4097ba83glWYwQTkbPqgLIlYDOPVLg xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/control.c
   3.169 -4097ba837h2tuiweIWp-voNVzCRI6g xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/interface.c
   3.170 -4087cf0d5dudKw_DecIJgOhLlBF_0Q xenolinux-2.4.26-sparse/arch/xen/drivers/netif/backend/main.c
   3.171 -405853f2wg7JXZJNltspMwOZJklxgw xenolinux-2.4.26-sparse/arch/xen/drivers/netif/frontend/Makefile
   3.172 -405853f6nbeazrNyEWNHBuoSg2PiPA xenolinux-2.4.26-sparse/arch/xen/drivers/netif/frontend/main.c
   3.173 -4097ba83Qy2eafeFUhGhm6_4iMIIDw xenolinux-2.4.26-sparse/arch/xen/drivers/netif/netif.h
   3.174 -3e5a4e65gZBRBB6RsSVg1c9iahigAw xenolinux-2.4.26-sparse/arch/xen/drivers/network/Makefile
   3.175 -3e5a4e65ZxKrbFetVB84JhrTyZ1YuQ xenolinux-2.4.26-sparse/arch/xen/drivers/network/network.c
   3.176 -3e5a4e65lWzkiPXsZdzPt2RNnJGG1g xenolinux-2.4.26-sparse/arch/xen/kernel/Makefile
   3.177 -4075806dE5mQwlVUf8-t3YXjiMMWDQ xenolinux-2.4.26-sparse/arch/xen/kernel/ctrl_if.c
   3.178 -3e5a4e65_hqfuxtGG8IUy6wRM86Ecg xenolinux-2.4.26-sparse/arch/xen/kernel/entry.S
   3.179 -3e5a4e65ibVQmwlOn0j3sVH_j_6hAg xenolinux-2.4.26-sparse/arch/xen/kernel/evtchn.c
   3.180 -3e5a4e65Hy_1iUvMTPsNqGNXd9uFpg xenolinux-2.4.26-sparse/arch/xen/kernel/head.S
   3.181 -3e5a4e65RMGcuA-HCn3-wNx3fFQwdg xenolinux-2.4.26-sparse/arch/xen/kernel/i386_ksyms.c
   3.182 -3e5a4e65MEvZhlr070sK5JsfAQlv7Q xenolinux-2.4.26-sparse/arch/xen/kernel/ioport.c
   3.183 -3e5a4e653U6cELGv528IxOLHvCq8iA xenolinux-2.4.26-sparse/arch/xen/kernel/irq.c
   3.184 -3e5a4e65muT6SU3ck47IP87Q7Ti5hA xenolinux-2.4.26-sparse/arch/xen/kernel/ldt.c
   3.185 -4051db84bZeRX7a_Kh6VyyDuT5FOIg xenolinux-2.4.26-sparse/arch/xen/kernel/pci-dma.c
   3.186 -4051db95N9N99FjsRwi49YKUNHWI8A xenolinux-2.4.26-sparse/arch/xen/kernel/pci-pc.c
   3.187 -3e5a4e65IGt3WwQDNiL4h-gYWgNTWQ xenolinux-2.4.26-sparse/arch/xen/kernel/process.c
   3.188 -3e5a4e66tR-qJMLj3MppcKqmvuI2XQ xenolinux-2.4.26-sparse/arch/xen/kernel/setup.c
   3.189 -3e5a4e66fWSTagLGU2P8BGFGRjhDiw xenolinux-2.4.26-sparse/arch/xen/kernel/signal.c
   3.190 -3e5a4e66N__lUXNwzQ-eADRzK9LXuQ xenolinux-2.4.26-sparse/arch/xen/kernel/time.c
   3.191 -3e5a4e66aHCbQ_F5QZ8VeyikLmuRZQ xenolinux-2.4.26-sparse/arch/xen/kernel/traps.c
   3.192 -3e5a4e66-9_NczrVMbuQkoSLyXckIw xenolinux-2.4.26-sparse/arch/xen/lib/Makefile
   3.193 -3e5a4e6637ZDk0BvFEC-aFQs599-ng xenolinux-2.4.26-sparse/arch/xen/lib/delay.c
   3.194 -3f68905cF5i8-NYpIhGjKmh0y8Gu5g xenolinux-2.4.26-sparse/arch/xen/lib/xen_proc.c
   3.195 -3e5a4e66croVgpcJyJuF2ycQw0HuJw xenolinux-2.4.26-sparse/arch/xen/mm/Makefile
   3.196 -3e5a4e66l8Q5Tv-6B3lQIRmaVbFPzg xenolinux-2.4.26-sparse/arch/xen/mm/fault.c
   3.197 -3e5a4e668SE9rixq4ahho9rNhLUUFQ xenolinux-2.4.26-sparse/arch/xen/mm/hypervisor.c
   3.198 -3e5a4e661gLzzff25pJooKIIWe7IWg xenolinux-2.4.26-sparse/arch/xen/mm/init.c
   3.199 -3f0bed43UUdQichXAiVNrjV-y2Kzcg xenolinux-2.4.26-sparse/arch/xen/mm/ioremap.c
   3.200 -3e5a4e66qRlSTcjafidMB6ulECADvg xenolinux-2.4.26-sparse/arch/xen/vmlinux.lds
   3.201 -3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.26-sparse/drivers/block/ll_rw_blk.c
   3.202 -3f108aeaLcGDgQdFAANLTUEid0a05w xenolinux-2.4.26-sparse/drivers/char/mem.c
   3.203 -3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.26-sparse/drivers/char/tty_io.c
   3.204 -3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.26-sparse/fs/exec.c
   3.205 -3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.26-sparse/include/asm-xen/bugs.h
   3.206 -4048c0ddxnIa2GpBAVR-mY6mNSdeJg xenolinux-2.4.26-sparse/include/asm-xen/ctrl_if.h
   3.207 -3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.26-sparse/include/asm-xen/desc.h
   3.208 -4048c0e0_P2wUTiT6UqgPhn0s7yFcA xenolinux-2.4.26-sparse/include/asm-xen/evtchn.h
   3.209 -3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.26-sparse/include/asm-xen/fixmap.h
   3.210 -406aeeaaQvl4RNtmd9hDEugBURbFpQ xenolinux-2.4.26-sparse/include/asm-xen/highmem.h
   3.211 -3e5a4e67YtcyDLQsShhCfQwPSELfvA xenolinux-2.4.26-sparse/include/asm-xen/hw_irq.h
   3.212 -3e5a4e677VBavzM1UZIEcH1B-RlXMA xenolinux-2.4.26-sparse/include/asm-xen/hypervisor.h
   3.213 -4060044fVx7-tokvNLKBf_6qBB4lqQ xenolinux-2.4.26-sparse/include/asm-xen/io.h
   3.214 -3e5a4e673p7PEOyHFm3nHkYX6HQYBg xenolinux-2.4.26-sparse/include/asm-xen/irq.h
   3.215 -3ead095db_LRUXnxaqs0dA1DWhPoQQ xenolinux-2.4.26-sparse/include/asm-xen/keyboard.h
   3.216 -3e5a4e678ddsQOpbSiRdy1GRcDc9WA xenolinux-2.4.26-sparse/include/asm-xen/mmu_context.h
   3.217 -3f8707e7ZmZ6TxyX0ZUEfvhA2Pb_xQ xenolinux-2.4.26-sparse/include/asm-xen/msr.h
   3.218 -3e7270deQqtGPSnFxcW4AvJZuTUWfg xenolinux-2.4.26-sparse/include/asm-xen/multicall.h
   3.219 -3e5a4e67mnQfh-R8KcQCaVo2Oho6yg xenolinux-2.4.26-sparse/include/asm-xen/page.h
   3.220 -409ba2e7ZfV5hqTvIzxLtpClnxtIzg xenolinux-2.4.26-sparse/include/asm-xen/pci.h
   3.221 -3e5a4e67uTYU5oEnIDjxuaez8njjqg xenolinux-2.4.26-sparse/include/asm-xen/pgalloc.h
   3.222 -3e5a4e67X7JyupgdYkgDX19Huj2sAw xenolinux-2.4.26-sparse/include/asm-xen/pgtable-2level.h
   3.223 -3e5a4e67gr4NLGtQ5CvSLimMYZlkOA xenolinux-2.4.26-sparse/include/asm-xen/pgtable.h
   3.224 -3f108af1qNv8DVSGPv4zpqIU1txCkg xenolinux-2.4.26-sparse/include/asm-xen/proc_cmd.h
   3.225 -3e5a4e676uK4xErTBDH6XJREn9LSyg xenolinux-2.4.26-sparse/include/asm-xen/processor.h
   3.226 -3e5a4e67AJPjW-zL7p-xWuA6IVeH1g xenolinux-2.4.26-sparse/include/asm-xen/ptrace.h
   3.227 -3e5a4e68uJz-xI0IBVMD7xRLQKJDFg xenolinux-2.4.26-sparse/include/asm-xen/segment.h
   3.228 -3e5a4e68Nfdh6QcOKUTGCaYkf2LmYA xenolinux-2.4.26-sparse/include/asm-xen/smp.h
   3.229 -3fa8e3f0kBLeE4To2vpdi3cpJbIkbQ xenolinux-2.4.26-sparse/include/asm-xen/suspend.h
   3.230 -4062f7e2PzFOUGT0PaE7A0VprTU3JQ xenolinux-2.4.26-sparse/include/asm-xen/synch_bitops.h
   3.231 -3e5a4e68mTr0zcp9SXDbnd-XLrrfxw xenolinux-2.4.26-sparse/include/asm-xen/system.h
   3.232 -3f1056a9L_kqHcFheV00KbKBzv9j5w xenolinux-2.4.26-sparse/include/asm-xen/vga.h
   3.233 -3f689063nhrIRsMMZjZxMFk7iEINqQ xenolinux-2.4.26-sparse/include/asm-xen/xen_proc.h
   3.234 -40659defgWA92arexpMGn8X3QMDj3w xenolinux-2.4.26-sparse/include/asm-xen/xor.h
   3.235 -3f056927gMHl7mWB89rb73JahbhQIA xenolinux-2.4.26-sparse/include/linux/blk.h
   3.236 -3e5a4e68WLX3B8owTvktP3HHOtznPQ xenolinux-2.4.26-sparse/include/linux/major.h
   3.237 -401c0590D_kwJDU59X8NyvqSv_Cl2A xenolinux-2.4.26-sparse/include/linux/sched.h
   3.238 -40a248afgI0_JKthdYAe8beVfXSTpQ xenolinux-2.4.26-sparse/include/linux/skbuff.h
   3.239 -3e5a4e686V0nioX2ZpFf056sgvdiQw xenolinux-2.4.26-sparse/include/linux/sunrpc/debug.h
   3.240 -401c0592pLrp_aCbQRo9GXiYQQaVVA xenolinux-2.4.26-sparse/include/linux/timer.h
   3.241 -3e5a4e68W_hpMlM3u_-QOKMp3gzcwQ xenolinux-2.4.26-sparse/init/do_mounts.c
   3.242 -3f9d4b44247udoqWEgFkaHiWv6Uvyg xenolinux-2.4.26-sparse/kernel/time.c
   3.243 -401c059bjLBFYHRD4Py2uM3eA1D4zQ xenolinux-2.4.26-sparse/kernel/timer.c
   3.244 -3e6e7c1efbQe93xCvOpOVCnXTMmQ5w xenolinux-2.4.26-sparse/mkbuildtree
   3.245 -406aeeafkrnCuIVWLFv3kfn4uAD5Eg xenolinux-2.4.26-sparse/mm/highmem.c
   3.246 -3e5a4e68GxCIaFH4sy01v1wjapetaA xenolinux-2.4.26-sparse/mm/memory.c
   3.247 -3f108af5VxPkLv13tXpXgoRKALQtXQ xenolinux-2.4.26-sparse/mm/mprotect.c
   3.248 -3e5a4e681xMPdF9xCMwpyfuYMySU5g xenolinux-2.4.26-sparse/mm/mremap.c
   3.249 -409ba2e7akOFqQUg6Qyg2s28xcXiMg xenolinux-2.4.26-sparse/mm/page_alloc.c
   3.250 -3e5a4e683HKVU-sxtagrDasRB8eBVw xenolinux-2.4.26-sparse/mm/swapfile.c
   3.251 -3f108af81Thhb242EmKjGCYkjx-GJA xenolinux-2.4.26-sparse/mm/vmalloc.c
   3.252 -407eb087XaNDLn8thVDLH-rI0hG-Xw xenolinux-sparse
     4.1 --- a/BitKeeper/etc/ignore	Wed Jun 09 15:42:10 2004 +0000
     4.2 +++ b/BitKeeper/etc/ignore	Wed Jun 09 16:36:08 2004 +0000
     4.3 @@ -6,6 +6,7 @@ PENDING/*
     4.4  *.a
     4.5  *.pyc
     4.6  extras/mini-os/h/hypervisor-ifs
     4.7 +linux-xen-sparse
     4.8  tools/*/build/lib*/*.py
     4.9  tools/balloon/balloon
    4.10  tools/misc/miniterm/miniterm
     5.1 --- a/Makefile	Wed Jun 09 15:42:10 2004 +0000
     5.2 +++ b/Makefile	Wed Jun 09 16:36:08 2004 +0000
     5.3 @@ -1,16 +1,8 @@
     5.4 -
     5.5 +#
     5.6  # Grand Unified Makefile for Xen.
     5.7  #
     5.8 -# Builds everything except Linux:
     5.9 -#  cd xenolinux-<version>-sparse
    5.10 -#  ./mkbuildtree <build dir>
    5.11 -#  cd <build dir>
    5.12 -#  ARCH=xen make oldconfig
    5.13 -#  ARCH=xen make dep
    5.14 -#  ARCH=xen make bzImage
    5.15 -#  (<build dir> should be a vanilla linux tree with matching version)
    5.16  
    5.17 -all:	
    5.18 +all: make-symlinks
    5.19  	$(MAKE) -C xen
    5.20  	$(MAKE) -C tools
    5.21  
    5.22 @@ -22,6 +14,31 @@ dist: all
    5.23  	$(MAKE) prefix=`pwd`/../install dist=yes -C xen install
    5.24  	$(MAKE) prefix=`pwd`/../install dist=yes -C tools install
    5.25  
    5.26 -clean:
    5.27 +LINUX_SRC        ?= ../linux-2.4.26.tar.gz
    5.28 +LINUX_CONFIG_DIR ?= ../install/config
    5.29 +world: dist
    5.30 +	$(RM) ../linux-2.4.26-xen
    5.31 +	tar -x -z -C .. -f $(LINUX_SRC)
    5.32 +	mv ../linux-2.4.26 ../linux-2.4.26-xen
    5.33 +	cd ../linux-2.4.26-xen
    5.34 +	cp $(LINUX_CONFIG_DIR)/dom0 .config
    5.35 +	ARCH=xen make oldconfig; ARCH=xen make dep; ARCH=xen make bzImage
    5.36 +	install -m0644 arch/xen/boot/bzImage \
    5.37 +		../install/boot/vmlinuz-2.4.26-xen0
    5.38 +	install -m0644 vmlinux ../install/boot/vmlinux-syms-2.4.26-xen0
    5.39 +	ARCH=xen make mrproper
    5.40 +	cp $(LINUX_CONFIG_DIR)/unprivileged .config
    5.41 +	ARCH=xen make oldconfig; ARCH=xen make dep; ARCH=xen make bzImage
    5.42 +	install -m0644 arch/xen/boot/bzImage \
    5.43 +		../install/boot/vmlinuz-2.4.26-xen
    5.44 +	install -m0644 vmlinux ../install/boot/vmlinux-syms-2.4.26-xen
    5.45 +
    5.46 +clean: delete-symlinks
    5.47  	$(MAKE) -C xen clean
    5.48  	$(MAKE) -C tools clean
    5.49 +
    5.50 +make-symlinks:
    5.51 +	ln -sf linux-2.4.26-xen-sparse linux-xen-sparse
    5.52 +
    5.53 +delete-symlinks:
    5.54 +	$(RM) linux-xen-sparse
     6.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     6.2 +++ b/linux-2.4.26-xen-sparse/Documentation/Configure.help	Wed Jun 09 16:36:08 2004 +0000
     6.3 @@ -0,0 +1,29164 @@
     6.4 +# Maintained by:
     6.5 +#	Eric S. Raymond <mailto:esr@thyrsus.com>
     6.6 +#	Steven Cole <mailto:elenstev@mesatop.com>
     6.7 +#
     6.8 +# Translations of this file available on the WWW:
     6.9 +#
    6.10 +#   - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
    6.11 +#     <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
    6.12 +#   - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
    6.13 +#     <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
    6.14 +#   - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
    6.15 +#     <http://www.traduc.org/kernelfr/>
    6.16 +#   - Polish, by Dominik Mierzejewski <mailto:dominik@piorunek.pl>, at
    6.17 +#     <http://www.piorunek.pl/~dominik/linux/kernel/>
    6.18 +#   - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
    6.19 +#     also includes infrastructure to support different languages.
    6.20 +#   - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
    6.21 +#     <http://www.terra.es/personal7/bella5/traduccions.htm>
    6.22 +#
    6.23 +# Information about what a kernel is, what it does, how to patch and
    6.24 +# compile it and much more is contained in the Kernel-HOWTO, available
    6.25 +# at <http://www.tldp.org/docs.html#howto>. Before you start
    6.26 +# compiling, make sure that you have the necessary versions of all
    6.27 +# programs and libraries required to compile and run this kernel; they
    6.28 +# are listed in the <file:Documentation/Changes>. Make sure to read the
    6.29 +# toplevel kernel README file as well.
    6.30 +#
    6.31 +# Format of this file: description<nl>variable<nl>help text<nl><nl>.
    6.32 +# The help texts may contain empty lines, but every non-empty line must
    6.33 +# be indented two positions.  Order of the help texts does not matter,
    6.34 +# however, no variable should be documented twice: if it is, only the
    6.35 +# first occurrence will be used. We try to keep the help texts of related
    6.36 +# variables close together. Lines starting with `#' are ignored. To be
    6.37 +# nice to menuconfig, limit your line length to 70 characters. Use emacs'
    6.38 +# kfill.el to edit and ispell.el to spell check this file or you lose.
    6.39 +#
    6.40 +# Comments of the form "# Choice:" followed by a menu name are used
    6.41 +# internally by the maintainers' consistency-checking tools.
    6.42 +#
    6.43 +# If you add a help text to this file, please try to be as gentle as
    6.44 +# possible. Don't use unexplained acronyms and generally write for the
    6.45 +# hypothetical ignorant but intelligent user who has just bought a PC,
    6.46 +# removed Windows, installed Linux and is now recompiling the kernel
    6.47 +# for the first time. Tell them what to do if they're unsure. Technical
    6.48 +# information should go in a README in the Documentation directory.
    6.49 +#
    6.50 +# Mention all the relevant READMEs and HOWTOs in the help text.
    6.51 +# Make them file URLs relative to the top level of the source tree so
    6.52 +# that help browsers can turn them into hotlinks.  All URLs should be
    6.53 +# surrounded by <>.
    6.54 +#
    6.55 +# Repetitions are fine since the help texts are not meant to be read
    6.56 +# in sequence.  It is good style to include URLs pointing to more
    6.57 +# detailed technical information, pictures of the hardware, etc.
    6.58 +#
    6.59 +# The most important thing to include in a help entry is *motivation*.
    6.60 +# Explain why someone configuring a kernel might want to select your
    6.61 +# option.
    6.62 +#
    6.63 +# All this was shamelessly stolen from numerous different sources. Many
    6.64 +# thanks to all the contributors. Feel free to use these help texts in
    6.65 +# your own kernel configuration tools. The texts are copyrighted (c)
    6.66 +# 1995-2000 by Axel Boldt and many others and are governed by the GNU
    6.67 +# General Public License.
    6.68 +
    6.69 +Prompt for development and/or incomplete code/drivers
    6.70 +CONFIG_EXPERIMENTAL
    6.71 +  Some of the various things that Linux supports (such as network
    6.72 +  drivers, file systems, network protocols, etc.) can be in a state
    6.73 +  of development where the functionality, stability, or the level of
    6.74 +  testing is not yet high enough for general use. This is usually
    6.75 +  known as the "alpha-test" phase among developers. If a feature is
    6.76 +  currently in alpha-test, then the developers usually discourage
    6.77 +  uninformed widespread use of this feature by the general public to
    6.78 +  avoid "Why doesn't this work?" type mail messages. However, active
    6.79 +  testing and use of these systems is welcomed. Just be aware that it
    6.80 +  may not meet the normal level of reliability or it may fail to work
    6.81 +  in some special cases. Detailed bug reports from people familiar
    6.82 +  with the kernel internals are usually welcomed by the developers
    6.83 +  (before submitting bug reports, please read the documents
    6.84 +  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
    6.85 +  <file:Documentation/BUG-HUNTING>, and
    6.86 +  <file:Documentation/oops-tracing.txt> in the kernel source).
    6.87 +
    6.88 +  This option will also make obsoleted drivers available. These are
    6.89 +  drivers that have been replaced by something else, and/or are
    6.90 +  scheduled to be removed in a future kernel release.
    6.91 +
    6.92 +  Unless you intend to help test and develop a feature or driver that
    6.93 +  falls into this category, or you have a situation that requires
    6.94 +  using these features, you should probably say N here, which will
    6.95 +  cause the configurator to present you with fewer choices. If
    6.96 +  you say Y here, you will be offered the choice of using features or
    6.97 +  drivers that are currently considered to be in the alpha-test phase.
    6.98 +
    6.99 +Prompt for drivers for obsolete features and hardware
   6.100 +CONFIG_OBSOLETE
   6.101 +  Obsolete drivers have usually been replaced by more recent software
   6.102 +  that can talk to the same hardware.  Obsolete hardware is things
   6.103 +  like MGA monitors that you are very unlikely to see on today's
   6.104 +  systems.
   6.105 +
   6.106 +Prompt for advanced kernel configuration options
   6.107 +CONFIG_ADVANCED_OPTIONS
   6.108 +  This option will enable prompting for a variety of advanced kernel
   6.109 +  configuration options.  These options can cause the kernel to not
   6.110 +  work if they are set incorrectly, but can be used to optimize certain
   6.111 +  aspects of kernel memory management.
   6.112 +
   6.113 +  Unless you know what you are doing you *should not* enable this option.
   6.114 +
   6.115 +Symmetric Multi-Processing support
   6.116 +CONFIG_SMP
   6.117 +  This enables support for systems with more than one CPU. If you have
   6.118 +  a system with only one CPU, like most personal computers, say N. If
   6.119 +  you have a system with more than one CPU, say Y.
   6.120 +
   6.121 +  If you say N here, the kernel will run on single and multiprocessor
   6.122 +  machines, but will use only one CPU of a multiprocessor machine. If
   6.123 +  you say Y here, the kernel will run on many, but not all,
   6.124 +  single machines. On a singleprocessor machine, the kernel
   6.125 +  will run faster if you say N here.
   6.126 +
   6.127 +  Note that if you say Y here and choose architecture "586" or
   6.128 +  "Pentium" under "Processor family", the kernel will not work on 486
   6.129 +  architectures. Similarly, multiprocessor kernels for the "PPro"
   6.130 +  architecture may not work on all Pentium based boards.
   6.131 +
   6.132 +  People using multiprocessor machines who say Y here should also say
   6.133 +  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
   6.134 +  Management" code will be disabled if you say Y here.
   6.135 +
   6.136 +  See also the <file:Documentation/smp.tex>,
   6.137 +  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
   6.138 +  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
   6.139 +  <http://www.tldp.org/docs.html#howto>.
   6.140 +
   6.141 +  If you don't know what to do here, say N.
   6.142 +
   6.143 +Maximum number of CPUs
   6.144 +CONFIG_NR_CPUS
   6.145 +  This allows you to specify the maximum number of CPUs which this
   6.146 +  kernel will support.  The maximum supported value is 32 and the
   6.147 +  mimimum value which makes sense is 2.
   6.148 +
   6.149 +  This is purely to save memory - each supported CPU adds
   6.150 +  approximately eight kilobytes to the kernel image.
   6.151 +
   6.152 +Intel or compatible 80x86 processor
   6.153 +CONFIG_X86
   6.154 +  This is Linux's home port.  Linux was originally native to the Intel
   6.155 +  386, and runs on all the later x86 processors including the Intel
   6.156 +  486, 586, Pentiums, and various instruction-set-compatible chips by
   6.157 +  AMD, Cyrix, and others.
   6.158 +
   6.159 +Alpha processor
   6.160 +CONFIG_ALPHA
   6.161 +  The Alpha is a 64-bit general-purpose processor designed and
   6.162 +  marketed by the Digital Equipment Corporation of blessed memory, now
   6.163 +  Compaq.  Alpha Linux dates from 1995-1996 and was the first non-x86
   6.164 +  port. The Alpha Linux project has a home page at
   6.165 +  <http://www.alphalinux.org/>.
   6.166 +
   6.167 +32-bit Sun Sparc
   6.168 +CONFIG_SPARC32
   6.169 +  SPARC is a family of RISC microprocessors designed and marketed by
   6.170 +  Sun Microsystems, incorporated.  They are very widely found in Sun
   6.171 +  workstations and clones. This port covers the original 32-bit SPARC;
   6.172 +  it is old and stable and usually considered one of the "big three"
   6.173 +  along with the Intel and Alpha ports.  The UltraLinux project
   6.174 +  maintains both the SPARC32 and SPARC64 ports; its web page is
   6.175 +  available at <http://www.ultralinux.org/>.
   6.176 +
   6.177 +64-bit Sun Sparc
   6.178 +CONFIG_SPARC64
   6.179 +  SPARC is a family of RISC microprocessors designed and marketed by
   6.180 +  Sun Microsystems, incorporated.  This port covers the newer 64-bit
   6.181 +  UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
   6.182 +  SPARC64 ports; its web page is available at
   6.183 +  <http://www.ultralinux.org/>.
   6.184 +
   6.185 +Power PC processor
   6.186 +CONFIG_PPC
   6.187 +  The PowerPC is a very capable 32-bit RISC processor from Motorola,
   6.188 +  the successor to their 68000 and 88000 series.  It powers recent
   6.189 +  Macintoshes and also a widely-used series of single-board computers
   6.190 +  from Motorola.  The Linux PowerPC port has a home page at
   6.191 +  <http://penguinppc.org/>.
   6.192 +
   6.193 +Motorola 68K processors
   6.194 +CONFIG_M68K
   6.195 +  The Motorola 68K microprocessors are now obsolete, having been
   6.196 +  superseded by the PowerPC line also from Motorola.  But they powered
   6.197 +  the first wave of workstation hardware in the 1980s, including Sun
   6.198 +  workstations; they were also the basis of the original Amiga and
   6.199 +  later Atari personal computers.  A lot of this hardware is still
   6.200 +  around.  The m68k project has a home page at
   6.201 +  <http://www.linux-m68k.org/>.
   6.202 +
   6.203 +ARM processors
   6.204 +CONFIG_ARM
   6.205 +  The ARM series is a line of low-power-consumption RISC chip designs
   6.206 +  licensed by ARM ltd and targeted at embedded applications and
   6.207 +  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
   6.208 +  manufactured, but  legacy ARM-based PC hardware remains popular in
   6.209 +  Europe.  There is an ARM Linux project with a web page at
   6.210 +  <http://www.arm.linux.org.uk/>.
   6.211 +
   6.212 +SuperH processors
   6.213 +CONFIG_SUPERH
   6.214 +  The SuperH is a RISC processor targeted for use in embedded systems
   6.215 +  and consumer electronics; it was also used in the Sega Dreamcast
   6.216 +  gaming console.  The SuperH port has a home page at
   6.217 +  <http://www.sh-linux.org/>.
   6.218 +
   6.219 +IA64 processors, including Intel Itanium
   6.220 +CONFIG_IA64
   6.221 +  The Itanium is Intel's 64-bit successor to the 32-bit X86 line.  As
   6.222 +  of early 2001 it is not yet in widespread production use.  The Linux
   6.223 +  IA-64 project has a home page at <http://www.linuxia64.org/>.
   6.224 +
   6.225 +HP PA-RISC processor
   6.226 +CONFIG_PARISC
   6.227 +  The PA-RISC microprocessor is a RISC chip designed by
   6.228 +  Hewlett-Packard and used in their line of workstations.  The PA-RISC
   6.229 +  Linux project has a home page at <www.parisc-linux.org>.
   6.230 +
   6.231 +IBM System/390
   6.232 +CONFIG_S390
   6.233 +  Linux now runs on the venerable System/390 mainframe from IBM, in a
   6.234 +  guest partition under VM.  In fact, over 40,000 simultaneous Linux
   6.235 +  images have been run on a single mainframe!  The S390 Linux project
   6.236 +  has a home page at <http://linux.s390.org/>.
   6.237 +
   6.238 +Axis Communications ETRAX 100LX embedded network CPU
   6.239 +CONFIG_CRIS
   6.240 +  Linux has been ported to run on the Axis Communications ETRAX 100LX
   6.241 +  CPU and the single-board computers built around it, targeted for
   6.242 +  network and embedded applications.  For more information see the
   6.243 +  Axis Communication site, <http://developer.axis.com/>.
   6.244 +
   6.245 +Unsynced TSC support
   6.246 +CONFIG_X86_TSC_DISABLE
   6.247 +  This option is used for getting Linux to run on a NUMA multi-node 
   6.248 +  boxes, laptops and other systems suffering from unsynced TSCs or 
   6.249 +  TSC drift, which can cause gettimeofday to return non-monotonic values. 
   6.250 +  Choosing this option will disable the CONFIG_X86_TSC optimization,
   6.251 +  and allows you to then specify "notsc" as a boot option regardless of 
   6.252 +  which processor you have compiled for. 
   6.253 +  
   6.254 +  NOTE: If your system hangs when init should run, you are probably
   6.255 +  using a i686 compiled glibc which reads the TSC without checking for 
   6.256 +  availability. Boot without "notsc" and install a i386 compiled glibc 
   6.257 +  to solve the problem.
   6.258 +
   6.259 +  If unsure, say N.
   6.260 +
   6.261 +Multiquad support for NUMAQ systems
   6.262 +CONFIG_X86_NUMAQ
   6.263 +  This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
   6.264 +  multiquad box. This changes the way that processors are bootstrapped,
   6.265 +  and uses Clustered Logical APIC addressing mode instead of Flat Logical.
   6.266 +  You will need a new lynxer.elf file to flash your firmware with - send
   6.267 +  email to Martin.Bligh@us.ibm.com
   6.268 +
   6.269 +Support for IBM Summit (EXA) systems
   6.270 +CONFIG_X86_SUMMIT
   6.271 +  This option is needed for IBM systems that use the Summit/EXA chipset.
   6.272 +  (EXA: Extendable Xseries Architecture)In particular, it is needed for 
   6.273 +  the x440 (even for the 4-CPU model).
   6.274 +
   6.275 +  If you don't have this computer, you may safely say N.
   6.276 +
   6.277 +IO-APIC support on uniprocessors
   6.278 +CONFIG_X86_UP_IOAPIC
   6.279 +  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
   6.280 +  SMP-capable replacement for PC-style interrupt controllers. Most
   6.281 +  SMP systems and a small number of uniprocessor systems have one.
   6.282 +  If you have a single-CPU system with an IO-APIC, you can say Y here
   6.283 +  to use it. If you say Y here even though your machine doesn't have
   6.284 +  an IO-APIC, then the kernel will still run with no slowdown at all.
   6.285 +
   6.286 +  If you have a system with several CPUs, you do not need to say Y
   6.287 +  here: the IO-APIC will be used automatically.
   6.288 +
   6.289 +Local APIC Support on Uniprocessors
   6.290 +CONFIG_X86_UP_APIC
   6.291 +  A local APIC (Advanced Programmable Interrupt Controller) is an
   6.292 +  integrated interrupt controller in the CPU. If you have a single-CPU
   6.293 +  system which has a processor with a local APIC, you can say Y here to
   6.294 +  enable and use it. If you say Y here even though your machine doesn't
   6.295 +  have a local APIC, then the kernel will still run with no slowdown at
   6.296 +  all. The local APIC supports CPU-generated self-interrupts (timer,
   6.297 +  performance counters), and the NMI watchdog which detects hard lockups.
   6.298 +
   6.299 +  If you have a system with several CPUs, you do not need to say Y
   6.300 +  here: the local APIC will be used automatically.
   6.301 +
   6.302 +Kernel math emulation
   6.303 +CONFIG_MATH_EMULATION
   6.304 +  Linux can emulate a math coprocessor (used for floating point
   6.305 +  operations) if you don't have one. 486DX and Pentium processors have
   6.306 +  a math coprocessor built in, 486SX and 386 do not, unless you added
   6.307 +  a 487DX or 387, respectively. (The messages during boot time can
   6.308 +  give you some hints here ["man dmesg"].) Everyone needs either a
   6.309 +  coprocessor or this emulation.
   6.310 +
   6.311 +  If you don't have a math coprocessor, you need to say Y here; if you
   6.312 +  say Y here even though you have a coprocessor, the coprocessor will
   6.313 +  be used nevertheless. (This behaviour can be changed with the kernel
   6.314 +  command line option "no387", which comes handy if your coprocessor
   6.315 +  is broken. Try "man bootparam" or see the documentation of your boot
   6.316 +  loader (lilo or loadlin) about how to pass options to the kernel at
   6.317 +  boot time.) This means that it is a good idea to say Y here if you
   6.318 +  intend to use this kernel on different machines.
   6.319 +
   6.320 +  More information about the internals of the Linux math coprocessor
   6.321 +  emulation can be found in <file:arch/i386/math-emu/README>.
   6.322 +
   6.323 +  If you are not sure, say Y; apart from resulting in a 66 KB bigger
   6.324 +  kernel, it won't hurt.
   6.325 +
   6.326 +Timer and CPU usage LEDs
   6.327 +CONFIG_LEDS
   6.328 +  If you say Y here, the LEDs on your machine will be used
   6.329 +  to provide useful information about your current system status.
   6.330 +
   6.331 +  If you are compiling a kernel for a NetWinder or EBSA-285, you will
   6.332 +  be able to select which LEDs are active using the options below. If
   6.333 +  you are compiling a kernel for the EBSA-110 or the LART however, the
   6.334 +  red LED will simply flash regularly to indicate that the system is
   6.335 +  still functional. It is safe to say Y here if you have a CATS
   6.336 +  system, but the driver will do nothing.
   6.337 +
   6.338 +Timer LED
   6.339 +CONFIG_LEDS_TIMER
   6.340 +  If you say Y here, one of the system LEDs (the green one on the
   6.341 +  NetWinder, the amber one on the EBSA285, or the red one on the LART)
   6.342 +  will flash regularly to indicate that the system is still
   6.343 +  operational. This is mainly useful to kernel hackers who are
   6.344 +  debugging unstable kernels.
   6.345 +
   6.346 +  The LART uses the same LED for both Timer LED and CPU usage LED
   6.347 +  functions. You may choose to use both, but the Timer LED function
   6.348 +  will overrule the CPU usage LED.
   6.349 +
   6.350 +CPU usage LED
   6.351 +CONFIG_LEDS_CPU
   6.352 +  If you say Y here, the red LED will be used to give a good real
   6.353 +  time indication of CPU usage, by lighting whenever the idle task
   6.354 +  is not currently executing.
   6.355 +
   6.356 +  The LART uses the same LED for both Timer LED and CPU usage LED
   6.357 +  functions. You may choose to use both, but the Timer LED function
   6.358 +  will overrule the CPU usage LED.
   6.359 +
   6.360 +Kernel FP software completion
   6.361 +CONFIG_MATHEMU
   6.362 +  This option is required for IEEE compliant floating point arithmetic
   6.363 +  on the Alpha. The only time you would ever not say Y is to say M in
   6.364 +  order to debug the code. Say Y unless you know what you are doing.
   6.365 +
   6.366 +# Choice: himem
   6.367 +High Memory support
   6.368 +CONFIG_NOHIGHMEM
   6.369 +  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
   6.370 +  However, the address space of 32-bit x86 processors is only 4
   6.371 +  Gigabytes large. That means that, if you have a large amount of
   6.372 +  physical memory, not all of it can be "permanently mapped" by the
   6.373 +  kernel. The physical memory that's not permanently mapped is called
   6.374 +  "high memory".
   6.375 +
   6.376 +  If you are compiling a kernel which will never run on a machine with
   6.377 +  more than 960 megabytes of total physical RAM, answer "off" here (default
   6.378 +  choice and suitable for most users). This will result in a "3GB/1GB"
   6.379 +  split: 3GB are mapped so that each process sees a 3GB virtual memory
   6.380 +  space and the remaining part of the 4GB virtual memory space is used
   6.381 +  by the kernel to permanently map as much physical memory as
   6.382 +  possible.
   6.383 +
   6.384 +  If the machine has between 1 and 4 Gigabytes physical RAM, then
   6.385 +  answer "4GB" here.
   6.386 +
   6.387 +  If more than 4 Gigabytes is used then answer "64GB" here. This
   6.388 +  selection turns Intel PAE (Physical Address Extension) mode on.
   6.389 +  PAE implements 3-level paging on IA32 processors. PAE is fully
   6.390 +  supported by Linux, PAE mode is implemented on all recent Intel
   6.391 +  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
   6.392 +  then the kernel will not boot on CPUs that don't support PAE!
   6.393 +
   6.394 +  The actual amount of total physical memory will either be auto
   6.395 +  detected or can be forced by using a kernel command line option such
   6.396 +  as "mem=256M". (Try "man bootparam" or see the documentation of your
   6.397 +  boot loader (grub, lilo or loadlin) about how to pass options to the
   6.398 +  kernel at boot time.)
   6.399 +
   6.400 +  If unsure, say "off".
   6.401 +
   6.402 +4GB
   6.403 +CONFIG_HIGHMEM4G
   6.404 +  Select this if you have a 32-bit processor and between 1 and 4
   6.405 +  gigabytes of physical RAM.
   6.406 +
   6.407 +64GB
   6.408 +CONFIG_HIGHMEM64G
   6.409 +  Select this if you have a 32-bit processor and more than 4
   6.410 +  gigabytes of physical RAM.
   6.411 +
   6.412 +HIGHMEM I/O support
   6.413 +CONFIG_HIGHIO
   6.414 +  If you want to be able to do I/O to high memory pages, say Y.
   6.415 +  Otherwise low memory pages are used as bounce buffers causing a
   6.416 +  degrade in performance.
   6.417 +
   6.418 +OOM killer support
   6.419 +CONFIG_OOM_KILLER
   6.420 +   This option selects the kernel behaviour during total out of memory
   6.421 +   condition. 
   6.422 +
   6.423 +   The default behaviour is to, as soon as no freeable memory and no swap
   6.424 +   space are available, kill the task which tries to allocate memory. 
   6.425 +   The default behaviour is very reliable.
   6.426 +
   6.427 +   If you select this option, as soon as no freeable memory is available, 
   6.428 +   the kernel will try to select the "best" task to be killed.
   6.429 +
   6.430 +   If unsure, say N.
   6.431 +
   6.432 +Normal floppy disk support
   6.433 +CONFIG_BLK_DEV_FD
   6.434 +  If you want to use the floppy disk drive(s) of your PC under Linux,
   6.435 +  say Y. Information about this driver, especially important for IBM
   6.436 +  Thinkpad users, is contained in <file:Documentation/floppy.txt>.
   6.437 +  That file also contains the location of the Floppy driver FAQ as
   6.438 +  well as location of the fdutils package used to configure additional
   6.439 +  parameters of the driver at run time.
   6.440 +
   6.441 +  This driver is also available as a module ( = code which can be
   6.442 +  inserted in and removed from the running kernel whenever you want).
   6.443 +  The module will be called floppy.o. If you want to compile it as a
   6.444 +  module, say M here and read <file:Documentation/modules.txt>.
   6.445 +
   6.446 +iSeries Virtual I/O Disk Support
   6.447 +CONFIG_VIODASD
   6.448 +  If you are running on an iSeries system and you want to use
   6.449 +  virtual disks created and managed by OS/400, say Y.
   6.450 +
   6.451 +iSeries Virtual I/O Disk IDE Emulation
   6.452 +CONFIG_VIODASD_IDE
   6.453 +  This causes the iSeries virtual disks to look like IDE disks.
   6.454 +  If you have programs or utilities that only support certain
   6.455 +  kinds of disks, this option will cause iSeries virtual disks
   6.456 +  to pretend to be IDE disks, which may satisfy the program.
   6.457 +
   6.458 +Support for PowerMac floppy
   6.459 +CONFIG_MAC_FLOPPY
   6.460 +  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
   6.461 +  floppy controller, say Y here. Most commonly found in PowerMacs.
   6.462 +
   6.463 +RAM disk support
   6.464 +CONFIG_BLK_DEV_RAM
   6.465 +  Saying Y here will allow you to use a portion of your RAM memory as
   6.466 +  a block device, so that you can make file systems on it, read and
   6.467 +  write to it and do all the other things that you can do with normal
   6.468 +  block devices (such as hard drives). It is usually used to load and
   6.469 +  store a copy of a minimal root file system off of a floppy into RAM
   6.470 +  during the initial install of Linux.
   6.471 +
   6.472 +  Note that the kernel command line option "ramdisk=XX" is now
   6.473 +  obsolete. For details, read <file:Documentation/ramdisk.txt>.
   6.474 +
   6.475 +  If you want to compile this as a module ( = code which can be
   6.476 +  inserted in and removed from the running kernel whenever you want),
   6.477 +  say M and read <file:Documentation/modules.txt>. The module will be
   6.478 +  called rd.o.
   6.479 +
   6.480 +  Most normal users won't need the RAM disk functionality, and can
   6.481 +  thus say N here.
   6.482 +
   6.483 +Default RAM disk size
   6.484 +CONFIG_BLK_DEV_RAM_SIZE
   6.485 +  The default value is 4096. Only change this if you know what are
   6.486 +  you doing. If you are using IBM S/390, then set this to 8192.
   6.487 +
   6.488 +Initial RAM disk (initrd) support
   6.489 +CONFIG_BLK_DEV_INITRD
   6.490 +  The initial RAM disk is a RAM disk that is loaded by the boot loader
   6.491 +  (loadlin or lilo) and that is mounted as root before the normal boot
   6.492 +  procedure. It is typically used to load modules needed to mount the
   6.493 +  "real" root file system, etc. See <file:Documentation/initrd.txt>
   6.494 +  for details.
   6.495 +
   6.496 +Embed root filesystem ramdisk into the kernel
   6.497 +CONFIG_EMBEDDED_RAMDISK
   6.498 +  Select this option if you want to build the ramdisk image into the
   6.499 +  the final kernel binary.
   6.500 +
   6.501 +Filename of gziped ramdisk image
   6.502 +CONFIG_EMBEDDED_RAMDISK_IMAGE
   6.503 +  This is the filename of the ramdisk image to be built into the
   6.504 +  kernel.  Relative pathnames are relative to arch/mips/ramdisk/.
   6.505 +  The ramdisk image is not part of the kernel distribution; you must
   6.506 +  provide one yourself.
   6.507 +
   6.508 +Loopback device support
   6.509 +CONFIG_BLK_DEV_LOOP
   6.510 +  Saying Y here will allow you to use a regular file as a block
   6.511 +  device; you can then create a file system on that block device and
   6.512 +  mount it just as you would mount other block devices such as hard
   6.513 +  drive partitions, CD-ROM drives or floppy drives. The loop devices
   6.514 +  are block special device files with major number 7 and typically
   6.515 +  called /dev/loop0, /dev/loop1 etc.
   6.516 +
   6.517 +  This is useful if you want to check an ISO 9660 file system before
   6.518 +  burning the CD, or if you want to use floppy images without first
   6.519 +  writing them to floppy. Furthermore, some Linux distributions avoid
   6.520 +  the need for a dedicated Linux partition by keeping their complete
   6.521 +  root file system inside a DOS FAT file using this loop device
   6.522 +  driver.
   6.523 +
   6.524 +  The loop device driver can also be used to "hide" a file system in a
   6.525 +  disk partition, floppy, or regular file, either using encryption
   6.526 +  (scrambling the data) or steganography (hiding the data in the low
   6.527 +  bits of, say, a sound file). This is also safe if the file resides
   6.528 +  on a remote file server. If you want to do this, you will first have
   6.529 +  to acquire and install a kernel patch from
   6.530 +  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
   6.531 +  say Y to this option.
   6.532 +
   6.533 +  Note that alternative ways to use encrypted file systems are
   6.534 +  provided by the cfs package, which can be gotten from
   6.535 +  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
   6.536 +  package, available at <http://tcfs.dia.unisa.it/>. You do not need
   6.537 +  to say Y here if you want to use one of these. However, using cfs
   6.538 +  requires saying Y to "NFS file system support" below while using
   6.539 +  tcfs requires applying a kernel patch. An alternative steganography
   6.540 +  solution is provided by StegFS, also available from
   6.541 +  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
   6.542 +
   6.543 +  To use the loop device, you need the losetup utility and a recent
   6.544 +  version of the mount program, both contained in the util-linux
   6.545 +  package. The location and current version number of util-linux is
   6.546 +  contained in the file <file:Documentation/Changes>.
   6.547 +
   6.548 +  Note that this loop device has nothing to do with the loopback
   6.549 +  device used for network connections from the machine to itself.
   6.550 +
   6.551 +  If you want to compile this driver as a module ( = code which can be
   6.552 +  inserted in and removed from the running kernel whenever you want),
   6.553 +  say M here and read <file:Documentation/modules.txt>. The module
   6.554 +  will be called loop.o.
   6.555 +
   6.556 +  Most users will answer N here.
   6.557 +
   6.558 +Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
   6.559 +CONFIG_BLK_DEV_UMEM
   6.560 +  Saying Y here will include support for the MM5415 family of
   6.561 +  battery backed (Non-volatile) RAM cards.
   6.562 +  <http://www.umem.com/>
   6.563 +
   6.564 +  The cards appear as block devices that can be partitioned into
   6.565 +  as many as 15 partitions.
   6.566 +
   6.567 +  If you want to compile this driver as a module ( = code which can be
   6.568 +  inserted in and removed from the running kernel whenever you want),
   6.569 +  say M here and read Documentation/modules.txt. The module will be
   6.570 +  called umem.o.
   6.571 +
   6.572 +  The umem driver has been allocated block major number 116.
   6.573 +  See Documentation/devices.txt for recommended device naming.
   6.574 +
   6.575 +Network block device support
   6.576 +CONFIG_BLK_DEV_NBD
   6.577 +  Saying Y here will allow your computer to be a client for network
   6.578 +  block devices, i.e. it will be able to use block devices exported by
   6.579 +  servers (mount file systems on them etc.). Communication between
   6.580 +  client and server works over TCP/IP networking, but to the client
   6.581 +  program this is hidden: it looks like a regular local file access to
   6.582 +  a block device special file such as /dev/nd0.
   6.583 +
   6.584 +  Network block devices also allows you to run a block-device in
   6.585 +  userland (making server and client physically the same computer,
   6.586 +  communicating using the loopback network device).
   6.587 +
   6.588 +  Read <file:Documentation/nbd.txt> for more information, especially
   6.589 +  about where to find the server code, which runs in user space and
   6.590 +  does not need special kernel support.
   6.591 +
   6.592 +  Note that this has nothing to do with the network file systems NFS
   6.593 +  or Coda; you can say N here even if you intend to use NFS or Coda.
   6.594 +
   6.595 +  If you want to compile this driver as a module ( = code which can be
   6.596 +  inserted in and removed from the running kernel whenever you want),
   6.597 +  say M here and read <file:Documentation/modules.txt>. The module
   6.598 +  will be called nbd.o.
   6.599 +
   6.600 +  If unsure, say N.
   6.601 +
   6.602 +XenoLinux virtual block device support
   6.603 +CONFIG_XEN_VBD
   6.604 +  Xen can export virtual block devices which map back to extents of
   6.605 +  blocks on the physical partitions.  This option is needed for
   6.606 +  Linux to make use of such devices when running as a Xen guest.
   6.607 +
   6.608 +  If unsure, say Y.
   6.609 +
   6.610 +Per partition statistics in /proc/partitions
   6.611 +CONFIG_BLK_STATS
   6.612 +  If you say yes here, your kernel will keep statistical information
   6.613 +  for every partition. The information includes things as numbers of
   6.614 +  read and write accesses, the number of merged requests etc.
   6.615 +
   6.616 +  This is required for the full functionality of sar(8) and interesting
   6.617 +  if you want to do performance tuning, by tweaking the elevator, e.g.
   6.618 +
   6.619 +  If unsure, say N.
   6.620 +
   6.621 +ATA/IDE/MFM/RLL support
   6.622 +CONFIG_IDE
   6.623 +  If you say Y here, your kernel will be able to manage low cost mass
   6.624 +  storage units such as ATA/(E)IDE and ATAPI units. The most common
   6.625 +  cases are IDE hard drives and ATAPI CD-ROM drives.
   6.626 +
   6.627 +  If your system is pure SCSI and doesn't use these interfaces, you
   6.628 +  can say N here.
   6.629 +
   6.630 +  Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
   6.631 +  for mass storage units such as hard disks. It was designed by
   6.632 +  Western Digital and Compaq Computer in 1984. It was then named
   6.633 +  ST506. Quite a number of disks use the IDE interface.
   6.634 +
   6.635 +  AT Attachment (ATA) is the superset of the IDE specifications.
   6.636 +  ST506 was also called ATA-1.
   6.637 +
   6.638 +  Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
   6.639 +  ATA-3. It provides support for larger disks (up to 8.4GB by means of
   6.640 +  the LBA standard), more disks (4 instead of 2) and for other mass
   6.641 +  storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
   6.642 +  ATA-4 and provides faster (and more CPU friendly) transfer modes
   6.643 +  than previous PIO (Programmed processor Input/Output) from previous
   6.644 +  ATA/IDE standards by means of fast DMA controllers.
   6.645 +
   6.646 +  ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
   6.647 +  CD-ROM drives, similar in many respects to the SCSI protocol.
   6.648 +
   6.649 +  SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
   6.650 +  designed in order to prevent data corruption and disk crash by
   6.651 +  detecting pre hardware failure conditions (heat, access time, and
   6.652 +  the like...). Disks built since June 1995 may follow this standard.
   6.653 +  The kernel itself don't manage this; however there are quite a
   6.654 +  number of user programs such as smart that can query the status of
   6.655 +  SMART parameters disk.
   6.656 +
   6.657 +  If you want to compile this driver as a module ( = code which can be
   6.658 +  inserted in and removed from the running kernel whenever you want),
   6.659 +  say M here and read <file:Documentation/modules.txt>. The module
   6.660 +  will be called ide.o.
   6.661 +
   6.662 +  For further information, please read <file:Documentation/ide.txt>.
   6.663 +
   6.664 +  If unsure, say Y.
   6.665 +
   6.666 +Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
   6.667 +CONFIG_BLK_DEV_IDE
   6.668 +  If you say Y here, you will use the full-featured IDE driver to
   6.669 +  control up to ten ATA/IDE interfaces, each being able to serve a
   6.670 +  "master" and a "slave" device, for a total of up to twenty ATA/IDE
   6.671 +  disk/cdrom/tape/floppy drives.
   6.672 +
   6.673 +  Useful information about large (>540 MB) IDE disks, multiple
   6.674 +  interfaces, what to do if ATA/IDE devices are not automatically
   6.675 +  detected, sound card ATA/IDE ports, module support, and other
   6.676 +  topics, is contained in <file:Documentation/ide.txt>. For detailed
   6.677 +  information about hard drives, consult the Disk-HOWTO and the
   6.678 +  Multi-Disk-HOWTO, available from
   6.679 +  <http://www.tldp.org/docs.html#howto>.
   6.680 +
   6.681 +  To fine-tune ATA/IDE drive/interface parameters for improved
   6.682 +  performance, look for the hdparm package at
   6.683 +  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   6.684 +
   6.685 +  If you want to compile this driver as a module ( = code which can be
   6.686 +  inserted in and removed from the running kernel whenever you want),
   6.687 +  say M here and read <file:Documentation/modules.txt> and
   6.688 +  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
   6.689 +  Do not compile this driver as a module if your root file system (the
   6.690 +  one containing the directory /) is located on an IDE device.
   6.691 +
   6.692 +  If you have one or more IDE drives, say Y or M here. If your system
   6.693 +  has no IDE drives, or if memory requirements are really tight, you
   6.694 +  could say N here, and select the "Old hard disk driver" below
   6.695 +  instead to save about 13 KB of memory in the kernel.
   6.696 +
   6.697 +Old hard disk (MFM/RLL/IDE) driver
   6.698 +CONFIG_BLK_DEV_HD_ONLY
   6.699 +  There are two drivers for MFM/RLL/IDE hard disks. Most people use
   6.700 +  the newer enhanced driver, but this old one is still around for two
   6.701 +  reasons. Some older systems have strange timing problems and seem to
   6.702 +  work only with the old driver (which itself does not work with some
   6.703 +  newer systems). The other reason is that the old driver is smaller,
   6.704 +  since it lacks the enhanced functionality of the new one. This makes
   6.705 +  it a good choice for systems with very tight memory restrictions, or
   6.706 +  for systems with only older MFM/RLL/ESDI drives. Choosing the old
   6.707 +  driver can save 13 KB or so of kernel memory.
   6.708 +
   6.709 +  If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
   6.710 +  instead of this one. For more detailed information, read the
   6.711 +  Disk-HOWTO, available from
   6.712 +  <http://www.tldp.org/docs.html#howto>.
   6.713 +
   6.714 +Use old disk-only driver on primary interface
   6.715 +CONFIG_BLK_DEV_HD_IDE
   6.716 +  There are two drivers for MFM/RLL/IDE disks.  Most people use just
   6.717 +  the new enhanced driver by itself.  This option however installs the
   6.718 +  old hard disk driver to control the primary IDE/disk interface in
   6.719 +  the system, leaving the new enhanced IDE driver to take care of only
   6.720 +  the 2nd/3rd/4th IDE interfaces.  Doing this will prevent you from
   6.721 +  having an IDE/ATAPI CD-ROM or tape drive connected to the primary
   6.722 +  IDE interface.  Choosing this option may be useful for older systems
   6.723 +  which have MFM/RLL/ESDI controller+drives at the primary port
   6.724 +  address (0x1f0), along with IDE drives at the secondary/3rd/4th port
   6.725 +  addresses.
   6.726 +
   6.727 +  Normally, just say N here; you will then use the new driver for all
   6.728 +  4 interfaces.
   6.729 +
   6.730 +Include IDE/ATA-2 DISK support
   6.731 +CONFIG_BLK_DEV_IDEDISK
   6.732 +  This will include enhanced support for MFM/RLL/IDE hard disks.  If
   6.733 +  you have a MFM/RLL/IDE disk, and there is no special reason to use
   6.734 +  the old hard disk driver instead, say Y.  If you have an SCSI-only
   6.735 +  system, you can say N here.
   6.736 +
   6.737 +  If you want to compile this driver as a module ( = code which can be
   6.738 +  inserted in and removed from the running kernel whenever you want),
   6.739 +  say M here and read <file:Documentation/modules.txt>.  The module
   6.740 +  will be called ide-disk.o.  Do not compile this driver as a module
   6.741 +  if your root file system (the one containing the directory /) is
   6.742 +  located on the IDE disk. If unsure, say Y.
   6.743 +
   6.744 +Use multi-mode by default
   6.745 +CONFIG_IDEDISK_MULTI_MODE
   6.746 +  If you get this error, try to say Y here:
   6.747 +
   6.748 +  hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
   6.749 +  hda: set_multmode: error=0x04 { DriveStatusError }
   6.750 +
   6.751 +  If in doubt, say N.
   6.752 +
   6.753 +PCMCIA IDE support
   6.754 +CONFIG_BLK_DEV_IDECS
   6.755 +  Support for outboard IDE disks, tape drives, and CD-ROM drives
   6.756 +  connected through a  PCMCIA card.
   6.757 +
   6.758 +  This driver is also available as a module ( = code which can be
   6.759 +  inserted in and removed from the running kernel whenever you want).
   6.760 +  If you want to compile it as a module, say M here and read
   6.761 +  <file:Documentation/modules.txt>. The module will be called
   6.762 +  ide-cs.o
   6.763 +
   6.764 +Include IDE/ATAPI CD-ROM support
   6.765 +CONFIG_BLK_DEV_IDECD
   6.766 +  If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
   6.767 +  a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
   6.768 +  SCSI protocol. Most new CD-ROM drives use ATAPI, including the
   6.769 +  NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
   6.770 +  double(2X) or better speed drives.
   6.771 +
   6.772 +  If you say Y here, the CD-ROM drive will be identified at boot time
   6.773 +  along with other IDE devices, as "hdb" or "hdc", or something
   6.774 +  similar (check the boot messages with dmesg). If this is your only
   6.775 +  CD-ROM drive, you can say N to all other CD-ROM options, but be sure
   6.776 +  to say Y or M to "ISO 9660 CD-ROM file system support".
   6.777 +
   6.778 +  Note that older versions of LILO (LInux LOader) cannot properly deal
   6.779 +  with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
   6.780 +  <ftp://brun.dyndns.org/pub/linux/lilo/>.
   6.781 +
   6.782 +  If you want to compile the driver as a module ( = code which can be
   6.783 +  inserted in and removed from the running kernel whenever you want),
   6.784 +  say M here and read <file:Documentation/modules.txt>.  The module
   6.785 +  will be called ide-cd.o.
   6.786 +
   6.787 +Include IDE/ATAPI TAPE support
   6.788 +CONFIG_BLK_DEV_IDETAPE
   6.789 +  If you have an IDE tape drive using the ATAPI protocol, say Y.
   6.790 +  ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
   6.791 +  similar to the SCSI protocol.  If you have an SCSI tape drive
   6.792 +  however, you can say N here.
   6.793 +
   6.794 +  You should also say Y if you have an OnStream DI-30 tape drive; this
   6.795 +  will not work with the SCSI protocol, until there is support for the
   6.796 +  SC-30 and SC-50 versions.
   6.797 +
   6.798 +  If you say Y here, the tape drive will be identified at boot time
   6.799 +  along with other IDE devices, as "hdb" or "hdc", or something
   6.800 +  similar, and will be mapped to a character device such as "ht0"
   6.801 +  (check the boot messages with dmesg).  Be sure to consult the
   6.802 +  <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
   6.803 +  for usage information.
   6.804 +
   6.805 +  If you want to compile the driver as a module ( = code which can be
   6.806 +  inserted in and removed from the running kernel whenever you want),
   6.807 +  say M here and read <file:Documentation/modules.txt>.  The module
   6.808 +  will be called ide-tape.o.
   6.809 +
   6.810 +Include IDE/ATAPI FLOPPY support
   6.811 +CONFIG_BLK_DEV_IDEFLOPPY
   6.812 +  If you have an IDE floppy drive which uses the ATAPI protocol,
   6.813 +  answer Y.  ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
   6.814 +  drives, similar to the SCSI protocol.
   6.815 +
   6.816 +  The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
   6.817 +  this driver. For information about jumper settings and the question
   6.818 +  of when a ZIP drive uses a partition table, see
   6.819 +  <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
   6.820 +  (ATAPI PD-CD/CDR drives are not supported by this driver; support
   6.821 +  for PD-CD/CDR drives is available if you answer Y to
   6.822 +  "SCSI emulation support", below).
   6.823 +
   6.824 +  If you say Y here, the FLOPPY drive will be identified along with
   6.825 +  other IDE devices, as "hdb" or "hdc", or something similar (check
   6.826 +  the boot messages with dmesg).
   6.827 +
   6.828 +  If you want to compile the driver as a module ( = code which can be
   6.829 +  inserted in and removed from the running kernel whenever you want),
   6.830 +  say M here and read <file:Documentation/modules.txt>.  The module
   6.831 +  will be called ide-floppy.o.
   6.832 +
   6.833 +AWARD Bios Work-Around
   6.834 +CONFIG_IDEDISK_STROKE
   6.835 +  Should you have a system w/ an AWARD Bios and your drives are larger
   6.836 +  than 32GB and it will not boot, one is required to perform a few OEM
   6.837 +  operations first.  The option is called "STROKE" because it allows
   6.838 +  one to "soft clip" the drive to work around a barrier limit.  For
   6.839 +  Maxtor drives it is called "jumpon.exe".  Please search Maxtor's
   6.840 +  web-site for "JUMPON.EXE".  IBM has a similar tool at:
   6.841 +  <http://www.storage.ibm.com/hdd/support/download.htm>.
   6.842 +
   6.843 +  If you are unsure, say N here.
   6.844 +
   6.845 +Raw Access to Media
   6.846 +CONFIG_IDE_TASK_IOCTL
   6.847 +  This is a direct raw access to the media.  It is a complex but
   6.848 +  elegant solution to test and validate the domain of the hardware and
   6.849 +  perform below the driver data recover if needed.  This is the most
   6.850 +  basic form of media-forensics.
   6.851 +
   6.852 +  If you are unsure, say N here.
   6.853 +
   6.854 +Use Taskfile I/O
   6.855 +CONFIG_IDE_TASKFILE_IO
   6.856 +  This is the "Jewel" of the patch.  It will go away and become the new
   6.857 +  driver core.  Since all the chipsets/host side hardware deal w/ their
   6.858 +  exceptions in "their local code" currently, adoption of a
   6.859 +  standardized data-transport is the only logical solution.
   6.860 +  Additionally we packetize the requests and gain rapid performance and
   6.861 +  a reduction in system latency.  Additionally by using a memory struct
   6.862 +  for the commands we can redirect to a MMIO host hardware in the next
   6.863 +  generation of controllers, specifically second generation Ultra133
   6.864 +  and Serial ATA.
   6.865 +
   6.866 +  Since this is a major transition, it was deemed necessary to make the
   6.867 +  driver paths buildable in separate models.  Therefore if using this
   6.868 +  option fails for your arch then we need to address the needs for that
   6.869 +  arch.
   6.870 +
   6.871 +  If you want to test this functionality, say Y here.
   6.872 +
   6.873 +Force DMA
   6.874 +CONFIG_BLK_DEV_IDEDMA_FORCED
   6.875 +  This is an old piece of lost code from Linux 2.0 Kernels.
   6.876 +
   6.877 +  Generally say N here.
   6.878 +
   6.879 +DMA Only on Disks
   6.880 +CONFIG_IDEDMA_ONLYDISK
   6.881 +  This is used if you know your ATAPI Devices are going to fail DMA
   6.882 +  Transfers.
   6.883 +
   6.884 +  Generally say N here.
   6.885 +
   6.886 +SCSI emulation support
   6.887 +CONFIG_BLK_DEV_IDESCSI
   6.888 +  This will provide SCSI host adapter emulation for IDE ATAPI devices,
   6.889 +  and will allow you to use a SCSI device driver instead of a native
   6.890 +  ATAPI driver.
   6.891 +
   6.892 +  This is useful if you have an ATAPI device for which no native
   6.893 +  driver has been written (for example, an ATAPI PD-CD or CDR drive);
   6.894 +  you can then use this emulation together with an appropriate SCSI
   6.895 +  device driver. In order to do this, say Y here and to "SCSI support"
   6.896 +  and "SCSI generic support", below. You must then provide the kernel
   6.897 +  command line "hdx=scsi" (try "man bootparam" or see the
   6.898 +  documentation of your boot loader (lilo or loadlin) about how to
   6.899 +  pass options to the kernel at boot time) for devices if you want the
   6.900 +  native EIDE sub-drivers to skip over the native support, so that
   6.901 +  this SCSI emulation can be used instead. This is required for use of
   6.902 +  CD-RW's.
   6.903 +
   6.904 +  Note that this option does NOT allow you to attach SCSI devices to a
   6.905 +  box that doesn't have a SCSI host adapter installed.
   6.906 +
   6.907 +  If both this SCSI emulation and native ATAPI support are compiled
   6.908 +  into the kernel, the native support will be used.
   6.909 +
   6.910 +  This driver is also available as a module ( = code which can be
   6.911 +  inserted in and removed from the running kernel whenever you want).
   6.912 +  If you want to compile it as a module, say M here and read
   6.913 +  <file:Documentation/modules.txt>. The module will be called
   6.914 +  ide-scsi.o
   6.915 +
   6.916 +Use the NOOP Elevator (WARNING)
   6.917 +CONFIG_BLK_DEV_ELEVATOR_NOOP
   6.918 +  If you are using a raid class top-level driver above the ATA/IDE core,
   6.919 +  one may find a performance boost by preventing a merging and re-sorting
   6.920 +  of the new requests.
   6.921 +
   6.922 +  If unsure, say N.
   6.923 +
   6.924 +ISA-PNP EIDE support
   6.925 +CONFIG_BLK_DEV_ISAPNP
   6.926 +  If you have an ISA EIDE card that is PnP (Plug and Play) and
   6.927 +  requires setup first before scanning for devices, say Y here.
   6.928 +
   6.929 +  If unsure, say N.
   6.930 +
   6.931 +CMD640 chipset bugfix/support
   6.932 +CONFIG_BLK_DEV_CMD640
   6.933 +  The CMD-Technologies CMD640 IDE chip is used on many common 486 and
   6.934 +  Pentium motherboards, usually in combination with a "Neptune" or
   6.935 +  "SiS" chipset. Unfortunately, it has a number of rather nasty
   6.936 +  design flaws that can cause severe data corruption under many common
   6.937 +  conditions. Say Y here to include code which tries to automatically
   6.938 +  detect and correct the problems under Linux. This option also
   6.939 +  enables access to the secondary IDE ports in some CMD640 based
   6.940 +  systems.
   6.941 +
   6.942 +  This driver will work automatically in PCI based systems (most new
   6.943 +  systems have PCI slots). But if your system uses VESA local bus
   6.944 +  (VLB) instead of PCI, you must also supply a kernel boot parameter
   6.945 +  to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
   6.946 +  bootparam" or see the documentation of your boot loader about how to
   6.947 +  pass options to the kernel.)
   6.948 +
   6.949 +  The CMD640 chip is also used on add-in cards by Acculogic, and on
   6.950 +  the "CSA-6400E PCI to IDE controller" that some people have. For
   6.951 +  details, read <file:Documentation/ide.txt>.
   6.952 +
   6.953 +CMD640 enhanced support
   6.954 +CONFIG_BLK_DEV_CMD640_ENHANCED
   6.955 +  This option includes support for setting/autotuning PIO modes and
   6.956 +  prefetch on CMD640 IDE interfaces.  For details, read
   6.957 +  <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
   6.958 +  and your BIOS does not already do this for you, then say Y here.
   6.959 +  Otherwise say N.
   6.960 +
   6.961 +RZ1000 chipset bugfix/support
   6.962 +CONFIG_BLK_DEV_RZ1000
   6.963 +  The PC-Technologies RZ1000 IDE chip is used on many common 486 and
   6.964 +  Pentium motherboards, usually along with the "Neptune" chipset.
   6.965 +  Unfortunately, it has a rather nasty design flaw that can cause
   6.966 +  severe data corruption under many conditions. Say Y here to include
   6.967 +  code which automatically detects and corrects the problem under
   6.968 +  Linux. This may slow disk throughput by a few percent, but at least
   6.969 +  things will operate 100% reliably.
   6.970 +
   6.971 +Generic PCI IDE chipset support
   6.972 +CONFIG_BLK_DEV_IDEPCI
   6.973 +  Say Y here for PCI systems which use IDE drive(s).
   6.974 +  This option helps the IDE driver to automatically detect and
   6.975 +  configure all PCI-based IDE interfaces in your system.
   6.976 +
   6.977 +Support for sharing PCI IDE interrupts
   6.978 +CONFIG_IDEPCI_SHARE_IRQ
   6.979 +  Some ATA/IDE chipsets have hardware support which allows for
   6.980 +  sharing a single IRQ with other cards. To enable support for
   6.981 +  this in the ATA/IDE driver, say Y here.
   6.982 +
   6.983 +  It is safe to say Y to this question, in most cases.
   6.984 +  If unsure, say N.
   6.985 +
   6.986 +Generic PCI bus-master DMA support
   6.987 +CONFIG_BLK_DEV_IDEDMA_PCI
   6.988 +  If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
   6.989 +  is capable of bus-master DMA operation (most Pentium PCI systems),
   6.990 +  you will want to say Y here to reduce CPU overhead. You can then use
   6.991 +  the "hdparm" utility to enable DMA for drives for which it was not
   6.992 +  enabled automatically. By default, DMA is not enabled automatically
   6.993 +  for these drives, but you can change that by saying Y to the
   6.994 +  following question "Use DMA by default when available". You can get
   6.995 +  the latest version of the hdparm utility from
   6.996 +  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   6.997 +
   6.998 +  Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
   6.999 +  and the file <file:Documentation/ide.txt> for more information.
  6.1000 +
  6.1001 +  It is safe to say Y to this question.
  6.1002 +
  6.1003 +Good-Bad DMA Model-Firmware (WIP)
  6.1004 +CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
  6.1005 +  If you say Y here, the model and firmware revision of your drive
  6.1006 +  will be compared against a blacklist of buggy drives that claim to
  6.1007 +  be (U)DMA capable but aren't. This is a blanket on/off test with no
  6.1008 +  speed limit options.
  6.1009 +
  6.1010 +  Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
  6.1011 +  whereas, many versions of EGCS have a problem and miscompile if you
  6.1012 +  say Y here.
  6.1013 +
  6.1014 +  If in doubt, say N.
  6.1015 +
  6.1016 +Attempt to HACK around Chipsets that TIMEOUT (WIP)
  6.1017 +CONFIG_BLK_DEV_IDEDMA_TIMEOUT
  6.1018 +  If you say Y here, this is a NASTY UGLY HACK!
  6.1019 +
  6.1020 +  We have to issue an abort and requeue the request DMA engine got
  6.1021 +  turned off by a goofy ASIC, and we have to clean up the mess, and
  6.1022 +  here is as good as any.  Do it globally for all chipsets.
  6.1023 +
  6.1024 +  If in doubt, say N.
  6.1025 +
  6.1026 +Boot off-board chipsets first support
  6.1027 +CONFIG_BLK_DEV_OFFBOARD
  6.1028 +  Normally, IDE controllers built into the motherboard (on-board
  6.1029 +  controllers) are assigned to ide0 and ide1 while those on add-in PCI
  6.1030 +  cards (off-board controllers) are relegated to ide2 and ide3.
  6.1031 +  Answering Y here will allow you to reverse the situation, with
  6.1032 +  off-board controllers on ide0/1 and on-board controllers on ide2/3.
  6.1033 +  This can improve the usability of some boot managers such as lilo
  6.1034 +  when booting from a drive on an off-board controller.
  6.1035 +
  6.1036 +  If you say Y here, and you actually want to reverse the device scan
  6.1037 +  order as explained above, you also need to issue the kernel command
  6.1038 +  line option "ide=reverse". (Try "man bootparam" or see the
  6.1039 +  documentation of your boot loader (lilo or loadlin) about how to
  6.1040 +  pass options to the kernel at boot time.)
  6.1041 +
  6.1042 +  Note that, if you do this, the order of the hd* devices will be
  6.1043 +  rearranged which may require modification of fstab and other files.
  6.1044 +
  6.1045 +  If in doubt, say N.
  6.1046 +
  6.1047 +Use PCI DMA by default when available
  6.1048 +CONFIG_IDEDMA_PCI_AUTO
  6.1049 +  Prior to kernel version 2.1.112, Linux used to automatically use
  6.1050 +  DMA for IDE drives and chipsets which support it. Due to concerns
  6.1051 +  about a couple of cases where buggy hardware may have caused damage,
  6.1052 +  the default is now to NOT use DMA automatically. To revert to the
  6.1053 +  previous behaviour, say Y to this question.
  6.1054 +
  6.1055 +  If you suspect your hardware is at all flakey, say N here.
  6.1056 +  Do NOT email the IDE kernel people regarding this issue!
  6.1057 +
  6.1058 +  It is normally safe to answer Y to this question unless your
  6.1059 +  motherboard uses a VIA VP2 chipset, in which case you should say N.
  6.1060 +
  6.1061 +IGNORE word93 Validation BITS
  6.1062 +CONFIG_IDEDMA_IVB
  6.1063 +  There are unclear terms in ATA-4 and ATA-5 standards how certain
  6.1064 +  hardware (an 80c ribbon) should be detected. Different interpretations
  6.1065 +  of the standards have been released in hardware. This causes problems:
  6.1066 +  for example, a host with Ultra Mode 4 (or higher) will not run
  6.1067 +  in that mode with an 80c ribbon.
  6.1068 +
  6.1069 +  If you are experiencing compatibility or performance problems, you
  6.1070 +  MAY try to answering Y here. However, it does not necessarily solve
  6.1071 +  any of your problems, it could even cause more of them.
  6.1072 +
  6.1073 +  It is normally safe to answer Y; however, the default is N.
  6.1074 +
  6.1075 +ATA Work(s) In Progress (EXPERIMENTAL)
  6.1076 +CONFIG_IDEDMA_PCI_WIP
  6.1077 +  If you enable this you will be able to use and test highly
  6.1078 +  developmental projects. If you say N, the configurator will
  6.1079 +  simply skip those options.
  6.1080 +
  6.1081 +  It is SAFEST to say N to this question.
  6.1082 +
  6.1083 +Asynchronous DMA support (EXPERIMENTAL)
  6.1084 +CONFIG_BLK_DEV_ADMA
  6.1085 +  Please read the comments at the top of
  6.1086 +  <file:drivers/ide/ide-adma.c>.
  6.1087 +
  6.1088 +Pacific Digital A-DMA support (EXPERIMENTAL)
  6.1089 +CONFIG_BLK_DEV_PDC_ADMA
  6.1090 +  Please read the comments at the top of <file:drivers/ide/setup-pci.c>.
  6.1091 +
  6.1092 +3ware Hardware ATA-RAID support
  6.1093 +CONFIG_BLK_DEV_3W_XXXX_RAID
  6.1094 +  3ware is the only hardware ATA-Raid product in Linux to date.
  6.1095 +  This card is 2,4, or 8 channel master mode support only.
  6.1096 +  SCSI support required!!!
  6.1097 +
  6.1098 +  <http://www.3ware.com/>
  6.1099 +
  6.1100 +  Please read the comments at the top of
  6.1101 +  <file:drivers/scsi/3w-xxxx.c>.
  6.1102 +
  6.1103 +  If you want to compile the driver as a module ( = code which can be
  6.1104 +  inserted in and removed from the running kernel whenever you want),
  6.1105 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.1106 +  will be called 3w-xxxx.o.
  6.1107 +
  6.1108 +AEC62XX chipset support
  6.1109 +CONFIG_BLK_DEV_AEC62XX
  6.1110 +  This driver adds up to 4 more EIDE devices sharing a single
  6.1111 +  interrupt. This add-on card is a bootable PCI UDMA controller. In
  6.1112 +  order to get this card to initialize correctly in some cases, you
  6.1113 +  should say Y here, and preferably also to "Use DMA by default when
  6.1114 +  available".
  6.1115 +
  6.1116 +  The ATP850U/UF is an UltraDMA 33 chipset base.
  6.1117 +  The ATP860 is an UltraDMA 66 chipset base.
  6.1118 +  The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
  6.1119 +
  6.1120 +  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  6.1121 +  If you say Y here, then say Y to "Use DMA by default when available"
  6.1122 +  as well.
  6.1123 +
  6.1124 +AEC62XX Tuning support
  6.1125 +CONFIG_AEC62XX_TUNING
  6.1126 +  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  6.1127 +  If unsure, say N.
  6.1128 +
  6.1129 +ALI M15x3 chipset support
  6.1130 +CONFIG_BLK_DEV_ALI15X3
  6.1131 +  This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
  6.1132 +  onboard chipsets.  It also tests for Simplex mode and enables
  6.1133 +  normal dual channel support.
  6.1134 +
  6.1135 +  If you say Y here, you also need to say Y to "Use DMA by default
  6.1136 +  when available", above.  Please read the comments at the top of
  6.1137 +  <file:drivers/ide/pci/alim15x3.c>.
  6.1138 +
  6.1139 +  If unsure, say N.
  6.1140 +
  6.1141 +ALI M15x3 WDC support (DANGEROUS)
  6.1142 +CONFIG_WDC_ALI15X3
  6.1143 +  This allows for UltraDMA support for WDC drives that ignore CRC
  6.1144 +  checking. You are a fool for enabling this option, but there have
  6.1145 +  been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
  6.1146 +  YOU ENABLE THIS! No one will listen, just laugh for ignoring this
  6.1147 +  SERIOUS WARNING.
  6.1148 +
  6.1149 +  Using this option can allow WDC drives to run at ATA-4/5 transfer
  6.1150 +  rates with only an ATA-2 support structure.
  6.1151 +
  6.1152 +  SAY N!
  6.1153 +
  6.1154 +AMD and nVidia IDE support
  6.1155 +CONFIG_BLK_DEV_AMD74XX
  6.1156 +  This driver adds explicit support for AMD-7xx and AMD-8111 chips
  6.1157 +  and also for the nVidia nForce chip.  This allows the kernel to
  6.1158 +  change PIO, DMA and UDMA speeds and to configure the chip to
  6.1159 +  optimum performance.
  6.1160 +
  6.1161 +  If you say Y here, you also need to say Y to "Use DMA by default
  6.1162 +  when available", above.
  6.1163 +  Please read the comments at the top of <file:drivers/ide/pci/amd74xx.c>.
  6.1164 +
  6.1165 +  If unsure, say N.
  6.1166 +
  6.1167 +AMD Viper ATA-66 Override support (WIP)
  6.1168 +CONFIG_AMD74XX_OVERRIDE
  6.1169 +  This option auto-forces the ata66 flag.
  6.1170 +  This effect can be also invoked by calling "idex=ata66"
  6.1171 +  If unsure, say N.
  6.1172 +
  6.1173 +ATI IXP chipset IDE support
  6.1174 +CONFIG_BLK_DEV_ATIIXP
  6.1175 +  This driver adds explicit support for ATI IXP chipset.
  6.1176 +  This allows the kernel to change PIO, DMA and UDMA speeds
  6.1177 +  and to configure the chip to optimum performance.
  6.1178 +
  6.1179 +  Say Y here if you have an ATI IXP chipset IDE controller.
  6.1180 +
  6.1181 +CMD64X/CMD680 chipset support
  6.1182 +CONFIG_BLK_DEV_CMD64X
  6.1183 +  Say Y here if you have an IDE controller which uses any of these
  6.1184 +  chipsets: CMD643, CMD646 and CMD648.
  6.1185 +
  6.1186 +Compaq Triflex IDE support
  6.1187 +CONFIG_BLK_DEV_TRIFLEX
  6.1188 +  Say Y here if you have a Compaq Triflex IDE controller, such
  6.1189 +  as those commonly found on Compaq Pentium-Pro systems
  6.1190 +
  6.1191 +  If you want to compile it as a module, say M here and read
  6.1192 +  <file:Documentation/modules.txt>.  The module will be called
  6.1193 +  triflex.o.
  6.1194 +
  6.1195 +CY82C693 chipset support
  6.1196 +CONFIG_BLK_DEV_CY82C693
  6.1197 +  This driver adds detection and support for the CY82C693 chipset
  6.1198 +  used on Digital's PC-Alpha 164SX boards.
  6.1199 +
  6.1200 +  If you say Y here, you need to say Y to "Use DMA by default
  6.1201 +  when available" as well.
  6.1202 +
  6.1203 +Cyrix CS5530 MediaGX chipset support
  6.1204 +CONFIG_BLK_DEV_CS5530
  6.1205 +  Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
  6.1206 +  will automatically be detected and configured if found.
  6.1207 +
  6.1208 +  It is safe to say Y to this question.
  6.1209 +
  6.1210 +  People with SCSI-only systems should say N here. If unsure, say Y.
  6.1211 +
  6.1212 +HPT34X chipset support
  6.1213 +CONFIG_BLK_DEV_HPT34X
  6.1214 +  This driver adds up to 4 more EIDE devices sharing a single
  6.1215 +  interrupt. The HPT343 chipset in its current form is a non-bootable
  6.1216 +  controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
  6.1217 +  PCI UDMA controllers. This driver requires dynamic tuning of the
  6.1218 +  chipset during the ide-probe at boot time. It is reported to support
  6.1219 +  DVD II drives, by the manufacturer.
  6.1220 +
  6.1221 +HPT34X AUTODMA support (WIP)
  6.1222 +CONFIG_HPT34X_AUTODMA
  6.1223 +  This is a dangerous thing to attempt currently! Please read the
  6.1224 +  comments at the top of <file:drivers/ide/pci/hpt34x.c>.  If you say Y
  6.1225 +  here, then say Y to "Use DMA by default when available" as well.
  6.1226 +
  6.1227 +  If unsure, say N.
  6.1228 +
  6.1229 +HPT36X/37X chipset support
  6.1230 +CONFIG_BLK_DEV_HPT366
  6.1231 +  HPT366 is an Ultra DMA chipset for ATA-66.
  6.1232 +  HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
  6.1233 +  HPT370 is an Ultra DMA chipset for ATA-100.
  6.1234 +  HPT372 is an Ultra DMA chipset for ATA-133.
  6.1235 +  HPT374 is an Ultra DMA chipset for ATA-133.
  6.1236 +
  6.1237 +  This driver adds up to 4 more EIDE devices sharing a single
  6.1238 +  interrupt.
  6.1239 +
  6.1240 +  The HPT366 chipset in its current form is bootable. One solution
  6.1241 +  for this problem are special LILO commands for redirecting the
  6.1242 +  reference to device 0x80. The other solution is to say Y to "Boot
  6.1243 +  off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
  6.1244 +  your mother board has the chipset natively mounted. Regardless one
  6.1245 +  should use the fore mentioned option and call at LILO or include
  6.1246 +  "ide=reverse" in LILO's append-line.
  6.1247 +
  6.1248 +  This driver requires dynamic tuning of the chipset during the
  6.1249 +  ide-probe at boot. It is reported to support DVD II drives, by the
  6.1250 +  manufacturer.
  6.1251 +
  6.1252 +NS87415 chipset support (EXPERIMENTAL)
  6.1253 +CONFIG_BLK_DEV_NS87415
  6.1254 +  This driver adds detection and support for the NS87415 chip
  6.1255 +  (used in SPARC64, among others).
  6.1256 +
  6.1257 +  Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
  6.1258 +
  6.1259 +OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
  6.1260 +CONFIG_BLK_DEV_OPTI621
  6.1261 +  This is a driver for the OPTi 82C621 EIDE controller.
  6.1262 +  Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
  6.1263 +
  6.1264 +National SCx200 chipset support
  6.1265 +CONFIG_BLK_DEV_SC1200
  6.1266 +  This driver adds support for the built in IDE on the National
  6.1267 +  SCx200 series of embedded x86 "Geode" systems
  6.1268 +
  6.1269 +  If you want to compile it as a module, say M here and read
  6.1270 +  <file:Documentation/modules.txt>.  The module will be called
  6.1271 +  sc1200.o.
  6.1272 +
  6.1273 +ServerWorks OSB4/CSB5 chipset support
  6.1274 +CONFIG_BLK_DEV_SVWKS
  6.1275 +  This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
  6.1276 +  chipsets.
  6.1277 +
  6.1278 +SGI IOC4 chipset support
  6.1279 +CONFIG_BLK_DEV_SGIIOC4
  6.1280 +  This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
  6.1281 +  chipset.  Please say Y here, if you have an Altix System from
  6.1282 +  Silicon Graphics Inc.
  6.1283 +
  6.1284 +Intel PIIXn chipsets support
  6.1285 +CONFIG_BLK_DEV_PIIX
  6.1286 +  This driver adds PIO mode setting and tuning for all PIIX IDE
  6.1287 +  controllers by Intel.  Since the BIOS can sometimes improperly tune
  6.1288 +  PIO 0-4 mode settings, this allows dynamic tuning of the chipset
  6.1289 +  via the standard end-user tool 'hdparm'.
  6.1290 +
  6.1291 +  Please read the comments at the top of <file:drivers/ide/pci/piix.c>.
  6.1292 +
  6.1293 +  If you say Y here, you should also say Y to "PIIXn Tuning support",
  6.1294 +  below.
  6.1295 +
  6.1296 +  If unsure, say N.
  6.1297 +
  6.1298 +PIIXn Tuning support
  6.1299 +CONFIG_PIIX_TUNING
  6.1300 +  This driver extension adds DMA mode setting and tuning for all PIIX
  6.1301 +  IDE controllers by Intel. Since the BIOS can sometimes improperly
  6.1302 +  set up the device/adapter combination and speed limits, it has
  6.1303 +  become a necessity to back/forward speed devices as needed.
  6.1304 +
  6.1305 +  Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
  6.1306 +  2 if the BIOS can not perform this task at initialization.
  6.1307 +
  6.1308 +  If unsure, say N.
  6.1309 +
  6.1310 +PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
  6.1311 +CONFIG_BLK_DEV_PDC202XX_OLD
  6.1312 +  Promise Ultra33 or PDC20246
  6.1313 +  Promise Ultra66 or PDC20262
  6.1314 +  Promise Ultra100 or PDC20265/PDC20267/PDC20268
  6.1315 +
  6.1316 +  This driver adds up to 4 more EIDE devices sharing a single
  6.1317 +  interrupt. This add-on card is a bootable PCI UDMA controller. Since
  6.1318 +  multiple cards can be installed and there are BIOS ROM problems that
  6.1319 +  happen if the BIOS revisions of all installed cards (three-max) do
  6.1320 +  not match, the driver attempts to do dynamic tuning of the chipset
  6.1321 +  at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
  6.1322 +  for more than one card. This card may require that you say Y to
  6.1323 +  "Special UDMA Feature".
  6.1324 +
  6.1325 +  If you say Y here, you need to say Y to "Use DMA by default when
  6.1326 +  available" as well.
  6.1327 +
  6.1328 +  Please read the comments at the top of
  6.1329 +  <file:drivers/ide/pci/pdc202xx_old.c>.
  6.1330 +
  6.1331 +  If unsure, say N.
  6.1332 +
  6.1333 +PROMISE PDC202{68|69|70|71|75|76|77} support
  6.1334 +CONFIG_BLK_DEV_PDC202XX_NEW
  6.1335 +  Promise Ultra 100 TX2 [PDC20268]
  6.1336 +  Promise Ultra 133 PTX2 [PDC20269]
  6.1337 +  Promise FastTrak LP/TX2/TX4 [PDC20270]
  6.1338 +  Promise FastTrak TX2000 [PDC20271]
  6.1339 +  Promise MB Ultra 133 [PDC20275]
  6.1340 +  Promise MB FastTrak 133 [PDC20276]
  6.1341 +  Promise FastTrak 133 [PDC20277]
  6.1342 +
  6.1343 +  This driver adds up to 4 more EIDE devices sharing a single
  6.1344 +  interrupt. This device is a bootable PCI UDMA controller. Since
  6.1345 +  multiple cards can be installed and there are BIOS ROM problems that
  6.1346 +  happen if the BIOS revisions of all installed cards (max of five) do
  6.1347 +  not match, the driver attempts to do dynamic tuning of the chipset
  6.1348 +  at boot-time for max speed.  Ultra33 BIOS 1.25 or newer is required
  6.1349 +  for more than one card.
  6.1350 +
  6.1351 +  If you say Y here, you need to say Y to "Use DMA by default when
  6.1352 +  available" as well.
  6.1353 +
  6.1354 +  If unsure, say N.
  6.1355 +
  6.1356 +Special UDMA Feature
  6.1357 +CONFIG_PDC202XX_BURST
  6.1358 +  This option causes the pdc202xx driver to enable UDMA modes on the
  6.1359 +  PDC202xx even when the PDC202xx BIOS has not done so.
  6.1360 +
  6.1361 +  It was originally designed for the PDC20246/Ultra33, whose BIOS will
  6.1362 +  only setup UDMA on the first two PDC20246 cards.  It has also been
  6.1363 +  used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
  6.1364 +  when the PDC20265 BIOS has been disabled (for faster boot up).
  6.1365 +
  6.1366 +  Please read the comments at the top of
  6.1367 +  <file:drivers/ide/pci/pdc202xx_old.c>.
  6.1368 +
  6.1369 +  If unsure, say N.
  6.1370 +
  6.1371 +Special FastTrak Feature
  6.1372 +CONFIG_PDC202XX_FORCE
  6.1373 +  For FastTrak enable overriding BIOS.
  6.1374 +
  6.1375 +SiS5513 chipset support
  6.1376 +CONFIG_BLK_DEV_SIS5513
  6.1377 +  This driver ensures (U)DMA support for SIS5513 chipset family based
  6.1378 +  mainboards.
  6.1379 +
  6.1380 +  The following chipsets are supported:
  6.1381 +  ATA16:  SiS5511, SiS5513
  6.1382 +  ATA33:  SiS5591, SiS5597, SiS5598, SiS5600
  6.1383 +  ATA66:  SiS530, SiS540, SiS620, SiS630, SiS640
  6.1384 +  ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
  6.1385 +          SiS745, SiS750
  6.1386 +
  6.1387 +  If you say Y here, you need to say Y to "Use DMA by default when
  6.1388 +  available" as well.
  6.1389 +
  6.1390 +  Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
  6.1391 +
  6.1392 +Silicon Image chipset support
  6.1393 +CONFIG_BLK_DEV_SIIMAGE
  6.1394 +  This driver provides (U)DMA support for the SII3112 SATA controllers and
  6.1395 +  for the CMD/SI680 UDMA/DMA ATA controller.
  6.1396 +
  6.1397 +SLC90E66 chipset support
  6.1398 +CONFIG_BLK_DEV_SLC90E66
  6.1399 +  This driver ensures (U)DMA support for Victroy66 SouthBridges for
  6.1400 +  SMsC with Intel NorthBridges.  This is an Ultra66 based chipset.
  6.1401 +  The nice thing about it is that you can mix Ultra/DMA/PIO devices
  6.1402 +  and it will handle timing cycles.  Since this is an improved
  6.1403 +  look-a-like to the PIIX4 it should be a nice addition.
  6.1404 +
  6.1405 +  If you say Y here, you need to say Y to "Use DMA by default when
  6.1406 +  available" as well.
  6.1407 +
  6.1408 +  Please read the comments at the top of
  6.1409 +  <file:drivers/ide/pci/slc90e66.c>.
  6.1410 +
  6.1411 +Winbond SL82c105 support
  6.1412 +CONFIG_BLK_DEV_SL82C105
  6.1413 +  If you have a Winbond SL82c105 IDE controller, say Y here to enable
  6.1414 +  special configuration for this chip. This is common on various CHRP
  6.1415 +  motherboards, but could be used elsewhere. If in doubt, say Y.
  6.1416 +
  6.1417 +Tekram TRM290 chipset support
  6.1418 +CONFIG_BLK_DEV_TRM290
  6.1419 +  This driver adds support for bus master DMA transfers
  6.1420 +  using the Tekram TRM290 PCI IDE chip. Volunteers are
  6.1421 +  needed for further tweaking and development.
  6.1422 +  Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
  6.1423 +
  6.1424 +VIA82CXXX chipset support
  6.1425 +CONFIG_BLK_DEV_VIA82CXXX
  6.1426 +  This allows you to configure your chipset for a better use while
  6.1427 +  running PIO/(U)DMA, it will allow you to enable efficiently the
  6.1428 +  second channel dma usage, as it may not be set by BIOS.  It will try
  6.1429 +  to set fifo configuration at its best.  It will allow you to get
  6.1430 +  information from /proc/ide/via provided you enabled "/proc file
  6.1431 +  system" support.
  6.1432 +
  6.1433 +  Please read the comments at the top of
  6.1434 +  <file:drivers/ide/pci/via82cxxx.c>.
  6.1435 +
  6.1436 +  If you say Y here, then say Y to "Use DMA by default when available"
  6.1437 +  as well.
  6.1438 +
  6.1439 +  If unsure, say N.
  6.1440 +
  6.1441 +RapIDE interface support
  6.1442 +CONFIG_BLK_DEV_IDE_RAPIDE
  6.1443 +  Say Y here if you want to support the Yellowstone RapIDE controller
  6.1444 +  manufactured for use with Acorn computers.
  6.1445 +
  6.1446 +Other IDE chipset support
  6.1447 +CONFIG_IDE_CHIPSETS
  6.1448 +  Say Y here if you want to include enhanced support for various IDE
  6.1449 +  interface chipsets used on motherboards and add-on cards. You can
  6.1450 +  then pick your particular IDE chip from among the following options.
  6.1451 +  This enhanced support may be necessary for Linux to be able to
  6.1452 +  access the 3rd/4th drives in some systems. It may also enable
  6.1453 +  setting of higher speed I/O rates to improve system performance with
  6.1454 +  these chipsets. Most of these also require special kernel boot
  6.1455 +  parameters to actually turn on the support at runtime; you can find
  6.1456 +  a list of these in the file <file:Documentation/ide.txt>.
  6.1457 +
  6.1458 +  People with SCSI-only systems can say N here.
  6.1459 +
  6.1460 +Generic 4 drives/port support
  6.1461 +CONFIG_BLK_DEV_4DRIVES
  6.1462 +  Certain older chipsets, including the Tekram 690CD, use a single set
  6.1463 +  of I/O ports at 0x1f0 to control up to four drives, instead of the
  6.1464 +  customary two drives per port. Support for this can be enabled at
  6.1465 +  runtime using the "ide0=four" kernel boot parameter if you say Y
  6.1466 +  here.
  6.1467 +
  6.1468 +ALI M14xx support
  6.1469 +CONFIG_BLK_DEV_ALI14XX
  6.1470 +  This driver is enabled at runtime using the "ide0=ali14xx" kernel
  6.1471 +  boot parameter.  It enables support for the secondary IDE interface
  6.1472 +  of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
  6.1473 +  I/O speeds to be set as well.  See the files
  6.1474 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
  6.1475 +  more info.
  6.1476 +
  6.1477 +DTC-2278 support
  6.1478 +CONFIG_BLK_DEV_DTC2278
  6.1479 +  This driver is enabled at runtime using the "ide0=dtc2278" kernel
  6.1480 +  boot parameter. It enables support for the secondary IDE interface
  6.1481 +  of the DTC-2278 card, and permits faster I/O speeds to be set as
  6.1482 +  well. See the <file:Documentation/ide.txt> and
  6.1483 +  <file:drivers/ide/legacy/dtc2278.c> files for more info.
  6.1484 +
  6.1485 +Holtek HT6560B support
  6.1486 +CONFIG_BLK_DEV_HT6560B
  6.1487 +  This driver is enabled at runtime using the "ide0=ht6560b" kernel
  6.1488 +  boot parameter. It enables support for the secondary IDE interface
  6.1489 +  of the Holtek card, and permits faster I/O speeds to be set as well.
  6.1490 +  See the <file:Documentation/ide.txt> and
  6.1491 +  <file:drivers/ide/legacy/ht6560b.c> files for more info.
  6.1492 +
  6.1493 +PROMISE DC4030 support (EXPERIMENTAL)
  6.1494 +CONFIG_BLK_DEV_PDC4030
  6.1495 +  This driver provides support for the secondary IDE interface and
  6.1496 +  cache of Promise IDE chipsets, e.g. DC4030 and DC5030.  This driver
  6.1497 +  is known to incur timeouts/retries during heavy I/O to drives
  6.1498 +  attached to the secondary interface.  CD-ROM and TAPE devices are
  6.1499 +  not supported yet.  This driver is enabled at runtime using the
  6.1500 +  "ide0=dc4030" kernel boot parameter.  See the
  6.1501 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/pdc4030.c> files
  6.1502 +  for more info.
  6.1503 +
  6.1504 +QDI QD65XX support
  6.1505 +CONFIG_BLK_DEV_QD65XX
  6.1506 +  This driver is enabled at runtime using the "ide0=qd65xx" kernel
  6.1507 +  boot parameter.  It permits faster I/O speeds to be set.  See the
  6.1508 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
  6.1509 +  more info.
  6.1510 +
  6.1511 +UMC 8672 support
  6.1512 +CONFIG_BLK_DEV_UMC8672
  6.1513 +  This driver is enabled at runtime using the "ide0=umc8672" kernel
  6.1514 +  boot parameter. It enables support for the secondary IDE interface
  6.1515 +  of the UMC-8672, and permits faster I/O speeds to be set as well.
  6.1516 +  See the files <file:Documentation/ide.txt> and
  6.1517 +  <file:drivers/ide/legacy/umc8672.c> for more info.
  6.1518 +
  6.1519 +Amiga Gayle IDE interface support
  6.1520 +CONFIG_BLK_DEV_GAYLE
  6.1521 +  This is the IDE driver for the Amiga Gayle IDE interface. It supports
  6.1522 +  both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
  6.1523 +  This includes builtin IDE interfaces on some Amiga models (A600,
  6.1524 +  A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
  6.1525 +  bus (M-Tech E-Matrix 530 expansion card).
  6.1526 +  Say Y if you have an Amiga with a Gayle IDE interface and want to use
  6.1527 +  IDE devices (hard disks, CD-ROM drives, etc.) that are connected to it.
  6.1528 +  Note that you also have to enable Zorro bus support if you want to
  6.1529 +  use Gayle IDE interfaces on the Zorro expansion bus.
  6.1530 +
  6.1531 +Falcon IDE interface support
  6.1532 +CONFIG_BLK_DEV_FALCON_IDE
  6.1533 +  This is the IDE driver for the builtin IDE interface on the Atari
  6.1534 +  Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
  6.1535 +  disks, CD-ROM drives, etc.) that are connected to the builtin IDE
  6.1536 +  interface.
  6.1537 +
  6.1538 +Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
  6.1539 +CONFIG_BLK_DEV_BUDDHA
  6.1540 +  This is the IDE driver for the IDE interfaces on the Buddha, 
  6.1541 +  Catweasel and X-Surf expansion boards.  It supports up to two interfaces 
  6.1542 +  on the Buddha, three on the Catweasel and two on the X-Surf.
  6.1543 +
  6.1544 +  Say Y if you have a Buddha or Catweasel expansion board and want to
  6.1545 +  use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
  6.1546 +  to one of its IDE interfaces.
  6.1547 +
  6.1548 +Amiga IDE Doubler support (EXPERIMENTAL)
  6.1549 +CONFIG_BLK_DEV_IDEDOUBLER
  6.1550 +  This driver provides support for the so-called `IDE doublers' (made
  6.1551 +  by various manufacturers, e.g. Eyetech) that can be connected to the
  6.1552 +  builtin IDE interface of some Amiga models. Using such an IDE
  6.1553 +  doubler, you can connect up to four instead of two IDE devices on
  6.1554 +  the Amiga's builtin IDE interface.
  6.1555 +
  6.1556 +  Note that the normal Amiga Gayle IDE driver may not work correctly
  6.1557 +  if you have an IDE doubler and don't enable this driver!
  6.1558 +
  6.1559 +  Say Y if you have an IDE doubler.  The driver is enabled at kernel
  6.1560 +  runtime using the "ide=doubler" kernel boot parameter.
  6.1561 +
  6.1562 +Builtin PowerMac IDE support
  6.1563 +CONFIG_BLK_DEV_IDE_PMAC
  6.1564 +  This driver provides support for the built-in IDE controller on
  6.1565 +  most of the recent Apple Power Macintoshes and PowerBooks.
  6.1566 +  If unsure, say Y.
  6.1567 +
  6.1568 +PowerMac IDE DMA support
  6.1569 +CONFIG_BLK_DEV_IDEDMA_PMAC
  6.1570 +  This option allows the driver for the built-in IDE controller on
  6.1571 +  Power Macintoshes and PowerBooks to use DMA (direct memory access)
  6.1572 +  to transfer data to and from memory.  Saying Y is safe and improves
  6.1573 +  performance.
  6.1574 +
  6.1575 +Broadcom SiByte onboard IDE support
  6.1576 +CONFIG_BLK_DEV_IDE_SIBYTE
  6.1577 +  Include the driver for on-board IDE on the SiByte Generic Bus.  Note
  6.1578 +  that this limits the number of IDE devices to 4 (ide0...ide3).
  6.1579 +
  6.1580 +Use DMA by default
  6.1581 +CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
  6.1582 +  This option allows the driver for the built-in IDE controller on
  6.1583 +  Power Macintoshes and PowerBooks to use DMA automatically, without
  6.1584 +  it having to be explicitly enabled.  This option is provided because
  6.1585 +  of concerns about a couple of cases where using DMA on buggy PC
  6.1586 +  hardware may have caused damage.  Saying Y should be safe on all
  6.1587 +  Apple machines.
  6.1588 +
  6.1589 +Macintosh Quadra/Powerbook IDE interface support
  6.1590 +CONFIG_BLK_DEV_MAC_IDE
  6.1591 +  This is the IDE driver for the builtin IDE interface on some m68k
  6.1592 +  Macintosh models. It supports both the `Quadra style' (used in
  6.1593 +  Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
  6.1594 +  (used in the Powerbook 150 and 190 models) IDE interface.
  6.1595 +
  6.1596 +  Say Y if you have such an Macintosh model and want to use IDE
  6.1597 +  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  6.1598 +  builtin IDE interface.
  6.1599 +
  6.1600 +ICS IDE interface support
  6.1601 +CONFIG_BLK_DEV_IDE_ICSIDE
  6.1602 +  On Acorn systems, say Y here if you wish to use the ICS IDE
  6.1603 +  interface card.  This is not required for ICS partition support.
  6.1604 +  If you are unsure, say N to this.
  6.1605 +
  6.1606 +ICS DMA support
  6.1607 +CONFIG_BLK_DEV_IDEDMA_ICS
  6.1608 +  Say Y here if you want to add DMA (Direct Memory Access) support to
  6.1609 +  the ICS IDE driver.
  6.1610 +
  6.1611 +Use ICS DMA by default
  6.1612 +CONFIG_IDEDMA_ICS_AUTO
  6.1613 +  Prior to kernel version 2.1.112, Linux used to automatically use
  6.1614 +  DMA for IDE drives and chipsets which support it. Due to concerns
  6.1615 +  about a couple of cases where buggy hardware may have caused damage,
  6.1616 +  the default is now to NOT use DMA automatically. To revert to the
  6.1617 +  previous behaviour, say Y to this question.
  6.1618 +
  6.1619 +  If you suspect your hardware is at all flakey, say N here.
  6.1620 +  Do NOT email the IDE kernel people regarding this issue!
  6.1621 +
  6.1622 +XT hard disk support
  6.1623 +CONFIG_BLK_DEV_XD
  6.1624 +  Very old 8 bit hard disk controllers used in the IBM XT computer
  6.1625 +  will be supported if you say Y here.
  6.1626 +
  6.1627 +  If you want to compile the driver as a module ( = code which can be
  6.1628 +  inserted in and removed from the running kernel whenever you want),
  6.1629 +  say M here and read <file:Documentation/modules.txt>. The module
  6.1630 +  will be called xd.o.
  6.1631 +
  6.1632 +  It's pretty unlikely that you have one of these: say N.
  6.1633 +
  6.1634 +PS/2 ESDI hard disk support
  6.1635 +CONFIG_BLK_DEV_PS2
  6.1636 +  Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  6.1637 +  hard disk.
  6.1638 +
  6.1639 +  If you want to compile the driver as a module ( = code which can be
  6.1640 +  inserted in and removed from the running kernel whenever you want),
  6.1641 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.1642 +  will be called ps2esdi.o.
  6.1643 +
  6.1644 +Mylex DAC960/DAC1100 PCI RAID Controller support
  6.1645 +CONFIG_BLK_DEV_DAC960
  6.1646 +  This driver adds support for the Mylex DAC960, AcceleRAID, and
  6.1647 +  eXtremeRAID PCI RAID controllers.  See the file
  6.1648 +  <file:Documentation/README.DAC960> for further information about
  6.1649 +  this driver.
  6.1650 +
  6.1651 +  If you want to compile the driver as a module ( = code which can be
  6.1652 +  inserted in and removed from the running kernel whenever you want),
  6.1653 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.1654 +  will be called DAC960.o.
  6.1655 +
  6.1656 +Parallel port IDE device support
  6.1657 +CONFIG_PARIDE
  6.1658 +  There are many external CD-ROM and disk devices that connect through
  6.1659 +  your computer's parallel port. Most of them are actually IDE devices
  6.1660 +  using a parallel port IDE adapter. This option enables the PARIDE
  6.1661 +  subsystem which contains drivers for many of these external drives.
  6.1662 +  Read <file:Documentation/paride.txt> for more information.
  6.1663 +
  6.1664 +  If you have said Y to the "Parallel-port support" configuration
  6.1665 +  option, you may share a single port between your printer and other
  6.1666 +  parallel port devices. Answer Y to build PARIDE support into your
  6.1667 +  kernel, or M if you would like to build it as a loadable module. If
  6.1668 +  your parallel port support is in a loadable module, you must build
  6.1669 +  PARIDE as a module. If you built PARIDE support into your kernel,
  6.1670 +  you may still build the individual protocol modules and high-level
  6.1671 +  drivers as loadable modules. If you build this support as a module,
  6.1672 +  it will be called paride.o.
  6.1673 +
  6.1674 +  To use the PARIDE support, you must say Y or M here and also to at
  6.1675 +  least one high-level driver (e.g. "Parallel port IDE disks",
  6.1676 +  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  6.1677 +  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  6.1678 +  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  6.1679 +  etc.).
  6.1680 +
  6.1681 +Parallel port IDE disks
  6.1682 +CONFIG_PARIDE_PD
  6.1683 +  This option enables the high-level driver for IDE-type disk devices
  6.1684 +  connected through a parallel port. If you chose to build PARIDE
  6.1685 +  support into your kernel, you may answer Y here to build in the
  6.1686 +  parallel port IDE driver, otherwise you should answer M to build
  6.1687 +  it as a loadable module. The module will be called pd.o. You
  6.1688 +  must also have at least one parallel port protocol driver in your
  6.1689 +  system. Among the devices supported by this driver are the SyQuest
  6.1690 +  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
  6.1691 +  hard drives from MicroSolutions.
  6.1692 +
  6.1693 +Parallel port ATAPI CD-ROMs
  6.1694 +CONFIG_PARIDE_PCD
  6.1695 +  This option enables the high-level driver for ATAPI CD-ROM devices
  6.1696 +  connected through a parallel port. If you chose to build PARIDE
  6.1697 +  support into your kernel, you may answer Y here to build in the
  6.1698 +  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
  6.1699 +  build it as a loadable module. The module will be called pcd.o. You
  6.1700 +  must also have at least one parallel port protocol driver in your
  6.1701 +  system. Among the devices supported by this driver are the
  6.1702 +  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
  6.1703 +  you have such a CD-ROM drive, you should also say Y or M to "ISO
  6.1704 +  9660 CD-ROM file system support" below, because that's the file
  6.1705 +  system used on CD-ROMs.
  6.1706 +
  6.1707 +Parallel port ATAPI disks
  6.1708 +CONFIG_PARIDE_PF
  6.1709 +  This option enables the high-level driver for ATAPI disk devices
  6.1710 +  connected through a parallel port. If you chose to build PARIDE
  6.1711 +  support into your kernel, you may answer Y here to build in the
  6.1712 +  parallel port ATAPI disk driver, otherwise you should answer M
  6.1713 +  to build it as a loadable module. The module will be called pf.o.
  6.1714 +  You must also have at least one parallel port protocol driver in
  6.1715 +  your system. Among the devices supported by this driver are the
  6.1716 +  MicroSolutions backpack PD/CD drive and the Imation Superdisk
  6.1717 +  LS-120 drive.
  6.1718 +
  6.1719 +Parallel port ATAPI tapes
  6.1720 +CONFIG_PARIDE_PT
  6.1721 +  This option enables the high-level driver for ATAPI tape devices
  6.1722 +  connected through a parallel port. If you chose to build PARIDE
  6.1723 +  support into your kernel, you may answer Y here to build in the
  6.1724 +  parallel port ATAPI disk driver, otherwise you should answer M
  6.1725 +  to build it as a loadable module. The module will be called pt.o.
  6.1726 +  You must also have at least one parallel port protocol driver in
  6.1727 +  your system. Among the devices supported by this driver is the
  6.1728 +  parallel port version of the HP 5GB drive.
  6.1729 +
  6.1730 +Parallel port generic ATAPI devices
  6.1731 +CONFIG_PARIDE_PG
  6.1732 +  This option enables a special high-level driver for generic ATAPI
  6.1733 +  devices connected through a parallel port. The driver allows user
  6.1734 +  programs, such as cdrtools, to send ATAPI commands directly to a
  6.1735 +  device.
  6.1736 +
  6.1737 +  If you chose to build PARIDE support into your kernel, you may
  6.1738 +  answer Y here to build in the parallel port generic ATAPI driver,
  6.1739 +  otherwise you should answer M to build it as a loadable module. The
  6.1740 +  module will be called pg.o.
  6.1741 +
  6.1742 +  You must also have at least one parallel port protocol driver in
  6.1743 +  your system.
  6.1744 +
  6.1745 +  This driver implements an API loosely related to the generic SCSI
  6.1746 +  driver. See <file:include/linux/pg.h>. for details.
  6.1747 +
  6.1748 +  You can obtain the most recent version of cdrtools from
  6.1749 +  <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
  6.1750 +  later fully support this driver.
  6.1751 +
  6.1752 +ATEN EH-100 protocol
  6.1753 +CONFIG_PARIDE_ATEN
  6.1754 +  This option enables support for the ATEN EH-100 parallel port IDE
  6.1755 +  protocol. This protocol is used in some inexpensive low performance
  6.1756 +  parallel port kits made in Hong Kong. If you chose to build PARIDE
  6.1757 +  support into your kernel, you may answer Y here to build in the
  6.1758 +  protocol driver, otherwise you should answer M to build it as a
  6.1759 +  loadable module. The module will be called aten.o. You must also
  6.1760 +  have a high-level driver for the type of device that you want to
  6.1761 +  support.
  6.1762 +
  6.1763 +Micro Solutions BACKPACK Series 5 protocol
  6.1764 +CONFIG_PARIDE_BPCK
  6.1765 +  This option enables support for the Micro Solutions BACKPACK
  6.1766 +  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
  6.1767 +  before 1999 were Series 5) Series 5 drives will NOT always have the
  6.1768 +  Series noted on the bottom of the drive. Series 6 drivers will.
  6.1769 +
  6.1770 +  In other words, if your BACKPACK drive dosen't say "Series 6" on the
  6.1771 +  bottom, enable this option.
  6.1772 +
  6.1773 +  If you chose to build PARIDE support into your kernel, you may
  6.1774 +  answer Y here to build in the protocol driver, otherwise you should
  6.1775 +  answer M to build it as a loadable module.  The module will be
  6.1776 +  called bpck.o.  You must also have a high-level driver for the type
  6.1777 +  of device that you want to support.
  6.1778 +
  6.1779 +Micro Solutions BACKPACK Series 6 protocol
  6.1780 +CONFIG_PARIDE_BPCK6
  6.1781 +  This option enables support for the Micro Solutions BACKPACK
  6.1782 +  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
  6.1783 +  after 1999 were Series 6) Series 6 drives will have the Series noted
  6.1784 +  on the bottom of the drive.  Series 5 drivers don't always have it
  6.1785 +  noted.
  6.1786 +
  6.1787 +  In other words, if your BACKPACK drive says "Series 6" on the
  6.1788 +  bottom, enable this option.
  6.1789 +
  6.1790 +  If you chose to build PARIDE support into your kernel, you may
  6.1791 +  answer Y here to build in the protocol driver, otherwise you should
  6.1792 +  answer M to build it as a loadable module.  The module will be
  6.1793 +  called bpck6.o.  You must also have a high-level driver for the type
  6.1794 +  of device that you want to support.
  6.1795 +
  6.1796 +DataStor Commuter protocol
  6.1797 +CONFIG_PARIDE_COMM
  6.1798 +  This option enables support for the Commuter parallel port IDE
  6.1799 +  protocol from DataStor. If you chose to build PARIDE support
  6.1800 +  into your kernel, you may answer Y here to build in the protocol
  6.1801 +  driver, otherwise you should answer M to build it as a loadable
  6.1802 +  module. The module will be called comm.o. You must also have
  6.1803 +  a high-level driver for the type of device that you want to support.
  6.1804 +
  6.1805 +DataStor EP-2000 protocol
  6.1806 +CONFIG_PARIDE_DSTR
  6.1807 +  This option enables support for the EP-2000 parallel port IDE
  6.1808 +  protocol from DataStor. If you chose to build PARIDE support
  6.1809 +  into your kernel, you may answer Y here to build in the protocol
  6.1810 +  driver, otherwise you should answer M to build it as a loadable
  6.1811 +  module. The module will be called dstr.o. You must also have
  6.1812 +  a high-level driver for the type of device that you want to support.
  6.1813 +
  6.1814 +Shuttle EPAT/EPEZ protocol
  6.1815 +CONFIG_PARIDE_EPAT
  6.1816 +  This option enables support for the EPAT parallel port IDE protocol.
  6.1817 +  EPAT is a parallel port IDE adapter manufactured by Shuttle
  6.1818 +  Technology and widely used in devices from major vendors such as
  6.1819 +  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
  6.1820 +  PARIDE support into your kernel, you may answer Y here to build in
  6.1821 +  the protocol driver, otherwise you should answer M to build it as a
  6.1822 +  loadable module. The module will be called epat.o. You must also
  6.1823 +  have a high-level driver for the type of device that you want to
  6.1824 +  support.
  6.1825 +
  6.1826 +Shuttle EPAT c7/c8 extension
  6.1827 +CONFIG_PARIDE_EPATC8
  6.1828 +  This option enables support for the newer Shuttle EP1284 (aka c7 and
  6.1829 +  c8) chip. You need this if you are using any recent Imation SuperDisk
  6.1830 +  (LS-120) drive.
  6.1831 +
  6.1832 +Shuttle EPIA protocol
  6.1833 +CONFIG_PARIDE_EPIA
  6.1834 +  This option enables support for the (obsolete) EPIA parallel port
  6.1835 +  IDE protocol from Shuttle Technology. This adapter can still be
  6.1836 +  found in some no-name kits. If you chose to build PARIDE support
  6.1837 +  into your kernel, you may answer Y here to build in the protocol
  6.1838 +  driver, otherwise you should answer M to build it as a loadable
  6.1839 +  module. The module will be called epia.o. You must also have a
  6.1840 +  high-level driver for the type of device that you want to support.
  6.1841 +
  6.1842 +FIT TD-2000 protocol
  6.1843 +CONFIG_PARIDE_FIT2
  6.1844 +  This option enables support for the TD-2000 parallel port IDE
  6.1845 +  protocol from Fidelity International Technology. This is a simple
  6.1846 +  (low speed) adapter that is used in some portable hard drives. If
  6.1847 +  you chose to build PARIDE support into your kernel, you may answer Y
  6.1848 +  here to build in the protocol driver, otherwise you should answer M
  6.1849 +  to build it as a loadable module. The module will be called fit2.o.
  6.1850 +  You must also have a high-level driver for the type of device that
  6.1851 +  you want to support.
  6.1852 +
  6.1853 +FIT TD-3000 protocol
  6.1854 +CONFIG_PARIDE_FIT3
  6.1855 +  This option enables support for the TD-3000 parallel port IDE
  6.1856 +  protocol from Fidelity International Technology. This protocol is
  6.1857 +  used in newer models of their portable disk, CD-ROM and PD/CD
  6.1858 +  devices. If you chose to build PARIDE support into your kernel, you
  6.1859 +  may answer Y here to build in the protocol driver, otherwise you
  6.1860 +  should answer M to build it as a loadable module. The module will be
  6.1861 +  called fit3.o. You must also have a high-level driver for the type
  6.1862 +  of device that you want to support.
  6.1863 +
  6.1864 +Freecom IQ ASIC-2 protocol
  6.1865 +CONFIG_PARIDE_FRIQ
  6.1866 +  This option enables support for version 2 of the Freecom IQ parallel
  6.1867 +  port IDE adapter.  This adapter is used by the Maxell Superdisk
  6.1868 +  drive.  If you chose to build PARIDE support into your kernel, you
  6.1869 +  may answer Y here to build in the protocol driver, otherwise you
  6.1870 +  should answer M to build it as a loadable module. The module will be
  6.1871 +  called friq.o. You must also have a high-level driver for the type
  6.1872 +  of device that you want to support.
  6.1873 +
  6.1874 +FreeCom power protocol
  6.1875 +CONFIG_PARIDE_FRPW
  6.1876 +  This option enables support for the Freecom power parallel port IDE
  6.1877 +  protocol. If you chose to build PARIDE support into your kernel, you
  6.1878 +  may answer Y here to build in the protocol driver, otherwise you
  6.1879 +  should answer M to build it as a loadable module. The module will be
  6.1880 +  called frpw.o. You must also have a high-level driver for the type
  6.1881 +  of device that you want to support.
  6.1882 +
  6.1883 +KingByte KBIC-951A/971A protocols
  6.1884 +CONFIG_PARIDE_KBIC
  6.1885 +  This option enables support for the KBIC-951A and KBIC-971A parallel
  6.1886 +  port IDE protocols from KingByte Information Corp. KingByte's
  6.1887 +  adapters appear in many no-name portable disk and CD-ROM products,
  6.1888 +  especially in Europe. If you chose to build PARIDE support into your
  6.1889 +  kernel, you may answer Y here to build in the protocol driver,
  6.1890 +  otherwise you should answer M to build it as a loadable module. The
  6.1891 +  module will be called kbic.o. You must also have a high-level driver
  6.1892 +  for the type of device that you want to support.
  6.1893 +
  6.1894 +KT PHd protocol
  6.1895 +CONFIG_PARIDE_KTTI
  6.1896 +  This option enables support for the "PHd" parallel port IDE protocol
  6.1897 +  from KT Technology. This is a simple (low speed) adapter that is
  6.1898 +  used in some 2.5" portable hard drives. If you chose to build PARIDE
  6.1899 +  support into your kernel, you may answer Y here to build in the
  6.1900 +  protocol driver, otherwise you should answer M to build it as a
  6.1901 +  loadable module. The module will be called ktti.o. You must also
  6.1902 +  have a high-level driver for the type of device that you want to
  6.1903 +  support.
  6.1904 +
  6.1905 +OnSpec 90c20 protocol
  6.1906 +CONFIG_PARIDE_ON20
  6.1907 +  This option enables support for the (obsolete) 90c20 parallel port
  6.1908 +  IDE protocol from OnSpec (often marketed under the ValuStore brand
  6.1909 +  name). If you chose to build PARIDE support into your kernel, you
  6.1910 +  may answer Y here to build in the protocol driver, otherwise you
  6.1911 +  should answer M to build it as a loadable module. The module will
  6.1912 +  be called on20.o. You must also have a high-level driver for the
  6.1913 +  type of device that you want to support.
  6.1914 +
  6.1915 +OnSpec 90c26 protocol
  6.1916 +CONFIG_PARIDE_ON26
  6.1917 +  This option enables support for the 90c26 parallel port IDE protocol
  6.1918 +  from OnSpec Electronics (often marketed under the ValuStore brand
  6.1919 +  name). If you chose to build PARIDE support into your kernel, you
  6.1920 +  may answer Y here to build in the protocol driver, otherwise you
  6.1921 +  should answer M to build it as a loadable module. The module will be
  6.1922 +  called on26.o. You must also have a high-level driver for the type
  6.1923 +  of device that you want to support.
  6.1924 +
  6.1925 +Logical Volume Manager (LVM) support
  6.1926 +CONFIG_BLK_DEV_LVM
  6.1927 +  This driver lets you combine several hard disks, hard disk
  6.1928 +  partitions, multiple devices or even loop devices (for evaluation
  6.1929 +  purposes) into a volume group.  Imagine a volume group as a kind of
  6.1930 +  virtual disk. Logical volumes, which can be thought of as virtual
  6.1931 +  partitions, can be created in the volume group.  You can resize
  6.1932 +  volume groups and logical volumes after creation time, corresponding
  6.1933 +  to new capacity needs.  Logical volumes are accessed as block
  6.1934 +  devices named /dev/VolumeGroupName/LogicalVolumeName.
  6.1935 +
  6.1936 +  For details see <file:Documentation/LVM-HOWTO>.  You will need
  6.1937 +  supporting user space software; location is in
  6.1938 +  <file:Documentation/Changes>.
  6.1939 +
  6.1940 +  If you want to compile this support as a module ( = code which can
  6.1941 +  be inserted in and removed from the running kernel whenever you
  6.1942 +  want), say M here and read <file:Documentation/modules.txt>.  The
  6.1943 +  module will be called lvm-mod.o.
  6.1944 +
  6.1945 +Multiple devices driver support (RAID and LVM)
  6.1946 +CONFIG_MD
  6.1947 +  Support multiple physical spindles through a single logical device.
  6.1948 +  Required for RAID and logical volume management (LVM).
  6.1949 +
  6.1950 +Multiple devices driver support
  6.1951 +CONFIG_BLK_DEV_MD
  6.1952 +  This driver lets you combine several hard disk partitions into one
  6.1953 +  logical block device. This can be used to simply append one
  6.1954 +  partition to another one or to combine several redundant hard disks
  6.1955 +  into a RAID1/4/5 device so as to provide protection against hard
  6.1956 +  disk failures. This is called "Software RAID" since the combining of
  6.1957 +  the partitions is done by the kernel. "Hardware RAID" means that the
  6.1958 +  combining is done by a dedicated controller; if you have such a
  6.1959 +  controller, you do not need to say Y here.
  6.1960 +
  6.1961 +  More information about Software RAID on Linux is contained in the
  6.1962 +  Software RAID mini-HOWTO, available from
  6.1963 +  <http://www.tldp.org/docs.html#howto>. There you will also learn
  6.1964 +  where to get the supporting user space utilities raidtools.
  6.1965 +
  6.1966 +  This driver is also available as a module ( = code which can be
  6.1967 +  inserted in and removed from the running kernel whenever you want).
  6.1968 +  If you want to compile it as a module, say M here and read
  6.1969 +  <file:Documentation/modules.txt>. The module will be called
  6.1970 +  md.o
  6.1971 +
  6.1972 +  If unsure, say N.
  6.1973 +
  6.1974 +Linear (append) mode
  6.1975 +CONFIG_MD_LINEAR
  6.1976 +  If you say Y here, then your multiple devices driver will be able to
  6.1977 +  use the so-called linear mode, i.e. it will combine the hard disk
  6.1978 +  partitions by simply appending one to the other.
  6.1979 +
  6.1980 +  If you want to compile this as a module ( = code which can be
  6.1981 +  inserted in and removed from the running kernel whenever you want),
  6.1982 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.1983 +  will be called linear.o.
  6.1984 +
  6.1985 +  If unsure, say Y.
  6.1986 +
  6.1987 +RAID-0 (striping) mode
  6.1988 +CONFIG_MD_RAID0
  6.1989 +  If you say Y here, then your multiple devices driver will be able to
  6.1990 +  use the so-called raid0 mode, i.e. it will combine the hard disk
  6.1991 +  partitions into one logical device in such a fashion as to fill them
  6.1992 +  up evenly, one chunk here and one chunk there. This will increase
  6.1993 +  the throughput rate if the partitions reside on distinct disks.
  6.1994 +
  6.1995 +  Information about Software RAID on Linux is contained in the
  6.1996 +  Software-RAID mini-HOWTO, available from
  6.1997 +  <http://www.tldp.org/docs.html#howto>. There you will also
  6.1998 +  learn where to get the supporting user space utilities raidtools.
  6.1999 +
  6.2000 +  If you want to compile this as a module ( = code which can be
  6.2001 +  inserted in and removed from the running kernel whenever you want),
  6.2002 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.2003 +  will be called raid0.o.
  6.2004 +
  6.2005 +  If unsure, say Y.
  6.2006 +
  6.2007 +RAID-1 (mirroring) mode
  6.2008 +CONFIG_MD_RAID1
  6.2009 +  A RAID-1 set consists of several disk drives which are exact copies
  6.2010 +  of each other.  In the event of a mirror failure, the RAID driver
  6.2011 +  will continue to use the operational mirrors in the set, providing
  6.2012 +  an error free MD (multiple device) to the higher levels of the
  6.2013 +  kernel.  In a set with N drives, the available space is the capacity
  6.2014 +  of a single drive, and the set protects against a failure of (N - 1)
  6.2015 +  drives.
  6.2016 +
  6.2017 +  Information about Software RAID on Linux is contained in the
  6.2018 +  Software-RAID mini-HOWTO, available from
  6.2019 +  <http://www.tldp.org/docs.html#howto>.  There you will also
  6.2020 +  learn where to get the supporting user space utilities raidtools.
  6.2021 +
  6.2022 +  If you want to use such a RAID-1 set, say Y. This code is also
  6.2023 +  available as a module called raid1.o ( = code which can be inserted
  6.2024 +  in and removed from the running kernel whenever you want).  If you
  6.2025 +  want to compile it as a module, say M here and read
  6.2026 +  <file:Documentation/modules.txt>.
  6.2027 +
  6.2028 +  If unsure, say Y.
  6.2029 +
  6.2030 +RAID-4/RAID-5 mode
  6.2031 +CONFIG_MD_RAID5
  6.2032 +  A RAID-5 set of N drives with a capacity of C MB per drive provides
  6.2033 +  the capacity of C * (N - 1) MB, and protects against a failure
  6.2034 +  of a single drive. For a given sector (row) number, (N - 1) drives
  6.2035 +  contain data sectors, and one drive contains the parity protection.
  6.2036 +  For a RAID-4 set, the parity blocks are present on a single drive,
  6.2037 +  while a RAID-5 set distributes the parity across the drives in one
  6.2038 +  of the available parity distribution methods.
  6.2039 +
  6.2040 +  Information about Software RAID on Linux is contained in the
  6.2041 +  Software-RAID mini-HOWTO, available from
  6.2042 +  <http://www.tldp.org/docs.html#howto>. There you will also
  6.2043 +  learn where to get the supporting user space utilities raidtools.
  6.2044 +
  6.2045 +  If you want to use such a RAID-4/RAID-5 set, say Y. This code is
  6.2046 +  also available as a module called raid5.o ( = code which can be
  6.2047 +  inserted in and removed from the running kernel whenever you want).
  6.2048 +  If you want to compile it as a module, say M here and read
  6.2049 +  <file:Documentation/modules.txt>.
  6.2050 +
  6.2051 +  If unsure, say Y.
  6.2052 +
  6.2053 +Multipath I/O support
  6.2054 +CONFIG_MD_MULTIPATH
  6.2055 +  Multipath-IO is the ability of certain devices to address the same
  6.2056 +  physical disk over multiple 'IO paths'. The code ensures that such
  6.2057 +  paths can be defined and handled at runtime, and ensures that a
  6.2058 +  transparent failover to the backup path(s) happens if a IO errors
  6.2059 +  arrives on the primary path.
  6.2060 +
  6.2061 +  This driver is also available as a module ( = code which can be
  6.2062 +  inserted in and removed from the running kernel whenever you want).
  6.2063 +  If you want to compile it as a module, say M here and read
  6.2064 +  <file:Documentation/modules.txt>. The module will be called
  6.2065 +  multipath.o
  6.2066 +
  6.2067 +  If unsure, say N.
  6.2068 +
  6.2069 +Support for IDE Raid controllers
  6.2070 +CONFIG_BLK_DEV_ATARAID
  6.2071 +  Say Y or M if you have an IDE Raid controller and want linux
  6.2072 +  to use its softwareraid feature.  You must also select an
  6.2073 +  appropriate for your board low-level driver below.
  6.2074 +
  6.2075 +  Note, that Linux does not use the Raid implementation in BIOS, and
  6.2076 +  the main purpose for this feature is to retain compatibility and
  6.2077 +  data integrity with other OS-es, using the same disk array. Linux
  6.2078 +  has its own Raid drivers, which you should use if you need better
  6.2079 +  performance.
  6.2080 +
  6.2081 +  This driver is also available as a module ( = code which can be
  6.2082 +  inserted in and removed from the running kernel whenever you want).
  6.2083 +  If you want to compile it as a module, say M here and read
  6.2084 +  <file:Documentation/modules.txt>. The module will be called
  6.2085 +  ataraid.o
  6.2086 +
  6.2087 +Support Promise software RAID (Fasttrak(tm))
  6.2088 +CONFIG_BLK_DEV_ATARAID_PDC
  6.2089 +  Say Y or M if you have a Promise Fasttrak (tm) Raid controller
  6.2090 +  and want linux to use the softwareraid feature of this card.
  6.2091 +  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  6.2092 +  names.
  6.2093 +
  6.2094 +  If you choose to compile this as a module, the module will be called
  6.2095 +  pdcraid.o.
  6.2096 +
  6.2097 +Highpoint 370 software RAID
  6.2098 +CONFIG_BLK_DEV_ATARAID_HPT
  6.2099 +  Say Y or M if you have a Highpoint HPT 370 Raid controller
  6.2100 +  and want linux to use the softwareraid feature of this card.
  6.2101 +  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  6.2102 +  names.
  6.2103 +
  6.2104 +  If you choose to compile this as a module, the module will be called
  6.2105 +  hptraid.o.
  6.2106 +
  6.2107 +CMD/Silicon Image Medley Software RAID
  6.2108 +CONFIG_BLK_DEV_ATARAID_MEDLEY
  6.2109 +  Say Y or M if you have a Silicon Image 3112 SATA RAID controller,
  6.2110 +  a CMD680 based controller, or another IDE RAID controller that uses
  6.2111 +  CMD's Medley software RAID, and want Linux to use the software RAID
  6.2112 +  feature of this card.  This driver uses /dev/ataraid/dXpY (X and Y
  6.2113 +  numbers) as device names.
  6.2114 +
  6.2115 +  This driver currently only supports RAID0 (striped) mode, so if you
  6.2116 +  are using RAID1 (mirroring) this will not work for you. In that
  6.2117 +  case, you may want to try the Silicon Image Medley Software RAID
  6.2118 +  driver (below).
  6.2119 +
  6.2120 +  Support for mirroring is planned in the future.
  6.2121 +
  6.2122 +  If you choose to compile this as a module, the module will be called
  6.2123 +  medley.o.
  6.2124 +
  6.2125 +Silicon Image Medley Software RAID (old driver)
  6.2126 +CONFIG_BLK_DEV_ATARAID_SII
  6.2127 +  Say Y or M if you have a Silicon Image SATARaid controller
  6.2128 +  and want Linux to use the softwareraid feature of this card.
  6.2129 +  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  6.2130 +  names.
  6.2131 +
  6.2132 +  This driver does not reliably detect all Medley RAID sets, and could
  6.2133 +  be dangerous if you have a striped set with disks of different size.
  6.2134 +
  6.2135 +  You should use the new Medley RAID driver (above), unless you use
  6.2136 +  RAID1 (mirroring), which the new driver does not yet support.
  6.2137 +
  6.2138 +  If you choose to compile this as a module, the module will be called
  6.2139 +  silraid.o.
  6.2140 +
  6.2141 +Support for Acer PICA 1 chipset
  6.2142 +CONFIG_ACER_PICA_61
  6.2143 +  This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
  6.2144 +  kernel that runs on these, say Y here. For details about Linux on
  6.2145 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  6.2146 +  <http://www.linux-mips.org/>.
  6.2147 +
  6.2148 +Support for Algorithmics P4032 (EXPERIMENTAL)
  6.2149 +CONFIG_ALGOR_P4032
  6.2150 +  This is an evaluation board of the British company Algorithmics.
  6.2151 +  The board uses the R4300 and a R5230 CPUs.  For more information
  6.2152 +  about this board see <http://www.algor.co.uk/>.
  6.2153 +
  6.2154 +SGI SN2 L1 serial port support
  6.2155 +CONFIG_SGI_L1_SERIAL
  6.2156 +  If you have an SGI SN2 and you want to use the serial port connected
  6.2157 +  to the system controller (you want this!), say Y.  Otherwise, say N.
  6.2158 +
  6.2159 +SGI SN2 L1 serial console support
  6.2160 +CONFIG_SGI_L1_SERIAL_CONSOLE
  6.2161 +  If you have an SGI SN2 and you would like to use the system
  6.2162 +  controller serial port as your console (you want this!), say Y.
  6.2163 +  Otherwise, say N.
  6.2164 +
  6.2165 +Support for BAGET MIPS series
  6.2166 +CONFIG_BAGET_MIPS
  6.2167 +  This enables support for the Baget, a Russian embedded system.  For
  6.2168 +  more details about the Baget see the Linux/MIPS FAQ on
  6.2169 +  <http://www.linux-mips.org/>.
  6.2170 +
  6.2171 +Baget AMD LANCE support
  6.2172 +CONFIG_BAGETLANCE
  6.2173 +  Say Y to enable kernel support for AMD Lance Ethernet cards on the
  6.2174 +  MIPS-32-based Baget embedded system.  This chipset is better known
  6.2175 +  via the NE2100 cards.
  6.2176 +
  6.2177 +Support for DECstations
  6.2178 +CONFIG_DECSTATION
  6.2179 +  This enables support for DEC's MIPS based workstations.  For details
  6.2180 +  see the Linux/MIPS FAQ on <http://www.linux-mips.org/> and the
  6.2181 +  DECstation porting pages on <http://decstation.unix-ag.org/>.
  6.2182 +
  6.2183 +  If you have one of the following DECstation Models you definitely
  6.2184 +  want to choose R4xx0 for the CPU Type:
  6.2185 +
  6.2186 +	DECstation 5000/50
  6.2187 +	DECstation 5000/150
  6.2188 +	DECstation 5000/260
  6.2189 +	DECsystem 5900/260
  6.2190 +
  6.2191 +  otherwise choose R3000.
  6.2192 +
  6.2193 +Support for Cobalt Micro Server
  6.2194 +CONFIG_COBALT_MICRO_SERVER
  6.2195 +  Support for MIPS-based Cobalt boxes (they have been bought by Sun
  6.2196 +  and are now the "Server Appliance Business Unit") including the 2700
  6.2197 +  series -- versions 1 of the Qube and Raq.  To compile a Linux kernel
  6.2198 +  for this hardware, say Y here.
  6.2199 +
  6.2200 +Support for Cobalt 2800
  6.2201 +CONFIG_COBALT_28
  6.2202 +  Support for the second generation of MIPS-based Cobalt boxes (they
  6.2203 +  have been bought by Sun and are now the "Server Appliance Business
  6.2204 +  Unit") including the 2800 series -- versions 2 of the Qube and Raq.
  6.2205 +  To compile a Linux kernel for this hardware, say Y here.
  6.2206 +
  6.2207 +Support for the Momentum Computer Ocelot SBC
  6.2208 +CONFIG_MOMENCO_OCELOT
  6.2209 +  The Ocelot is a MIPS-based Single Board Computer (SBC) made by
  6.2210 +  Momentum Computer <http://www.momenco.com/>.
  6.2211 +
  6.2212 +Support for NEC DDB Vrc-5074
  6.2213 +CONFIG_DDB5074
  6.2214 +  This enables support for the VR5000-based NEC DDB Vrc-5074
  6.2215 +  evaluation board.
  6.2216 +
  6.2217 +Support for NEC DDB Vrc-5476
  6.2218 +CONFIG_DDB5476
  6.2219 +  This enables support for the R5432-based NEC DDB Vrc-5476
  6.2220 +  evaluation board.
  6.2221 +
  6.2222 +  Features : kernel debugging, serial terminal, NFS root fs, on-board
  6.2223 +  ether port (Need an additional patch at <http://linux.junsun.net/>),
  6.2224 +  USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
  6.2225 +  PS2 keyboard, PS2 mouse, etc.
  6.2226 +
  6.2227 +Support for NEC DDB Vrc-5477
  6.2228 +CONFIG_DDB5477
  6.2229 +  This enables support for the R5432-based NEC DDB Vrc-5477
  6.2230 +  evaluation board.
  6.2231 +
  6.2232 +  Features : kernel debugging, serial terminal, NFS root fs, on-board
  6.2233 +  ether port (Need an additional patch at <http://linux.junsun.net/>),
  6.2234 +  USB, AC97, PCI, etc.
  6.2235 +
  6.2236 +Support for MIPS Atlas board
  6.2237 +CONFIG_MIPS_ATLAS
  6.2238 +  This enables support for the QED R5231-based MIPS Atlas evaluation
  6.2239 +  board.
  6.2240 +
  6.2241 +Support for MIPS Malta board
  6.2242 +CONFIG_MIPS_MALTA
  6.2243 +  This enables support for the VR5000-based MIPS Malta evaluation
  6.2244 +  board.
  6.2245 +
  6.2246 +# Choice: bcmboard
  6.2247 +Support for Broadcom SiByte boards
  6.2248 +CONFIG_SIBYTE_SWARM
  6.2249 +  Enable support for boards based on the Broadcom SiByte family:
  6.2250 +
  6.2251 +  BCM91250A-SWARM    BCM1250 ATX size Eval Board (BCM91250A-SWARM)
  6.2252 +
  6.2253 +  BCM91250E-Sentosa  BCM1250 PCI card Eval Board (BCM91250E-Sentosa)
  6.2254 +
  6.2255 +  BCM91125E-Rhone    BCM1125 PCI card Eval Board (BCM91125E-Rhone)
  6.2256 +
  6.2257 +  Other              Non-Broadcom SiByte-based platform
  6.2258 +
  6.2259 +# Choice: bcmsoc
  6.2260 +Support for Broadcom BCM1xxx SOCs
  6.2261 +CONFIG_SIBYTE_SB1250
  6.2262 +
  6.2263 +  BCM1250     Dual-CPU SB1 with PCI and HyperTransport.
  6.2264 +
  6.2265 +  BCM1120     Uniprocessor SB1.
  6.2266 +
  6.2267 +  BCM1125     Uniprocessor SB1 with PCI (and HyperTransport for 1125H).
  6.2268 +
  6.2269 +BCM1250 Stepping
  6.2270 +CONFIG_CPU_SB1_PASS_1
  6.2271 +  Which pass of the SOC is supported (see the "system_revision"
  6.2272 +  register in the User Manual for more discussion of revisions):
  6.2273 +
  6.2274 +  Pass1    1250 "Pass 1"
  6.2275 +
  6.2276 +  An       1250 "Pass 2"
  6.2277 +
  6.2278 +  Bn       1250 "Pass 2.2"
  6.2279 +
  6.2280 +  Cn       1250 "Pass 3"
  6.2281 +
  6.2282 +BCM112x Stepping
  6.2283 +CONFIG_CPU_SB1_PASS_2
  6.2284 +  Which pass of the SOC is supported (see the "system_revision"
  6.2285 +  register in the User Manual for more discussion of revisions):
  6.2286 +
  6.2287 +  Hybrid   1250 "Pass 2"
  6.2288 +
  6.2289 +  An       112x "Pass 1"
  6.2290 +
  6.2291 +Booting from CFE
  6.2292 +CONFIG_SIBYTE_CFE
  6.2293 +  Make use of the CFE API for enumerating available memory,
  6.2294 +  controlling secondary CPUs, and possibly console output.
  6.2295 +
  6.2296 +Use firmware console
  6.2297 +CONFIG_SIBYTE_CFE_CONSOLE
  6.2298 +  Use the CFE API's console write routines during boot.  Other console
  6.2299 +  options (VT console, sb1250 duart console, etc.) should not be
  6.2300 +  configured.
  6.2301 +
  6.2302 +Support for Bus Watcher statistics
  6.2303 +CONFIG_SIBYTE_BUS_WATCHER
  6.2304 +  Handle and keep statistics on the bus error interrupts (COR_ECC,
  6.2305 +  BAD_ECC, IO_BUS).
  6.2306 +
  6.2307 +Bus trace dump on bus error
  6.2308 +CONFIG_SIBYTE_BW_TRACE
  6.2309 +  Run a continuous bus trace, dumping the raw data as soon as a ZBbus
  6.2310 +  error is detected.  Cannot work if ZBbus profiling is turned on, and
  6.2311 +  also will interfere with JTAG-based trace buffer activity.  Raw
  6.2312 +  buffer data is dumped to console, and must be processed off-line.
  6.2313 +
  6.2314 +Corelis Debugger
  6.2315 +CONFIG_SB1XXX_CORELIS
  6.2316 +  Select compile flags that produce code that can be processed by the
  6.2317 +  Corelis mksym utility and UDB Emulator.
  6.2318 +
  6.2319 +DMA for page clear and copy
  6.2320 +CONFIG_SIBYTE_DMA_PAGEOPS
  6.2321 +  Instead of using the CPU to zero and copy pages, use a Data Mover
  6.2322 +  channel.  These DMA channels are otherwise unused by the standard
  6.2323 +  SiByte Linux port.  Seems to give a small performance benefit.
  6.2324 +
  6.2325 +Support for Galileo Evaluation board or CoSine Orion
  6.2326 +CONFIG_ORION
  6.2327 +  Say Y if configuring for the Galileo evaluation board
  6.2328 +  or CoSine Orion.  More information is available at
  6.2329 +  <http://tochna.technion.ac.il/project/linux/html/linux.html>.
  6.2330 +
  6.2331 +  Otherwise, say N.
  6.2332 +
  6.2333 +Support for Mips Magnum 4000
  6.2334 +CONFIG_MIPS_MAGNUM_4000
  6.2335 +  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  6.2336 +  kernel that runs on these, say Y here. For details about Linux on
  6.2337 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  6.2338 +  <http://www.linux-mips.org/>.
  6.2339 +
  6.2340 +Enable Qtronix 990P Keyboard Support
  6.2341 +CONFIG_QTRONIX_KEYBOARD
  6.2342 +  Images of Qtronix keyboards are at
  6.2343 +  <http://www.qtronix.com/keyboard.html>.
  6.2344 +
  6.2345 +Support for Olivetti M700
  6.2346 +CONFIG_OLIVETTI_M700
  6.2347 +  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  6.2348 +  kernel that runs on these, say Y here. For details about Linux on
  6.2349 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  6.2350 +  <http://www.linux-mips.org/>.
  6.2351 +
  6.2352 +Support for SNI RM200 PCI
  6.2353 +CONFIG_SNI_RM200_PCI
  6.2354 +  The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
  6.2355 +  Nixdorf Informationssysteme (SNI), parent company of Pyramid
  6.2356 +  Technology and now in turn merged with Fujitsu.  Say Y here to
  6.2357 +  support this machine type.
  6.2358 +
  6.2359 +Support for SGI-IP22 (Indy/Indigo2)
  6.2360 +CONFIG_SGI_IP22
  6.2361 +  This are the SGI Indy, Challenge S and Indigo2, as well as certain
  6.2362 +  OEM variants like the Tandem CMN B006S. To compile a Linux kernel
  6.2363 +  that runs on these, say Y here.
  6.2364 +
  6.2365 +Support for SGI IP27 (Origin200/2000)
  6.2366 +CONFIG_SGI_IP27
  6.2367 +  This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
  6.2368 +  workstations.  To compile a Linux kernel that runs on these, say Y
  6.2369 +  here.
  6.2370 +
  6.2371 +IP27 N-Mode
  6.2372 +CONFIG_SGI_SN0_N_MODE
  6.2373 +  The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
  6.2374 +  configured in either N-Modes which allows for more nodes or M-Mode
  6.2375 +  which allows for more memory.  Your system is most probably
  6.2376 +  running in M-Mode, so you should say N here.
  6.2377 +
  6.2378 +Lasi Ethernet
  6.2379 +CONFIG_LASI_82596
  6.2380 +  Say Y here to support the on-board Intel 82596 ethernet controller
  6.2381 +  built into Hewlett-Packard PA-RISC machines.
  6.2382 +
  6.2383 +MIPS JAZZ onboard SONIC Ethernet support
  6.2384 +CONFIG_MIPS_JAZZ_SONIC
  6.2385 +  This is the driver for the onboard card of MIPS Magnum 4000,
  6.2386 +  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
  6.2387 +
  6.2388 +MIPS JAZZ FAS216 SCSI support
  6.2389 +CONFIG_JAZZ_ESP
  6.2390 +  This is the driver for the onboard SCSI host adapter of MIPS Magnum
  6.2391 +  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
  6.2392 +  systems.
  6.2393 +
  6.2394 +MIPS GT96100 Ethernet support
  6.2395 +CONFIG_MIPS_GT96100ETH
  6.2396 +  Say Y here to support the Ethernet subsystem on your GT96100 card.
  6.2397 +
  6.2398 +Zalon SCSI support
  6.2399 +CONFIG_SCSI_ZALON
  6.2400 +  The Zalon is an interface chip that sits between the PA-RISC
  6.2401 +  processor and the NCR 53c720 SCSI controller on K-series PA-RISC
  6.2402 +  boards (these are used, among other places, on some HP 780
  6.2403 +  workstations).  Say Y here to make sure it gets initialized
  6.2404 +  correctly before the Linux kernel tries to talk to the controller.
  6.2405 +
  6.2406 +SGI PROM Console Support
  6.2407 +CONFIG_SGI_PROM_CONSOLE
  6.2408 +  Say Y here to set up the boot console on serial port 0.
  6.2409 +
  6.2410 +DECstation serial support
  6.2411 +CONFIG_SERIAL_DEC
  6.2412 +  This selects whether you want to be asked about drivers for
  6.2413 +  DECstation serial ports.
  6.2414 +
  6.2415 +  Note that the answer to this question won't directly affect the
  6.2416 +  kernel: saying N will just cause the configurator to skip all
  6.2417 +  the questions about DECstation serial ports.
  6.2418 +
  6.2419 +  If unsure, say Y.
  6.2420 +
  6.2421 +Support for console on a DECstation serial port
  6.2422 +CONFIG_SERIAL_DEC_CONSOLE
  6.2423 +  If you say Y here, it will be possible to use a serial port as the
  6.2424 +  system console (the system console is the device which receives all
  6.2425 +  kernel messages and warnings and which allows logins in single user
  6.2426 +  mode).  Note that the firmware uses ttyS0 as the serial console on
  6.2427 +  the Maxine and ttyS2 on the others.
  6.2428 +
  6.2429 +  If unsure, say Y.
  6.2430 +
  6.2431 +DZ11 Serial Support
  6.2432 +CONFIG_DZ
  6.2433 +  DZ11-family serial controllers for VAXstations, including the
  6.2434 +  DC7085, M7814, and M7819.
  6.2435 +
  6.2436 +TURBOchannel support
  6.2437 +CONFIG_TC
  6.2438 +  TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
  6.2439 +  Documentation on writing device drivers for TurboChannel is available at:
  6.2440 +  <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
  6.2441 +
  6.2442 +# Choice: galileo_clock
  6.2443 +75
  6.2444 +CONFIG_SYSCLK_75
  6.2445 +  Configure the kernel for clock speed of your Galileo board.  
  6.2446 +  The choices are 75MHz, 83.3MHz, and 100MHz.
  6.2447 +
  6.2448 +83.3
  6.2449 +CONFIG_SYSCLK_83
  6.2450 +  Configure the Galileo kernel for a clock speed of 83.3 MHz.
  6.2451 +
  6.2452 +100
  6.2453 +CONFIG_SYSCLK_100
  6.2454 +  Configure the Galileo kernel for a clock speed of 100 MHz.
  6.2455 +
  6.2456 +Z85C30 Serial Support
  6.2457 +CONFIG_ZS
  6.2458 +  Documentation on the Zilog 85C350 serial communications controller
  6.2459 +  is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
  6.2460 +
  6.2461 +PCMCIA SCSI adapter support
  6.2462 +CONFIG_SCSI_PCMCIA
  6.2463 +  Say Y here if you intend to attach a PCMCIA or CardBus card to your
  6.2464 +  computer which acts as a SCSI host adapter. These are credit card
  6.2465 +  size devices often used with laptops.
  6.2466 +
  6.2467 +  Note that the answer to this question won't directly affect the
  6.2468 +  kernel: saying N will just cause the configurator to skip all
  6.2469 +  the questions PCMCIA SCSI host adapters.
  6.2470 +
  6.2471 +Adaptec APA1480 CardBus support
  6.2472 +CONFIG_PCMCIA_APA1480
  6.2473 +  Say Y here if you intend to attach this type of CardBus SCSI host
  6.2474 +  adapter to your computer.
  6.2475 +
  6.2476 +  This driver is also available as a module called apa1480_cb.o ( =
  6.2477 +  code which can be inserted in and removed from the running kernel
  6.2478 +  whenever you want). If you want to compile it as a module, say M
  6.2479 +  here and read <file:Documentation/modules.txt>.
  6.2480 +
  6.2481 +NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
  6.2482 +CONFIG_PCMCIA_NINJA_SCSI
  6.2483 +  If you intend to attach this type of PCMCIA SCSI host adapter to
  6.2484 +  your computer, say Y here and read
  6.2485 +  <file:Documentation/README.nsp_cs.eng>.
  6.2486 +
  6.2487 +  This driver is also available as a module called nsp_cs.o ( =
  6.2488 +  code which can be inserted in and removed from the running kernel
  6.2489 +  whenever you want). If you want to compile it as a module, say M
  6.2490 +  here and read <file:Documentation/modules.txt>.
  6.2491 +
  6.2492 +Adaptec AHA152X PCMCIA support
  6.2493 +CONFIG_PCMCIA_AHA152X
  6.2494 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  6.2495 +  adapter to your computer.
  6.2496 +
  6.2497 +  This driver is also available as a module called aha152x_cs.o ( =
  6.2498 +  code which can be inserted in and removed from the running kernel
  6.2499 +  whenever you want). If you want to compile it as a module, say M
  6.2500 +  here and read <file:Documentation/modules.txt>.
  6.2501 +
  6.2502 +Qlogic PCMCIA support
  6.2503 +CONFIG_PCMCIA_QLOGIC
  6.2504 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  6.2505 +  adapter to your computer.
  6.2506 +
  6.2507 +  This driver is also available as a module called qlogic_cs.o ( =
  6.2508 +  code which can be inserted in and removed from the running kernel
  6.2509 +  whenever you want).  If you want to compile it as a module, say M
  6.2510 +  here and read <file:Documentation/modules.txt>.
  6.2511 +
  6.2512 +Future Domain PCMCIA support
  6.2513 +CONFIG_PCMCIA_FDOMAIN
  6.2514 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  6.2515 +  adapter to your computer.
  6.2516 +
  6.2517 +  This driver is also available as a module called fdomain_cs.o ( =
  6.2518 +  code which can be inserted in and removed from the running kernel
  6.2519 +  whenever you want).  If you want to compile it as a module, say M
  6.2520 +  here and read <file:Documentation/modules.txt>.
  6.2521 +
  6.2522 +# Choice: mipstype
  6.2523 +CPU type
  6.2524 +CONFIG_CPU_R3000
  6.2525 +  Please make sure to pick the right CPU type. Linux/MIPS is not
  6.2526 +  designed to be generic, i.e. Kernels compiled for R3000 CPUs will
  6.2527 +  *not* work on R4000 machines and vice versa.  However, since most
  6.2528 +  of the supported machines have an R4000 (or similar) CPU, R4x00
  6.2529 +  might be a safe bet.  If the resulting kernel does not work,
  6.2530 +  try to recompile with R3000.
  6.2531 +
  6.2532 +  R3000    MIPS Technologies R3000-series processors,
  6.2533 +           including the 3041, 3051, and 3081.
  6.2534 +
  6.2535 +  R6000    MIPS Technologies R6000-series processors,
  6.2536 +           including the 64474, 64475, 64574 and 64575.
  6.2537 +
  6.2538 +  R4300    MIPS Technologies R4300-series processors.
  6.2539 +
  6.2540 +  R4x00    MIPS Technologies R4000-series processors other than 4300,
  6.2541 +           including the 4640, 4650, and 4700.
  6.2542 +
  6.2543 +  R5000    MIPS Technologies R5000-series processors other than the
  6.2544 +           Nevada.
  6.2545 +
  6.2546 +  R52xx    MIPS Technologies R52xx-series ("Nevada") processors.
  6.2547 +
  6.2548 +  R10000   MIPS Technologies R10000-series processors.
  6.2549 +
  6.2550 +  SB1      Broadcom SiByte SB1 processor.
  6.2551 +
  6.2552 +R6000
  6.2553 +CONFIG_CPU_R6000
  6.2554 +  MIPS Technologies R6000-series processors, including the 64474,
  6.2555 +  64475, 64574 and 64575.
  6.2556 +
  6.2557 +R4300
  6.2558 +CONFIG_CPU_R4300
  6.2559 +  MIPS Technologies R4300-series processors.
  6.2560 +
  6.2561 +R4x00
  6.2562 +CONFIG_CPU_R4X00
  6.2563 +  MIPS Technologies R4000-series processors other than 4300, including
  6.2564 +  the 4640, 4650, and 4700.
  6.2565 +
  6.2566 +R5000
  6.2567 +CONFIG_CPU_R5000
  6.2568 +  MIPS Technologies R5000-series processors other than the Nevada.
  6.2569 +
  6.2570 +R52x0
  6.2571 +CONFIG_CPU_NEVADA
  6.2572 +  MIPS Technologies R52x0-series ("Nevada") processors.
  6.2573 +
  6.2574 +R8000
  6.2575 +CONFIG_CPU_R8000
  6.2576 +  MIPS Technologies R8000-series processors.
  6.2577 +
  6.2578 +R10000
  6.2579 +CONFIG_CPU_R10000
  6.2580 +  MIPS Technologies R10000-series processors.
  6.2581 +
  6.2582 +SB1
  6.2583 +CONFIG_CPU_SB1
  6.2584 +  Broadcom SiByte SB1 processor.
  6.2585 +
  6.2586 +Discontiguous Memory Support
  6.2587 +CONFIG_DISCONTIGMEM
  6.2588 +  Say Y to support efficient handling of discontiguous physical memory,
  6.2589 +  for architectures which are either NUMA (Non-Uniform Memory Access)
  6.2590 +  or have huge holes in the physical address space for other reasons.
  6.2591 +  See <file:Documentation/vm/numa> for more.
  6.2592 +
  6.2593 +Mapped kernel support
  6.2594 +CONFIG_MAPPED_KERNEL
  6.2595 +  Change the way a Linux kernel is loaded unto memory on a MIPS64
  6.2596 +  machine.  This is required in order to support text replication and
  6.2597 +  NUMA.  If you need to understand it, read the source code.
  6.2598 +
  6.2599 +Kernel text replication support
  6.2600 +CONFIG_REPLICATE_KTEXT
  6.2601 +  Say Y here to enable replicating the kernel text across multiple
  6.2602 +  nodes in a NUMA cluster.  This trades memory for speed.
  6.2603 +
  6.2604 +Exception handler replication support
  6.2605 +CONFIG_REPLICATE_EXHANDLERS
  6.2606 +  Say Y here to enable replicating the kernel exception handlers
  6.2607 +  across multiple nodes in a NUMA cluster. This trades memory for
  6.2608 +  speed.
  6.2609 +
  6.2610 +NUMA support?
  6.2611 +CONFIG_NUMA
  6.2612 +  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
  6.2613 +  Access).  This option is for configuring high-end multiprocessor
  6.2614 +  server machines.  If in doubt, say N.
  6.2615 +
  6.2616 +R41xx
  6.2617 +CONFIG_CPU_VR41XX
  6.2618 +  The options selects support for the NEC VR41xx series of processors.
  6.2619 +  Only choose this option if you have one of these processors as a
  6.2620 +  kernel built with this option will not run on any other type of
  6.2621 +  processor or vice versa.
  6.2622 +
  6.2623 +CPU feature configuration
  6.2624 +CONFIG_CPU_ADVANCED
  6.2625 +  Saying yes here allows you to select support for various features
  6.2626 +  your CPU may or may not have.  Most people should say N here.
  6.2627 +
  6.2628 +ll and sc instructions available
  6.2629 +CONFIG_CPU_HAS_LLSC
  6.2630 +  MIPS R4000 series and later provide the Load Linked (ll)
  6.2631 +  and Store Conditional (sc) instructions. More information is
  6.2632 +  available at <http://www.go-ecs.com/mips/miptek1.htm>.
  6.2633 +
  6.2634 +  Say Y here if your CPU has the ll and sc instructions.  Say Y here
  6.2635 +  for better performance, N if you don't know.  You must say Y here
  6.2636 +  for multiprocessor machines.
  6.2637 +
  6.2638 +lld and scd instructions available
  6.2639 +CONFIG_CPU_HAS_LLDSCD
  6.2640 +  Say Y here if your CPU has the lld and scd instructions, the 64-bit
  6.2641 +  equivalents of ll and sc.  Say Y here for better performance, N if
  6.2642 +  you don't know.  You must say Y here for multiprocessor machines.
  6.2643 +
  6.2644 +Writeback Buffer available
  6.2645 +CONFIG_CPU_HAS_WB
  6.2646 +  Say N here for slightly better performance.  You must say Y here for
  6.2647 +  machines which require flushing of write buffers in software.  Saying
  6.2648 +  Y is the safe option; N may result in kernel malfunction and crashes.
  6.2649 +
  6.2650 +Support for large 64-bit configurations
  6.2651 +CONFIG_MIPS_INSANE_LARGE
  6.2652 +  MIPS R10000 does support a 44 bit / 16TB address space as opposed to
  6.2653 +  previous 64-bit processors which only supported 40 bit / 1TB. If you
  6.2654 +  need processes of more than 1TB virtual address space, say Y here.
  6.2655 +  This will result in additional memory usage, so it is not
  6.2656 +  recommended for normal users.
  6.2657 +
  6.2658 +Generate little endian code
  6.2659 +CONFIG_CPU_LITTLE_ENDIAN
  6.2660 +  Some MIPS machines can be configured for either little or big endian
  6.2661 +  byte order. These modes require different kernels. Say Y if your
  6.2662 +  machine is little endian, N if it's a big endian machine.
  6.2663 +
  6.2664 +Use power LED as a heartbeat
  6.2665 +CONFIG_HEARTBEAT
  6.2666 +  Use the power-on LED on your machine as a load meter.  The exact
  6.2667 +  behaviour is platform-dependent, but normally the flash frequency is
  6.2668 +  a hyperbolic function of the 5-minute load average.
  6.2669 +
  6.2670 +Networking support
  6.2671 +CONFIG_NET
  6.2672 +  Unless you really know what you are doing, you should say Y here.
  6.2673 +  The reason is that some programs need kernel networking support even
  6.2674 +  when running on a stand-alone machine that isn't connected to any
  6.2675 +  other computer. If you are upgrading from an older kernel, you
  6.2676 +  should consider updating your networking tools too because changes
  6.2677 +  in the kernel and the tools often go hand in hand. The tools are
  6.2678 +  contained in the package net-tools, the location and version number
  6.2679 +  of which are given in <file:Documentation/Changes>.
  6.2680 +
  6.2681 +  For a general introduction to Linux networking, it is highly
  6.2682 +  recommended to read the NET-HOWTO, available from
  6.2683 +  <http://www.tldp.org/docs.html#howto>.
  6.2684 +
  6.2685 +Socket filtering
  6.2686 +CONFIG_FILTER
  6.2687 +  The Linux Socket Filter is derived from the Berkeley Packet Filter.
  6.2688 +  If you say Y here, user-space programs can attach a filter to any
  6.2689 +  socket and thereby tell the kernel that it should allow or disallow
  6.2690 +  certain types of data to get through the socket.  Linux Socket
  6.2691 +  Filtering works on all socket types except TCP for now.  See the
  6.2692 +  text file <file:Documentation/networking/filter.txt> for more
  6.2693 +  information.
  6.2694 +
  6.2695 +  You need to say Y here if you want to use PPP packet filtering
  6.2696 +  (see the CONFIG_PPP_FILTER option below).
  6.2697 +
  6.2698 +  If unsure, say N.
  6.2699 +
  6.2700 +Network packet filtering (replaces ipchains)
  6.2701 +CONFIG_NETFILTER
  6.2702 +  Netfilter is a framework for filtering and mangling network packets
  6.2703 +  that pass through your Linux box.
  6.2704 +
  6.2705 +  The most common use of packet filtering is to run your Linux box as
  6.2706 +  a firewall protecting a local network from the Internet. The type of
  6.2707 +  firewall provided by this kernel support is called a "packet
  6.2708 +  filter", which means that it can reject individual network packets
  6.2709 +  based on type, source, destination etc. The other kind of firewall,
  6.2710 +  a "proxy-based" one, is more secure but more intrusive and more
  6.2711 +  bothersome to set up; it inspects the network traffic much more
  6.2712 +  closely, modifies it and has knowledge about the higher level
  6.2713 +  protocols, which a packet filter lacks. Moreover, proxy-based
  6.2714 +  firewalls often require changes to the programs running on the local
  6.2715 +  clients. Proxy-based firewalls don't need support by the kernel, but
  6.2716 +  they are often combined with a packet filter, which only works if
  6.2717 +  you say Y here.
  6.2718 +
  6.2719 +  You should also say Y here if you intend to use your Linux box as
  6.2720 +  the gateway to the Internet for a local network of machines without
  6.2721 +  globally valid IP addresses. This is called "masquerading": if one
  6.2722 +  of the computers on your local network wants to send something to
  6.2723 +  the outside, your box can "masquerade" as that computer, i.e. it
  6.2724 +  forwards the traffic to the intended outside destination, but
  6.2725 +  modifies the packets to make it look like they came from the
  6.2726 +  firewall box itself. It works both ways: if the outside host
  6.2727 +  replies, the Linux box will silently forward the traffic to the
  6.2728 +  correct local computer. This way, the computers on your local net
  6.2729 +  are completely invisible to the outside world, even though they can
  6.2730 +  reach the outside and can receive replies. It is even possible to
  6.2731 +  run globally visible servers from within a masqueraded local network
  6.2732 +  using a mechanism called portforwarding. Masquerading is also often
  6.2733 +  called NAT (Network Address Translation).
  6.2734 +
  6.2735 +  Another use of Netfilter is in transparent proxying: if a machine on
  6.2736 +  the local network tries to connect to an outside host, your Linux
  6.2737 +  box can transparently forward the traffic to a local server,
  6.2738 +  typically a caching proxy server.
  6.2739 +
  6.2740 +  Various modules exist for netfilter which replace the previous
  6.2741 +  masquerading (ipmasqadm), packet filtering (ipchains), transparent
  6.2742 +  proxying, and portforwarding mechanisms. Please see
  6.2743 +  <file:Documentation/Changes> under "iptables" for the location of
  6.2744 +  these packages.
  6.2745 +
  6.2746 +  Make sure to say N to "Fast switching" below if you intend to say Y
  6.2747 +  here, as Fast switching currently bypasses netfilter.
  6.2748 +
  6.2749 +  Chances are that you should say Y here if you compile a kernel which
  6.2750 +  will run as a router and N for regular hosts. If unsure, say N.
  6.2751 +
  6.2752 +Network packet filtering debugging
  6.2753 +CONFIG_NETFILTER_DEBUG
  6.2754 +  You can say Y here if you want to get additional messages useful in
  6.2755 +  debugging the netfilter code.
  6.2756 +
  6.2757 +Connection tracking (required for masq/NAT)
  6.2758 +CONFIG_IP_NF_CONNTRACK
  6.2759 +  Connection tracking keeps a record of what packets have passed
  6.2760 +  through your machine, in order to figure out how they are related
  6.2761 +  into connections.
  6.2762 +
  6.2763 +  This is required to do Masquerading or other kinds of Network
  6.2764 +  Address Translation (except for Fast NAT).  It can also be used to
  6.2765 +  enhance packet filtering (see `Connection state match support'
  6.2766 +  below).
  6.2767 +
  6.2768 +  If you want to compile it as a module, say M here and read
  6.2769 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2770 +
  6.2771 +Amanda protocol support
  6.2772 +CONFIG_IP_NF_AMANDA
  6.2773 +  If you are running the Amanda backup package (http://www.amanda.org/)
  6.2774 +  on this machine or machines that will be MASQUERADED through this
  6.2775 +  machine, then you may want to enable this feature.  This allows the
  6.2776 +  connection tracking and natting code to allow the sub-channels that
  6.2777 +  Amanda requires for communication of the backup data, messages and
  6.2778 +  index.
  6.2779 +
  6.2780 +  If you want to compile it as a module, say M here and read
  6.2781 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2782 +
  6.2783 +
  6.2784 +IRC Send/Chat protocol support
  6.2785 +CONFIG_IP_NF_IRC
  6.2786 +  There is a commonly-used extension to IRC called
  6.2787 +  Direct Client-to-Client Protocol (DCC).  This enables users to send
  6.2788 +  files to each other, and also chat to each other without the need
  6.2789 +  of a server.  DCC Sending is used anywhere you send files over IRC,
  6.2790 +  and DCC Chat is most commonly used by Eggdrop bots.  If you are
  6.2791 +  using NAT, this extension will enable you to send files and initiate
  6.2792 +  chats.  Note that you do NOT need this extension to get files or
  6.2793 +  have others initiate chats, or everything else in IRC.
  6.2794 +
  6.2795 +  If you want to compile it as a module, say 'M' here and read
  6.2796 +  Documentation/modules.txt.  If unsure, say 'N'.
  6.2797 +
  6.2798 +TFTP protocol support
  6.2799 +CONFIG_IP_NF_TFTP
  6.2800 +  TFTP connection tracking helper, this is required depending
  6.2801 +  on how restrictive your ruleset is.
  6.2802 +  If you are using a tftp client behind -j SNAT or -j MASQUERADING
  6.2803 +  you will need this.
  6.2804 +
  6.2805 +  If you want to compile it as a module, say M here and read
  6.2806 +  Documentation/modules.txt.  If unsure, say `Y'.
  6.2807 +
  6.2808 +FTP protocol support
  6.2809 +CONFIG_IP_NF_FTP
  6.2810 +  Tracking FTP connections is problematic: special helpers are
  6.2811 +  required for tracking them, and doing masquerading and other forms
  6.2812 +  of Network Address Translation on them.
  6.2813 +
  6.2814 +  If you want to compile it as a module, say M here and read
  6.2815 +  <file:Documentation/modules.txt>.  If unsure, say `Y'.
  6.2816 +
  6.2817 +User space queueing via NETLINK
  6.2818 +CONFIG_IP_NF_QUEUE
  6.2819 +  Netfilter has the ability to queue packets to user space: the
  6.2820 +  netlink device can be used to access them using this driver.
  6.2821 +
  6.2822 +  If you want to compile it as a module, say M here and read
  6.2823 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2824 +
  6.2825 +IP tables support (required for filtering/masq/NAT)
  6.2826 +CONFIG_IP_NF_IPTABLES
  6.2827 +  iptables is a general, extensible packet identification framework.
  6.2828 +  The packet filtering and full NAT (masquerading, port forwarding,
  6.2829 +  etc) subsystems now use this: say `Y' or `M' here if you want to use
  6.2830 +  either of those.
  6.2831 +
  6.2832 +  If you want to compile it as a module, say M here and read
  6.2833 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2834 +
  6.2835 +recent match support
  6.2836 +CONFIG_IP_NF_MATCH_RECENT
  6.2837 +  This match is used for creating one or many lists of recently
  6.2838 +  used addresses and then matching against that/those list(s).
  6.2839 +
  6.2840 +  Short options are available by using 'iptables -m recent -h'
  6.2841 +  Official Website: <http://snowman.net/projects/ipt_recent/>
  6.2842 +
  6.2843 +  If you want to compile it as a module, say M here and read
  6.2844 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2845 +
  6.2846 +limit match support
  6.2847 +CONFIG_IP_NF_MATCH_LIMIT
  6.2848 +  limit matching allows you to control the rate at which a rule can be
  6.2849 +  matched: mainly useful in combination with the LOG target ("LOG
  6.2850 +  target support", below) and to avoid some Denial of Service attacks.
  6.2851 +
  6.2852 +  If you want to compile it as a module, say M here and read
  6.2853 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2854 +
  6.2855 +skb->pkt_type packet match support
  6.2856 +CONFIG_IP_NF_MATCH_PKTTYPE
  6.2857 +  This patch allows you to match packet in accrodance
  6.2858 +  to its "class", eg. BROADCAST, MULTICAST, ...
  6.2859 +  
  6.2860 +  Typical usage:
  6.2861 +  iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  6.2862 +  
  6.2863 +  If you want to compile it as a module, say M here and read
  6.2864 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2865 +
  6.2866 +MAC address match support
  6.2867 +CONFIG_IP_NF_MATCH_MAC
  6.2868 +  MAC matching allows you to match packets based on the source
  6.2869 +  Ethernet address of the packet.
  6.2870 +
  6.2871 +  If you want to compile it as a module, say M here and read
  6.2872 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2873 +
  6.2874 +Netfilter MARK match support
  6.2875 +CONFIG_IP_NF_MATCH_MARK
  6.2876 +  Netfilter mark matching allows you to match packets based on the
  6.2877 +  `nfmark' value in the packet.  This can be set by the MARK target
  6.2878 +  (see below).
  6.2879 +
  6.2880 +  If you want to compile it as a module, say M here and read
  6.2881 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2882 +
  6.2883 +Multiple port match support
  6.2884 +CONFIG_IP_NF_MATCH_MULTIPORT
  6.2885 +  Multiport matching allows you to match TCP or UDP packets based on
  6.2886 +  a series of source or destination ports: normally a rule can only
  6.2887 +  match a single range of ports.
  6.2888 +
  6.2889 +  If you want to compile it as a module, say M here and read
  6.2890 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2891 +
  6.2892 +TTL match support
  6.2893 +CONFIG_IP_NF_MATCH_TTL
  6.2894 +  This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
  6.2895 +  to match packets by their TTL value.
  6.2896 +
  6.2897 +  If you want to compile it as a module, say M here and read
  6.2898 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2899 +
  6.2900 +LENGTH match support
  6.2901 +CONFIG_IP_NF_MATCH_LENGTH
  6.2902 +  This option allows you to match the length of a packet against a
  6.2903 +  specific value or range of values.
  6.2904 +
  6.2905 +  If you want to compile it as a module, say M here and read
  6.2906 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2907 +
  6.2908 +AH/ESP match support
  6.2909 +CONFIG_IP_NF_MATCH_AH_ESP
  6.2910 +  These two match extensions (`ah' and `esp') allow you to match a
  6.2911 +  range of SPIs inside AH or ESP headers of IPSec packets.
  6.2912 +
  6.2913 +  If you want to compile it as a module, say M here and read
  6.2914 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2915 +
  6.2916 +DSCP match support
  6.2917 +CONFIG_IP_NF_MATCH_DSCP
  6.2918 +  This option adds a `DSCP' match, which allows you to match against
  6.2919 +  the IPv4 header DSCP field (DSCP codepoint).
  6.2920 +
  6.2921 +  The DSCP codepoint can have any value between 0x0 and 0x4f.
  6.2922 +
  6.2923 +  If you want to compile it as a module, say M here and read
  6.2924 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2925 +
  6.2926 + 
  6.2927 +
  6.2928 +ECN match support
  6.2929 +CONFIG_IP_NF_MATCH_ECN
  6.2930 +  This option adds a `ECN' match, which allows you to match against
  6.2931 +  the IPv4 and TCP header ECN fields.
  6.2932 +
  6.2933 +  If you want to compile it as a module, say M here and read
  6.2934 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2935 +
  6.2936 + 
  6.2937 +
  6.2938 +TOS match support
  6.2939 +CONFIG_IP_NF_MATCH_TOS
  6.2940 +  TOS matching allows you to match packets based on the Type Of
  6.2941 +  Service fields of the IP packet.
  6.2942 +
  6.2943 +  If you want to compile it as a module, say M here and read
  6.2944 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2945 +
  6.2946 +conntrack match support
  6.2947 +CONFIG_IP_NF_MATCH_CONNTRACK
  6.2948 +  This is a general conntrack match module, a superset of the state match.
  6.2949 +
  6.2950 +  It allows matching on additional conntrack information, which is
  6.2951 +  useful in complex configurations, such as NAT gateways with multiple
  6.2952 +  internet links or tunnels.
  6.2953 +
  6.2954 +  If you want to compile it as a module, say M here and read
  6.2955 +  Documentation/modules.txt.  If unsure, say `N'.
  6.2956 +
  6.2957 +
  6.2958 +Connection state match support
  6.2959 +CONFIG_IP_NF_MATCH_STATE
  6.2960 +  Connection state matching allows you to match packets based on their
  6.2961 +  relationship to a tracked connection (ie. previous packets).  This
  6.2962 +  is a powerful tool for packet classification.
  6.2963 +
  6.2964 +  If you want to compile it as a module, say M here and read
  6.2965 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2966 +
  6.2967 +Unclean match support
  6.2968 +CONFIG_IP_NF_MATCH_UNCLEAN
  6.2969 +  Unclean packet matching matches any strange or invalid packets, by
  6.2970 +  looking at a series of fields in the IP, TCP, UDP and ICMP headers.
  6.2971 +
  6.2972 +  If you want to compile it as a module, say M here and read
  6.2973 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2974 +
  6.2975 +Owner match support
  6.2976 +CONFIG_IP_NF_MATCH_OWNER
  6.2977 +  Packet owner matching allows you to match locally-generated packets
  6.2978 +  based on who created them: the user, group, process or session.
  6.2979 +
  6.2980 +  If you want to compile it as a module, say M here and read
  6.2981 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2982 +
  6.2983 +Packet filtering
  6.2984 +CONFIG_IP_NF_FILTER
  6.2985 +  Packet filtering defines a table `filter', which has a series of
  6.2986 +  rules for simple packet filtering at local input, forwarding and
  6.2987 +  local output.  See the man page for iptables(8).
  6.2988 +
  6.2989 +  If you want to compile it as a module, say M here and read
  6.2990 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.2991 +
  6.2992 +REJECT target support
  6.2993 +CONFIG_IP_NF_TARGET_REJECT
  6.2994 +  The REJECT target allows a filtering rule to specify that an ICMP
  6.2995 +  error should be issued in response to an incoming packet, rather
  6.2996 +  than silently being dropped.
  6.2997 +
  6.2998 +  If you want to compile it as a module, say M here and read
  6.2999 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3000 +
  6.3001 +MIRROR target support
  6.3002 +CONFIG_IP_NF_TARGET_MIRROR
  6.3003 +  The MIRROR target allows a filtering rule to specify that an
  6.3004 +  incoming packet should be bounced back to the sender.
  6.3005 +
  6.3006 +  If you want to compile it as a module, say M here and read
  6.3007 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3008 +
  6.3009 +Local NAT support
  6.3010 +CONFIG_IP_NF_NAT_LOCAL
  6.3011 +  This option enables support for NAT of locally originated connections. 
  6.3012 +  Enable this if you need to use destination NAT on connections
  6.3013 +  originating from local processes on the nat box itself.
  6.3014 +
  6.3015 +  Please note that you will need a recent version (>= 1.2.6a)
  6.3016 +  of the iptables userspace program in order to use this feature.
  6.3017 +  See <http://www.iptables.org/> for download instructions.
  6.3018 +
  6.3019 +  If unsure, say 'N'.
  6.3020 +
  6.3021 +
  6.3022 +Full NAT (Network Address Translation)
  6.3023 +CONFIG_IP_NF_NAT
  6.3024 +  The Full NAT option allows masquerading, port forwarding and other
  6.3025 +  forms of full Network Address Port Translation.  It is controlled by
  6.3026 +  the `nat' table in iptables: see the man page for iptables(8).
  6.3027 +
  6.3028 +  If you want to compile it as a module, say M here and read
  6.3029 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3030 +
  6.3031 +MASQUERADE target support
  6.3032 +CONFIG_IP_NF_TARGET_MASQUERADE
  6.3033 +  Masquerading is a special case of NAT: all outgoing connections are
  6.3034 +  changed to seem to come from a particular interface's address, and
  6.3035 +  if the interface goes down, those connections are lost.  This is
  6.3036 +  only useful for dialup accounts with dynamic IP address (ie. your IP
  6.3037 +  address will be different on next dialup).
  6.3038 +
  6.3039 +  If you want to compile it as a module, say M here and read
  6.3040 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3041 +
  6.3042 +Basic SNMP-ALG support
  6.3043 +CONFIG_IP_NF_NAT_SNMP_BASIC
  6.3044 +
  6.3045 +  This module implements an Application Layer Gateway (ALG) for
  6.3046 +  SNMP payloads.  In conjunction with NAT, it allows a network
  6.3047 +  management system to access multiple private networks with
  6.3048 +  conflicting addresses.  It works by modifying IP addresses
  6.3049 +  inside SNMP payloads to match IP-layer NAT mapping.
  6.3050 +
  6.3051 +  This is the "basic" form of SNMP-ALG, as described in RFC 2962
  6.3052 +
  6.3053 +  If you want to compile it as a module, say M here and read
  6.3054 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3055 +
  6.3056 +REDIRECT target support
  6.3057 +CONFIG_IP_NF_TARGET_REDIRECT
  6.3058 +  REDIRECT is a special case of NAT: all incoming connections are
  6.3059 +  mapped onto the incoming interface's address, causing the packets to
  6.3060 +  come to the local machine instead of passing through.  This is
  6.3061 +  useful for transparent proxies.
  6.3062 +
  6.3063 +  If you want to compile it as a module, say M here and read
  6.3064 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3065 +
  6.3066 +Packet mangling
  6.3067 +CONFIG_IP_NF_MANGLE
  6.3068 +  This option adds a `mangle' table to iptables: see the man page for
  6.3069 +  iptables(8).  This table is used for various packet alterations
  6.3070 +  which can effect how the packet is routed.
  6.3071 +
  6.3072 +  If you want to compile it as a module, say M here and read
  6.3073 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3074 +
  6.3075 +DSCP target support
  6.3076 +CONFIG_IP_NF_TARGET_DSCP
  6.3077 +  This option adds a `DSCP' target, which allows you to create rules in
  6.3078 +  the iptables mangle table. The selected packet has the DSCP field set
  6.3079 +  to the hex value provided on the command line; unlike the TOS target
  6.3080 +  which will only set the legal values within ip.h.
  6.3081 +
  6.3082 +  The DSCP field can be set to any value between 0x0 and 0x4f. It does
  6.3083 +  take into account that bits 6 and 7 are used by ECN.
  6.3084 +
  6.3085 +  If you want to compile it as a module, say M here and read
  6.3086 +  Documentation/modules.txt.  If unsure, say `N'.
  6.3087 +
  6.3088 + 
  6.3089 +
  6.3090 +ECN target support
  6.3091 +CONFIG_IP_NF_TARGET_ECN
  6.3092 +  This option adds a `ECN' target, which can be used in the iptables mangle
  6.3093 +  table.  
  6.3094 +
  6.3095 +  You can use this target to remove the ECN bits from the IPv4 header of
  6.3096 +  an IP packet.  This is particularly useful, if you need to work around
  6.3097 +  existing ECN blackholes on the internet, but don't want to disable
  6.3098 +  ECN support in general.
  6.3099 +
  6.3100 +  If you want to compile it as a module, say M here and read
  6.3101 +  Documentation/modules.txt.  If unsure, say `N'.
  6.3102 +
  6.3103 + 
  6.3104 +
  6.3105 +TOS target support
  6.3106 +CONFIG_IP_NF_TARGET_TOS
  6.3107 +  This option adds a `TOS' target, which allows you to create rules in
  6.3108 +  the `mangle' table which alter the Type Of Service field of an IP
  6.3109 +  packet prior to routing.
  6.3110 +
  6.3111 +  If you want to compile it as a module, say M here and read
  6.3112 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3113 +
  6.3114 +MARK target support
  6.3115 +CONFIG_IP_NF_TARGET_MARK
  6.3116 +  This option adds a `MARK' target, which allows you to create rules
  6.3117 +  in the `mangle' table which alter the netfilter mark (nfmark) field
  6.3118 +  associated with the packet prior to routing. This can change
  6.3119 +  the routing method (see `Use netfilter MARK value as routing
  6.3120 +  key') and can also be used by other subsystems to change their
  6.3121 +  behaviour.
  6.3122 +
  6.3123 +  If you want to compile it as a module, say M here and read
  6.3124 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3125 +
  6.3126 +TCPMSS target support
  6.3127 +CONFIG_IP_NF_TARGET_TCPMSS
  6.3128 +  This option adds a `TCPMSS' target, which allows you to alter the
  6.3129 +  MSS value of TCP SYN packets, to control the maximum size for that
  6.3130 +  connection (usually limiting it to your outgoing interface's MTU
  6.3131 +  minus 40).
  6.3132 +
  6.3133 +  This is used to overcome criminally braindead ISPs or servers which
  6.3134 +  block ICMP Fragmentation Needed packets.  The symptoms of this
  6.3135 +  problem are that everything works fine from your Linux
  6.3136 +  firewall/router, but machines behind it can never exchange large
  6.3137 +  packets:
  6.3138 +	1) Web browsers connect, then hang with no data received.
  6.3139 +	2) Small mail works fine, but large emails hang.
  6.3140 +	3) ssh works fine, but scp hangs after initial handshaking.
  6.3141 +
  6.3142 +  Workaround: activate this option and add a rule to your firewall
  6.3143 +  configuration like:
  6.3144 +
  6.3145 +        iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  6.3146 +		 -j TCPMSS --clamp-mss-to-pmtu
  6.3147 +
  6.3148 +  If you want to compile it as a module, say M here and read
  6.3149 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3150 +
  6.3151 +Helper match support
  6.3152 +CONFIG_IP_NF_MATCH_HELPER
  6.3153 +  Helper matching allows you to match packets in dynamic connections
  6.3154 +  tracked by a conntrack-helper, ie. ip_conntrack_ftp
  6.3155 +
  6.3156 +  If you want to compile it as a module, say M here and read
  6.3157 +  Documentation/modules.txt.  If unsure, say `Y'.
  6.3158 +
  6.3159 +TCPMSS match support
  6.3160 +CONFIG_IP_NF_MATCH_TCPMSS
  6.3161 +  This option adds a `tcpmss' match, which allows you to examine the
  6.3162 +  MSS value of TCP SYN packets, which control the maximum packet size
  6.3163 +  for that connection.
  6.3164 +
  6.3165 +  If you want to compile it as a module, say M here and read
  6.3166 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3167 +
  6.3168 +ULOG target support
  6.3169 +CONFIG_IP_NF_TARGET_ULOG
  6.3170 +  This option adds a `ULOG' target, which allows you to create rules in
  6.3171 +  any iptables table. The packet is passed to a userspace logging
  6.3172 +  daemon using netlink multicast sockets; unlike the LOG target
  6.3173 +  which can only be viewed through syslog.
  6.3174 +
  6.3175 +  The appropriate userspace logging daemon (ulogd) may be obtained from
  6.3176 +  <http://www.gnumonks.org/projects/ulogd>
  6.3177 +
  6.3178 +  If you want to compile it as a module, say M here and read
  6.3179 +  Documentation/modules.txt.  If unsure, say `N'.
  6.3180 +
  6.3181 +LOG target support
  6.3182 +CONFIG_IP_NF_TARGET_LOG
  6.3183 +  This option adds a `LOG' target, which allows you to create rules in
  6.3184 +  any iptables table which records the packet header to the syslog.
  6.3185 +
  6.3186 +  If you want to compile it as a module, say M here and read
  6.3187 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3188 +
  6.3189 +ipchains (2.2-style) support
  6.3190 +CONFIG_IP_NF_COMPAT_IPCHAINS
  6.3191 +  This option places ipchains (with masquerading and redirection
  6.3192 +  support) back into the kernel, using the new netfilter
  6.3193 +  infrastructure.  It is not recommended for new installations (see
  6.3194 +  `Packet filtering').  With this enabled, you should be able to use
  6.3195 +  the ipchains tool exactly as in 2.2 kernels.
  6.3196 +
  6.3197 +  If you want to compile it as a module, say M here and read
  6.3198 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3199 +
  6.3200 +ipfwadm (2.0-style) support
  6.3201 +CONFIG_IP_NF_COMPAT_IPFWADM
  6.3202 +  This option places ipfwadm (with masquerading and redirection
  6.3203 +  support) back into the kernel, using the new netfilter
  6.3204 +  infrastructure.  It is not recommended for new installations (see
  6.3205 +  `Packet filtering').  With this enabled, you should be able to use
  6.3206 +  the ipfwadm tool exactly as in 2.0 kernels.
  6.3207 +
  6.3208 +  If you want to compile it as a module, say M here and read
  6.3209 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3210 +
  6.3211 +EUI64 address check (EXPERIMENTAL)
  6.3212 +CONFIG_IP6_NF_MATCH_EUI64
  6.3213 +  This module performs checking on the IPv6 source address
  6.3214 +  Compares the last 64 bits with the EUI64 (delivered
  6.3215 +  from the MAC address) address
  6.3216 +
  6.3217 +  If you want to compile it as a module, say M here and read
  6.3218 +  Documentation/modules.txt.  If unsure, say `N'.
  6.3219 +
  6.3220 +MAC address match support
  6.3221 +CONFIG_IP6_NF_MATCH_MAC
  6.3222 +  mac matching allows you to match packets based on the source
  6.3223 +  Ethernet address of the packet.
  6.3224 +
  6.3225 +  If you want to compile it as a module, say M here and read
  6.3226 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3227 +
  6.3228 +length match support
  6.3229 +CONFIG_IP6_NF_MATCH_LENGTH
  6.3230 +  This option allows you to match the length of a packet against a
  6.3231 +  specific value or range of values.
  6.3232 +
  6.3233 +  If you want to compile it as a module, say M here and read
  6.3234 +  Documentation/modules.txt.  If unsure, say `N'.
  6.3235 +
  6.3236 +Netfilter MARK match support
  6.3237 +CONFIG_IP6_NF_MATCH_MARK
  6.3238 +  Netfilter mark matching allows you to match packets based on the
  6.3239 +  `nfmark' value in the packet.  This can be set by the MARK target
  6.3240 +  (see below).
  6.3241 +
  6.3242 +  If you want to compile it as a module, say M here and read
  6.3243 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3244 +
  6.3245 +Multiple port match support
  6.3246 +CONFIG_IP6_NF_MATCH_MULTIPORT
  6.3247 +  Multiport matching allows you to match TCP or UDP packets based on
  6.3248 +  a series of source or destination ports: normally a rule can only
  6.3249 +  match a single range of ports.
  6.3250 +
  6.3251 +  If you want to compile it as a module, say M here and read
  6.3252 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3253 +
  6.3254 +IPV6 queue handler (EXPERIMENTAL)
  6.3255 +CONFIG_IP6_NF_QUEUE
  6.3256 +
  6.3257 +  This option adds a queue handler to the kernel for IPv6
  6.3258 +  packets which lets us to receive the filtered packets
  6.3259 +  with QUEUE target using libiptc as we can do with
  6.3260 +  the IPv4 now.
  6.3261 +
  6.3262 +  (C) Fernando Anton 2001
  6.3263 +  IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
  6.3264 +  Universidad Carlos III de Madrid
  6.3265 +  Universidad Politecnica de Alcala de Henares
  6.3266 +  email: fanton@it.uc3m.es
  6.3267 +
  6.3268 +  If you want to compile it as a module, say M here and read
  6.3269 +  Documentation/modules.txt. If unsure, say `N'.
  6.3270 +
  6.3271 +Owner match support
  6.3272 +CONFIG_IP6_NF_MATCH_OWNER
  6.3273 +  Packet owner matching allows you to match locally-generated packets
  6.3274 +  based on who created them: the user, group, process or session.
  6.3275 +
  6.3276 +  If you want to compile it as a module, say M here and read
  6.3277 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3278 +
  6.3279 +Packet filtering
  6.3280 +CONFIG_IP6_NF_FILTER
  6.3281 +  Packet filtering defines a table `filter', which has a series of
  6.3282 +  rules for simple packet filtering at local input, forwarding and
  6.3283 +  local output.  See the man page for iptables(8).
  6.3284 +
  6.3285 +  If you want to compile it as a module, say M here and read
  6.3286 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3287 +
  6.3288 +Packet mangling
  6.3289 +CONFIG_IP6_NF_MANGLE
  6.3290 +  This option adds a `mangle' table to iptables: see the man page for
  6.3291 +  iptables(8).  This table is used for various packet alterations
  6.3292 +  which can effect how the packet is routed.
  6.3293 +
  6.3294 +  If you want to compile it as a module, say M here and read
  6.3295 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3296 +
  6.3297 +MARK target support
  6.3298 +CONFIG_IP6_NF_TARGET_MARK
  6.3299 +  This option adds a `MARK' target, which allows you to create rules
  6.3300 +  in the `mangle' table which alter the netfilter mark (nfmark) field
  6.3301 +  associated with the packet packet prior to routing. This can change
  6.3302 +  the routing method (see `Use netfilter MARK value as routing
  6.3303 +  key') and can also be used by other subsystems to change their
  6.3304 +  behaviour.
  6.3305 +
  6.3306 +  If you want to compile it as a module, say M here and read
  6.3307 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3308 +
  6.3309 +ARP tables support
  6.3310 +CONFIG_IP_NF_ARPTABLES
  6.3311 +  arptables is a general, extensible packet identification framework.
  6.3312 +  The ARP packet filtering and mangling (manipulation)subsystems
  6.3313 +  use this: say Y or M here if you want to use either of those.
  6.3314 +
  6.3315 +  If you want to compile it as a module, say M here and read
  6.3316 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3317 +
  6.3318 +ARP packet filtering
  6.3319 +CONFIG_IP_NF_ARPFILTER
  6.3320 +  ARP packet filtering defines a table `filter', which has a series of
  6.3321 +  rules for simple ARP packet filtering at local input and
  6.3322 +  local output.  See the man page for arptables(8).
  6.3323 +
  6.3324 +  If you want to compile it as a module, say M here and read
  6.3325 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3326 +
  6.3327 +ARP payload mangling
  6.3328 +CONFIG_IP_NF_ARP_MANGLE
  6.3329 +  Allows altering the ARP packet payload: source and destination
  6.3330 +  hardware and network addresses.
  6.3331 +
  6.3332 +  If you want to compile it as a module, say M here and read
  6.3333 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3334 +
  6.3335 +TCP Explicit Congestion Notification support
  6.3336 +CONFIG_INET_ECN
  6.3337 +  Explicit Congestion Notification (ECN) allows routers to notify
  6.3338 +  clients about network congestion, resulting in fewer dropped packets
  6.3339 +  and increased network performance.  This option adds ECN support to
  6.3340 +  the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
  6.3341 +  which allows ECN support to be disabled at runtime.
  6.3342 +
  6.3343 +  Note that, on the Internet, there are many broken firewalls which
  6.3344 +  refuse connections from ECN-enabled machines, and it may be a while
  6.3345 +  before these firewalls are fixed.  Until then, to access a site
  6.3346 +  behind such a firewall (some of which are major sites, at the time
  6.3347 +  of this writing) you will have to disable this option, either by
  6.3348 +  saying N now or by using the sysctl.
  6.3349 +
  6.3350 +  If in doubt, say N.
  6.3351 +
  6.3352 +IPv6 tables support (required for filtering/masq/NAT)
  6.3353 +CONFIG_IP6_NF_IPTABLES
  6.3354 +  ip6tables is a general, extensible packet identification framework.
  6.3355 +  Currently only the packet filtering and packet mangling subsystem
  6.3356 +  for IPv6 use this, but connection tracking is going to follow.
  6.3357 +  Say 'Y' or 'M' here if you want to use either of those.
  6.3358 +
  6.3359 +  If you want to compile it as a module, say M here and read
  6.3360 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3361 +
  6.3362 +IPv6 limit match support
  6.3363 +CONFIG_IP6_NF_MATCH_LIMIT
  6.3364 +  limit matching allows you to control the rate at which a rule can be
  6.3365 +  matched: mainly useful in combination with the LOG target ("LOG
  6.3366 +  target support", below) and to avoid some Denial of Service attacks.
  6.3367 +
  6.3368 +  If you want to compile it as a module, say M here and read
  6.3369 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3370 +
  6.3371 +LOG target support
  6.3372 +CONFIG_IP6_NF_TARGET_LOG
  6.3373 +  This option adds a `LOG' target, which allows you to create rules in
  6.3374 +  any iptables table which records the packet header to the syslog.
  6.3375 +
  6.3376 +  If you want to compile it as a module, say M here and read
  6.3377 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  6.3378 +
  6.3379 +IP: virtual server support
  6.3380 +CONFIG_IP_VS
  6.3381 +  IP Virtual Server support will let you build a high-performance
  6.3382 +  virtual server based on cluster of two or more real servers. This
  6.3383 +  option must be enabled for at least one of the clustered computers
  6.3384 +  that will take care of intercepting incomming connections to a
  6.3385 +  single IP address and scheduling them to real servers.
  6.3386 +
  6.3387 +  Three request dispatching techniques are implemented, they are
  6.3388 +  virtual server via NAT, virtual server via tunneling and virtual
  6.3389 +  server via direct routing. The several scheduling algorithms can
  6.3390 +  be used to choose which server the connection is directed to,
  6.3391 +  thus load balancing can be achieved among the servers.  For more
  6.3392 +  information and its administration program, please visit the
  6.3393 +  following URL:
  6.3394 +	http://www.linuxvirtualserver.org/
  6.3395 +
  6.3396 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3397 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3398 +  unsure, say N.
  6.3399 +
  6.3400 +IP virtual server debugging
  6.3401 +CONFIG_IP_VS_DEBUG
  6.3402 +  Say Y here if you want to get additional messages useful in
  6.3403 +  debugging the IP virtual server code. You can change the debug
  6.3404 +  level in /proc/sys/net/ipv4/vs/debug_level
  6.3405 +
  6.3406 +IPVS connection hash table size (the Nth power of 2)
  6.3407 +CONFIG_IP_VS_TAB_BITS
  6.3408 +  The IPVS connection hash table uses the chaining scheme to handle
  6.3409 +  hash collisions. Using a big IPVS connection hash table will greatly
  6.3410 +  reduce conflicts when there are hundreds of thousands of connections
  6.3411 +  in the hash table.
  6.3412 +
  6.3413 +  Note the table size must be power of 2. The table size will be the
  6.3414 +  value of 2 to the your input number power. The number to choose is
  6.3415 +  from 8 to 20, the default number is 12, which means the table size
  6.3416 +  is 4096. Don't input the number too small, otherwise you will lose
  6.3417 +  performance on it. You can adapt the table size yourself, according
  6.3418 +  to your virtual server application. It is good to set the table size
  6.3419 +  not far less than the number of connections per second multiplying
  6.3420 +  average lasting time of connection in the table.  For example, your
  6.3421 +  virtual server gets 200 connections per second, the connection lasts
  6.3422 +  for 200 seconds in average in the connection table, the table size
  6.3423 +  should be not far less than 200x200, it is good to set the table
  6.3424 +  size 32768 (2**15).
  6.3425 +
  6.3426 +  Another note that each connection occupies 128 bytes effectively and
  6.3427 +  each hash entry uses 8 bytes, so you can estimate how much memory is
  6.3428 +  needed for your box.
  6.3429 +
  6.3430 +IPVS: round-robin scheduling
  6.3431 +CONFIG_IP_VS_RR
  6.3432 +  The robin-robin scheduling algorithm simply directs network
  6.3433 +  connections to different real servers in a round-robin manner.
  6.3434 +
  6.3435 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3436 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3437 +  unsure, say N.
  6.3438 +
  6.3439 +IPVS: weighted round-robin scheduling
  6.3440 +CONFIG_IP_VS_WRR
  6.3441 +  The weighted robin-robin scheduling algorithm directs network
  6.3442 +  connections to different real servers based on server weights
  6.3443 +  in a round-robin manner. Servers with higher weights receive
  6.3444 +  new connections first than those with less weights, and servers
  6.3445 +  with higher weights get more connections than those with less
  6.3446 +  weights and servers with equal weights get equal connections.
  6.3447 +
  6.3448 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3449 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3450 +  unsure, say N.
  6.3451 +
  6.3452 +IPVS: least-connection scheduling
  6.3453 +CONFIG_IP_VS_LC
  6.3454 +  The least-connection scheduling algorithm directs network
  6.3455 +  connections to the server with the least number of active 
  6.3456 +  connections.
  6.3457 +
  6.3458 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3459 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3460 +  unsure, say N.
  6.3461 +
  6.3462 +IPVS: weighted least-connection scheduling
  6.3463 +CONFIG_IP_VS_WLC
  6.3464 +  The weighted least-connection scheduling algorithm directs network
  6.3465 +  connections to the server with the least active connections
  6.3466 +  normalized by the server weight.
  6.3467 +
  6.3468 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3469 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3470 +  unsure, say N.
  6.3471 +
  6.3472 +IPVS: locality-based least-connection scheduling
  6.3473 +CONFIG_IP_VS_LBLC
  6.3474 +  The locality-based least-connection scheduling algorithm is for
  6.3475 +  destination IP load balancing. It is usually used in cache cluster.
  6.3476 +  This algorithm usually directs packet destined for an IP address to
  6.3477 +  its server if the server is alive and under load. If the server is
  6.3478 +  overloaded (its active connection numbers is larger than its weight)
  6.3479 +  and there is a server in its half load, then allocate the weighted
  6.3480 +  least-connection server to this IP address.
  6.3481 +
  6.3482 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3483 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3484 +  unsure, say N.
  6.3485 +
  6.3486 +IPVS: locality-based least-connection with replication scheduling
  6.3487 +CONFIG_IP_VS_LBLCR
  6.3488 +  The locality-based least-connection with replication scheduling
  6.3489 +  algorithm is also for destination IP load balancing. It is 
  6.3490 +  usually used in cache cluster. It differs from the LBLC scheduling
  6.3491 +  as follows: the load balancer maintains mappings from a target
  6.3492 +  to a set of server nodes that can serve the target. Requests for
  6.3493 +  a target are assigned to the least-connection node in the target's
  6.3494 +  server set. If all the node in the server set are over loaded,
  6.3495 +  it picks up a least-connection node in the cluster and adds it
  6.3496 +  in the sever set for the target. If the server set has not been
  6.3497 +  modified for the specified time, the most loaded node is removed
  6.3498 +  from the server set, in order to avoid high degree of replication.
  6.3499 +
  6.3500 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3501 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3502 +  unsure, say N.
  6.3503 +
  6.3504 +IPVS: destination hashing scheduling
  6.3505 +CONFIG_IP_VS_DH
  6.3506 +  The destination hashing scheduling algorithm assigns network
  6.3507 +  connections to the servers through looking up a statically assigned
  6.3508 +  hash table by their destination IP addresses.
  6.3509 +
  6.3510 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3511 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3512 +  unsure, say N.
  6.3513 +
  6.3514 +IPVS: source hashing scheduling
  6.3515 +CONFIG_IP_VS_SH
  6.3516 +  The source hashing scheduling algorithm assigns network
  6.3517 +  connections to the servers through looking up a statically assigned
  6.3518 +  hash table by their source IP addresses.
  6.3519 +
  6.3520 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3521 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3522 +  unsure, say N.
  6.3523 +
  6.3524 +IPVS: shortest expected delay scheduling
  6.3525 +CONFIG_IP_VS_SED
  6.3526 +  The shortest expected delay scheduling algorithm assigns network
  6.3527 +  connections to the server with the shortest expected delay. The 
  6.3528 +  expected delay that the job will experience is (Ci + 1) / Ui if 
  6.3529 +  sent to the ith server, in which Ci is the number of connections
  6.3530 +  on the the ith server and Ui is the fixed service rate (weight)
  6.3531 +  of the ith server.
  6.3532 +
  6.3533 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3534 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3535 +  unsure, say N.
  6.3536 +
  6.3537 +IPVS: never queue scheduling
  6.3538 +CONFIG_IP_VS_NQ
  6.3539 +  The never queue scheduling algorithm adopts a two-speed model.
  6.3540 +  When there is an idle server available, the job will be sent to
  6.3541 +  the idle server, instead of waiting for a fast one. When there
  6.3542 +  is no idle server available, the job will be sent to the server
  6.3543 +  that minimize its expected delay (The Shortest Expected Delay
  6.3544 +  scheduling algorithm).
  6.3545 +
  6.3546 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3547 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3548 +  unsure, say N.
  6.3549 +
  6.3550 +IPVS: FTP protocol helper
  6.3551 +CONFIG_IP_VS_FTP
  6.3552 +  FTP is a protocol that transfers IP address and/or port number in
  6.3553 +  the payload. In the virtual server via Network Address Translation,
  6.3554 +  the IP address and port number of real servers cannot be sent to
  6.3555 +  clients in ftp connections directly, so FTP protocol helper is
  6.3556 +  required for tracking the connection and mangling it back to that of
  6.3557 +  virtual service.
  6.3558 +
  6.3559 +  If you want to compile it in kernel, say Y. If you want to compile
  6.3560 +  it as a module, say M here and read Documentation/modules.txt. If
  6.3561 +  unsure, say N.
  6.3562 +
  6.3563 +AH/ESP match support (EXPERIMENTAL)
  6.3564 +CONFIG_IP6_NF_MATCH_AHESP
  6.3565 +  This module allows one to match AH and ESP packets.
  6.3566 +
  6.3567 +  If you want to compile it as a module, say M here and read
  6.3568 +  <file:Documentation/modules.txt>.  The modules will be called
  6.3569 +  ip6t_ah.o and ip6t_esp.o.
  6.3570 +
  6.3571 +  If unsure, say 'N'.
  6.3572 +
  6.3573 +Routing header match support
  6.3574 +CONFIG_IP6_NF_MATCH_RT
  6.3575 +  rt matching allows you to match packets based on the routing
  6.3576 +  header of the packet.
  6.3577 +
  6.3578 +  If you want to compile it as a module, say M here and read
  6.3579 +  <file:Documentation/modules.txt>.  The module will be called
  6.3580 +  ip6t_rt.o.
  6.3581 +
  6.3582 +  If unsure, say 'N'.
  6.3583 +
  6.3584 +Hop-by-hop and Dst opts header match support
  6.3585 +CONFIG_IP6_NF_MATCH_OPTS
  6.3586 +  This allows one to match packets based on the hop-by-hop
  6.3587 +  and destination options headers of a packet.
  6.3588 +
  6.3589 +  If you want to compile it as a module, say M here and read
  6.3590 +  <file:Documentation/modules.txt>.  The modules will be called
  6.3591 +  ip6t_hbh.o and ip6t_dst.o.
  6.3592 +
  6.3593 +  If unsure, say 'N'.
  6.3594 +
  6.3595 +Fragmentation header match support
  6.3596 +CONFIG_IP6_NF_MATCH_FRAG
  6.3597 +  frag matching allows you to match packets based on the fragmentation
  6.3598 +  header of the packet.
  6.3599 +
  6.3600 +  If you want to compile it as a module, say M here and read
  6.3601 +  <file:Documentation/modules.txt>.  The module will be called
  6.3602 +  ip6t_frag.o.
  6.3603 +
  6.3604 +  If unsure, say 'N'.
  6.3605 +
  6.3606 +HL match support
  6.3607 +CONFIG_IP6_NF_MATCH_HL
  6.3608 +  HL matching allows you to match packets based on the hop
  6.3609 +  limit of the packet.
  6.3610 +
  6.3611 +  If you want to compile it as a module, say M here and read
  6.3612 +  <file:Documentation/modules.txt>.  The module will be called
  6.3613 +  ip6t_hl.o.
  6.3614 +
  6.3615 +  If unsure, say 'N'.
  6.3616 +
  6.3617 +IPv6 Extension Headers Match (EXPERIMENTAL)
  6.3618 +CONFIG_IP6_NF_MATCH_IPV6HEADER
  6.3619 +  This module allows one to match packets based upon
  6.3620 +  the ipv6 extension headers.
  6.3621 +
  6.3622 +  If you want to compile it as a module, say M here and read
  6.3623 +  <file:Documentation/modules.txt>.  The module will be called
  6.3624 +  ip6t_ipv6header.o.
  6.3625 +
  6.3626 +  If unsure, say 'N'.
  6.3627 +
  6.3628 +SYN flood protection
  6.3629 +CONFIG_SYN_COOKIES
  6.3630 +  Normal TCP/IP networking is open to an attack known as "SYN
  6.3631 +  flooding". This denial-of-service attack prevents legitimate remote
  6.3632 +  users from being able to connect to your computer during an ongoing
  6.3633 +  attack and requires very little work from the attacker, who can
  6.3634 +  operate from anywhere on the Internet.
  6.3635 +
  6.3636 +  SYN cookies provide protection against this type of attack. If you
  6.3637 +  say Y here, the TCP/IP stack will use a cryptographic challenge
  6.3638 +  protocol known as "SYN cookies" to enable legitimate users to
  6.3639 +  continue to connect, even when your machine is under attack. There
  6.3640 +  is no need for the legitimate users to change their TCP/IP software;
  6.3641 +  SYN cookies work transparently to them. For technical information
  6.3642 +  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
  6.3643 +
  6.3644 +  If you are SYN flooded, the source address reported by the kernel is
  6.3645 +  likely to have been forged by the attacker; it is only reported as
  6.3646 +  an aid in tracing the packets to their actual source and should not
  6.3647 +  be taken as absolute truth.
  6.3648 +
  6.3649 +  SYN cookies may prevent correct error reporting on clients when the
  6.3650 +  server is really overloaded. If this happens frequently better turn
  6.3651 +  them off.
  6.3652 +
  6.3653 +  If you say Y here, note that SYN cookies aren't enabled by default;
  6.3654 +  you can enable them by saying Y to "/proc file system support" and
  6.3655 +  "Sysctl support" below and executing the command
  6.3656 +
  6.3657 +    echo 1 >/proc/sys/net/ipv4/tcp_syncookies
  6.3658 +
  6.3659 +  at boot time after the /proc file system has been mounted.
  6.3660 +
  6.3661 +  If unsure, say N.
  6.3662 +
  6.3663 +# Choice: alphatype
  6.3664 +Alpha system type
  6.3665 +CONFIG_ALPHA_GENERIC
  6.3666 +  This is the system type of your hardware.  A "generic" kernel will
  6.3667 +  run on any supported Alpha system. However, if you configure a
  6.3668 +  kernel for your specific system, it will be faster and smaller.
  6.3669 +
  6.3670 +  To find out what type of Alpha system you have, you may want to
  6.3671 +  check out the Linux/Alpha FAQ, accessible on the WWW from
  6.3672 +  <http://www.alphalinux.org/>. In summary:
  6.3673 +
  6.3674 +  Alcor/Alpha-XLT     AS 600
  6.3675 +  Alpha-XL            XL-233, XL-266
  6.3676 +  AlphaBook1          Alpha laptop
  6.3677 +  Avanti              AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
  6.3678 +  Cabriolet           AlphaPC64, AlphaPCI64
  6.3679 +  DP264               DP264
  6.3680 +  EB164               EB164 21164 evaluation board
  6.3681 +  EB64+               EB64+ 21064 evaluation board
  6.3682 +  EB66                EB66 21066 evaluation board
  6.3683 +  EB66+               EB66+ 21066 evaluation board
  6.3684 +  Jensen              DECpc 150, DEC 2000 model 300,
  6.3685 +                      DEC 2000 model 500
  6.3686 +  LX164               AlphaPC164-LX
  6.3687 +  Miata               Personal Workstation 433a, 433au, 500a,
  6.3688 +                      500au, 600a, or 600au
  6.3689 +  Mikasa              AS 1000
  6.3690 +  Noname              AXPpci33, UDB (Multia)
  6.3691 +  Noritake            AS 1000A, AS 600A, AS 800
  6.3692 +  PC164               AlphaPC164
  6.3693 +  Rawhide             AS 1200, AS 4000, AS 4100
  6.3694 +  Ruffian             RPX164-2, AlphaPC164-UX, AlphaPC164-BX
  6.3695 +  SX164               AlphaPC164-SX
  6.3696 +  Sable               AS 2000, AS 2100
  6.3697 +  Shark		      DS 20L
  6.3698 +  Takara              Takara
  6.3699 +  Titan               Privateer
  6.3700 +  Wildfire            AlphaServer GS 40/80/160/320
  6.3701 +
  6.3702 +  If you don't know what to do, choose "generic".
  6.3703 +
  6.3704 +# Most of the information on these variants is from
  6.3705 +# <http://www.alphalinux.org/docs/alpha-howto.html>
  6.3706 +Alcor/Alpha-XLT
  6.3707 +CONFIG_ALPHA_ALCOR
  6.3708 +  For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
  6.3709 +  slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
  6.3710 +  Address, CIA) - a 383 pin plastic PGA).  It provides a DRAM
  6.3711 +  controller (256-bit memory bus) and a PCI interface.  It also does
  6.3712 +  all the work required to support an external Bcache and to maintain
  6.3713 +  memory coherence when a PCI device DMAs into (or out of) memory.
  6.3714 +
  6.3715 +Alpha-XL
  6.3716 +CONFIG_ALPHA_XL
  6.3717 +  XL-233 and XL-266-based Alpha systems.
  6.3718 +
  6.3719 +AlphaBook1
  6.3720 +CONFIG_ALPHA_BOOK1
  6.3721 +  Dec AlphaBook1/Burns Alpha-based laptops.
  6.3722 +
  6.3723 +Avanti
  6.3724 +CONFIG_ALPHA_AVANTI
  6.3725 +  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
  6.3726 +  Alphas. Info at
  6.3727 +  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
  6.3728 +
  6.3729 +Cabriolet
  6.3730 +CONFIG_ALPHA_CABRIOLET
  6.3731 +  Cabriolet AlphaPC64, AlphaPCI64 systems.  Derived from EB64+ but now
  6.3732 +  baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
  6.3733 +  slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
  6.3734 +  Bcache SIMMs.  Requires power supply with 3.3V output.
  6.3735 +
  6.3736 +DP264
  6.3737 +CONFIG_ALPHA_DP264
  6.3738 +  Various 21264 systems with the tsunami core logic chipset.
  6.3739 +  API Networks: 264DP, UP2000(+), CS20;
  6.3740 +  Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
  6.3741 +
  6.3742 +EB164
  6.3743 +CONFIG_ALPHA_EB164
  6.3744 +  EB164 21164 evaluation board from DEC.  Uses 21164 and ALCOR.  Has
  6.3745 +  ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
  6.3746 +  shared with an ISA slot) and 2 32-bit PCI slots.  Uses plus-in
  6.3747 +  Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
  6.3748 +  MOUSE (PS2 style), RTC/NVRAM.  Boot ROM is Flash.  PC-AT-sized
  6.3749 +  motherboard.  Requires power supply with 3.3V output.
  6.3750 +
  6.3751 +EB64+
  6.3752 +CONFIG_ALPHA_EB64P
  6.3753 +  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,
  6.3754 +  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
  6.3755 +  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
  6.3756 +  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
  6.3757 +  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.
  6.3758 +  Runs from standard PC power supply.
  6.3759 +
  6.3760 +EB66
  6.3761 +CONFIG_ALPHA_EB66
  6.3762 +  A Digital DS group board.  Uses 21066 or 21066A.  I/O sub-system is
  6.3763 +  identical to EB64+.  Baby PC-AT size.  Runs from standard PC power
  6.3764 +  supply.  The EB66 schematic was published as a marketing poster
  6.3765 +  advertising the 21066 as "the first microprocessor in the world with
  6.3766 +  embedded PCI".
  6.3767 +
  6.3768 +EB66+
  6.3769 +CONFIG_ALPHA_EB66P
  6.3770 +  Later variant of the EB66 board.
  6.3771 +
  6.3772 +Eiger
  6.3773 +CONFIG_ALPHA_EIGER
  6.3774 +  Apparently an obscure OEM single-board computer based on the
  6.3775 +  Typhoon/Tsunami chipset family. Information on it is scanty.
  6.3776 +
  6.3777 +Jensen
  6.3778 +CONFIG_ALPHA_JENSEN
  6.3779 +  DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
  6.3780 +  of the first-generation Alpha systems. A number of these systems
  6.3781 +  seem to be available on the second- hand market. The Jensen is a
  6.3782 +  floor-standing tower system which originally used a 150MHz 21064 It
  6.3783 +  used programmable logic to interface a 486 EISA I/O bridge to the
  6.3784 +  CPU.
  6.3785 +
  6.3786 +LX164
  6.3787 +CONFIG_ALPHA_LX164
  6.3788 +  A technical overview of this board is available at
  6.3789 +  <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
  6.3790 +
  6.3791 +Miata
  6.3792 +CONFIG_ALPHA_MIATA
  6.3793 +  The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
  6.3794 +  or 600au).  There is an Installation HOWTO for this hardware at
  6.3795 +  <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
  6.3796 +
  6.3797 +Mikasa
  6.3798 +CONFIG_ALPHA_MIKASA
  6.3799 +  AlphaServer 1000-based Alpha systems.
  6.3800 +
  6.3801 +Nautilus
  6.3802 +CONFIG_ALPHA_NAUTILUS
  6.3803 +  Alpha systems based on the AMD 751 & ALI 1543C chipsets.
  6.3804 +
  6.3805 +Noname
  6.3806 +CONFIG_ALPHA_NONAME
  6.3807 +  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
  6.3808 +  UDB).  This design was produced by Digital's Technical OEM (TOEM)
  6.3809 +  group. It uses the 21066 processor running at 166MHz or 233MHz. It
  6.3810 +  is a baby-AT size, and runs from a standard PC power supply. It has
  6.3811 +  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
  6.3812 +  2 versions, with either PS/2 or large DIN connectors for the
  6.3813 +  keyboard.
  6.3814 +
  6.3815 +Noritake
  6.3816 +CONFIG_ALPHA_NORITAKE
  6.3817 +  AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
  6.3818 +  systems.
  6.3819 +
  6.3820 +Rawhide
  6.3821 +CONFIG_ALPHA_RAWHIDE
  6.3822 +  AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
  6.3823 +  See HOWTO at
  6.3824 +  <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
  6.3825 +
  6.3826 +Ruffian
  6.3827 +CONFIG_ALPHA_RUFFIAN
  6.3828 +  Samsung APC164UX.  There is a page on known problems and workarounds
  6.3829 +  at <http://www.alphalinux.org/faq/FAQ-11.html>.
  6.3830 +
  6.3831 +Sable
  6.3832 +CONFIG_ALPHA_SABLE
  6.3833 +  Digital AlphaServer 2000 and 2100-based systems.
  6.3834 +
  6.3835 +Takara
  6.3836 +CONFIG_ALPHA_TAKARA
  6.3837 +  Alpha 11164-based OEM single-board computer.
  6.3838 +
  6.3839 +Wildfire
  6.3840 +CONFIG_ALPHA_WILDFIRE
  6.3841 +  AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
  6.3842 +
  6.3843 +EV5 CPU daughtercard (model 5/xxx)
  6.3844 +CONFIG_ALPHA_PRIMO
  6.3845 +  Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
  6.3846 +
  6.3847 +EV5 CPU(s) (model 5/xxx)
  6.3848 +CONFIG_ALPHA_GAMMA
  6.3849 +  Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
  6.3850 +
  6.3851 +EV67 (or later) CPU (speed > 600MHz)?
  6.3852 +CONFIG_ALPHA_EV67
  6.3853 +  Is this a machine based on the EV67 core?  If in doubt, select N here
  6.3854 +  and the machine will be treated as an EV6.
  6.3855 +
  6.3856 +Use SRM as bootloader
  6.3857 +CONFIG_ALPHA_SRM
  6.3858 +  There are two different types of booting firmware on Alphas: SRM,
  6.3859 +  which is command line driven, and ARC, which uses menus and arrow
  6.3860 +  keys. Details about the Linux/Alpha booting process are contained in
  6.3861 +  the Linux/Alpha FAQ, accessible on the WWW from
  6.3862 +  <http://www.alphalinux.org/>.
  6.3863 +
  6.3864 +  The usual way to load Linux on an Alpha machine is to use MILO
  6.3865 +  (a bootloader that lets you pass command line parameters to the
  6.3866 +  kernel just like lilo does for the x86 architecture) which can be
  6.3867 +  loaded either from ARC or can be installed directly as a permanent
  6.3868 +  firmware replacement from floppy (which requires changing a certain
  6.3869 +  jumper on the motherboard). If you want to do either of these, say N
  6.3870 +  here. If MILO doesn't work on your system (true for Jensen
  6.3871 +  motherboards), you can bypass it altogether and boot Linux directly
  6.3872 +  from an SRM console; say Y here in order to do that. Note that you
  6.3873 +  won't be able to boot from an IDE disk using old versions of SRM.
  6.3874 +
  6.3875 +  If unsure, say N.
  6.3876 +
  6.3877 +Legacy kernel start address
  6.3878 +CONFIG_ALPHA_LEGACY_START_ADDRESS
  6.3879 +  The 2.4 kernel changed the kernel start address from 0x310000
  6.3880 +  to 0x810000 to make room for the Wildfire's larger SRM console.
  6.3881 +
  6.3882 +  If you're using aboot 0.7 or later, the bootloader will examine the
  6.3883 +  ELF headers to determine where to transfer control. Unfortunately,
  6.3884 +  most older bootloaders -- APB or MILO -- hardcoded the kernel start
  6.3885 +  address rather than examining the ELF headers, and the result is a
  6.3886 +  hard lockup.
  6.3887 +
  6.3888 +  Say Y if you have a broken bootloader.  Say N if you do not, or if
  6.3889 +  you wish to run on Wildfire.
  6.3890 +
  6.3891 +Large VMALLOC support
  6.3892 +CONFIG_ALPHA_LARGE_VMALLOC
  6.3893 +  Process creation and other aspects of virtual memory management can
  6.3894 +  be streamlined if we restrict the kernel to one PGD for all vmalloc
  6.3895 +  allocations.  This equates to about 8GB.
  6.3896 +
  6.3897 +  Under normal circumstances, this is so far and above what is needed
  6.3898 +  as to be laughable.  However, there are certain applications (such
  6.3899 +  as benchmark-grade in-kernel web serving) that can make use of as
  6.3900 +  much vmalloc space as is available.
  6.3901 +
  6.3902 +  Say N unless you know you need gobs and gobs of vmalloc space.
  6.3903 +
  6.3904 +Non-standard serial port support
  6.3905 +CONFIG_SERIAL_NONSTANDARD
  6.3906 +  Say Y here if you have any non-standard serial boards -- boards
  6.3907 +  which aren't supported using the standard "dumb" serial driver.
  6.3908 +  This includes intelligent serial boards such as Cyclades,
  6.3909 +  Digiboards, etc. These are usually used for systems that need many
  6.3910 +  serial ports because they serve many terminals or dial-in
  6.3911 +  connections.
  6.3912 +
  6.3913 +  Note that the answer to this question won't directly affect the
  6.3914 +  kernel: saying N will just cause the configurator to skip all
  6.3915 +  the questions about non-standard serial boards.
  6.3916 +
  6.3917 +  Most people can say N here.
  6.3918 +
  6.3919 +Extended dumb serial driver options
  6.3920 +CONFIG_SERIAL_EXTENDED
  6.3921 +  If you wish to use any non-standard features of the standard "dumb"
  6.3922 +  driver, say Y here. This includes HUB6 support, shared serial
  6.3923 +  interrupts, special multiport support, support for more than the
  6.3924 +  four COM 1/2/3/4 boards, etc.
  6.3925 +
  6.3926 +  Note that the answer to this question won't directly affect the
  6.3927 +  kernel: saying N will just cause the configurator to skip all
  6.3928 +  the questions about serial driver options. If unsure, say N.
  6.3929 +
  6.3930 +Support more than 4 serial ports
  6.3931 +CONFIG_SERIAL_MANY_PORTS
  6.3932 +  Say Y here if you have dumb serial boards other than the four
  6.3933 +  standard COM 1/2/3/4 ports. This may happen if you have an AST
  6.3934 +  FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
  6.3935 +  from <http://www.tldp.org/docs.html#howto>), or other custom
  6.3936 +  serial port hardware which acts similar to standard serial port
  6.3937 +  hardware. If you only use the standard COM 1/2/3/4 ports, you can
  6.3938 +  say N here to save some memory. You can also say Y if you have an
  6.3939 +  "intelligent" multiport card such as Cyclades, Digiboards, etc.
  6.3940 +
  6.3941 +Support for sharing serial interrupts
  6.3942 +CONFIG_SERIAL_SHARE_IRQ
  6.3943 +  Some serial boards have hardware support which allows multiple dumb
  6.3944 +  serial ports on the same board to share a single IRQ. To enable
  6.3945 +  support for this in the serial driver, say Y here.
  6.3946 +
  6.3947 +Auto-detect IRQ on standard ports (unsafe)
  6.3948 +CONFIG_SERIAL_DETECT_IRQ
  6.3949 +  Say Y here if you want the kernel to try to guess which IRQ
  6.3950 +  to use for your serial port.
  6.3951 +
  6.3952 +  This is considered unsafe; it is far better to configure the IRQ in
  6.3953 +  a boot script using the setserial command.
  6.3954 +
  6.3955 +  If unsure, say N.
  6.3956 +
  6.3957 +Support special multiport boards
  6.3958 +CONFIG_SERIAL_MULTIPORT
  6.3959 +  Some multiport serial ports have special ports which are used to
  6.3960 +  signal when there are any serial ports on the board which need
  6.3961 +  servicing. Say Y here to enable the serial driver to take advantage
  6.3962 +  of those special I/O ports.
  6.3963 +
  6.3964 +SGI IP22 Zilog85C30 serial support
  6.3965 +CONFIG_IP22_SERIAL
  6.3966 +  If you want to use your IP22's built-in serial ports under Linux,
  6.3967 +  answer Y.
  6.3968 +
  6.3969 +SGI Newport Console support
  6.3970 +CONFIG_SGI_NEWPORT_CONSOLE
  6.3971 +  Say Y here if you want the console on the Newport aka XL graphics
  6.3972 +  card of your Indy.  Most people say Y here.
  6.3973 +
  6.3974 +SGI DS1286 RTC support
  6.3975 +CONFIG_SGI_DS1286
  6.3976 +  If you say Y here and create a character special file /dev/rtc with
  6.3977 +  major number 10 and minor number 135 using mknod ("man mknod"), you
  6.3978 +  will get access to the real time clock built into your computer.
  6.3979 +  Every SGI has such a clock built in. It reports status information
  6.3980 +  via the file /proc/rtc and its behaviour is set by various ioctls on
  6.3981 +  /dev/rtc.
  6.3982 +
  6.3983 +Dallas DS1742 RTC Support
  6.3984 +CONFIG_DS1742
  6.3985 +  If you say Y here and create a character special file /dev/rtc with
  6.3986 +  major number 10 and minor number 135 using mknod ("man mknod"), you
  6.3987 +  will get access to the real time clock present on various Toshiba
  6.3988 +  MIPS-based boards. It reports status information via the file
  6.3989 +  /proc/driver/rtc and its behaviour is set by various ioctls on
  6.3990 +  /dev/rtc or /dev/misc/rtc if using devfs.
  6.3991 +
  6.3992 +  For technical information and application notes, please see the
  6.3993 +  Dallas Semiconductor website:
  6.3994 +  <http://www.dalsemi.com/quick_view2.cfm?qv_pk=2768>.
  6.3995 +
  6.3996 +  This driver is also available as a module ( = code which can be
  6.3997 +  inserted in and removed from the running kernel whenever you want).
  6.3998 +  The module is called ds1742.o. If you want to compile it as a module,
  6.3999 +  say M here and read <file:Documentation/modules.txt>.
  6.4000 +
  6.4001 +Indy/I2 Hardware Watchdog
  6.4002 +CONFIG_INDYDOG
  6.4003 +  Hardwaredriver for the Indy's/I2's watchdog. This is a
  6.4004 +  watchdog timer that will reboot the machine after a 60 second 
  6.4005 +  timer expired and no process has written to /dev/watchdog during
  6.4006 +  that time.
  6.4007 +
  6.4008 +Support the Bell Technologies HUB6 card
  6.4009 +CONFIG_HUB6
  6.4010 +  Say Y here to enable support in the dumb serial driver to support
  6.4011 +  the HUB6 card.
  6.4012 +
  6.4013 +PCMCIA serial device support
  6.4014 +CONFIG_PCMCIA_SERIAL_CS
  6.4015 +  Say Y here to enable support for 16-bit PCMCIA serial devices,
  6.4016 +  including serial port cards, modems, and the modem functions of
  6.4017 +  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
  6.4018 +  credit-card size devices often used with laptops.)
  6.4019 +
  6.4020 +  This driver is also available as a module ( = code which can be
  6.4021 +  inserted in and removed from the running kernel whenever you want).
  6.4022 +  The module will be called serial_cs.o.  If you want to compile it as
  6.4023 +  a module, say M here and read <file:Documentation/modules.txt>.
  6.4024 +  If unsure, say N.
  6.4025 +
  6.4026 +CONFIG_SYNCLINK_CS
  6.4027 +  Enable support for the SyncLink PC Card serial adapter, running
  6.4028 +  asynchronous and HDLC communications up to 512Kbps. The port is
  6.4029 +  selectable for RS-232, V.35, RS-449, RS-530, and X.21
  6.4030 +
  6.4031 +  This driver may be built as a module ( = code which can be
  6.4032 +  inserted in and removed from the running kernel whenever you want).
  6.4033 +  The module will be called synclinkmp.o.  If you want to do that, say M
  6.4034 +  here.
  6.4035 +
  6.4036 +ACP Modem (Mwave) support
  6.4037 +CONFIG_MWAVE
  6.4038 +  The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
  6.4039 +  kernel driver and a user level application. Together these components
  6.4040 +  support direct attachment to public switched telephone networks (PSTNs)
  6.4041 +  and support selected world wide countries.
  6.4042 +
  6.4043 +  This version of the ACP Modem driver supports the IBM Thinkpad 600E,
  6.4044 +  600, and 770 that include on board ACP modem hardware.
  6.4045 +
  6.4046 +  The modem also supports the standard communications port interface
  6.4047 +  (ttySx) and is compatible with the Hayes AT Command Set.
  6.4048 +
  6.4049 +  The user level application needed to use this driver can be found at
  6.4050 +  the IBM Linux Technology Center (LTC) web site:
  6.4051 +  <http://www.ibm.com/linux/ltc/>.
  6.4052 +
  6.4053 +  If you own one of the above IBM Thinkpads which has the Mwave chipset
  6.4054 +  in it, say Y.
  6.4055 +
  6.4056 +  This driver is also available as a module ( = code which can be
  6.4057 +  inserted in and removed from the running kernel whenever you want).
  6.4058 +  The module will be called mwave.o. If you want to compile it as
  6.4059 +  a module, say M here and read Documentation/modules.txt.
  6.4060 +
  6.4061 +/dev/agpgart (AGP Support)
  6.4062 +CONFIG_AGP
  6.4063 +  AGP (Accelerated Graphics Port) is a bus system mainly used to
  6.4064 +  connect graphics cards to the rest of the system.
  6.4065 +
  6.4066 +  If you have an AGP system and you say Y here, it will be possible to
  6.4067 +  use the AGP features of your 3D rendering video card. This code acts
  6.4068 +  as a sort of "AGP driver" for the motherboard's chipset.
  6.4069 +
  6.4070 +  If you need more texture memory than you can get with the AGP GART
  6.4071 +  (theoretically up to 256 MB, but in practice usually 64 or 128 MB
  6.4072 +  due to kernel allocation issues), you could use PCI accesses
  6.4073 +  and have up to a couple gigs of texture space.
  6.4074 +
  6.4075 +  Note that this is the only means to have XFree4/GLX use
  6.4076 +  write-combining with MTRR support on the AGP bus. Without it, OpenGL
  6.4077 +  direct rendering will be a lot slower but still faster than PIO.
  6.4078 +
  6.4079 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4080 +  use GLX or DRI.  If unsure, say N.
  6.4081 +
  6.4082 +  This driver is available as a module.  If you want to compile it as
  6.4083 +  a module, say M here and read <file:Documentation/modules.txt>.  The
  6.4084 +  module will be called agpgart.o.
  6.4085 +
  6.4086 +Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
  6.4087 +CONFIG_AGP_INTEL
  6.4088 +  This option gives you AGP support for the GLX component of the
  6.4089 +  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
  6.4090 +
  6.4091 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4092 +  use GLX or DRI.  If unsure, say N.
  6.4093 +
  6.4094 +Intel 460GX support
  6.4095 +CONFIG_AGP_I460
  6.4096 +  This option gives you AGP support for the Intel 460GX chipset.  This
  6.4097 +  chipset, the first to support Intel Itanium processors, is new and
  6.4098 +  this option is correspondingly a little experimental.
  6.4099 +
  6.4100 +  If you don't have a 460GX based machine (such as BigSur) with an AGP 
  6.4101 +  slot then this option isn't going to do you much good.  If you're
  6.4102 +  dying to do Direct Rendering on IA-64, this is what you're looking for.
  6.4103 +
  6.4104 +Intel I810/I815 DC100/I810e support
  6.4105 +CONFIG_AGP_I810
  6.4106 +  This option gives you AGP support for the Xserver on the Intel 810
  6.4107 +  815 and 830m chipset boards for their on-board integrated graphics. This
  6.4108 +  is required to do any useful video modes with these boards.
  6.4109 +
  6.4110 +VIA chipset support
  6.4111 +CONFIG_AGP_VIA
  6.4112 +  This option gives you AGP support for the GLX component of the
  6.4113 +  XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
  6.4114 +
  6.4115 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4116 +  use GLX or DRI.  If unsure, say N.
  6.4117 +
  6.4118 +AMD Irongate, 761, and 762 support
  6.4119 +CONFIG_AGP_AMD
  6.4120 +  This option gives you AGP support for the GLX component of the
  6.4121 +  XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
  6.4122 +
  6.4123 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4124 +  use GLX or DRI.  If unsure, say N.
  6.4125 +
  6.4126 +CONFIG_AGP_AMD_K8
  6.4127 +  This option gives you AGP support for the GLX component of
  6.4128 +  XFree86 on an AMD Opteron/Athlon64 using the on-CPU GART.
  6.4129 +
  6.4130 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4131 +  use GLX or DRI.  If unsure, say N.
  6.4132 +
  6.4133 +Generic SiS support
  6.4134 +CONFIG_AGP_SIS
  6.4135 +  This option gives you AGP support for the GLX component of
  6.4136 +  XFree86 4.x on Silicon Integrated Systems [SiS] chipsets.
  6.4137 +
  6.4138 +  Note that 5591/5592 AGP chipsets are NOT specifically supported;
  6.4139 +  However, the driver works well on these, too.
  6.4140 +
  6.4141 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4142 +  use GLX or DRI.  If unsure, say N.
  6.4143 +
  6.4144 +Serverworks LE/HE support
  6.4145 +CONFIG_AGP_SWORKS
  6.4146 +  Say Y here to support the Serverworks AGP card.  See
  6.4147 +  <http://www.serverworks.com/> for product descriptions and images.
  6.4148 +
  6.4149 +NVIDIA chipset support
  6.4150 +CONFIG_AGP_NVIDIA
  6.4151 +  This option gives you AGP support for the GLX component of the
  6.4152 +  XFree86 4.x on NVIDIA nForce/nForce2 chipsets.
  6.4153 +
  6.4154 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4155 +  use GLX or DRI.  If unsure, say N.
  6.4156 +
  6.4157 +ALI chipset support
  6.4158 +CONFIG_AGP_ALI
  6.4159 +  This option gives you AGP support for the GLX component of the
  6.4160 +  XFree86 4.x on the following ALi chipsets.  The supported chipsets
  6.4161 +  include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
  6.4162 +  For the ALi-chipset question, ALi suggests you refer to
  6.4163 +  <http://www.ali.com.tw/eng/support/index.shtml>.
  6.4164 +
  6.4165 +  The M1541 chipset can do AGP 1x and 2x, but note that there is an
  6.4166 +  acknowledged incompatibility with Matrox G200 cards. Due to
  6.4167 +  timing issues, this chipset cannot do AGP 2x with the G200.
  6.4168 +  This is a hardware limitation. AGP 1x seems to be fine, though.
  6.4169 +
  6.4170 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4171 +  use GLX or DRI.  If unsure, say N.
  6.4172 +
  6.4173 +CONFIG_AGP_HP_ZX1
  6.4174 +  This option gives you AGP GART support for the HP ZX1 chipset
  6.4175 +  for IA64 processors.
  6.4176 +
  6.4177 +CONFIG_AGP_ATI
  6.4178 +  This option gives you AGP support for the GLX component of
  6.4179 +  XFree86 4.x on the ATI RadeonIGP family of chipsets.
  6.4180 +
  6.4181 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  6.4182 +  use GLX or DRI.  If unsure, say N.
  6.4183 +
  6.4184 +Support for ISA-bus hardware
  6.4185 +CONFIG_ISA
  6.4186 +  Find out whether you have ISA slots on your motherboard.  ISA is the
  6.4187 +  name of a bus system, i.e. the way the CPU talks to the other stuff
  6.4188 +  inside your box.  Other bus systems are PCI, EISA, MicroChannel
  6.4189 +  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
  6.4190 +  newer boards don't support it.  If you have ISA, say Y, otherwise N.
  6.4191 +
  6.4192 +Support for PCI bus hardware
  6.4193 +CONFIG_PCI
  6.4194 +  Find out whether you have a PCI motherboard. PCI is the name of a
  6.4195 +  bus system, i.e. the way the CPU talks to the other stuff inside
  6.4196 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  6.4197 +  VESA. If you have PCI, say Y, otherwise N.
  6.4198 +
  6.4199 +  The PCI-HOWTO, available from
  6.4200 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  6.4201 +  information about which PCI hardware does work under Linux and which
  6.4202 +  doesn't.
  6.4203 +
  6.4204 +PCI support
  6.4205 +CONFIG_PCI_INTEGRATOR
  6.4206 +  Find out whether you have a PCI motherboard. PCI is the name of a
  6.4207 +  bus system, i.e. the way the CPU talks to the other stuff inside
  6.4208 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  6.4209 +  VESA. If you have PCI, say Y, otherwise N.
  6.4210 +
  6.4211 +  The PCI-HOWTO, available from
  6.4212 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  6.4213 +  information about which PCI hardware does work under Linux and which
  6.4214 +  doesn't.
  6.4215 +
  6.4216 +QSpan PCI
  6.4217 +CONFIG_PCI_QSPAN
  6.4218 +  Find out whether you have a PCI motherboard. PCI is the name of a
  6.4219 +  bus system, i.e. the way the CPU talks to the other stuff inside
  6.4220 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  6.4221 +  VESA. If you have PCI, say Y, otherwise N.
  6.4222 +
  6.4223 +  The PCI-HOWTO, available from
  6.4224 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  6.4225 +  information about which PCI hardware does work under Linux and which
  6.4226 +  doesn't.
  6.4227 +
  6.4228 +# Choice: pci_access
  6.4229 +PCI access mode
  6.4230 +CONFIG_PCI_GOBIOS
  6.4231 +  On PCI systems, the BIOS can be used to detect the PCI devices and
  6.4232 +  determine their configuration. However, some old PCI motherboards
  6.4233 +  have BIOS bugs and may crash if this is done. Also, some embedded
  6.4234 +  PCI-based systems don't have any BIOS at all. Linux can also try to
  6.4235 +  detect the PCI hardware directly without using the BIOS.
  6.4236 +
  6.4237 +  With this option, you can specify how Linux should detect the PCI
  6.4238 +  devices. If you choose "BIOS", the BIOS will be used, if you choose
  6.4239 +  "Direct", the BIOS won't be used, and if you choose "Any", the
  6.4240 +  kernel will try the direct access method and falls back to the BIOS
  6.4241 +  if that doesn't work. If unsure, go with the default, which is
  6.4242 +  "Any".
  6.4243 +
  6.4244 +PCI device name database
  6.4245 +CONFIG_PCI_NAMES
  6.4246 +  By default, the kernel contains a database of all known PCI device
  6.4247 +  names to make the information in /proc/pci, /proc/ioports and
  6.4248 +  similar files comprehensible to the user. This database increases
  6.4249 +  size of the kernel image by about 80KB, but it gets freed after the
  6.4250 +  system boots up, so it doesn't take up kernel memory. Anyway, if you
  6.4251 +  are building an installation floppy or kernel for an embedded system
  6.4252 +  where kernel image size really matters, you can disable this feature
  6.4253 +  and you'll get device ID numbers instead of names.
  6.4254 +
  6.4255 +  When in doubt, say Y.
  6.4256 +
  6.4257 +Generic PCI hotplug support
  6.4258 +CONFIG_HOTPLUG_PCI
  6.4259 +  Say Y here if you have a motherboard with a PCI Hotplug controller.
  6.4260 +  This allows you to add and remove PCI cards while the machine is
  6.4261 +  powered up and running.  The file system pcihpfs must be mounted
  6.4262 +  in order to interact with any PCI Hotplug controllers.
  6.4263 +
  6.4264 +  This code is also available as a module ( = code which can be
  6.4265 +  inserted in and removed from the running kernel whenever you want).
  6.4266 +  The module will be called pci_hotplug.o. If you want to compile it
  6.4267 +  as a module, say M here and read <file:Documentation/modules.txt>.
  6.4268 +
  6.4269 +  When in doubt, say N.
  6.4270 +
  6.4271 +Compaq PCI Hotplug driver
  6.4272 +CONFIG_HOTPLUG_PCI_COMPAQ
  6.4273 +  Say Y here if you have a motherboard with a Compaq PCI Hotplug
  6.4274 +  controller.
  6.4275 +
  6.4276 +  This code is also available as a module ( = code which can be
  6.4277 +  inserted in and removed from the running kernel whenever you want).
  6.4278 +  The module will be called cpqphp.o. If you want to compile it
  6.4279 +  as a module, say M here and read <file:Documentation/modules.txt>.
  6.4280 +
  6.4281 +  When in doubt, say N.
  6.4282 +
  6.4283 +PCI Compaq Hotplug controller NVRAM support
  6.4284 +CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
  6.4285 +  Say Y here if you have a Compaq server that has a PCI Hotplug
  6.4286 +  controller.  This will allow the PCI Hotplug driver to store the PCI
  6.4287 +  system configuration options in NVRAM.
  6.4288 +
  6.4289 +  When in doubt, say N.
  6.4290 +
  6.4291 +ACPI PCI Hotplug driver
  6.4292 +CONFIG_HOTPLUG_PCI_ACPI
  6.4293 +  Say Y here if you have a system that supports PCI Hotplug using
  6.4294 +  ACPI.
  6.4295 +
  6.4296 +  This code is also available as a module ( = code which can be
  6.4297 +  inserted in and removed from the running kernel whenever you want).
  6.4298 +  The module will be called acpiphp.o. If you want to compile it
  6.4299 +  as a module, say M here and read <file:Documentation/modules.txt>.
  6.4300 +
  6.4301 +MCA support
  6.4302 +CONFIG_MCA
  6.4303 +  MicroChannel Architecture is found in some IBM PS/2 machines and
  6.4304 +  laptops.  It is a bus system similar to PCI or ISA. See
  6.4305 +  <file:Documentation/mca.txt> (and especially the web page given
  6.4306 +  there) before attempting to build an MCA bus kernel.
  6.4307 +
  6.4308 +Support for EISA-bus hardware
  6.4309 +CONFIG_EISA
  6.4310 +  The Extended Industry Standard Architecture (EISA) bus was
  6.4311 +  developed as an open alternative to the IBM MicroChannel bus.
  6.4312 +
  6.4313 +  The EISA bus provided some of the features of the IBM MicroChannel
  6.4314 +  bus while maintaining backward compatibility with cards made for
  6.4315 +  the older ISA bus.  The EISA bus saw limited use between 1988 and
  6.4316 +  1995 when it was made obsolete by the PCI bus.
  6.4317 +
  6.4318 +  Say Y here if you are building a kernel for an EISA-based machine.
  6.4319 +
  6.4320 +  Otherwise, say N.
  6.4321 +
  6.4322 +SGI Visual Workstation support
  6.4323 +CONFIG_VISWS
  6.4324 +  The SGI Visual Workstation series is an IA32-based workstation
  6.4325 +  based on SGI systems chips with some legacy PC hardware attached.
  6.4326 +  Say Y here to create a kernel to run on the SGI 320 or 540.
  6.4327 +  A kernel compiled for the Visual Workstation will not run on other
  6.4328 +  PC boards and vice versa.
  6.4329 +  See <file:Documentation/sgi-visws.txt> for more.
  6.4330 +
  6.4331 +SGI Visual Workstation framebuffer support
  6.4332 +CONFIG_FB_SGIVW
  6.4333 +  SGI Visual Workstation support for framebuffer graphics.
  6.4334 +
  6.4335 +I2O support
  6.4336 +CONFIG_I2O
  6.4337 +  The Intelligent Input/Output (I2O) architecture allows hardware
  6.4338 +  drivers to be split into two parts: an operating system specific
  6.4339 +  module called the OSM and an hardware specific module called the
  6.4340 +  HDM. The OSM can talk to a whole range of HDM's, and ideally the
  6.4341 +  HDM's are not OS dependent. This allows for the same HDM driver to
  6.4342 +  be used under different operating systems if the relevant OSM is in
  6.4343 +  place. In order for this to work, you need to have an I2O interface
  6.4344 +  adapter card in your computer. This card contains a special I/O
  6.4345 +  processor (IOP), thus allowing high speeds since the CPU does not
  6.4346 +  have to deal with I/O.
  6.4347 +
  6.4348 +  If you say Y here, you will get a choice of interface adapter
  6.4349 +  drivers and OSM's with the following questions.
  6.4350 +
  6.4351 +  This support is also available as a module ( = code which can be
  6.4352 +  inserted in and removed from the running kernel whenever you want).
  6.4353 +  If you want to compile it as a module, say M here and read
  6.4354 +  <file:Documentation/modules.txt>.  You will get modules called
  6.4355 +  i2o_core.o and i2o_config.o.
  6.4356 +
  6.4357 +  If unsure, say N.
  6.4358 +
  6.4359 +I2O PCI support
  6.4360 +CONFIG_I2O_PCI
  6.4361 +  Say Y for support of PCI bus I2O interface adapters. Currently this
  6.4362 +  is the only variety supported, so you should say Y.
  6.4363 +
  6.4364 +  This support is also available as a module called i2o_pci.o ( = code
  6.4365 +  which can be inserted in and removed from the running kernel
  6.4366 +  whenever you want). If you want to compile it as a module, say M
  6.4367 +  here and read <file:Documentation/modules.txt>.
  6.4368 +
  6.4369 +I2O Block OSM
  6.4370 +CONFIG_I2O_BLOCK
  6.4371 +  Include support for the I2O Block OSM. The Block OSM presents disk
  6.4372 +  and other structured block devices to the operating system.
  6.4373 +
  6.4374 +  This support is also available as a module called i2o_block.o ( =
  6.4375 +  code which can be inserted in and removed from the running kernel
  6.4376 +  whenever you want). If you want to compile it as a module, say M
  6.4377 +  here and read <file:Documentation/modules.txt>.
  6.4378 +
  6.4379 +I2O LAN OSM
  6.4380 +CONFIG_I2O_LAN
  6.4381 +  Include support for the LAN OSM. You will also need to include
  6.4382 +  support for token ring or FDDI if you wish to use token ring or FDDI
  6.4383 +  I2O cards with this driver.
  6.4384 +
  6.4385 +  This support is also available as a module called i2o_lan.o ( = code
  6.4386 +  which can be inserted in and removed from the running kernel
  6.4387 +  whenever you want). If you want to compile it as a module, say M
  6.4388 +  here and read <file:Documentation/modules.txt>.
  6.4389 +
  6.4390 +I2O SCSI OSM
  6.4391 +CONFIG_I2O_SCSI
  6.4392 +  Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  6.4393 +  I2O controller. You can use both the SCSI and Block OSM together if
  6.4394 +  you wish.
  6.4395 +
  6.4396 +  This support is also available as a module called i2o_scsi.o ( =
  6.4397 +  code which can be inserted in and removed from the running kernel
  6.4398 +  whenever you want). If you want to compile it as a module, say M
  6.4399 +  here and read <file:Documentation/modules.txt>.
  6.4400 +
  6.4401 +I2O /proc support
  6.4402 +CONFIG_I2O_PROC
  6.4403 +  If you say Y here and to "/proc file system support", you will be
  6.4404 +  able to read I2O related information from the virtual directory
  6.4405 +  /proc/i2o.
  6.4406 +
  6.4407 +  This support is also available as a module called i2o_proc.o ( =
  6.4408 +  code which can be inserted in and removed from the running kernel
  6.4409 +  whenever you want). If you want to compile it as a module, say M
  6.4410 +  here and read <file:Documentation/modules.txt>.
  6.4411 +
  6.4412 +Plug and Play support
  6.4413 +CONFIG_PNP
  6.4414 +  Plug and Play (PnP) is a standard for peripherals which allows those
  6.4415 +  peripherals to be configured by software, e.g. assign IRQ's or other
  6.4416 +  parameters. No jumpers on the cards are needed, instead the values
  6.4417 +  are provided to the cards from the BIOS, from the operating system,
  6.4418 +  or using a user-space utility.
  6.4419 +
  6.4420 +  Say Y here if you would like Linux to configure your Plug and Play
  6.4421 +  devices. You should then also say Y to "ISA Plug and Play support",
  6.4422 +  below. Alternatively, you can say N here and configure your PnP
  6.4423 +  devices using the user space utilities contained in the isapnptools
  6.4424 +  package.
  6.4425 +
  6.4426 +  This support is also available as a module ( = code which can be
  6.4427 +  inserted in and removed from the running kernel whenever you want).
  6.4428 +  If you want to compile it as a module, say M here and read
  6.4429 +  <file:Documentation/modules.txt>.
  6.4430 +
  6.4431 +ISA Plug and Play support
  6.4432 +CONFIG_ISAPNP
  6.4433 +  Say Y here if you would like support for ISA Plug and Play devices.
  6.4434 +  Some information is in <file:Documentation/isapnp.txt>.
  6.4435 +
  6.4436 +  This support is also available as a module called isapnp.o ( =
  6.4437 +  code which can be inserted in and removed from the running kernel
  6.4438 +  whenever you want). If you want to compile it as a module, say M
  6.4439 +  here and read <file:Documentation/modules.txt>.
  6.4440 +
  6.4441 +  If unsure, say Y.
  6.4442 +
  6.4443 +PNPBIOS support
  6.4444 +CONFIG_PNPBIOS
  6.4445 +  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
  6.4446 +  Specification Version 1.0A May 5, 1994" to autodetect built-in
  6.4447 +  mainboard resources (e.g. parallel port resources).
  6.4448 +
  6.4449 +  Other features (e.g. change resources, ESCD, event notification,
  6.4450 +  Docking station information, ISAPNP services) are not used.
  6.4451 +
  6.4452 +  Note: ACPI is expected to supersede PNPBIOS some day, currently it
  6.4453 +  co-exists nicely.
  6.4454 +
  6.4455 +  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
  6.4456 +  or have a look at /proc/bus/pnp.
  6.4457 +
  6.4458 +  If unsure, say Y.
  6.4459 +
  6.4460 +Support for hot-pluggable devices
  6.4461 +CONFIG_HOTPLUG
  6.4462 +  Say Y here if you want to plug devices into your computer while
  6.4463 +  the system is running, and be able to use them quickly.  In many
  6.4464 +  cases, the devices can likewise be unplugged at any time too.
  6.4465 +
  6.4466 +  One well known example of this is PCMCIA- or PC-cards, credit-card
  6.4467 +  size devices such as network cards, modems or hard drives which are
  6.4468 +  plugged into slots found on all modern laptop computers.  Another
  6.4469 +  example, used on modern desktops as well as laptops, is USB.
  6.4470 +
  6.4471 +  Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
  6.4472 +  software (at <http://linux-hotplug.sourceforge.net/>) and install it.
  6.4473 +  Then your kernel will automatically call out to a user mode "policy
  6.4474 +  agent" (/sbin/hotplug) to load modules and set up software needed
  6.4475 +  to use devices as you hotplug them.
  6.4476 +
  6.4477 +PCMCIA/CardBus support
  6.4478 +CONFIG_PCMCIA
  6.4479 +  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  6.4480 +  computer.  These are credit-card size devices such as network cards,
  6.4481 +  modems or hard drives often used with laptops computers.  There are
  6.4482 +  actually two varieties of these cards: the older 16 bit PCMCIA cards
  6.4483 +  and the newer 32 bit CardBus cards.  If you want to use CardBus
  6.4484 +  cards, you need to say Y here and also to "CardBus support" below.
  6.4485 +
  6.4486 +  To use your PC-cards, you will need supporting software from David
  6.4487 +  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  6.4488 +  for location).  Please also read the PCMCIA-HOWTO, available from
  6.4489 +  <http://www.tldp.org/docs.html#howto>.
  6.4490 +
  6.4491 +  This driver is also available as a module ( = code which can be
  6.4492 +  inserted in and removed from the running kernel whenever you want).
  6.4493 +  When compiled this way, there will be modules called pcmcia_core.o
  6.4494 +  and ds.o.  If you want to compile it as a module, say M here and
  6.4495 +  read <file:Documentation/modules.txt>.
  6.4496 +
  6.4497 +CardBus card and (Yenta) bridge support
  6.4498 +CONFIG_CARDBUS
  6.4499 +  CardBus is a bus mastering architecture for PC-cards, which allows
  6.4500 +  for 32 bit PC-cards (the original PCMCIA standard specifies only
  6.4501 +  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  6.4502 +
  6.4503 +  This option enables support for CardBus PC Cards, as well as support
  6.4504 +  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
  6.4505 +  CardBus compatible.  A "bridge" is the hardware inside your computer
  6.4506 +  that PCMCIA cards are plugged into.
  6.4507 +
  6.4508 +  To use your PC-cards, you will need supporting software from David
  6.4509 +  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  6.4510 +  for location).
  6.4511 +
  6.4512 +  If unsure, say Y.
  6.4513 +
  6.4514 +i82092 compatible bridge support
  6.4515 +CONFIG_I82092
  6.4516 +  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  6.4517 +  found in some older laptops and more commonly in evaluation boards for the
  6.4518 +  chip.
  6.4519 +
  6.4520 +i82365 compatible host bridge support
  6.4521 +CONFIG_I82365
  6.4522 +  Say Y here to include support for ISA-bus PCMCIA host bridges that
  6.4523 +  are register compatible with the Intel i82365.  These are found on
  6.4524 +  older laptops and ISA-bus card readers for desktop systems.  A
  6.4525 +  "bridge" is the hardware inside your computer that PCMCIA cards are
  6.4526 +  plugged into. If unsure, say N.
  6.4527 +
  6.4528 +Databook TCIC host bridge support
  6.4529 +CONFIG_TCIC
  6.4530 +  Say Y here to include support for the Databook TCIC family of PCMCIA
  6.4531 +  host bridges. These are only found on a handful of old systems.
  6.4532 +  "Bridge" is the name used for the hardware inside your computer that
  6.4533 +  PCMCIA cards are plugged into. If unsure, say N.
  6.4534 +
  6.4535 +CONFIG_PCMCIA_SIBYTE
  6.4536 +  Say Y here to include support for the SiByte SOC's built-in PCMCIA
  6.4537 +  interface.  Only ATA cards and CompactFlash are currently
  6.4538 +  supported.
  6.4539 +
  6.4540 +System V IPC
  6.4541 +CONFIG_SYSVIPC
  6.4542 +  Inter Process Communication is a suite of library functions and
  6.4543 +  system calls which let processes (running programs) synchronize and
  6.4544 +  exchange information. It is generally considered to be a good thing,
  6.4545 +  and some programs won't run unless you say Y here. In particular, if
  6.4546 +  you want to run the DOS emulator dosemu under Linux (read the
  6.4547 +  DOSEMU-HOWTO, available from
  6.4548 +  <http://www.tldp.org/docs.html#howto>), you'll need to say Y
  6.4549 +  here.
  6.4550 +
  6.4551 +  You can find documentation about IPC with "info ipc" and also in
  6.4552 +  section 6.4 of the Linux Programmer's Guide, available from
  6.4553 +  <http://www.tldp.org/docs.html#guide>.
  6.4554 +
  6.4555 +BSD Process Accounting
  6.4556 +CONFIG_BSD_PROCESS_ACCT
  6.4557 +  If you say Y here, a user level program will be able to instruct the
  6.4558 +  kernel (via a special system call) to write process accounting
  6.4559 +  information to a file: whenever a process exits, information about
  6.4560 +  that process will be appended to the file by the kernel.  The
  6.4561 +  information includes things such as creation time, owning user,
  6.4562 +  command name, memory usage, controlling terminal etc. (the complete
  6.4563 +  list is in the struct acct in <file:include/linux/acct.h>).  It is
  6.4564 +  up to the user level program to do useful things with this
  6.4565 +  information.  This is generally a good idea, so say Y.
  6.4566 +
  6.4567 +Sysctl support
  6.4568 +CONFIG_SYSCTL
  6.4569 +  The sysctl interface provides a means of dynamically changing
  6.4570 +  certain kernel parameters and variables on the fly without requiring
  6.4571 +  a recompile of the kernel or reboot of the system.  The primary
  6.4572 +  interface consists of a system call, but if you say Y to "/proc
  6.4573 +  file system support", a tree of modifiable sysctl entries will be
  6.4574 +  generated beneath the /proc/sys directory. They are explained in the
  6.4575 +  files in <file:Documentation/sysctl/>.  Note that enabling this
  6.4576 +  option will enlarge the kernel by at least 8 KB.
  6.4577 +
  6.4578 +  As it is generally a good thing, you should say Y here unless
  6.4579 +  building a kernel for install/rescue disks or your system is very
  6.4580 +  limited in memory.
  6.4581 +
  6.4582 +# Choice: kcore
  6.4583 +Kernel core (/proc/kcore) format
  6.4584 +CONFIG_KCORE_ELF
  6.4585 +  If you enabled support for /proc file system then the file
  6.4586 +  /proc/kcore will contain the kernel core image. This can be used
  6.4587 +  in gdb:
  6.4588 +
  6.4589 +  $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
  6.4590 +
  6.4591 +  You have two choices here: ELF and A.OUT. Selecting ELF will make
  6.4592 +  /proc/kcore appear in ELF core format as defined by the Executable
  6.4593 +  and Linking Format specification. Selecting A.OUT will choose the
  6.4594 +  old "a.out" format which may be necessary for some old versions
  6.4595 +  of binutils or on some architectures.
  6.4596 +
  6.4597 +  This is especially useful if you have compiled the kernel with the
  6.4598 +  "-g" option to preserve debugging information. It is mainly used
  6.4599 +  for examining kernel data structures on the live kernel so if you
  6.4600 +  don't understand what this means or are not a kernel hacker, just
  6.4601 +  leave it at its default value ELF.
  6.4602 +
  6.4603 +Select a.out format for /proc/kcore
  6.4604 +CONFIG_KCORE_AOUT
  6.4605 +  Not necessary unless you're using a very out-of-date binutils
  6.4606 +  version.  You probably want KCORE_ELF.
  6.4607 +
  6.4608 +Kernel support for ELF binaries
  6.4609 +CONFIG_BINFMT_ELF
  6.4610 +  ELF (Executable and Linkable Format) is a format for libraries and
  6.4611 +  executables used across different architectures and operating
  6.4612 +  systems. Saying Y here will enable your kernel to run ELF binaries
  6.4613 +  and enlarge it by about 13 KB. ELF support under Linux has now all
  6.4614 +  but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  6.4615 +  because it is portable (this does *not* mean that you will be able
  6.4616 +  to run executables from different architectures or operating systems
  6.4617 +  however) and makes building run-time libraries very easy. Many new
  6.4618 +  executables are distributed solely in ELF format. You definitely
  6.4619 +  want to say Y here.
  6.4620 +
  6.4621 +  Information about ELF is contained in the ELF HOWTO available from
  6.4622 +  <http://www.tldp.org/docs.html#howto>.
  6.4623 +
  6.4624 +  If you find that after upgrading from Linux kernel 1.2 and saying Y
  6.4625 +  here, you still can't run any ELF binaries (they just crash), then
  6.4626 +  you'll have to install the newest ELF runtime libraries, including
  6.4627 +  ld.so (check the file <file:Documentation/Changes> for location and
  6.4628 +  latest version).
  6.4629 +
  6.4630 +  If you want to compile this as a module ( = code which can be
  6.4631 +  inserted in and removed from the running kernel whenever you want),
  6.4632 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.4633 +  will be called binfmt_elf.o. Saying M or N here is dangerous because
  6.4634 +  some crucial programs on your system might be in ELF format.
  6.4635 +
  6.4636 +Kernel support for a.out binaries
  6.4637 +CONFIG_BINFMT_AOUT
  6.4638 +  A.out (Assembler.OUTput) is a set of formats for libraries and
  6.4639 +  executables used in the earliest versions of UNIX. Linux used the
  6.4640 +  a.out formats QMAGIC and ZMAGIC until they were replaced with the
  6.4641 +  ELF format.
  6.4642 +
  6.4643 +  As more and more programs are converted to ELF, the use for a.out
  6.4644 +  will gradually diminish. If you disable this option it will reduce
  6.4645 +  your kernel by one page. This is not much and by itself does not
  6.4646 +  warrant removing support. However its removal is a good idea if you
  6.4647 +  wish to ensure that absolutely none of your programs will use this
  6.4648 +  older executable format. If you don't know what to answer at this
  6.4649 +  point then answer Y. If someone told you "You need a kernel with
  6.4650 +  QMAGIC support" then you'll have to say Y here. You may answer M to
  6.4651 +  compile a.out support as a module and later load the module when you
  6.4652 +  want to use a program or library in a.out format. The module will be
  6.4653 +  called binfmt_aout.o. Saying M or N here is dangerous though,
  6.4654 +  because some crucial programs on your system might still be in A.OUT
  6.4655 +  format.
  6.4656 +
  6.4657 +OSF/1 v4 readv/writev compatibility
  6.4658 +CONFIG_OSF4_COMPAT
  6.4659 +  Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  6.4660 +  with v4 shared libraries freely available from Compaq. If you're
  6.4661 +  going to use shared libraries from Tru64 version 5.0 or later, say N.
  6.4662 +
  6.4663 +Kernel support for Linux/Intel ELF binaries
  6.4664 +CONFIG_BINFMT_EM86
  6.4665 +  Say Y here if you want to be able to execute Linux/Intel ELF
  6.4666 +  binaries just like native Alpha binaries on your Alpha machine. For
  6.4667 +  this to work, you need to have the emulator /usr/bin/em86 in place.
  6.4668 +
  6.4669 +  You can get the same functionality by saying N here and saying Y to
  6.4670 +  "Kernel support for MISC binaries".
  6.4671 +
  6.4672 +  You may answer M to compile the emulation support as a module and
  6.4673 +  later load the module when you want to use a Linux/Intel binary. The
  6.4674 +  module will be called binfmt_em86.o. If unsure, say Y.
  6.4675 +
  6.4676 +Kernel support for SOM binaries
  6.4677 +CONFIG_BINFMT_SOM
  6.4678 +  SOM is a binary executable format inherited from HP/UX.  Say Y here
  6.4679 +  to be able to load and execute SOM binaries directly.
  6.4680 +
  6.4681 +Kernel support for MISC binaries
  6.4682 +CONFIG_BINFMT_MISC
  6.4683 +  If you say Y here, it will be possible to plug wrapper-driven binary
  6.4684 +  formats into the kernel. You will like this especially when you use
  6.4685 +  programs that need an interpreter to run like Java, Python or
  6.4686 +  Emacs-Lisp. It's also useful if you often run DOS executables under
  6.4687 +  the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  6.4688 +  <http://www.tldp.org/docs.html#howto>). Once you have
  6.4689 +  registered such a binary class with the kernel, you can start one of
  6.4690 +  those programs simply by typing in its name at a shell prompt; Linux
  6.4691 +  will automatically feed it to the correct interpreter.
  6.4692 +
  6.4693 +  You can do other nice things, too. Read the file
  6.4694 +  <file:Documentation/binfmt_misc.txt> to learn how to use this
  6.4695 +  feature, and <file:Documentation/java.txt> for information about how
  6.4696 +  to include Java support.
  6.4697 +
  6.4698 +  You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
  6.4699 +  use this part of the kernel.
  6.4700 +
  6.4701 +  You may say M here for module support and later load the module when
  6.4702 +  you have use for it; the module is called binfmt_misc.o. If you
  6.4703 +  don't know what to answer at this point, say Y.
  6.4704 +
  6.4705 +Kernel support for JAVA binaries
  6.4706 +CONFIG_BINFMT_JAVA
  6.4707 +  If you say Y here, the kernel will load and execute Java J-code
  6.4708 +  binaries directly.  Note: this option is obsolete and scheduled for
  6.4709 +  removal, use CONFIG_BINFMT_MISC instead.
  6.4710 +
  6.4711 +Solaris binary emulation
  6.4712 +CONFIG_SOLARIS_EMUL
  6.4713 +  This is experimental code which will enable you to run (many)
  6.4714 +  Solaris binaries on your SPARC Linux machine.
  6.4715 +
  6.4716 +  This code is also available as a module ( = code which can be
  6.4717 +  inserted in and removed from the running kernel whenever you want).
  6.4718 +  The module will be called solaris.o. If you want to compile it as a
  6.4719 +  module, say M here and read <file:Documentation/modules.txt>.
  6.4720 +
  6.4721 +SUN SME environment monitoring
  6.4722 +CONFIG_ENVCTRL
  6.4723 +  Kernel support for temperature and fan monitoring on Sun SME
  6.4724 +  machines.
  6.4725 +
  6.4726 +  This code is also available as a module ( = code which can be
  6.4727 +  inserted in and removed from the running kernel whenever you want).
  6.4728 +  The module will be called envctrl.o. If you want to compile it as a
  6.4729 +  module, say M here and read <file:Documentation/modules.txt>.
  6.4730 +
  6.4731 +# Choice: x86type
  6.4732 +Processor family
  6.4733 +CONFIG_M386
  6.4734 +  This is the processor type of your CPU. This information is used for
  6.4735 +  optimizing purposes. In order to compile a kernel that can run on
  6.4736 +  all x86 CPU types (albeit not optimally fast), you can specify
  6.4737 +  "386" here.
  6.4738 +
  6.4739 +  The kernel will not necessarily run on earlier architectures than
  6.4740 +  the one you have chosen, e.g. a Pentium optimized kernel will run on
  6.4741 +  a PPro, but not necessarily on a i486.
  6.4742 +
  6.4743 +  Here are the settings recommended for greatest speed:
  6.4744 +   - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
  6.4745 +     486DLC/DLC2, UMC 486SX-S and NexGen Nx586.  Only "386" kernels
  6.4746 +     will run on a 386 class machine.
  6.4747 +   - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
  6.4748 +     SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
  6.4749 +   - "586" for generic Pentium CPUs, possibly lacking the TSC
  6.4750 +     (time stamp counter) register.
  6.4751 +   - "Pentium-Classic" for the Intel Pentium.
  6.4752 +   - "Pentium-MMX" for the Intel Pentium MMX.
  6.4753 +   - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
  6.4754 +   - "Pentium-III" for the Intel Pentium III
  6.4755 +     and Celerons based on the Coppermine core.
  6.4756 +   - "Pentium-4" for the Intel Pentium 4.
  6.4757 +   - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
  6.4758 +   - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
  6.4759 +   - "Elan" for the AMD Elan family (Elan SC400/SC410).
  6.4760 +   - "Crusoe" for the Transmeta Crusoe series.
  6.4761 +   - "Winchip-C6" for original IDT Winchip.
  6.4762 +   - "Winchip-2" for IDT Winchip 2.
  6.4763 +   - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
  6.4764 +   - "CyrixIII" for VIA Cyrix III or VIA C3.
  6.4765 +   - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
  6.4766 +
  6.4767 +  If you don't know what to do, choose "386".
  6.4768 +
  6.4769 +486
  6.4770 +CONFIG_M486
  6.4771 +  Select this for a x486 processor, ether Intel or one of the
  6.4772 +  compatible processors from AMD, Cyrix, IBM, or Intel.  Includes DX,
  6.4773 +  DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
  6.4774 +  U5S.
  6.4775 +
  6.4776 +586/K5/5x86/6x86/6x86MX
  6.4777 +CONFIG_M586
  6.4778 +  Select this for an x586 or x686 processor such as the AMD K5, the
  6.4779 +  Intel 5x86 or 6x86, or the Intel 6x86MX.  This choice does not
  6.4780 +  assume the RDTSC instruction.
  6.4781 +
  6.4782 +Pentium Classic
  6.4783 +CONFIG_M586TSC
  6.4784 +  Select this for a Pentium Classic processor with the RDTSC (Read
  6.4785 +  Time Stamp Counter) instruction for benchmarking.
  6.4786 +
  6.4787 +VIA C3-2 (Nehemiah)
  6.4788 +CONFIG_MVIAC3_2
  6.4789 +  Select this for a VIA C3 "Nehemiah". Selecting this enables usage of SSE
  6.4790 +  and tells gcc to treat the CPU as a 686.
  6.4791 +
  6.4792 +  Note, this kernel will not boot on older (pre model 9) C3s.
  6.4793 +
  6.4794 +32-bit PDC
  6.4795 +CONFIG_PDC_NARROW
  6.4796 +  Saying Y here will allow developers with a C180, C200, C240, C360,
  6.4797 +  J200, J210, and/or a J2240 to test 64-bit kernels by providing a
  6.4798 +  wrapper for the 32-bit PDC calls.  Since the machines which require
  6.4799 +  this option do not support over 4G of RAM, this option is targeted
  6.4800 +  for developers of these machines wishing to test changes on both
  6.4801 +  32-bit and 64-bit configurations.
  6.4802 +
  6.4803 +  If unsure, say N.
  6.4804 +
  6.4805 +VGA text console
  6.4806 +CONFIG_VGA_CONSOLE
  6.4807 +  Saying Y here will allow you to use Linux in text mode through a
  6.4808 +  display that complies with the generic VGA standard. Virtually
  6.4809 +  everyone wants that.
  6.4810 +
  6.4811 +  The program SVGATextMode can be used to utilize SVGA video cards to
  6.4812 +  their full potential in text mode. Download it from
  6.4813 +  <ftp://ibiblio.org/pub/Linux/utils/console/>.
  6.4814 +
  6.4815 +  Say Y.
  6.4816 +
  6.4817 +Distribute interrupts on all CPUs by default
  6.4818 +CONFIG_IRQ_ALL_CPUS
  6.4819 +  This option gives the kernel permission to distribute IRQs across
  6.4820 +  multiple CPUs.  Saying N here will route all IRQs to the first
  6.4821 +  CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
  6.4822 +  Power3 boxes should say N for now.
  6.4823 +
  6.4824 +Video mode selection support
  6.4825 +CONFIG_VIDEO_SELECT
  6.4826 +  This enables support for text mode selection on kernel startup. If
  6.4827 +  you want to take advantage of some high-resolution text mode your
  6.4828 +  card's BIOS offers, but the traditional Linux utilities like
  6.4829 +  SVGATextMode don't, you can say Y here and set the mode using the
  6.4830 +  "vga=" option from your boot loader (lilo or loadlin) or set
  6.4831 +  "vga=ask" which brings up a video mode menu on kernel startup. (Try
  6.4832 +  "man bootparam" or see the documentation of your boot loader about
  6.4833 +  how to pass options to the kernel.)
  6.4834 +
  6.4835 +  Read the file <file:Documentation/svga.txt> for more information
  6.4836 +  about the Video mode selection support. If unsure, say N.
  6.4837 +
  6.4838 +Support for frame buffer devices
  6.4839 +CONFIG_FB
  6.4840 +  The frame buffer device provides an abstraction for the graphics
  6.4841 +  hardware. It represents the frame buffer of some video hardware and
  6.4842 +  allows application software to access the graphics hardware through
  6.4843 +  a well-defined interface, so the software doesn't need to know
  6.4844 +  anything about the low-level (hardware register) stuff.
  6.4845 +
  6.4846 +  Frame buffer devices work identically across the different
  6.4847 +  architectures supported by Linux and make the implementation of
  6.4848 +  application programs easier and more portable; at this point, an X
  6.4849 +  server exists which uses the frame buffer device exclusively.
  6.4850 +  On several non-X86 architectures, the frame buffer device is the
  6.4851 +  only way to use the graphics hardware.
  6.4852 +
  6.4853 +  The device is accessed through special device nodes, usually located
  6.4854 +  in the /dev directory, i.e. /dev/fb*.
  6.4855 +
  6.4856 +  You need an utility program called fbset to make full use of frame
  6.4857 +  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  6.4858 +  and the Framebuffer-HOWTO at
  6.4859 +  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  6.4860 +  information.
  6.4861 +
  6.4862 +  Say Y here and to the driver for your graphics board below if you
  6.4863 +  are compiling a kernel for a non-x86 architecture.
  6.4864 +
  6.4865 +  If you are compiling for the x86 architecture, you can say Y if you
  6.4866 +  want to play with it, but it is not essential. Please note that
  6.4867 +  running graphical applications that directly touch the hardware
  6.4868 +  (e.g. an accelerated X server) and that are not frame buffer
  6.4869 +  device-aware may cause unexpected results. If unsure, say N.
  6.4870 +
  6.4871 +Acorn VIDC support
  6.4872 +CONFIG_FB_ACORN
  6.4873 +  This is the frame buffer device driver for the Acorn VIDC graphics
  6.4874 +  hardware found in Acorn RISC PCs and other ARM-based machines.  If
  6.4875 +  unsure, say N.
  6.4876 +
  6.4877 +Permedia2 support
  6.4878 +CONFIG_FB_PM2
  6.4879 +  This is the frame buffer device driver for the Permedia2 AGP frame
  6.4880 +  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
  6.4881 +  product page at
  6.4882 +  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
  6.4883 +
  6.4884 +Enable FIFO disconnect feature
  6.4885 +CONFIG_FB_PM2_FIFO_DISCONNECT
  6.4886 +  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
  6.4887 +
  6.4888 +Generic Permedia2 PCI board support
  6.4889 +CONFIG_FB_PM2_PCI
  6.4890 +  Say Y to enable support for Permedia2 AGP frame buffer card from
  6.4891 +  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
  6.4892 +
  6.4893 +Phase5 CVisionPPC/BVisionPPC support
  6.4894 +CONFIG_FB_PM2_CVPPC
  6.4895 +  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
  6.4896 +  framebuffer cards.  Phase 5 is no longer with us, alas.
  6.4897 +
  6.4898 +Amiga native chipset support
  6.4899 +CONFIG_FB_AMIGA
  6.4900 +  This is the frame buffer device driver for the builtin graphics
  6.4901 +  chipset found in Amigas.
  6.4902 +
  6.4903 +  The driver is also available as a module ( = code which can be
  6.4904 +  inserted and removed from the running kernel whenever you want). The
  6.4905 +  module will be called amifb.o. If you want to compile it as a
  6.4906 +  module, say M here and read <file:Documentation/modules.txt>.
  6.4907 +
  6.4908 +Amiga OCS chipset support
  6.4909 +CONFIG_FB_AMIGA_OCS
  6.4910 +  This enables support for the original Agnus and Denise video chips,
  6.4911 +  found in the Amiga 1000 and most A500's and A2000's. If you intend
  6.4912 +  to run Linux on any of these systems, say Y; otherwise say N.
  6.4913 +
  6.4914 +Amiga ECS chipset support
  6.4915 +CONFIG_FB_AMIGA_ECS
  6.4916 +  This enables support for the Enhanced Chip Set, found in later
  6.4917 +  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
  6.4918 +  you intend to run Linux on any of these systems, say Y; otherwise
  6.4919 +  say N.
  6.4920 +
  6.4921 +Amiga AGA chipset support
  6.4922 +CONFIG_FB_AMIGA_AGA
  6.4923 +  This enables support for the Advanced Graphics Architecture (also
  6.4924 +  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
  6.4925 +  and CD32. If you intend to run Linux on any of these systems, say Y;
  6.4926 +  otherwise say N.
  6.4927 +
  6.4928 +Amiga CyberVision support
  6.4929 +CONFIG_FB_CYBER
  6.4930 +  This enables support for the Cybervision 64 graphics card from
  6.4931 +  Phase5. Please note that its use is not all that intuitive (i.e. if
  6.4932 +  you have any questions, be sure to ask!). Say N unless you have a
  6.4933 +  Cybervision 64 or plan to get one before you next recompile the
  6.4934 +  kernel. Please note that this driver DOES NOT support the
  6.4935 +  Cybervision 64 3D card, as they use incompatible video chips.
  6.4936 +
  6.4937 +CyberPro 20x0 support
  6.4938 +CONFIG_FB_CYBER2000
  6.4939 +  This enables support for the Integraphics CyberPro 20x0 and 5000
  6.4940 +  VGA chips used in the Rebel.com Netwinder and other machines.
  6.4941 +  Say Y if you have a NetWinder or a graphics card containing this
  6.4942 +  device, otherwise say N.
  6.4943 +
  6.4944 +Amiga CyberVision3D support
  6.4945 +CONFIG_FB_VIRGE
  6.4946 +  This enables support for the Cybervision 64/3D graphics card from
  6.4947 +  Phase5. Please note that its use is not all that intuitive (i.e. if
  6.4948 +  you have any questions, be sure to ask!). Say N unless you have a
  6.4949 +  Cybervision 64/3D or plan to get one before you next recompile the
  6.4950 +  kernel. Please note that this driver DOES NOT support the older
  6.4951 +  Cybervision 64 card, as they use incompatible video chips.
  6.4952 +
  6.4953 +Amiga RetinaZ3 support
  6.4954 +CONFIG_FB_RETINAZ3
  6.4955 +  This enables support for the Retina Z3 graphics card. Say N unless
  6.4956 +  you have a Retina Z3 or plan to get one before you next recompile
  6.4957 +  the kernel.
  6.4958 +
  6.4959 +Cirrus Logic generic driver
  6.4960 +CONFIG_FB_CLGEN
  6.4961 +  This enables support for Cirrus Logic GD542x/543x based boards on
  6.4962 +  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
  6.4963 +
  6.4964 +  If you have a PCI-based system, this enables support for these
  6.4965 +  chips: GD-543x, GD-544x, GD-5480.
  6.4966 +
  6.4967 +  Please read the file <file:Documentation/fb/clgenfb.txt>.
  6.4968 +
  6.4969 +  Say N unless you have such a graphics board or plan to get one
  6.4970 +  before you next recompile the kernel.
  6.4971 +
  6.4972 +Apollo support
  6.4973 +CONFIG_APOLLO
  6.4974 +  Say Y here if you want to run Linux on an MC680x0-based Apollo
  6.4975 +  Domain workstation such as the DN3500.
  6.4976 +
  6.4977 +Apollo 3c505 "EtherLink Plus" support
  6.4978 +CONFIG_APOLLO_ELPLUS
  6.4979 +  Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
  6.4980 +  If you don't have one made for Apollos, you can use one from a PC,
  6.4981 +  except that your Apollo won't be able to boot from it (because the
  6.4982 +  code in the ROM will be for a PC).
  6.4983 +
  6.4984 +Atari native chipset support
  6.4985 +CONFIG_FB_ATARI
  6.4986 +  This is the frame buffer device driver for the builtin graphics
  6.4987 +  chipset found in Ataris.
  6.4988 +
  6.4989 +Amiga FrameMaster II/Rainbow II support
  6.4990 +CONFIG_FB_FM2
  6.4991 +  This is the frame buffer device driver for the Amiga FrameMaster
  6.4992 +  card from BSC (exhibited 1992 but not shipped as a CBM product).
  6.4993 +
  6.4994 +Open Firmware frame buffer device support
  6.4995 +CONFIG_FB_OF
  6.4996 +  Say Y if you want support with Open Firmware for your graphics
  6.4997 +  board.
  6.4998 +
  6.4999 +S3 Trio frame buffer device support
  6.5000 +CONFIG_FB_S3TRIO
  6.5001 +  If you have a S3 Trio say Y. Say N for S3 Virge.
  6.5002 +
  6.5003 +3Dfx Banshee/Voodoo3 display support
  6.5004 +CONFIG_FB_3DFX
  6.5005 +  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  6.5006 +  chips. Say Y if you have such a graphics board.
  6.5007 +
  6.5008 +  The driver is also available as a module ( = code which can be
  6.5009 +  inserted and removed from the running kernel whenever you want). The
  6.5010 +  module will be called tdfxfb.o. If you want to compile it as a
  6.5011 +  module, say M here and read <file:Documentation/modules.txt>.
  6.5012 +
  6.5013 +nVidia Riva support
  6.5014 +CONFIG_FB_RIVA
  6.5015 +  This driver supports graphics boards with the nVidia Riva/Geforce
  6.5016 +  chips.
  6.5017 +  Say Y if you have such a graphics board.
  6.5018 +
  6.5019 +  The driver is also available as a module ( = code which can be
  6.5020 +  inserted and removed from the running kernel whenever you want). The
  6.5021 +  module will be called rivafb.o. If you want to compile it as a
  6.5022 +  module, say M here and read <file:Documentation/modules.txt>.
  6.5023 +
  6.5024 +Trident Blade/Image support
  6.5025 +CONFIG_FB_TRIDENT
  6.5026 +  This driver is supposed to support graphics boards with the
  6.5027 +  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  6.5028 +  but also on some motherboards.Read <file:Documentation/fb/tridentfb.txt>
  6.5029 +
  6.5030 +  Say Y if you have such a graphics board.
  6.5031 +
  6.5032 +  The driver is also available as a module ( = code which can be
  6.5033 +  inserted and removed from the running kernel whenever you want). The
  6.5034 +  module will be called tridentfb.o. If you want to compile it as a
  6.5035 +  module, say M here and read <file:Documentation/modules.txt>.
  6.5036 +
  6.5037 +ATI Mach64 display support
  6.5038 +CONFIG_FB_ATY
  6.5039 +  This driver supports graphics boards with the ATI Mach64 chips.
  6.5040 +  Say Y if you have such a graphics board.
  6.5041 +
  6.5042 +  The driver is also available as a module ( = code which can be
  6.5043 +  inserted and removed from the running kernel whenever you want). The
  6.5044 +  module will be called atyfb.o. If you want to compile it as a
  6.5045 +  module, say M here and read <file:Documentation/modules.txt>.
  6.5046 +
  6.5047 +ATI Rage128 display support
  6.5048 +CONFIG_FB_ATY128
  6.5049 +  This driver supports graphics boards with the ATI Rage128 chips.
  6.5050 +  Say Y if you have such a graphics board and read
  6.5051 +  <file:Documentation/fb/aty128fb.txt>.
  6.5052 +
  6.5053 +  The driver is also available as a module ( = code which can be
  6.5054 +  inserted and removed from the running kernel whenever you want). The
  6.5055 +  module will be called aty128fb.o. If you want to compile it as a
  6.5056 +  module, say M here and read <file:Documentation/modules.txt>.
  6.5057 +
  6.5058 +Maxine (Personal DECstation) onboard framebuffer support
  6.5059 +CONFIG_FB_MAXINE
  6.5060 +  Support for the onboard framebuffer (1024x768x8) in the Personal
  6.5061 +  DECstation series (Personal DECstation 5000/20, /25, /33, /50,
  6.5062 +  Codename "Maxine").
  6.5063 +
  6.5064 +PMAG-AA TURBOchannel framebuffer support
  6.5065 +CONFIG_FB_PMAG_AA
  6.5066 +  Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
  6.5067 +  used mainly in the MIPS-based DECstation series.
  6.5068 +
  6.5069 +PMAG-BA TURBOchannel framebuffer support
  6.5070 +CONFIG_FB_PMAG_BA
  6.5071 +  Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
  6.5072 +  used mainly in the MIPS-based DECstation series.
  6.5073 +
  6.5074 +PMAGB-B TURBOchannel framebuffer support
  6.5075 +CONFIG_FB_PMAGB_B
  6.5076 +  Support for the PMAGB-B TURBOchannel framebuffer card used mainly
  6.5077 +  in the MIPS-based DECstation series. The card is currently only 
  6.5078 +  supported in 1280x1024x8 mode.  
  6.5079 +
  6.5080 +FutureTV PCI card
  6.5081 +CONFIG_ARCH_FTVPCI
  6.5082 +  Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
  6.5083 +  Electronics) StrongARM PCI card.
  6.5084 +
  6.5085 +ANAKIN Vehicle Telematics Platform
  6.5086 +CONFIG_ARCH_ANAKIN
  6.5087 +  The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
  6.5088 +  64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
  6.5089 +
  6.5090 +  On board peripherals:
  6.5091 +        * Front display: 400x234 16 bit TFT touchscreen
  6.5092 +        * External independent second screen interface
  6.5093 +        * CAN controller SJA1000
  6.5094 +        * USB host controller
  6.5095 +        * 6 channel video codec with hardware overlay
  6.5096 +        * Smartcard reader
  6.5097 +        * IrDa
  6.5098 +
  6.5099 +  Modules interfaced over the Multi Media Extension slots:
  6.5100 +        * A communication card
  6.5101 +                Wavecom GPRS modem
  6.5102 +                uBlock GPS
  6.5103 +                Bosch DAB module
  6.5104 +        * An audio card ( 4 * 40W, AC97 Codec, I2S)
  6.5105 +
  6.5106 +Altera Excalibur XA10 Dev Board
  6.5107 +ARCH_CAMELOT
  6.5108 +  This enables support for Altera's Excalibur XA10 development board.
  6.5109 +  If you would like to build your kernel to run on one of these boards
  6.5110 +  then you must say 'Y' here. Otherwise say 'N'
  6.5111 +
  6.5112 +Link-Up Systems LCD support
  6.5113 +CONFIG_FB_L7200
  6.5114 +  This driver supports the L7200 Color LCD.
  6.5115 +  Say Y if you want graphics support.
  6.5116 +
  6.5117 +NeoMagic display support (EXPERIMENTAL)
  6.5118 +CONFIG_FB_NEOMAGIC
  6.5119 +  This driver supports notebooks with NeoMagic PCI chips.
  6.5120 +  Say Y if you have such a graphics card. 
  6.5121 +
  6.5122 +  The driver is also available as a module ( = code which can be
  6.5123 +  inserted and removed from the running kernel whenever you want). The
  6.5124 +  module will be called neofb.o. If you want to compile it as a
  6.5125 +  module, say M here and read Documentation/modules.txt.
  6.5126 +
  6.5127 +PowerMac "control" frame buffer device support
  6.5128 +CONFIG_FB_CONTROL
  6.5129 +  This driver supports a frame buffer for the graphics adapter in the
  6.5130 +  Power Macintosh 7300 and others.
  6.5131 +
  6.5132 +PowerMac "platinum" frame buffer device support
  6.5133 +CONFIG_FB_PLATINUM
  6.5134 +  This driver supports a frame buffer for the "platinum" graphics
  6.5135 +  adapter in some Power Macintoshes.
  6.5136 +
  6.5137 +PowerMac "valkyrie" frame buffer device support
  6.5138 +CONFIG_FB_VALKYRIE
  6.5139 +  This driver supports a frame buffer for the "valkyrie" graphics
  6.5140 +  adapter in some Power Macintoshes.
  6.5141 +
  6.5142 +Chips 65550 display support
  6.5143 +CONFIG_FB_CT65550
  6.5144 +  This is the frame buffer device driver for the Chips & Technologies
  6.5145 +  65550 graphics chip in PowerBooks.
  6.5146 +
  6.5147 +TGA frame buffer support
  6.5148 +CONFIG_FB_TGA
  6.5149 +  This is the frame buffer device driver for generic TGA graphic
  6.5150 +  cards. Say Y if you have one of those.
  6.5151 +
  6.5152 +VESA VGA graphics console
  6.5153 +CONFIG_FB_VESA
  6.5154 +  This is the frame buffer device driver for generic VESA 2.0
  6.5155 +  compliant graphic cards. The older VESA 1.2 cards are not supported.
  6.5156 +  You will get a boot time penguin logo at no additional cost. Please
  6.5157 +  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
  6.5158 +
  6.5159 +VGA 16-color planar support
  6.5160 +CONFIG_FBCON_VGA_PLANES
  6.5161 +  This low level frame buffer console driver enable the kernel to use
  6.5162 +  the 16-color planar modes of the old VGA cards where the bits of
  6.5163 +  each pixel are separated into 4 planes.
  6.5164 +
  6.5165 +  Only answer Y here if you have a (very old) VGA card that isn't VESA
  6.5166 +  2 compatible.
  6.5167 +
  6.5168 +VGA 16-color graphics console
  6.5169 +CONFIG_FB_VGA16
  6.5170 +  This is the frame buffer device driver for VGA 16 color graphic
  6.5171 +  cards. Say Y if you have such a card.
  6.5172 +
  6.5173 +  This code is also available as a module. If you want to compile it
  6.5174 +  as a module ( = code which can be inserted in and removed from the
  6.5175 +  running kernel whenever you want), say M here and read
  6.5176 +  <file:Documentation/modules.txt>.  The module will be called
  6.5177 +  vga16fb.o.
  6.5178 +
  6.5179 +Generic STI frame buffer device support
  6.5180 +CONFIG_FB_STI
  6.5181 +  STI refers to the HP "Standard Text Interface" which is a set of
  6.5182 +  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
  6.5183 +  Enabling this option will implement the linux framebuffer device and
  6.5184 +  an fbcon color text console using calls to the STI BIOS routines.
  6.5185 +  The HP framebuffer device is sometimes planar, using a strange memory
  6.5186 +  layout, and changing the plane mask to create colored pixels
  6.5187 +  can require a call to the STI routines, so /dev/fb may not actually 
  6.5188 +  be useful.  However, on some systems packed pixel formats are supported.  
  6.5189 +  It is sufficient for basic text console functions, including fonts.
  6.5190 +
  6.5191 +  You should probably enable this option, unless you are having
  6.5192 +  trouble getting video when booting the kernel (make sure it isn't
  6.5193 +  just that you are running the console on the serial port, though).
  6.5194 +  Really old HP boxes may not have STI, and must use the PDC BIOS
  6.5195 +  console or the IODC BIOS.
  6.5196 +
  6.5197 +Select other compiled-in fonts
  6.5198 +CONFIG_FBCON_FONTS
  6.5199 +  Say Y here if you would like to use fonts other than the default
  6.5200 +  your frame buffer console usually use.
  6.5201 +
  6.5202 +  Note that the answer to this question won't directly affect the
  6.5203 +  kernel: saying N will just cause the configurator to skip all
  6.5204 +  the questions about foreign fonts.
  6.5205 +
  6.5206 +  If unsure, say N (the default choices are safe).
  6.5207 +
  6.5208 +VGA 8x16 font
  6.5209 +CONFIG_FONT_8x16
  6.5210 +  This is the "high resolution" font for the VGA frame buffer (the one
  6.5211 +  provided by the VGA text console 80x25 mode.
  6.5212 +
  6.5213 +  If unsure, say Y.
  6.5214 +
  6.5215 +Support only 8 pixels wide fonts
  6.5216 +CONFIG_FBCON_FONTWIDTH8_ONLY
  6.5217 +  Answer Y here will make the kernel provide only the 8x8 fonts (these
  6.5218 +  are the less readable).
  6.5219 +
  6.5220 +  If unsure, say N.
  6.5221 +
  6.5222 +Sparc console 8x16 font
  6.5223 +CONFIG_FONT_SUN8x16
  6.5224 +  This is the high resolution console font for Sun machines. Say Y.
  6.5225 +
  6.5226 +Sparc console 12x22 font (not supported by all drivers)
  6.5227 +CONFIG_FONT_SUN12x22
  6.5228 +  This is the high resolution console font for Sun machines with very
  6.5229 +  big letters (like the letters used in the SPARC PROM). If the
  6.5230 +  standard font is unreadable for you, say Y, otherwise say N.
  6.5231 +
  6.5232 +VGA 8x8 font
  6.5233 +CONFIG_FONT_8x8
  6.5234 +  This is the "high resolution" font for the VGA frame buffer (the one
  6.5235 +  provided by the text console 80x50 (and higher) modes).
  6.5236 +
  6.5237 +  Note that this is a poor quality font. The VGA 8x16 font is quite a
  6.5238 +  lot more readable.
  6.5239 +
  6.5240 +  Given the resolution provided by the frame buffer device, answer N
  6.5241 +  here is safe.
  6.5242 +
  6.5243 +Mac console 6x11 font (not supported by all drivers)
  6.5244 +CONFIG_FONT_6x11
  6.5245 +  Small console font with Macintosh-style high-half glyphs.  Some Mac
  6.5246 +  framebuffer drivers don't support this one at all.
  6.5247 +
  6.5248 +Pearl (old m68k) console 8x8 font
  6.5249 +CONFIG_FONT_PEARL_8x8
  6.5250 +  Small console font with PC-style control-character and high-half
  6.5251 +  glyphs.
  6.5252 +
  6.5253 +Acorn console 8x8 font
  6.5254 +CONFIG_FONT_ACORN_8x8
  6.5255 +  Small console font with PC-style control characters and high-half
  6.5256 +  glyphs.
  6.5257 +
  6.5258 +Backward compatibility mode for Xpmac
  6.5259 +CONFIG_FB_COMPAT_XPMAC
  6.5260 +  If you use the Xpmac X server (common with mklinux), you'll need to
  6.5261 +  say Y here to use X. You should consider changing to XFree86 which
  6.5262 +  includes a server that supports the frame buffer device directly
  6.5263 +  (XF68_FBDev).
  6.5264 +
  6.5265 +Hercules (HGA) mono graphics support
  6.5266 +CONFIG_FB_HGA
  6.5267 +  Say Y here if you have a Hercules mono graphics card.
  6.5268 +
  6.5269 +  This driver is also available as a module ( = code which can be
  6.5270 +  inserted and removed from the running kernel whenever you want).
  6.5271 +  The module will be called hgafb.o. If you want to compile it as
  6.5272 +  a module, say M here and read <file:Documentation/modules.txt>.
  6.5273 +
  6.5274 +  As this card technology is 15 years old, most people will answer N
  6.5275 +  here.
  6.5276 +
  6.5277 +Epson 1355 framebuffer support
  6.5278 +CONFIG_FB_E1355
  6.5279 +  Build in support for the SED1355 Epson Research Embedded RAMDAC
  6.5280 +  LCD/CRT Controller (since redesignated as the S1D13505) as a
  6.5281 +  framebuffer.  Product specs at
  6.5282 +  <http://www.erd.epson.com/vdc/html/products.htm>.
  6.5283 +
  6.5284 +Dreamcast Frame Buffer support
  6.5285 +CONFIG_FB_DC
  6.5286 +  Say Y here to enable support for the framebuffer on the Sega
  6.5287 +  Dreamcast.  This driver is also available as a module, dcfb.o.
  6.5288 +
  6.5289 +Register Base Address
  6.5290 +CONFIG_E1355_REG_BASE
  6.5291 +  Epson SED1355/S1D13505 LCD/CRT controller register base address.
  6.5292 +  See the manuals at
  6.5293 +  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  6.5294 +  discussion.
  6.5295 +
  6.5296 +Framebuffer Base Address
  6.5297 +CONFIG_E1355_FB_BASE
  6.5298 +  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
  6.5299 +  the manuals at
  6.5300 +  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  6.5301 +  discussion.
  6.5302 +
  6.5303 +NEC PowerVR 2 display support
  6.5304 +CONFIG_FB_PVR2
  6.5305 +  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
  6.5306 +  run linux on your Dreamcast, you will have to say Y here.
  6.5307 +  This driver may or may not work on other PowerVR 2 cards, but is
  6.5308 +  totally untested.  Use at your own risk.  If unsure, say N.
  6.5309 +
  6.5310 +  This driver is also available as a module ( = code which can be
  6.5311 +  inserted and removed from the running kernel whenever you want).
  6.5312 +  The module will be called pvr2fb.o.  If you want to compile it as
  6.5313 +  a module, say M here and read <file:Documentation/modules.txt>.
  6.5314 +
  6.5315 +  You can pass several parameters to the driver at boot time or at
  6.5316 +  module load time.  The parameters look like "video=pvr2:XXX", where
  6.5317 +  the meaning of XXX can be found at the end of the main source file
  6.5318 +  (<file:drivers/video/pvr2fb.c>). Please see the file
  6.5319 +  <file:Documentation/fb/pvr2fb.txt>.
  6.5320 +
  6.5321 +Debug pvr2fb
  6.5322 +CONFIG_FB_PVR2_DEBUG
  6.5323 +  Say Y here if you wish for the pvr2fb driver to print out debugging
  6.5324 +  messages. Most people will want to say N here. If unsure, you will
  6.5325 +  also want to say N.
  6.5326 +
  6.5327 +Matrox unified accelerated driver
  6.5328 +CONFIG_FB_MATROX
  6.5329 +  Say Y here if you have a Matrox Millennium, Millennium II, Mystique,
  6.5330 +  Mystique 220, Productiva G100, Mystique G200, Millennium G200,
  6.5331 +  Matrox G400, G450 or G550 card in your box. At this time, support for 
  6.5332 +  the G-series digital output is almost non-existant.
  6.5333 +
  6.5334 +  This driver is also available as a module ( = code which can be
  6.5335 +  inserted and removed from the running kernel whenever you want).
  6.5336 +  The module will be called matroxfb.o. If you want to compile it as
  6.5337 +  a module, say M here and read <file:Documentation/modules.txt>.
  6.5338 +
  6.5339 +  You can pass several parameters to the driver at boot time or at
  6.5340 +  module load time. The parameters look like "video=matrox:XXX", and
  6.5341 +  are described in <file:Documentation/fb/matroxfb.txt>.
  6.5342 +
  6.5343 +Matrox Millennium I/II support
  6.5344 +CONFIG_FB_MATROX_MILLENIUM
  6.5345 +  Say Y here if you have a Matrox Millennium or Matrox Millennium II
  6.5346 +  video card. If you select "Advanced lowlevel driver options" below,
  6.5347 +  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
  6.5348 +  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
  6.5349 +  also use font widths different from 8.
  6.5350 +
  6.5351 +Matrox Mystique support
  6.5352 +CONFIG_FB_MATROX_MYSTIQUE
  6.5353 +  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
  6.5354 +  video card. If you select "Advanced lowlevel driver options" below,
  6.5355 +  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  6.5356 +  packed pixel and 32 bpp packed pixel. You can also use font widths
  6.5357 +  different from 8.
  6.5358 +
  6.5359 +CONFIG_FB_MATROX_G450
  6.5360 +  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
  6.5361 +  video card. If you select "Advanced lowlevel driver options", you
  6.5362 +  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
  6.5363 +  pixel and 32 bpp packed pixel. You can also use font widths
  6.5364 +  different from 8.
  6.5365 +
  6.5366 +  If you need support for G400 secondary head, you must first say Y to
  6.5367 +  "I2C support" and "I2C bit-banging support" in the character devices
  6.5368 +  section, and then to "Matrox I2C support" and "G400 second head
  6.5369 +  support" here in the framebuffer section. G450/G550 secondary head
  6.5370 +  and digital output are supported without additional modules.
  6.5371 +  
  6.5372 +  The driver starts in monitor mode. You must use the matroxset tool 
  6.5373 +  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
  6.5374 +  swap primary and secondary head outputs, or to change output mode.  
  6.5375 +  Secondary head driver always start in 640x480 resolution and you 
  6.5376 +  must use fbset to change it.
  6.5377 +
  6.5378 +  Do not forget that second head supports only 16 and 32 bpp
  6.5379 +  packed pixels, so it is a good idea to compile them into the kernel
  6.5380 +  too. You can use only some font widths, as the driver uses generic
  6.5381 +  painting procedures (the secondary head does not use acceleration
  6.5382 +  engine).
  6.5383 +  
  6.5384 +  G450/G550 hardware can display TV picture only from secondary CRTC,
  6.5385 +  and it performs no scaling, so picture must have 525 or 625 lines.
  6.5386 +
  6.5387 +CONFIG_FB_MATROX_G100A
  6.5388 +  Say Y here if you have a Matrox G100, G200 or G400 based
  6.5389 +  video card. If you select "Advanced lowlevel driver options", you
  6.5390 +  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
  6.5391 +  pixel and 32 bpp packed pixel. You can also use font widths
  6.5392 +  different from 8.
  6.5393 +
  6.5394 +  If you need support for G400 secondary head, you must first say Y to
  6.5395 +  "I2C support" and "I2C bit-banging support" in the character devices
  6.5396 +  section, and then to "Matrox I2C support" and "G400 second head
  6.5397 +  support" here in the framebuffer section.
  6.5398 +
  6.5399 +CONFIG_FB_MATROX_I2C
  6.5400 +  This drivers creates I2C buses which are needed for accessing the
  6.5401 +  DDC (I2C) bus present on all Matroxes, an I2C bus which
  6.5402 +  interconnects Matrox optional devices, like MGA-TVO on G200 and
  6.5403 +  G400, and the secondary head DDC bus, present on G400 only.
  6.5404 +
  6.5405 +  You can say Y or M here if you want to experiment with monitor
  6.5406 +  detection code. You must say Y or M here if you want to use either
  6.5407 +  second head of G400 or MGA-TVO on G200 or G400.
  6.5408 +
  6.5409 +  If you compile it as module, it will create a module named
  6.5410 +  i2c-matroxfb.o.
  6.5411 +
  6.5412 +Matrox G400 second head support
  6.5413 +CONFIG_FB_MATROX_MAVEN
  6.5414 +  WARNING !!! This support does not work with G450 !!!
  6.5415 +
  6.5416 +  Say Y or M here if you want to use a secondary head (meaning two
  6.5417 +  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
  6.5418 +  head is not compatible with accelerated XFree 3.3.x SVGA servers -
  6.5419 +  secondary head output is blanked while you are in X. With XFree
  6.5420 +  3.9.17 preview you can use both heads if you use SVGA over fbdev or
  6.5421 +  the fbdev driver on first head and the fbdev driver on second head.
  6.5422 +
  6.5423 +  If you compile it as module, two modules are created,
  6.5424 +  matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
  6.5425 +  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
  6.5426 +  also load i2c-matroxfb to get it to run.
  6.5427 +
  6.5428 +  The driver starts in monitor mode and you must use the matroxset
  6.5429 +  tool (available at
  6.5430 +  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
  6.5431 +  PAL or NTSC or to swap primary and secondary head outputs.
  6.5432 +  Secondary head driver also always start in 640x480 resolution, you
  6.5433 +  must use fbset to change it.
  6.5434 +
  6.5435 +  Also do not forget that second head supports only 16 and 32 bpp
  6.5436 +  packed pixels, so it is a good idea to compile them into the kernel
  6.5437 +  too.  You can use only some font widths, as the driver uses generic
  6.5438 +  painting procedures (the secondary head does not use acceleration
  6.5439 +  engine).
  6.5440 +
  6.5441 +CONFIG_FB_MATROX_PROC
  6.5442 +  Say Y or M here if you want to access some informations about driver
  6.5443 +  state through /proc interface.
  6.5444 +  
  6.5445 +  You should download matrox_pins tool (available at
  6.5446 +  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to get human
  6.5447 +  readable output.
  6.5448 +  
  6.5449 +CONFIG_FB_MATROX_MULTIHEAD
  6.5450 +  Say Y here if you have more than one (supported) Matrox device in
  6.5451 +  your computer and you want to use all of them for different monitors
  6.5452 +  ("multihead"). If you have only one device, you should say N because
  6.5453 +  the driver compiled with Y is larger and a bit slower, especially on
  6.5454 +  ia32 (ix86).
  6.5455 +
  6.5456 +  If you said M to "Matrox unified accelerated driver" and N here, you
  6.5457 +  will still be able to use several Matrox devices simultaneously:
  6.5458 +  insert several instances of the module matroxfb.o into the kernel
  6.5459 +  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
  6.5460 +  for the different Matrox devices. This method is slightly faster but
  6.5461 +  uses 40 KB of kernel memory per Matrox card.
  6.5462 +
  6.5463 +  There is no need for enabling 'Matrox multihead support' if you have
  6.5464 +  only one Matrox card in the box.
  6.5465 +
  6.5466 +3Dfx Voodoo Graphics / Voodoo2 frame buffer support
  6.5467 +CONFIG_FB_VOODOO1
  6.5468 +  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
  6.5469 +  Voodoo2 (cvg) based graphics card.
  6.5470 +
  6.5471 +  This driver is also available as a module ( = code which can be 
  6.5472 +  inserted and removed from the running kernel whenever you want).
  6.5473 +  The module will be called sstfb.o. If you want to compile it as
  6.5474 +  a module, say M here and read Documentation/modules.txt.
  6.5475 +
  6.5476 +  WARNING: Do not use any application that uses the 3D engine
  6.5477 +  (namely glide) while using this driver.
  6.5478 +  Please read the file Documentation/fb/README-sstfb.txt for supported
  6.5479 +  options and other important info  support.
  6.5480 +
  6.5481 +MDA text console (dual-headed)
  6.5482 +CONFIG_MDA_CONSOLE
  6.5483 +  Say Y here if you have an old MDA or monochrome Hercules graphics
  6.5484 +  adapter in your system acting as a second head ( = video card). You
  6.5485 +  will then be able to use two monitors with your Linux system. Do not
  6.5486 +  say Y here if your MDA card is the primary card in your system; the
  6.5487 +  normal VGA driver will handle it.
  6.5488 +
  6.5489 +  This driver is also available as a module ( = code which can be
  6.5490 +  inserted and removed from the running kernel whenever you want).
  6.5491 +  The module will be called mdacon.o. If you want to compile it as
  6.5492 +  a module, say M here and read <file:Documentation/modules.txt>.
  6.5493 +
  6.5494 +  If unsure, say N.
  6.5495 +
  6.5496 +SBUS and UPA framebuffers
  6.5497 +CONFIG_FB_SBUS
  6.5498 +  Say Y if you want support for SBUS or UPA based frame buffer device.
  6.5499 +
  6.5500 +Creator/Creator3D support
  6.5501 +CONFIG_FB_CREATOR
  6.5502 +  This is the frame buffer device driver for the Creator and Creator3D
  6.5503 +  graphics boards.
  6.5504 +
  6.5505 +CGsix (GX,TurboGX) support
  6.5506 +CONFIG_FB_CGSIX
  6.5507 +  This is the frame buffer device driver for the CGsix (GX, TurboGX)
  6.5508 +  frame buffer.
  6.5509 +
  6.5510 +BWtwo support
  6.5511 +CONFIG_FB_BWTWO
  6.5512 +  This is the frame buffer device driver for the BWtwo frame buffer.
  6.5513 +
  6.5514 +CGthree support
  6.5515 +CONFIG_FB_CGTHREE
  6.5516 +  This is the frame buffer device driver for the CGthree frame buffer.
  6.5517 +
  6.5518 +CGfourteen (SX) support
  6.5519 +CONFIG_FB_CGFOURTEEN
  6.5520 +  This is the frame buffer device driver for the CGfourteen frame
  6.5521 +  buffer on Desktop SPARCsystems with the SX graphics option.
  6.5522 +
  6.5523 +P9100 (Sparcbook 3 only) support
  6.5524 +CONFIG_FB_P9100
  6.5525 +  This is the frame buffer device driver for the P9100 card
  6.5526 +  supported on Sparcbook 3 machines.
  6.5527 +
  6.5528 +Leo (ZX) support
  6.5529 +CONFIG_FB_LEO
  6.5530 +  This is the frame buffer device driver for the SBUS-based Sun ZX
  6.5531 +  (leo) frame buffer cards.
  6.5532 +
  6.5533 +IGA 168x display support
  6.5534 +CONFIG_FB_IGA
  6.5535 +  This is the framebuffer device for the INTERGRAPHICS 1680 and
  6.5536 +  successor frame buffer cards.
  6.5537 +
  6.5538 +TCX (SS4/SS5 only) support
  6.5539 +CONFIG_FB_TCX
  6.5540 +  This is the frame buffer device driver for the TCX 24/8bit frame
  6.5541 +  buffer.
  6.5542 +
  6.5543 +HD64461 Frame Buffer support
  6.5544 +CONFIG_FB_HIT
  6.5545 +  This is the frame buffer device driver for the Hitachi HD64461 LCD
  6.5546 +  frame buffer card.
  6.5547 +
  6.5548 +SIS display support
  6.5549 +CONFIG_FB_SIS
  6.5550 +  This is the frame buffer device driver for the SiS 300, 315 and 330
  6.5551 +  series chipsets.  Documentation available at the maintainer's site
  6.5552 +  at <http://www.winischhofer.net/linuxsisvga.shtml>.
  6.5553 +
  6.5554 +SIS 300 series support
  6.5555 +CONFIG_FB_SIS_300
  6.5556 +  This enables support for SiS 300 series chipsets (300/305, 540, 630,
  6.5557 +  730).  Documentation available at the maintainer's website at
  6.5558 +   <http://www.winischhofer.net/linuxsisvga.shtml>.
  6.5559 +
  6.5560 +SIS 315/330 series support
  6.5561 +CONFIG_FB_SIS_315
  6.5562 +  This enables support for SiS 315/330 series chipsets (315, 550, 650,
  6.5563 +  M650, 651, 661FX, M661FX, 740, 741, 330). Documentation available at
  6.5564 +  the maintainer's site <http://www.winischhofer.net/linuxsisvga.shtml>.
  6.5565 +
  6.5566 +IMS Twin Turbo display support
  6.5567 +CONFIG_FB_IMSTT
  6.5568 +  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
  6.5569 +  many Macintosh and compatible computers.
  6.5570 +
  6.5571 +CONFIG_FB_TX3912
  6.5572 +  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core;
  6.5573 +  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  6.5574 +
  6.5575 +  Say Y here to enable kernel support for the on-board framebuffer.
  6.5576 +
  6.5577 +Virtual Frame Buffer support (ONLY FOR TESTING!)
  6.5578 +CONFIG_FB_VIRTUAL
  6.5579 +  This is a `virtual' frame buffer device. It operates on a chunk of
  6.5580 +  unswappable kernel memory instead of on the memory of a graphics
  6.5581 +  board. This means you cannot see any output sent to this frame
  6.5582 +  buffer device, while it does consume precious memory. The main use
  6.5583 +  of this frame buffer device is testing and debugging the frame
  6.5584 +  buffer subsystem. Do NOT enable it for normal systems! To protect
  6.5585 +  the innocent, it has to be enabled explicitly at boot time using the
  6.5586 +  kernel option `video=vfb:'.
  6.5587 +
  6.5588 +  This driver is also available as a module ( = code which can be
  6.5589 +  inserted and removed from the running kernel whenever you want). The
  6.5590 +  module will be called vfb.o. If you want to compile it as a module,
  6.5591 +  say M here and read <file:Documentation/modules.txt>.
  6.5592 +
  6.5593 +  If unsure, say N.
  6.5594 +
  6.5595 +Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
  6.5596 +CONFIG_FB_ATY_CT
  6.5597 +  Say Y here to support use of ATI's 64-bit Rage boards (or other
  6.5598 +  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
  6.5599 +  framebuffer device.  The ATI product support page for these boards
  6.5600 +  is at <http://support.ati.com/products/pc/mach64/>.
  6.5601 +
  6.5602 +Sony Vaio Picturebook laptop LCD panel support
  6.5603 +CONFIG_FB_ATY_CT_VAIO_LCD
  6.5604 +  Say Y here if you want to use the full width of the Sony Vaio 
  6.5605 +  Picturebook laptops LCD panels (you will get a 128x30 console).
  6.5606 +
  6.5607 +  Note that you need to activate this mode using the 'vga=0x301'
  6.5608 +  option from your boot loader (lilo or loadlin).  See the
  6.5609 +  documentation of your boot loader about how to pass options to the
  6.5610 +  kernel.
  6.5611 +  
  6.5612 +Mach64 GX support
  6.5613 +CONFIG_FB_ATY_GX
  6.5614 +  Say Y here to support use of the ATI Mach64 Graphics Expression
  6.5615 +  board (or other boards based on the Mach64 GX chipset) as a
  6.5616 +  framebuffer device.  The ATI product support page for these boards
  6.5617 +  is at
  6.5618 +  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  6.5619 +
  6.5620 +Mach64 Generic LCD support
  6.5621 +CONFIG_FB_ATY_GENERIC_LCD
  6.5622 +  Enabling this option enables the Atyfb driver to drive LCD panels. It
  6.5623 +  will autodetect the resulution and format of your display and emulate
  6.5624 +  other resolutions using the hardware stretcher on the chip.
  6.5625 +  Say Y here if you have computer with a Rage LT Pro, Rage Mobility M1,
  6.5626 +  Rage XC or Rage XL chip and a laptop LCD display or any other LCD display
  6.5627 +  that needs to be digitally driven. It is not necessary to enable this
  6.5628 +  option if you are using an LCD display with a normal VGA connector,
  6.5629 +  but it won't hurt if you do.
  6.5630 +
  6.5631 +ATI Radeon display support
  6.5632 +CONFIG_FB_RADEON
  6.5633 +  Choose this option if you want to use an ATI Radeon graphics card as
  6.5634 +  a framebuffer device.  There are both PCI and AGP versions.  You
  6.5635 +  don't need to choose this to run the Radeon in plain VGA mode.
  6.5636 +  There is a product page at
  6.5637 +  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
  6.5638 +
  6.5639 +SA-1100 LCD support
  6.5640 +CONFIG_FB_SA1100
  6.5641 +  This is a framebuffer device for the SA-1100 LCD Controller.
  6.5642 +  See <http://www.linux-fbdev.org/> for information on framebuffer
  6.5643 +  devices.
  6.5644 +
  6.5645 +  If you plan to use the LCD display with your SA-1100 system, say
  6.5646 +  Y here.
  6.5647 +
  6.5648 +Advanced low level driver options
  6.5649 +CONFIG_FBCON_ADVANCED
  6.5650 +  The frame buffer console uses character drawing routines that are
  6.5651 +  tailored to the specific organization of pixels in the memory of
  6.5652 +  your graphics hardware. These are called the low level frame buffer
  6.5653 +  console drivers. Note that they are used for text console output
  6.5654 +  only; they are NOT needed for graphical applications.
  6.5655 +
  6.5656 +  If you say N here, the needed low level drivers are automatically
  6.5657 +  enabled, depending on what frame buffer devices you selected above.
  6.5658 +  This is recommended for most users.
  6.5659 +
  6.5660 +  If you say Y here, you have more fine-grained control over which low
  6.5661 +  level drivers are enabled. You can e.g. leave out low level drivers
  6.5662 +  for color depths you do not intend to use for text consoles.
  6.5663 +
  6.5664 +  Low level frame buffer console drivers can be modules ( = code which
  6.5665 +  can be inserted and removed from the running kernel whenever you
  6.5666 +  want). The modules will be called fbcon-*.o. If you want to compile
  6.5667 +  (some of) them as modules, read <file:Documentation/modules.txt>.
  6.5668 +
  6.5669 +  If unsure, say N.
  6.5670 +
  6.5671 +Monochrome support
  6.5672 +CONFIG_FBCON_MFB
  6.5673 +  This is the low level frame buffer console driver for monochrome
  6.5674 +  (2 colors) packed pixels.
  6.5675 +
  6.5676 +2 bpp packed pixels support
  6.5677 +CONFIG_FBCON_CFB2
  6.5678 +  This is the low level frame buffer console driver for 2 bits per
  6.5679 +  pixel (4 colors) packed pixels.
  6.5680 +
  6.5681 +4 bpp packed pixels support
  6.5682 +CONFIG_FBCON_CFB4
  6.5683 +  This is the low level frame buffer console driver for 4 bits per
  6.5684 +  pixel (16 colors) packed pixels.
  6.5685 +
  6.5686 +8 bpp packed pixels support
  6.5687 +CONFIG_FBCON_CFB8
  6.5688 +  This is the low level frame buffer console driver for 8 bits per
  6.5689 +  pixel (256 colors) packed pixels.
  6.5690 +
  6.5691 +16 bpp packed pixels support
  6.5692 +CONFIG_FBCON_CFB16
  6.5693 +  This is the low level frame buffer console driver for 15 or 16 bits
  6.5694 +  per pixel (32K or 64K colors, also known as `hicolor') packed
  6.5695 +  pixels.
  6.5696 +
  6.5697 +24 bpp packed pixels support
  6.5698 +CONFIG_FBCON_CFB24
  6.5699 +  This is the low level frame buffer console driver for 24 bits per
  6.5700 +  pixel (16M colors, also known as `truecolor') packed pixels. It is
  6.5701 +  NOT for `sparse' 32 bits per pixel mode.
  6.5702 +
  6.5703 +32 bpp packed pixels support
  6.5704 +CONFIG_FBCON_CFB32
  6.5705 +  This is the low level frame buffer console driver for 32 bits per
  6.5706 +  pixel (16M colors, also known as `truecolor') sparse packed pixels.
  6.5707 +
  6.5708 +Amiga bitplanes support
  6.5709 +CONFIG_FBCON_AFB
  6.5710 +  This is the low level frame buffer console driver for 1 to 8
  6.5711 +  bitplanes (2 to 256 colors) on Amiga.
  6.5712 +
  6.5713 +Amiga interleaved bitplanes support
  6.5714 +CONFIG_FBCON_ILBM
  6.5715 +  This is the low level frame buffer console driver for 1 to 8
  6.5716 +  interleaved bitplanes (2 to 256 colors) on Amiga.
  6.5717 +
  6.5718 +Atari interleaved bitplanes (2 planes) support
  6.5719 +CONFIG_FBCON_IPLAN2P2
  6.5720 +  This is the low level frame buffer console driver for 2 interleaved
  6.5721 +  bitplanes (4 colors) on Atari.
  6.5722 +
  6.5723 +Atari interleaved bitplanes (4 planes) support
  6.5724 +CONFIG_FBCON_IPLAN2P4
  6.5725 +  This is the low level frame buffer console driver for 4 interleaved
  6.5726 +  bitplanes (16 colors) on Atari.
  6.5727 +
  6.5728 +Atari interleaved bitplanes (8 planes) support
  6.5729 +CONFIG_FBCON_IPLAN2P8
  6.5730 +  This is the low level frame buffer console driver for 8 interleaved
  6.5731 +  bitplanes (256 colors) on Atari.
  6.5732 +
  6.5733 +Mac variable bpp packed pixels support
  6.5734 +CONFIG_FBCON_MAC
  6.5735 +  This is the low level frame buffer console driver for 1/2/4/8/16/32
  6.5736 +  bits per pixel packed pixels on Mac. It supports variable font
  6.5737 +  widths for low resolution screens.
  6.5738 +
  6.5739 +Permedia3 support (EXPERIMENTAL)
  6.5740 +CONFIG_FB_PM3
  6.5741 +  This is the frame buffer device driver for the 3DLabs Permedia3
  6.5742 +  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  6.5743 +  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  6.5744 +  and maybe other boards.
  6.5745 +
  6.5746 +HGA monochrome support
  6.5747 +CONFIG_FBCON_HGA
  6.5748 +  This is the low level frame buffer console driver for Hercules mono
  6.5749 +  graphics cards.
  6.5750 +
  6.5751 +VGA characters/attributes support
  6.5752 +CONFIG_FBCON_VGA
  6.5753 +  This is the low level frame buffer console driver for VGA text mode;
  6.5754 +  it is used by frame buffer device drivers that support VGA text
  6.5755 +  mode.
  6.5756 +
  6.5757 +Parallel-port support
  6.5758 +CONFIG_PARPORT
  6.5759 +  If you want to use devices connected to your machine's parallel port
  6.5760 +  (the connector at the computer with 25 holes), e.g. printer, ZIP
  6.5761 +  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
  6.5762 +  create a mini network by connecting the parallel ports of two local
  6.5763 +  machines) etc., then you need to say Y here; please read
  6.5764 +  <file:Documentation/parport.txt> and
  6.5765 +  <file:drivers/parport/BUGS-parport>.
  6.5766 +
  6.5767 +  For extensive information about drivers for many devices attaching
  6.5768 +  to the parallel port see <http://www.torque.net/linux-pp.html> on
  6.5769 +  the WWW.
  6.5770 +
  6.5771 +  It is possible to share a single parallel port among several devices
  6.5772 +  and it is safe to compile all the corresponding drivers into the
  6.5773 +  kernel.  If you want to compile parallel port support as a module
  6.5774 +  ( = code which can be inserted in and removed from the running
  6.5775 +  kernel whenever you want), say M here and read
  6.5776 +  <file:Documentation/modules.txt>.  The module will be called
  6.5777 +  parport.o.  If you have more than one parallel port and want to
  6.5778 +  specify which port and IRQ to be used by this driver at module load
  6.5779 +  time, take a look at <file:Documentation/parport.txt>.
  6.5780 +
  6.5781 +  If unsure, say Y.
  6.5782 +
  6.5783 +PC-style hardware
  6.5784 +CONFIG_PARPORT_PC
  6.5785 +  You should say Y here if you have a PC-style parallel port. All IBM
  6.5786 +  PC compatible computers and some Alphas have PC-style parallel
  6.5787 +  ports.
  6.5788 +
  6.5789 +  This code is also available as a module.  If you want to compile it
  6.5790 +  as a module ( = code which can be inserted in and removed from the
  6.5791 +  running kernel whenever you want), say M here and read
  6.5792 +  <file:Documentation/modules.txt>.  The module will be called
  6.5793 +  parport_pc.o.
  6.5794 +
  6.5795 +  If unsure, say Y.
  6.5796 +
  6.5797 +Parallel+serial PCI multi-IO card support
  6.5798 +CONFIG_PARPORT_SERIAL
  6.5799 +  This adds support for multi-IO PCI cards that have parallel and
  6.5800 +  serial ports.  You should say Y or M here.  If you say M, the module
  6.5801 +  will be called parport_serial.o.
  6.5802 +
  6.5803 +Use FIFO/DMA if available
  6.5804 +CONFIG_PARPORT_PC_FIFO
  6.5805 +  Many parallel port chipsets provide hardware that can speed up
  6.5806 +  printing. Say Y here if you want to take advantage of that.
  6.5807 +
  6.5808 +  As well as actually having a FIFO, or DMA capability, the kernel
  6.5809 +  will need to know which IRQ the parallel port has.  By default,
  6.5810 +  parallel port interrupts will not be used, and so neither will the
  6.5811 +  FIFO.  See <file:Documentation/parport.txt> to find out how to
  6.5812 +  specify which IRQ/DMA to use.
  6.5813 +
  6.5814 +SuperIO chipset support
  6.5815 +CONFIG_PARPORT_PC_SUPERIO
  6.5816 +  Saying Y here enables some probes for Super-IO chipsets in order to
  6.5817 +  find out things like base addresses, IRQ lines and DMA channels.  It
  6.5818 +  is safe to say N.
  6.5819 +
  6.5820 +Support for PCMCIA management for PC-style ports
  6.5821 +CONFIG_PARPORT_PC_PCMCIA
  6.5822 +  Say Y here if you need PCMCIA support for your PC-style parallel
  6.5823 +  ports. If unsure, say N.
  6.5824 +
  6.5825 +  This driver is also available as a module ( = code which can be
  6.5826 +  inserted in and removed from the running kernel whenever you want).
  6.5827 +  If you want to compile it as a module, say M here and read
  6.5828 +  <file:Documentation/modules.txt>. The module will be called
  6.5829 +  parport_cs.o
  6.5830 +
  6.5831 +Support foreign hardware
  6.5832 +CONFIG_PARPORT_OTHER
  6.5833 +  Say Y here if you want to be able to load driver modules to support
  6.5834 +  other non-standard types of parallel ports. This causes a
  6.5835 +  performance loss, so most people say N.
  6.5836 +
  6.5837 +Amiga built-in parallel port support
  6.5838 +CONFIG_PARPORT_AMIGA
  6.5839 +  Say Y here if you need support for the parallel port hardware on
  6.5840 +  Amiga machines. This code is also available as a module (say M),
  6.5841 +  called parport_amiga.o. If in doubt, saying N is the safe plan.
  6.5842 +
  6.5843 +Atari built-in parallel port support
  6.5844 +CONFIG_PARPORT_ATARI
  6.5845 +  Say Y here if you need support for the parallel port hardware on
  6.5846 +  Atari machines. This code is also available as a module (say M),
  6.5847 +  called parport_atari.o. If in doubt, saying N is the safe plan.
  6.5848 +
  6.5849 +Multiface III parallel port support
  6.5850 +CONFIG_PARPORT_MFC3
  6.5851 +  Say Y here if you need parallel port support for the MFC3 card.
  6.5852 +  This code is also available as a module (say M), called
  6.5853 +  parport_mfc3.o. If in doubt, saying N is the safe plan.
  6.5854 +
  6.5855 +Support IEEE 1284 status readback
  6.5856 +CONFIG_PRINTER_READBACK
  6.5857 +  If you have a device on your parallel port that support this
  6.5858 +  protocol, this option will allow the device to report its status. It
  6.5859 +  is safe to say Y.
  6.5860 +
  6.5861 +IEEE 1284 transfer modes
  6.5862 +CONFIG_PARPORT_1284
  6.5863 +  If you have a printer that supports status readback or device ID, or
  6.5864 +  want to use a device that uses enhanced parallel port transfer modes
  6.5865 +  such as EPP and ECP, say Y here to enable advanced IEEE 1284
  6.5866 +  transfer modes. Also say Y if you want device ID information to
  6.5867 +  appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
  6.5868 +
  6.5869 +Enable loadable module support
  6.5870 +CONFIG_MODULES
  6.5871 +  Kernel modules are small pieces of compiled code which can be
  6.5872 +  inserted in or removed from the running kernel, using the programs
  6.5873 +  insmod and rmmod. This is described in the file
  6.5874 +  <file:Documentation/modules.txt>, including the fact that you have
  6.5875 +  to say "make modules" in order to compile the modules that you chose
  6.5876 +  during kernel configuration.  Modules can be device drivers, file
  6.5877 +  systems, binary executable formats, and so on. If you think that you
  6.5878 +  may want to make use of modules with this kernel in the future, then
  6.5879 +  say Y here.  If unsure, say Y.
  6.5880 +
  6.5881 +Set version information on all symbols for modules
  6.5882 +CONFIG_MODVERSIONS
  6.5883 +  Usually, modules have to be recompiled whenever you switch to a new
  6.5884 +  kernel.  Saying Y here makes it possible, and safe, to use the
  6.5885 +  same modules even after compiling a new kernel; this requires the
  6.5886 +  program modprobe. All the software needed for module support is in
  6.5887 +  the modutils package (check the file <file:Documentation/Changes>
  6.5888 +  for location and latest version).  NOTE: if you say Y here but don't
  6.5889 +  have the program genksyms (which is also contained in the above
  6.5890 +  mentioned modutils package), then the building of your kernel will
  6.5891 +  fail.  If you are going to use modules that are generated from
  6.5892 +  non-kernel sources, you would benefit from this option.  Otherwise
  6.5893 +  it's not that important.  So, N ought to be a safe bet.
  6.5894 +
  6.5895 +Kernel module loader support
  6.5896 +CONFIG_KMOD
  6.5897 +  Normally when you have selected some drivers and/or file systems to
  6.5898 +  be created as loadable modules, you also have the responsibility to
  6.5899 +  load the corresponding modules (using the programs insmod or
  6.5900 +  modprobe) before you can use them. If you say Y here however, the
  6.5901 +  kernel will be able to load modules for itself: when a part of the
  6.5902 +  kernel needs a module, it runs modprobe with the appropriate
  6.5903 +  arguments, thereby loading the module if it is available. (This is a
  6.5904 +  replacement for kerneld.) Say Y here and read about configuring it
  6.5905 +  in <file:Documentation/kmod.txt>.
  6.5906 +
  6.5907 +ARP daemon support
  6.5908 +CONFIG_ARPD
  6.5909 +  Normally, the kernel maintains an internal cache which maps IP
  6.5910 +  addresses to hardware addresses on the local network, so that
  6.5911 +  Ethernet/Token Ring/ etc. frames are sent to the proper address on
  6.5912 +  the physical networking layer. For small networks having a few
  6.5913 +  hundred directly connected hosts or less, keeping this address
  6.5914 +  resolution (ARP) cache inside the kernel works well. However,
  6.5915 +  maintaining an internal ARP cache does not work well for very large
  6.5916 +  switched networks, and will use a lot of kernel memory if TCP/IP
  6.5917 +  connections are made to many machines on the network.
  6.5918 +
  6.5919 +  If you say Y here, the kernel's internal ARP cache will never grow
  6.5920 +  to more than 256 entries (the oldest entries are expired in a LIFO
  6.5921 +  manner) and communication will be attempted with the user space ARP
  6.5922 +  daemon arpd. Arpd then answers the address resolution request either
  6.5923 +  from its own cache or by asking the net.
  6.5924 +
  6.5925 +  This code is experimental and also obsolete. If you want to use it,
  6.5926 +  you need to find a version of the daemon arpd on the net somewhere,
  6.5927 +  and you should also say Y to "Kernel/User network link driver",
  6.5928 +  below. If unsure, say N.
  6.5929 +
  6.5930 +TCP/IP networking
  6.5931 +CONFIG_INET
  6.5932 +  These are the protocols used on the Internet and on most local
  6.5933 +  Ethernets. It is highly recommended to say Y here (this will enlarge
  6.5934 +  your kernel by about 144 KB), since some programs (e.g. the X window
  6.5935 +  system) use TCP/IP even if your machine is not connected to any
  6.5936 +  other computer. You will get the so-called loopback device which
  6.5937 +  allows you to ping yourself (great fun, that!).
  6.5938 +
  6.5939 +  For an excellent introduction to Linux networking, please read the
  6.5940 +  NET-3-HOWTO, available from
  6.5941 +  <http://www.tldp.org/docs.html#howto>.
  6.5942 +
  6.5943 +  This option is also necessary if you want to use the full power of
  6.5944 +  term (term is a program which gives you almost full Internet
  6.5945 +  connectivity if you have a regular dial up shell account on some
  6.5946 +  Internet connected Unix computer; for more information, read
  6.5947 +  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
  6.5948 +
  6.5949 +  If you say Y here and also to "/proc file system support" and
  6.5950 +  "Sysctl support" below, you can change various aspects of the
  6.5951 +  behaviour of the TCP/IP code by writing to the (virtual) files in
  6.5952 +  /proc/sys/net/ipv4/*; the options are explained in the file
  6.5953 +  <file:Documentation/networking/ip-sysctl.txt>.
  6.5954 +
  6.5955 +  Short answer: say Y.
  6.5956 +
  6.5957 +IP multicasting
  6.5958 +CONFIG_IP_MULTICAST
  6.5959 +  This is code for addressing several networked computers at once,
  6.5960 +  enlarging your kernel by about 2 KB. You need multicasting if you
  6.5961 +  intend to participate in the MBONE, a high bandwidth network on top
  6.5962 +  of the Internet which carries audio and video broadcasts. More
  6.5963 +  information about the MBONE is on the WWW at
  6.5964 +  <http://www-itg.lbl.gov/mbone/>. Information about the multicast
  6.5965 +  capabilities of the various network cards is contained in
  6.5966 +  <file:Documentation/networking/multicast.txt>. For most people, it's
  6.5967 +  safe to say N.
  6.5968 +
  6.5969 +Advanced router
  6.5970 +CONFIG_IP_ADVANCED_ROUTER
  6.5971 +  If you intend to run your Linux box mostly as a router, i.e. as a
  6.5972 +  computer that forwards and redistributes network packets, say Y; you
  6.5973 +  will then be presented with several options that allow more precise
  6.5974 +  control about the routing process.
  6.5975 +
  6.5976 +  The answer to this question won't directly affect the kernel:
  6.5977 +  answering N will just cause the configurator to skip all the
  6.5978 +  questions about advanced routing.
  6.5979 +
  6.5980 +  Note that your box can only act as a router if you enable IP
  6.5981 +  forwarding in your kernel; you can do that by saying Y to "/proc
  6.5982 +  file system support" and "Sysctl support" below and executing the
  6.5983 +  line
  6.5984 +
  6.5985 +    echo "1" > /proc/sys/net/ipv4/ip_forward
  6.5986 +
  6.5987 +  at boot time after the /proc file system has been mounted.
  6.5988 +
  6.5989 +  If you turn on IP forwarding, you will also get the rp_filter, which
  6.5990 +  automatically rejects incoming packets if the routing table entry
  6.5991 +  for their source address doesn't match the network interface they're
  6.5992 +  arriving on. This has security advantages because it prevents the
  6.5993 +  so-called IP spoofing, however it can pose problems if you use
  6.5994 +  asymmetric routing (packets from you to a host take a different path
  6.5995 +  than packets from that host to you) or if you operate a non-routing
  6.5996 +  host which has several IP addresses on different interfaces. To turn
  6.5997 +  rp_filter off use:
  6.5998 +
  6.5999 +        echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
  6.6000 +  or
  6.6001 +        echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
  6.6002 +
  6.6003 +  If unsure, say N here.
  6.6004 +
  6.6005 +Policy routing
  6.6006 +CONFIG_IP_MULTIPLE_TABLES
  6.6007 +  Normally, a router decides what to do with a received packet based
  6.6008 +  solely on the packet's final destination address. If you say Y here,
  6.6009 +  the Linux router will also be able to take the packet's source
  6.6010 +  address into account. Furthermore, if you also say Y to "Use TOS
  6.6011 +  value as routing key" below, the TOS (Type-Of-Service) field of the
  6.6012 +  packet can be used for routing decisions as well. In addition, if
  6.6013 +  you say Y here and to "Fast network address translation" below,
  6.6014 +  the router will also be able to modify source and destination
  6.6015 +  addresses of forwarded packets.
  6.6016 +
  6.6017 +  If you are interested in this, please see the preliminary
  6.6018 +  documentation at <http://www.compendium.com.ar/policy-routing.txt>
  6.6019 +  and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
  6.6020 +  You will need supporting software from
  6.6021 +  <ftp://ftp.inr.ac.ru/ip-routing/>.
  6.6022 +
  6.6023 +  If unsure, say N.
  6.6024 +
  6.6025 +Equal cost multipath
  6.6026 +CONFIG_IP_ROUTE_MULTIPATH
  6.6027 +  Normally, the routing tables specify a single action to be taken in
  6.6028 +  a deterministic manner for a given packet. If you say Y here
  6.6029 +  however, it becomes possible to attach several actions to a packet
  6.6030 +  pattern, in effect specifying several alternative paths to travel
  6.6031 +  for those packets. The router considers all these paths to be of
  6.6032 +  equal "cost" and chooses one of them in a non-deterministic fashion
  6.6033 +  if a matching packet arrives.
  6.6034 +
  6.6035 +Use TOS value as routing key
  6.6036 +CONFIG_IP_ROUTE_TOS
  6.6037 +  The header of every IP packet carries a TOS (Type Of Service) value
  6.6038 +  with which the packet requests a certain treatment, e.g. low
  6.6039 +  latency (for interactive traffic), high throughput, or high
  6.6040 +  reliability.  If you say Y here, you will be able to specify
  6.6041 +  different routes for packets with different TOS values.
  6.6042 +
  6.6043 +Use netfilter MARK value as routing key
  6.6044 +CONFIG_IP_ROUTE_FWMARK
  6.6045 +  If you say Y here, you will be able to specify different routes for
  6.6046 +  packets with different mark values (see iptables(8), MARK target).
  6.6047 +
  6.6048 +Verbose route monitoring
  6.6049 +CONFIG_IP_ROUTE_VERBOSE
  6.6050 +  If you say Y here, which is recommended, then the kernel will print
  6.6051 +  verbose messages regarding the routing, for example warnings about
  6.6052 +  received packets which look strange and could be evidence of an
  6.6053 +  attack or a misconfigured system somewhere. The information is
  6.6054 +  handled by the klogd daemon which is responsible for kernel messages
  6.6055 +  ("man klogd").
  6.6056 +
  6.6057 +Fast network address translation
  6.6058 +CONFIG_IP_ROUTE_NAT
  6.6059 +  If you say Y here, your router will be able to modify source and
  6.6060 +  destination addresses of packets that pass through it, in a manner
  6.6061 +  you specify.  General information about Network Address Translation
  6.6062 +  can be gotten from the document
  6.6063 +  <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
  6.6064 +
  6.6065 +Kernel level IP autoconfiguration
  6.6066 +CONFIG_IP_PNP
  6.6067 +  This enables automatic configuration of IP addresses of devices and
  6.6068 +  of the routing table during kernel boot, based on either information
  6.6069 +  supplied on the kernel command line or by BOOTP or RARP protocols.
  6.6070 +  You need to say Y only for diskless machines requiring network
  6.6071 +  access to boot (in which case you want to say Y to "Root file system
  6.6072 +  on NFS" as well), because all other machines configure the network
  6.6073 +  in their startup scripts.
  6.6074 +
  6.6075 +BOOTP support
  6.6076 +CONFIG_IP_PNP_BOOTP
  6.6077 +  If you want your Linux box to mount its whole root file system (the
  6.6078 +  one containing the directory /) from some other computer over the
  6.6079 +  net via NFS and you want the IP address of your computer to be
  6.6080 +  discovered automatically at boot time using the BOOTP protocol (a
  6.6081 +  special protocol designed for doing this job), say Y here. In case
  6.6082 +  the boot ROM of your network card was designed for booting Linux and
  6.6083 +  does BOOTP itself, providing all necessary information on the kernel
  6.6084 +  command line, you can say N here. If unsure, say Y. Note that if you
  6.6085 +  want to use BOOTP, a BOOTP server must be operating on your network.
  6.6086 +  Read <file:Documentation/nfsroot.txt> for details.
  6.6087 +
  6.6088 +DHCP support
  6.6089 +CONFIG_IP_PNP_DHCP
  6.6090 +  If you want your Linux box to mount its whole root file system (the
  6.6091 +  one containing the directory /) from some other computer over the
  6.6092 +  net via NFS and you want the IP address of your computer to be
  6.6093 +  discovered automatically at boot time using the DHCP protocol (a
  6.6094 +  special protocol designed for doing this job), say Y here. In case
  6.6095 +  the boot ROM of your network card was designed for booting Linux and
  6.6096 +  does DHCP itself, providing all necessary information on the kernel
  6.6097 +  command line, you can say N here.
  6.6098 +
  6.6099 +  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
  6.6100 +  must be operating on your network.  Read
  6.6101 +  <file:Documentation/nfsroot.txt> for details.
  6.6102 +
  6.6103 +RARP support
  6.6104 +CONFIG_IP_PNP_RARP
  6.6105 +  If you want your Linux box to mount its whole root file system (the
  6.6106 +  one containing the directory /) from some other computer over the
  6.6107 +  net via NFS and you want the IP address of your computer to be
  6.6108 +  discovered automatically at boot time using the RARP protocol (an
  6.6109 +  older protocol which is being obsoleted by BOOTP and DHCP), say Y
  6.6110 +  here. Note that if you want to use RARP, a RARP server must be
  6.6111 +  operating on your network. Read <file:Documentation/nfsroot.txt> for
  6.6112 +  details.
  6.6113 +
  6.6114 +IP tunneling
  6.6115 +CONFIG_NET_IPIP
  6.6116 +  Tunneling means encapsulating data of one protocol type within
  6.6117 +  another protocol and sending it over a channel that understands the
  6.6118 +  encapsulating protocol. This particular tunneling driver implements
  6.6119 +  encapsulation of IP within IP, which sounds kind of pointless, but
  6.6120 +  can be useful if you want to make your (or some other) machine
  6.6121 +  appear on a different network than it physically is, or to use
  6.6122 +  mobile-IP facilities (allowing laptops to seamlessly move between
  6.6123 +  networks without changing their IP addresses; check out
  6.6124 +  <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
  6.6125 +
  6.6126 +  Saying Y to this option will produce two modules ( = code which can
  6.6127 +  be inserted in and removed from the running kernel whenever you
  6.6128 +  want). Most people won't need this and can say N.
  6.6129 +
  6.6130 +  This driver is also available as a module ( = code which can be
  6.6131 +  inserted in and removed from the running kernel whenever you want).
  6.6132 +  If you want to compile it as a module, say M here and read
  6.6133 +  <file:Documentation/modules.txt>. The module will be called
  6.6134 +  ipip.o
  6.6135 +
  6.6136 +GRE tunnels over IP
  6.6137 +CONFIG_NET_IPGRE
  6.6138 +  Tunneling means encapsulating data of one protocol type within
  6.6139 +  another protocol and sending it over a channel that understands the
  6.6140 +  encapsulating protocol. This particular tunneling driver implements
  6.6141 +  GRE (Generic Routing Encapsulation) and at this time allows
  6.6142 +  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  6.6143 +  This driver is useful if the other endpoint is a Cisco router: Cisco
  6.6144 +  likes GRE much better than the other Linux tunneling driver ("IP
  6.6145 +  tunneling" above). In addition, GRE allows multicast redistribution
  6.6146 +  through the tunnel.
  6.6147 +
  6.6148 +  This driver is also available as a module ( = code which can be
  6.6149 +  inserted in and removed from the running kernel whenever you want).
  6.6150 +  If you want to compile it as a module, say M here and read
  6.6151 +  <file:Documentation/modules.txt>. The module will be called
  6.6152 +  ip_gre.o
  6.6153 +
  6.6154 +Broadcast GRE over IP
  6.6155 +CONFIG_NET_IPGRE_BROADCAST
  6.6156 +  One application of GRE/IP is to construct a broadcast WAN (Wide Area
  6.6157 +  Network), which looks like a normal Ethernet LAN (Local Area
  6.6158 +  Network), but can be distributed all over the Internet. If you want
  6.6159 +  to do that, say Y here and to "IP multicast routing" below.
  6.6160 +
  6.6161 +IP multicast routing
  6.6162 +CONFIG_IP_MROUTE
  6.6163 +  This is used if you want your machine to act as a router for IP
  6.6164 +  packets that have several destination addresses. It is needed on the
  6.6165 +  MBONE, a high bandwidth network on top of the Internet which carries
  6.6166 +  audio and video broadcasts. In order to do that, you would most
  6.6167 +  likely run the program mrouted. Information about the multicast
  6.6168 +  capabilities of the various network cards is contained in
  6.6169 +  <file:Documentation/networking/multicast.txt>. If you haven't heard
  6.6170 +  about it, you don't need it.
  6.6171 +
  6.6172 +PIM-SM version 1 support
  6.6173 +CONFIG_IP_PIMSM_V1
  6.6174 +  Kernel side support for Sparse Mode PIM (Protocol Independent
  6.6175 +  Multicast) version 1. This multicast routing protocol is used widely
  6.6176 +  because Cisco supports it. You need special software to use it
  6.6177 +  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
  6.6178 +  information about PIM.
  6.6179 +
  6.6180 +  Say Y if you want to use PIM-SM v1. Note that you can say N here if
  6.6181 +  you just want to use Dense Mode PIM.
  6.6182 +
  6.6183 +PIM-SM version 2 support
  6.6184 +CONFIG_IP_PIMSM_V2
  6.6185 +  Kernel side support for Sparse Mode PIM version 2. In order to use
  6.6186 +  this, you need an experimental routing daemon supporting it (pimd or
  6.6187 +  gated-5). This routing protocol is not used widely, so say N unless
  6.6188 +  you want to play with it.
  6.6189 +
  6.6190 +Unix domain sockets
  6.6191 +CONFIG_UNIX
  6.6192 +  If you say Y here, you will include support for Unix domain sockets;
  6.6193 +  sockets are the standard Unix mechanism for establishing and
  6.6194 +  accessing network connections.  Many commonly used programs such as
  6.6195 +  the X Window system and syslog use these sockets even if your
  6.6196 +  machine is not connected to any network.  Unless you are working on
  6.6197 +  an embedded system or something similar, you therefore definitely
  6.6198 +  want to say Y here.
  6.6199 +
  6.6200 +  However, the socket support is also available as a module ( = code
  6.6201 +  which can be inserted in and removed from the running kernel
  6.6202 +  whenever you want).  If you want to compile it as a module, say M
  6.6203 +  here and read <file:Documentation/modules.txt>. The module will be
  6.6204 +  called unix.o.  If you try building this as a module and you have
  6.6205 +  said Y to "Kernel module loader support" above, be sure to add
  6.6206 +  'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
  6.6207 +  several important services won't work correctly if you say M here
  6.6208 +  and then neglect to load the module.
  6.6209 +
  6.6210 +  Say Y unless you know what you are doing.
  6.6211 +
  6.6212 +The IPv6 protocol
  6.6213 +CONFIG_IPV6
  6.6214 +  This is experimental support for the next version of the Internet
  6.6215 +  Protocol: IP version 6 (also called IPng "IP next generation").
  6.6216 +  Features of this new protocol include: expanded address space,
  6.6217 +  authentication and privacy, and seamless interoperability with the
  6.6218 +  current version of IP (IP version 4). For general information about
  6.6219 +  IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
  6.6220 +  for specific information about IPv6 under Linux read the HOWTO at
  6.6221 +  <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
  6.6222 +  in the kernel source.
  6.6223 +
  6.6224 +  If you want to use IPv6, please upgrade to the newest net-tools as
  6.6225 +  given in <file:Documentation/Changes>. You will still be able to do
  6.6226 +  regular IPv4 networking as well.
  6.6227 +
  6.6228 +  This protocol support is also available as a module ( = code which
  6.6229 +  can be inserted in and removed from the running kernel whenever you
  6.6230 +  want). The module will be called ipv6.o. If you want to compile it
  6.6231 +  as a module, say M here and read <file:Documentation/modules.txt>.
  6.6232 +
  6.6233 +  It is safe to say N here for now.
  6.6234 +
  6.6235 +The SCTP Protocol (EXPERIMENTAL)
  6.6236 +CONFIG_IP_SCTP
  6.6237 +  Stream Control Transmission Protocol
  6.6238 +
  6.6239 +  From RFC 2960 (http://www.ietf.org/rfc/rfc2960.txt)
  6.6240 +
  6.6241 +  "SCTP is a reliable transport protocol operating on top of a
  6.6242 +  connectionless packet network such as IP.  It offers the following
  6.6243 +  services to its users:
  6.6244 +
  6.6245 +  -- acknowledged error-free non-duplicated transfer of user data,
  6.6246 +  -- data fragmentation to conform to discovered path MTU size,
  6.6247 +  -- sequenced delivery of user messages within multiple streams,
  6.6248 +  with an option for order-of-arrival delivery of individual user
  6.6249 +  messages,
  6.6250 +  -- optional bundling of multiple user messages into a single SCTP
  6.6251 +  packet, and
  6.6252 +  -- network-level fault tolerance through supporting of multi-
  6.6253 +  homing at either or both ends of an association."
  6.6254 +
  6.6255 +  This protocol support is also available as a module ( = code which
  6.6256 +  can be inserted in and removed from the running kernel whenever you
  6.6257 +  want). The module will be called sctp. If you want to compile it
  6.6258 +  as a module, say M here and read <file:Documentation/modules.txt>.
  6.6259 +
  6.6260 +  If in doubt, say N.
  6.6261 +
  6.6262 +SCTP: Debug messages
  6.6263 +CONFIG_SCTP_DBG_MSG
  6.6264 +  If you say Y, this will enable verbose debugging messages. 
  6.6265 +
  6.6266 +  If unsure, say N.  However, if you are running into problems, use 
  6.6267 +  this option to gather detailed trace information
  6.6268 +
  6.6269 +SCTP: Debug object counts
  6.6270 +CONFIG_SCTP_DBG_OBJCNT
  6.6271 +  If you say Y, this will enable debugging support for counting the 
  6.6272 +  type of objects that are currently allocated.  This is useful for 
  6.6273 +  identifying memory leaks.   If the /proc filesystem is enabled this 
  6.6274 +  debug information can be viewed by 
  6.6275 +  'cat /proc/net/sctp/sctp_dbg_objcnt'
  6.6276 +
  6.6277 +  If unsure, say N
  6.6278 +
  6.6279 +#choice
  6.6280 +SCTP: HMAC algorithm
  6.6281 +CONFIG_SCTP_HMAC_NONE
  6.6282 +  Choose an HMAC algorithm to be used during association establishment.
  6.6283 +  It can be one of SHA1, MD5 or NONE. It is advised to use either HMAC-MD5
  6.6284 +  or HMAC-SHA1.
  6.6285 +  See configuration for Cryptographic API and enable these algorithms
  6.6286 +  to make usable by SCTP.
  6.6287 +
  6.6288 +SCTP: SHA1 HMAC algorithm
  6.6289 +CONFIG_SCTP_HMAC_SHA1
  6.6290 +  Enable the use of HMAC-SHA1 during association establishment.  It 
  6.6291 +  is advised to use either HMAC-MD5 or HMAC-SHA1.
  6.6292 +  See configuration for Cryptographic API and enable these algorithms
  6.6293 +  to make usable by SCTP.
  6.6294 +
  6.6295 +SCTP: MD5 HMAC algorithm
  6.6296 +config SCTP_HMAC_MD5
  6.6297 +  Enable the use of HMAC-MD5 during association establishment.  It is 
  6.6298 +  advised to use either HMAC-MD5 or HMAC-SHA1.
  6.6299 +  See configuration for Cryptographic API and enable these algorithms
  6.6300 +  to make usable by SCTP.
  6.6301 +
  6.6302 +Kernel httpd acceleration
  6.6303 +CONFIG_KHTTPD
  6.6304 +  The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
  6.6305 +  server built into the kernel. It is limited since it can only serve
  6.6306 +  files from the file system and cannot deal with executable content
  6.6307 +  such as CGI scripts. Serving files is sped up if you use kHTTPd.
  6.6308 +  If kHTTPd is not able to fulfill a request, it can transparently
  6.6309 +  pass it through to a user space web server such as apache.
  6.6310 +
  6.6311 +  Saying "M" here builds the kHTTPd module; this is NOT enough to have
  6.6312 +  a working kHTTPd. For safety reasons, the module has to be activated
  6.6313 +  by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
  6.6314 +  module.
  6.6315 +
  6.6316 +  Before using this, read the README in net/khttpd !
  6.6317 +
  6.6318 +  The kHTTPd is experimental. Be careful when using it on a production
  6.6319 +  machine. Also note that kHTTPd doesn't support virtual servers yet.
  6.6320 +
  6.6321 +The IPX protocol
  6.6322 +CONFIG_IPX
  6.6323 +  This is support for the Novell networking protocol, IPX, commonly
  6.6324 +  used for local networks of Windows machines.  You need it if you
  6.6325 +  want to access Novell NetWare file or print servers using the Linux
  6.6326 +  Novell client ncpfs (available from
  6.6327 +  <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
  6.6328 +  within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
  6.6329 +  available from <http://www.tldp.org/docs.html#howto>).  In order
  6.6330 +  to do the former, you'll also have to say Y to "NCP file system
  6.6331 +  support", below.
  6.6332 +
  6.6333 +  IPX is similar in scope to IP, while SPX, which runs on top of IPX,
  6.6334 +  is similar to TCP. There is also experimental support for SPX in
  6.6335 +  Linux (see "SPX networking", below).
  6.6336 +
  6.6337 +  To turn your Linux box into a fully featured NetWare file server and
  6.6338 +  IPX router, say Y here and fetch either lwared from
  6.6339 +  <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
  6.6340 +  mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
  6.6341 +  information, read the IPX-HOWTO available from
  6.6342 +  <http://www.tldp.org/docs.html#howto>.
  6.6343 +
  6.6344 +  General information about how to connect Linux, Windows machines and
  6.6345 +  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  6.6346 +
  6.6347 +  The IPX driver would enlarge your kernel by about 16 KB. This driver
  6.6348 +  is also available as a module ( = code which can be inserted in and
  6.6349 +  removed from the running kernel whenever you want).  The module will
  6.6350 +  be called ipx.o.  If you want to compile it as a module, say M here
  6.6351 +  and read <file:Documentation/modules.txt>.  Unless you want to
  6.6352 +  integrate your Linux box with a local Novell network, say N.
  6.6353 +
  6.6354 +Full internal IPX network
  6.6355 +CONFIG_IPX_INTERN
  6.6356 +  Every IPX network has an address that identifies it. Sometimes it is
  6.6357 +  useful to give an IPX "network" address to your Linux box as well
  6.6358 +  (for example if your box is acting as a file server for different
  6.6359 +  IPX networks: it will then be accessible from everywhere using the
  6.6360 +  same address). The way this is done is to create a virtual internal
  6.6361 +  "network" inside your box and to assign an IPX address to this
  6.6362 +  network. Say Y here if you want to do this; read the IPX-HOWTO at
  6.6363 +  <http://www.tldp.org/docs.html#howto> for details.
  6.6364 +
  6.6365 +  The full internal IPX network enables you to allocate sockets on
  6.6366 +  different virtual nodes of the internal network. This is done by
  6.6367 +  evaluating the field sipx_node of the socket address given to the
  6.6368 +  bind call. So applications should always initialize the node field
  6.6369 +  to 0 when binding a socket on the primary network. In this case the
  6.6370 +  socket is assigned the default node that has been given to the
  6.6371 +  kernel when the internal network was created. By enabling the full
  6.6372 +  internal IPX network the cross-forwarding of packets targeted at
  6.6373 +  'special' sockets to sockets listening on the primary network is
  6.6374 +  disabled. This might break existing applications, especially RIP/SAP
  6.6375 +  daemons. A RIP/SAP daemon that works well with the full internal net
  6.6376 +  can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
  6.6377 +
  6.6378 +  If you don't know what you are doing, say N.
  6.6379 +
  6.6380 +#(We're told this will come back someday)
  6.6381 +
  6.6382 +SPX networking
  6.6383 +CONFIG_SPX
  6.6384 +  * Orphaned entry retained 20 April 2001 by Petr Vandrovec     *
  6.6385 +  * If you read this note from the configurator, please contact *
  6.6386 +  * the Configure.help maintainers.                             *
  6.6387 +  The Sequenced Packet eXchange protocol is a transport layer protocol
  6.6388 +  built on top of IPX. It is used in Novell NetWare systems for
  6.6389 +  client-server applications and is similar to TCP (which runs on top
  6.6390 +  of IP).
  6.6391 +
  6.6392 +  Note that Novell NetWare file sharing does not use SPX; it uses a
  6.6393 +  protocol called NCP, for which separate Linux support is available
  6.6394 +  ("NCP file system support" below for the client side, and the user
  6.6395 +  space programs lwared or mars_nwe for the server side).
  6.6396 +
  6.6397 +  Say Y here if you have use for SPX; read the IPX-HOWTO at
  6.6398 +  <http://www.tldp.org/docs.html#howto> for details.
  6.6399 +
  6.6400 +  This driver is also available as a module ( = code which can be
  6.6401 +  inserted in and removed from the running kernel whenever you want).
  6.6402 +  The module will be called af_spx.o. If you want to compile it as a
  6.6403 +  module, say M here and read <file:Documentation/modules.txt>.
  6.6404 +
  6.6405 +DECnet networking
  6.6406 +CONFIG_DECNET
  6.6407 +  The DECnet networking protocol was used in many products made by
  6.6408 +  Digital (now Compaq).  It provides reliable stream and sequenced
  6.6409 +  packet communications over which run a variety of services similar
  6.6410 +  to those which run over TCP/IP.
  6.6411 +
  6.6412 +  To find some tools to use with the kernel layer support, please
  6.6413 +  look at Patrick Caulfield's web site:
  6.6414 +  <http://linux.dreamtime.org/decnet/>.
  6.6415 +
  6.6416 +  More detailed documentation is available in
  6.6417 +  <file:Documentation/networking/decnet.txt>.
  6.6418 +
  6.6419 +  Be sure to say Y to "/proc file system support" and "Sysctl support"
  6.6420 +  below when using DECnet, since you will need sysctl support to aid
  6.6421 +  in configuration at run time.
  6.6422 +
  6.6423 +  The DECnet code is also available as a module ( = code which can be
  6.6424 +  inserted in and removed from the running kernel whenever you want).
  6.6425 +  The module is called decnet.o.
  6.6426 +
  6.6427 +DECnet SIOCFIGCONF support
  6.6428 +CONFIG_DECNET_SIOCGIFCONF
  6.6429 +  This option should only be turned on if you are really sure that
  6.6430 +  you know what you are doing. It can break other applications which
  6.6431 +  use this system call and the proper way to get the information
  6.6432 +  provided by this call is to use rtnetlink.
  6.6433 +
  6.6434 +  If unsure, say N.
  6.6435 +
  6.6436 +DECnet router support
  6.6437 +CONFIG_DECNET_ROUTER
  6.6438 +  Add support for turning your DECnet Endnode into a level 1 or 2
  6.6439 +  router.  This is an unfinished option for developers only.  If you
  6.6440 +  do say Y here, then make sure that you also say Y to "Kernel/User
  6.6441 +  network link driver", "Routing messages" and "Network packet
  6.6442 +  filtering".  The first two are required to allow configuration via
  6.6443 +  rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
  6.6444 +  from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
  6.6445 +  will be required for the forthcoming routing daemon to work.
  6.6446 +
  6.6447 +  See <file:Documentation/networking/decnet.txt> for more information.
  6.6448 +
  6.6449 +Use FWMARK value as DECnet routing key
  6.6450 +CONFIG_DECNET_ROUTE_FWMARK
  6.6451 +  If you say Y here, you will be able to specify different routes for
  6.6452 +  packets with different FWMARK ("firewalling mark") values
  6.6453 +  (see ipchains(8), "-m" argument).
  6.6454 +
  6.6455 +AppleTalk interfaces support
  6.6456 +CONFIG_DEV_APPLETALK
  6.6457 +  AppleTalk is the protocol that Apple computers can use to communicate
  6.6458 +  on a network.  If your Linux box is connected to such a network, and wish
  6.6459 +  to do IP over it, or you have a LocalTalk card and wish to use it to
  6.6460 +  connect to the AppleTalk network, say Y.
  6.6461 +
  6.6462 +AppleTalk protocol support
  6.6463 +CONFIG_ATALK
  6.6464 +  AppleTalk is the protocol that Apple computers can use to communicate
  6.6465 +  on a network.  If your Linux box is connected to such a network and you
  6.6466 +  wish to connect to it, say Y.  You will need to use the netatalk package
  6.6467 +  so that your Linux box can act as a print and file server for Macs as
  6.6468 +  well as access AppleTalk printers.  Check out
  6.6469 +  <http://www.zettabyte.net/netatalk/> on the WWW for details.
  6.6470 +  EtherTalk is the name used for AppleTalk over Ethernet and the
  6.6471 +  cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
  6.6472 +  network using serial links.  EtherTalk and LocalTalk are fully
  6.6473 +  supported by Linux.
  6.6474 +
  6.6475 +  General information about how to connect Linux, Windows machines and
  6.6476 +  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.  The
  6.6477 +  NET-3-HOWTO, available from
  6.6478 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  6.6479 +  information as well.
  6.6480 +
  6.6481 +  This driver is also available as a module ( = code which can be
  6.6482 +  inserted in and removed from the running kernel whenever you want).
  6.6483 +  The module is called appletalk.o.  If you want to compile it as a
  6.6484 +  module, say M here and read <file:Documentation/modules.txt>.  You
  6.6485 +  almost certainly want to compile it as a module so you can restart
  6.6486 +  your AppleTalk stack without rebooting your machine.  I hear that
  6.6487 +  the GNU boycott of Apple is over, so even politically correct people
  6.6488 +  are allowed to say Y here.
  6.6489 +
  6.6490 +AppleTalk-IP driver support
  6.6491 +CONFIG_IPDDP
  6.6492 +  This allows IP networking for users who only have AppleTalk
  6.6493 +  networking available. This feature is experimental. With this
  6.6494 +  driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
  6.6495 +  box is stuck on an AppleTalk only network) or decapsulate (e.g. if
  6.6496 +  you want your Linux box to act as an Internet gateway for a zoo of
  6.6497 +  AppleTalk connected Macs). Please see the file
  6.6498 +  <file:Documentation/networking/ipddp.txt> for more information.
  6.6499 +
  6.6500 +  If you say Y here, the AppleTalk-IP support will be compiled into
  6.6501 +  the kernel. In this case, you can either use encapsulation or
  6.6502 +  decapsulation, but not both. With the following two questions, you
  6.6503 +  decide which one you want.
  6.6504 +
  6.6505 +  If you say M here, the AppleTalk-IP support will be compiled as a
  6.6506 +  module ( = code which can be inserted in and removed from the
  6.6507 +  running kernel whenever you want, read
  6.6508 +  <file:Documentation/modules.txt>).  The module is called ipddp.o.
  6.6509 +  In this case, you will be able to use both encapsulation and
  6.6510 +  decapsulation simultaneously, by loading two copies of the module
  6.6511 +  and specifying different values for the module option ipddp_mode.
  6.6512 +
  6.6513 +IP to AppleTalk-IP Encapsulation support
  6.6514 +CONFIG_IPDDP_ENCAP
  6.6515 +  If you say Y here, the AppleTalk-IP code will be able to encapsulate
  6.6516 +  IP packets inside AppleTalk frames; this is useful if your Linux box
  6.6517 +  is stuck on an AppleTalk network (which hopefully contains a
  6.6518 +  decapsulator somewhere). Please see
  6.6519 +  <file:Documentation/networking/ipddp.txt> for more information. If
  6.6520 +  you said Y to "AppleTalk-IP driver support" above and you say Y
  6.6521 +  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
  6.6522 +  support", below.
  6.6523 +
  6.6524 +AppleTalk-IP to IP Decapsulation support
  6.6525 +CONFIG_IPDDP_DECAP
  6.6526 +  If you say Y here, the AppleTalk-IP code will be able to decapsulate
  6.6527 +  AppleTalk-IP frames to IP packets; this is useful if you want your
  6.6528 +  Linux box to act as an Internet gateway for an AppleTalk network.
  6.6529 +  Please see <file:Documentation/networking/ipddp.txt> for more
  6.6530 +  information.  If you said Y to "AppleTalk-IP driver support" above
  6.6531 +  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
  6.6532 +  Encapsulation support", above.
  6.6533 +
  6.6534 +Apple/Farallon LocalTalk PC card support
  6.6535 +CONFIG_LTPC
  6.6536 +  This allows you to use the AppleTalk PC card to connect to LocalTalk
  6.6537 +  networks. The card is also known as the Farallon PhoneNet PC card.
  6.6538 +  If you are in doubt, this card is the one with the 65C02 chip on it.
  6.6539 +  You also need version 1.3.3 or later of the netatalk package.
  6.6540 +  This driver is experimental, which means that it may not work.
  6.6541 +  See the file <file:Documentation/networking/ltpc.txt>.
  6.6542 +
  6.6543 +  This driver is also available as a module ( = code which can be
  6.6544 +  inserted in and removed from the running kernel whenever you want).
  6.6545 +  If you want to compile it as a module, say M here and read
  6.6546 +  <file:Documentation/modules.txt>. The module will be called
  6.6547 +  ltpc.o
  6.6548 +
  6.6549 +COPS LocalTalk PC card support
  6.6550 +CONFIG_COPS
  6.6551 +  This allows you to use COPS AppleTalk cards to connect to LocalTalk
  6.6552 +  networks. You also need version 1.3.3 or later of the netatalk
  6.6553 +  package. This driver is experimental, which means that it may not
  6.6554 +  work. This driver will only work if you choose "AppleTalk DDP"
  6.6555 +  networking support, above.
  6.6556 +  Please read the file <file:Documentation/networking/cops.txt>.
  6.6557 +
  6.6558 +  This driver is also available as a module ( = code which can be
  6.6559 +  inserted in and removed from the running kernel whenever you want).
  6.6560 +  If you want to compile it as a module, say M here and read
  6.6561 +  <file:Documentation/modules.txt>. The module will be called
  6.6562 +  cops.o
  6.6563 +
  6.6564 +Dayna firmware support
  6.6565 +CONFIG_COPS_DAYNA
  6.6566 +  Support COPS compatible cards with Dayna style firmware (Dayna
  6.6567 +  DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
  6.6568 +  III, Farallon PhoneNET PC II).
  6.6569 +
  6.6570 +Tangent firmware support
  6.6571 +CONFIG_COPS_TANGENT
  6.6572 +  Support COPS compatible cards with Tangent style firmware (Tangent
  6.6573 +  ATB_II, Novell NL-1000, Daystar Digital LT-200.
  6.6574 +
  6.6575 +Amateur Radio support
  6.6576 +CONFIG_HAMRADIO
  6.6577 +  If you want to connect your Linux box to an amateur radio, answer Y
  6.6578 +  here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
  6.6579 +  the AX25-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
  6.6580 +
  6.6581 +  Note that the answer to this question won't directly affect the
  6.6582 +  kernel: saying N will just cause the configurator to skip all
  6.6583 +  the questions about amateur radio.
  6.6584 +
  6.6585 +Amateur Radio AX.25 Level 2 protocol
  6.6586 +CONFIG_AX25
  6.6587 +  This is the protocol used for computer communication over amateur
  6.6588 +  radio. It is either used by itself for point-to-point links, or to
  6.6589 +  carry other protocols such as tcp/ip. To use it, you need a device
  6.6590 +  that connects your Linux box to your amateur radio. You can either
  6.6591 +  use a low speed TNC (a Terminal Node Controller acts as a kind of
  6.6592 +  modem connecting your computer's serial port to your radio's
  6.6593 +  microphone input and speaker output) supporting the KISS protocol or
  6.6594 +  one of the various SCC cards that are supported by the generic Z8530
  6.6595 +  or the DMA SCC driver. Another option are the Baycom modem serial
  6.6596 +  and parallel port hacks or the sound card modem (supported by their
  6.6597 +  own drivers). If you say Y here, you also have to say Y to one of
  6.6598 +  those drivers.
  6.6599 +
  6.6600 +  Information about where to get supporting software for Linux amateur
  6.6601 +  radio as well as information about how to configure an AX.25 port is
  6.6602 +  contained in the AX25-HOWTO, available from
  6.6603 +  <http://www.tldp.org/docs.html#howto>. You might also want to
  6.6604 +  check out the file <file:Documentation/networking/ax25.txt> in the
  6.6605 +  kernel source. More information about digital amateur radio in
  6.6606 +  general is on the WWW at
  6.6607 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  6.6608 +
  6.6609 +  This driver is also available as a module ( = code which can be
  6.6610 +  inserted in and removed from the running kernel whenever you want).
  6.6611 +  The module will be called ax25.o. If you want to compile it as a
  6.6612 +  module, say M here and read <file:Documentation/modules.txt>.
  6.6613 +
  6.6614 +AX.25 DAMA Slave support
  6.6615 +CONFIG_AX25_DAMA_SLAVE
  6.6616 +  DAMA is a mechanism to prevent collisions when doing AX.25
  6.6617 +  networking. A DAMA server (called "master") accepts incoming traffic
  6.6618 +  from clients (called "slaves") and redistributes it to other slaves.
  6.6619 +  If you say Y here, your Linux box will act as a DAMA slave; this is
  6.6620 +  transparent in that you don't have to do any special DAMA
  6.6621 +  configuration. (Linux cannot yet act as a DAMA server.) If unsure,
  6.6622 +  say N.
  6.6623 +
  6.6624 +AX.25 DAMA Master support
  6.6625 +CONFIG_AX25_DAMA_MASTER
  6.6626 +  DAMA is a mechanism to prevent collisions when doing AX.25
  6.6627 +  networking. A DAMA server (called "master") accepts incoming traffic
  6.6628 +  from clients (called "slaves") and redistributes it to other
  6.6629 +  slaves. If you say Y here, your Linux box will act as a DAMA server.
  6.6630 +  If unsure, say N.
  6.6631 +
  6.6632 +Amateur Radio NET/ROM support
  6.6633 +CONFIG_NETROM
  6.6634 +  NET/ROM is a network layer protocol on top of AX.25 useful for
  6.6635 +  routing.
  6.6636 +
  6.6637 +  A comprehensive listing of all the software for Linux amateur radio
  6.6638 +  users as well as information about how to configure an AX.25 port is
  6.6639 +  contained in the AX25-HOWTO, available from
  6.6640 +  <http://www.tldp.org/docs.html#howto>. You also might want to
  6.6641 +  check out the file <file:Documentation/networking/ax25.txt>. More
  6.6642 +  information about digital amateur radio in general is on the WWW at
  6.6643 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  6.6644 +
  6.6645 +  This driver is also available as a module ( = code which can be
  6.6646 +  inserted in and removed from the running kernel whenever you want).
  6.6647 +  The module will be called netrom.o. If you want to compile it as a
  6.6648 +  module, say M here and read <file:Documentation/modules.txt>.
  6.6649 +
  6.6650 +Amateur Radio X.25 PLP (Rose)
  6.6651 +CONFIG_ROSE
  6.6652 +  The Packet Layer Protocol (PLP) is a way to route packets over X.25
  6.6653 +  connections in general and amateur radio AX.25 connections in
  6.6654 +  particular, essentially an alternative to NET/ROM.
  6.6655 +
  6.6656 +  A comprehensive listing of all the software for Linux amateur radio
  6.6657 +  users as well as information about how to configure an AX.25 port is
  6.6658 +  contained in the AX25-HOWTO, available from
  6.6659 +  <http://www.tldp.org/docs.html#howto>.  You also might want to
  6.6660 +  check out the file <file:Documentation/networking/ax25.txt>. More
  6.6661 +  information about digital amateur radio in general is on the WWW at
  6.6662 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  6.6663 +
  6.6664 +  This driver is also available as a module ( = code which can be
  6.6665 +  inserted in and removed from the running kernel whenever you want).
  6.6666 +  The module will be called rose.o. If you want to compile it as a
  6.6667 +  module, say M here and read <file:Documentation/modules.txt>.
  6.6668 +
  6.6669 +Serial port KISS driver for AX.25
  6.6670 +CONFIG_MKISS
  6.6671 +  KISS is a protocol used for the exchange of data between a computer
  6.6672 +  and a Terminal Node Controller (a small embedded system commonly
  6.6673 +  used for networking over AX.25 amateur radio connections; it
  6.6674 +  connects the computer's serial port with the radio's microphone
  6.6675 +  input and speaker output).
  6.6676 +
  6.6677 +  Although KISS is less advanced than the 6pack protocol, it has
  6.6678 +  the advantage that it is already supported by most modern TNCs
  6.6679 +  without the need for a firmware upgrade.
  6.6680 +
  6.6681 +  If you want to compile this driver as a module ( = code which can be
  6.6682 +  inserted in and removed from the running kernel whenever you want),
  6.6683 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6684 +  will be called mkiss.o.
  6.6685 +
  6.6686 +Serial port 6PACK driver for AX.25
  6.6687 +CONFIG_6PACK
  6.6688 +  6pack is a transmission protocol for the data exchange between your
  6.6689 +  PC and your TNC (the Terminal Node Controller acts as a kind of
  6.6690 +  modem connecting your computer's serial port to your radio's
  6.6691 +  microphone input and speaker output). This protocol can be used as
  6.6692 +  an alternative to KISS for networking over AX.25 amateur radio
  6.6693 +  connections, but it has some extended functionality.
  6.6694 +
  6.6695 +  Note that this driver is still experimental and might cause
  6.6696 +  problems. For details about the features and the usage of the
  6.6697 +  driver, read <file:Documentation/networking/6pack.txt>.
  6.6698 +
  6.6699 +  If you want to compile this driver as a module ( = code which can be
  6.6700 +  inserted in and removed from the running kernel whenever you want),
  6.6701 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6702 +  will be called 6pack.o.
  6.6703 +
  6.6704 +BPQ Ethernet driver
  6.6705 +CONFIG_BPQETHER
  6.6706 +  AX.25 is the protocol used for computer communication over amateur
  6.6707 +  radio. If you say Y here, you will be able to send and receive AX.25
  6.6708 +  traffic over Ethernet (also called "BPQ AX.25"), which could be
  6.6709 +  useful if some other computer on your local network has a direct
  6.6710 +  amateur radio connection.
  6.6711 +
  6.6712 +  If you want to compile the driver as a module ( = code which can be
  6.6713 +  inserted in and removed from the running kernel whenever you want),
  6.6714 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6715 +  will be called bpqether.o.
  6.6716 +
  6.6717 +High-speed (DMA) SCC driver for AX.25
  6.6718 +CONFIG_DMASCC
  6.6719 +  This is a driver for high-speed SCC boards, i.e. those supporting
  6.6720 +  DMA on one port. You usually use those boards to connect your
  6.6721 +  computer to an amateur radio modem (such as the WA4DSY 56kbps
  6.6722 +  modem), in order to send and receive AX.25 packet radio network
  6.6723 +  traffic.
  6.6724 +
  6.6725 +  Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
  6.6726 +  PackeTwin, and S5SCC/DMA boards. They are detected automatically.
  6.6727 +  If you have one of these cards, say Y here and read the AX25-HOWTO,
  6.6728 +  available from <http://www.tldp.org/docs.html#howto>.
  6.6729 +
  6.6730 +  This driver can operate multiple boards simultaneously. If you
  6.6731 +  compile it as a module (by saying M instead of Y), it will be called
  6.6732 +  dmascc.o. If you don't pass any parameter to the driver, all
  6.6733 +  possible I/O addresses are probed. This could irritate other devices
  6.6734 +  that are currently not in use. You may specify the list of addresses
  6.6735 +  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
  6.6736 +  kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
  6.6737 +  network interfaces will be called dmascc0 and dmascc1 for the board
  6.6738 +  detected first, dmascc2 and dmascc3 for the second one, and so on.
  6.6739 +
  6.6740 +  Before you configure each interface with ifconfig, you MUST set
  6.6741 +  certain parameters, such as channel access timing, clock mode, and
  6.6742 +  DMA channel. This is accomplished with a small utility program,
  6.6743 +  dmascc_cfg, available at
  6.6744 +  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
  6.6745 +  at least version 1.27 of dmascc_cfg, as older versions will not
  6.6746 +  work with the current driver.
  6.6747 +
  6.6748 +Z8530 SCC driver for AX.25
  6.6749 +CONFIG_SCC
  6.6750 +  These cards are used to connect your Linux box to an amateur radio
  6.6751 +  in order to communicate with other computers. If you want to use
  6.6752 +  this, read <file:Documentation/networking/z8530drv.txt> and the
  6.6753 +  AX25-HOWTO, available from
  6.6754 +  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  6.6755 +  to "Amateur Radio AX.25 Level 2" support.
  6.6756 +
  6.6757 +  If you want to compile this as a module ( = code which can be
  6.6758 +  inserted in and removed from the running kernel whenever you want),
  6.6759 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6760 +  will be called scc.o.
  6.6761 +
  6.6762 +Support for TRX that feedback the tx signal to rx
  6.6763 +CONFIG_SCC_TRXECHO
  6.6764 +  Some transmitters feed the transmitted signal back to the receive
  6.6765 +  line.  Say Y here to foil this by explicitly disabling the receiver
  6.6766 +  during data transmission.  If in doubt, say Y.
  6.6767 +
  6.6768 +Additional delay for PA0HZP OptoSCC compatible boards
  6.6769 +CONFIG_SCC_DELAY
  6.6770 +  Say Y here if you experience problems with the SCC driver not
  6.6771 +  working properly; please read
  6.6772 +  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
  6.6773 +  say N.
  6.6774 +
  6.6775 +YAM driver for AX.25
  6.6776 +CONFIG_YAM
  6.6777 +  The YAM is a modem for packet radio which connects to the serial
  6.6778 +  port and includes some of the functions of a Terminal Node
  6.6779 +  Controller. If you have one of those, say Y here.
  6.6780 +
  6.6781 +  If you want to compile the driver as a module ( = code which can be
  6.6782 +  inserted in and removed from the running kernel whenever you want),
  6.6783 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6784 +  will be called yam.o.
  6.6785 +
  6.6786 +BAYCOM picpar and par96 driver for AX.25
  6.6787 +CONFIG_BAYCOM_PAR
  6.6788 +  This is a driver for Baycom style simple amateur radio modems that
  6.6789 +  connect to a parallel interface. The driver supports the picpar and
  6.6790 +  par96 designs. To configure the driver, use the sethdlc utility
  6.6791 +  available in the standard ax25 utilities package. For information on
  6.6792 +  the modems, see <http://www.baycom.de/> and the file
  6.6793 +  <file:Documentation/networking/baycom.txt>.
  6.6794 +
  6.6795 +  If you want to compile this driver as a module ( = code which can be
  6.6796 +  inserted in and removed from the running kernel whenever you want),
  6.6797 +  say M here and read <file:Documentation/modules.txt>.  This is
  6.6798 +  recommended.  The module will be called baycom_par.o.
  6.6799 +
  6.6800 +BAYCOM EPP driver for AX.25
  6.6801 +CONFIG_BAYCOM_EPP
  6.6802 +  This is a driver for Baycom style simple amateur radio modems that
  6.6803 +  connect to a parallel interface. The driver supports the EPP
  6.6804 +  designs. To configure the driver, use the sethdlc utility available
  6.6805 +  in the standard ax25 utilities package. For information on the
  6.6806 +  modems, see <http://www.baycom.de/> and the file
  6.6807 +  <file:Documentation/networking/baycom.txt>.
  6.6808 +
  6.6809 +  If you want to compile this driver as a module ( = code which can be
  6.6810 +  inserted in and removed from the running kernel whenever you want),
  6.6811 +  say M here and read <file:Documentation/modules.txt>.  This is
  6.6812 +  recommended.  The module will be called baycom_par.o.
  6.6813 +
  6.6814 +BAYCOM ser12 full-duplex driver for AX.25
  6.6815 +CONFIG_BAYCOM_SER_FDX
  6.6816 +  This is one of two drivers for Baycom style simple amateur radio
  6.6817 +  modems that connect to a serial interface. The driver supports the
  6.6818 +  ser12 design in full-duplex mode. In addition, it allows the
  6.6819 +  baudrate to be set between 300 and 4800 baud (however not all modems
  6.6820 +  support all baudrates). This is the preferred driver. The next
  6.6821 +  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
  6.6822 +  driver and still provided in case this driver does not work with
  6.6823 +  your serial interface chip. To configure the driver, use the sethdlc
  6.6824 +  utility available in the standard ax25 utilities package. For
  6.6825 +  information on the modems, see <http://www.baycom.de/> and
  6.6826 +  <file:Documentation/networking/baycom.txt>.
  6.6827 +
  6.6828 +  If you want to compile this driver as a module ( = code which can be
  6.6829 +  inserted in and removed from the running kernel whenever you want),
  6.6830 +  say M here and read <file:Documentation/modules.txt>.  This is
  6.6831 +  recommended.  The module will be called baycom_ser_fdx.o.
  6.6832 +
  6.6833 +BAYCOM ser12 half-duplex driver for AX.25
  6.6834 +CONFIG_BAYCOM_SER_HDX
  6.6835 +  This is one of two drivers for Baycom style simple amateur radio
  6.6836 +  modems that connect to a serial interface. The driver supports the
  6.6837 +  ser12 design in full-duplex mode. This is the old driver.  It is
  6.6838 +  still provided in case your serial interface chip does not work with
  6.6839 +  the full-duplex driver. This driver is depreciated.  To configure
  6.6840 +  the driver, use the sethdlc utility available in the standard ax25
  6.6841 +  utilities package. For information on the modems, see
  6.6842 +  <http://www.baycom.de/> and
  6.6843 +  <file:Documentation/networking/baycom.txt>.
  6.6844 +
  6.6845 +  If you want to compile this driver as a module ( = code which can be
  6.6846 +  inserted in and removed from the running kernel whenever you want),
  6.6847 +  say M here and read <file:Documentation/modules.txt>.  This is
  6.6848 +  recommended.  The module will be called baycom_ser_hdx.o.
  6.6849 +
  6.6850 +Sound card modem driver for AX.25
  6.6851 +CONFIG_SOUNDMODEM
  6.6852 +  This experimental driver allows a standard Sound Blaster or
  6.6853 +  WindowsSoundSystem compatible sound card to be used as a packet
  6.6854 +  radio modem (NOT as a telephone modem!), to send digital traffic
  6.6855 +  over amateur radio.
  6.6856 +
  6.6857 +  To configure the driver, use the sethdlc, smdiag and smmixer
  6.6858 +  utilities available in the standard ax25 utilities package. For
  6.6859 +  information on how to key the transmitter, see
  6.6860 +  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
  6.6861 +  <file:Documentation/networking/soundmodem.txt>.
  6.6862 +
  6.6863 +  If you want to compile this driver as a module ( = code which can be
  6.6864 +  inserted in and removed from the running kernel whenever you want),
  6.6865 +  say M here and read <file:Documentation/modules.txt>.  This is
  6.6866 +  recommended.  The module will be called soundmodem.o.
  6.6867 +
  6.6868 +Sound card modem support for Sound Blaster and compatible cards
  6.6869 +CONFIG_SOUNDMODEM_SBC
  6.6870 +  This option enables the soundmodem driver to use Sound Blaster and
  6.6871 +  compatible cards. If you have a dual mode card (i.e. a WSS cards
  6.6872 +  with a Sound Blaster emulation) you should say N here and Y to
  6.6873 +  "Sound card modem support for WSS and Crystal cards", below, because
  6.6874 +  this usually results in better performance. This option also
  6.6875 +  supports SB16/32/64 in full-duplex mode.
  6.6876 +
  6.6877 +Sound card modem support for WSS and Crystal cards
  6.6878 +CONFIG_SOUNDMODEM_WSS
  6.6879 +  This option enables the soundmodem driver to use WindowsSoundSystem
  6.6880 +  compatible cards. These cards feature a codec chip from either
  6.6881 +  Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
  6.6882 +  Semiconductors (such as CS4248, CS423x). This option also supports
  6.6883 +  the WSS full-duplex operation which currently works with Crystal
  6.6884 +  CS423x chips. If you don't need full-duplex operation, do not enable
  6.6885 +  it to save performance.
  6.6886 +
  6.6887 +Sound card modem support for 1200 baud AFSK modulation
  6.6888 +CONFIG_SOUNDMODEM_AFSK1200
  6.6889 +  This option enables the soundmodem driver 1200 baud AFSK modem,
  6.6890 +  compatible to popular modems using TCM3105 or AM7911. The
  6.6891 +  demodulator requires about 12% of the CPU power of a Pentium 75 CPU
  6.6892 +  per channel.
  6.6893 +
  6.6894 +Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
  6.6895 +CONFIG_SOUNDMODEM_AFSK2400_7
  6.6896 +  This option enables the soundmodem driver 2400 baud AFSK modem,
  6.6897 +  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
  6.6898 +  crystal. Note that the availability of this driver does _not_ imply
  6.6899 +  that I recommend building such links. It is only here since users
  6.6900 +  especially in eastern Europe have asked me to do so. In fact this
  6.6901 +  modulation scheme has many disadvantages, mainly its incompatibility
  6.6902 +  with many transceiver designs and the fact that the TCM3105 (if
  6.6903 +  used) is operated widely outside its specifications.
  6.6904 +
  6.6905 +Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
  6.6906 +CONFIG_SOUNDMODEM_AFSK2400_8
  6.6907 +  This option enables the soundmodem driver 2400 baud AFSK modem,
  6.6908 +  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
  6.6909 +  Note that the availability of this driver does _not_ imply that I
  6.6910 +  recommend building such links. It is only here since users
  6.6911 +  especially in eastern Europe have asked me to do so. In fact this
  6.6912 +  modulation scheme has many disadvantages, mainly its incompatibility
  6.6913 +  with many transceiver designs and the fact that the TCM3105 (if
  6.6914 +  used) is operated widely outside its specifications.
  6.6915 +
  6.6916 +Sound card modem support for 2666 baud AFSK modulation
  6.6917 +CONFIG_SOUNDMODEM_AFSK2666
  6.6918 +  This option enables the soundmodem driver 2666 baud AFSK modem.
  6.6919 +  This modem is experimental, and not compatible to anything
  6.6920 +  else I know of.
  6.6921 +
  6.6922 +Sound card modem support for 4800 baud 8PSK modulation
  6.6923 +CONFIG_SOUNDMODEM_PSK4800
  6.6924 +  This option enables the soundmodem driver 4800 baud 8PSK modem.
  6.6925 +  This modem is experimental, and not compatible to anything
  6.6926 +  else I know of.
  6.6927 +
  6.6928 +Sound card modem support for 4800 baud HAPN-1 modulation
  6.6929 +CONFIG_SOUNDMODEM_HAPN4800
  6.6930 +  This option enables the soundmodem driver 4800 baud HAPN-1
  6.6931 +  compatible modem. This modulation seems to be widely used 'down
  6.6932 +  under' and in the Netherlands. Here, nobody uses it, so I could not
  6.6933 +  test if it works. It is compatible to itself, however :-)
  6.6934 +
  6.6935 +Sound card modem support for 9600 baud FSK G3RUH modulation
  6.6936 +CONFIG_SOUNDMODEM_FSK9600
  6.6937 +  This option enables the soundmodem driver 9600 baud FSK modem,
  6.6938 +  compatible to the G3RUH standard. The demodulator requires about 4%
  6.6939 +  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
  6.6940 +  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
  6.6941 +  can only use one protocol at a time, depending on what the other end
  6.6942 +  can understand).
  6.6943 +
  6.6944 +CCITT X.25 Packet Layer
  6.6945 +CONFIG_X25
  6.6946 +  X.25 is a set of standardized network protocols, similar in scope to
  6.6947 +  frame relay; the one physical line from your box to the X.25 network
  6.6948 +  entry point can carry several logical point-to-point connections
  6.6949 +  (called "virtual circuits") to other computers connected to the X.25
  6.6950 +  network. Governments, banks, and other organizations tend to use it
  6.6951 +  to connect to each other or to form Wide Area Networks (WANs). Many
  6.6952 +  countries have public X.25 networks. X.25 consists of two
  6.6953 +  protocols: the higher level Packet Layer Protocol (PLP) (say Y here
  6.6954 +  if you want that) and the lower level data link layer protocol LAPB
  6.6955 +  (say Y to "LAPB Data Link Driver" below if you want that).
  6.6956 +
  6.6957 +  You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
  6.6958 +  <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
  6.6959 +  Information about X.25 for Linux is contained in the files
  6.6960 +  <file:Documentation/networking/x25.txt> and
  6.6961 +  <file:Documentation/networking/x25-iface.txt>.
  6.6962 +
  6.6963 +  One connects to an X.25 network either with a dedicated network card
  6.6964 +  using the X.21 protocol (not yet supported by Linux) or one can do
  6.6965 +  X.25 over a standard telephone line using an ordinary modem (say Y
  6.6966 +  to "X.25 async driver" below) or over Ethernet using an ordinary
  6.6967 +  Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
  6.6968 +  LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
  6.6969 +  and "LAPB over Ethernet driver" below).
  6.6970 +
  6.6971 +  If you want to compile this driver as a module ( = code which can be
  6.6972 +  inserted in and removed from the running kernel whenever you want),
  6.6973 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.6974 +  will be called x25.o. If unsure, say N.
  6.6975 +
  6.6976 +LAPB Data Link Driver
  6.6977 +CONFIG_LAPB
  6.6978 +  Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
  6.6979 +  the lower) part of the X.25 protocol. It offers a reliable
  6.6980 +  connection service to exchange data frames with one other host, and
  6.6981 +  it is used to transport higher level protocols (mostly X.25 Packet
  6.6982 +  Layer, the higher part of X.25, but others are possible as well).
  6.6983 +  Usually, LAPB is used with specialized X.21 network cards, but Linux
  6.6984 +  currently supports LAPB only over Ethernet connections. If you want
  6.6985 +  to use LAPB connections over Ethernet, say Y here and to "LAPB over
  6.6986 +  Ethernet driver" below. Read
  6.6987 +  <file:Documentation/networking/lapb-module.txt> for technical
  6.6988 +  details.
  6.6989 +
  6.6990 +  If you want to compile this driver as a module though ( = code which
  6.6991 +  can be inserted in and removed from the running kernel whenever you
  6.6992 +  want), say M here and read <file:Documentation/modules.txt>.  The
  6.6993 +  module will be called lapb.o.  If unsure, say N.
  6.6994 +
  6.6995 +802.2 LLC
  6.6996 +CONFIG_LLC
  6.6997 +  This is a Logical Link Layer protocol used for X.25 connections over
  6.6998 +  Ethernet, using ordinary Ethernet cards.
  6.6999 +
  6.7000 +Frame Diverter
  6.7001 +CONFIG_NET_DIVERT
  6.7002 +  The Frame Diverter allows you to divert packets from the
  6.7003 +  network, that are not aimed at the interface receiving it (in
  6.7004 +  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
  6.7005 +  with the Frames Diverter on, can do some *really* transparent www
  6.7006 +  caching using a Squid proxy for example.
  6.7007 +
  6.7008 +  This is very useful when you don't want to change your router's
  6.7009 +  config (or if you simply don't have access to it).
  6.7010 +
  6.7011 +  The other possible usages of diverting Ethernet Frames are
  6.7012 +  numberous:
  6.7013 +   - reroute smtp traffic to another interface
  6.7014 +   - traffic-shape certain network streams
  6.7015 +   - transparently proxy smtp connections
  6.7016 +   - etc...
  6.7017 +
  6.7018 +  For more informations, please refer to:
  6.7019 +    <http://diverter.sourceforge.net/>
  6.7020 +    <http://perso.wanadoo.fr/magpie/EtherDivert.html>
  6.7021 +
  6.7022 +  If unsure, say N.
  6.7023 +
  6.7024 +802.1d Ethernet Bridging
  6.7025 +CONFIG_BRIDGE
  6.7026 +  If you say Y here, then your Linux box will be able to act as an
  6.7027 +  Ethernet bridge, which means that the different Ethernet segments it
  6.7028 +  is connected to will appear as one Ethernet to the participants.
  6.7029 +  Several such bridges can work together to create even larger
  6.7030 +  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  6.7031 +  As this is a standard, Linux bridges will cooperate properly with
  6.7032 +  other third party bridge products.
  6.7033 +
  6.7034 +  In order to use the Ethernet bridge, you'll need the bridge
  6.7035 +  configuration tools; see <file:Documentation/networking/bridge.txt>
  6.7036 +  for location. Please read the Bridge mini-HOWTO for more
  6.7037 +  information.
  6.7038 +
  6.7039 +  Note that if your box acts as a bridge, it probably contains several
  6.7040 +  Ethernet devices, but the kernel is not able to recognize more than
  6.7041 +  one at boot time without help; for details read the Ethernet-HOWTO,
  6.7042 +  available from in <http://www.tldp.org/docs.html#howto>.
  6.7043 +
  6.7044 +  If you want to compile this code as a module ( = code which can be
  6.7045 +  inserted in and removed from the running kernel whenever you want),
  6.7046 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.7047 +  will be called bridge.o.
  6.7048 +
  6.7049 +  If unsure, say N.
  6.7050 +
  6.7051 +Packet socket
  6.7052 +CONFIG_PACKET
  6.7053 +  The Packet protocol is used by applications which communicate
  6.7054 +  directly with network devices without an intermediate network
  6.7055 +  protocol implemented in the kernel, e.g. tcpdump.  If you want them
  6.7056 +  to work, choose Y.
  6.7057 +
  6.7058 +  This driver is also available as a module called af_packet.o ( =
  6.7059 +  code which can be inserted in and removed from the running kernel
  6.7060 +  whenever you want).  If you want to compile it as a module, say M
  6.7061 +  here and read <file:Documentation/modules.txt>; if you use modprobe
  6.7062 +  or kmod, you may also want to add "alias net-pf-17 af_packet" to
  6.7063 +  /etc/modules.conf.
  6.7064 +
  6.7065 +  If unsure, say Y.
  6.7066 +
  6.7067 +Packet socket: mmapped IO
  6.7068 +CONFIG_PACKET_MMAP
  6.7069 +  If you say Y here, the Packet protocol driver can use a faster and 
  6.7070 +  more efficient capture method. This feature also allows bigger 
  6.7071 +  receive buffers. To take advantage of this method who have to use 
  6.7072 +  a libpcap library that supports it. For more info see
  6.7073 +  <file:Documentation/networking/packet_mmap.txt>.
  6.7074 +
  6.7075 +  If unsure, say N.
  6.7076 +
  6.7077 +Netlink device emulation
  6.7078 +CONFIG_NETLINK_DEV
  6.7079 +  This option will be removed soon. Any programs that want to use
  6.7080 +  character special nodes like /dev/tap0 or /dev/route (all with major
  6.7081 +  number 36) need this option, and need to be rewritten soon to use
  6.7082 +  the real netlink socket.
  6.7083 +  This is a backward compatibility option, choose Y for now.
  6.7084 +
  6.7085 +  This driver is also available as a module ( = code which can be
  6.7086 +  inserted in and removed from the running kernel whenever you want).
  6.7087 +  If you want to compile it as a module, say M here and read
  6.7088 +  <file:Documentation/modules.txt>. The module will be called
  6.7089 +  netlink_dev.o
  6.7090 +
  6.7091 +Asynchronous Transfer Mode (ATM)
  6.7092 +CONFIG_ATM
  6.7093 +  ATM is a high-speed networking technology for Local Area Networks
  6.7094 +  and Wide Area Networks.  It uses a fixed packet size and is
  6.7095 +  connection oriented, allowing for the negotiation of minimum
  6.7096 +  bandwidth requirements.
  6.7097 +
  6.7098 +  In order to participate in an ATM network, your Linux box needs an
  6.7099 +  ATM networking card. If you have that, say Y here and to the driver
  6.7100 +  of your ATM card below.
  6.7101 +
  6.7102 +  Note that you need a set of user-space programs to actually make use
  6.7103 +  of ATM.  See the file <file:Documentation/networking/atm.txt> for
  6.7104 +  further details.
  6.7105 +
  6.7106 +Classical IP over ATM
  6.7107 +CONFIG_ATM_CLIP
  6.7108 +  Classical IP over ATM for PVCs and SVCs, supporting InARP and
  6.7109 +  ATMARP. If you want to communication with other IP hosts on your ATM
  6.7110 +  network, you will typically either say Y here or to "LAN Emulation
  6.7111 +  (LANE)" below.
  6.7112 +
  6.7113 +Do NOT send ICMP if no neighbour
  6.7114 +CONFIG_ATM_CLIP_NO_ICMP
  6.7115 +  Normally, an "ICMP host unreachable" message is sent if a neighbour
  6.7116 +  cannot be reached because there is no VC to it in the kernel's
  6.7117 +  ATMARP table. This may cause problems when ATMARP table entries are
  6.7118 +  briefly removed during revalidation. If you say Y here, packets to
  6.7119 +  such neighbours are silently discarded instead.
  6.7120 +
  6.7121 +RFC1483/2684 Bridged protocols
  6.7122 +CONFIG_ATM_BR2684
  6.7123 +  ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
  6.7124 +  This device will act like an ethernet from the kernels point of view,
  6.7125 +  with the traffic being carried by ATM PVCs (currently 1 PVC/device).
  6.7126 +  This is sometimes used over DSL lines.  If in doubt, say N.
  6.7127 +
  6.7128 +Per-VC IP filter kludge
  6.7129 +CONFIG_ATM_BR2684_IPFILTER
  6.7130 +  This is an experimental mechanism for users who need to terminating a
  6.7131 +  large number of IP-only vcc's.  Do not enable this unless you are sure
  6.7132 +  you know what you are doing.
  6.7133 +
  6.7134 +LAN Emulation (LANE) support
  6.7135 +CONFIG_ATM_LANE
  6.7136 +  LAN Emulation emulates services of existing LANs across an ATM
  6.7137 +  network. Besides operating as a normal ATM end station client, Linux
  6.7138 +  LANE client can also act as an proxy client bridging packets between
  6.7139 +  ELAN and Ethernet segments. You need LANE if you want to try MPOA.
  6.7140 +
  6.7141 +Multi-Protocol Over ATM (MPOA) support
  6.7142 +CONFIG_ATM_MPOA
  6.7143 +  Multi-Protocol Over ATM allows ATM edge devices such as routers,
  6.7144 +  bridges and ATM attached hosts establish direct ATM VCs across
  6.7145 +  subnetwork boundaries. These shortcut connections bypass routers
  6.7146 +  enhancing overall network performance.
  6.7147 +
  6.7148 +ATM over TCP
  6.7149 +CONFIG_ATM_TCP
  6.7150 +  ATM over TCP driver. Useful mainly for development and for
  6.7151 +  experiments. If unsure, say N.
  6.7152 +
  6.7153 +Efficient Networks ENI155P
  6.7154 +CONFIG_ATM_ENI
  6.7155 +  Driver for the Efficient Networks ENI155p series and SMC ATM
  6.7156 +  Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
  6.7157 +  2MB on-board RAM (Efficient calls them "C" and "S", respectively),
  6.7158 +  and the FPGA and the ASIC Tonga versions of the board are supported.
  6.7159 +  The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
  6.7160 +  adapters.
  6.7161 +
  6.7162 +  This driver is also available as a module.  If you want to compile
  6.7163 +  it as a module, say M here and read
  6.7164 +  <file:Documentation/modules.txt>.  The module will be called eni.o.
  6.7165 +
  6.7166 +Enable extended debugging
  6.7167 +CONFIG_ATM_ENI_DEBUG
  6.7168 +  Extended debugging records various events and displays that list
  6.7169 +  when an inconsistency is detected. This mechanism is faster than
  6.7170 +  generally using printks, but still has some impact on performance.
  6.7171 +  Note that extended debugging may create certain race conditions
  6.7172 +  itself. Enable this ONLY if you suspect problems with the driver.
  6.7173 +
  6.7174 +Fine-tune burst settings
  6.7175 +CONFIG_ATM_ENI_TUNE_BURST
  6.7176 +  In order to obtain good throughput, the ENI NIC can transfer
  6.7177 +  multiple words of data per PCI bus access cycle. Such a multi-word
  6.7178 +  transfer is called a burst.
  6.7179 +
  6.7180 +  The default settings for the burst sizes are suitable for most PCI
  6.7181 +  chipsets. However, in some cases, large bursts may overrun buffers
  6.7182 +  in the PCI chipset and cause data corruption. In such cases, large
  6.7183 +  bursts must be disabled and only (slower) small bursts can be used.
  6.7184 +  The burst sizes can be set independently in the send (TX) and
  6.7185 +  receive (RX) direction.
  6.7186 +
  6.7187 +  Note that enabling many different burst sizes in the same direction
  6.7188 +  may increase the cost of setting up a transfer such that the
  6.7189 +  resulting throughput is lower than when using only the largest
  6.7190 +  available burst size.
  6.7191 +
  6.7192 +  Also, sometimes larger bursts lead to lower throughput, e.g. on an
  6.7193 +  Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
  6.7194 +  when going from 8W to 16W bursts.
  6.7195 +
  6.7196 +Enable 16W TX bursts (discouraged)
  6.7197 +CONFIG_ATM_ENI_BURST_TX_16W
  6.7198 +  Burst sixteen words at once in the send direction. This may work
  6.7199 +  with recent PCI chipsets, but is known to fail with older chipsets.
  6.7200 +
  6.7201 +Enable 8W TX bursts (recommended)
  6.7202 +CONFIG_ATM_ENI_BURST_TX_8W
  6.7203 +  Burst eight words at once in the send direction. This is the default
  6.7204 +  setting.
  6.7205 +
  6.7206 +Enable 4W TX bursts (optional)
  6.7207 +CONFIG_ATM_ENI_BURST_TX_4W
  6.7208 +  Burst four words at once in the send direction. You may want to try
  6.7209 +  this if you have disabled 8W bursts. Enabling 4W if 8W is also set
  6.7210 +  may or may not improve throughput.
  6.7211 +
  6.7212 +Enable 2W TX bursts (optional)
  6.7213 +CONFIG_ATM_ENI_BURST_TX_2W
  6.7214 +  Burst two words at once in the send direction. You may want to try
  6.7215 +  this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
  6.7216 +  are also set may or may not improve throughput.
  6.7217 +
  6.7218 +Enable 16W RX bursts (discouraged)
  6.7219 +CONFIG_ATM_ENI_BURST_RX_16W
  6.7220 +  Burst sixteen words at once in the receive direction. This may work
  6.7221 +  with recent PCI chipsets, but is known to fail with older chipsets.
  6.7222 +
  6.7223 +Enable 8W RX bursts (discouraged)
  6.7224 +CONFIG_ATM_ENI_BURST_RX_8W
  6.7225 +  Burst eight words at once in the receive direction. This may work
  6.7226 +  with recent PCI chipsets, but is known to fail with older chipsets,
  6.7227 +  such as the Intel Neptune series.
  6.7228 +
  6.7229 +Enable 4W RX bursts (recommended)
  6.7230 +CONFIG_ATM_ENI_BURST_RX_4W
  6.7231 +  Burst four words at once in the receive direction. This is the
  6.7232 +  default setting. Enabling 4W if 8W is also set may or may not
  6.7233 +  improve throughput.
  6.7234 +
  6.7235 +Enable 2W RX bursts (optional)
  6.7236 +CONFIG_ATM_ENI_BURST_RX_2W
  6.7237 +  Burst two words at once in the receive direction. You may want to
  6.7238 +  try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
  6.7239 +  8W are also set may or may not improve throughput.
  6.7240 +
  6.7241 +ZeitNet ZN1221/ZN1225
  6.7242 +CONFIG_ATM_ZATM
  6.7243 +  Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
  6.7244 +  adapters.
  6.7245 +
  6.7246 +  This driver is also available as a module.  If you want to compile
  6.7247 +  it as a module, say M here and read
  6.7248 +  <file:Documentation/modules.txt>.  The module will be called zatm.o.
  6.7249 +
  6.7250 +Enable extended debugging
  6.7251 +CONFIG_ATM_ZATM_DEBUG
  6.7252 +  Extended debugging records various events and displays that list
  6.7253 +  when an inconsistency is detected. This mechanism is faster than
  6.7254 +  generally using printks, but still has some impact on performance.
  6.7255 +  Note that extended debugging may create certain race conditions
  6.7256 +  itself. Enable this ONLY if you suspect problems with the driver.
  6.7257 +
  6.7258 +Fujitsu FireStream (FS50/FS155)
  6.7259 +CONFIG_ATM_FIRESTREAM
  6.7260 +  Driver for the Fujitsu FireStream 155 (MB86697) and
  6.7261 +  FireStream 50 (MB86695) ATM PCI chips.
  6.7262 +
  6.7263 +  This driver is also available as a module.  If you want to compile
  6.7264 +  it as a module, say M here and read
  6.7265 +  <file:Documentation/modules.txt>.  The module will be called
  6.7266 +  firestream.o.
  6.7267 +
  6.7268 +Enable usec resolution timestamps
  6.7269 +CONFIG_ATM_ZATM_EXACT_TS
  6.7270 +  The uPD98401 SAR chip supports a high-resolution timer (approx. 30
  6.7271 +  MHz) that is used for very accurate reception timestamps. Because
  6.7272 +  that timer overflows after 140 seconds, and also to avoid timer
  6.7273 +  drift, time measurements need to be periodically synchronized with
  6.7274 +  the normal system time. Enabling this feature will add some general
  6.7275 +  overhead for timer synchronization and also per-packet overhead for
  6.7276 +  time conversion.
  6.7277 +
  6.7278 +IDT 77201/11 (NICStAR) (ForeRunnerLE)
  6.7279 +CONFIG_ATM_NICSTAR
  6.7280 +  The NICStAR chipset family is used in a large number of ATM NICs for
  6.7281 +  25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
  6.7282 +  series. Say Y if you have one of those.
  6.7283 +
  6.7284 +  This driver is also available as a module.  If you want to compile
  6.7285 +  it as a module, say M here and read
  6.7286 +  <file:Documentation/modules.txt>. The module will be called
  6.7287 +  nicstar.o.
  6.7288 +
  6.7289 +Use suni PHY driver (155Mbps)
  6.7290 +CONFIG_ATM_NICSTAR_USE_SUNI
  6.7291 +  Support for the S-UNI and compatible PHYsical layer chips. These are
  6.7292 +  found in most 155Mbps NICStAR based ATM cards, namely in the
  6.7293 +  ForeRunner LE155 cards. This driver provides detection of cable~
  6.7294 +  removal and reinsertion and provides some statistics. This driver
  6.7295 +  doesn't have removal capability when compiled as a module, so if you
  6.7296 +  need that capability don't include S-UNI support (it's not needed to
  6.7297 +  make the card work).
  6.7298 +
  6.7299 +Use IDT77015 PHY driver (25Mbps)
  6.7300 +CONFIG_ATM_NICSTAR_USE_IDT77105
  6.7301 +  Support for the PHYsical layer chip in ForeRunner LE25 cards. In
  6.7302 +  addition to cable removal/reinsertion detection, this driver allows
  6.7303 +  you to control the loopback mode of the chip via a dedicated IOCTL.
  6.7304 +  This driver is required for proper handling of temporary carrier
  6.7305 +  loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
  6.7306 +
  6.7307 +IDT 77252 (NICStAR II)
  6.7308 +CONFIG_ATM_IDT77252
  6.7309 +  Driver for the IDT 77252 ATM PCI chips.
  6.7310 +
  6.7311 +  This driver is also available as a module.  If you want to compile
  6.7312 +  it as a module, say M here and read
  6.7313 +  <file:Documentation/modules.txt>. The module will be called idt77252.o
  6.7314 +
  6.7315 +Enable debugging messages
  6.7316 +CONFIG_ATM_IDT77252_DEBUG
  6.7317 +  Somewhat useful debugging messages are available. The choice of
  6.7318 +  messages is controlled by a bitmap.  This may be specified as a
  6.7319 +  module argument.  See the file <file:drivers/atm/idt77252.h> for
  6.7320 +  the meanings of the bits in the mask.
  6.7321 +
  6.7322 +  When active, these messages can have a significant impact on the
  6.7323 +  speed of the driver, and the size of your syslog files! When
  6.7324 +  inactive, they will have only a modest impact on performance.
  6.7325 +
  6.7326 +Receive ALL cells in raw queue
  6.7327 +CONFIG_ATM_IDT77252_RCV_ALL
  6.7328 +  Enable receiving of all cells on the ATM link, that do not match
  6.7329 +  an open connection in the raw cell queue of the driver.  Useful
  6.7330 +  for debugging or special applications only, so the safe answer is N.
  6.7331 +
  6.7332 +Madge Ambassador (Collage PCI 155 Server)
  6.7333 +CONFIG_ATM_AMBASSADOR
  6.7334 +  This is a driver for ATMizer based ATM card produced by Madge
  6.7335 +  Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
  6.7336 +  here if you have one of these cards.
  6.7337 +
  6.7338 +Enable debugging messages
  6.7339 +CONFIG_ATM_AMBASSADOR_DEBUG
  6.7340 +  Somewhat useful debugging messages are available. The choice of
  6.7341 +  messages is controlled by a bitmap.  This may be specified as a
  6.7342 +  module argument (kernel command line argument as well?), changed
  6.7343 +  dynamically using an ioctl (not yet) or changed by sending the
  6.7344 +  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  6.7345 +  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
  6.7346 +  mask.
  6.7347 +
  6.7348 +  When active, these messages can have a significant impact on the
  6.7349 +  speed of the driver, and the size of your syslog files! When
  6.7350 +  inactive, they will have only a modest impact on performance.
  6.7351 +
  6.7352 +Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
  6.7353 +CONFIG_ATM_HORIZON
  6.7354 +  This is a driver for the Horizon chipset ATM adapter cards once
  6.7355 +  produced by Madge Networks Ltd. Say Y (or M to compile as a module
  6.7356 +  named horizon.o) here if you have one of these cards.
  6.7357 +
  6.7358 +Enable debugging messages
  6.7359 +CONFIG_ATM_HORIZON_DEBUG
  6.7360 +  Somewhat useful debugging messages are available. The choice of
  6.7361 +  messages is controlled by a bitmap.  This may be specified as a
  6.7362 +  module argument (kernel command line argument as well?), changed
  6.7363 +  dynamically using an ioctl (not yet) or changed by sending the
  6.7364 +  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  6.7365 +  <file:drivers/atm/horizon.h> for the meanings of the bits in the
  6.7366 +  mask.
  6.7367 +
  6.7368 +  When active, these messages can have a significant impact on the
  6.7369 +  speed of the driver, and the size of your syslog files! When
  6.7370 +  inactive, they will have only a modest impact on performance.
  6.7371 +
  6.7372 +Interphase ATM PCI x575/x525/x531
  6.7373 +CONFIG_ATM_IA
  6.7374 +  This is a driver for the Interphase (i)ChipSAR adapter cards
  6.7375 +  which include a variety of variants in term of the size of the
  6.7376 +  control memory (128K-1KVC, 512K-4KVC), the size of the packet
  6.7377 +  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
  6.7378 +  UTP155, UTP25, DS3 and E3). Go to:
  6.7379 +  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
  6.7380 +  for more info about the cards. Say Y (or M to compile as a module
  6.7381 +  named iphase.o) here if you have one of these cards.
  6.7382 +
  6.7383 +  See the file <file:Documentation/networking/iphase.txt> for further
  6.7384 +  details.
  6.7385 +
  6.7386 +Enable debugging messages
  6.7387 +CONFIG_ATM_IA_DEBUG
  6.7388 +  Somewhat useful debugging messages are available. The choice of
  6.7389 +  messages is controlled by a bitmap. This may be specified as a
  6.7390 +  module argument (kernel command line argument as well?), changed
  6.7391 +  dynamically using an ioctl (Get the debug utility, iadbg, from
  6.7392 +  <ftp://ftp.iphase.com/pub/atm/pci/>).
  6.7393 +
  6.7394 +  See the file <file:drivers/atm/iphase.h> for the meanings of the
  6.7395 +  bits in the mask.
  6.7396 +
  6.7397 +  When active, these messages can have a significant impact on the
  6.7398 +  speed of the driver, and the size of your syslog files! When
  6.7399 +  inactive, they will have only a modest impact on performance.
  6.7400 +
  6.7401 +Efficient Networks Speedstream 3010
  6.7402 +CONFIG_ATM_LANAI
  6.7403 +  Supports ATM cards based on the Efficient Networks "Lanai"
  6.7404 +  chipset such as the Speedstream 3010 and the ENI-25p.  The
  6.7405 +  Speedstream 3060 is currently not supported since we don't
  6.7406 +  have the code to drive the on-board Alcatel DSL chipset (yet).
  6.7407 +
  6.7408 +Linux telephony support
  6.7409 +CONFIG_PHONE
  6.7410 +  Say Y here if you have a telephony card, which for example allows
  6.7411 +  you to use a regular phone for voice-over-IP applications.
  6.7412 +
  6.7413 +  Note: this has nothing to do with modems.  You do not need to say Y
  6.7414 +  here in order to be able to use a modem under Linux.
  6.7415 +
  6.7416 +  This support is also available as a module.  If you want to compile
  6.7417 +  it as a module, say M here and read
  6.7418 +  <file:Documentation/modules.txt>.  The module will be called
  6.7419 +  phonedev.o.
  6.7420 +
  6.7421 +Compaq Smart Array support
  6.7422 +CONFIG_BLK_CPQ_CISS_DA
  6.7423 +  This is the driver for Compaq Smart Array 5xxx controllers.
  6.7424 +  Everyone using these boards should say Y here.
  6.7425 +  See <file:Documentation/cciss.txt> for the current list of
  6.7426 +  boards supported by this driver, and for further information
  6.7427 +  on the use of this driver.
  6.7428 +
  6.7429 +  This driver is also available as a module ( = code which can be
  6.7430 +  inserted in and removed from the running kernel whenever you want).
  6.7431 +  If you want to compile it as a module, say M here and read
  6.7432 +  <file:Documentation/modules.txt>. The module will be called
  6.7433 +  cciss.o
  6.7434 +
  6.7435 +SCSI tape drive support for Smart Array 5xxx
  6.7436 +CONFIG_CISS_SCSI_TAPE
  6.7437 +  When enabled (Y), this option allows SCSI tape drives and SCSI medium
  6.7438 +  changers (tape robots) to be accessed via a Compaq 5xxx array
  6.7439 +  controller.  (See <file:Documentation/cciss.txt> for more details.)
  6.7440 +
  6.7441 +  "SCSI support" and "SCSI tape support" must also be enabled for this
  6.7442 +  option to work.
  6.7443 +
  6.7444 +  When this option is disabled (N), the SCSI portion of the driver
  6.7445 +  is not compiled.
  6.7446 +
  6.7447 +Enable monitor thread
  6.7448 +CONFIG_CISS_MONITOR_THREAD
  6.7449 +  Intended for use with multipath configurations (see the md driver).
  6.7450 +  This option allows a per-adapter monitoring thread to periodically
  6.7451 +  poll the adapter to detect failure modes in which the processor
  6.7452 +  is unable to receive interrupts from the adapter, thus enabling 
  6.7453 +  fail-over to an alternate adapter in such situations.  See 
  6.7454 +  <file:Documentation/cciss.txt> for more details.
  6.7455 +
  6.7456 +QuickNet Internet LineJack/PhoneJack support
  6.7457 +CONFIG_PHONE_IXJ
  6.7458 +  Say M if you have a telephony card manufactured by Quicknet
  6.7459 +  Technologies, Inc.  These include the Internet PhoneJACK and
  6.7460 +  Internet LineJACK Telephony Cards. You will get a module called
  6.7461 +  ixj.o.
  6.7462 +
  6.7463 +  For the ISA versions of these products, you can configure the
  6.7464 +  cards using the isapnp tools (pnpdump/isapnp) or you can use the
  6.7465 +  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
  6.7466 +
  6.7467 +  For more information on these cards, see Quicknet's web site at:
  6.7468 +  <http://www.quicknet.net/>.
  6.7469 +
  6.7470 +  If you do not have any Quicknet telephony cards, you can safely
  6.7471 +  say N here.
  6.7472 +
  6.7473 +QuickNet Internet LineJack/PhoneJack PCMCIA support
  6.7474 +CONFIG_PHONE_IXJ_PCMCIA
  6.7475 +  Say Y here to configure in PCMCIA service support for the Quicknet
  6.7476 +  cards manufactured by Quicknet Technologies, Inc.  This builds an
  6.7477 +  additional support module for the PCMCIA version of the card.
  6.7478 +
  6.7479 +FORE Systems 200E-series
  6.7480 +CONFIG_ATM_FORE200E_MAYBE
  6.7481 +  This is a driver for the FORE Systems 200E-series ATM adapter
  6.7482 +  cards. It simultaneously supports PCA-200E and SBA-200E models
  6.7483 +  on PCI and SBUS hosts. Say Y (or M to compile as a module
  6.7484 +  named fore_200e.o) here if you have one of these ATM adapters.
  6.7485 +
  6.7486 +  Note that the driver will actually be compiled only if you
  6.7487 +  additionally enable the support for PCA-200E and/or SBA-200E
  6.7488 +  cards.
  6.7489 +
  6.7490 +  See the file <file:Documentation/networking/fore200e.txt> for
  6.7491 +  further details.
  6.7492 +
  6.7493 +Enable PCA-200E card support on PCI-based hosts
  6.7494 +CONFIG_ATM_FORE200E_PCA
  6.7495 +  Say Y here if you want your PCA-200E cards to be probed.
  6.7496 +
  6.7497 +Use default PCA-200E firmware
  6.7498 +CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
  6.7499 +  Use the default PCA-200E firmware data shipped with the driver.
  6.7500 +
  6.7501 +  Normal users do not have to deal with the firmware stuff, so
  6.7502 +  they should say Y here.
  6.7503 +
  6.7504 +Pathname of user-supplied binary firmware
  6.7505 +CONFIG_ATM_FORE200E_PCA_FW
  6.7506 +  This defines the pathname of an alternative PCA-200E binary
  6.7507 +  firmware image supplied by the user. This pathname may be
  6.7508 +  absolute or relative to the drivers/atm directory.
  6.7509 +
  6.7510 +  The driver comes with an adequate firmware image, so normal users do
  6.7511 +  not have to supply an alternative one. They just say Y to "Use
  6.7512 +  default PCA-200E firmware" instead.
  6.7513 +
  6.7514 +Enable SBA-200E card support on SBUS-based hosts
  6.7515 +CONFIG_ATM_FORE200E_SBA
  6.7516 +  Say Y here if you want your SBA-200E cards to be probed.
  6.7517 +
  6.7518 +Use default SBA-200E firmware
  6.7519 +CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
  6.7520 +  Use the default SBA-200E firmware data shipped with the driver.
  6.7521 +
  6.7522 +  Normal users do not have to deal with the firmware stuff, so
  6.7523 +  they should say Y here.
  6.7524 +
  6.7525 +Pathname of user-supplied binary firmware
  6.7526 +CONFIG_ATM_FORE200E_SBA_FW
  6.7527 +  This defines the pathname of an alternative SBA-200E binary
  6.7528 +  firmware image supplied by the user. This pathname may be
  6.7529 +  absolute or relative to the drivers/atm directory.
  6.7530 +
  6.7531 +  The driver comes with an adequate firmware image, so normal users do
  6.7532 +  not have to supply an alternative one. They just say Y to "Use
  6.7533 +  default SBA-200E firmware", above.
  6.7534 +
  6.7535 +Maximum number of tx retries
  6.7536 +CONFIG_ATM_FORE200E_TX_RETRY
  6.7537 +  Specifies the number of times the driver attempts to transmit
  6.7538 +  a message before giving up, if the transmit queue of the ATM card
  6.7539 +  is transiently saturated.
  6.7540 +
  6.7541 +  Saturation of the transmit queue may occur only under extreme
  6.7542 +  conditions, e.g. when a fast host continuously submits very small
  6.7543 +  frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
  6.7544 +
  6.7545 +  Note that under common conditions, it is unlikely that you encounter
  6.7546 +  a saturation of the transmit queue, so the retry mechanism never
  6.7547 +  comes into play.
  6.7548 +
  6.7549 +Debugging level (0-3)
  6.7550 +CONFIG_ATM_FORE200E_DEBUG
  6.7551 +  Specifies the level of debugging messages issued by the driver.
  6.7552 +  The verbosity of the driver increases with the value of this
  6.7553 +  parameter.
  6.7554 +
  6.7555 +  When active, these messages can have a significant impact on
  6.7556 +  the performances of the driver, and the size of your syslog files!
  6.7557 +  Keep the debugging level to 0 during normal operations.
  6.7558 +
  6.7559 +ForeRunner HE Series
  6.7560 +CONFIG_ATM_HE
  6.7561 +  This is a driver for the Marconi ForeRunner HE-series ATM adapter
  6.7562 +  cards. It simultaneously supports the 155 and 622 versions.
  6.7563 +
  6.7564 +Use S/UNI PHY driver
  6.7565 +  Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
  6.7566 +  HE cards.  This driver provides carrier detection some statistics.
  6.7567 +
  6.7568 +PPP over ATM
  6.7569 +CONFIG_PPPOATM
  6.7570 +  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  6.7571 +  This implementation does not yet comply with section 8 of RFC2364,
  6.7572 +  which can lead to bad results idf the ATM peer loses state and 
  6.7573 +  changes its encapsulation unilaterally.
  6.7574 +
  6.7575 +Fusion MPT device support
  6.7576 +CONFIG_FUSION
  6.7577 +  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
  6.7578 +  provides high performance SCSI host initiator, and LAN [1] interface
  6.7579 +  services to a host system.  The Fusion architecture is capable of
  6.7580 +  duplexing these protocols on high-speed Fibre Channel
  6.7581 +  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
  6.7582 +  physical medium.
  6.7583 +
  6.7584 +          [1] LAN is not supported on parallel SCSI medium.
  6.7585 +
  6.7586 +  These drivers require a Fusion MPT compatible PCI adapter installed
  6.7587 +  in the host system.  MPT adapters contain specialized I/O processors
  6.7588 +  to handle I/O workload, and more importantly to offload this work
  6.7589 +  from the host CPU(s).
  6.7590 +
  6.7591 +  If you have Fusion MPT hardware and want to use it, you can say
  6.7592 +  Y or M here to add MPT (base + ScsiHost) drivers.
  6.7593 +    <Y> = build lib (fusion.o), and link [static] into the kernel [2]
  6.7594 +          proper
  6.7595 +    <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
  6.7596 +          mptscsih.o)
  6.7597 +
  6.7598 +          [2] In order enable capability to boot the linux kernel
  6.7599 +              natively from a Fusion MPT target device, you MUST
  6.7600 +               answer Y here! (currently requires CONFIG_BLK_DEV_SD)
  6.7601 +          [3] This support is also available as a module ( = code
  6.7602 +              which can be inserted in and removed from the running
  6.7603 +              kernel whenever you want).  If you want to compile as
  6.7604 +              modules, say M here and read
  6.7605 +              <file:Documentation/modules.txt>.
  6.7606 +
  6.7607 +  If unsure, say N.
  6.7608 +
  6.7609 +  If you say Y or M here you will get a choice of these
  6.7610 +  additional protocol and support module options:         Module Name:
  6.7611 +    <M>   Enhanced SCSI error reporting                     (isense.o)
  6.7612 +    <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
  6.7613 +    <M>   Fusion MPT LAN driver                             (mptlan.o)
  6.7614 +
  6.7615 +  ---
  6.7616 +  Fusion MPT is trademark of LSI Logic Corporation, and its
  6.7617 +  architecture is based on LSI Logic's Message Passing Interface (MPI)
  6.7618 +  specification.
  6.7619 +
  6.7620 +Maximum number of scatter gather entries
  6.7621 +CONFIG_FUSION_MAX_SGE
  6.7622 +  This option allows you to specify the maximum number of scatter-
  6.7623 +  gather entries per I/O. The driver defaults to 40, a reasonable number
  6.7624 +  for most systems. However, the user may increase this up to 128.
  6.7625 +  Increasing this parameter will require significantly more memory
  6.7626 +  on a per controller instance. Increasing the parameter is not
  6.7627 +  necessary (or recommended) unless the user will be running
  6.7628 +  large I/O's via the raw interface.
  6.7629 +
  6.7630 +Fusion MPT enhanced SCSI error reporting [optional] module
  6.7631 +CONFIG_FUSION_ISENSE
  6.7632 +  The isense module (roughly stands for Interpret SENSE data) is
  6.7633 +  completely optional.  It simply provides extra English readable
  6.7634 +  strings in SCSI Error Report(s) that might be generated from the
  6.7635 +  Fusion MPT SCSI Host driver, for example when a target device
  6.7636 +  returns a SCSI check condition on a I/O.  Without this module
  6.7637 +  loaded you might see:
  6.7638 +
  6.7639 +    SCSI Error Report =-=-= (ioc0,scsi5:0)
  6.7640 +      SCSI_Status=02h (CHECK_CONDITION)
  6.7641 +      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
  6.7642 +      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  6.7643 +      SenseKey=2h (NOT READY); FRU=02h
  6.7644 +      ASC/ASCQ=29h/00h
  6.7645 +
  6.7646 +  Where otherwise, if this module had been loaded, you would see:
  6.7647 +
  6.7648 +    SCSI Error Report =-=-= (ioc0,scsi5:0)
  6.7649 +      SCSI_Status=02h (CHECK_CONDITION)
  6.7650 +      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
  6.7651 +      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  6.7652 +      SenseKey=2h (NOT READY); FRU=02h
  6.7653 +      ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
  6.7654 +
  6.7655 +  Say M for "Enhanced SCSI error reporting" to compile this optional module,
  6.7656 +  creating a driver named: isense.o.
  6.7657 +
  6.7658 +  NOTE: Support for building this feature into the kernel is not
  6.7659 +  available, due to kernel size considerations.
  6.7660 +
  6.7661 +Fusion MPT misc device (ioctl) driver [optional] module
  6.7662 +CONFIG_FUSION_CTL
  6.7663 +  The Fusion MPT misc device driver provides specialized control
  6.7664 +  of MPT adapters via system ioctl calls.  Use of ioctl calls to
  6.7665 +  the MPT driver requires that you create and use a misc device
  6.7666 +  node ala:
  6.7667 +    mknod /dev/mptctl c 10 240
  6.7668 +
  6.7669 +  One use of this ioctl interface is to perform an upgrade (reflash)
  6.7670 +  of the MPT adapter firmware.  Refer to readme file(s) distributed
  6.7671 +  with the Fusion MPT linux driver for additional details.
  6.7672 +
  6.7673 +  If enabled by saying M to this, a driver named: mptctl.o
  6.7674 +  will be compiled.
  6.7675 +
  6.7676 +  If unsure whether you really want or need this, say N.
  6.7677 +
  6.7678 +Fusion MPT LAN driver [optional]
  6.7679 +CONFIG_FUSION_LAN
  6.7680 +  This module supports LAN IP traffic over Fibre Channel port(s)
  6.7681 +  on Fusion MPT compatible hardware (LSIFC9xx chips).
  6.7682 +  The physical interface used is defined in RFC 2625.
  6.7683 +  Please refer to that document for details.
  6.7684 +
  6.7685 +  Installing this driver requires the knowledge to configure and
  6.7686 +  activate a new network interface, "fc0", using standard Linux tools.
  6.7687 +
  6.7688 +  If enabled by saying M to this, a driver named: mptlan.o
  6.7689 +  will be compiled.
  6.7690 +
  6.7691 +  If unsure whether you really want or need this, say N.
  6.7692 +
  6.7693 +  NOTES: This feature is NOT available nor supported for linux-2.2.x
  6.7694 +  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
  6.7695 +  in order to configure this option.
  6.7696 +  Support for building this feature into the linux kernel is not
  6.7697 +  yet available.
  6.7698 +
  6.7699 +SCSI support
  6.7700 +CONFIG_SCSI
  6.7701 +  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  6.7702 +  any other SCSI device under Linux, say Y and make sure that you know
  6.7703 +  the name of your SCSI host adapter (the card inside your computer
  6.7704 +  that "speaks" the SCSI protocol, also called SCSI controller),
  6.7705 +  because you will be asked for it.
  6.7706 +
  6.7707 +  You also need to say Y here if you want support for the parallel
  6.7708 +  port version of the 100 MB IOMEGA ZIP drive.
  6.7709 +
  6.7710 +  This driver is also available as a module ( = code which can be
  6.7711 +  inserted in and removed from the running kernel whenever you want).
  6.7712 +  The module will be called scsi_mod.o.  If you want to compile it as
  6.7713 +  a module, say M here and read <file:Documentation/modules.txt> and
  6.7714 +  <file:Documentation/scsi.txt>.  However, do not compile this as a
  6.7715 +  module if your root file system (the one containing the directory /)
  6.7716 +  is located on a SCSI device.
  6.7717 +
  6.7718 +SCSI disk support
  6.7719 +CONFIG_BLK_DEV_SD
  6.7720 +  If you want to use a SCSI hard disk or the SCSI or parallel port
  6.7721 +  version of the IOMEGA ZIP drive under Linux, say Y and read the
  6.7722 +  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  6.7723 +  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  6.7724 +  CD-ROMs.
  6.7725 +
  6.7726 +  This driver is also available as a module ( = code which can be
  6.7727 +  inserted in and removed from the running kernel whenever you want).
  6.7728 +  The module will be called sd_mod.o.  If you want to compile it as a
  6.7729 +  module, say M here and read <file:Documentation/modules.txt> and
  6.7730 +  <file:Documentation/scsi.txt>.  Do not compile this driver as a
  6.7731 +  module if your root file system (the one containing the directory /)
  6.7732 +  is located on a SCSI disk. In this case, do not compile the driver
  6.7733 +  for your SCSI host adapter (below) as a module either.
  6.7734 +
  6.7735 +Maximum number of SCSI disks that can be loaded as modules
  6.7736 +CONFIG_SD_EXTRA_DEVS
  6.7737 +  This controls the amount of additional space allocated in tables for
  6.7738 +  drivers that are loaded as modules after the kernel is booted.  In
  6.7739 +  the event that the SCSI core itself was loaded as a module, this
  6.7740 +  value is the number of additional disks that can be loaded after the
  6.7741 +  first host driver is loaded.
  6.7742 +
  6.7743 +  Admittedly this isn't pretty, but there are tons of race conditions
  6.7744 +  involved with resizing the internal arrays on the fly.  Someday this
  6.7745 +  flag will go away, and everything will work automatically.
  6.7746 +
  6.7747 +  If you don't understand what's going on, go with the default.
  6.7748 +
  6.7749 +Maximum number of SCSI tapes that can be loaded as modules
  6.7750 +CONFIG_ST_EXTRA_DEVS
  6.7751 +  This controls the amount of additional space allocated in tables for
  6.7752 +  drivers that are loaded as modules after the kernel is booted.  In
  6.7753 +  the event that the SCSI core itself was loaded as a module, this
  6.7754 +  value is the number of additional tapes that can be loaded after the
  6.7755 +  first host driver is loaded.
  6.7756 +
  6.7757 +  Admittedly this isn't pretty, but there are tons of race conditions
  6.7758 +  involved with resizing the internal arrays on the fly.  Someday this
  6.7759 +  flag will go away, and everything will work automatically.
  6.7760 +
  6.7761 +  If you don't understand what's going on, go with the default.
  6.7762 +
  6.7763 +SCSI tape support
  6.7764 +CONFIG_CHR_DEV_ST
  6.7765 +  If you want to use a SCSI tape drive under Linux, say Y and read the
  6.7766 +  SCSI-HOWTO, available from
  6.7767 +  <http://www.tldp.org/docs.html#howto>, and
  6.7768 +  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
  6.7769 +  SCSI CD-ROMs.
  6.7770 +
  6.7771 +  This driver is also available as a module ( = code which can be
  6.7772 +  inserted in and removed from the running kernel whenever you want).
  6.7773 +  The module will be called st.o. If you want to compile it as a
  6.7774 +  module, say M here and read <file:Documentation/modules.txt> and
  6.7775 +  <file:Documentation/scsi.txt>.
  6.7776 +
  6.7777 +OnStream SC-x0 SCSI tape support
  6.7778 +CONFIG_CHR_DEV_OSST
  6.7779 +  The OnStream SC-x0 SCSI tape drives can not be driven by the
  6.7780 +  standard st driver, but instead need this special osst driver and
  6.7781 +  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
  6.7782 +  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
  6.7783 +  as well.  Note that there is also a second generation of OnStream
  6.7784 +  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
  6.7785 +  tapes (QIC-157) and can be driven by the standard driver st.
  6.7786 +  For more information, you may have a look at the SCSI-HOWTO
  6.7787 +  <http://www.tldp.org/docs.html#howto>  and
  6.7788 +  <file:drivers/scsi/README.osst>  in the kernel source.
  6.7789 +  More info on the OnStream driver may be found on
  6.7790 +  <http://linux1.onstream.nl/test/>
  6.7791 +  Please also have a look at the standard st docu, as most of it
  6.7792 +  applies to osst as well.
  6.7793 +
  6.7794 +  This driver is also available as a module ( = code which can be
  6.7795 +  inserted in and removed from the running kernel whenever you want).
  6.7796 +  The module will be called osst.o. If you want to compile it as a
  6.7797 +  module, say M here and read <file:Documentation/modules.txt> and
  6.7798 +  <file:Documentation/scsi.txt>.
  6.7799 +
  6.7800 +SCSI CD-ROM support
  6.7801 +CONFIG_BLK_DEV_SR
  6.7802 +  If you want to use a SCSI CD-ROM under Linux, say Y and read the
  6.7803 +  SCSI-HOWTO and the CD-ROM-HOWTO at
  6.7804 +  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  6.7805 +  or M to "ISO 9660 CD-ROM file system support" later.
  6.7806 +
  6.7807 +  This driver is also available as a module ( = code which can be
  6.7808 +  inserted in and removed from the running kernel whenever you want).
  6.7809 +  The module will be called sr_mod.o. If you want to compile it as a
  6.7810 +  module, say M here and read <file:Documentation/modules.txt> and
  6.7811 +  <file:Documentation/scsi.txt>.
  6.7812 +
  6.7813 +Maximum number of CD-ROM devices that can be loaded as modules
  6.7814 +CONFIG_SR_EXTRA_DEVS
  6.7815 +  This controls the amount of additional space allocated in tables for
  6.7816 +  drivers that are loaded as modules after the kernel is booted. In
  6.7817 +  the event that the SCSI core itself was loaded as a module, this
  6.7818 +  value is the number of additional CD-ROMs that can be loaded after
  6.7819 +  the first host driver is loaded.
  6.7820 +
  6.7821 +  Admittedly this isn't pretty, but there are tons of race conditions
  6.7822 +  involved with resizing the internal arrays on the fly.  Someday this
  6.7823 +  flag will go away, and everything will work automatically.
  6.7824 +
  6.7825 +  If you don't understand what's going on, go with the default.
  6.7826 +
  6.7827 +Enable vendor-specific extensions (for SCSI CD-ROM)
  6.7828 +CONFIG_BLK_DEV_SR_VENDOR
  6.7829 +  This enables the usage of vendor specific SCSI commands. This is
  6.7830 +  required to support multisession CDs with old NEC/TOSHIBA cdrom
  6.7831 +  drives (and HP Writers). If you have such a drive and get the first
  6.7832 +  session only, try saying Y here; everybody else says N.
  6.7833 +
  6.7834 +SCSI generic support
  6.7835 +CONFIG_CHR_DEV_SG
  6.7836 +  If you want to use SCSI scanners, synthesizers or CD-writers or just
  6.7837 +  about anything having "SCSI" in its name other than hard disks,
  6.7838 +  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
  6.7839 +  directly, so you need some additional software which knows how to
  6.7840 +  talk to these devices using the SCSI protocol:
  6.7841 +
  6.7842 +  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
  6.7843 +  writer software look at Cdrtools
  6.7844 +  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
  6.7845 +  and for burning a "disk at once": CDRDAO
  6.7846 +  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
  6.7847 +  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
  6.7848 +  For other devices, it's possible that you'll have to write the
  6.7849 +  driver software yourself. Please read the file
  6.7850 +  <file:Documentation/scsi-generic.txt> for more information.
  6.7851 +
  6.7852 +  If you want to compile this as a module ( = code which can be
  6.7853 +  inserted in and removed from the running kernel whenever you want),
  6.7854 +  say M here and read <file:Documentation/modules.txt> and
  6.7855 +  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
  6.7856 +  say N.
  6.7857 +
  6.7858 +Probe all LUNs on each SCSI device
  6.7859 +CONFIG_SCSI_MULTI_LUN
  6.7860 +  If you have a SCSI device that supports more than one LUN (Logical
  6.7861 +  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
  6.7862 +  can say Y here to force the SCSI driver to probe for multiple LUNs.
  6.7863 +  A SCSI device with multiple LUNs acts logically like multiple SCSI
  6.7864 +  devices. The vast majority of SCSI devices have only one LUN, and
  6.7865 +  so most people can say N here and should in fact do so, because it
  6.7866 +  is safer.
  6.7867 +
  6.7868 +Verbose SCSI error reporting (kernel size +=12K)
  6.7869 +CONFIG_SCSI_CONSTANTS
  6.7870 +  The error messages regarding your SCSI hardware will be easier to
  6.7871 +  understand if you say Y here; it will enlarge your kernel by about
  6.7872 +  12 KB. If in doubt, say Y.
  6.7873 +
  6.7874 +SCSI logging facility
  6.7875 +CONFIG_SCSI_LOGGING
  6.7876 +  This turns on a logging facility that can be used to debug a number
  6.7877 +  of SCSI related problems.
  6.7878 +
  6.7879 +  If you say Y here, no logging output will appear by default, but you
  6.7880 +  can enable logging by saying Y to "/proc file system support" and
  6.7881 +  "Sysctl support" below and executing the command
  6.7882 +
  6.7883 +     echo "scsi log token [level]" > /proc/scsi/scsi
  6.7884 +
  6.7885 +  at boot time after the /proc file system has been mounted.
  6.7886 +
  6.7887 +  There are a number of things that can be used for 'token' (you can
  6.7888 +  find them in the source: <file:drivers/scsi/scsi.c>), and this
  6.7889 +  allows you to select the types of information you want, and the
  6.7890 +  level allows you to select the level of verbosity.
  6.7891 +
  6.7892 +  If you say N here, it may be harder to track down some types of SCSI
  6.7893 +  problems. If you say Y here your kernel will be somewhat larger, but
  6.7894 +  there should be no noticeable performance impact as long as you have
  6.7895 +  logging turned off.
  6.7896 +
  6.7897 +QDIO base support for IBM S/390 and zSeries
  6.7898 +CONFIG_QDIO
  6.7899 +  This driver provides the Queued Direct I/O base support for the
  6.7900 +  IBM S/390 (G5 and G6) and eServer zSeries (z800 and z900).
  6.7901 +
  6.7902 +  For details please refer to the documentation provided by IBM at
  6.7903 +  <http://www10.software.ibm.com/developerworks/opensource/linux390>
  6.7904 +
  6.7905 +  This driver is also available as a module ( = code which can be
  6.7906 +  inserted in and removed from the running kernel whenever you want).
  6.7907 +  The module will be called qdio.o. If you want to compile it as a
  6.7908 +  module, say M here and read <file:Documentation/modules.txt>.
  6.7909 +
  6.7910 +  If unsure, say Y.
  6.7911 +
  6.7912 +Performance statistics for QDIO base support
  6.7913 +CONFIG_QDIO_PERF_STATS
  6.7914 +  Say Y here to get performance statistics in /proc/qdio_perf
  6.7915 +
  6.7916 +  If unsure, say N.
  6.7917 +
  6.7918 +SGI WD93C93 SCSI Driver
  6.7919 +CONFIG_SCSI_SGIWD93
  6.7920 +  Say Y here to support the on-board WD93C93 SCSI controller found (a)
  6.7921 +  on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
  6.7922 +  ARM-based machines.
  6.7923 +
  6.7924 +DEC NCR53C94 SCSI Driver
  6.7925 +CONFIG_SCSI_DECNCR
  6.7926 +  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
  6.7927 +  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
  6.7928 +
  6.7929 +AdvanSys SCSI support
  6.7930 +CONFIG_SCSI_ADVANSYS
  6.7931 +  This is a driver for all SCSI host adapters manufactured by
  6.7932 +  AdvanSys. It is documented in the kernel source in
  6.7933 +  <file:drivers/scsi/advansys.c>.
  6.7934 +
  6.7935 +  This driver is also available as a module ( = code which can be
  6.7936 +  inserted in and removed from the running kernel whenever you want).
  6.7937 +  If you want to compile it as a module, say M here and read
  6.7938 +  <file:Documentation/modules.txt>.  The module will be called
  6.7939 +  advansys.o.
  6.7940 +
  6.7941 +Adaptec AHA152X/2825 support
  6.7942 +CONFIG_SCSI_AHA152X
  6.7943 +  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
  6.7944 +  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
  6.7945 +  must be manually specified in this case.
  6.7946 +
  6.7947 +  It is explained in section 3.3 of the SCSI-HOWTO, available from
  6.7948 +  <http://www.tldp.org/docs.html#howto>. You might also want to
  6.7949 +  read the file <file:drivers/scsi/README.aha152x>.
  6.7950 +
  6.7951 +  This driver is also available as a module ( = code which can be
  6.7952 +  inserted in and removed from the running kernel whenever you want).
  6.7953 +  The module will be called aha152x.o. If you want to compile it as a
  6.7954 +  module, say M here and read <file:Documentation/modules.txt>.
  6.7955 +
  6.7956 +Adaptec AHA1542 support
  6.7957 +CONFIG_SCSI_AHA1542
  6.7958 +  This is support for a SCSI host adapter.  It is explained in section
  6.7959 +  3.4 of the SCSI-HOWTO, available from
  6.7960 +  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
  6.7961 +  purchased by Adaptec, and some former Trantor products are being
  6.7962 +  sold under the Adaptec name.  If it doesn't work out of the box, you
  6.7963 +  may have to change some settings in <file:drivers/scsi/aha1542.h>.
  6.7964 +
  6.7965 +  If you want to compile this as a module ( = code which can be
  6.7966 +  inserted in and removed from the running kernel whenever you want),
  6.7967 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.7968 +  will be called aha1542.o.
  6.7969 +
  6.7970 +Adaptec AHA1740 support
  6.7971 +CONFIG_SCSI_AHA1740
  6.7972 +  This is support for a SCSI host adapter.  It is explained in section
  6.7973 +  3.5 of the SCSI-HOWTO, available from
  6.7974 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  6.7975 +  of the box, you may have to change some settings in
  6.7976 +  <file:drivers/scsi/aha1740.h>.
  6.7977 +
  6.7978 +  This driver is also available as a module ( = code which can be
  6.7979 +  inserted in and removed from the running kernel whenever you want).
  6.7980 +  The module will be called aha1740.o.  If you want to compile it as a
  6.7981 +  module, say M here and read <file:Documentation/modules.txt>.
  6.7982 +
  6.7983 +Adaptec AIC7xxx support
  6.7984 +CONFIG_SCSI_AIC7XXX
  6.7985 +  This driver supports all of Adaptec's Fast through Ultra 160 PCI
  6.7986 +  based SCSI controllers as well as the aic7770 based EISA and VLB
  6.7987 +  SCSI controllers (the 274x and 284x series).  For AAA and ARO based
  6.7988 +  configurations, only SCSI functionality is provided.
  6.7989 +
  6.7990 +  If you want to compile the driver as a module ( = code which can be
  6.7991 +  inserted in and removed from the running kernel whenever you want),
  6.7992 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.7993 +  will be called aic7xxx.o.
  6.7994 +
  6.7995 +Maximum number of TCQ commands per device
  6.7996 +CONFIG_AIC7XXX_CMDS_PER_DEVICE
  6.7997 +  Specify the number of commands you would like to allocate per SCSI
  6.7998 +  device when Tagged Command Queueing (TCQ) is enabled on that device.
  6.7999 +
  6.8000 +  This is an upper bound value for the number of tagged transactions
  6.8001 +  to be used for any device.  The aic7xxx driver will automatically
  6.8002 +  vary this number based on device behavior.  For devices with a
  6.8003 +  fixed maximum, the driver will eventually lock to this maximum
  6.8004 +  and display a console message indicating this value.
  6.8005 +
  6.8006 +  Due to resource allocation issues in the Linux SCSI mid-layer, using
  6.8007 +  a high number of commands per device may result in memory allocation
  6.8008 +  failures when many devices are attached to the system.  For this reason,
  6.8009 +  the default is set to 32.  Higher values may result in higer performance
  6.8010 +  on some devices.  The upper bound is 253. 0 disables tagged queueing.
  6.8011 +
  6.8012 +  Per device tag depth can be controlled via the kernel command line
  6.8013 +  "tag_info" option.  See drivers/scsi/aic7xxx/README.aic7xxx
  6.8014 +  for details.
  6.8015 +
  6.8016 +  Default: 32
  6.8017 +
  6.8018 +Initial bus reset delay in milli-seconds
  6.8019 +CONFIG_AIC7XXX_RESET_DELAY_MS
  6.8020 +  The number of milliseconds to delay after an initial bus reset.
  6.8021 +  The bus settle delay following all error recovery actions is
  6.8022 +  dictated by the SCSI layer and is not affected by this value.
  6.8023 +
  6.8024 +  Default: 15000 (15 seconds)
  6.8025 +
  6.8026 +Probe for EISA and VL AIC7XXX Adapters
  6.8027 +CONFIG_AIC7XXX_PROBE_EISA_VL
  6.8028 +   Probe for EISA and VLB Aic7xxx controllers.  In many newer systems,
  6.8029 +   the invasive probes necessary to detect these controllers can cause
  6.8030 +   other devices to fail.  For this reason, the non-PCI probe code is
  6.8031 +   disabled by default.  The current value of this option can be "toggled"
  6.8032 +   via the no_probe kernel command line option.
  6.8033 +
  6.8034 +CONFIG_AIC7XXX_BUILD_FIRMWARE
  6.8035 +  This option should only be enabled if you are modifying the firmware
  6.8036 +  source to the aic7xxx driver and wish to have the generated firmware
  6.8037 +  include files updated during a normal kernel build.  The assembler
  6.8038 +  for the firmware requires lex and yacc or their equivalents, as well
  6.8039 +  as the db v1 library.  You may have to install additional packages
  6.8040 +  or modify the assembler Makefile or the files it includes if your
  6.8041 +  build environment is different than that of the author.
  6.8042 +
  6.8043 +Compile in Debugging Code
  6.8044 +CONFIG_AIC7XXX_DEBUG_ENABLE
  6.8045 +  Compile in aic7xxx debugging code that can be useful in diagnosing
  6.8046 +  driver errors.
  6.8047 +
  6.8048 +Debug code enable mask (2048 for all debugging)
  6.8049 +CONFIG_AIC7XXX_DEBUG_MASK
  6.8050 +  Bit mask of debug options that is only valid if the
  6.8051 +  CONFIG_AIC7XXX_DEBUG_ENBLE option is enabled.  The bits in this mask
  6.8052 +  are defined in the drivers/scsi/aic7xxx/aic7xxx.h - search for the
  6.8053 +  variable ahc_debug in that file to find them.
  6.8054 +
  6.8055 +  Default: 0
  6.8056 +
  6.8057 +Decode registers during diagnostics
  6.8058 +CONFIG_AIC7XXX_REG_PRETTY_PRINT
  6.8059 +  Compile in register value tables for the output of expanded register
  6.8060 +  contents in diagnostics.  This make it much easier to understand debug
  6.8061 +  output without having to refer to a data book and/or the aic7xxx.reg file.
  6.8062 +
  6.8063 +Old Adaptec AIC7xxx support
  6.8064 +CONFIG_SCSI_AIC7XXX_OLD
  6.8065 +  WARNING This driver is an older aic7xxx driver and is no longer
  6.8066 +  under active development.  Adaptec, Inc. is writing a new driver to
  6.8067 +  take the place of this one, and it is recommended that whenever
  6.8068 +  possible, people should use the new Adaptec written driver instead
  6.8069 +  of this one.  This driver will eventually be phased out entirely.
  6.8070 +
  6.8071 +  This is support for the various aic7xxx based Adaptec SCSI
  6.8072 +  controllers. These include the 274x EISA cards; 284x VLB cards;
  6.8073 +  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
  6.8074 +  motherboard based SCSI controllers from Adaptec. It does not support
  6.8075 +  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
  6.8076 +  support them. It does not support the 2920 cards from Adaptec that
  6.8077 +  use the Future Domain SCSI controller chip. For those cards, you
  6.8078 +  need the "Future Domain 16xx SCSI support" driver.
  6.8079 +
  6.8080 +  In general, if the controller is based on an Adaptec SCSI controller
  6.8081 +  chip from the aic777x series or the aic78xx series, this driver
  6.8082 +  should work. The only exception is the 7810 which is specifically
  6.8083 +  not supported (that's the RAID controller chip on the AAA-13x
  6.8084 +  cards).
  6.8085 +
  6.8086 +  Note that the AHA2920 SCSI host adapter is *not* supported by this
  6.8087 +  driver; choose "Future Domain 16xx SCSI support" instead if you have
  6.8088 +  one of those.
  6.8089 +
  6.8090 +  Information on the configuration options for this controller can be
  6.8091 +  found by checking the help file for each of the available
  6.8092 +  configuration options. You should read
  6.8093 +  <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
  6.8094 +  contacting the maintainer with any questions.  The SCSI-HOWTO,
  6.8095 +  available from <http://www.tldp.org/docs.html#howto>, can also
  6.8096 +  be of great help.
  6.8097 +
  6.8098 +  If you want to compile this driver as a module ( = code which can be
  6.8099 +  inserted in and removed from the running kernel whenever you want),
  6.8100 +  say M here and read <file:Documentation/modules.txt>.  The module
  6.8101 +  will be called aic7xxx_old.o.
  6.8102 +
  6.8103 +Enable tagged command queueing (TCQ) by default
  6.8104 +CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
  6.8105 +  This option causes the aic7xxx driver to attempt to use Tagged
  6.8106 +  Command Queueing (TCQ) on all devices that claim to support it.
  6.8107 +
  6.8108 +  TCQ is a feature of SCSI-2 which improves performance: the host
  6.8109 +  adapter can send several SCSI commands to a device's queue even if
  6.8110 +  previous commands haven't finished yet.  Because the device is
  6.8111 +  intelligent, it can optimize its operations (like head positioning)
  6.8112 +  based on its own request queue.  Not all devices implement this
  6.8113 +  correctly.
  6.8114 +
  6.8115 +  If you say Y here, you can still turn off TCQ on troublesome devices
  6.8116 +  with the use of the tag_info boot parameter.  See the file
  6.8117 +  <file:drivers/scsi/README.aic7xxx> for more information on that and
  6.8118 +  other aic7xxx setup commands.  If this option is turned off, you may
  6.8119 +  still enable TCQ on known good devices by use of the tag_info boot
  6.8120 +  parameter.
  6.8121 +
  6.8122 +  If you are unsure about your devices then it is safest to say N
  6.8123 +  here.
  6.8124 +
  6.8125 +  However, TCQ can increase performance on some hard drives by as much
  6.8126 +  as 50% or more, so it is recommended that if you say N here, you
  6.8127 +  should at least read the <file:drivers/scsi/README.aic7xxx> file so
  6.8128 +  you will know how to enable this option manually should your drives
  6.8129 +  prove to be safe in regards to TCQ.
  6.8130 +
  6.8131 +  Conversely, certain drives are known to lock up or cause bus resets
  6.8132 +  when TCQ is enabled on them.  If you have a Western Digital
  6.8133 +  Enterprise SCSI drive for instance, then don't even bother to enable
  6.8134 +  TCQ on it as the drive will become unreliable, and it will actually
  6.8135 +  reduce performance.
  6.8136 +
  6.8137 +Default number of TCQ commands per device
  6.8138 +CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
  6.8139 +  Specify the number of commands you would like to allocate per SCSI
  6.8140 +  device when Tagged Command Queueing (TCQ) is enabled on that device.
  6.8141 +
  6.8142 +  Reasonable figures are in the range of 8 to 24 commands per device,
  6.8143 +  but depending on hardware could be increased or decreased from that
  6.8144 +  figure. If the number is too high for any particular device, the
  6.8145 +  driver will automatically compensate usually after only 10 minutes
  6.8146 +  of uptime. It will not hinder performance if some of your devices
  6.8147 +  eventually have their command depth reduced, but is a waste of
  6.8148 +  memory if all of your devices end up reducing this number down to a
  6.8149 +  more reasonable figure.
  6.8150 +
  6.8151 +  NOTE: Certain very broken drives are known to lock up when given
  6.8152 +  more commands than they like to deal with. Quantum Fireball drives
  6.8153 +  are the most common in this category. For the Quantum Fireball
  6.8154 +  drives it is suggested to use no more than 8 commands per device.
  6.8155 +
  6.8156 +  Default: 8
  6.8157 +
  6.8158 +Collect statistics to report in /proc
  6.8159 +CONFIG_AIC7XXX_OLD_PROC_STATS
  6.8160 +  This option tells the driver to keep track of how many commands have
  6.8161 +  been sent to each particular device and report that information to
  6.8162 +  the user via the /proc/scsi/aic7xxx/n file, where n is the number of
  6.8163 +  the aic7xxx controller you want the information on. This adds a
  6.8164 +  small amount of overhead to each and every SCSI command the aic7xxx
  6.8165 +  driver handles, so if you aren't really interested in this
  6.8166 +  information, it is best to leave it disabled. This will only work if
  6.8167 +  you also say Y to "/proc file system support", below.
  6.8168 +
  6.8169 +  If unsure, say N.
  6.8170 +
  6.8171 +CONFIG_SCSI_AIC79XX
  6.8172 +  This driver supports all of Adaptec's Ultra 320 PCI-X based SCSI controllers.
  6.8173 +
  6.8174 +CONFIG_AIC79XX_CMDS_PER_DEVICE 32
  6.8175 +  Specify the number of commands you would like to allocate per SCSI
  6.8176 +  device when Tagged Command Queueing (TCQ) is enabled on that device.
  6.8177 +
  6.8178 +  This is an upper bound value for the number of tagged transactions
  6.8179 +  to be used for any device.  The aic7xxx driver will automatically
  6.8180 +  vary this number based on device behavior.  For devices with a
  6.8181 +  fixed maximum, the driver will eventually lock to this maximum
  6.8182 +  and display a console message indicating this value.
  6.8183 +
  6.8184 +  Due to resource allocation issues in the Linux SCSI mid-layer, using
  6.8185 +  a high number of commands per device may result in memory allocation
  6.8186 +  failures when many devices are attached to the system.  For this reason,
  6.8187 +  the default is set to 32.  Higher values may result in higer performance
  6.8188 +  on some devices.  The upper bound is 253.
  6.8189 +
  6.8190 +  Per device tag depth can be controlled via the kernel command line
  6.8191 +  "tag_info" option.  See drivers/scsi/aic7xxx/README.aic79xx
  6.8192 +  for details.
  6.8193 +
  6.8194 +  Default: 32
  6.8195 +
  6.8196 +CONFIG_AIC79XX_RESET_DELAY_MS 15000
  6.8197 +  The number of milliseconds to delay after an initial bus reset.
  6.8198 +  The bus settle delay following all error recovery actions is
  6.8199 +  dictated by the SCSI layer and is not affected by this value.
  6.8200 +
  6.8201 +  Default: 15000 (15 seconds)
  6.8202 +
  6.8203 +CONFIG_AIC79XX_BUILD_FIRMWARE
  6.8204 +  This option should only be enabled if you are modifying the firmware
  6.8205 +  source to the aic7xxx driver and wish to have the generated firmware
  6.8206 +  include files updated during a normal kernel build.  The assembler
  6.8207 +  for the firmware requires lex and yacc or their equivalents, as well
  6.8208 +  as the db v1 library.  You may have to install additional packages
  6.8209 +  or modify the assembler Makefile or the files it includes if your
  6.8210 +  build environment is different than that of the author.
  6.8211 +
  6.8212 +CONFIG_AIC79XX_ENABLE_RD_STRM
  6.8213 +  Read Streaming is a U320 protocol option that should enhance performance.
  6.8214 +  Early U320 drive firmware actually performs slower with read streaming
  6.8215 +  enabled so it is disabled by default.  Read Streaming can be configured
  6.8216 +  in much the same way as tagged queueing using the "rd_strm" command line
  6.8217 +  option.  See drivers/scsi/aic7xxx/README.aic79xx for details.
  6.8218 +
  6.8219 +CONFIG_AIC79XX_DEBUG_ENABLE
  6.8220 +  Compile in aic79xx debugging code that can be useful in diagnosing
  6.8221 +  driver errors.
  6.8222 +
  6.8223 +CONFIG_AIC79XX_DEBUG_MASK
  6.8224 +  Bit mask of debug options that is only valid if the
  6.8225 +  CONFIG_AIC79XX_DEBUG_ENBLE option is enabled.  The bits in this mask
  6.8226 +  are defined in the drivers/scsi/aic7xxx/aic79xx.h - search for the
  6.8227 +  variable ahd_debug in that file to find them.
  6.8228 +
  6.8229 +  Default: 0
  6.8230 +
  6.8231