What's New For 2.6.0-test3 on ia64

Home   Search

array(2464) { [0]=> array(11) { ["entry_id"]=> string(1) "1" ["entry_type"]=> string(4) "MENU" ["text"]=> string(26) "Linux Kernel Configuration" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1]=> array(11) { ["entry_id"]=> string(1) "2" ["entry_type"]=> string(4) "MENU" ["text"]=> string(27) "Code maturity level options" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [2]=> array(11) { ["entry_id"]=> string(1) "3" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "Prompt for development and/or incomplete code/drivers" ["name"]=> string(12) "EXPERIMENTAL" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1587) " Some of the various things that Linux supports (such as network drivers, file systems, network protocols, etc.) can be in a state of development where the functionality, stability, or the level of testing is not yet high enough for general use. This is usually known as the "alpha-test" phase among developers. If a feature is currently in alpha-test, then the developers usually discourage uninformed widespread use of this feature by the general public to avoid "Why doesn't this work?" type mail messages. However, active testing and use of these systems is welcomed. Just be aware that it may not meet the normal level of reliability or it may fail to work in some special cases. Detailed bug reports from people familiar with the kernel internals are usually welcomed by the developers (before submitting bug reports, please read the documents , , , , and in the kernel source). This option will also make obsoleted drivers available. These are drivers that have been replaced by something else, and/or are scheduled to be removed in a future kernel release. Unless you intend to help test and develop a feature or driver that falls into this category, or you have a situation that requires using these features, you should probably say N here, which will cause the configurator to present you with fewer choices. If you say Y here, you will be offered the choice of using features or drivers that are currently considered to be in the alpha-test phase. " } [3]=> array(11) { ["entry_id"]=> string(1) "4" ["entry_type"]=> string(4) "MENU" ["text"]=> string(13) "General setup" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [4]=> array(11) { ["entry_id"]=> string(1) "5" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Support for paging of anonymous memory" ["name"]=> string(4) "SWAP" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(234) " This option allows you to choose whether you want to have support for socalled swap devices or swap files in your kernel that are used to provide more virtual memory than the actual RAM present in your computer. If unsure say Y. " } [5]=> array(11) { ["entry_id"]=> string(1) "6" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "System V IPC" ["name"]=> string(7) "SYSVIPC" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(597) " Inter Process Communication is a suite of library functions and system calls which let processes (running programs) synchronize and exchange information. It is generally considered to be a good thing, and some programs won't run unless you say Y here. In particular, if you want to run the DOS emulator dosemu under Linux (read the DOSEMU-HOWTO, available from ), you'll need to say Y here. You can find documentation about IPC with "info ipc" and also in section 6.4 of the Linux Programmer's Guide, available from . " } [6]=> array(11) { ["entry_id"]=> string(1) "7" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "BSD Process Accounting" ["name"]=> string(16) "BSD_PROCESS_ACCT" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(578) " If you say Y here, a user level program will be able to instruct the kernel (via a special system call) to write process accounting information to a file: whenever a process exits, information about that process will be appended to the file by the kernel. The information includes things such as creation time, owning user, command name, memory usage, controlling terminal etc. (the complete list is in the struct acct in ). It is up to the user level program to do useful things with this information. This is generally a good idea, so say Y. " } [7]=> array(11) { ["entry_id"]=> string(1) "8" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "Sysctl support" ["name"]=> string(6) "SYSCTL" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(659) " The sysctl interface provides a means of dynamically changing certain kernel parameters and variables on the fly without requiring a recompile of the kernel or reboot of the system. The primary interface consists of a system call, but if you say Y to "/proc file system support", a tree of modifiable sysctl entries will be generated beneath the /proc/sys directory. They are explained in the files in . Note that enabling this option will enlarge the kernel by at least 8 KB. As it is generally a good thing, you should say Y here unless building a kernel for install/rescue disks or your system is very limited in memory. " } [8]=> array(11) { ["entry_id"]=> string(1) "9" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(13) "LOG_BUF_SHIFT" ["value"]=> string(2) "16" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(48) "Kernel log buffer size (16 => 64KB, 17 => 128KB)" ["help_text"]=> NULL } [9]=> array(11) { ["entry_id"]=> string(2) "10" ["entry_type"]=> string(4) "MENU" ["text"]=> string(45) "Remove kernel features (for embedded systems)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [10]=> array(11) { ["entry_id"]=> string(2) "11" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Remove kernel features (for embedded systems)" ["name"]=> string(8) "EMBEDDED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(218) " This option allows certain base kernel features to be removed from the build. This is for specialized environments which can tolerate a "non-standard" kernel. Only use this if you really know what you are doing. " } [11]=> array(11) { ["entry_id"]=> string(2) "12" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Load all symbols for debugging/kksymoops" ["name"]=> string(8) "KALLSYMS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(205) " Say Y here to let the kernel print out symbolic crash information and symbolic stack backtraces. This increases the size of the kernel somewhat, as all symbols have to be loaded into the kernel image. " } [12]=> array(11) { ["entry_id"]=> string(2) "13" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Enable futex support" ["name"]=> string(5) "FUTEX" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(176) " Disabling this option will cause the kernel to be built without support for "fast userspace mutexes". The resulting kernel may not run glibc-based applications correctly. " } [13]=> array(11) { ["entry_id"]=> string(2) "14" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Enable eventpoll support" ["name"]=> string(5) "EPOLL" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(110) " Disabling this option will cause the kernel to be built without support for epoll family of system calls. " } [14]=> array(11) { ["entry_id"]=> string(2) "15" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Anticipatory I/O scheduler" ["name"]=> string(10) "IOSCHED_AS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [15]=> array(11) { ["entry_id"]=> string(2) "16" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Deadline I/O scheduler" ["name"]=> string(16) "IOSCHED_DEADLINE" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [16]=> array(11) { ["entry_id"]=> string(2) "17" ["entry_type"]=> string(4) "MENU" ["text"]=> string(23) "Loadable module support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [17]=> array(11) { ["entry_id"]=> string(2) "18" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Enable loadable module support" ["name"]=> string(7) "MODULES" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(552) " Kernel modules are small pieces of compiled code which can be inserted in or removed from the running kernel, using the programs insmod and rmmod. This is described in the file , including the fact that you have to say "make modules" in order to compile the modules that you chose during kernel configuration. Modules can be device drivers, file systems, binary executable formats, and so on. If you think that you may want to make use of modules with this kernel in the future, then say Y here. If unsure, say Y. " } [18]=> array(11) { ["entry_id"]=> string(2) "19" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Module unloading" ["name"]=> string(13) "MODULE_UNLOAD" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(195) " Without this option you will not be able to unload any modules (note that some modules may not be unloadable anyway), which makes your kernel slightly smaller and simpler. If unsure, say Y. " } [19]=> array(11) { ["entry_id"]=> string(2) "20" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Forced module unloading" ["name"]=> string(19) "MODULE_FORCE_UNLOAD" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(285) " This option allows you to force a module to unload, even if the kernel believes it is unsafe: the kernel will remove the module without waiting for anyone to stop using it (using the -f option to rmmod). This is mainly for kernel developers and desperate users. If unsure, say N. " } [20]=> array(11) { ["entry_id"]=> string(2) "21" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "OBSOLETE_MODPARM" ["name"]=> string(16) "OBSOLETE_MODPARM" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(149) " You need this option to use module parameters on modules which have not been converted to the new module parameter system yet. If unsure, say Y. " } [21]=> array(11) { ["entry_id"]=> string(2) "22" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Module versioning support (EXPERIMENTAL)" ["name"]=> string(11) "MODVERSIONS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(370) " Usually, you have to use modules compiled with your kernel. Saying Y here makes it sometimes possible to use modules compiled for different kernels, by adding enough information to the modules to (hopefully) spot any changes which would make them incompatible with the kernel you are running. If you say Y here, you will need a copy of genksyms. If unsure, say N. " } [22]=> array(11) { ["entry_id"]=> string(2) "23" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Kernel module loader" ["name"]=> string(4) "KMOD" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(565) " Normally when you have selected some drivers and/or file systems to be created as loadable modules, you also have the responsibility to load the corresponding modules (using the programs insmod or modprobe) before you can use them. If you say Y here however, the kernel will be able to load modules for itself: when a part of the kernel needs a module, it runs modprobe with the appropriate arguments, thereby loading the module if it is available. (This is a replacement for kerneld.) Say Y here and read about configuring it in . " } [23]=> array(11) { ["entry_id"]=> string(2) "24" ["entry_type"]=> string(4) "MENU" ["text"]=> string(27) "Processor type and features" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [24]=> array(11) { ["entry_id"]=> string(2) "25" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(4) "IA64" ["name"]=> string(4) "IA64" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(205) " The Itanium Processor Family is Intel's 64-bit successor to the 32-bit X86 line. The IA-64 Linux project has a home page at and a mailing list at linux-ia64@linuxia64.org. " } [25]=> array(11) { ["entry_id"]=> string(2) "26" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(3) "MMU" ["name"]=> string(3) "MMU" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [26]=> array(11) { ["entry_id"]=> string(2) "27" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "RWSEM_XCHGADD_ALGORITHM" ["name"]=> string(23) "RWSEM_XCHGADD_ALGORITHM" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [27]=> array(11) { ["entry_id"]=> string(2) "28" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "TIME_INTERPOLATION" ["name"]=> string(18) "TIME_INTERPOLATION" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [28]=> array(11) { ["entry_id"]=> string(2) "29" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(7) "ITANIUM" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(7) "Itanium" ["help_text"]=> NULL } [29]=> array(11) { ["entry_id"]=> string(2) "30" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(8) "MCKINLEY" ["value"]=> string(1) "2" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(9) "Itanium 2" ["help_text"]=> NULL } [30]=> array(11) { ["entry_id"]=> string(2) "31" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(12) "IA64_GENERIC" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(7) "generic" ["help_text"]=> NULL } [31]=> array(11) { ["entry_id"]=> string(2) "32" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(8) "IA64_DIG" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(13) "DIG-compliant" ["help_text"]=> NULL } [32]=> array(11) { ["entry_id"]=> string(2) "33" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(11) "IA64_HP_SIM" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(12) "HP-simulator" ["help_text"]=> NULL } [33]=> array(11) { ["entry_id"]=> string(2) "34" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(11) "IA64_HP_ZX1" ["value"]=> string(1) "2" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(6) "HP-zx1" ["help_text"]=> NULL } [34]=> array(11) { ["entry_id"]=> string(2) "35" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(12) "IA64_SGI_SN2" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(7) "SGI-SN2" ["help_text"]=> NULL } [35]=> array(11) { ["entry_id"]=> string(2) "36" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(18) "IA64_PAGE_SIZE_4KB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(3) "4KB" ["help_text"]=> NULL } [36]=> array(11) { ["entry_id"]=> string(2) "37" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(18) "IA64_PAGE_SIZE_8KB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(3) "8KB" ["help_text"]=> NULL } [37]=> array(11) { ["entry_id"]=> string(2) "38" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(19) "IA64_PAGE_SIZE_16KB" ["value"]=> string(1) "2" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(4) "16KB" ["help_text"]=> NULL } [38]=> array(11) { ["entry_id"]=> string(2) "39" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(19) "IA64_PAGE_SIZE_64KB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(4) "64KB" ["help_text"]=> NULL } [39]=> array(11) { ["entry_id"]=> string(2) "40" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(4) "ACPI" ["name"]=> string(4) "ACPI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1183) " Advanced Configuration and Power Interface (ACPI) support for Linux requires an ACPI compliant platform (hardware/firmware), and assumes the presence of OS-directed configuration and power management (OSPM) software. This option will enlarge your kernel by about 70K. Linux ACPI provides a robust functional replacement for several legacy configuration and power management intefaces, including the Plug-and-Play BIOS specification (PnP BIOS), the MultiProcessor Specification (MPS), and the Advanced Power Management (APM) specification. If both ACPI and APM support are configured, whichever is loaded first shall be used. The ACPI SourceForge project contains the latest source code, documentation, tools, mailing list subscription, and other information. This project is available at: Linux support for ACPI is based on Intel Corporation's ACPI Component Architecture (ACPI CA). For more information see: ACPI is an open industry specification co-developed by Compaq, Intel, Microsoft, Phoenix, and Toshiba. The specification is available at: " } [40]=> array(11) { ["entry_id"]=> string(2) "41" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "ACPI_EFI" ["name"]=> string(8) "ACPI_EFI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [41]=> array(11) { ["entry_id"]=> string(2) "42" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "ACPI_INTERPRETER" ["name"]=> string(16) "ACPI_INTERPRETER" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [42]=> array(11) { ["entry_id"]=> string(2) "43" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "ACPI_KERNEL_CONFIG" ["name"]=> string(18) "ACPI_KERNEL_CONFIG" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(118) " If you say `Y' here, Linux's ACPI support will use the hardware-level system descriptions found on IA-64 systems. " } [43]=> array(11) { ["entry_id"]=> string(2) "44" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "IA64_BRL_EMU" ["name"]=> string(12) "IA64_BRL_EMU" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [44]=> array(11) { ["entry_id"]=> string(2) "45" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Enable Itanium B-step specific code" ["name"]=> string(22) "ITANIUM_BSTEP_SPECIFIC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(194) " Select this option to build a kernel for an Itanium prototype system with a B-step CPU. You have a B-step CPU if the "revision" field in /proc/cpuinfo has a value in the range from 1 to 4. " } [45]=> array(11) { ["entry_id"]=> string(2) "46" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "IA64_L1_CACHE_SHIFT" ["value"]=> string(1) "7" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(19) "IA64_L1_CACHE_SHIFT" ["help_text"]=> NULL } [46]=> array(11) { ["entry_id"]=> string(2) "47" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Enable McKinley A-step specific code" ["name"]=> string(23) "MCKINLEY_ASTEP_SPECIFIC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(105) " Select this option to build a kernel for an IA-64 McKinley prototype system with any A-stepping CPU. " } [47]=> array(11) { ["entry_id"]=> string(2) "48" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Enable McKinley A0/A1-step specific code" ["name"]=> string(20) "MCKINLEY_A0_SPECIFIC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(111) " Select this option to build a kernel for an IA-64 McKinley prototype system with an A0 or A1 stepping CPU. " } [48]=> array(11) { ["entry_id"]=> string(2) "49" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Enable NUMA support" ["name"]=> string(4) "NUMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(170) " Say Y to compile the kernel to support NUMA (Non-Uniform Memory Access). This option is for configuring high-end multiprocessor server systems. If in doubt, say N. " } [49]=> array(11) { ["entry_id"]=> string(2) "50" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(18) "IA64_NODESIZE_16GB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(4) "16GB" ["help_text"]=> NULL } [50]=> array(11) { ["entry_id"]=> string(2) "51" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(18) "IA64_NODESIZE_64GB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(4) "64GB" ["help_text"]=> NULL } [51]=> array(11) { ["entry_id"]=> string(2) "52" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(19) "IA64_NODESIZE_256GB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(5) "256GB" ["help_text"]=> NULL } [52]=> array(11) { ["entry_id"]=> string(2) "53" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "DISCONTIGMEM" ["name"]=> string(12) "DISCONTIGMEM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(253) " Say Y to support efficient handling of discontiguous physical memory, for architectures which are either NUMA (Non-Uniform Memory Access) or have huge holes in the physical address space for other reasons. See for more. " } [53]=> array(11) { ["entry_id"]=> string(2) "54" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Enable Virtual Mem Map" ["name"]=> string(15) "VIRTUAL_MEM_MAP" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(538) " Say Y to compile the kernel with support for a virtual mem map. This is an alternate method of supporting large holes in the physical address space on non NUMA machines. Since the DISCONTIGMEM option is not supported on machines with the ZX1 chipset, this is the only way of supporting more than 1 Gb of memory on those machines. This code also only takes effect if a memory hole of greater than 1 Gb is found during boot, so it is safe to enable unless you require the DISCONTIGMEM option for your machine. If you are unsure, say Y. " } [54]=> array(11) { ["entry_id"]=> string(2) "55" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Enable IA-64 Machine Check Abort" ["name"]=> string(8) "IA64_MCA" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(87) " Say Y here to enable machine check support for IA-64. If you're unsure, answer Y. " } [55]=> array(11) { ["entry_id"]=> string(2) "56" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(2) "PM" ["name"]=> string(2) "PM" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(774) " "Power Management" means that parts of your computer are shut off or put into a power conserving "sleep" mode if they are not being used. There are two competing standards for doing this: APM and ACPI. If you want to use either one, say Y here and then also to the requisite support below. Power Management is most important for battery powered laptop computers; if you have a laptop, check out the Linux Laptop home page on the WWW at and the Battery Powered Linux mini-HOWTO, available from . Note that, even if you say N here, Linux on the x86 architecture will issue the hlt instruction if nothing is to be done, thereby sending the processor to sleep and saving power. " } [56]=> array(11) { ["entry_id"]=> string(2) "57" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(7) "IOSAPIC" ["name"]=> string(7) "IOSAPIC" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [57]=> array(11) { ["entry_id"]=> string(2) "58" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Enable extra debugging code" ["name"]=> string(17) "IA64_SGI_SN_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(150) " Turns on extra debugging code in the SGI SN (Scalable NUMA) platform for IA-64. Unless you are debugging problems on an SGI SN IA-64 box, say N. " } [58]=> array(11) { ["entry_id"]=> string(2) "59" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Enable SGI Medusa Simulator Support" ["name"]=> string(15) "IA64_SGI_SN_SIM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(114) " If you are compiling a kernel that will run under SGI's IA-64 simulator (Medusa) then say Y, otherwise say N. " } [59]=> array(11) { ["entry_id"]=> string(2) "60" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(67) "Enable autotest (llsc). Option to run cache test instead of booting" ["name"]=> string(17) "IA64_SGI_AUTOTEST" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(226) " Build a kernel used for hardware validation. If you include the keyword "autotest" on the boot command line, the kernel does NOT boot. Instead, it starts all cpus and runs cache coherency tests instead. If unsure, say N. " } [60]=> array(11) { ["entry_id"]=> string(2) "61" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Enable protocol mode for the L1 console" ["name"]=> string(22) "SERIAL_SGI_L1_PROTOCOL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(207) " Uses protocol mode instead of raw mode for the level 1 console on the SGI SN (Scalable NUMA) platform for IA-64. If you are compiling for an SGI SN box then Y is the recommended value, otherwise say N. " } [61]=> array(11) { ["entry_id"]=> string(2) "62" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "PERCPU_IRQ" ["name"]=> string(10) "PERCPU_IRQ" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [62]=> array(11) { ["entry_id"]=> string(2) "63" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "KCORE_ELF" ["name"]=> string(9) "KCORE_ELF" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(785) " If you enabled support for /proc file system then the file /proc/kcore will contain the kernel core image. This can be used in gdb: $ cd /usr/src/linux ; gdb vmlinux /proc/kcore You have two choices here: ELF and A.OUT. Selecting ELF will make /proc/kcore appear in ELF core format as defined by the Executable and Linking Format specification. Selecting A.OUT will choose the old "a.out" format which may be necessary for some old versions of binutils or on some architectures. This is especially useful if you have compiled the kernel with the "-g" option to preserve debugging information. It is mainly used for examining kernel data structures on the live kernel so if you don't understand what this means or are not a kernel hacker, just leave it at its default value ELF. " } [63]=> array(11) { ["entry_id"]=> string(2) "64" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "FORCE_MAX_ZONEORDER" ["value"]=> string(2) "18" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(19) "FORCE_MAX_ZONEORDER" ["help_text"]=> NULL } [64]=> array(11) { ["entry_id"]=> string(2) "65" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "IA-64 Huge TLB Page Support" ["name"]=> string(12) "HUGETLB_PAGE" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [65]=> array(11) { ["entry_id"]=> string(2) "66" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(21) "HUGETLB_PAGE_SIZE_4GB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(3) "4GB" ["help_text"]=> NULL } [66]=> array(11) { ["entry_id"]=> string(2) "67" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(21) "HUGETLB_PAGE_SIZE_1GB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(3) "1GB" ["help_text"]=> NULL } [67]=> array(11) { ["entry_id"]=> string(2) "68" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(23) "HUGETLB_PAGE_SIZE_256MB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(5) "256MB" ["help_text"]=> NULL } [68]=> array(11) { ["entry_id"]=> string(2) "69" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(22) "HUGETLB_PAGE_SIZE_64MB" ["value"]=> string(1) "2" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(4) "64MB" ["help_text"]=> NULL } [69]=> array(11) { ["entry_id"]=> string(2) "70" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(22) "HUGETLB_PAGE_SIZE_16MB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(4) "16MB" ["help_text"]=> NULL } [70]=> array(11) { ["entry_id"]=> string(2) "71" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(21) "HUGETLB_PAGE_SIZE_4MB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(3) "4MB" ["help_text"]=> NULL } [71]=> array(11) { ["entry_id"]=> string(2) "72" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(21) "HUGETLB_PAGE_SIZE_1MB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(3) "1MB" ["help_text"]=> NULL } [72]=> array(11) { ["entry_id"]=> string(2) "73" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(23) "HUGETLB_PAGE_SIZE_256KB" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(5) "256KB" ["help_text"]=> NULL } [73]=> array(11) { ["entry_id"]=> string(2) "74" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Use PAL_HALT_LIGHT in idle loop" ["name"]=> string(13) "IA64_PAL_IDLE" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(311) " Say Y here to enable use of PAL_HALT_LIGHT in the cpu_idle loop. This allows the CPU to enter a low power state when idle. You can enable CONFIG_IA64_PALINFO and check /proc/pal/cpu0/power_info to see the power consumption and latency for this state. If you're unsure your firmware supports it, answer N. " } [74]=> array(11) { ["entry_id"]=> string(2) "75" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "SMP support" ["name"]=> string(3) "SMP" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(638) " This enables support for systems with more than one CPU. If you have a system with only one CPU say N. If you have a system with more than one CPU, say Y. If you say N here, the kernel will run on single and multiprocessor systems, but will use only one CPU of a multiprocessor system. If you say Y here, the kernel will run on many, but not all, singleprocessor system. On a singleprocessor system, the kernel will run faster if you say N here. See also the , , and the SMP-HOWTO available at . If you don't know what to do here, say N. " } [75]=> array(11) { ["entry_id"]=> string(2) "76" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Preemptible Kernel" ["name"]=> string(7) "PREEMPT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(398) " This option reduces the latency of the kernel when reacting to real-time or interactive events by allowing a low priority process to be preempted even if it is in kernel mode executing a system call. This allows applications to run more reliably even when the system is under load. Say Y here if you are building a kernel for a desktop, embedded or real-time system. Say N if you are unsure. " } [76]=> array(11) { ["entry_id"]=> string(2) "77" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Support running of Linux/x86 binaries" ["name"]=> string(12) "IA32_SUPPORT" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(250) " IA-64 processors can execute IA-32 (X86) instructions. By saying Y here, the kernel will include IA-32 system call emulation support which makes it possible to transparently run IA-32 Linux binaries on an IA-64 Linux system. If in doubt, say Y. " } [77]=> array(11) { ["entry_id"]=> string(2) "78" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(6) "COMPAT" ["name"]=> string(6) "COMPAT" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [78]=> array(11) { ["entry_id"]=> string(2) "79" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Performance monitor support" ["name"]=> string(7) "PERFMON" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(261) " Selects whether support for the IA-64 performance monitor hardware is included in the kernel. This makes some kernel data-structures a little bigger and slows down execution a bit, but it is generally a good idea to turn this on. If you're unsure, say Y. " } [79]=> array(11) { ["entry_id"]=> string(2) "80" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "/proc/pal support" ["name"]=> string(12) "IA64_PALINFO" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(351) " If you say Y here, you are able to get PAL (Processor Abstraction Layer) information in /proc/pal. This contains useful information about the processors in your systems, such as cache and TLB sizes and the PAL firmware version in use. To use this option, you have to ensure that the "/proc file system support" (CONFIG_PROC_FS) is enabled, too. " } [80]=> array(11) { ["entry_id"]=> string(2) "81" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "/proc/efi/vars support" ["name"]=> string(8) "EFI_VARS" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(309) " If you say Y here, you are able to get EFI (Extensible Firmware Interface) variable information in /proc/efi/vars. You may read, write, create, and destroy EFI variables through this interface. To use this option, you have to check that the "/proc file system support" (CONFIG_PROC_FS) is enabled, too. " } [81]=> array(11) { ["entry_id"]=> string(2) "82" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(7) "NR_CPUS" ["value"]=> string(2) "16" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> string(29) "Maximum number of CPUs (2-64)" ["help_text"]=> NULL } [82]=> array(11) { ["entry_id"]=> string(2) "83" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Kernel support for ELF binaries" ["name"]=> string(10) "BINFMT_ELF" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1344) " ELF (Executable and Linkable Format) is a format for libraries and executables used across different architectures and operating systems. Saying Y here will enable your kernel to run ELF binaries and enlarge it by about 13 KB. ELF support under Linux has now all but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC) because it is portable (this does *not* mean that you will be able to run executables from different architectures or operating systems however) and makes building run-time libraries very easy. Many new executables are distributed solely in ELF format. You definitely want to say Y here. Information about ELF is contained in the ELF HOWTO available from . If you find that after upgrading from Linux kernel 1.2 and saying Y here, you still can't run any ELF binaries (they just crash), then you'll have to install the newest ELF runtime libraries, including ld.so (check the file for location and latest version). If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called binfmt_elf. Saying M or N here is dangerous because some crucial programs on your system might be in ELF format. " } [83]=> array(11) { ["entry_id"]=> string(2) "84" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Kernel support for flat binaries" ["name"]=> string(11) "BINFMT_FLAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(42) " Support uClinux FLAT format binaries. " } [84]=> array(11) { ["entry_id"]=> string(2) "85" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Enable ZFLAT support" ["name"]=> string(12) "BINFMT_ZFLAT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(44) " Support FLAT format compressed binaries " } [85]=> array(11) { ["entry_id"]=> string(2) "86" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Kernel support for a.out and ECOFF binaries" ["name"]=> string(11) "BINFMT_AOUT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(709) " A.out (Assembler.OUTput) is a set of formats for libraries and executables used in the earliest versions of UNIX. Linux used the a.out formats QMAGIC and ZMAGIC until they were replaced with the ELF format. The conversion to ELF started in 1995. This option is primarily provided for historical interest and for the benefit of those who need to run binaries from that era. Most people should answer N here. If you think you may have occasional use for this format, enable module support above and answer M here to compile this support as a module called binfmt_aout. If any crucial components of your system (such as /sbin/init or /lib/ld.so) are still in a.out format, you will have to say Y here. " } [86]=> array(11) { ["entry_id"]=> string(2) "87" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "OSF/1 v4 readv/writev compatibility" ["name"]=> string(11) "OSF4_COMPAT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(205) " Say Y if you are using OSF/1 binaries (like Netscape and Acrobat) with v4 shared libraries freely available from Compaq. If you're going to use shared libraries from Tru64 version 5.0 or later, say N. " } [87]=> array(11) { ["entry_id"]=> string(2) "88" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Kernel support for Linux/Intel ELF binaries" ["name"]=> string(11) "BINFMT_EM86" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(495) " Say Y here if you want to be able to execute Linux/Intel ELF binaries just like native Alpha binaries on your Alpha machine. For this to work, you need to have the emulator /usr/bin/em86 in place. You can get the same functionality by saying N here and saying Y to "Kernel support for MISC binaries". You may answer M to compile the emulation support as a module and later load the module when you want to use a Linux/Intel binary. The module will be called binfmt_em86. If unsure, say Y. " } [88]=> array(11) { ["entry_id"]=> string(2) "89" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Kernel support for SOM binaries" ["name"]=> string(10) "BINFMT_SOM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(126) " SOM is a binary executable format inherited from HP/UX. Say Y here to be able to load and execute SOM binaries directly. " } [89]=> array(11) { ["entry_id"]=> string(2) "90" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Kernel support for MISC binaries" ["name"]=> string(11) "BINFMT_MISC" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(973) " If you say Y here, it will be possible to plug wrapper-driven binary formats into the kernel. You will like this especially when you use programs that need an interpreter to run like Java, Python or Emacs-Lisp. It's also useful if you often run DOS executables under the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from ). Once you have registered such a binary class with the kernel, you can start one of those programs simply by typing in its name at a shell prompt; Linux will automatically feed it to the correct interpreter. You can do other nice things, too. Read the file to learn how to use this feature, and for information about how to include Java support. You may say M here for module support and later load the module when you have use for it; the module is called binfmt_misc. If you don't know what to answer at this point, say Y. " } [90]=> array(11) { ["entry_id"]=> string(2) "91" ["entry_type"]=> string(4) "MENU" ["text"]=> string(12) "ACPI Support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [91]=> array(11) { ["entry_id"]=> string(2) "92" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "ACPI Support" ["name"]=> string(4) "ACPI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1183) " Advanced Configuration and Power Interface (ACPI) support for Linux requires an ACPI compliant platform (hardware/firmware), and assumes the presence of OS-directed configuration and power management (OSPM) software. This option will enlarge your kernel by about 70K. Linux ACPI provides a robust functional replacement for several legacy configuration and power management intefaces, including the Plug-and-Play BIOS specification (PnP BIOS), the MultiProcessor Specification (MPS), and the Advanced Power Management (APM) specification. If both ACPI and APM support are configured, whichever is loaded first shall be used. The ACPI SourceForge project contains the latest source code, documentation, tools, mailing list subscription, and other information. This project is available at: Linux support for ACPI is based on Intel Corporation's ACPI Component Architecture (ACPI CA). For more information see: ACPI is an open industry specification co-developed by Compaq, Intel, Microsoft, Phoenix, and Toshiba. The specification is available at: " } [92]=> array(11) { ["entry_id"]=> string(2) "93" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "CPU Enumeration Only" ["name"]=> string(12) "ACPI_HT_ONLY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(561) " This option enables limited ACPI support -- just enough to enumerate processors from the ACPI Multiple APIC Description Table (MADT). Note that ACPI supports both logical (e.g. Hyper- Threading) and physical processors, where the MultiProcessor Specification (MPS) table only supports physical processors. Full ACPI support (CONFIG_ACPI) is preferred. Use this option only if you wish to limit ACPI's role to processor enumeration. In this configuration, ACPI defaults to off. It must be enabled on the command-line with the "acpismp=force" option. " } [93]=> array(11) { ["entry_id"]=> string(2) "94" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "ACPI_BOOT" ["name"]=> string(9) "ACPI_BOOT" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [94]=> array(11) { ["entry_id"]=> string(2) "95" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "Sleep States" ["name"]=> string(10) "ACPI_SLEEP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(615) " This option adds support for ACPI suspend states. With this option, you will be able to put the system "to sleep". Sleep states are low power states for the system and devices. All of the system operating state is saved to either memory or disk (depending on the state), to allow the system to resume operation quickly at your request. Although this option sounds really nifty, barely any of the device drivers have been converted to the new driver model and hence few have proper power management support. This option is not recommended for anyone except those doing driver power management development. " } [95]=> array(11) { ["entry_id"]=> string(2) "96" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "ACPI_SLEEP_PROC_FS" ["name"]=> string(18) "ACPI_SLEEP_PROC_FS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [96]=> array(11) { ["entry_id"]=> string(2) "97" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "AC Adapter" ["name"]=> string(7) "ACPI_AC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(191) " This driver adds support for the AC Adapter object, which indicates whether a system is on AC, or not. Typically, only mobile systems have this object, since desktops are always on AC. " } [97]=> array(11) { ["entry_id"]=> string(2) "98" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(7) "Battery" ["name"]=> string(12) "ACPI_BATTERY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(133) " This driver adds support for battery information through /proc/acpi/battery. If you have a mobile system with a battery, say Y. " } [98]=> array(11) { ["entry_id"]=> string(2) "99" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(6) "Button" ["name"]=> string(11) "ACPI_BUTTON" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(286) " This driver registers for events based on buttons, such as the power, sleep, and lid switch. In the future, a daemon will read /proc/acpi/event and perform user-defined actions such as shutting down the system. Until then, you can cat it, and see output when a button is pressed. " } [99]=> array(11) { ["entry_id"]=> string(3) "100" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(3) "Fan" ["name"]=> string(8) "ACPI_FAN" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(132) " This driver adds support for ACPI fan devices, allowing user-mode applications to perform basic fan control (on, off, status). " } [100]=> array(11) { ["entry_id"]=> string(3) "101" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "Processor" ["name"]=> string(14) "ACPI_PROCESSOR" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " This driver installs ACPI as the idle handler for Linux, and uses ACPI C2 and C3 processor states to save power, on systems that support it. " } [101]=> array(11) { ["entry_id"]=> string(3) "102" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "Thermal Zone" ["name"]=> string(12) "ACPI_THERMAL" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(222) " This driver adds support for ACPI thermal zones. Most mobile and some desktop systems support ACPI thermal zones. It is HIGHLY recommended that this option be enabled, as your processor(s) may be damaged without it. " } [102]=> array(11) { ["entry_id"]=> string(3) "103" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "NUMA support" ["name"]=> string(9) "ACPI_NUMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [103]=> array(11) { ["entry_id"]=> string(3) "104" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ASUS/Medion Laptop Extras" ["name"]=> string(9) "ACPI_ASUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1066) " This driver provides support for extra features of ACPI-compatible ASUS laptops. As some of Medion laptops are made by ASUS, it may also support some Medion laptops (such as 9675 for example). It makes all the extra buttons generate standard ACPI events that go through /proc/acpi/events, and (on some models) adds support for changing the display brightness and output, switching the LCD backlight on and off, and most importantly, allows you to blink those fancy LEDs intended for reporting mail and wireless status. All settings are changed via /proc/acpi/asus directory entries. Owner and group for these entries can be set with asus_uid and asus_gid parameters. More information and a userspace daemon for handling the extra buttons at . If you have an ACPI-compatible ASUS laptop, say Y or M here. This driver is still under development, so if your laptop is unsupported or something works not quite as expected, please use the mailing list available on the above page (acpi4asus-user@lists.sourceforge.net) " } [104]=> array(11) { ["entry_id"]=> string(3) "105" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Toshiba Laptop Extras" ["name"]=> string(12) "ACPI_TOSHIBA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(926) " This driver adds support for access to certain system settings on "legacy free" Toshiba laptops. These laptops can be recognized by their lack of a BIOS setup menu and APM support. On these machines, all system configuration is handled through the ACPI. This driver is required for access to controls not covered by the general ACPI drivers, such as LCD brightness, video output, etc. This driver differs from the non-ACPI Toshiba laptop driver (located under "Processor type and features") in several aspects. Configuration is accessed by reading and writing text files in the /proc tree instead of by program interface to /dev. Furthermore, no power management functions are exposed, as those are handled by the general ACPI drivers. More information about this driver is available at . If you have a legacy free Toshiba laptop (such as the Libretto L1 series), say Y. " } [105]=> array(11) { ["entry_id"]=> string(3) "106" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Debug Statements" ["name"]=> string(10) "ACPI_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(167) " The ACPI driver can optionally report errors with a great deal of verbosity. Saying Y enables these statements. This will increase your kernel size by around 50K. " } [106]=> array(11) { ["entry_id"]=> string(3) "107" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "ACPI_BUS" ["name"]=> string(8) "ACPI_BUS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [107]=> array(11) { ["entry_id"]=> string(3) "108" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "ACPI_INTERPRETER" ["name"]=> string(16) "ACPI_INTERPRETER" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [108]=> array(11) { ["entry_id"]=> string(3) "109" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(7) "ACPI_EC" ["name"]=> string(7) "ACPI_EC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(156) " This driver is required on some systems for the proper operation of the battery and thermal drivers. If you are compiling for a mobile system, say Y. " } [109]=> array(11) { ["entry_id"]=> string(3) "110" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "ACPI_POWER" ["name"]=> string(10) "ACPI_POWER" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [110]=> array(11) { ["entry_id"]=> string(3) "111" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "ACPI_PCI" ["name"]=> string(8) "ACPI_PCI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [111]=> array(11) { ["entry_id"]=> string(3) "112" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "ACPI_SYSTEM" ["name"]=> string(11) "ACPI_SYSTEM" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(118) " This driver will enable your system to shut down using ACPI, and dump your ACPI DSDT table using /proc/acpi/dsdt. " } [112]=> array(11) { ["entry_id"]=> string(3) "113" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "ACPI_EFI" ["name"]=> string(8) "ACPI_EFI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [113]=> array(11) { ["entry_id"]=> string(3) "114" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "PCI support" ["name"]=> string(3) "PCI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(409) " Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from , contains valuable information about which PCI hardware does work under Linux and which doesn't. " } [114]=> array(11) { ["entry_id"]=> string(3) "115" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "PCI_DOMAINS" ["name"]=> string(11) "PCI_DOMAINS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [115]=> array(11) { ["entry_id"]=> string(3) "116" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Legacy /proc/pci interface" ["name"]=> string(15) "PCI_LEGACY_PROC" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(495) " This feature enables a procfs file -- /proc/pci -- that provides a summary of PCI devices in the system. This feature has been deprecated as of v2.5.53, in favor of using the tool lspci(8). This feature may be removed at a future date. lspci can provide the same data, as well as much more. lspci is a part of the pci-utils package, which should be installed by your distribution. See Documentation/Changes for information on where to get the latest version. When in doubt, say N. " } [116]=> array(11) { ["entry_id"]=> string(3) "117" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "PCI device name database" ["name"]=> string(9) "PCI_NAMES" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(550) " By default, the kernel contains a database of all known PCI device names to make the information in /proc/pci, /proc/ioports and similar files comprehensible to the user. This database increases size of the kernel image by about 80KB. This memory is freed after the system boots up if CONFIG_HOTPLUG is not set. Anyway, if you are building an installation floppy or kernel for an embedded system where kernel image size really matters, you can disable this feature and you'll get device ID numbers instead of names. When in doubt, say Y. " } [117]=> array(11) { ["entry_id"]=> string(3) "118" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Support for hot-pluggable devices" ["name"]=> string(7) "HOTPLUG" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(763) " Say Y here if you want to plug devices into your computer while the system is running, and be able to use them quickly. In many cases, the devices can likewise be unplugged at any time too. One well known example of this is PCMCIA- or PC-cards, credit-card size devices such as network cards, modems or hard drives which are plugged into slots found on all modern laptop computers. Another example, used on modern desktops as well as laptops, is USB. Enable HOTPLUG and KMOD, and build a modular kernel. Get agent software (at ) and install it. Then your kernel will automatically call out to a user mode "policy agent" (/sbin/hotplug) to load modules and set up software needed to use devices as you hotplug them. " } [118]=> array(11) { ["entry_id"]=> string(3) "119" ["entry_type"]=> string(4) "MENU" ["text"]=> string(19) "PCI Hotplug Support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [119]=> array(11) { ["entry_id"]=> string(3) "120" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Support for PCI Hotplug (EXPERIMENTAL)" ["name"]=> string(11) "HOTPLUG_PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(543) " Say Y here if you have a motherboard with a PCI Hotplug controller. This allows you to add and remove PCI cards while the machine is powered up and running. The file system pcihpfs must be mounted in order to interact with any PCI Hotplug controllers. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called pci_hotplug. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [120]=> array(11) { ["entry_id"]=> string(3) "121" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Fake PCI Hotplug driver" ["name"]=> string(16) "HOTPLUG_PCI_FAKE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(812) " Say Y here if you want to use the fake PCI hotplug driver. It can be used to simulate PCI hotplug events if even if your system is not PCI hotplug capable. This driver will "emulate" removing PCI devices from the system. If the "power" file is written to with "0" then the specified PCI device will be completely removed from the kernel. WARNING, this does NOT turn off the power to the PCI device. This is a "logical" removal, not a physical or electrical removal. Use this module at your own risk. You have been warned! This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fakephp. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [121]=> array(11) { ["entry_id"]=> string(3) "122" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Compaq PCI Hotplug driver" ["name"]=> string(18) "HOTPLUG_PCI_COMPAQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(360) " Say Y here if you have a motherboard with a Compaq PCI Hotplug controller. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cpqphp. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [122]=> array(11) { ["entry_id"]=> string(3) "123" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Save configuration into NVRAM on Compaq servers" ["name"]=> string(24) "HOTPLUG_PCI_COMPAQ_NVRAM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(197) " Say Y here if you have a Compaq server that has a PCI Hotplug controller. This will allow the PCI Hotplug driver to store the PCI system configuration options in NVRAM. When in doubt, say N. " } [123]=> array(11) { ["entry_id"]=> string(3) "124" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "IBM PCI Hotplug driver" ["name"]=> string(15) "HOTPLUG_PCI_IBM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(357) " Say Y here if you have a motherboard with a IBM PCI Hotplug controller. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cpqphp. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [124]=> array(11) { ["entry_id"]=> string(3) "125" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "ACPI PCI Hotplug driver" ["name"]=> string(16) "HOTPLUG_PCI_ACPI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(356) " Say Y here if you have a system that supports PCI Hotplug using ACPI. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called acpiphp. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [125]=> array(11) { ["entry_id"]=> string(3) "126" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "CompactPCI Hotplug driver" ["name"]=> string(16) "HOTPLUG_PCI_CPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(140) " Say Y here if you have a CompactPCI system card with CompactPCI hotswap support per the PICMG 2.1 specification. When in doubt, say N. " } [126]=> array(11) { ["entry_id"]=> string(3) "127" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Ziatech ZT5550 CompactPCI Hotplug driver" ["name"]=> string(23) "HOTPLUG_PCI_CPCI_ZT5550" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(422) " Say Y here if you have an Performance Technologies (formerly Intel, formerly just Ziatech) Ziatech ZT5550 CompactPCI system card. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cpcihp_zt5550. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [127]=> array(11) { ["entry_id"]=> string(3) "128" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Generic port I/O CompactPCI Hotplug driver" ["name"]=> string(24) "HOTPLUG_PCI_CPCI_GENERIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(453) " Say Y here if you have a CompactPCI system card that exposes the #ENUM hotswap signal as a bit in a system register that can be read through standard port I/O. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cpcihp_generic. If you want to compile it as a module, say M here and read . When in doubt, say N. " } [128]=> array(11) { ["entry_id"]=> string(3) "129" ["entry_type"]=> string(4) "MENU" ["text"]=> string(22) "PCMCIA/CardBus support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [129]=> array(11) { ["entry_id"]=> string(3) "130" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "PCMCIA/CardBus support" ["name"]=> string(6) "PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(949) " Say Y here if you want to attach PCMCIA- or PC-cards to your Linux computer. These are credit-card size devices such as network cards, modems or hard drives often used with laptops computers. There are actually two varieties of these cards: the older 16 bit PCMCIA cards and the newer 32 bit CardBus cards. If you want to use CardBus cards, you need to say Y here and also to "CardBus support" below. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). Please also read the PCMCIA-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). When compiled this way, there will be modules called pcmcia_core and ds. If you want to compile it as a module, say M here and read . " } [130]=> array(11) { ["entry_id"]=> string(3) "131" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "CardBus yenta-compatible bridge support" ["name"]=> string(5) "YENTA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(616) " CardBus is a bus mastering architecture for PC-cards, which allows for 32 bit PC-cards (the original PCMCIA standard specifies only a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. This option enables support for CardBus PC Cards, as well as support for CardBus host bridges. Virtually all modern PCMCIA bridges are CardBus compatible. A "bridge" is the hardware inside your computer that PCMCIA cards are plugged into. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). If unsure, say Y. " } [131]=> array(11) { ["entry_id"]=> string(3) "132" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(7) "CARDBUS" ["name"]=> string(7) "CARDBUS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [132]=> array(11) { ["entry_id"]=> string(3) "133" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "i82092 compatible bridge support" ["name"]=> string(6) "I82092" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(159) " This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device, found in some older laptops and more commonly in evaluation boards for the chip. " } [133]=> array(11) { ["entry_id"]=> string(3) "134" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "i82365 compatible bridge support" ["name"]=> string(6) "I82365" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(301) " Say Y here to include support for ISA-bus PCMCIA host bridges that are register compatible with the Intel i82365. These are found on older laptops and ISA-bus card readers for desktop systems. A "bridge" is the hardware inside your computer that PCMCIA cards are plugged into. If unsure, say N. " } [134]=> array(11) { ["entry_id"]=> string(3) "135" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Databook TCIC host bridge support" ["name"]=> string(4) "TCIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(255) " Say Y here to include support for the Databook TCIC family of PCMCIA host bridges. These are only found on a handful of old systems. "Bridge" is the name used for the hardware inside your computer that PCMCIA cards are plugged into. If unsure, say N. " } [135]=> array(11) { ["entry_id"]=> string(3) "136" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "HD64465 host bridge support" ["name"]=> string(14) "HD64465_PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [136]=> array(11) { ["entry_id"]=> string(3) "137" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "SA1100 support" ["name"]=> string(13) "PCMCIA_SA1100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(212) " Say Y here to include support for SA11x0-based PCMCIA or CF sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/ Xscale(R) embedded machines. This driver is also available as a module called sa1100_cs. " } [137]=> array(11) { ["entry_id"]=> string(3) "138" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "SA1111 support" ["name"]=> string(13) "PCMCIA_SA1111" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(228) " Say Y here to include support for SA1111-based PCMCIA or CF sockets, found on the Jornada 720, Graphicsmaster and other StrongARM(R)/Xscale(R) embedded machines. This driver is also available as a module called sa1111_cs. " } [138]=> array(11) { ["entry_id"]=> string(3) "139" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "PCMCIA_PROBE" ["name"]=> string(12) "PCMCIA_PROBE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [139]=> array(11) { ["entry_id"]=> string(3) "140" ["entry_type"]=> string(4) "MENU" ["text"]=> string(21) "Parallel port support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [140]=> array(11) { ["entry_id"]=> string(3) "141" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Parallel port support" ["name"]=> string(7) "PARPORT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1124) " If you want to use devices connected to your machine's parallel port (the connector at the computer with 25 holes), e.g. printer, ZIP drive, PLIP link (Parallel Line Internet Protocol is mainly used to create a mini network by connecting the parallel ports of two local machines) etc., then you need to say Y here; please read and . For extensive information about drivers for many devices attaching to the parallel port see on the WWW. It is possible to share a single parallel port among several devices and it is safe to compile all the corresponding drivers into the kernel. If you want to compile parallel port support as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called parport. If you have more than one parallel port and want to specify which port and IRQ to be used by this driver at module load time, take a look at . If unsure, say Y. " } [141]=> array(11) { ["entry_id"]=> string(3) "142" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "PC-style hardware" ["name"]=> string(10) "PARPORT_PC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(502) " You should say Y here if you have a PC-style parallel port. All IBM PC compatible computers and some Alphas have PC-style parallel ports. PA-RISC owners should only say Y here if they have a SuperIO parallel port. This code is also available as a module. If you want to compile it as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called parport_pc. If unsure, say Y. " } [142]=> array(11) { ["entry_id"]=> string(3) "143" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "PARPORT_PC_CML1" ["name"]=> string(15) "PARPORT_PC_CML1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [143]=> array(11) { ["entry_id"]=> string(3) "144" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Multi-IO cards (parallel and serial)" ["name"]=> string(14) "PARPORT_SERIAL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(168) " This adds support for multi-IO PCI cards that have parallel and serial ports. You should say Y or M here. If you say M, the module will be called parport_serial. " } [144]=> array(11) { ["entry_id"]=> string(3) "145" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Use FIFO/DMA if available (EXPERIMENTAL)" ["name"]=> string(15) "PARPORT_PC_FIFO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(417) " Many parallel port chipsets provide hardware that can speed up printing. Say Y here if you want to take advantage of that. As well as actually having a FIFO, or DMA capability, the kernel will need to know which IRQ the parallel port has. By default, parallel port interrupts will not be used, and so neither will the FIFO. See to find out how to specify which IRQ/DMA to use. " } [145]=> array(11) { ["entry_id"]=> string(3) "146" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "SuperIO chipset support (EXPERIMENTAL)" ["name"]=> string(18) "PARPORT_PC_SUPERIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(159) " Saying Y here enables some probes for Super-IO chipsets in order to find out things like base addresses, IRQ lines and DMA channels. It is safe to say N. " } [146]=> array(11) { ["entry_id"]=> string(3) "147" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Support for PCMCIA management for PC-style ports" ["name"]=> string(17) "PARPORT_PC_PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(94) " Say Y here if you need PCMCIA support for your PC-style parallel ports. If unsure, say N. " } [147]=> array(11) { ["entry_id"]=> string(3) "148" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Archimedes hardware" ["name"]=> string(11) "PARPORT_ARC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [148]=> array(11) { ["entry_id"]=> string(3) "149" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Amiga builtin port" ["name"]=> string(13) "PARPORT_AMIGA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(196) " Say Y here if you need support for the parallel port hardware on Amiga machines. This code is also available as a module (say M), called parport_amiga. If in doubt, saying N is the safe plan. " } [149]=> array(11) { ["entry_id"]=> string(3) "150" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Multiface III parallel port" ["name"]=> string(12) "PARPORT_MFC3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(178) " Say Y here if you need parallel port support for the MFC3 card. This code is also available as a module (say M), called parport_mfc3. If in doubt, saying N is the safe plan. " } [150]=> array(11) { ["entry_id"]=> string(3) "151" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "Atari hardware" ["name"]=> string(13) "PARPORT_ATARI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(196) " Say Y here if you need support for the parallel port hardware on Atari machines. This code is also available as a module (say M), called parport_atari. If in doubt, saying N is the safe plan. " } [151]=> array(11) { ["entry_id"]=> string(3) "152" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "PARPORT_GSC" ["name"]=> string(11) "PARPORT_GSC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [152]=> array(11) { ["entry_id"]=> string(3) "153" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Sparc hardware (EXPERIMENTAL)" ["name"]=> string(14) "PARPORT_SUNBPP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(173) " This driver provides support for the bidirectional parallel port found on many Sun machines. Note that many of the newer Ultras actually have pc style hardware instead. " } [153]=> array(11) { ["entry_id"]=> string(3) "154" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Support foreign hardware" ["name"]=> string(13) "PARPORT_OTHER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(170) " Say Y here if you want to be able to load driver modules to support other non-standard types of parallel ports. This causes a performance loss, so most people say N. " } [154]=> array(11) { ["entry_id"]=> string(3) "155" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "IEEE 1284 transfer modes" ["name"]=> string(12) "PARPORT_1284" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(334) " If you have a printer that supports status readback or device ID, or want to use a device that uses enhanced parallel port transfer modes such as EPP and ECP, say Y here to enable advanced IEEE 1284 transfer modes. Also say Y if you want device ID information to appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N. " } [155]=> array(11) { ["entry_id"]=> string(3) "156" ["entry_type"]=> string(4) "MENU" ["text"]=> string(22) "Generic Driver Options" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [156]=> array(11) { ["entry_id"]=> string(3) "157" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Hotplug firmware loading support" ["name"]=> string(9) "FW_LOADER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(164) " This option is provided for the case where no in-kernel-tree modules require hotplug firmware loading support, but a module built outside the kernel tree does. " } [157]=> array(11) { ["entry_id"]=> string(3) "158" ["entry_type"]=> string(4) "MENU" ["text"]=> string(31) "Memory Technology Devices (MTD)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [158]=> array(11) { ["entry_id"]=> string(3) "159" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Memory Technology Device (MTD) support" ["name"]=> string(3) "MTD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(457) " Memory Technology Devices are flash, RAM and similar chips, often used for solid state file systems on embedded devices. This option will provide the generic support for MTD drivers to register themselves with the kernel and for potential users of MTD devices to enumerate the devices which are present and obtain a handle on them. It will also allow you to select individual drivers for particular hardware and users of MTD devices. If unsure, say N. " } [159]=> array(11) { ["entry_id"]=> string(3) "160" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "Debugging" ["name"]=> string(9) "MTD_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(99) " This turns on low-level debugging for the entire MTD sub-system. Normally, you should say 'N'. " } [160]=> array(11) { ["entry_id"]=> string(3) "161" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(17) "MTD_DEBUG_VERBOSE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> string(42) "Debugging verbosity (0 = quiet, 3 = noisy)" ["help_text"]=> NULL } [161]=> array(11) { ["entry_id"]=> string(3) "162" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "MTD partitioning support" ["name"]=> string(14) "MTD_PARTITIONS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(404) " If you have a device which needs to divide its flash chip(s) up into multiple 'partitions', each of which appears to the user as a separate MTD device, you require this option to be enabled. If unsure, say 'Y'. Note, however, that you don't need this option for the DiskOnChip devices. Partitioning on NFTL 'devices' is a different - that's the 'normal' form of partitioning used on a block device. " } [162]=> array(11) { ["entry_id"]=> string(3) "163" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "MTD concatenating support" ["name"]=> string(10) "MTD_CONCAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(199) " Support for concatenating several MTD devices into a single (virtual) one. This allows you to have -for example- a JFFS(2) file system spanning multiple physical flash chips. If unsure, say 'Y'. " } [163]=> array(11) { ["entry_id"]=> string(3) "164" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "RedBoot partition table parsing" ["name"]=> string(17) "MTD_REDBOOT_PARTS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(626) " RedBoot is a ROM monitor and bootloader which deals with multiple 'images' in flash devices by putting a table in the last erase block of the device, similar to a partition table, which gives the offsets, lengths and names of all the images stored in the flash. If you need code which can detect and parse this table, and register MTD 'partitions' corresponding to each image in the table, enable this option. You will still need the parsing functions to be called by the driver for your particular device. It won't happen automatically. The SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for example. " } [164]=> array(11) { ["entry_id"]=> string(3) "165" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Command line partition table parsing" ["name"]=> string(17) "MTD_CMDLINE_PARTS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1085) " Allow generic configuration of the MTD paritition tables via the kernel command line. Multiple flash resources are supported for hardware where different kinds of flash memory are available. You will still need the parsing functions to be called by the driver for your particular device. It won't happen automatically. The SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for example. The format for the command line is as follows: mtdparts=[; := :[,] := [@offset][][ro] := unique id used in mapping driver/device := standard linux memsize OR "-" to denote all remaining space := (NAME) Due to the way Linux handles the command line, no spaces are allowed in the partition definition, including mtd id's and partition names. Examples: 1 flash resource (mtd-id "sa1100"), with 1 single writable partition: mtdparts=sa1100:- Same flash, but 2 named partitions, the first one being read-only: mtdparts=sa1100:256k(ARMboot)ro,-(root) If unsure, say 'N'. " } [165]=> array(11) { ["entry_id"]=> string(3) "166" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "ARM Firmware Suite partition parsing" ["name"]=> string(13) "MTD_AFS_PARTS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(509) " The ARM Firmware Suite allows the user to divide flash devices into multiple 'images'. Each such image has a header containing its name and offset/size etc. If you need code which can detect and parse these tables, and register MTD 'partitions' corresponding to each image detected, enable this option. You will still need the parsing functions to be called by the driver for your particular device. It won't happen automatically. The 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example. " } [166]=> array(11) { ["entry_id"]=> string(3) "167" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Direct char device access to MTD devices" ["name"]=> string(8) "MTD_CHAR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(232) " This provides a character device for each MTD device present in the system, allowing the user to read and write directly to the memory chips, and also use ioctl() to obtain information about the device, or to erase parts of it. " } [167]=> array(11) { ["entry_id"]=> string(3) "168" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Caching block device access to MTD devices" ["name"]=> string(9) "MTD_BLOCK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(811) " Although most flash chips have an erase size too large to be useful as block devices, it is possible to use MTD devices which are based on RAM chips in this manner. This block device is a user of MTD devices performing that function. At the moment, it is also required for the Journalling Flash File System(s) to obtain a handle on the MTD device when it's mounted (although JFFS and JFFS2 don't actually use any of the functionality of the mtdblock device). Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, this is very unsafe, but could be useful for file systems which are almost never written to. You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (CONFIG_NFTL) instead. " } [168]=> array(11) { ["entry_id"]=> string(3) "169" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Readonly block device access to MTD devices" ["name"]=> string(12) "MTD_BLOCK_RO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(266) " This allows you to mount read-only file systems (such as cramfs) from an MTD device, without the overhead (and danger) of the caching driver. You do not need this option for use with the DiskOnChip devices. For those, enable NFTL support (CONFIG_NFTL) instead. " } [169]=> array(11) { ["entry_id"]=> string(3) "170" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "FTL (Flash Translation Layer) support" ["name"]=> string(3) "FTL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(599) " This provides support for the original Flash Translation Layer which is part of the PCMCIA specification. It uses a kind of pseudo- file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on PCMCIA hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. " } [170]=> array(11) { ["entry_id"]=> string(3) "171" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "NFTL (NAND Flash Translation Layer) support" ["name"]=> string(4) "NFTL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(604) " This provides support for the NAND Flash Translation Layer which is used on M-Systems' DiskOnChip devices. It uses a kind of pseudo- file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on DiskOnChip hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. " } [171]=> array(11) { ["entry_id"]=> string(3) "172" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Write support for NFTL" ["name"]=> string(7) "NFTL_RW" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(88) " Support for writing to the NAND Flash Translation Layer, as used on the DiskOnChip. " } [172]=> array(11) { ["entry_id"]=> string(3) "173" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(52) "INFTL (Inverse NAND Flash Translation Layer) support" ["name"]=> string(5) "INFTL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(618) " This provides support for the Inverse NAND Flash Translation Layer which is used on M-Systems' newer DiskOnChip devices. It uses a kind of pseudo-file system on a flash device to emulate a block device with 512-byte sectors, on top of which you put a 'normal' file system. You may find that the algorithms used in this code are patented unless you live in the Free World where software patents aren't legal - in the USA you are only permitted to use this on DiskOnChip hardware, although under the terms of the GPL you're obviously permitted to copy, modify and distribute the code as you wish. Just not use it. " } [173]=> array(11) { ["entry_id"]=> string(3) "174" ["entry_type"]=> string(4) "MENU" ["text"]=> string(26) "RAM/ROM/Flash chip drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [174]=> array(11) { ["entry_id"]=> string(3) "175" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(56) "Detect flash chips by Common Flash Interface (CFI) probe" ["name"]=> string(7) "MTD_CFI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(358) " The Common Flash Interface specification was developed by Intel, AMD and other flash manufactures that provides a universal method for probing the capabilities of flash devices. If you wish to support any device that is CFI-compliant, you need to enable this option. Visit for more information on CFI. " } [175]=> array(11) { ["entry_id"]=> string(3) "176" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Detect non-CFI AMD/JEDEC-compatible flash chips" ["name"]=> string(14) "MTD_JEDECPROBE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(448) " This option enables JEDEC-style probing of flash chips which are not compatible with the Common Flash Interface, but will use the common CFI-targetted flash drivers for any chips which are identified which are in fact compatible in all but the probe method. This actually covers most AMD/Fujitsu-compatible chips, and will shortly cover also non-CFI Intel chips (that code is in MTD CVS and should shortly be sent for inclusion in Linus' tree) " } [176]=> array(11) { ["entry_id"]=> string(3) "177" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "MTD_GEN_PROBE" ["name"]=> string(13) "MTD_GEN_PROBE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [177]=> array(11) { ["entry_id"]=> string(3) "178" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Flash chip driver advanced configuration options" ["name"]=> string(19) "MTD_CFI_ADV_OPTIONS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(340) " If you need to specify a specific endianness for access to flash chips, or if you wish to reduce the size of the kernel by including support for only specific arrangements of flash chips, say 'Y'. This option does not directly affect the code, but will enable other configuration options which allow you to do so. If unsure, say 'N'. " } [178]=> array(11) { ["entry_id"]=> string(3) "179" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "MTD_CFI_NOSWAP" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(2) "NO" ["help_text"]=> NULL } [179]=> array(11) { ["entry_id"]=> string(3) "180" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(20) "MTD_CFI_BE_BYTE_SWAP" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(15) "BIG_ENDIAN_BYTE" ["help_text"]=> NULL } [180]=> array(11) { ["entry_id"]=> string(3) "181" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(20) "MTD_CFI_LE_BYTE_SWAP" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(18) "LITTLE_ENDIAN_BYTE" ["help_text"]=> NULL } [181]=> array(11) { ["entry_id"]=> string(3) "182" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Specific CFI Flash geometry selection" ["name"]=> string(16) "MTD_CFI_GEOMETRY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(315) " This option does not affect the code directly, but will enable some other configuration options which would allow you to reduce the size of the kernel by including support for only certain arrangements of CFI chips. If unsure, say 'N' and all options which are supported by the current code will be enabled. " } [182]=> array(11) { ["entry_id"]=> string(3) "183" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support 8-bit buswidth" ["name"]=> string(10) "MTD_CFI_B1" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(88) " If you wish to support CFI devices on a physical bus which is 8 bits wide, say 'Y'. " } [183]=> array(11) { ["entry_id"]=> string(3) "184" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support 16-bit buswidth" ["name"]=> string(10) "MTD_CFI_B2" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(89) " If you wish to support CFI devices on a physical bus which is 16 bits wide, say 'Y'. " } [184]=> array(11) { ["entry_id"]=> string(3) "185" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support 32-bit buswidth" ["name"]=> string(10) "MTD_CFI_B4" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(89) " If you wish to support CFI devices on a physical bus which is 32 bits wide, say 'Y'. " } [185]=> array(11) { ["entry_id"]=> string(3) "186" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support 64-bit buswidth" ["name"]=> string(10) "MTD_CFI_B8" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(89) " If you wish to support CFI devices on a physical bus which is 64 bits wide, say 'Y'. " } [186]=> array(11) { ["entry_id"]=> string(3) "187" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support 1-chip flash interleave" ["name"]=> string(10) "MTD_CFI_I1" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(123) " If your flash chips are not interleaved - i.e. you only have one flash chip addressed by each bus cycle, then say 'Y'. " } [187]=> array(11) { ["entry_id"]=> string(3) "188" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support 2-chip flash interleave" ["name"]=> string(10) "MTD_CFI_I2" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(124) " If your flash chips are interleaved in pairs - i.e. you have two flash chips addressed by each bus cycle, then say 'Y'. " } [188]=> array(11) { ["entry_id"]=> string(3) "189" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support 4-chip flash interleave" ["name"]=> string(10) "MTD_CFI_I4" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(125) " If your flash chips are interleaved in fours - i.e. you have four flash chips addressed by each bus cycle, then say 'Y'. " } [189]=> array(11) { ["entry_id"]=> string(3) "190" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support 8-chip flash interleave" ["name"]=> string(10) "MTD_CFI_I8" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(127) " If your flash chips are interleaved in eights - i.e. you have eight flash chips addressed by each bus cycle, then say 'Y'. " } [190]=> array(11) { ["entry_id"]=> string(3) "191" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Support for Intel/Sharp flash chips" ["name"]=> string(16) "MTD_CFI_INTELEXT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(226) " The Common Flash Interface defines a number of different command sets which a CFI-compliant chip may claim to implement. This code provides support for one of those command sets, used on Intel StrataFlash and other parts. " } [191]=> array(11) { ["entry_id"]=> string(3) "192" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Support for AMD/Fujitsu flash chips" ["name"]=> string(14) "MTD_CFI_AMDSTD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(227) " The Common Flash Interface defines a number of different command sets which a CFI-compliant chip may claim to implement. This code provides support for one of those command sets, used on chips including the AMD Am29LV320. " } [192]=> array(11) { ["entry_id"]=> string(3) "193" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(50) "Support for ST (Advanced Architecture) flash chips" ["name"]=> string(12) "MTD_CFI_STAA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(183) " The Common Flash Interface defines a number of different command sets which a CFI-compliant chip may claim to implement. This code provides support for one of those command sets. " } [193]=> array(11) { ["entry_id"]=> string(3) "194" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Support for RAM chips in bus mapping" ["name"]=> string(7) "MTD_RAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(92) " This option enables basic support for RAM chips accessed through a bus mapping driver. " } [194]=> array(11) { ["entry_id"]=> string(3) "195" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Support for ROM chips in bus mapping" ["name"]=> string(7) "MTD_ROM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(92) " This option enables basic support for ROM chips accessed through a bus mapping driver. " } [195]=> array(11) { ["entry_id"]=> string(3) "196" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Support for absent chips in bus mapping" ["name"]=> string(10) "MTD_ABSENT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(374) " This option enables support for a dummy probing driver used to allocated placeholder MTD devices on systems that have socketed or removable media. Use of this driver as a fallback chip probe preserves the expected registration order of MTD device nodes on the system regardless of media presence. Device nodes created with this driver will return -ENODEV upon access. " } [196]=> array(11) { ["entry_id"]=> string(3) "197" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(61) "Older (theoretically obsoleted now) drivers for non-CFI chips" ["name"]=> string(18) "MTD_OBSOLETE_CHIPS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(475) " This option does not enable any code directly, but will allow you to select some other chip drivers which are now considered obsolete, because the generic CONFIG_JEDECPROBE code above should now detect the chips which are supported by these drivers, and allow the generic CFI-compatible drivers to drive the chips. Say 'N' here unless you have already tried the CONFIG_JEDECPROBE method and reported its failure to the MTD mailing list at " } [197]=> array(11) { ["entry_id"]=> string(3) "198" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "AMD compatible flash chip support (non-CFI)" ["name"]=> string(10) "MTD_AMDSTD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(251) " This option enables support for flash chips using AMD-compatible commands, including some which are not CFI-compatible and hence cannot be used with the CONFIG_MTD_CFI_AMDSTD option. It also works on AMD compatible chips that do conform to CFI. " } [198]=> array(11) { ["entry_id"]=> string(3) "199" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "pre-CFI Sharp chip support" ["name"]=> string(9) "MTD_SHARP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(193) " This option enables support for flash chips using Sharp-compatible commands, including some which are not CFI-compatible and hence cannot be used with the CONFIG_MTD_CFI_INTELxxx options. " } [199]=> array(11) { ["entry_id"]=> string(3) "200" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "JEDEC device support" ["name"]=> string(9) "MTD_JEDEC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(253) " Enable older older JEDEC flash interface devices for self programming flash. It is commonly used in older AMD chips. It is only called JEDEC because the JEDEC association distributes the identification codes for the chips. " } [200]=> array(11) { ["entry_id"]=> string(3) "201" ["entry_type"]=> string(4) "MENU" ["text"]=> string(31) "Mapping drivers for chip access" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [201]=> array(11) { ["entry_id"]=> string(3) "202" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Support non-linear mappings of flash chips" ["name"]=> string(20) "MTD_COMPLEX_MAPPINGS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(89) " This causes the chip drivers to allow for complicated paged mappings of flash chips. " } [202]=> array(11) { ["entry_id"]=> string(3) "203" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "CFI Flash device in physical memory map" ["name"]=> string(11) "MTD_PHYSMAP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(302) " This provides a 'mapping' driver which allows the CFI probe and command set driver code to communicate with flash chips which are mapped physically into the CPU's memory. You will need to configure the physical address and size of the flash chips on your particular board as well as the bus width. " } [203]=> array(11) { ["entry_id"]=> string(3) "204" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(17) "MTD_PHYSMAP_START" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(39) "Physical start address of flash mapping" ["help_text"]=> NULL } [204]=> array(11) { ["entry_id"]=> string(3) "205" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(15) "MTD_PHYSMAP_LEN" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(32) "Physical length of flash mapping" ["help_text"]=> NULL } [205]=> array(11) { ["entry_id"]=> string(3) "206" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(20) "MTD_PHYSMAP_BUSWIDTH" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(19) "Bus width in octets" ["help_text"]=> NULL } [206]=> array(11) { ["entry_id"]=> string(3) "207" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Sun Microsystems userflash support" ["name"]=> string(14) "MTD_SUN_UFLASH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(262) " This provides a 'mapping' driver which supports the way in which user-programmable flash chips are connected on various Sun Microsystems boardsets. This driver will require CFI support in the kernel, so if you did not enable CFI previously, do that now. " } [207]=> array(11) { ["entry_id"]=> string(3) "208" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "CFI Flash device mapped on Photron PNC-2000" ["name"]=> string(11) "MTD_PNC2000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(108) " PNC-2000 is the name of Network Camera product from PHOTRON Ltd. in Japan. It uses CFI-compliant flash. " } [208]=> array(11) { ["entry_id"]=> string(3) "209" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "CFI Flash device mapped on AMD SC520 CDP" ["name"]=> string(12) "MTD_SC520CDP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(175) " The SC520 CDP board has two banks of CFI-compliant chips and one Dual-in-line JEDEC chip. This 'mapping' driver supports that arrangement, implementing three MTD devices. " } [209]=> array(11) { ["entry_id"]=> string(3) "210" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "CFI Flash device mapped on AMD NetSc520" ["name"]=> string(12) "MTD_NETSC520" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(181) " This enables access routines for the flash chips on the AMD NetSc520 demonstration board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [210]=> array(11) { ["entry_id"]=> string(3) "211" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "CFI Flash device mapped on Arcom SBC-GXx boards" ["name"]=> string(11) "MTD_SBC_GXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(340) " This provides a driver for the on-board flash of Arcom Control Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. By default the flash is split into 3 partitions which are accessed as separate MTD devices. This board utilizes Intel StrataFlash. More info at . " } [211]=> array(11) { ["entry_id"]=> string(3) "212" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "CFI Flash device mapped on Arcom ELAN-104NC" ["name"]=> string(14) "MTD_ELAN_104NC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(317) " This provides a driver for the on-board flash of the Arcom Control System's ELAN-104NC development board. By default the flash is split into 3 partitions which are accessed as separate MTD devices. This board utilizes Intel StrataFlash. More info at . " } [212]=> array(11) { ["entry_id"]=> string(3) "213" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "CFI Flash device mapped on Intel Lubbock XScale eval board" ["name"]=> string(11) "MTD_LUBBOCK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(98) " This provides a driver for the on-board flash of the Intel 'Lubbock' XScale evaluation board. " } [213]=> array(11) { ["entry_id"]=> string(3) "214" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "JEDEC Flash device mapped on Octagon 5066 SBC" ["name"]=> string(11) "MTD_OCTAGON" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(245) " This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Octagon-5066 Single Board Computer. More information on the board is available at . " } [214]=> array(11) { ["entry_id"]=> string(3) "215" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "JEDEC Flash device mapped on Tempustech VMAX SBC301" ["name"]=> string(8) "MTD_VMAX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(237) " This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Tempustech VMAX SBC301 Single Board Computer. More information on the board is available at . " } [215]=> array(11) { ["entry_id"]=> string(3) "216" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Flash device mapped with DOCCS on NatSemi SCx200" ["name"]=> string(19) "MTD_SCx200_DOCFLASH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(216) " Enable support for a flash chip mapped using the DOCCS signal on a National Semiconductor SCx200 processor. If you don't know what to do here, say N. If compiled as a module, it will be called scx200_docflash. " } [216]=> array(11) { ["entry_id"]=> string(3) "217" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "BIOS flash chip on AMD76x southbridge" ["name"]=> string(13) "MTD_AMD76XROM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(144) " Support for treating the BIOS flash chip on AMD76x motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. " } [217]=> array(11) { ["entry_id"]=> string(3) "218" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "BIOS flash chip on Intel Hub Controller 2" ["name"]=> string(11) "MTD_ICH2ROM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(142) " Support for treating the BIOS flash chip on ICH2 motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. " } [218]=> array(11) { ["entry_id"]=> string(3) "219" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "BIOS flash chip on Intel SCB2 boards" ["name"]=> string(14) "MTD_SCB2_FLASH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(142) " Support for treating the BIOS flash chip on Intel SCB2 boards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. " } [219]=> array(11) { ["entry_id"]=> string(3) "220" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Flash chips on Tsunami TIG bus" ["name"]=> string(11) "MTD_TSUNAMI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(51) " Support for the flash chip on Tsunami TIG bus. " } [220]=> array(11) { ["entry_id"]=> string(3) "221" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Flash chips on LASAT board" ["name"]=> string(9) "MTD_LASAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(65) " Support for the flash chips on the Lasat 100 and 200 boards. " } [221]=> array(11) { ["entry_id"]=> string(3) "222" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "CFI flash device on SnapGear/SecureEdge" ["name"]=> string(10) "MTD_NETtel" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(66) " Support for flash chips on NETtel/SecureEdge/SnapGear boards. " } [222]=> array(11) { ["entry_id"]=> string(3) "223" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Flash devices on Alchemy PB1xxx boards" ["name"]=> string(10) "MTD_PB1XXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(63) " Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards " } [223]=> array(11) { ["entry_id"]=> string(3) "224" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "PB1x00 boot flash device" ["name"]=> string(15) "MTD_PB1XXX_BOOT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(148) " Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board. You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use both banks. " } [224]=> array(11) { ["entry_id"]=> string(3) "225" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "PB1x00 user flash device" ["name"]=> string(15) "MTD_PB1XXX_USER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(149) " Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board. You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use both banks. " } [225]=> array(11) { ["entry_id"]=> string(3) "226" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "CFI Flash device mapped on DIL/Net PC" ["name"]=> string(12) "MTD_DILNETPC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(176) " MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". For details, see http://www.ssv-embedded.de/ssv/pc104/p169.htm and http://www.ssv-embedded.de/ssv/pc104/p170.htm " } [226]=> array(11) { ["entry_id"]=> string(3) "227" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(21) "MTD_DILNETPC_BOOTSIZE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(39) "Size of DIL/Net PC flash boot partition" ["help_text"]=> NULL } [227]=> array(11) { ["entry_id"]=> string(3) "228" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "BIOS flash chip on Intel L440GX boards" ["name"]=> string(10) "MTD_L440GX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(150) " Support for treating the BIOS flash chip on Intel L440GX motherboards as an MTD device - with this you can reprogram your BIOS. BE VERY CAREFUL. " } [228]=> array(11) { ["entry_id"]=> string(3) "229" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "CFI Flash device mapped on TQM8XXL" ["name"]=> string(11) "MTD_TQM8XXL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(301) " The TQM8xxL PowerPC board has up to two banks of CFI-compliant chips, currently uses AMD one. This 'mapping' driver supports that arrangement, allowing the CFI probe and command set driver code to communicate with the chips on the TQM8xxL board. More at . " } [229]=> array(11) { ["entry_id"]=> string(3) "230" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "CFI Flash device mapped on RPX Lite or CLLF" ["name"]=> string(11) "MTD_RPXLITE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(316) " The RPXLite PowerPC board has CFI-compliant chips mapped in a strange sparse mapping. This 'mapping' driver supports that arrangement, allowing the CFI probe and command set driver code to communicate with the chips on the RPXLite board. More at . " } [230]=> array(11) { ["entry_id"]=> string(3) "231" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "System flash on MBX860 board" ["name"]=> string(10) "MTD_MBX860" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(169) " This enables access routines for the flash chips on the Motorola MBX860 board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [231]=> array(11) { ["entry_id"]=> string(3) "232" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "CFI Flash device mapped on D-Box2" ["name"]=> string(9) "MTD_DBOX2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(173) " This enables access routines for the flash chips on the Nokia/Sagem D-Box 2 board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [232]=> array(11) { ["entry_id"]=> string(3) "233" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "CFI Flash device mapping on FlagaDM" ["name"]=> string(15) "MTD_CFI_FLAGADM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(86) " Mapping for the Flaga digital module. If you donīt have one, ignore this setting. " } [233]=> array(11) { ["entry_id"]=> string(3) "234" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "CFI Flash device mapped on IBM 405LP Beech" ["name"]=> string(9) "MTD_BEECH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(169) " This enables access routines for the flash chips on the IBM 405LP Beech board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [234]=> array(11) { ["entry_id"]=> string(3) "235" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "CFI Flash device mapped on IBM 405LP Arctic" ["name"]=> string(10) "MTD_ARCTIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(170) " This enables access routines for the flash chips on the IBM 405LP Arctic board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [235]=> array(11) { ["entry_id"]=> string(3) "236" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "CFI Flash device mapped on IBM 440GP Ebony" ["name"]=> string(9) "MTD_EBONY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(169) " This enables access routines for the flash chips on the IBM 440GP Ebony board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [236]=> array(11) { ["entry_id"]=> string(3) "237" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "CFI Flash devices mapped on IBM Redwood" ["name"]=> string(11) "MTD_REDWOOD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(165) " This enables access routines for the flash chips on the IBM Redwood board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [237]=> array(11) { ["entry_id"]=> string(3) "238" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(68) "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board" ["name"]=> string(17) "MTD_CSTM_MIPS_IXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(656) " This provides a mapping driver for the Integrated Tecnology Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference Board. It provides the necessary addressing, length, buswidth, vpp code and addition setup of the flash device for these boards. In addition, this mapping driver can be used for other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/ LEN/BUSWIDTH parameters. This mapping will provide one mtd device using one partition. The start address can be offset from the beginning of flash and the len can be less than the total flash device size to allow a window into the flash. Both CFI and JEDEC probes are called. " } [238]=> array(11) { ["entry_id"]=> string(3) "239" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(23) "MTD_CSTM_MIPS_IXX_START" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(39) "Physical start address of flash mapping" ["help_text"]=> NULL } [239]=> array(11) { ["entry_id"]=> string(3) "240" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(21) "MTD_CSTM_MIPS_IXX_LEN" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(32) "Physical length of flash mapping" ["help_text"]=> NULL } [240]=> array(11) { ["entry_id"]=> string(3) "241" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(26) "MTD_CSTM_MIPS_IXX_BUSWIDTH" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(19) "Bus width in octets" ["help_text"]=> NULL } [241]=> array(11) { ["entry_id"]=> string(3) "242" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Momenco Ocelot boot flash device" ["name"]=> string(10) "MTD_OCELOT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(189) " This enables access routines for the boot flash device and for the NVRAM on the Momenco Ocelot board. If you have one of these boards and would like access to either of these, say 'Y'. " } [242]=> array(11) { ["entry_id"]=> string(3) "243" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "CFI Flash device mapped on Hitachi SolutionEngine" ["name"]=> string(18) "MTD_SOLUTIONENGINE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(148) " This enables access to the flash chips on the Hitachi SolutionEngine and similar boards. Say 'Y' if you are building a kernel for such a board. " } [243]=> array(11) { ["entry_id"]=> string(3) "244" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "CFI Flash device mapped on ARM Integrator/P720T" ["name"]=> string(18) "MTD_ARM_INTEGRATOR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [244]=> array(11) { ["entry_id"]=> string(3) "245" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Cirrus CDB89712 evaluation board mappings" ["name"]=> string(12) "MTD_CDB89712" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(108) " This enables access to the flash or ROM chips on the CDB89712 board. If you have such a board, say 'Y'. " } [245]=> array(11) { ["entry_id"]=> string(3) "246" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "CFI Flash device mapped on StrongARM SA11x0" ["name"]=> string(10) "MTD_SA1100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(171) " This enables access to the flash chips on most platforms based on the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. If you have such a board, say 'Y'. " } [246]=> array(11) { ["entry_id"]=> string(3) "247" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "CFI Flash device mapped on DC21285 Footbridge" ["name"]=> string(11) "MTD_DC21285" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(198) " This provides a driver for the flash accessed using Intel's 21285 bridge used with Intel's StrongARM processors. More info at . " } [247]=> array(11) { ["entry_id"]=> string(3) "248" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "CFI Flash device mapped on the XScale IQ80310 board" ["name"]=> string(11) "MTD_IQ80310" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(186) " This enables access routines for the flash chips on the Intel XScale IQ80310 evaluation board. If you have one of these boards and would like to use the flash chips on it, say 'Y'. " } [248]=> array(11) { ["entry_id"]=> string(3) "249" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "CFI Flash device mapped on Epxa10db" ["name"]=> string(12) "MTD_EPXA10DB" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(190) " This enables support for the flash devices on the Altera Excalibur XA10 Development Board. If you are building a kernel for on of these boards then you should say 'Y' otherwise say 'N'. " } [249]=> array(11) { ["entry_id"]=> string(3) "250" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "CFI Flash device mapped on the FortuNet board" ["name"]=> string(12) "MTD_FORTUNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(96) " This enables access to the Flash on the FortuNet board. If you have such a board, say 'Y'. " } [250]=> array(11) { ["entry_id"]=> string(3) "251" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "NV-RAM mapping AUTCPU12 board" ["name"]=> string(12) "MTD_AUTCPU12" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(101) " This enables access to the NV-RAM on autronix autcpu12 board. If you have such a board, say 'Y'. " } [251]=> array(11) { ["entry_id"]=> string(3) "252" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "CFI Flash device mapped on EDB7312" ["name"]=> string(11) "MTD_EDB7312" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(110) " This enables access to the CFI Flash on the Cogent EDB7312 board. If you have such a board, say 'Y' here. " } [252]=> array(11) { ["entry_id"]=> string(3) "253" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "JEDEC Flash device mapped on impA7" ["name"]=> string(9) "MTD_IMPA7" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(120) " This enables access to the NOR Flash on the impA7 board of implementa GmbH. If you have such a board, say 'Y' here. " } [253]=> array(11) { ["entry_id"]=> string(3) "254" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(74) "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" ["name"]=> string(9) "MTD_CEIVA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(133) " This enables access to the flash chips on the Ceiva/Polaroid PhotoMax Digital Picture Frame. If you have such a device, say 'Y'. " } [254]=> array(11) { ["entry_id"]=> string(3) "255" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Hynix evaluation board mappings" ["name"]=> string(9) "MTD_H720X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(110) " This enables access to the flash chips on the Hynix evaluation boards. If you have such a board, say 'Y'. " } [255]=> array(11) { ["entry_id"]=> string(3) "256" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "PCI MTD driver" ["name"]=> string(7) "MTD_PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(225) " Mapping for accessing flash devices on add-in cards like the Intel XScale IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode (please see the manual for the link settings). If you are not sure, say N. " } [256]=> array(11) { ["entry_id"]=> string(3) "257" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "PCMCIA MTD driver" ["name"]=> string(10) "MTD_PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(187) " Map driver for accessing PCMCIA linear flash memory cards. These cards are usually around 4-16MiB in size. This does not include Compact Flash cards which are treated as IDE devices. " } [257]=> array(11) { ["entry_id"]=> string(3) "258" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Generic uClinux RAM/ROM filesystem support" ["name"]=> string(11) "MTD_UCLINUX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(63) " Map driver to support image based filesystems for uClinux. " } [258]=> array(11) { ["entry_id"]=> string(3) "259" ["entry_type"]=> string(4) "MENU" ["text"]=> string(33) "Self-contained MTD device drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [259]=> array(11) { ["entry_id"]=> string(3) "260" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Ramix PMC551 PCI Mezzanine RAM card support" ["name"]=> string(10) "MTD_PMC551" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(748) " This provides a MTD device driver for the Ramix PMC551 RAM PCI card from Ramix Inc. . These devices come in memory configurations from 32M - 1G. If you have one, you probably want to enable this. If this driver is compiled as a module you get the ability to select the size of the aperture window pointing into the devices memory. What this means is that if you have a 1G card, normally the kernel will use a 1G memory map as its view of the device. As a module, you can select a 1M window into the memory and the driver will "slide" the window around the PMC551's memory. This was particularly useful on the 2.2 kernels on PPC architectures as there was limited kernel space to deal with. " } [260]=> array(11) { ["entry_id"]=> string(3) "261" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "PMC551 256M DRAM Bugfix" ["name"]=> string(17) "MTD_PMC551_BUGFIX" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(189) " Some of Ramix's PMC551 boards with 256M configurations have invalid column and row mux values. This option will fix them, but will break other memory configurations. If unsure say N. " } [261]=> array(11) { ["entry_id"]=> string(3) "262" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "PMC551 Debugging" ["name"]=> string(16) "MTD_PMC551_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(194) " This option makes the PMC551 more verbose during its operation and is only really useful if you are developing on this driver or suspect a possible hardware or driver bug. If unsure say N. " } [262]=> array(11) { ["entry_id"]=> string(3) "263" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "DEC MS02-NV NVRAM module support" ["name"]=> string(10) "MTD_MS02NV" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(44) " Support for NVRAM module on DECstation. " } [263]=> array(11) { ["entry_id"]=> string(3) "264" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Uncached system RAM" ["name"]=> string(9) "MTD_SLRAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(194) " If your CPU cannot cache all of the physical memory in your machine, you can still use it for storage or swap by using this driver to present it to the system as a Memory Technology Device. " } [264]=> array(11) { ["entry_id"]=> string(3) "265" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "28F160xx flash driver for LART" ["name"]=> string(8) "MTD_LART" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(199) " This enables the flash driver for LART. Please note that you do not need any mapping/chip driver for LART. This one does it all for you, so go disable all of those if you enabled some of them (: " } [265]=> array(11) { ["entry_id"]=> string(3) "266" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Test driver using RAM" ["name"]=> string(10) "MTD_MTDRAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(142) " This enables a test MTD device driver which uses vmalloc() to provide storage. You probably want to say 'N' unless you're testing stuff. " } [266]=> array(11) { ["entry_id"]=> string(3) "267" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(17) "MTDRAM_TOTAL_SIZE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(25) "MTDRAM device size in KiB" ["help_text"]=> NULL } [267]=> array(11) { ["entry_id"]=> string(3) "268" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(17) "MTDRAM_ERASE_SIZE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(30) "MTDRAM erase block size in KiB" ["help_text"]=> NULL } [268]=> array(11) { ["entry_id"]=> string(3) "269" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(14) "MTDRAM_ABS_POS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(39) "SRAM Hexadecimal Absolute position or 0" ["help_text"]=> NULL } [269]=> array(11) { ["entry_id"]=> string(3) "270" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "MTD emulation using block device" ["name"]=> string(10) "MTD_BLKMTD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(323) " This driver allows a block device to appear as an MTD. It would generally be used in the following cases: Using Compact Flash as an MTD, these usually present themselves to the system as an ATA drive. Testing MTD users (eg JFFS2) on large media and media that might be removed during a write (using the floppy drive). " } [270]=> array(11) { ["entry_id"]=> string(3) "271" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "M-Systems Disk-On-Chip 2000 and Millennium" ["name"]=> string(11) "MTD_DOC2000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(669) " This provides an MTD device driver for the M-Systems DiskOnChip 2000 and Millennium devices. Originally designed for the DiskOnChip 2000, it also now includes support for the DiskOnChip Millennium. If you have problems with this driver and the DiskOnChip Millennium, you may wish to try the alternative Millennium driver below. To use the alternative driver, you will need to undefine DOC_SINGLE_DRIVER in the source code. If you use this device, you probably also want to enable the NFTL 'NAND Flash Translation Layer' option below, which is used to emulate a block device by using a kind of file system on the flash chips. " } [271]=> array(11) { ["entry_id"]=> string(3) "272" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(68) "M-Systems Disk-On-Chip Millennium-only alternative driver (see help)" ["name"]=> string(11) "MTD_DOC2001" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(591) " This provides an alternative MTD device driver for the M-Systems DiskOnChip Millennium devices. Use this if you have problems with the combined DiskOnChip 2000 and Millennium driver above. To get the DiskOnChip probe code to load and use this driver instead of the other one, you will need to undefine DOC_SINGLE_DRIVER near the beginning of . If you use this device, you probably also want to enable the NFTL 'NAND Flash Translation Layer' option below, which is used to emulate a block device by using a kind of file system on the flash chips. " } [272]=> array(11) { ["entry_id"]=> string(3) "273" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "M-Systems Disk-On-Chip Millennium Plus" ["name"]=> string(15) "MTD_DOC2001PLUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(306) " This provides an MTD device driver for the M-Systems DiskOnChip Millennium Plus devices. If you use this device, you probably also want to enable the INFTL 'Inverse NAND Flash Translation Layer' option below, which is used to emulate a block device by using a kind of file system on the flash chips. " } [273]=> array(11) { ["entry_id"]=> string(3) "274" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "MTD_DOCPROBE" ["name"]=> string(12) "MTD_DOCPROBE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(51) " This isn't a real config option, it's derived. " } [274]=> array(11) { ["entry_id"]=> string(3) "275" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Advanced detection options for DiskOnChip" ["name"]=> string(21) "MTD_DOCPROBE_ADVANCED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(209) " This option allows you to specify nonstandard address at which to probe for a DiskOnChip, or to change the detection options. You are unlikely to need any of this unless you are using LinuxBIOS. Say 'N'. " } [275]=> array(11) { ["entry_id"]=> string(3) "276" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(20) "MTD_DOCPROBE_ADDRESS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(30) "Physical address of DiskOnChip" ["help_text"]=> NULL } [276]=> array(11) { ["entry_id"]=> string(3) "277" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Probe high addresses" ["name"]=> string(17) "MTD_DOCPROBE_HIGH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(286) " By default, the probe for DiskOnChip devices will look for a DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. This option changes to make it probe between 0xFFFC8000 and 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be useful to you. Say 'N'. " } [277]=> array(11) { ["entry_id"]=> string(3) "278" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "Probe for 0x55 0xAA BIOS Extension Signature" ["name"]=> string(17) "MTD_DOCPROBE_55AA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(439) " Check for the 0x55 0xAA signature of a DiskOnChip, and do not continue with probing if it is absent. The signature will always be present for a DiskOnChip 2000 or a normal DiskOnChip Millennium. Only if you have overwritten the first block of a DiskOnChip Millennium will it be absent. Enable this option if you are using LinuxBIOS or if you need to recover a DiskOnChip Millennium on which you have managed to wipe the first block. " } [278]=> array(11) { ["entry_id"]=> string(3) "279" ["entry_type"]=> string(4) "MENU" ["text"]=> string(25) "NAND Flash Device Drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [279]=> array(11) { ["entry_id"]=> string(3) "280" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "NAND Device Support" ["name"]=> string(8) "MTD_NAND" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(177) " This enables support for accessing all type of NAND flash devices with an 8-bit data bus interface. For further information see www.linux-mtd.infradead.org/tech/nand.html. " } [280]=> array(11) { ["entry_id"]=> string(3) "281" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Verify NAND page writes" ["name"]=> string(21) "MTD_NAND_VERIFY_WRITE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(310) " This adds an extra check when data is written to the flash. The NAND flash device internally checks only bits transitioning from 1 to 0. There is a rare possibility that even though the device thinks the write was successful, a bit could have been flipped accidentaly due to device wear or something else. " } [281]=> array(11) { ["entry_id"]=> string(3) "282" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "SmartMediaCard on autronix autcpu12 board" ["name"]=> string(17) "MTD_NAND_AUTCPU12" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(91) " This enables the driver for the autronix autcpu12 board to access the SmartMediaCard. " } [282]=> array(11) { ["entry_id"]=> string(3) "283" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Support for Cirrus Logic EBD7312 evaluation board" ["name"]=> string(16) "MTD_NAND_EDB7312" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(109) " This enables the driver for the Cirrus Logic EBD7312 evaluation board to access the onboard NAND Flash. " } [283]=> array(11) { ["entry_id"]=> string(3) "284" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "NAND Flash device on SPIA board" ["name"]=> string(13) "MTD_NAND_SPIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(52) " If you had to ask, you don't have one. Say 'N'. " } [284]=> array(11) { ["entry_id"]=> string(3) "285" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "MTD_NAND_IDS" ["name"]=> string(12) "MTD_NAND_IDS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [285]=> array(11) { ["entry_id"]=> string(3) "286" ["entry_type"]=> string(4) "MENU" ["text"]=> string(21) "Plug and Play support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [286]=> array(11) { ["entry_id"]=> string(3) "287" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Plug and Play support" ["name"]=> string(3) "PNP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(587) " Plug and Play (PnP) is a standard for peripherals which allows those peripherals to be configured by software, e.g. assign IRQ's or other parameters. No jumpers on the cards are needed, instead the values are provided to the cards from the BIOS, from the operating system, or using a user-space utility. Say Y here if you would like Linux to configure your Plug and Play devices. You should then also say Y to all of the protocols below. Alternatively, you can say N here and configure your PnP devices using user space utilities such as the isapnptools package. If unsure, say Y. " } [287]=> array(11) { ["entry_id"]=> string(3) "288" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Plug and Play device name database" ["name"]=> string(9) "PNP_NAMES" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(227) " Select Y if you want the Plug and Play Layer to keep a database of human readable names for your PnP devices. It will increase the size of the kernel image by around 5 KB and use 16 KB of system memory. If unsure, say Y. " } [288]=> array(11) { ["entry_id"]=> string(3) "289" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "PnP Debug Messages" ["name"]=> string(9) "PNP_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(141) " Say Y if you want the Plug and Play Layer to print debug messages. This is useful if you are developing a PnP driver or troubleshooting. " } [289]=> array(11) { ["entry_id"]=> string(3) "290" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "ISA Plug and Play support (EXPERIMENTAL)" ["name"]=> string(6) "ISAPNP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(147) " Say Y here if you would like support for ISA Plug and Play devices. Some information is in . If unsure, say Y. " } [290]=> array(11) { ["entry_id"]=> string(3) "291" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Plug and Play BIOS support (EXPERIMENTAL)" ["name"]=> string(7) "PNPBIOS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(485) " Linux uses the PNPBIOS as defined in "Plug and Play BIOS Specification Version 1.0A May 5, 1994" to autodetect built-in mainboard resources (e.g. parallel port resources). Some features (e.g. event notification, docking station information, ISAPNP services) are not used. Note: ACPI is expected to supersede PNPBIOS some day, currently it co-exists nicely. See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools, or have a look at /proc/bus/pnp. If unsure, say Y. " } [291]=> array(11) { ["entry_id"]=> string(3) "292" ["entry_type"]=> string(4) "MENU" ["text"]=> string(13) "Block devices" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [292]=> array(11) { ["entry_id"]=> string(3) "293" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Normal floppy disk support" ["name"]=> string(10) "BLK_DEV_FD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(636) " If you want to use the floppy disk drive(s) of your PC under Linux, say Y. Information about this driver, especially important for IBM Thinkpad users, is contained in . That file also contains the location of the Floppy driver FAQ as well as location of the fdutils package used to configure additional parameters of the driver at run time. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called floppy. If you want to compile it as a module, say M here and read . " } [293]=> array(11) { ["entry_id"]=> string(3) "294" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Amiga floppy support" ["name"]=> string(12) "AMIGA_FLOPPY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [294]=> array(11) { ["entry_id"]=> string(3) "295" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Atari floppy support" ["name"]=> string(12) "ATARI_FLOPPY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [295]=> array(11) { ["entry_id"]=> string(3) "296" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "NEC PC-9800 floppy disk support" ["name"]=> string(12) "BLK_DEV_FD98" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(79) " If you want to use the floppy disk drive(s) of NEC PC-9801/PC-9821, say Y. " } [296]=> array(11) { ["entry_id"]=> string(3) "297" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(66) "Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)" ["name"]=> string(16) "BLK_DEV_SWIM_IOP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(130) " Say Y here to support the SWIM (Super Woz Integrated Machine) IOP floppy controller on the Macintosh IIfx and Quadra 900/950. " } [297]=> array(11) { ["entry_id"]=> string(3) "298" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "PS/2 ESDI hard disk support" ["name"]=> string(11) "BLK_DEV_PS2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(307) " Say Y here if you have a PS/2 machine with a MCA bus and an ESDI hard disk. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ps2esdi. " } [298]=> array(11) { ["entry_id"]=> string(3) "299" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Amiga Zorro II ramdisk support" ["name"]=> string(11) "AMIGA_Z2RAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(407) " This enables support for using Chip RAM and Zorro II RAM as a ramdisk or as a swap partition. Say Y if you want to include this driver in the kernel. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called z2ram. If you want to compile it as a module, say M here and read . " } [299]=> array(11) { ["entry_id"]=> string(3) "300" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Atari ACSI support" ["name"]=> string(10) "ATARI_ACSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(725) " This enables support for the Atari ACSI interface. The driver supports hard disks and CD-ROMs, which have 512-byte sectors, or can be switched to that mode. Due to the ACSI command format, only disks up to 1 GB are supported. Special support for certain ACSI to SCSI adapters, which could relax that, isn't included yet. The ACSI driver is also the basis for certain other drivers for devices attached to the ACSI bus: Atari SLM laser printer, BioNet-100 Ethernet, and PAMsNet Ethernet. If you want to use one of these devices, you need ACSI support, too. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called acsi. " } [300]=> array(11) { ["entry_id"]=> string(3) "301" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Probe all LUNs on each ACSI device" ["name"]=> string(14) "ACSI_MULTI_LUN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(383) " If you have a ACSI device that supports more than one LUN (Logical Unit Number), e.g. a CD jukebox, you should say Y here so that all will be found by the ACSI driver. An ACSI device with multiple LUNs acts logically like multiple ACSI devices. The vast majority of ACSI devices have only one LUN, and so most people can say N here and should in fact do so, because it is safer. " } [301]=> array(11) { ["entry_id"]=> string(3) "302" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Atari SLM laser printer support" ["name"]=> string(9) "ATARI_SLM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(358) " If you have an Atari SLM laser printer, say Y to include support for it in the kernel. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called acsi_slm. Be warned: the driver needs much ST-RAM and can cause problems due to that fact! " } [302]=> array(11) { ["entry_id"]=> string(3) "303" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "XT hard disk support" ["name"]=> string(10) "BLK_DEV_XD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(384) " Very old 8 bit hard disk controllers used in the IBM XT computer will be supported if you say Y here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called xd. It's pretty unlikely that you have one of these: say N. " } [303]=> array(11) { ["entry_id"]=> string(3) "304" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Parallel port IDE device support" ["name"]=> string(6) "PARIDE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1227) " There are many external CD-ROM and disk devices that connect through your computer's parallel port. Most of them are actually IDE devices using a parallel port IDE adapter. This option enables the PARIDE subsystem which contains drivers for many of these external drives. Read for more information. If you have said Y to the "Parallel-port support" configuration option, you may share a single port between your printer and other parallel port devices. Answer Y to build PARIDE support into your kernel, or M if you would like to build it as a loadable module. If your parallel port support is in a loadable module, you must build PARIDE as a module. If you built PARIDE support into your kernel, you may still build the individual protocol modules and high-level drivers as loadable modules. If you build this support as a module, it will be called paride. To use the PARIDE support, you must say Y or M here and also to at least one high-level driver (e.g. "Parallel port IDE disks", "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and to at least one protocol driver (e.g. "ATEN EH-100 protocol", "MicroSolutions backpack protocol", "DataStor Commuter protocol" etc.). " } [304]=> array(11) { ["entry_id"]=> string(3) "305" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "PARIDE_PARPORT" ["name"]=> string(14) "PARIDE_PARPORT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [305]=> array(11) { ["entry_id"]=> string(3) "306" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Parallel port IDE disks" ["name"]=> string(9) "PARIDE_PD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(557) " This option enables the high-level driver for IDE-type disk devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port IDE driver, otherwise you should answer M to build it as a loadable module. The module will be called pd. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the SyQuest EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack hard drives from MicroSolutions. " } [306]=> array(11) { ["entry_id"]=> string(3) "307" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Parallel port ATAPI CD-ROMs" ["name"]=> string(10) "PARIDE_PCD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(678) " This option enables the high-level driver for ATAPI CD-ROM devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI CD-ROM driver, otherwise you should answer M to build it as a loadable module. The module will be called pcd. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If you have such a CD-ROM drive, you should also say Y or M to "ISO 9660 CD-ROM file system support" below, because that's the file system used on CD-ROMs. " } [307]=> array(11) { ["entry_id"]=> string(3) "308" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Parallel port ATAPI disks" ["name"]=> string(9) "PARIDE_PF" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(529) " This option enables the high-level driver for ATAPI disk devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI disk driver, otherwise you should answer M to build it as a loadable module. The module will be called pf. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the MicroSolutions backpack PD/CD drive and the Imation Superdisk LS-120 drive. " } [308]=> array(11) { ["entry_id"]=> string(3) "309" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Parallel port ATAPI tapes" ["name"]=> string(9) "PARIDE_PT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(495) " This option enables the high-level driver for ATAPI tape devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI disk driver, otherwise you should answer M to build it as a loadable module. The module will be called pt. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver is the parallel port version of the HP 5GB drive. " } [309]=> array(11) { ["entry_id"]=> string(3) "310" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Parallel port generic ATAPI devices" ["name"]=> string(9) "PARIDE_PG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(787) " This option enables a special high-level driver for generic ATAPI devices connected through a parallel port. The driver allows user programs, such as cdrtools, to send ATAPI commands directly to a device. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port generic ATAPI driver, otherwise you should answer M to build it as a loadable module. The module will be called pg. You must also have at least one parallel port protocol driver in your system. This driver implements an API loosely related to the generic SCSI driver. See . for details. You can obtain the most recent version of cdrtools from . Versions 1.6.1a3 and later fully support this driver. " } [310]=> array(11) { ["entry_id"]=> string(3) "311" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "ATEN EH-100 protocol" ["name"]=> string(11) "PARIDE_ATEN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(470) " This option enables support for the ATEN EH-100 parallel port IDE protocol. This protocol is used in some inexpensive low performance parallel port kits made in Hong Kong. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called aten. You must also have a high-level driver for the type of device that you want to support. " } [311]=> array(11) { ["entry_id"]=> string(3) "312" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "MicroSolutions backpack (Series 5) protocol" ["name"]=> string(11) "PARIDE_BPCK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(657) " This option enables support for the Micro Solutions BACKPACK parallel port Series 5 IDE protocol. (Most BACKPACK drives made before 1999 were Series 5) Series 5 drives will NOT always have the Series noted on the bottom of the drive. Series 6 drivers will. In other words, if your BACKPACK drive dosen't say "Series 6" on the bottom, enable this option. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called bpck. You must also have a high-level driver for the type of device that you want to support. " } [312]=> array(11) { ["entry_id"]=> string(3) "313" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "MicroSolutions backpack (Series 6) protocol" ["name"]=> string(12) "PARIDE_BPCK6" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(662) " This option enables support for the Micro Solutions BACKPACK parallel port Series 6 IDE protocol. (Most BACKPACK drives made after 1999 were Series 6) Series 6 drives will have the Series noted on the bottom of the drive. Series 5 drivers don't always have it noted. In other words, if your BACKPACK drive says "Series 6" on the bottom, enable this option. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called bpck6. You must also have a high-level driver for the type of device that you want to support. " } [313]=> array(11) { ["entry_id"]=> string(3) "314" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "DataStor Commuter protocol" ["name"]=> string(11) "PARIDE_COMM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(385) " This option enables support for the Commuter parallel port IDE protocol from DataStor. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called comm. You must also have a high-level driver for the type of device that you want to support. " } [314]=> array(11) { ["entry_id"]=> string(3) "315" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "DataStor EP-2000 protocol" ["name"]=> string(11) "PARIDE_DSTR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(384) " This option enables support for the EP-2000 parallel port IDE protocol from DataStor. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called dstr. You must also have a high-level driver for the type of device that you want to support. " } [315]=> array(11) { ["entry_id"]=> string(3) "316" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "FIT TD-2000 protocol" ["name"]=> string(11) "PARIDE_FIT2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(489) " This option enables support for the TD-2000 parallel port IDE protocol from Fidelity International Technology. This is a simple (low speed) adapter that is used in some portable hard drives. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called ktti. You must also have a high-level driver for the type of device that you want to support. " } [316]=> array(11) { ["entry_id"]=> string(3) "317" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "FIT TD-3000 protocol" ["name"]=> string(11) "PARIDE_FIT3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(497) " This option enables support for the TD-3000 parallel port IDE protocol from Fidelity International Technology. This protocol is used in newer models of their portable disk, CD-ROM and PD/CD devices. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called fit3. You must also have a high-level driver for the type of device that you want to support. " } [317]=> array(11) { ["entry_id"]=> string(3) "318" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Shuttle EPAT/EPEZ protocol" ["name"]=> string(11) "PARIDE_EPAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(538) " This option enables support for the EPAT parallel port IDE protocol. EPAT is a parallel port IDE adapter manufactured by Shuttle Technology and widely used in devices from major vendors such as Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called epat. You must also have a high-level driver for the type of device that you want to support. " } [318]=> array(11) { ["entry_id"]=> string(3) "319" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Support c7/c8 chips (EXPERIMENTAL)" ["name"]=> string(13) "PARIDE_EPATC8" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(159) " This option enables support for the newer Shuttle EP1284 (aka c7 and c8) chip. You need this if you are using any recent Imation SuperDisk (LS-120) drive. " } [319]=> array(11) { ["entry_id"]=> string(3) "320" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Shuttle EPIA protocol" ["name"]=> string(11) "PARIDE_EPIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(456) " This option enables support for the (obsolete) EPIA parallel port IDE protocol from Shuttle Technology. This adapter can still be found in some no-name kits. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called epia. You must also have a high-level driver for the type of device that you want to support. " } [320]=> array(11) { ["entry_id"]=> string(3) "321" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Freecom IQ ASIC-2 protocol" ["name"]=> string(11) "PARIDE_FRIQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(439) " This option enables support for version 2 of the Freecom IQ parallel port IDE adapter. This adapter is used by the Maxell Superdisk drive. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called friq. You must also have a high-level driver for the type of device that you want to support. " } [321]=> array(11) { ["entry_id"]=> string(3) "322" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "FreeCom power protocol" ["name"]=> string(11) "PARIDE_FRPW" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(376) " This option enables support for the Freecom power parallel port IDE protocol. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called frpw. You must also have a high-level driver for the type of device that you want to support. " } [322]=> array(11) { ["entry_id"]=> string(3) "323" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "KingByte KBIC-951A/971A protocols" ["name"]=> string(11) "PARIDE_KBIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(518) " This option enables support for the KBIC-951A and KBIC-971A parallel port IDE protocols from KingByte Information Corp. KingByte's adapters appear in many no-name portable disk and CD-ROM products, especially in Europe. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called kbic. You must also have a high-level driver for the type of device that you want to support. " } [323]=> array(11) { ["entry_id"]=> string(3) "324" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "KT PHd protocol" ["name"]=> string(11) "PARIDE_KTTI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(472) " This option enables support for the "PHd" parallel port IDE protocol from KT Technology. This is a simple (low speed) adapter that is used in some 2.5" portable hard drives. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called ktti. You must also have a high-level driver for the type of device that you want to support. " } [324]=> array(11) { ["entry_id"]=> string(3) "325" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "OnSpec 90c20 protocol" ["name"]=> string(11) "PARIDE_ON20" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(439) " This option enables support for the (obsolete) 90c20 parallel port IDE protocol from OnSpec (often marketed under the ValuStore brand name). If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called on20. You must also have a high-level driver for the type of device that you want to support. " } [325]=> array(11) { ["entry_id"]=> string(3) "326" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "OnSpec 90c26 protocol" ["name"]=> string(11) "PARIDE_ON26" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(440) " This option enables support for the 90c26 parallel port IDE protocol from OnSpec Electronics (often marketed under the ValuStore brand name). If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called on26. You must also have a high-level driver for the type of device that you want to support. " } [326]=> array(11) { ["entry_id"]=> string(3) "327" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Compaq SMART2 support" ["name"]=> string(10) "BLK_CPQ_DA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(267) " This is the driver for Compaq Smart Array controllers. Everyone using these boards should say Y here. See the file for the current list of boards supported by this driver, and for further information on the use of this driver. " } [327]=> array(11) { ["entry_id"]=> string(3) "328" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Compaq Smart Array 5xxx support" ["name"]=> string(15) "BLK_CPQ_CISS_DA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(258) " This is the driver for Compaq Smart Array 5xxx controllers. Everyone using these boards should say Y here. See for the current list of boards supported by this driver, and for further information on the use of this driver. " } [328]=> array(11) { ["entry_id"]=> string(3) "329" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "SCSI tape drive support for Smart Array 5xxx" ["name"]=> string(14) "CISS_SCSI_TAPE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(369) " When enabled (Y), this option allows SCSI tape drives and SCSI medium changers (tape robots) to be accessed via a Compaq 5xxx array controller. (See Documentation/cciss.txt for more details.) "SCSI support" and "SCSI tape support" must also be enabled for this option to work. When this option is disabled (N), the SCSI portion of the driver is not compiled. " } [329]=> array(11) { ["entry_id"]=> string(3) "330" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Mylex DAC960/DAC1100 PCI RAID Controller support" ["name"]=> string(14) "BLK_DEV_DAC960" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(419) " This driver adds support for the Mylex DAC960, AcceleRAID, and eXtremeRAID PCI RAID controllers. See the file for further information about this driver. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called DAC960. " } [330]=> array(11) { ["entry_id"]=> string(3) "331" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(61) "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)" ["name"]=> string(12) "BLK_DEV_UMEM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(583) " Saying Y here will include support for the MM5415 family of battery backed (Non-volatile) RAM cards. http://www.umem.com/ The cards appear as block devices that can be partitioned into as many as 15 partitions. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called umem. The umem driver has not yet been allocated a MAJOR number, so one is chosen dynamically. Use "devfs" or look in /proc/devices for the device number " } [331]=> array(11) { ["entry_id"]=> string(3) "332" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Loopback device support" ["name"]=> string(12) "BLK_DEV_LOOP" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1792) " Saying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc. This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver. To use the loop device, you need the losetup utility, found in the util-linux package, see . The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server. There are several ways of doing this. Some of these require kernel patches. The vanilla kernel offers the cryptoloop option. If you want to use that, say Y to both LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 or later) version of util-linux. Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called loop. Most users will answer N here. " } [332]=> array(11) { ["entry_id"]=> string(3) "333" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Cryptoloop Support" ["name"]=> string(18) "BLK_DEV_CRYPTOLOOP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(161) " Say Y here if you want to be able to use the ciphers that are provided by the CryptoAPI as loop transformation. This might be used as hard disk encryption. " } [333]=> array(11) { ["entry_id"]=> string(3) "334" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Network block device support" ["name"]=> string(11) "BLK_DEV_NBD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1113) " Saying Y here will allow your computer to be a client for network block devices, i.e. it will be able to use block devices exported by servers (mount file systems on them etc.). Communication between client and server works over TCP/IP networking, but to the client program this is hidden: it looks like a regular local file access to a block device special file such as /dev/nd0. Network block devices also allows you to run a block-device in userland (making server and client physically the same computer, communicating using the loopback network device). Read for more information, especially about where to find the server code, which runs in user space and does not need special kernel support. Note that this has nothing to do with the network file systems NFS or Coda; you can say N here even if you intend to use NFS or Coda. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called nbd. If unsure, say N. " } [334]=> array(11) { ["entry_id"]=> string(3) "335" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "RAM disk support" ["name"]=> string(11) "BLK_DEV_RAM" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(796) " Saying Y here will allow you to use a portion of your RAM memory as a block device, so that you can make file systems on it, read and write to it and do all the other things that you can do with normal block devices (such as hard drives). It is usually used to load and store a copy of a minimal root file system off of a floppy into RAM during the initial install of Linux. Note that the kernel command line option "ramdisk=XX" is now obsolete. For details, read . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M and read . The module will be called rd. Most normal users won't need the RAM disk functionality, and can thus say N here. " } [335]=> array(11) { ["entry_id"]=> string(3) "336" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(16) "BLK_DEV_RAM_SIZE" ["value"]=> string(4) "4096" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(21) "Default RAM disk size" ["help_text"]=> NULL } [336]=> array(11) { ["entry_id"]=> string(3) "337" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Initial RAM disk (initrd) support" ["name"]=> string(14) "BLK_DEV_INITRD" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(289) " The initial RAM disk is a RAM disk that is loaded by the boot loader (loadlin or lilo) and that is mounted as root before the normal boot procedure. It is typically used to load modules needed to mount the "real" root file system, etc. See for details. " } [337]=> array(11) { ["entry_id"]=> string(3) "338" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support for Large Block Devices" ["name"]=> string(3) "LBD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(168) " Say Y here if you want to attach large (bigger than 2TB) discs to your machine, or if you want to have a raid or loopback device bigger than 2TB. Otherwise say N. " } [338]=> array(11) { ["entry_id"]=> string(3) "339" ["entry_type"]=> string(4) "MENU" ["text"]=> string(25) "ATA/ATAPI/MFM/RLL support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [339]=> array(11) { ["entry_id"]=> string(3) "340" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ATA/ATAPI/MFM/RLL support" ["name"]=> string(3) "IDE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1937) " If you say Y here, your kernel will be able to manage low cost mass storage units such as ATA/(E)IDE and ATAPI units. The most common cases are IDE hard drives and ATAPI CD-ROM drives. If your system is pure SCSI and doesn't use these interfaces, you can say N here. Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard for mass storage units such as hard disks. It was designed by Western Digital and Compaq Computer in 1984. It was then named ST506. Quite a number of disks use the IDE interface. AT Attachment (ATA) is the superset of the IDE specifications. ST506 was also called ATA-1. Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is ATA-3. It provides support for larger disks (up to 8.4GB by means of the LBA standard), more disks (4 instead of 2) and for other mass storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is ATA-4 and provides faster (and more CPU friendly) transfer modes than previous PIO (Programmed processor Input/Output) from previous ATA/IDE standards by means of fast DMA controllers. ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and CD-ROM drives, similar in many respects to the SCSI protocol. SMART IDE (Self Monitoring, Analysis and Reporting Technology) was designed in order to prevent data corruption and disk crash by detecting pre hardware failure conditions (heat, access time, and the like...). Disks built since June 1995 may follow this standard. The kernel itself doesn't manage this; however there are quite a number of user programs such as smart that can query the status of SMART parameters from disk drives. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide. For further information, please read . If unsure, say Y. " } [340]=> array(11) { ["entry_id"]=> string(3) "341" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(13) "IDE_MAX_HWIFS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(18) "Max IDE interfaces" ["help_text"]=> NULL } [341]=> array(11) { ["entry_id"]=> string(3) "342" ["entry_type"]=> string(4) "MENU" ["text"]=> string(32) "IDE, ATA and ATAPI Block devices" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [342]=> array(11) { ["entry_id"]=> string(3) "343" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support" ["name"]=> string(11) "BLK_DEV_IDE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1415) " If you say Y here, you will use the full-featured IDE driver to control up to ten ATA/IDE interfaces, each being able to serve a "master" and a "slave" device, for a total of up to twenty ATA/IDE disk/cdrom/tape/floppy drives. Useful information about large (>540 MB) IDE disks, multiple interfaces, what to do if ATA/IDE devices are not automatically detected, sound card ATA/IDE ports, module support, and other topics, is contained in . For detailed information about hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO, available from . To fine-tune ATA/IDE drive/interface parameters for improved performance, look for the hdparm package at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read and . The module will be called ide-mod. Do not compile this driver as a module if your root file system (the one containing the directory /) is located on an IDE device. If you have one or more IDE drives, say Y or M here. If your system has no IDE drives, or if memory requirements are really tight, you could say N here, and select the "Old hard disk driver" below instead to save about 13 KB of memory in the kernel. " } [343]=> array(11) { ["entry_id"]=> string(3) "344" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Use old disk-only driver on primary interface" ["name"]=> string(14) "BLK_DEV_HD_IDE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(701) " There are two drivers for MFM/RLL/IDE disks. Most people use just the new enhanced driver by itself. This option however installs the old hard disk driver to control the primary IDE/disk interface in the system, leaving the new enhanced IDE driver to take care of only the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from having an IDE/ATAPI CD-ROM or tape drive connected to the primary IDE interface. Choosing this option may be useful for older systems which have MFM/RLL/ESDI controller+drives at the primary port address (0x1f0), along with IDE drives at the secondary/3rd/4th port addresses. Normally, just say N here; you will then use the new driver for all 4 interfaces. " } [344]=> array(11) { ["entry_id"]=> string(3) "345" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Use old disk-only driver on primary interface" ["name"]=> string(16) "BLK_DEV_HD_IDE98" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(701) " There are two drivers for MFM/RLL/IDE disks. Most people use just the new enhanced driver by itself. This option however installs the old hard disk driver to control the primary IDE/disk interface in the system, leaving the new enhanced IDE driver to take care of only the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from having an IDE/ATAPI CD-ROM or tape drive connected to the primary IDE interface. Choosing this option may be useful for older systems which have MFM/RLL/ESDI controller+drives at the primary port address (0x1f0), along with IDE drives at the secondary/3rd/4th port addresses. Normally, just say N here; you will then use the new driver for all 4 interfaces. " } [345]=> array(11) { ["entry_id"]=> string(3) "346" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "BLK_DEV_HD" ["name"]=> string(10) "BLK_DEV_HD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [346]=> array(11) { ["entry_id"]=> string(3) "347" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Include IDE/ATA-2 DISK support" ["name"]=> string(15) "BLK_DEV_IDEDISK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(610) " This will include enhanced support for MFM/RLL/IDE hard disks. If you have a MFM/RLL/IDE disk, and there is no special reason to use the old hard disk driver instead, say Y. If you have an SCSI-only system, you can say N here. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-disk. Do not compile this driver as a module if your root file system (the one containing the directory /) is located on the IDE disk. If unsure, say Y. " } [347]=> array(11) { ["entry_id"]=> string(3) "348" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Use multi-mode by default" ["name"]=> string(18) "IDEDISK_MULTI_MODE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(184) " If you get this error, try to say Y here: hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } hda: set_multmode: error=0x04 { DriveStatusError } If in doubt, say N. " } [348]=> array(11) { ["entry_id"]=> string(3) "349" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Auto-Geometry Resizing support" ["name"]=> string(14) "IDEDISK_STROKE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(482) " Should you have a system w/ an AWARD Bios and your drives are larger than 32GB and it will not boot, one is required to perform a few OEM operations first. The option is called "STROKE" because it allows one to "soft clip" the drive to work around a barrier limit. For Maxtor drives it is called "jumpon.exe". Please search Maxtor's web-site for "JUMPON.EXE". IBM has a similar tool at: . If you are unsure, say N here. " } [349]=> array(11) { ["entry_id"]=> string(3) "350" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "PCMCIA IDE support" ["name"]=> string(13) "BLK_DEV_IDECS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(101) " Support for outboard IDE disks, tape drives, and CD-ROM drives connected through a PCMCIA card. " } [350]=> array(11) { ["entry_id"]=> string(3) "351" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Include IDE/ATAPI CDROM support" ["name"]=> string(13) "BLK_DEV_IDECD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1030) " If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is a newer protocol used by IDE CD-ROM and TAPE drives, similar to the SCSI protocol. Most new CD-ROM drives use ATAPI, including the NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI double(2X) or better speed drives. If you say Y here, the CD-ROM drive will be identified at boot time along with other IDE devices, as "hdb" or "hdc", or something similar (check the boot messages with dmesg). If this is your only CD-ROM drive, you can say N to all other CD-ROM options, but be sure to say Y or M to "ISO 9660 CD-ROM file system support". Note that older versions of LILO (LInux LOader) cannot properly deal with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from . If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-cd. " } [351]=> array(11) { ["entry_id"]=> string(3) "352" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Include IDE/ATAPI FLOPPY support" ["name"]=> string(17) "BLK_DEV_IDEFLOPPY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(956) " If you have an IDE floppy drive which uses the ATAPI protocol, answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy drives, similar to the SCSI protocol. The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by this driver. For information about jumper settings and the question of when a ZIP drive uses a partition table, see . (ATAPI PD-CD/CDR drives are not supported by this driver; support for PD-CD/CDR drives is available if you answer Y to "SCSI emulation support", below). If you say Y here, the FLOPPY drive will be identified along with other IDE devices, as "hdb" or "hdc", or something similar (check the boot messages with dmesg). If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-floppy. " } [352]=> array(11) { ["entry_id"]=> string(3) "353" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "SCSI emulation support" ["name"]=> string(15) "BLK_DEV_IDESCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1066) " This will provide SCSI host adapter emulation for IDE ATAPI devices, and will allow you to use a SCSI device driver instead of a native ATAPI driver. This is useful if you have an ATAPI device for which no native driver has been written (for example, an ATAPI PD-CD or CDR drive); you can then use this emulation together with an appropriate SCSI device driver. In order to do this, say Y here and to "SCSI support" and "SCSI generic support", below. You must then provide the kernel command line "hdx=ide-scsi" (try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time) for devices if you want the native EIDE sub-drivers to skip over the native support, so that this SCSI emulation can be used instead. This is required for use of CD-RW's. Note that this option does NOT allow you to attach SCSI devices to a box that doesn't have a SCSI host adapter installed. If both this SCSI emulation and native ATAPI support are compiled into the kernel, the native support will be used. " } [353]=> array(11) { ["entry_id"]=> string(3) "354" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "IDE Taskfile Access" ["name"]=> string(14) "IDE_TASK_IOCTL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(266) " This is a direct raw access to the media. It is a complex but elegant solution to test and validate the domain of the hardware and perform below the driver data recover if needed. This is the most basic form of media-forensics. If you are unsure, say N here. " } [354]=> array(11) { ["entry_id"]=> string(3) "355" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "IDE Taskfile IO (EXPERIMENTAL)" ["name"]=> string(15) "IDE_TASKFILE_IO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(84) " Use new taskfile IO code. It is safe to say Y to this question, in most cases. " } [355]=> array(11) { ["entry_id"]=> string(3) "356" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "CMD640 chipset bugfix/support" ["name"]=> string(14) "BLK_DEV_CMD640" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1009) " The CMD-Technologies CMD640 IDE chip is used on many common 486 and Pentium motherboards, usually in combination with a "Neptune" or "SiS" chipset. Unfortunately, it has a number of rather nasty design flaws that can cause severe data corruption under many common conditions. Say Y here to include code which tries to automatically detect and correct the problems under Linux. This option also enables access to the secondary IDE ports in some CMD640 based systems. This driver will work automatically in PCI based systems (most new systems have PCI slots). But if your system uses VESA local bus (VLB) instead of PCI, you must also supply a kernel boot parameter to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel.) The CMD640 chip is also used on add-in cards by Acculogic, and on the "CSA-6400E PCI to IDE controller" that some people have. For details, read . " } [356]=> array(11) { ["entry_id"]=> string(3) "357" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "CMD640 enhanced support" ["name"]=> string(23) "BLK_DEV_CMD640_ENHANCED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(271) " This option includes support for setting/autotuning PIO modes and prefetch on CMD640 IDE interfaces. For details, read . If you have a CMD640 IDE interface and your BIOS does not already do this for you, then say Y here. Otherwise say N. " } [357]=> array(11) { ["entry_id"]=> string(3) "358" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "PNP EIDE support" ["name"]=> string(14) "BLK_DEV_IDEPNP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(138) " If you have a PnP (Plug and Play) compatible EIDE card and would like the kernel to automatically detect and activate it, say Y here. " } [358]=> array(11) { ["entry_id"]=> string(3) "359" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "PCI IDE chipset support" ["name"]=> string(14) "BLK_DEV_IDEPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(171) " Say Y here for PCI systems which use IDE drive(s). This option helps the IDE driver to automatically detect and configure all PCI-based IDE interfaces in your system. " } [359]=> array(11) { ["entry_id"]=> string(3) "360" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Generic PCI IDE Chipset Support" ["name"]=> string(15) "BLK_DEV_GENERIC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [360]=> array(11) { ["entry_id"]=> string(3) "361" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Sharing PCI IDE interrupts support" ["name"]=> string(16) "IDEPCI_SHARE_IRQ" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(238) " Some ATA/IDE chipsets have hardware support which allows for sharing a single IRQ with other cards. To enable support for this in the ATA/IDE driver, say Y here. It is safe to say Y to this question, in most cases. If unsure, say N. " } [361]=> array(11) { ["entry_id"]=> string(3) "362" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Generic PCI bus-master DMA support" ["name"]=> string(18) "BLK_DEV_IDEDMA_PCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(736) " If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and is capable of bus-master DMA operation (most Pentium PCI systems), you will want to say Y here to reduce CPU overhead. You can then use the "hdparm" utility to enable DMA for drives for which it was not enabled automatically. By default, DMA is not enabled automatically for these drives, but you can change that by saying Y to the following question "Use DMA by default when available". You can get the latest version of the hdparm utility from . Read the comments at the beginning of and the file for more information. It is safe to say Y to this question. " } [362]=> array(11) { ["entry_id"]=> string(3) "363" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "ATA tagged command queueing (EXPERIMENTAL)" ["name"]=> string(15) "BLK_DEV_IDE_TCQ" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(457) " Support for tagged command queueing on ATA disk drives. This enables the IDE layer to have multiple in-flight requests on hardware that supports it. For now this includes the IBM Deskstar series drives, such as the 22GXP, 75GXP, 40GV, 60GXP, and 120GXP (ie any Deskstar made in the last couple of years), and at least some of the Western Digital drives in the Expert series (by nature of really being IBM drives). If you have such a drive, say Y here. " } [363]=> array(11) { ["entry_id"]=> string(3) "364" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "TCQ on by default" ["name"]=> string(23) "BLK_DEV_IDE_TCQ_DEFAULT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(387) " Enable tagged command queueing unconditionally on drives that report support for it. Regardless of the chosen value here, tagging can be controlled at run time: echo "using_tcq:32" > /proc/ide/hdX/settings where any value between 1-32 selects chosen queue depth and enables TCQ, and 0 disables it. hdparm version 4.7 an above also support TCQ manipulations. Generally say Y here. " } [364]=> array(11) { ["entry_id"]=> string(3) "365" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(21) "BLK_DEV_IDE_TCQ_DEPTH" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> string(19) "Default queue depth" ["help_text"]=> NULL } [365]=> array(11) { ["entry_id"]=> string(3) "366" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Boot off-board chipsets first support" ["name"]=> string(16) "BLK_DEV_OFFBOARD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(906) " Normally, IDE controllers built into the motherboard (on-board controllers) are assigned to ide0 and ide1 while those on add-in PCI cards (off-board controllers) are relegated to ide2 and ide3. Answering Y here will allow you to reverse the situation, with off-board controllers on ide0/1 and on-board controllers on ide2/3. This can improve the usability of some boot managers such as lilo when booting from a drive on an off-board controller. If you say Y here, and you actually want to reverse the device scan order as explained above, you also need to issue the kernel command line option "ide=reverse". (Try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time.) Note that, if you do this, the order of the hd* devices will be rearranged which may require modification of fstab and other files. If in doubt, say N. " } [366]=> array(11) { ["entry_id"]=> string(3) "367" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Force enable legacy 2.0.X HOSTS to use DMA" ["name"]=> string(21) "BLK_DEV_IDEDMA_FORCED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(85) " This is an old piece of lost code from Linux 2.0 Kernels. Generally say N here. " } [367]=> array(11) { ["entry_id"]=> string(3) "368" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Use PCI DMA by default when available" ["name"]=> string(15) "IDEDMA_PCI_AUTO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(561) " Prior to kernel version 2.1.112, Linux used to automatically use DMA for IDE drives and chipsets which support it. Due to concerns about a couple of cases where buggy hardware may have caused damage, the default is now to NOT use DMA automatically. To revert to the previous behaviour, say Y to this question. If you suspect your hardware is at all flakey, say N here. Do NOT email the IDE kernel people regarding this issue! It is normally safe to answer Y to this question unless your motherboard uses a VIA VP2 chipset, in which case you should say N. " } [368]=> array(11) { ["entry_id"]=> string(3) "369" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Enable DMA only for disks " ["name"]=> string(15) "IDEDMA_ONLYDISK" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(104) " This is used if you know your ATAPI Devices are going to fail DMA Transfers. Generally say N here. " } [369]=> array(11) { ["entry_id"]=> string(3) "370" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "BLK_DEV_IDEDMA" ["name"]=> string(14) "BLK_DEV_IDEDMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [370]=> array(11) { ["entry_id"]=> string(3) "371" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "ATA Work(s) In Progress (EXPERIMENTAL)" ["name"]=> string(14) "IDEDMA_PCI_WIP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(191) " If you enable this you will be able to use and test highly developmental projects. If you say N, the configurator will simply skip those options. It is SAFEST to say N to this question. " } [371]=> array(11) { ["entry_id"]=> string(3) "372" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Good-Bad DMA Model-Firmware (WIP)" ["name"]=> string(25) "IDEDMA_NEW_DRIVE_LISTINGS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(246) " If you say Y here, the model and firmware revision of your drive will be compared against a blacklist of buggy drives that claim to be (U)DMA capable but aren't. This is a blanket on/off test with no speed limit options. If in doubt, say N. " } [372]=> array(11) { ["entry_id"]=> string(3) "373" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "BLK_DEV_ADMA" ["name"]=> string(12) "BLK_DEV_ADMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [373]=> array(11) { ["entry_id"]=> string(3) "374" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "AEC62XX chipset support" ["name"]=> string(15) "BLK_DEV_AEC62XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(196) " This driver adds explicit support for Acard AEC62xx (Artop ATP8xx) IDE controllers. This allows the kernel to change PIO, DMA and UDMA speeds and to configure the chip to optimum performance. " } [374]=> array(11) { ["entry_id"]=> string(3) "375" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ALI M15x3 chipset support" ["name"]=> string(15) "BLK_DEV_ALI15X3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(343) " This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C onboard chipsets. It also tests for Simplex mode and enables normal dual channel support. If you say Y here, you also need to say Y to "Use DMA by default when available", above. Please read the comments at the top of . If unsure, say N. " } [375]=> array(11) { ["entry_id"]=> string(3) "376" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "ALI M15x3 WDC support (DANGEROUS)" ["name"]=> string(11) "WDC_ALI15X3" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(403) " This allows for UltraDMA support for WDC drives that ignore CRC checking. You are a fool for enabling this option, but there have been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF YOU ENABLE THIS! No one will listen, just laugh for ignoring this SERIOUS WARNING. Using this option can allow WDC drives to run at ATA-4/5 transfer rates with only an ATA-2 support structure. SAY N! " } [376]=> array(11) { ["entry_id"]=> string(3) "377" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "AMD and nVidia IDE support" ["name"]=> string(15) "BLK_DEV_AMD74XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(215) " This driver adds explicit support for AMD-7xx and AMD-8111 chips and also for the nVidia nForce chip. This allows the kernel to change PIO, DMA and UDMA speeds and to configure the chip to optimum performance. " } [377]=> array(11) { ["entry_id"]=> string(3) "378" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "CMD64{3|6|8|9} chipset support" ["name"]=> string(14) "BLK_DEV_CMD64X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(106) " Say Y here if you have an IDE controller which uses any of these chipsets: CMD643, CMD646, or CMD648. " } [378]=> array(11) { ["entry_id"]=> string(3) "379" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Compaq Triflex IDE support" ["name"]=> string(15) "BLK_DEV_TRIFLEX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(119) " Say Y here if you have a Compaq Triflex IDE controller, such as those commonly found on Compaq Pentium-Pro systems " } [379]=> array(11) { ["entry_id"]=> string(3) "380" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "CY82C693 chipset support" ["name"]=> string(16) "BLK_DEV_CY82C693" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(195) " This driver adds detection and support for the CY82C693 chipset used on Digital's PC-Alpha 164SX boards. If you say Y here, you need to say Y to "Use DMA by default when available" as well. " } [380]=> array(11) { ["entry_id"]=> string(3) "381" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)" ["name"]=> string(14) "BLK_DEV_CS5520" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(191) " Include support for PIO tuning an virtual DMA on the Cyrix MediaGX 5510/5520 chipset. This will automatically be detected and configured if found. It is safe to say Y to this question. " } [381]=> array(11) { ["entry_id"]=> string(3) "382" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "Cyrix/National Semiconductor CS5530 MediaGX chipset support" ["name"]=> string(14) "BLK_DEV_CS5530" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(164) " Include support for UDMA on the Cyrix MediaGX 5530 chipset. This will automatically be detected and configured if found. It is safe to say Y to this question. " } [382]=> array(11) { ["entry_id"]=> string(3) "383" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "HPT34X chipset support" ["name"]=> string(14) "BLK_DEV_HPT34X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(371) " This driver adds up to 4 more EIDE devices sharing a single interrupt. The HPT343 chipset in its current form is a non-bootable controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX) PCI UDMA controllers. This driver requires dynamic tuning of the chipset during the ide-probe at boot time. It is reported to support DVD II drives, by the manufacturer. " } [383]=> array(11) { ["entry_id"]=> string(3) "384" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "HPT34X AUTODMA support (WIP)" ["name"]=> string(14) "HPT34X_AUTODMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(222) " This is a dangerous thing to attempt currently! Please read the comments at the top of . If you say Y here, then say Y to "Use DMA by default when available" as well. If unsure, say N. " } [384]=> array(11) { ["entry_id"]=> string(3) "385" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "HPT36X/37X chipset support" ["name"]=> string(14) "BLK_DEV_HPT366" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(880) " HPT366 is an Ultra DMA chipset for ATA-66. HPT368 is an Ultra DMA chipset for ATA-66 RAID Based. HPT370 is an Ultra DMA chipset for ATA-100. HPT372 is an Ultra DMA chipset for ATA-100. HPT374 is an Ultra DMA chipset for ATA-100. This driver adds up to 4 more EIDE devices sharing a single interrupt. The HPT366 chipset in its current form is bootable. One solution for this problem are special LILO commands for redirecting the reference to device 0x80. The other solution is to say Y to "Boot off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless your mother board has the chipset natively mounted. Regardless one should use the fore mentioned option and call at LILO or include "ide=reverse" in LILO's append-line. This driver requires dynamic tuning of the chipset during the ide-probe at boot. It is reported to support DVD II drives, by the manufacturer. " } [385]=> array(11) { ["entry_id"]=> string(3) "386" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "National SCx200 chipset support" ["name"]=> string(14) "BLK_DEV_SC1200" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(112) " This driver adds support for the built in IDE on the National SCx200 series of embedded x86 "Geode" systems " } [386]=> array(11) { ["entry_id"]=> string(3) "387" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Intel PIIXn chipsets support" ["name"]=> string(12) "BLK_DEV_PIIX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(225) " This driver adds explicit support for Intel PIIX and ICH chips and also for the Efar Victory66 (slc90e66) chip. This allows the kernel to change PIO, DMA and UDMA speeds and to configure the chip to optimum performance. " } [387]=> array(11) { ["entry_id"]=> string(3) "388" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "IT8172 IDE support" ["name"]=> string(14) "BLK_DEV_IT8172" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(253) " Say Y here to support the on-board IDE controller on the Integrated Technology Express, Inc. ITE8172 SBC. Vendor page at ; picture of the board at . " } [388]=> array(11) { ["entry_id"]=> string(3) "389" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "NS87415 chipset support" ["name"]=> string(15) "BLK_DEV_NS87415" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(171) " This driver adds detection and support for the NS87415 chip (used in SPARC64, among others). Please read the comments at the top of . " } [389]=> array(11) { ["entry_id"]=> string(3) "390" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)" ["name"]=> string(15) "BLK_DEV_OPTI621" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(131) " This is a driver for the OPTi 82C621 EIDE controller. Please read the comments at the top of . " } [390]=> array(11) { ["entry_id"]=> string(3) "391" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "PROMISE PDC202{46|62|65|67} support" ["name"]=> string(20) "BLK_DEV_PDC202XX_OLD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [391]=> array(11) { ["entry_id"]=> string(3) "392" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Special UDMA Feature" ["name"]=> string(14) "PDC202XX_BURST" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(491) " This option causes the pdc202xx driver to enable UDMA modes on the PDC202xx even when the PDC202xx BIOS has not done so. It was originally designed for the PDC20246/Ultra33, whose BIOS will only setup UDMA on the first two PDC20246 cards. It has also been used succesfully on a PDC20265/Ultra100, allowing use of UDMA modes when the PDC20265 BIOS has been disabled (for faster boot up). Please read the comments at the top of . If unsure, say N. " } [392]=> array(11) { ["entry_id"]=> string(3) "393" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "PROMISE PDC202{68|69|70|71|75|76|77} support" ["name"]=> string(20) "BLK_DEV_PDC202XX_NEW" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [393]=> array(11) { ["entry_id"]=> string(3) "394" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Special FastTrak Feature" ["name"]=> string(14) "PDC202XX_FORCE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(41) " For FastTrak enable overriding BIOS. " } [394]=> array(11) { ["entry_id"]=> string(3) "395" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "RZ1000 chipset bugfix/support" ["name"]=> string(14) "BLK_DEV_RZ1000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(434) " The PC-Technologies RZ1000 IDE chip is used on many common 486 and Pentium motherboards, usually along with the "Neptune" chipset. Unfortunately, it has a rather nasty design flaw that can cause severe data corruption under many conditions. Say Y here to include code which automatically detects and corrects the problem under Linux. This may slow disk throughput by a few percent, but at least things will operate 100% reliably. " } [395]=> array(11) { ["entry_id"]=> string(3) "396" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "ServerWorks OSB4/CSB5/CSB6 chipsets support" ["name"]=> string(13) "BLK_DEV_SVWKS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(80) " This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5 chipsets. " } [396]=> array(11) { ["entry_id"]=> string(3) "397" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Silicon Image chipset support" ["name"]=> string(15) "BLK_DEV_SIIMAGE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(91) " This driver adds PIO/(U)DMA support for the SI CMD680 and SII 3112 (Serial ATA) chips. " } [397]=> array(11) { ["entry_id"]=> string(3) "398" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "SiS5513 chipset support" ["name"]=> string(15) "BLK_DEV_SIS5513" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(469) " This driver ensures (U)DMA support for SIS5513 chipset family based mainboards. The following chipsets are supported: ATA16: SiS5511, SiS5513 ATA33: SiS5591, SiS5597, SiS5598, SiS5600 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740, SiS745, SiS750 If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of . " } [398]=> array(11) { ["entry_id"]=> string(3) "399" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "SLC90E66 chipset support" ["name"]=> string(16) "BLK_DEV_SLC90E66" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(471) " This driver ensures (U)DMA support for Victroy66 SouthBridges for SMsC with Intel NorthBridges. This is an Ultra66 based chipset. The nice thing about it is that you can mix Ultra/DMA/PIO devices and it will handle timing cycles. Since this is an improved look-a-like to the PIIX4 it should be a nice addition. If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of drivers/ide/pci/slc90e66.c. " } [399]=> array(11) { ["entry_id"]=> string(3) "400" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Tekram TRM290 chipset support" ["name"]=> string(14) "BLK_DEV_TRM290" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(228) " This driver adds support for bus master DMA transfers using the Tekram TRM290 PCI IDE chip. Volunteers are needed for further tweaking and development. Please read the comments at the top of . " } [400]=> array(11) { ["entry_id"]=> string(3) "401" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "VIA82CXXX chipset support" ["name"]=> string(17) "BLK_DEV_VIA82CXXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(178) " This driver adds explicit support for VIA BusMastering IDE chips. This allows the kernel to change PIO, DMA and UDMA speeds and to configure the chip to optimum performance. " } [401]=> array(11) { ["entry_id"]=> string(3) "402" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Winbond SL82c105 support" ["name"]=> string(16) "BLK_DEV_SL82C105" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(203) " If you have a Winbond SL82c105 IDE controller, say Y here to enable special configuration for this chip. This is common on various CHRP motherboards, but could be used elsewhere. If in doubt, say Y. " } [402]=> array(11) { ["entry_id"]=> string(3) "403" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Builtin PowerMac IDE support" ["name"]=> string(16) "BLK_DEV_IDE_PMAC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " This driver provides support for the built-in IDE controller on most of the recent Apple Power Macintoshes and PowerBooks. If unsure, say Y. " } [403]=> array(11) { ["entry_id"]=> string(3) "404" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "PowerMac IDE DMA support" ["name"]=> string(19) "BLK_DEV_IDEDMA_PMAC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(217) " This option allows the driver for the built-in IDE controller on Power Macintoshes and PowerBooks to use DMA (direct memory access) to transfer data to and from memory. Saying Y is safe and improves performance. " } [404]=> array(11) { ["entry_id"]=> string(3) "405" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Use DMA by default" ["name"]=> string(24) "BLK_DEV_IDEDMA_PMAC_AUTO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(350) " This option allows the driver for the built-in IDE controller on Power Macintoshes and PowerBooks to use DMA automatically, without it having to be explicitly enabled. This option is provided because of concerns about a couple of cases where using DMA on buggy PC hardware may have caused damage. Saying Y should be safe on all Apple machines. " } [405]=> array(11) { ["entry_id"]=> string(3) "406" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "SWARM onboard IDE support" ["name"]=> string(17) "BLK_DEV_IDE_SWARM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [406]=> array(11) { ["entry_id"]=> string(3) "407" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ICS IDE interface support" ["name"]=> string(18) "BLK_DEV_IDE_ICSIDE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(163) " On Acorn systems, say Y here if you wish to use the ICS IDE interface card. This is not required for ICS partition support. If you are unsure, say N to this. " } [407]=> array(11) { ["entry_id"]=> string(3) "408" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "ICS DMA support" ["name"]=> string(18) "BLK_DEV_IDEDMA_ICS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(92) " Say Y here if you want to add DMA (Direct Memory Access) support to the ICS IDE driver. " } [408]=> array(11) { ["entry_id"]=> string(3) "409" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Use ICS DMA by default" ["name"]=> string(15) "IDEDMA_ICS_AUTO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(431) " Prior to kernel version 2.1.112, Linux used to automatically use DMA for IDE drives and chipsets which support it. Due to concerns about a couple of cases where buggy hardware may have caused damage, the default is now to NOT use DMA automatically. To revert to the previous behaviour, say Y to this question. If you suspect your hardware is at all flakey, say N here. Do NOT email the IDE kernel people regarding this issue! " } [409]=> array(11) { ["entry_id"]=> string(3) "410" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "RapIDE interface support" ["name"]=> string(18) "BLK_DEV_IDE_RAPIDE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(115) " Say Y here if you want to support the Yellowstone RapIDE controller manufactured for use with Acorn computers. " } [410]=> array(11) { ["entry_id"]=> string(3) "411" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Amiga Gayle IDE interface support" ["name"]=> string(13) "BLK_DEV_GAYLE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(361) " This is the IDE driver for the builtin IDE interface on some Amiga models. It supports both the `A1200 style' (used in A600 and A1200) and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE interface. Say Y if you have such an Amiga model and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. " } [411]=> array(11) { ["entry_id"]=> string(3) "412" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Amiga IDE Doubler support (EXPERIMENTAL)" ["name"]=> string(18) "BLK_DEV_IDEDOUBLER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(552) " This driver provides support for the so-called `IDE doublers' (made by various manufacturers, e.g. Eyetech) that can be connected to the builtin IDE interface of some Amiga models. Using such an IDE doubler, you can connect up to four instead of two IDE devices on the Amiga's builtin IDE interface. Note that the normal Amiga Gayle IDE driver may not work correctly if you have an IDE doubler and don't enable this driver! Say Y if you have an IDE doubler. The driver is enabled at kernel runtime using the "ide=doubler" kernel boot parameter. " } [412]=> array(11) { ["entry_id"]=> string(3) "413" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(60) "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)" ["name"]=> string(14) "BLK_DEV_BUDDHA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(369) " This is the IDE driver for the IDE interfaces on the Buddha, Catweasel and X-Surf expansion boards. It supports up to two interfaces on the Buddha, three on the Catweasel and two on the X-Surf. Say Y if you have a Buddha or Catweasel expansion board and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to one of its IDE interfaces. " } [413]=> array(11) { ["entry_id"]=> string(3) "414" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Falcon IDE interface support" ["name"]=> string(18) "BLK_DEV_FALCON_IDE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(216) " This is the IDE driver for the builtin IDE interface on the Atari Falcon. Say Y if you have a Falcon and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. " } [414]=> array(11) { ["entry_id"]=> string(3) "415" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Macintosh Quadra/Powerbook IDE interface support" ["name"]=> string(15) "BLK_DEV_MAC_IDE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(412) " This is the IDE driver for the builtin IDE interface on some m68k Macintosh models. It supports both the `Quadra style' (used in Quadra/ Centris 630 and Performa 588 models) and `Powerbook style' (used in the Powerbook 150 and 190 models) IDE interface. Say Y if you have such an Macintosh model and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. " } [415]=> array(11) { ["entry_id"]=> string(3) "416" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Q40/Q60 IDE interface support" ["name"]=> string(14) "BLK_DEV_Q40IDE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(176) " Enable the on-board IDE controller in the Q40/Q60. This should normally be on; disable it only if you are running a custom hard drive subsystem through an expansion card. " } [416]=> array(11) { ["entry_id"]=> string(3) "417" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "MPC8xx IDE support" ["name"]=> string(18) "BLK_DEV_MPC8xx_IDE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(143) " This option provides support for IDE on Motorola MPC8xx Systems. Please see 'Type of MPC8xx IDE interface' for details. If unsure, say N. " } [417]=> array(11) { ["entry_id"]=> string(3) "418" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "IDE_8xx_PCCARD" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(10) "8xx_PCCARD" ["help_text"]=> NULL } [418]=> array(11) { ["entry_id"]=> string(3) "419" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "IDE_8xx_DIRECT" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(10) "8xx_DIRECT" ["help_text"]=> NULL } [419]=> array(11) { ["entry_id"]=> string(3) "420" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "IDE_EXT_DIRECT" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(10) "EXT_DIRECT" ["help_text"]=> NULL } [420]=> array(11) { ["entry_id"]=> string(3) "421" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Other IDE chipset support" ["name"]=> string(12) "IDE_CHIPSETS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(636) " Say Y here if you want to include enhanced support for various IDE interface chipsets used on motherboards and add-on cards. You can then pick your particular IDE chip from among the following options. This enhanced support may be necessary for Linux to be able to access the 3rd/4th drives in some systems. It may also enable setting of higher speed I/O rates to improve system performance with these chipsets. Most of these also require special kernel boot parameters to actually turn on the support at runtime; you can find a list of these in the file . People with SCSI-only systems can say N here. " } [421]=> array(11) { ["entry_id"]=> string(3) "422" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Generic 4 drives/port support" ["name"]=> string(15) "BLK_DEV_4DRIVES" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(277) " Certain older chipsets, including the Tekram 690CD, use a single set of I/O ports at 0x1f0 to control up to four drives, instead of the customary two drives per port. Support for this can be enabled at runtime using the "ide0=four" kernel boot parameter if you say Y here. " } [422]=> array(11) { ["entry_id"]=> string(3) "423" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "ALI M14xx support" ["name"]=> string(15) "BLK_DEV_ALI14XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(333) " This driver is enabled at runtime using the "ide0=ali14xx" kernel boot parameter. It enables support for the secondary IDE interface of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster I/O speeds to be set as well. See the files and for more info. " } [423]=> array(11) { ["entry_id"]=> string(3) "424" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "DTC-2278 support" ["name"]=> string(15) "BLK_DEV_DTC2278" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(306) " This driver is enabled at runtime using the "ide0=dtc2278" kernel boot parameter. It enables support for the secondary IDE interface of the DTC-2278 card, and permits faster I/O speeds to be set as well. See the and files for more info. " } [424]=> array(11) { ["entry_id"]=> string(3) "425" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Holtek HT6560B support" ["name"]=> string(15) "BLK_DEV_HT6560B" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(304) " This driver is enabled at runtime using the "ide0=ht6560b" kernel boot parameter. It enables support for the secondary IDE interface of the Holtek card, and permits faster I/O speeds to be set as well. See the and files for more info. " } [425]=> array(11) { ["entry_id"]=> string(3) "426" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "PROMISE DC4030 support (EXPERIMENTAL)" ["name"]=> string(15) "BLK_DEV_PDC4030" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(519) " This driver provides support for the secondary IDE interface and cache of the original Promise IDE chipsets, e.g. DC4030 and DC5030. It is nothing to do with the later range of Promise UDMA chipsets - see the PDC_202XX support for these. CD-ROM and TAPE devices are not supported (and probably never will be since I don't think the cards support them). This driver is enabled at runtime using the "ide0=dc4030" or "ide1=dc4030" kernel boot parameter. See the file for more info. " } [426]=> array(11) { ["entry_id"]=> string(3) "427" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "QDI QD65xx support" ["name"]=> string(14) "BLK_DEV_QD65XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(218) " This driver is enabled at runtime using the "ide0=qd65xx" kernel boot parameter. It permits faster I/O speeds to be set. See the and for more info. " } [427]=> array(11) { ["entry_id"]=> string(3) "428" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "UMC-8672 support" ["name"]=> string(15) "BLK_DEV_UMC8672" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(301) " This driver is enabled at runtime using the "ide0=umc8672" kernel boot parameter. It enables support for the secondary IDE interface of the UMC-8672, and permits faster I/O speeds to be set as well. See the files and for more info. " } [428]=> array(11) { ["entry_id"]=> string(3) "429" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Old hard disk (MFM/RLL/IDE) driver" ["name"]=> string(15) "BLK_DEV_HD_ONLY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(789) " There are two drivers for MFM/RLL/IDE hard disks. Most people use the newer enhanced driver, but this old one is still around for two reasons. Some older systems have strange timing problems and seem to work only with the old driver (which itself does not work with some newer systems). The other reason is that the old driver is smaller, since it lacks the enhanced functionality of the new one. This makes it a good choice for systems with very tight memory restrictions, or for systems with only older MFM/RLL/ESDI drives. Choosing the old driver can save 13 KB or so of kernel memory. If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver instead of this one. For more detailed information, read the Disk-HOWTO, available from . " } [429]=> array(11) { ["entry_id"]=> string(3) "430" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "IDEDMA_AUTO" ["name"]=> string(11) "IDEDMA_AUTO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [430]=> array(11) { ["entry_id"]=> string(3) "431" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "IGNORE word93 Validation BITS" ["name"]=> string(10) "IDEDMA_IVB" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(560) " There are unclear terms in ATA-4 and ATA-5 standards how certain hardware (an 80c ribbon) should be detected. Different interpretations of the standards have been released in hardware. This causes problems: for example, a host with Ultra Mode 4 (or higher) will not run in that mode with an 80c ribbon. If you are experiencing compatibility or performance problems, you MAY try to answering Y here. However, it does not necessarily solve any of your problems, it could even cause more of them. It is normally safe to answer Y; however, the default is N. " } [431]=> array(11) { ["entry_id"]=> string(3) "432" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "DMA_NONPCI" ["name"]=> string(10) "DMA_NONPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [432]=> array(11) { ["entry_id"]=> string(3) "433" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "BLK_DEV_PDC202XX" ["name"]=> string(16) "BLK_DEV_PDC202XX" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(776) " Promise Ultra33 or PDC20246 Promise Ultra66 or PDC20262 Promise Ultra100 or PDC20265/PDC20267/PDC20268 This driver adds up to 4 more EIDE devices sharing a single interrupt. This add-on card is a bootable PCI UDMA controller. Since multiple cards can be installed and there are BIOS ROM problems that happen if the BIOS revisions of all installed cards (three-max) do not match, the driver attempts to do dynamic tuning of the chipset at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required for more than one card. This card may require that you say Y to "Special UDMA Feature". If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of . If unsure, say N. " } [433]=> array(11) { ["entry_id"]=> string(3) "434" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "BLK_DEV_IDE_MODES" ["name"]=> string(17) "BLK_DEV_IDE_MODES" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [434]=> array(11) { ["entry_id"]=> string(3) "435" ["entry_type"]=> string(4) "MENU" ["text"]=> string(43) "IEEE 1394 (FireWire) support (EXPERIMENTAL)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [435]=> array(11) { ["entry_id"]=> string(3) "436" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "IEEE 1394 (FireWire) support (EXPERIMENTAL)" ["name"]=> string(8) "IEEE1394" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(591) " IEEE 1394 describes a high performance serial bus, which is also known as FireWire(tm) or i.Link(tm) and is used for connecting all sorts of devices (most notably digital video cameras) to your computer. If you have FireWire hardware and want to use it, say Y here. This is the core support only, you will also need to select a driver for your IEEE 1394 adapter. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ieee1394. " } [436]=> array(11) { ["entry_id"]=> string(3) "437" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Excessive debugging output" ["name"]=> string(21) "IEEE1394_VERBOSEDEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(372) " If you say Y here, you will get very verbose debugging logs from the subsystem which includes a dump of the header of every sent and received packet. This can amount to a high amount of data collected in a very short time which is usually also saved to disk by the system logging daemons. Say Y if you really want or need the debugging output, everyone else says N. " } [437]=> array(11) { ["entry_id"]=> string(3) "438" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "OUI Database built-in" ["name"]=> string(15) "IEEE1394_OUI_DB" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(441) " If you say Y here, then an OUI list (vendor unique ID's) will be compiled into the ieee1394 module. This doesn't really do much accept being able to display the vendor of a hardware node. The downside is that it adds about 300k to the size of the module, or kernel (depending on whether you compile ieee1394 as a module, or static in the kernel). This option is not needed for userspace programs like gscanbus to show this information. " } [438]=> array(11) { ["entry_id"]=> string(3) "439" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Texas Instruments PCILynx support" ["name"]=> string(16) "IEEE1394_PCILYNX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(405) " Say Y here if you have an IEEE-1394 controller with the Texas Instruments PCILynx chip. Note: this driver is written for revision 2 of this chip and may not work with revision 0. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called pcilynx. " } [439]=> array(11) { ["entry_id"]=> string(3) "440" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "OHCI-1394 support" ["name"]=> string(17) "IEEE1394_OHCI1394" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(519) " Enable this driver if you have an IEEE 1394 controller based on the OHCI-1394 specification. The current driver is only tested with OHCI chipsets made by Texas Instruments and NEC. Most third-party vendors use one of these chipsets. It should work with any OHCI-1394 compliant card, however. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ohci1394. " } [440]=> array(11) { ["entry_id"]=> string(3) "441" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "OHCI-1394 Video support" ["name"]=> string(18) "IEEE1394_VIDEO1394" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(159) " This option enables video device usage for OHCI-1394 cards. Enable this option only if you have an IEEE 1394 video device connected to an OHCI-1394 card. " } [441]=> array(11) { ["entry_id"]=> string(3) "442" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "SBP-2 support (Harddisks etc.)" ["name"]=> string(13) "IEEE1394_SBP2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(133) " This option enables you to use SBP-2 devices connected to your IEEE 1394 bus. SBP-2 devices include harddrives and DVD devices. " } [442]=> array(11) { ["entry_id"]=> string(3) "443" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Enable Phys DMA support for SBP2 (Debug)" ["name"]=> string(22) "IEEE1394_SBP2_PHYS_DMA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [443]=> array(11) { ["entry_id"]=> string(3) "444" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Ethernet over 1394" ["name"]=> string(16) "IEEE1394_ETH1394" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(140) " Extremely Experimental! This driver is a Linux specific way to use your IEEE1394 Host as an Ethernet type device. This is _NOT_ IP1394. " } [444]=> array(11) { ["entry_id"]=> string(3) "445" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "OHCI-DV I/O support" ["name"]=> string(15) "IEEE1394_DV1394" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(418) " This driver allows you to transmit and receive DV (digital video) streams on an OHCI-1394 card using a simple frame-oriented interface. The user-space API for dv1394 is documented in dv1394.h. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called dv1394. " } [445]=> array(11) { ["entry_id"]=> string(3) "446" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Raw IEEE1394 I/O support" ["name"]=> string(14) "IEEE1394_RAWIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(457) " Say Y here if you want support for the raw device. This is generally a good idea, so you should say Y here. The raw device enables direct communication of user programs with the IEEE 1394 bus and thus with the attached peripherals. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called raw1394. " } [446]=> array(11) { ["entry_id"]=> string(3) "447" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "IEC61883-1 Plug support" ["name"]=> string(12) "IEEE1394_CMP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(342) " This option enables the Connection Management Procedures (IEC61883-1) driver, which implements input and output plugs. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called amdtp. " } [447]=> array(11) { ["entry_id"]=> string(3) "448" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "IEC61883-6 (Audio transmission) support" ["name"]=> string(14) "IEEE1394_AMDTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(411) " This option enables the Audio & Music Data Transmission Protocol (IEC61883-6) driver, which implements audio transmission over IEEE1394. The userspace interface is documented in amdtp.h. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called amdtp. " } [448]=> array(11) { ["entry_id"]=> string(3) "449" ["entry_type"]=> string(4) "MENU" ["text"]=> string(18) "I2O device support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [449]=> array(11) { ["entry_id"]=> string(3) "450" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "I2O support" ["name"]=> string(3) "I2O" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1030) " The Intelligent Input/Output (I2O) architecture allows hardware drivers to be split into two parts: an operating system specific module called the OSM and an hardware specific module called the HDM. The OSM can talk to a whole range of HDM's, and ideally the HDM's are not OS dependent. This allows for the same HDM driver to be used under different operating systems if the relevant OSM is in place. In order for this to work, you need to have an I2O interface adapter card in your computer. This card contains a special I/O processor (IOP), thus allowing high speeds since the CPU does not have to deal with I/O. If you say Y here, you will get a choice of interface adapter drivers and OSM's with the following questions. This support is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . You will get modules called i2o_core and i2o_config. If unsure, say N. " } [450]=> array(11) { ["entry_id"]=> string(3) "451" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "I2O PCI support" ["name"]=> string(7) "I2O_PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(366) " Say Y for support of PCI bus I2O interface adapters. Currently this is the only variety supported, so you should say Y. This support is also available as a module called i2o_pci ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [451]=> array(11) { ["entry_id"]=> string(3) "452" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "I2O Block OSM" ["name"]=> string(9) "I2O_BLOCK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(375) " Include support for the I2O Block OSM. The Block OSM presents disk and other structured block devices to the operating system. This support is also available as a module called i2o_block ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [452]=> array(11) { ["entry_id"]=> string(3) "453" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "I2O SCSI OSM" ["name"]=> string(8) "I2O_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(393) " Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel I2O controller. You can use both the SCSI and Block OSM together if you wish. This support is also available as a module called i2o_scsi ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [453]=> array(11) { ["entry_id"]=> string(3) "454" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "I2O /proc support" ["name"]=> string(8) "I2O_PROC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(388) " If you say Y here and to "/proc file system support", you will be able to read I2O related information from the virtual directory /proc/i2o. This support is also available as a module called i2o_proc ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [454]=> array(11) { ["entry_id"]=> string(3) "455" ["entry_type"]=> string(4) "MENU" ["text"]=> string(35) "Multi-device support (RAID and LVM)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [455]=> array(11) { ["entry_id"]=> string(3) "456" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(46) "Multiple devices driver support (RAID and LVM)" ["name"]=> string(2) "MD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(121) " Support multiple physical spindles through a single logical device. Required for RAID and logical volume management. " } [456]=> array(11) { ["entry_id"]=> string(3) "457" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "RAID support" ["name"]=> string(10) "BLK_DEV_MD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(761) " This driver lets you combine several hard disk partitions into one logical block device. This can be used to simply append one partition to another one or to combine several redundant hard disks into a RAID1/4/5 device so as to provide protection against hard disk failures. This is called "Software RAID" since the combining of the partitions is done by the kernel. "Hardware RAID" means that the combining is done by a dedicated controller; if you have such a controller, you do not need to say Y here. More information about Software RAID on Linux is contained in the Software RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If unsure, say N. " } [457]=> array(11) { ["entry_id"]=> string(3) "458" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Linear (append) mode" ["name"]=> string(9) "MD_LINEAR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(427) " If you say Y here, then your multiple devices driver will be able to use the so-called linear mode, i.e. it will combine the hard disk partitions by simply appending one to the other. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called linear. If unsure, say Y. " } [458]=> array(11) { ["entry_id"]=> string(3) "459" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "RAID-0 (striping) mode" ["name"]=> string(8) "MD_RAID0" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(803) " If you say Y here, then your multiple devices driver will be able to use the so-called raid0 mode, i.e. it will combine the hard disk partitions into one logical device in such a fashion as to fill them up evenly, one chunk here and one chunk there. This will increase the throughput rate if the partitions reside on distinct disks. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called raid0. If unsure, say Y. " } [459]=> array(11) { ["entry_id"]=> string(3) "460" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "RAID-1 (mirroring) mode" ["name"]=> string(8) "MD_RAID1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(945) " A RAID-1 set consists of several disk drives which are exact copies of each other. In the event of a mirror failure, the RAID driver will continue to use the operational mirrors in the set, providing an error free MD (multiple device) to the higher levels of the kernel. In a set with N drives, the available space is the capacity of a single drive, and the set protects against a failure of (N - 1) drives. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to use such a RAID-1 set, say Y. This code is also available as a module called raid1 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . If unsure, say Y. " } [460]=> array(11) { ["entry_id"]=> string(3) "461" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "RAID-4/RAID-5 mode" ["name"]=> string(8) "MD_RAID5" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(986) " A RAID-5 set of N drives with a capacity of C MB per drive provides the capacity of C * (N - 1) MB, and protects against a failure of a single drive. For a given sector (row) number, (N - 1) drives contain data sectors, and one drive contains the parity protection. For a RAID-4 set, the parity blocks are present on a single drive, while a RAID-5 set distributes the parity across the drives in one of the available parity distribution methods. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to use such a RAID-4/RAID-5 set, say Y. This code is also available as a module called raid5 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . If unsure, say Y. " } [461]=> array(11) { ["entry_id"]=> string(3) "462" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Multipath I/O support" ["name"]=> string(12) "MD_MULTIPATH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(316) " Multipath-IO is the ability of certain devices to address the same physical disk over multiple 'IO paths'. The code ensures that such paths can be defined and handled at runtime, and ensures that a transparent failover to the backup path(s) happens if a IO errors arrives on the primary path. If unsure, say N. " } [462]=> array(11) { ["entry_id"]=> string(3) "463" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Device mapper support" ["name"]=> string(10) "BLK_DEV_DM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(466) " Device-mapper is a low level volume manager. It works by allowing people to specify mappings for ranges of logical sectors. Various mapping types are available, in addition people may write their own modules containing custom mappings if they wish. Higher level volume managers such as LVM2 use this driver. If you want to compile this as a module, say M here and read . The module will be called dm-mod. If unsure, say N. " } [463]=> array(11) { ["entry_id"]=> string(3) "464" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ioctl interface version 4" ["name"]=> string(11) "DM_IOCTL_V4" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(115) " Recent tools use a new version of the ioctl interface, only select this option if you intend using such tools. " } [464]=> array(11) { ["entry_id"]=> string(3) "465" ["entry_type"]=> string(4) "MENU" ["text"]=> string(25) "Fusion MPT device support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [465]=> array(11) { ["entry_id"]=> string(3) "466" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Fusion MPT (base + ScsiHost) drivers" ["name"]=> string(6) "FUSION" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1751) " LSI Logic Fusion(TM) Message Passing Technology (MPT) device support provides high performance SCSI host initiator, and LAN [1] interface services to a host system. The Fusion architecture is capable of duplexing these protocols on high-speed Fibre Channel (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320) physical medium. [1] LAN is not supported on parallel SCSI medium. These drivers require a Fusion MPT compatible PCI adapter installed in the host system. MPT adapters contain specialized I/O processors to handle I/O workload, and more importantly to offload this work from the host CPU(s). If you have Fusion MPT hardware and want to use it, you can say Y or M here to add MPT (base + ScsiHost) drivers. = build lib (fusion), and link [static] into the kernel [2] proper = compiled as [dynamic] modules [3] named: (mptbase, mptscsih) [2] In order enable capability to boot the linux kernel natively from a Fusion MPT target device, you MUST answer Y here! (currently requires CONFIG_BLK_DEV_SD) [3] This support is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile as modules, say M here and read . If unsure, say N. If you say Y or M here you will get a choice of these additional protocol and support module options: Module Name: Enhanced SCSI error reporting (isense) Fusion MPT misc device (ioctl) driver (mptctl) Fusion MPT LAN driver (mptlan) --- Fusion MPT is trademark of LSI Logic Corporation, and its architecture is based on LSI Logic's Message Passing Interface (MPI) specification. " } [466]=> array(11) { ["entry_id"]=> string(3) "467" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "FUSION_BOOT" ["name"]=> string(11) "FUSION_BOOT" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [467]=> array(11) { ["entry_id"]=> string(3) "468" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(14) "FUSION_MAX_SGE" ["value"]=> string(2) "40" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(40) "Maximum number of scatter gather entries" ["help_text"]=> NULL } [468]=> array(11) { ["entry_id"]=> string(3) "469" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Enhanced SCSI error reporting" ["name"]=> string(13) "FUSION_ISENSE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1173) " The isense module (roughly stands for Interpret SENSE data) is completely optional. It simply provides extra English readable strings in SCSI Error Report(s) that might be generated from the Fusion MPT SCSI Host driver, for example when a target device returns a SCSI check condition on a I/O. Without this module loaded you might see: SCSI Error Report =-=-= (ioc0,scsi5:0) SCSI_Status=02h (CHECK_CONDITION) Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00 SenseKey=2h (NOT READY); FRU=02h ASC/ASCQ=29h/00h Where otherwise, if this module had been loaded, you would see: SCSI Error Report =-=-= (ioc0,scsi5:0) SCSI_Status=02h (CHECK_CONDITION) Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)" SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00 SenseKey=2h (NOT READY); FRU=02h ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED" Say M for "Enhanced SCSI error reporting" to compile this optional module, creating a driver named: isense. NOTE: Support for building this feature into the kernel is not available, due to kernel size considerations. " } [469]=> array(11) { ["entry_id"]=> string(3) "470" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Fusion MPT misc device (ioctl) driver" ["name"]=> string(10) "FUSION_CTL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(550) " The Fusion MPT misc device driver provides specialized control of MPT adapters via system ioctl calls. Use of ioctl calls to the MPT driver requires that you create and use a misc device node ala: mknod /dev/mptctl c 10 240 One use of this ioctl interface is to perform an upgrade (reflash) of the MPT adapter firmware. Refer to readme file(s) distributed with the Fusion MPT linux driver for additional details. If enabled by saying M to this, a driver named: mptctl will be compiled. If unsure whether you really want or need this, say N. " } [470]=> array(11) { ["entry_id"]=> string(3) "471" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Fusion MPT LAN driver" ["name"]=> string(10) "FUSION_LAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(725) " This module supports LAN IP traffic over Fibre Channel port(s) on Fusion MPT compatible hardware (LSIFC9xx chips). The physical interface used is defined in RFC 2625. Please refer to that document for details. Installing this driver requires the knowledge to configure and activate a new network interface, "fc0", using standard Linux tools. If enabled by saying M to this, a driver named: mptlan will be compiled. If unsure whether you really want or need this, say N. NOTES: This feature is NOT available nor supported for linux-2.2.x kernels. You must be building a linux-2.3.x or linux-2.4.x kernel in order to configure this option. Support for building this feature into the linux kernel is not yet available. " } [471]=> array(11) { ["entry_id"]=> string(3) "472" ["entry_type"]=> string(4) "MENU" ["text"]=> string(19) "SCSI device support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [472]=> array(11) { ["entry_id"]=> string(3) "473" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "SCSI device support" ["name"]=> string(4) "SCSI" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(987) " If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or any other SCSI device under Linux, say Y and make sure that you know the name of your SCSI host adapter (the card inside your computer that "speaks" the SCSI protocol, also called SCSI controller), because you will be asked for it. You also need to say Y here if you have a device which speaks the SCSI protocol. Examples of this include the parallel port version of the IOMEGA ZIP drive, USB storage devices, Fibre Channel, FireWire storage and the IDE-SCSI emulation driver. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called scsi_mod. If you want to compile it as a module, say M here and read and . However, do not compile this as a module if your root file system (the one containing the directory /) is located on a SCSI device. " } [473]=> array(11) { ["entry_id"]=> string(3) "474" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SCSI disk support" ["name"]=> string(10) "BLK_DEV_SD" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(815) " If you want to use SCSI hard disks, Fibre Channel disks, USB storage or the SCSI or parallel port version of the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from . This is NOT for SCSI CD-ROMs. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called sd_mod. If you want to compile it as a module, say M here and read and . Do not compile this driver as a module if your root file system (the one containing the directory /) is located on a SCSI disk. In this case, do not compile the driver for your SCSI host adapter (below) as a module either. " } [474]=> array(11) { ["entry_id"]=> string(3) "475" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SCSI tape support" ["name"]=> string(10) "CHR_DEV_ST" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(524) " If you want to use a SCSI tape drive under Linux, say Y and read the SCSI-HOWTO, available from , and in the kernel source. This is NOT for SCSI CD-ROMs. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called st. If you want to compile it as a module, say M here and read and . " } [475]=> array(11) { ["entry_id"]=> string(3) "476" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "SCSI OnStream SC-x0 tape support" ["name"]=> string(12) "CHR_DEV_OSST" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1090) " The OnStream SC-x0 SCSI tape drives can not be driven by the standard st driver, but instead need this special osst driver and use the /dev/osstX char device nodes (major 206). Via usb-storage and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives as well. Note that there is also a second generation of OnStream tape drives (ADR-x0) that supports the standard SCSI-2 commands for tapes (QIC-157) and can be driven by the standard driver st. For more information, you may have a look at the SCSI-HOWTO and in the kernel source. More info on the OnStream driver may be found on Please also have a look at the standard st docu, as most of it applies to osst as well. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called osst. If you want to compile it as a module, say M here and read and . " } [476]=> array(11) { ["entry_id"]=> string(3) "477" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "SCSI CDROM support" ["name"]=> string(10) "BLK_DEV_SR" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(530) " If you want to use a SCSI or FireWire CD-ROM under Linux, say Y and read the SCSI-HOWTO and the CDROM-HOWTO at . Also make sure to say Y or M to "ISO 9660 CD-ROM file system support" later. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called sr_mod. If you want to compile it as a module, say M here and read and . " } [477]=> array(11) { ["entry_id"]=> string(3) "478" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(50) "Enable vendor-specific extensions (for SCSI CDROM)" ["name"]=> string(17) "BLK_DEV_SR_VENDOR" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(257) " This enables the usage of vendor specific SCSI commands. This is required to support multisession CDs with old NEC/TOSHIBA cdrom drives (and HP Writers). If you have such a drive and get the first session only, try saying Y here; everybody else says N. " } [478]=> array(11) { ["entry_id"]=> string(3) "479" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "SCSI generic support" ["name"]=> string(10) "CHR_DEV_SG" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1131) " If you want to use SCSI scanners, synthesizers or CD-writers or just about anything having "SCSI" in its name other than hard disks, CD-ROMs or tapes, say Y here. These won't be supported by the kernel directly, so you need some additional software which knows how to talk to these devices using the SCSI protocol: For scanners, look at SANE (). For CD writer software look at Cdrtools () and for burning a "disk at once": CDRDAO (). Cdparanoia is a high quality digital reader of audio CDs (). For other devices, it's possible that you'll have to write the driver software yourself. Please read the file for more information. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read and . The module will be called sg. If unsure, say N. " } [479]=> array(11) { ["entry_id"]=> string(3) "480" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Probe all LUNs on each SCSI device" ["name"]=> string(14) "SCSI_MULTI_LUN" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(416) " If you have a SCSI device that supports more than one LUN (Logical Unit Number), e.g. a CD jukebox, and only one LUN is detected, you can say Y here to force the SCSI driver to probe for multiple LUNs. A SCSI device with multiple LUNs acts logically like multiple SCSI devices. The vast majority of SCSI devices have only one LUN, and so most people can say N here and should in fact do so, because it is safer. " } [480]=> array(11) { ["entry_id"]=> string(3) "481" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Build with SCSI REPORT LUNS support" ["name"]=> string(16) "SCSI_REPORT_LUNS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(299) " If you want support for SCSI REPORT LUNS, say Y here. The REPORT LUNS command is useful for devices (such as disk arrays) with large numbers of LUNs where the LUN values are not contiguous (sparse LUN). REPORT LUNS scanning is done only for SCSI-3 devices. Most users can safely answer N here. " } [481]=> array(11) { ["entry_id"]=> string(3) "482" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Verbose SCSI error reporting (kernel size +=12K)" ["name"]=> string(14) "SCSI_CONSTANTS" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(164) " The error messages regarding your SCSI hardware will be easier to understand if you say Y here; it will enlarge your kernel by about 12 KB. If in doubt, say Y. " } [482]=> array(11) { ["entry_id"]=> string(3) "483" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "SCSI logging facility" ["name"]=> string(12) "SCSI_LOGGING" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(867) " This turns on a logging facility that can be used to debug a number of SCSI related problems. If you say Y here, no logging output will appear by default, but you can enable logging by saying Y to "/proc file system support" and "Sysctl support" below and executing the command echo "scsi log token [level]" > /proc/scsi/scsi at boot time after the /proc file system has been mounted. There are a number of things that can be used for 'token' (you can find them in the source: ), and this allows you to select the types of information you want, and the level allows you to select the level of verbosity. If you say N here, it may be harder to track down some types of SCSI problems. If you say Y here your kernel will be somewhat larger, but there should be no noticeable performance impact as long as you have logging turned off. " } [483]=> array(11) { ["entry_id"]=> string(3) "484" ["entry_type"]=> string(4) "MENU" ["text"]=> string(22) "SCSI low-level drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [484]=> array(11) { ["entry_id"]=> string(3) "485" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "SGI WD93C93 SCSI Driver" ["name"]=> string(12) "SGIWD93_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(104) " If you have a Western Digital WD93 SCSI controller on an SGI MIPS system, say Y. Otherwise, say N. " } [485]=> array(11) { ["entry_id"]=> string(3) "486" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "DEC NCR53C94 Scsi Driver" ["name"]=> string(11) "SCSI_DECNCR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(133) " Say Y here to support the NCR53C94 SCSI controller chips on IOASIC based TURBOchannel DECstations and TURBOchannel PMAZ-A cards. " } [486]=> array(11) { ["entry_id"]=> string(3) "487" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "DEC SII Scsi Driver" ["name"]=> string(11) "SCSI_DECSII" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [487]=> array(11) { ["entry_id"]=> string(3) "488" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "3ware Hardware ATA-RAID support" ["name"]=> string(20) "BLK_DEV_3W_XXXX_RAID" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(244) " 3ware is the only hardware ATA-Raid product in Linux to date. This card is 2,4, or 8 channel master mode support only. SCSI support required!!! Please read the comments at the top of . " } [488]=> array(11) { ["entry_id"]=> string(3) "489" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "7000FASST SCSI support" ["name"]=> string(14) "SCSI_7000FASST" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(403) " This driver supports the Western Digital 7000 SCSI host adapter family. Some information is in the source: . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wd7000. If you want to compile it as a module, say M here and read . " } [489]=> array(11) { ["entry_id"]=> string(3) "490" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "ACARD SCSI support" ["name"]=> string(10) "SCSI_ACARD" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(322) " This driver supports the ACARD 870U/W SCSI host adapter. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called atp870u. If you want to compile it as a module, say M here and read . " } [490]=> array(11) { ["entry_id"]=> string(3) "491" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Adaptec AHA152X/2825 support" ["name"]=> string(12) "SCSI_AHA152X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(624) " This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc. must be manually specified in this case. It is explained in section 3.3 of the SCSI-HOWTO, available from . You might also want to read the file . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called aha152x. If you want to compile it as a module, say M here and read . " } [491]=> array(11) { ["entry_id"]=> string(3) "492" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Adaptec AHA1542 support" ["name"]=> string(12) "SCSI_AHA1542" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(595) " This is support for a SCSI host adapter. It is explained in section 3.4 of the SCSI-HOWTO, available from . Note that Trantor was purchased by Adaptec, and some former Trantor products are being sold under the Adaptec name. If it doesn't work out of the box, you may have to change some settings in . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called aha1542. " } [492]=> array(11) { ["entry_id"]=> string(3) "493" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Adaptec AHA1740 support" ["name"]=> string(12) "SCSI_AHA1740" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(519) " This is support for a SCSI host adapter. It is explained in section 3.5 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called aha1740. If you want to compile it as a module, say M here and read . " } [493]=> array(11) { ["entry_id"]=> string(3) "494" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Adaptec AACRAID support (EXPERIMENTAL)" ["name"]=> string(12) "SCSI_AACRAID" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [494]=> array(11) { ["entry_id"]=> string(3) "495" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Adaptec AIC7xxx Fast -> U160 support (New Driver)" ["name"]=> string(12) "SCSI_AIC7XXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(482) " This driver supports all of Adaptec's Fast through Ultra 160 PCI based SCSI controllers as well as the aic7770 based EISA and VLB SCSI controllers (the 274x and 284x series). For AAA and ARO based configurations, only SCSI functionality is provided. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called aic7xxx. " } [495]=> array(11) { ["entry_id"]=> string(3) "496" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(23) "AIC7XXX_CMDS_PER_DEVICE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(41) "Maximum number of TCQ commands per device" ["help_text"]=> NULL } [496]=> array(11) { ["entry_id"]=> string(3) "497" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(22) "AIC7XXX_RESET_DELAY_MS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(40) "Initial bus reset delay in milli-seconds" ["help_text"]=> NULL } [497]=> array(11) { ["entry_id"]=> string(3) "498" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Probe for EISA and VL AIC7XXX Adapters" ["name"]=> string(21) "AIC7XXX_PROBE_EISA_VL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(324) " Probe for EISA and VLB Aic7xxx controllers. In many newer systems, the invasive probes necessary to detect these controllers can cause other devices to fail. For this reason, the non-PCI probe code is disabled by default. The current value of this option can be "toggled" via the no_probe kernel command line option. " } [498]=> array(11) { ["entry_id"]=> string(3) "499" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Build Adapter Firmware with Kernel Build" ["name"]=> string(22) "AIC7XXX_BUILD_FIRMWARE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(467) " This option should only be enabled if you are modifying the firmware source to the aic7xxx driver and wish to have the generated firmware include files updated during a normal kernel build. The assembler for the firmware requires lex and yacc or their equivalents, as well as the db v1 library. You may have to install additional packages or modify the assembler Makefile or the files it includes if your build environment is different than that of the author. " } [499]=> array(11) { ["entry_id"]=> string(3) "500" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Compile in Debugging Code" ["name"]=> string(20) "AIC7XXX_DEBUG_ENABLE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(86) " Compile in aic7xxx debugging code that can be useful in diagnosing driver errors. " } [500]=> array(11) { ["entry_id"]=> string(3) "501" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(18) "AIC7XXX_DEBUG_MASK" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(47) "Debug code enable mask (2047 for all debugging)" ["help_text"]=> NULL } [501]=> array(11) { ["entry_id"]=> string(3) "502" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Decode registers during diagnostics" ["name"]=> string(24) "AIC7XXX_REG_PRETTY_PRINT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(219) " Compile in register value tables for the output of expanded register contents in diagnostics. This make it much easier to understand debug output without having to refer to a data book and/or the aic7xxx.reg file. " } [502]=> array(11) { ["entry_id"]=> string(3) "503" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Adaptec AIC7xxx support (old driver)" ["name"]=> string(16) "SCSI_AIC7XXX_OLD" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1862) " WARNING This driver is an older aic7xxx driver and is no longer under active development. Adaptec, Inc. is writing a new driver to take the place of this one, and it is recommended that whenever possible, people should use the new Adaptec written driver instead of this one. This driver will eventually be phased out entirely. This is support for the various aic7xxx based Adaptec SCSI controllers. These include the 274x EISA cards; 284x VLB cards; 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and motherboard based SCSI controllers from Adaptec. It does not support the AAA-13x RAID controllers from Adaptec, nor will it likely ever support them. It does not support the 2920 cards from Adaptec that use the Future Domain SCSI controller chip. For those cards, you need the "Future Domain 16xx SCSI support" driver. In general, if the controller is based on an Adaptec SCSI controller chip from the aic777x series or the aic78xx series, this driver should work. The only exception is the 7810 which is specifically not supported (that's the RAID controller chip on the AAA-13x cards). Note that the AHA2920 SCSI host adapter is *not* supported by this driver; choose "Future Domain 16xx SCSI support" instead if you have one of those. Information on the configuration options for this controller can be found by checking the help file for each of the available configuration options. You should read at a minimum before contacting the maintainer with any questions. The SCSI-HOWTO, available from , can also be of great help. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called aic7xxx_old. " } [503]=> array(11) { ["entry_id"]=> string(3) "504" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Adaptec AIC79xx U320 support" ["name"]=> string(12) "SCSI_AIC79XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(82) " This driver supports all of Adaptec's Ultra 320 PCI-X based SCSI controllers. " } [504]=> array(11) { ["entry_id"]=> string(3) "505" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(23) "AIC79XX_CMDS_PER_DEVICE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(41) "Maximum number of TCQ commands per device" ["help_text"]=> NULL } [505]=> array(11) { ["entry_id"]=> string(3) "506" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(22) "AIC79XX_RESET_DELAY_MS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(40) "Initial bus reset delay in milli-seconds" ["help_text"]=> NULL } [506]=> array(11) { ["entry_id"]=> string(3) "507" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Build Adapter Firmware with Kernel Build" ["name"]=> string(22) "AIC79XX_BUILD_FIRMWARE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(467) " This option should only be enabled if you are modifying the firmware source to the aic79xx driver and wish to have the generated firmware include files updated during a normal kernel build. The assembler for the firmware requires lex and yacc or their equivalents, as well as the db v1 library. You may have to install additional packages or modify the assembler Makefile or the files it includes if your build environment is different than that of the author. " } [507]=> array(11) { ["entry_id"]=> string(3) "508" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Enable Read Streaming for All Targets" ["name"]=> string(22) "AIC79XX_ENABLE_RD_STRM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(357) " Read Streaming is a U320 protocol option that should enhance performance. Early U320 drive firmware actually performs slower with read streaming enabled so it is disabled by default. Read Streaming can be configured in much the same way as tagged queueing using the "rd_strm" command line option. See drivers/scsi/aic7xxx/README.aic79xx for details. " } [508]=> array(11) { ["entry_id"]=> string(3) "509" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Compile in Debugging Code" ["name"]=> string(20) "AIC79XX_DEBUG_ENABLE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(86) " Compile in aic79xx debugging code that can be useful in diagnosing driver errors. " } [509]=> array(11) { ["entry_id"]=> string(3) "510" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(18) "AIC79XX_DEBUG_MASK" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(48) "Debug code enable mask (16383 for all debugging)" ["help_text"]=> NULL } [510]=> array(11) { ["entry_id"]=> string(3) "511" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Decode registers during diagnostics" ["name"]=> string(24) "AIC79XX_REG_PRETTY_PRINT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(219) " Compile in register value tables for the output of expanded register contents in diagnostics. This make it much easier to understand debug output without having to refer to a data book and/or the aic7xxx.reg file. " } [511]=> array(11) { ["entry_id"]=> string(3) "512" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Adaptec I2O RAID support " ["name"]=> string(12) "SCSI_DPT_I2O" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(466) " This driver supports all of Adaptec's I2O based RAID controllers as well as the DPT SmartRaid V cards. This is an Adaptec maintained driver by Deanna Bonds. See . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . The module will be called dpt_i2o. " } [512]=> array(11) { ["entry_id"]=> string(3) "513" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "AdvanSys SCSI support" ["name"]=> string(13) "SCSI_ADVANSYS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(410) " This is a driver for all SCSI host adapters manufactured by AdvanSys. It is documented in the kernel source in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . The module will be called advansys. " } [513]=> array(11) { ["entry_id"]=> string(3) "514" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Always IN2000 SCSI support" ["name"]=> string(11) "SCSI_IN2000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(445) " This is support for an ISA bus SCSI host adapter. You'll find more information in . If it doesn't work out of the box, you may have to change the jumpers for IRQ or address selection. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called in2000. " } [514]=> array(11) { ["entry_id"]=> string(3) "515" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "AM53/79C974 PCI SCSI support" ["name"]=> string(13) "SCSI_AM53C974" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(597) " This is support for the AM53/79C974 SCSI host adapters. Please read for details. Also, the SCSI-HOWTO, available from , is for you. Note that there is another driver for AM53C974 based adapters: "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You can pick either one. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called AM53C974. " } [515]=> array(11) { ["entry_id"]=> string(3) "516" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "AMI MegaRAID support" ["name"]=> string(13) "SCSI_MEGARAID" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(328) " This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490 and 467 SCSI host adapters. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called megaraid. " } [516]=> array(11) { ["entry_id"]=> string(3) "517" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "BusLogic SCSI support" ["name"]=> string(13) "SCSI_BUSLOGIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(722) " This is support for BusLogic MultiMaster and FlashPoint SCSI Host Adapters. Consult the SCSI-HOWTO, available from , and the files and for more information. If this driver does not work correctly without modification, please contact the author, Leonard N. Zubkoff, by email to lnz@dandelion.com. You can also build this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), but only a single instance may be loaded. If you want to compile it as a module, say M here and read . The module will be called BusLogic. " } [517]=> array(11) { ["entry_id"]=> string(3) "518" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Omit FlashPoint support" ["name"]=> string(20) "SCSI_OMIT_FLASHPOINT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(197) " This option allows you to omit the FlashPoint support from the BusLogic SCSI driver. The FlashPoint SCCB Manager code is substantial, so users of MultiMaster Host Adapters may wish to omit it. " } [518]=> array(11) { ["entry_id"]=> string(3) "519" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Compaq Fibre Channel 64-bit/66Mhz HBA support" ["name"]=> string(12) "SCSI_CPQFCTS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(110) " Say Y here to compile in support for the Compaq StorageWorks Fibre Channel 64-bit/66Mhz Host Bus Adapter. " } [519]=> array(11) { ["entry_id"]=> string(3) "520" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "DMX3191D SCSI support" ["name"]=> string(13) "SCSI_DMX3191D" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(322) " This is support for Domex DMX3191D SCSI Host Adapters. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dmx3191d. If you want to compile it as a module, say M here and read . " } [520]=> array(11) { ["entry_id"]=> string(3) "521" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "DTC3180/3280 SCSI support" ["name"]=> string(12) "SCSI_DTC3280" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(451) " This is support for DTC 3180/3280 SCSI Host Adapters. Please read the SCSI-HOWTO, available from , and the file . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dtc. If you want to compile it as a module, say M here and read . " } [521]=> array(11) { ["entry_id"]=> string(3) "522" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(69) "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support" ["name"]=> string(9) "SCSI_EATA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(595) " This driver supports all EATA/DMA-compliant SCSI host adapters. DPT ISA and all EISA I/O addresses are probed looking for the "EATA" signature. The addresses of all the PCI SCSI controllers reported by the PCI subsystem are probed as well. You want to read the start of and the SCSI-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called eata. " } [522]=> array(11) { ["entry_id"]=> string(3) "523" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "enable tagged command queueing" ["name"]=> string(22) "SCSI_EATA_TAGGED_QUEUE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(227) " This is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. This is equivalent to the "eata=tc:y" boot option. " } [523]=> array(11) { ["entry_id"]=> string(3) "524" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "enable elevator sorting" ["name"]=> string(25) "SCSI_EATA_LINKED_COMMANDS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(307) " This option enables elevator sorting for all probed SCSI disks and CD-ROMs. It definitely reduces the average seek distance when doing random seeks, but this does not necessarily result in a noticeable performance improvement: your mileage may vary... This is equivalent to the "eata=lc:y" boot option. " } [524]=> array(11) { ["entry_id"]=> string(3) "525" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(18) "SCSI_EATA_MAX_TAGS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(33) "maximum number of queued commands" ["help_text"]=> NULL } [525]=> array(11) { ["entry_id"]=> string(3) "526" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "EATA-PIO (old DPT PM2001, PM2012A) support" ["name"]=> string(13) "SCSI_EATA_PIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(607) " This driver supports all EATA-PIO protocol compliant SCSI Host Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant host adapters could also use this driver but are discouraged from doing so, since this driver only supports hard disks and lacks numerous features. You might want to have a look at the SCSI-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called eata_pio. " } [526]=> array(11) { ["entry_id"]=> string(3) "527" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Future Domain 16xx SCSI/AHA-2920A support" ["name"]=> string(18) "SCSI_FUTURE_DOMAIN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(886) " This is support for Future Domain's 16-bit SCSI host adapters (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and other adapters based on the Future Domain chipsets (Quantum ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board). It is explained in section 3.7 of the SCSI-HOWTO, available from . NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI controller support"). This Future Domain driver works with the older Adaptec AHA-2920A boards with a Future Domain chip on them. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fdomain. If you want to compile it as a module, say M here and read . " } [527]=> array(11) { ["entry_id"]=> string(3) "528" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Future Domain MCS-600/700 SCSI support" ["name"]=> string(11) "SCSI_FD_MCS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(584) " This is support for Future Domain MCS 600/700 MCA SCSI adapters. Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which is identical to the MCS 700 and hence also supported by this driver. This driver also supports the Reply SB16/SCSI card (the SCSI part). It supports multiple adapters in the same system. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fd_mcs. If you want to compile it as a module, say M here and read . " } [528]=> array(11) { ["entry_id"]=> string(3) "529" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(62) "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support" ["name"]=> string(9) "SCSI_GDTH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(510) " Formerly called GDT SCSI Disk Array Controller Support. This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) manufactured by Intel/ICP vortex (an Intel Company). It is documented in the kernel source in and This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [529]=> array(11) { ["entry_id"]=> string(3) "530" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Generic NCR5380/53c400 SCSI PIO support" ["name"]=> string(20) "SCSI_GENERIC_NCR5380" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(835) " This is a driver for the old NCR 53c80 series of SCSI controllers on boards using PIO. Most boards such as the Trantor T130 fit this category, along with a large number of ISA 8bit controllers shipped for free with SCSI scanners. If you have a PAS16, T128 or DMX3191 you should select the specific driver for that card rather than generic 5380 support. It is explained in section 3.8 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called g_NCR5380. If you want to compile it as a module, say M here and read . " } [530]=> array(11) { ["entry_id"]=> string(3) "531" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Generic NCR5380/53c400 SCSI MMIO support" ["name"]=> string(25) "SCSI_GENERIC_NCR5380_MMIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(588) " This is a driver for the old NCR 53c80 series of SCSI controllers on boards using memory mapped I/O. It is explained in section 3.8 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called g_NCR5380_mmio. If you want to compile it as a module, say M here and read . " } [531]=> array(11) { ["entry_id"]=> string(3) "532" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Enable NCR53c400 extensions" ["name"]=> string(22) "SCSI_GENERIC_NCR53C400" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(362) " This enables certain optimizations for the NCR53c400 SCSI cards. You might as well try it out. Note that this driver will only probe for the Trantor T130B in its default configuration; you might have to pass a command line option to the kernel at boot time if it does not detect your card. See the file for details. " } [532]=> array(11) { ["entry_id"]=> string(3) "533" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "IBMMCA SCSI support" ["name"]=> string(11) "SCSI_IBMMCA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(999) " This is support for the IBM SCSI adapter found in many of the PS/2 series computers. These machines have an MCA bus, so you need to answer Y to "MCA support" as well and read . If the adapter isn't found during boot (a common problem for models 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=' kernel option, where is the id of the SCSI subsystem (usually 7, but if that doesn't work check your reference diskette). Owners of model 95 with a LED-matrix-display can in addition activate some activity info like under OS/2, but more informative, by setting 'ibmmcascsi=display' as an additional kernel parameter. Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ibmmca. " } [533]=> array(11) { ["entry_id"]=> string(3) "534" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Standard SCSI-order" ["name"]=> string(26) "IBMMCA_SCSI_ORDER_STANDARD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1579) " In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks are assigned to the drive letters, starting with the lowest SCSI-id (physical number -- pun) to be drive C:, as seen from DOS and similar operating systems. When looking into papers describing the ANSI-SCSI-standard, this assignment of drives appears to be wrong. The SCSI-standard follows a hardware-hierarchy which says that id 7 has the highest priority and id 0 the lowest. Therefore, the host adapters are still today everywhere placed as SCSI-id 7 by default. In the SCSI-standard, the drive letters express the priority of the disk. C: should be the hard disk, or a partition on it, with the highest priority. This must therefore be the disk with the highest SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the original definition of the SCSI-standard as also industrial- and process-control-machines, like VME-CPUs running under realtime-OSes (e.g. LynxOS, OS9) do. If you like to run Linux on your MCA-machine with the same assignment of hard disks as seen from e.g. DOS or OS/2 on your machine, which is in addition conformant to the SCSI-standard, you must say Y here. This is also necessary for MCA-Linux users who want to keep downward compatibility to older releases of the IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than June 1997). If you like to have the lowest SCSI-id assigned as drive C:, as modern SCSI-BIOSes do, which does not conform to the standard, but is widespread and common in the PC-world of today, you must say N here. If unsure, say Y. " } [534]=> array(11) { ["entry_id"]=> string(3) "535" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Reset SCSI-devices at boottime" ["name"]=> string(21) "IBMMCA_SCSI_DEV_RESET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(606) " By default, SCSI-devices are reset when the machine is powered on. However, some devices exist, like special-control-devices, SCSI-CNC-machines, SCSI-printer or scanners of older type, that do not reset when switched on. If you say Y here, each device connected to your SCSI-bus will be issued a reset-command after it has been probed, while the kernel is booting. This may cause problems with more modern devices, like hard disks, which do not appreciate these reset commands, and can cause your system to hang. So say Y only if you know that one of your older devices needs it; N is the safe answer. " } [535]=> array(11) { ["entry_id"]=> string(3) "536" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "IBM ServeRAID support" ["name"]=> string(8) "SCSI_IPS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(574) " This is support for the IBM ServeRAID hardware RAID controllers. See for more information. If this driver does not work correctly without modification please contact the author by email at ipslinux@us.ibm.com. You can build this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), but only a single instance may be loaded. If you want to compile it as a module, say M here and read . The module will be called ips. " } [536]=> array(11) { ["entry_id"]=> string(3) "537" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Initio 9100U(W) support" ["name"]=> string(11) "SCSI_INITIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(366) " This is support for the Initio 91XXU(W) SCSI host adapter. Please read the SCSI-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called initio. " } [537]=> array(11) { ["entry_id"]=> string(3) "538" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Initio INI-A100U2W support" ["name"]=> string(12) "SCSI_INIA100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(369) " This is support for the Initio INI-A100U2W SCSI host adapter. Please read the SCSI-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called a100u2w. " } [538]=> array(11) { ["entry_id"]=> string(3) "539" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "IOMEGA parallel port (ppa - older drives)" ["name"]=> string(8) "SCSI_PPA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1130) " This driver supports older versions of IOMEGA's parallel port ZIP drive (a 100 MB removable media device). Note that you can say N here if you have the SCSI version of the ZIP drive: it will be supported automatically if you said Y to the generic "SCSI disk support", above. If you have the ZIP Plus drive or a more recent parallel port ZIP drive (if the supplied cable with the drive is labeled "AutoDetect") then you should say N here and Y to "IOMEGA parallel port (imm - newer drives)", below. For more information about this driver and how to use it you should read the file . You should also read the SCSI-HOWTO, which is available from . If you use this driver, you will still be able to use the parallel port for other tasks, such as a printer; it is safe to compile both drivers into the kernel. This driver is also available as a module which can be inserted in and removed from the running kernel whenever you want. To compile this driver as a module, say M here and read . The module will be called ppa. " } [539]=> array(11) { ["entry_id"]=> string(3) "540" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "IOMEGA parallel port (imm - newer drives)" ["name"]=> string(8) "SCSI_IMM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1174) " This driver supports newer versions of IOMEGA's parallel port ZIP drive (a 100 MB removable media device). Note that you can say N here if you have the SCSI version of the ZIP drive: it will be supported automatically if you said Y to the generic "SCSI disk support", above. If you have the ZIP Plus drive or a more recent parallel port ZIP drive (if the supplied cable with the drive is labeled "AutoDetect") then you should say Y here; if you have an older ZIP drive, say N here and Y to "IOMEGA Parallel Port (ppa - older drives)", above. For more information about this driver and how to use it you should read the file . You should also read the SCSI-HOWTO, which is available from . If you use this driver, you will still be able to use the parallel port for other tasks, such as a printer; it is safe to compile both drivers into the kernel. This driver is also available as a module which can be inserted in and removed from the running kernel whenever you want. To compile this driver as a module, say M here and read . The module will be called imm. " } [540]=> array(11) { ["entry_id"]=> string(3) "541" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "ppa/imm option - Use slow (but safe) EPP-16" ["name"]=> string(15) "SCSI_IZIP_EPP16" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(428) " EPP (Enhanced Parallel Port) is a standard for parallel ports which allows them to act as expansion buses that can handle up to 64 peripheral devices. Some parallel port chipsets are slower than their motherboard, and so we have to control the state of the chipset's FIFO queue every now and then to avoid data loss. This will be done if you say Y here. Generally, saying Y is the safe option and slows things down a bit. " } [541]=> array(11) { ["entry_id"]=> string(3) "542" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "ppa/imm option - Assume slow parport control register" ["name"]=> string(18) "SCSI_IZIP_SLOW_CTR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(482) " Some parallel ports are known to have excessive delays between changing the parallel port control register and good data being available on the parallel port data/status register. This option forces a small delay (1.0 usec to be exact) after changing the control register to let things settle out. Enabling this option may result in a big drop in performance but some very old parallel ports (found in 386 vintage machines) will not work properly. Generally, saying N is fine. " } [542]=> array(11) { ["entry_id"]=> string(3) "543" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "NCR53c406a SCSI support" ["name"]=> string(15) "SCSI_NCR53C406A" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(469) " This is support for the NCR53c406a SCSI host adapter. For user configurable parameters, check out in the kernel source. Also read the SCSI-HOWTO, available from . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called NCR53c406. " } [543]=> array(11) { ["entry_id"]=> string(3) "544" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "NCR Dual 700 MCA SCSI support" ["name"]=> string(13) "SCSI_NCR_D700" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(299) " This is a driver for the MicroChannel Dual 700 card produced by NCR and commonly used in 345x/35xx/4100 class machines. It always tries to negotiate sync and uses tag command queueing. Unless you have an NCR manufactured machine, the chances are that you do not have this SCSI card, so say N. " } [544]=> array(11) { ["entry_id"]=> string(3) "545" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "53C700_IO_MAPPED" ["name"]=> string(16) "53C700_IO_MAPPED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [545]=> array(11) { ["entry_id"]=> string(3) "546" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "HP Lasi SCSI support for 53c700/710" ["name"]=> string(12) "SCSI_LASI700" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(186) " This is a driver for the SCSI controller in the Lasi chip found in many PA-RISC workstations & servers. If you do not know whether you have a Lasi chip, it is safe to say "Y" here. " } [546]=> array(11) { ["entry_id"]=> string(3) "547" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "53C700_MEM_MAPPED" ["name"]=> string(17) "53C700_MEM_MAPPED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [547]=> array(11) { ["entry_id"]=> string(3) "548" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "53C700_LE_ON_BE" ["name"]=> string(15) "53C700_LE_ON_BE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [548]=> array(11) { ["entry_id"]=> string(3) "549" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "SYM53C8XX Version 2 SCSI support" ["name"]=> string(16) "SCSI_SYM53C8XX_2" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(401) " This driver supports the whole NCR53C8XX/SYM53C8XX family of PCI-SCSI controllers. It also supports the subset of LSI53C10XX Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI controllers; you need to use the Fusion MPT driver for that. Please read for more information. " } [549]=> array(11) { ["entry_id"]=> string(3) "550" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(34) "SCSI_SYM53C8XX_DMA_ADDRESSING_MODE" ["value"]=> string(1) "1" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(19) "DMA addressing mode" ["help_text"]=> NULL } [550]=> array(11) { ["entry_id"]=> string(3) "551" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(27) "SCSI_SYM53C8XX_DEFAULT_TAGS" ["value"]=> string(2) "16" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(34) "default tagged command queue depth" ["help_text"]=> NULL } [551]=> array(11) { ["entry_id"]=> string(3) "552" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(23) "SCSI_SYM53C8XX_MAX_TAGS" ["value"]=> string(2) "64" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(33) "maximum number of queued commands" ["help_text"]=> NULL } [552]=> array(11) { ["entry_id"]=> string(3) "553" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "use normal IO" ["name"]=> string(23) "SCSI_SYM53C8XX_IOMAPPED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(96) " If you say Y here, the driver will preferently use normal IO rather than memory mapped IO. " } [553]=> array(11) { ["entry_id"]=> string(3) "554" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Zalon SCSI support" ["name"]=> string(10) "SCSI_ZALON" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(307) " The Zalon is a GSC/HSC bus interface chip that sits between the PA-RISC processor and the NCR 53c720 SCSI controller on C100, C110, J200, J210 and some D, K & R-class machines. It's also used on the add-in Bluefish, Barracuda & Shrike SCSI cards. Say Y here if you have one of these machines or cards. " } [554]=> array(11) { ["entry_id"]=> string(3) "555" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "NCR Quad 720 MCA SCSI support" ["name"]=> string(13) "SCSI_NCR_Q720" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(299) " This is a driver for the MicroChannel Quad 720 card produced by NCR and commonly used in 345x/35xx/4100 class machines. It always tries to negotiate sync and uses tag command queueing. Unless you have an NCR manufactured machine, the chances are that you do not have this SCSI card, so say N. " } [555]=> array(11) { ["entry_id"]=> string(3) "556" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "SYM53C8XX SCSI support" ["name"]=> string(14) "SCSI_SYM53C8XX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1076) " This driver supports all the features of recent 53C8XX chips (used in PCI SCSI controllers), notably the hardware phase mismatch feature of the SYM53C896. Older versions of the 53C8XX chips are not supported by this driver. If your system uses either a 810 rev. < 16, a 815, or a 825 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX driver ("NCR53C8XX SCSI support" above) or configure both the NCR53C8XX and this SYM53C8XX drivers either as module or linked to the kernel image. When both drivers are linked into the kernel, the SYM53C8XX driver is called first at initialization and you can use the 'excl=ioaddr' driver boot option to exclude attachment of adapters by the SYM53C8XX driver. For example, entering 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents adapters at io address 0xb400 and 0xc000 from being attached by the SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them. The 'excl' option is also supported by the NCR53C8XX driver. Please read for more information. " } [556]=> array(11) { ["entry_id"]=> string(3) "557" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(27) "SCSI_NCR53C8XX_DEFAULT_TAGS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(36) " default tagged command queue depth" ["help_text"]=> NULL } [557]=> array(11) { ["entry_id"]=> string(3) "558" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(23) "SCSI_NCR53C8XX_MAX_TAGS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(35) " maximum number of queued commands" ["help_text"]=> NULL } [558]=> array(11) { ["entry_id"]=> string(3) "559" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "SCSI_NCR53C8XX_SYNC" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(40) " synchronous transfers frequency in MHz" ["help_text"]=> NULL } [559]=> array(11) { ["entry_id"]=> string(3) "560" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) " enable profiling" ["name"]=> string(22) "SCSI_NCR53C8XX_PROFILE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(273) " This option allows you to enable profiling information gathering. These statistics are not very accurate due to the low frequency of the kernel clock (100 Hz on i386) and have performance impact on systems that use very fast devices. The normal answer therefore is N. " } [560]=> array(11) { ["entry_id"]=> string(3) "561" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) " use normal IO" ["name"]=> string(23) "SCSI_NCR53C8XX_IOMAPPED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(384) " If you say Y here, the driver will use normal IO, as opposed to memory mapped IO. Memory mapped IO has less latency than normal IO and works for most Intel-based hardware. Under Linux/Alpha only normal IO is currently supported by the driver and so, this option has no effect on those systems. The normal answer therefore is N; try Y only if you encounter SCSI related problems. " } [561]=> array(11) { ["entry_id"]=> string(3) "562" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) " include support for the NCR PQS/PDS SCSI card" ["name"]=> string(22) "SCSI_NCR53C8XX_PQS_PDS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(329) " Say Y here if you have a special SCSI adapter produced by NCR corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need this if you do not have one of these adapters. However, since this device is detected as a specific PCI device, this option is quite safe. The common answer here is N, but answering Y is safe. " } [562]=> array(11) { ["entry_id"]=> string(3) "563" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) " not allow targets to disconnect" ["name"]=> string(28) "SCSI_NCR53C8XX_NO_DISCONNECT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(329) " This option is only provided for safety if you suspect some SCSI device of yours to not support properly the target-disconnect feature. In that case, you would say Y here. In general however, to not allow targets to disconnect is not reasonable if there is more than 1 device on a SCSI bus. The normal answer therefore is N. " } [563]=> array(11) { ["entry_id"]=> string(3) "564" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) " assume boards are SYMBIOS compatible (EXPERIMENTAL)" ["name"]=> string(29) "SCSI_NCR53C8XX_SYMBIOS_COMPAT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(727) " This option allows you to enable some features depending on GPIO wiring. These General Purpose Input/Output pins can be used for vendor specific features or implementation of the standard SYMBIOS features. Genuine SYMBIOS controllers use GPIO0 in output for controller LED and GPIO3 bit as a flag indicating singled-ended/differential interface. The Tekram DC-390U/F boards uses a different GPIO wiring. Your answer to this question is ignored if all your controllers have NVRAM, since the driver is able to detect the board type from the NVRAM format. If all the controllers in your system are genuine SYMBIOS boards or use BIOS and drivers from SYMBIOS, you would want to say Y here, otherwise N. N is the safe answer. " } [564]=> array(11) { ["entry_id"]=> string(3) "565" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "NCR MCA 53C9x SCSI support" ["name"]=> string(14) "SCSI_MCA_53C9X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(409) " Some MicroChannel machines, notably the NCR 35xx line, use a SCSI controller based on the NCR 53C94. This driver will allow use of the controller on the 3550, and very possibly others. If you want to compile this as a module (= code which can be inserted and removed from the running kernel whenever you want), say M here and read . The module will be called mca_53c9x. " } [565]=> array(11) { ["entry_id"]=> string(3) "566" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "PAS16 SCSI support" ["name"]=> string(10) "SCSI_PAS16" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(516) " This is support for a SCSI host adapter. It is explained in section 3.10 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called pas16. If you want to compile it as a module, say M here and read . " } [566]=> array(11) { ["entry_id"]=> string(3) "567" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "PCI2000 support" ["name"]=> string(12) "SCSI_PCI2000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(417) " This is support for the PCI2000I EIDE interface card which acts as a SCSI host adapter. Please read the SCSI-HOWTO, available from . This driver is also available as a module called pci2000 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [567]=> array(11) { ["entry_id"]=> string(3) "568" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "PCI2220i support" ["name"]=> string(13) "SCSI_PCI2220I" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(418) " This is support for the PCI2220i EIDE interface card which acts as a SCSI host adapter. Please read the SCSI-HOWTO, available from . This driver is also available as a module called pci2220i ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [568]=> array(11) { ["entry_id"]=> string(3) "569" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "PSI240i support" ["name"]=> string(12) "SCSI_PSI240I" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(416) " This is support for the PSI240i EIDE interface card which acts as a SCSI host adapter. Please read the SCSI-HOWTO, available from . This driver is also available as a module called psi240i ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [569]=> array(11) { ["entry_id"]=> string(3) "570" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Qlogic FAS SCSI support" ["name"]=> string(15) "SCSI_QLOGIC_FAS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(798) " This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic FastSCSI! cards as well as any other card based on the FASXX chip (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards). This driver does NOT support the PCI versions of these cards. The PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP SCSI support"), below. Information about this driver is contained in . You should also read the SCSI-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called qlogicfas. If you want to compile it as a module, say M here and read . " } [570]=> array(11) { ["entry_id"]=> string(3) "571" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Qlogic ISP SCSI support" ["name"]=> string(15) "SCSI_QLOGIC_ISP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(693) " This driver works for all QLogic PCI SCSI host adapters (IQ-PCI, IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter card is supported by the "AM53/79C974 PCI SCSI" driver.) If you say Y here, make sure to choose "BIOS" at the question "PCI access mode". Please read the file . You should also read the SCSI-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called qlogicisp. If you want to compile it as a module, say M here and read . " } [571]=> array(11) { ["entry_id"]=> string(3) "572" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Qlogic ISP FC SCSI support" ["name"]=> string(14) "SCSI_QLOGIC_FC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(330) " This is a driver for the QLogic ISP2100 SCSI-FCP host adapter. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called qlogicfc. If you want to compile it as a module, say M here and read . " } [572]=> array(11) { ["entry_id"]=> string(3) "573" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Include loadable firmware in driver" ["name"]=> string(23) "SCSI_QLOGIC_FC_FIRMWARE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(180) " Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with expanded LUN addressing and FcTape (FCP-2) support, in the qlogicfc driver. This is required on some platforms. " } [573]=> array(11) { ["entry_id"]=> string(3) "574" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Qlogic QLA 1280 SCSI support" ["name"]=> string(16) "SCSI_QLOGIC_1280" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(325) " Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called qla1280. If you want to compile it as a module, say M here and read . " } [574]=> array(11) { ["entry_id"]=> string(3) "575" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "PTI Qlogic, ISP Driver" ["name"]=> string(14) "SCSI_QLOGICPTI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(479) " This driver supports SBUS SCSI controllers from PTI or QLogic. These controllers are known under Solaris as qpti and in the openprom as PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are driven by a different driver. This support is also available as a module called qlogicpti ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [575]=> array(11) { ["entry_id"]=> string(3) "576" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(52) "Seagate ST-02 and Future Domain TMC-8xx SCSI support" ["name"]=> string(12) "SCSI_SEAGATE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(556) " These are 8-bit SCSI controllers; the ST-01 is also supported by this driver. It is explained in section 3.9 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called seagate. If you want to compile it as a module, say M here and read . " } [576]=> array(11) { ["entry_id"]=> string(3) "577" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Simple 53c710 SCSI support (Compaq, NCR machines)" ["name"]=> string(11) "SCSI_SIM710" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(115) " This driver for NCR53c710 based SCSI host adapters. It currently supports Compaq EISA cards and NCR MCA cards " } [577]=> array(11) { ["entry_id"]=> string(3) "578" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "53C700_IO_MAPPED" ["name"]=> string(16) "53C700_IO_MAPPED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [578]=> array(11) { ["entry_id"]=> string(3) "579" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Symbios 53c416 SCSI support" ["name"]=> string(14) "SCSI_SYM53C416" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(803) " This is support for the sym53c416 SCSI host adapter, the SCSI adapter that comes with some HP scanners. This driver requires that the sym53c416 is configured first using some sort of PnP configuration program (e.g. isapnp) or by a PnP aware BIOS. If you are using isapnp then you need to compile this driver as a module and then load it using insmod after isapnp has run. The parameters of the configured card(s) should be passed to the driver. The format is: insmod sym53c416 sym53c416=, [sym53c416_1=,] There is support for up to four adapters. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called sym53c416. " } [579]=> array(11) { ["entry_id"]=> string(3) "580" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(61) "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)" ["name"]=> string(11) "SCSI_DC395x" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(549) " This driver supports PCI SCSI host adapters based on the ASIC TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants. This driver works, but is still in experimental status. So better have a bootable disk and a backup in case of emergency. Documentation can be found in . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called dc395x. " } [580]=> array(11) { ["entry_id"]=> string(3) "581" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "Tekram DC390(T) and Am53/79C974 SCSI support" ["name"]=> string(11) "SCSI_DC390T" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(727) " This driver supports PCI SCSI host adapters based on the Am53C974A chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard PCscsi/PCnet (Am53/79C974) solutions. Documentation can be found in . Note that this driver does NOT support Tekram DC390W/U/F, which are based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those. Also note that there is another generic Am53C974 driver, "AM53/79C974 PCI SCSI support" below. You can pick either one. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called tmscsim. " } [581]=> array(11) { ["entry_id"]=> string(3) "582" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "_omit_ support for non-DC390 adapters" ["name"]=> string(21) "SCSI_DC390T_NOGENSUPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(612) " If you say N here, the DC390(T) SCSI driver relies on the DC390 EEPROM to get initial values for its settings, such as speed, termination, etc. If it can't find this EEPROM, it will use defaults or the user supplied boot/module parameters. For details on driver configuration see . If you say Y here and if no EEPROM is found, the driver gives up and thus only supports Tekram DC390(T) adapters. This can be useful if you have a DC390(T) and another Am53C974 based adapter, which, for some reason, you want to drive with the other AM53C974 driver. If unsure, say N. " } [582]=> array(11) { ["entry_id"]=> string(3) "583" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Trantor T128/T128F/T228 SCSI support" ["name"]=> string(9) "SCSI_T128" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(630) " This is support for a SCSI host adapter. It is explained in section 3.11 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . Note that Trantor was purchased by Adaptec, and some former Trantor products are being sold under the Adaptec name. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called t128. If you want to compile it as a module, say M here and read . " } [583]=> array(11) { ["entry_id"]=> string(3) "584" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "UltraStor 14F/34F support" ["name"]=> string(12) "SCSI_U14_34F" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(777) " This is support for the UltraStor 14F and 34F SCSI-2 host adapters. The source at contains some information about this hardware. If the driver doesn't work out of the box, you may have to change some settings in . Read the SCSI-HOWTO, available from . Note that there is also another driver for the same hardware: "UltraStor SCSI support", below. You should say Y to both only if you want 24F support as well. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called u14-34f. If you want to compile it as a module, say M here and read . " } [584]=> array(11) { ["entry_id"]=> string(3) "585" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "enable tagged command queueing" ["name"]=> string(25) "SCSI_U14_34F_TAGGED_QUEUE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(230) " This is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. This is equivalent to the "u14-34f=tc:y" boot option. " } [585]=> array(11) { ["entry_id"]=> string(3) "586" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "enable elevator sorting" ["name"]=> string(28) "SCSI_U14_34F_LINKED_COMMANDS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(310) " This option enables elevator sorting for all probed SCSI disks and CD-ROMs. It definitely reduces the average seek distance when doing random seeks, but this does not necessarily result in a noticeable performance improvement: your mileage may vary... This is equivalent to the "u14-34f=lc:y" boot option. " } [586]=> array(11) { ["entry_id"]=> string(3) "587" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(21) "SCSI_U14_34F_MAX_TAGS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(33) "maximum number of queued commands" ["help_text"]=> NULL } [587]=> array(11) { ["entry_id"]=> string(3) "588" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "UltraStor SCSI support" ["name"]=> string(14) "SCSI_ULTRASTOR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(629) " This is support for the UltraStor 14F, 24F and 34F SCSI-2 host adapter family. This driver is explained in section 3.12 of the SCSI-HOWTO, available from . If it doesn't work out of the box, you may have to change some settings in . Note that there is also another driver for the same hardware: "UltraStor 14F/34F support", above. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ultrastor. " } [588]=> array(11) { ["entry_id"]=> string(3) "589" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Workbit NinjaSCSI-32Bi/UDE support" ["name"]=> string(10) "SCSI_NSP32" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(387) " This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus SCSI host adapter. Please read the SCSI-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called nsp32. " } [589]=> array(11) { ["entry_id"]=> string(3) "590" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "SCSI debugging host simulator" ["name"]=> string(10) "SCSI_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(509) " This is a host adapter simulator that can simulate multiple hosts each with multiple dummy SCSI devices (disks). It defaults to one host adapter with one dummy SCSI disk. Each dummy disk uses kernel RAM as storage (i.e. it is a ramdisk). To save space when multiple dummy disks are simulated, they share the same kernel RAM for their storage. See http://www.torque.net/sg/sdebug.html for more information. This driver is primarily of use to those testing the SCSI and block subsystems. If unsure, say N. " } [590]=> array(11) { ["entry_id"]=> string(3) "591" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "MESH (Power Mac internal SCSI) support" ["name"]=> string(9) "SCSI_MESH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(450) " Many Power Macintoshes and clones have a MESH (Macintosh Enhanced SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the other Power Macintoshes do). Say Y to include support for this SCSI adaptor. This driver is also available as a module called mesh ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [591]=> array(11) { ["entry_id"]=> string(3) "592" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "SCSI_MESH_SYNC_RATE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(52) "maximum synchronous transfer rate (MB/s) (0 = async)" ["help_text"]=> NULL } [592]=> array(11) { ["entry_id"]=> string(3) "593" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(24) "SCSI_MESH_RESET_DELAY_MS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> string(43) "initial bus reset delay (ms) (0 = no reset)" ["help_text"]=> NULL } [593]=> array(11) { ["entry_id"]=> string(3) "594" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "53C94 (Power Mac external SCSI) support" ["name"]=> string(13) "SCSI_MAC53C94" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(497) " On Power Macintoshes (and clones) with two SCSI buses, the external SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older machines which only have one SCSI bus, such as the 7200, also use the 53C94. Say Y to include support for the 53C94. This driver is also available as a module called mac53c94 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [594]=> array(11) { ["entry_id"]=> string(3) "595" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Acorn SCSI card (aka30) support" ["name"]=> string(16) "SCSI_ACORNSCSI_3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(130) " This enables support for the Acorn SCSI card (aka30). If you have an Acorn system with one of these, say Y. If unsure, say N. " } [595]=> array(11) { ["entry_id"]=> string(3) "596" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Support SCSI 2 Tagged queueing" ["name"]=> string(27) "SCSI_ACORNSCSI_TAGGED_QUEUE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(319) " Say Y here to enable tagged queuing support on the Acorn SCSI card. This is a feature of SCSI-2 which improves performance: the host adapter can send several SCSI commands to a device's queue even if previous commands haven't finished yet. Some SCSI devices don't implement this properly, so the safe answer is N. " } [596]=> array(11) { ["entry_id"]=> string(3) "597" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Support SCSI 2 Synchronous Transfers" ["name"]=> string(19) "SCSI_ACORNSCSI_SYNC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(219) " Say Y here to enable synchronous transfer negotiation with all targets on the Acorn SCSI card. In general, this improves performance; however some SCSI devices don't implement it properly, so the safe answer is N. " } [597]=> array(11) { ["entry_id"]=> string(3) "598" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "ARXE SCSI support" ["name"]=> string(13) "SCSI_ARXESCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(447) " Around 1991, Arxe Systems Limited released a high density floppy disc interface for the Acorn Archimedes range, to allow the use of HD discs from the then new A5000 on earlier models. This interface was either sold on its own or with an integral SCSI controller. Technical details on this NCR53c94-based device are available at Say Y here to compile in support for the SCSI controller. " } [598]=> array(11) { ["entry_id"]=> string(3) "599" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "CumanaSCSI II support" ["name"]=> string(13) "SCSI_CUMANA_2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(126) " This enables support for the Cumana SCSI II card. If you have an Acorn system with one of these, say Y. If unsure, say N. " } [599]=> array(11) { ["entry_id"]=> string(3) "600" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "EESOX support" ["name"]=> string(14) "SCSI_EESOXSCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(121) " This enables support for the EESOX SCSI card. If you have an Acorn system with one of these, say Y, otherwise say N. " } [600]=> array(11) { ["entry_id"]=> string(3) "601" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "PowerTec support" ["name"]=> string(17) "SCSI_POWERTECSCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(121) " This enables support for the Powertec SCSI card on Acorn systems. If you have one of these, say Y. If unsure, say N. " } [601]=> array(11) { ["entry_id"]=> string(3) "602" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "CumanaSCSI I support (EXPERIMENTAL)" ["name"]=> string(13) "SCSI_CUMANA_1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(125) " This enables support for the Cumana SCSI I card. If you have an Acorn system with one of these, say Y. If unsure, say N. " } [602]=> array(11) { ["entry_id"]=> string(3) "603" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "EcoScsi support (EXPERIMENTAL)" ["name"]=> string(12) "SCSI_ECOSCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(166) " This enables support for the EcoSCSI card -- a small card that sits in the Econet socket. If you have an Acorn system with one of these, say Y. If unsure, say N. " } [603]=> array(11) { ["entry_id"]=> string(3) "604" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Oak SCSI support (EXPERIMENTAL)" ["name"]=> string(9) "SCSI_OAK1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(121) " This enables support for the Oak SCSI card. If you have an Acorn system with one of these, say Y. If unsure, say N. " } [604]=> array(11) { ["entry_id"]=> string(3) "605" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "MIPS JAZZ FAS216 SCSI support" ["name"]=> string(8) "JAZZ_ESP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " This is the driver for the onboard SCSI host adapter of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. " } [605]=> array(11) { ["entry_id"]=> string(3) "606" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "A3000 WD33C93A support" ["name"]=> string(10) "A3000_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(375) " If you have an Amiga 3000 and have SCSI devices connected to the built-in SCSI controller, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called wd33c93. If you want to compile it as a module, say M here and read . " } [606]=> array(11) { ["entry_id"]=> string(3) "607" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "A4000T SCSI support (EXPERIMENTAL)" ["name"]=> string(11) "A4000T_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(66) " Support for the NCR53C710 SCSI controller on the Amiga 4000T. " } [607]=> array(11) { ["entry_id"]=> string(3) "608" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "A2091/A590 WD33C93A support" ["name"]=> string(10) "A2091_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(331) " If you have a Commodore A2091 SCSI controller, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called wd33c93. If you want to compile it as a module, say M here and read . " } [608]=> array(11) { ["entry_id"]=> string(3) "609" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "GVP Series II WD33C93A support" ["name"]=> string(10) "GVP11_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(547) " If you have a Great Valley Products Series II SCSI controller, answer Y. Also say Y if you have a later model of GVP SCSI controller (such as the GVP A4008 or a Combo board). Otherwise, answer N. This driver does NOT work for the T-Rex series of accelerators from TekMagic and GVP-M. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called gvp11. If you want to compile it as a module, say M here and read . " } [609]=> array(11) { ["entry_id"]=> string(3) "610" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "CyberStorm SCSI support" ["name"]=> string(15) "CYBERSTORM_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(157) " If you have an Amiga with an original (MkI) Phase5 Cyberstorm accelerator board and the optional Cyberstorm SCSI controller, answer Y. Otherwise, say N. " } [610]=> array(11) { ["entry_id"]=> string(3) "611" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "CyberStorm Mk II SCSI support" ["name"]=> string(17) "CYBERSTORMII_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(146) " If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board and the optional Cyberstorm SCSI controller, say Y. Otherwise, answer N. " } [611]=> array(11) { ["entry_id"]=> string(3) "612" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Blizzard 2060 SCSI support" ["name"]=> string(12) "BLZ2060_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(144) " If you have an Amiga with a Phase5 Blizzard 2060 accelerator board and want to use the onboard SCSI controller, say Y. Otherwise, answer N. " } [612]=> array(11) { ["entry_id"]=> string(3) "613" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Blizzard 1230IV/1260 SCSI support" ["name"]=> string(12) "BLZ1230_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard 1260 accelerator, and the optional SCSI module, say Y. Otherwise, say N. " } [613]=> array(11) { ["entry_id"]=> string(3) "614" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Fastlane SCSI support" ["name"]=> string(13) "FASTLANE_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(137) " If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one in the near future, say Y to this question. Otherwise, say N. " } [614]=> array(11) { ["entry_id"]=> string(3) "615" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "A4091 SCSI support (EXPERIMENTAL)" ["name"]=> string(10) "A4091_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(194) " Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller (1993). Very obscure -- the 4091 was part of an Amiga 4000 upgrade plan at the time the Amiga business was sold to DKB. " } [615]=> array(11) { ["entry_id"]=> string(3) "616" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "WarpEngine SCSI support (EXPERIMENTAL)" ["name"]=> string(15) "WARPENGINE_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(151) " Support for MacroSystem Development's WarpEngine Amiga SCSI-2 controller. Info at . " } [616]=> array(11) { ["entry_id"]=> string(3) "617" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)" ["name"]=> string(16) "BLZ603EPLUS_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(105) " If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+ accelerator, say Y. Otherwise, say N. " } [617]=> array(11) { ["entry_id"]=> string(3) "618" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "BSC Oktagon SCSI support (EXPERIMENTAL)" ["name"]=> string(12) "OKTAGON_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(210) " If you have the BSC Oktagon SCSI disk controller for the Amiga, say Y to this question. If you're in doubt about whether you have one, see the picture at . " } [618]=> array(11) { ["entry_id"]=> string(3) "619" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Atari native SCSI support" ["name"]=> string(10) "ATARI_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(664) " If you have an Atari with built-in NCR5380 SCSI controller (TT, Falcon, ...) say Y to get it supported. Of course also, if you have a compatible SCSI controller (e.g. for Medusa). This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called atari_scsi. If you want to compile it as a module, say M here and read . This driver supports both styles of NCR integration into the system: the TT style (separate DMA), and the Falcon style (via ST-DMA, replacing ACSI). It does NOT support other schemes, like in the Hades (without DMA). " } [619]=> array(11) { ["entry_id"]=> string(3) "620" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Long delays for Toshiba CD-ROMs" ["name"]=> string(24) "ATARI_SCSI_TOSHIBA_DELAY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(243) " This option increases the delay after a SCSI arbitration to accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to use a Toshiba CD-ROM drive; otherwise, the option is not needed and would impact performance a bit, so say N. " } [620]=> array(11) { ["entry_id"]=> string(3) "621" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Reset SCSI-devices at boottime" ["name"]=> string(21) "ATARI_SCSI_RESET_BOOT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(203) " Reset the devices on your Atari whenever it boots. This makes the boot process fractionally longer but may assist recovery from errors that leave the devices with SCSI operations partway completed. " } [621]=> array(11) { ["entry_id"]=> string(3) "622" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Hades SCSI DMA emulator" ["name"]=> string(11) "TT_DMA_EMUL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(164) " This option enables code which emulates the TT SCSI DMA chip on the Hades. This increases the SCSI transfer rates at least ten times compared to PIO transfers. " } [622]=> array(11) { ["entry_id"]=> string(3) "623" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Macintosh NCR5380 SCSI" ["name"]=> string(8) "MAC_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(201) " This is the NCR 5380 SCSI controller included on most of the 68030 based Macintoshes. If you have one of these say Y and read the SCSI-HOWTO, available from . " } [623]=> array(11) { ["entry_id"]=> string(3) "624" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Macintosh NCR53c9[46] SCSI" ["name"]=> string(12) "SCSI_MAC_ESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(461) " This is the NCR 53c9x SCSI controller found on most of the 68040 based Macintoshes. If you have one of these say Y and read the SCSI-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called mac_esp. If you want to compile it as a module, say M here and read . " } [624]=> array(11) { ["entry_id"]=> string(3) "625" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "WD33C93 SCSI driver for MVME147" ["name"]=> string(12) "MVME147_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(92) " Support for the on-board SCSI controller on the Motorola MVME147 single-board computer. " } [625]=> array(11) { ["entry_id"]=> string(3) "626" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "NCR53C710 SCSI driver for MVME16x" ["name"]=> string(12) "MVME16x_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(175) " The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question. " } [626]=> array(11) { ["entry_id"]=> string(3) "627" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "NCR53C710 SCSI driver for BVME6000" ["name"]=> string(13) "BVME6000_SCSI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(170) " The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question. " } [627]=> array(11) { ["entry_id"]=> string(3) "628" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "allow FAST-SCSI [10MHz]" ["name"]=> string(19) "SCSI_NCR53C7xx_FAST" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " This will enable 10MHz FAST-SCSI transfers with your host adapter. Some systems have problems with that speed, so it's safest to say N here. " } [628]=> array(11) { ["entry_id"]=> string(3) "629" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "Sun3 NCR5380 SCSI" ["name"]=> string(9) "SUN3_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(314) " This option will enable support for the OBIO (onboard io) NCR5380 SCSI controller found in the Sun 3/50 and 3/60, as well as for "Sun3" type VME scsi controllers also based on the NCR5380. General Linux information on the Sun 3 series (now discontinued) is at . " } [629]=> array(11) { ["entry_id"]=> string(3) "630" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "Sun3x ESP SCSI" ["name"]=> string(9) "SUN3X_ESP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(113) " The ESP was an on-board SCSI controller used on Sun 3/80 machines. Say Y here to compile in support for it. " } [630]=> array(11) { ["entry_id"]=> string(3) "631" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Sparc ESP Scsi Driver" ["name"]=> string(11) "SCSI_SUNESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(359) " This is the driver for the Sun ESP SCSI host adapter. The ESP chipset is present in most SPARC SBUS-based computers. This support is also available as a module called esp ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [631]=> array(11) { ["entry_id"]=> string(3) "632" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "NEC PC-9801-55 SCSI support" ["name"]=> string(13) "SCSI_PC980155" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(102) " If you have the NEC PC-9801-55 SCSI interface card or compatibles for NEC PC-9801/PC-9821, say Y. " } [632]=> array(11) { ["entry_id"]=> string(3) "633" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "WD33C93_PIO" ["name"]=> string(11) "WD33C93_PIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [633]=> array(11) { ["entry_id"]=> string(3) "634" ["entry_type"]=> string(4) "MENU" ["text"]=> string(27) "PCMCIA SCSI adapter support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [634]=> array(11) { ["entry_id"]=> string(3) "635" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Adaptec AHA152X PCMCIA support" ["name"]=> string(14) "PCMCIA_AHA152X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(339) " Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called aha152x_cs ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [635]=> array(11) { ["entry_id"]=> string(3) "636" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Future Domain PCMCIA support" ["name"]=> string(14) "PCMCIA_FDOMAIN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(340) " Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called fdomain_cs ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [636]=> array(11) { ["entry_id"]=> string(3) "637" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support" ["name"]=> string(17) "PCMCIA_NINJA_SCSI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(385) " If you intend to attach this type of PCMCIA SCSI host adapter to your computer, say Y here and read . This driver is also available as a module called nsp_cs ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [637]=> array(11) { ["entry_id"]=> string(3) "638" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Qlogic PCMCIA support" ["name"]=> string(13) "PCMCIA_QLOGIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(339) " Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called qlogic_cs ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [638]=> array(11) { ["entry_id"]=> string(3) "639" ["entry_type"]=> string(4) "MENU" ["text"]=> string(18) "Networking support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [639]=> array(11) { ["entry_id"]=> string(3) "640" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Networking support" ["name"]=> string(3) "NET" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(671) " Unless you really know what you are doing, you should say Y here. The reason is that some programs need kernel networking support even when running on a stand-alone machine that isn't connected to any other computer. If you are upgrading from an older kernel, you should consider updating your networking tools too because changes in the kernel and the tools often go hand in hand. The tools are contained in the package net-tools, the location and version number of which are given in . For a general introduction to Linux networking, it is highly recommended to read the NET-HOWTO, available from . " } [640]=> array(11) { ["entry_id"]=> string(3) "641" ["entry_type"]=> string(4) "MENU" ["text"]=> string(18) "Networking options" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [641]=> array(11) { ["entry_id"]=> string(3) "642" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "Packet socket" ["name"]=> string(6) "PACKET" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(582) " The Packet protocol is used by applications which communicate directly with network devices without an intermediate network protocol implemented in the kernel, e.g. tcpdump. If you want them to work, choose Y. This driver is also available as a module called af_packet ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read ; if you use modprobe or kmod, you may also want to add "alias net-pf-17 af_packet" to /etc/modules.conf. If unsure, say Y. " } [642]=> array(11) { ["entry_id"]=> string(3) "643" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Packet socket: mmapped IO" ["name"]=> string(11) "PACKET_MMAP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(132) " If you say Y here, the Packet protocol driver will use an IO mechanism that results in faster communication. If unsure, say N. " } [643]=> array(11) { ["entry_id"]=> string(3) "644" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Netlink device emulation" ["name"]=> string(11) "NETLINK_DEV" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(287) " This option will be removed soon. Any programs that want to use character special nodes like /dev/tap0 or /dev/route (all with major number 36) need this option, and need to be rewritten soon to use the real netlink socket. This is a backward compatibility option, choose Y for now. " } [644]=> array(11) { ["entry_id"]=> string(3) "645" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "Network packet filtering (replaces ipchains)" ["name"]=> string(9) "NETFILTER" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(2625) " Netfilter is a framework for filtering and mangling network packets that pass through your Linux box. The most common use of packet filtering is to run your Linux box as a firewall protecting a local network from the Internet. The type of firewall provided by this kernel support is called a "packet filter", which means that it can reject individual network packets based on type, source, destination etc. The other kind of firewall, a "proxy-based" one, is more secure but more intrusive and more bothersome to set up; it inspects the network traffic much more closely, modifies it and has knowledge about the higher level protocols, which a packet filter lacks. Moreover, proxy-based firewalls often require changes to the programs running on the local clients. Proxy-based firewalls don't need support by the kernel, but they are often combined with a packet filter, which only works if you say Y here. You should also say Y here if you intend to use your Linux box as the gateway to the Internet for a local network of machines without globally valid IP addresses. This is called "masquerading": if one of the computers on your local network wants to send something to the outside, your box can "masquerade" as that computer, i.e. it forwards the traffic to the intended outside destination, but modifies the packets to make it look like they came from the firewall box itself. It works both ways: if the outside host replies, the Linux box will silently forward the traffic to the correct local computer. This way, the computers on your local net are completely invisible to the outside world, even though they can reach the outside and can receive replies. It is even possible to run globally visible servers from within a masqueraded local network using a mechanism called portforwarding. Masquerading is also often called NAT (Network Address Translation). Another use of Netfilter is in transparent proxying: if a machine on the local network tries to connect to an outside host, your Linux box can transparently forward the traffic to a local server, typically a caching proxy server. Various modules exist for netfilter which replace the previous masquerading (ipmasqadm), packet filtering (ipchains), transparent proxying, and portforwarding mechanisms. Please see under "iptables" for the location of these packages. Make sure to say N to "Fast switching" below if you intend to say Y here, as Fast switching currently bypasses netfilter. Chances are that you should say Y here if you compile a kernel which will run as a router and N for regular hosts. If unsure, say N. " } [645]=> array(11) { ["entry_id"]=> string(3) "646" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Network packet filtering debugging" ["name"]=> string(15) "NETFILTER_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(102) " You can say Y here if you want to get additional messages useful in debugging the netfilter code. " } [646]=> array(11) { ["entry_id"]=> string(3) "647" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Unix domain sockets" ["name"]=> string(4) "UNIX" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1017) " If you say Y here, you will include support for Unix domain sockets; sockets are the standard Unix mechanism for establishing and accessing network connections. Many commonly used programs such as the X Window system and syslog use these sockets even if your machine is not connected to any network. Unless you are working on an embedded system or something similar, you therefore definitely want to say Y here. However, the socket support is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . The module will be called unix. If you try building this as a module and you have said Y to "Kernel module loader support" above, be sure to add 'alias net-pf-1 unix' to your /etc/modules.conf file. Note that several important services won't work correctly if you say M here and then neglect to load the module. Say Y unless you know what you are doing. " } [647]=> array(11) { ["entry_id"]=> string(3) "648" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "PF_KEY sockets" ["name"]=> string(7) "NET_KEY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(168) " PF_KEYv2 socket family, compatible to KAME ones. They are required if you are going to use IPsec tools ported from KAME. Say Y unless you know what you are doing. " } [648]=> array(11) { ["entry_id"]=> string(3) "649" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "TCP/IP networking" ["name"]=> string(4) "INET" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1151) " These are the protocols used on the Internet and on most local Ethernets. It is highly recommended to say Y here (this will enlarge your kernel by about 144 KB), since some programs (e.g. the X window system) use TCP/IP even if your machine is not connected to any other computer. You will get the so-called loopback device which allows you to ping yourself (great fun, that!). For an excellent introduction to Linux networking, please read the NET-3-HOWTO, available from . This option is also necessary if you want to use the full power of term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer; for more information, read ). If you say Y here and also to "/proc file system support" and "Sysctl support" below, you can change various aspects of the behavior of the TCP/IP code by writing to the (virtual) files in /proc/sys/net/ipv4/*; the options are explained in the file . Short answer: say Y. " } [649]=> array(11) { ["entry_id"]=> string(3) "650" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "IP: multicasting" ["name"]=> string(12) "IP_MULTICAST" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(518) " This is code for addressing several networked computers at once, enlarging your kernel by about 2 KB. You need multicasting if you intend to participate in the MBONE, a high bandwidth network on top of the Internet which carries audio and video broadcasts. More information about the MBONE is on the WWW at . Information about the multicast capabilities of the various network cards is contained in . For most people, it's safe to say N. " } [650]=> array(11) { ["entry_id"]=> string(3) "651" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "IP: advanced router" ["name"]=> string(18) "IP_ADVANCED_ROUTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1386) " If you intend to run your Linux box mostly as a router, i.e. as a computer that forwards and redistributes network packets, say Y; you will then be presented with several options that allow more precise control about the routing process. The answer to this question won't directly affect the kernel: answering N will just cause the configurator to skip all the questions about advanced routing. Note that your box can only act as a router if you enable IP forwarding in your kernel; you can do that by saying Y to "/proc file system support" and "Sysctl support" below and executing the line echo "1" > /proc/sys/net/ipv4/ip_forward at boot time after the /proc file system has been mounted. If you turn on IP forwarding, you will also get the rp_filter, which automatically rejects incoming packets if the routing table entry for their source address doesn't match the network interface they're arriving on. This has security advantages because it prevents the so-called IP spoofing, however it can pose problems if you use asymmetric routing (packets from you to a host take a different path than packets from that host to you) or if you operate a non-routing host which has several IP addresses on different interfaces. To turn rp_filter off use: echo 0 > /proc/sys/net/ipv4/conf//rp_filter or echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter If unsure, say N here. " } [651]=> array(11) { ["entry_id"]=> string(3) "652" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "IP: policy routing" ["name"]=> string(18) "IP_MULTIPLE_TABLES" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(848) " Normally, a router decides what to do with a received packet based solely on the packet's final destination address. If you say Y here, the Linux router will also be able to take the packet's source address into account. Furthermore, if you also say Y to "Use TOS value as routing key" below, the TOS (Type-Of-Service) field of the packet can be used for routing decisions as well. In addition, if you say Y here and to "Fast network address translation" below, the router will also be able to modify source and destination addresses of forwarded packets. If you are interested in this, please see the preliminary documentation at and . You will need supporting software from . If unsure, say N. " } [652]=> array(11) { ["entry_id"]=> string(3) "653" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "IP: use netfilter MARK value as routing key" ["name"]=> string(15) "IP_ROUTE_FWMARK" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(139) " If you say Y here, you will be able to specify different routes for packets with different mark values (see iptables(8), MARK target). " } [653]=> array(11) { ["entry_id"]=> string(3) "654" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "IP: fast network address translation" ["name"]=> string(12) "IP_ROUTE_NAT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(303) " If you say Y here, your router will be able to modify source and destination addresses of packets that pass through it, in a manner you specify. General information about Network Address Translation can be gotten from the document . " } [654]=> array(11) { ["entry_id"]=> string(3) "655" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "IP: equal cost multipath" ["name"]=> string(18) "IP_ROUTE_MULTIPATH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(429) " Normally, the routing tables specify a single action to be taken in a deterministic manner for a given packet. If you say Y here however, it becomes possible to attach several actions to a packet pattern, in effect specifying several alternative paths to travel for those packets. The router considers all these paths to be of equal "cost" and chooses one of them in a non-deterministic fashion if a matching packet arrives. " } [655]=> array(11) { ["entry_id"]=> string(3) "656" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "IP: use TOS value as routing key" ["name"]=> string(12) "IP_ROUTE_TOS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(310) " The header of every IP packet carries a TOS (Type Of Service) value with which the packet requests a certain treatment, e.g. low latency (for interactive traffic), high throughput, or high reliability. If you say Y here, you will be able to specify different routes for packets with different TOS values. " } [656]=> array(11) { ["entry_id"]=> string(3) "657" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "IP: verbose route monitoring" ["name"]=> string(16) "IP_ROUTE_VERBOSE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(350) " If you say Y here, which is recommended, then the kernel will print verbose messages regarding the routing, for example warnings about received packets which look strange and could be evidence of an attack or a misconfigured system somewhere. The information is handled by the klogd daemon which is responsible for kernel messages ("man klogd"). " } [657]=> array(11) { ["entry_id"]=> string(3) "658" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "IP: kernel level autoconfiguration" ["name"]=> string(6) "IP_PNP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(433) " This enables automatic configuration of IP addresses of devices and of the routing table during kernel boot, based on either information supplied on the kernel command line or by BOOTP or RARP protocols. You need to say Y only for diskless machines requiring network access to boot (in which case you want to say Y to "Root file system on NFS" as well), because all other machines configure the network in their startup scripts. " } [658]=> array(11) { ["entry_id"]=> string(3) "659" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "IP: DHCP support" ["name"]=> string(11) "IP_PNP_DHCP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(659) " If you want your Linux box to mount its whole root file system (the one containing the directory /) from some other computer over the net via NFS and you want the IP address of your computer to be discovered automatically at boot time using the DHCP protocol (a special protocol designed for doing this job), say Y here. In case the boot ROM of your network card was designed for booting Linux and does DHCP itself, providing all necessary information on the kernel command line, you can say N here. If unsure, say Y. Note that if you want to use DHCP, a DHCP server must be operating on your network. Read for details. " } [659]=> array(11) { ["entry_id"]=> string(3) "660" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "IP: BOOTP support" ["name"]=> string(12) "IP_PNP_BOOTP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(661) " If you want your Linux box to mount its whole root file system (the one containing the directory /) from some other computer over the net via NFS and you want the IP address of your computer to be discovered automatically at boot time using the BOOTP protocol (a special protocol designed for doing this job), say Y here. In case the boot ROM of your network card was designed for booting Linux and does BOOTP itself, providing all necessary information on the kernel command line, you can say N here. If unsure, say Y. Note that if you want to use BOOTP, a BOOTP server must be operating on your network. Read for details. " } [660]=> array(11) { ["entry_id"]=> string(3) "661" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "IP: RARP support" ["name"]=> string(11) "IP_PNP_RARP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(474) " If you want your Linux box to mount its whole root file system (the one containing the directory /) from some other computer over the net via NFS and you want the IP address of your computer to be discovered automatically at boot time using the RARP protocol (an older protocol which is being obsoleted by BOOTP and DHCP), say Y here. Note that if you want to use RARP, a RARP server must be operating on your network. Read for details. " } [661]=> array(11) { ["entry_id"]=> string(3) "662" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "IP: tunneling" ["name"]=> string(8) "NET_IPIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(761) " Tunneling means encapsulating data of one protocol type within another protocol and sending it over a channel that understands the encapsulating protocol. This particular tunneling driver implements encapsulation of IP within IP, which sounds kind of pointless, but can be useful if you want to make your (or some other) machine appear on a different network than it physically is, or to use mobile-IP facilities (allowing laptops to seamlessly move between networks without changing their IP addresses; check out ). Saying Y to this option will produce two modules ( = code which can be inserted in and removed from the running kernel whenever you want). Most people won't need this and can say N. " } [662]=> array(11) { ["entry_id"]=> string(3) "663" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "IP: GRE tunnels over IP" ["name"]=> string(9) "NET_IPGRE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(550) " Tunneling means encapsulating data of one protocol type within another protocol and sending it over a channel that understands the encapsulating protocol. This particular tunneling driver implements GRE (Generic Routing Encapsulation) and at this time allows encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure. This driver is useful if the other endpoint is a Cisco router: Cisco likes GRE much better than the other Linux tunneling driver ("IP tunneling" above). In addition, GRE allows multicast redistribution through the tunnel. " } [663]=> array(11) { ["entry_id"]=> string(3) "664" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "IP: broadcast GRE over IP" ["name"]=> string(19) "NET_IPGRE_BROADCAST" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(262) " One application of GRE/IP is to construct a broadcast WAN (Wide Area Network), which looks like a normal Ethernet LAN (Local Area Network), but can be distributed all over the Internet. If you want to do that, say Y here and to "IP multicast routing" below. " } [664]=> array(11) { ["entry_id"]=> string(3) "665" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "IP: multicast routing" ["name"]=> string(9) "IP_MROUTE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(489) " This is used if you want your machine to act as a router for IP packets that have several destination addresses. It is needed on the MBONE, a high bandwidth network on top of the Internet which carries audio and video broadcasts. In order to do that, you would most likely run the program mrouted. Information about the multicast capabilities of the various network cards is contained in . If you haven't heard about it, you don't need it. " } [665]=> array(11) { ["entry_id"]=> string(3) "666" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "IP: PIM-SM version 1 support" ["name"]=> string(11) "IP_PIMSM_V1" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(387) " Kernel side support for Sparse Mode PIM (Protocol Independent Multicast) version 1. This multicast routing protocol is used widely because Cisco supports it. You need special software to use it (pimd-v1). Please see for more information about PIM. Say Y if you want to use PIM-SM v1. Note that you can say N here if you just want to use Dense Mode PIM. " } [666]=> array(11) { ["entry_id"]=> string(3) "667" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "IP: PIM-SM version 2 support" ["name"]=> string(11) "IP_PIMSM_V2" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(234) " Kernel side support for Sparse Mode PIM version 2. In order to use this, you need an experimental routing daemon supporting it (pimd or gated-5). This routing protocol is not used widely, so say N unless you want to play with it. " } [667]=> array(11) { ["entry_id"]=> string(3) "668" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "IP: ARP daemon support (EXPERIMENTAL)" ["name"]=> string(4) "ARPD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1110) " Normally, the kernel maintains an internal cache which maps IP addresses to hardware addresses on the local network, so that Ethernet/Token Ring/ etc. frames are sent to the proper address on the physical networking layer. For small networks having a few hundred directly connected hosts or less, keeping this address resolution (ARP) cache inside the kernel works well. However, maintaining an internal ARP cache does not work well for very large switched networks, and will use a lot of kernel memory if TCP/IP connections are made to many machines on the network. If you say Y here, the kernel's internal ARP cache will never grow to more than 256 entries (the oldest entries are expired in a LIFO manner) and communication will be attempted with the user space ARP daemon arpd. Arpd then answers the address resolution request either from its own cache or by asking the net. This code is experimental and also obsolete. If you want to use it, you need to find a version of the daemon arpd on the net somewhere, and you should also say Y to "Kernel/User network link driver", below. If unsure, say N. " } [668]=> array(11) { ["entry_id"]=> string(3) "669" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "IP: TCP Explicit Congestion Notification support" ["name"]=> string(8) "INET_ECN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(713) " Explicit Congestion Notification (ECN) allows routers to notify clients about network congestion, resulting in fewer dropped packets and increased network performance. This option adds ECN support to the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which allows ECN support to be disabled at runtime. Note that, on the Internet, there are many broken firewalls which refuse connections from ECN-enabled machines, and it may be a while before these firewalls are fixed. Until then, to access a site behind such a firewall (some of which are major sites, at the time of this writing) you will have to disable this option, either by saying N now or by using the sysctl. If in doubt, say N. " } [669]=> array(11) { ["entry_id"]=> string(3) "670" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "IP: TCP syncookie support (disabled per default)" ["name"]=> string(11) "SYN_COOKIES" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1450) " Normal TCP/IP networking is open to an attack known as "SYN flooding". This denial-of-service attack prevents legitimate remote users from being able to connect to your computer during an ongoing attack and requires very little work from the attacker, who can operate from anywhere on the Internet. SYN cookies provide protection against this type of attack. If you say Y here, the TCP/IP stack will use a cryptographic challenge protocol known as "SYN cookies" to enable legitimate users to continue to connect, even when your machine is under attack. There is no need for the legitimate users to change their TCP/IP software; SYN cookies work transparently to them. For technical information about SYN cookies, check out . If you are SYN flooded, the source address reported by the kernel is likely to have been forged by the attacker; it is only reported as an aid in tracing the packets to their actual source and should not be taken as absolute truth. SYN cookies may prevent correct error reporting on clients when the server is really overloaded. If this happens frequently better turn them off. If you say Y here, note that SYN cookies aren't enabled by default; you can enable them by saying Y to "/proc file system support" and "Sysctl support" below and executing the command echo 1 >/proc/sys/net/ipv4/tcp_syncookies at boot time after the /proc file system has been mounted. If unsure, say N. " } [670]=> array(11) { ["entry_id"]=> string(3) "671" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "IP: AH transformation" ["name"]=> string(7) "INET_AH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(45) " Support for IPsec AH. If unsure, say Y. " } [671]=> array(11) { ["entry_id"]=> string(3) "672" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "IP: ESP transformation" ["name"]=> string(8) "INET_ESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(46) " Support for IPsec ESP. If unsure, say Y. " } [672]=> array(11) { ["entry_id"]=> string(3) "673" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "IP: IPComp transformation" ["name"]=> string(11) "INET_IPCOMP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(96) " Support for IP Paylod Compression (RFC3173), typically needed for IPsec. If unsure, say Y. " } [673]=> array(11) { ["entry_id"]=> string(3) "674" ["entry_type"]=> string(4) "MENU" ["text"]=> string(27) "IP: Netfilter Configuration" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [674]=> array(11) { ["entry_id"]=> string(3) "675" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Connection tracking (required for masq/NAT)" ["name"]=> string(15) "IP_NF_CONNTRACK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(467) " Connection tracking keeps a record of what packets have passed through your machine, in order to figure out how they are related into connections. This is required to do Masquerading or other kinds of Network Address Translation (except for Fast NAT). It can also be used to enhance packet filtering (see `Connection state match support' below). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [675]=> array(11) { ["entry_id"]=> string(3) "676" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "FTP protocol support" ["name"]=> string(9) "IP_NF_FTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(287) " Tracking FTP connections is problematic: special helpers are required for tracking them, and doing masquerading and other forms of Network Address Translation on them. If you want to compile it as a module, say M here and read . If unsure, say `Y'. " } [676]=> array(11) { ["entry_id"]=> string(3) "677" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "IRC protocol support" ["name"]=> string(9) "IP_NF_IRC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(623) " There is a commonly-used extension to IRC called Direct Client-to-Client Protocol (DCC). This enables users to send files to each other, and also chat to each other without the need of a server. DCC Sending is used anywhere you send files over IRC, and DCC Chat is most commonly used by Eggdrop bots. If you are using NAT, this extension will enable you to send files and initiate chats. Note that you do NOT need this extension to get files or have others initiate chats, or everything else in IRC. If you want to compile it as a module, say M here and read . If unsure, say `Y'. " } [677]=> array(11) { ["entry_id"]=> string(3) "678" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "TFTP protocol support" ["name"]=> string(10) "IP_NF_TFTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(300) " TFTP connection tracking helper, this is required depending on how restrictive your ruleset is. If you are using a tftp client behind -j SNAT or -j MASQUERADING you will need this. If you want to compile it as a module, say M here and read . If unsure, say `Y'. " } [678]=> array(11) { ["entry_id"]=> string(3) "679" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Amanda backup protocol support" ["name"]=> string(12) "IP_NF_AMANDA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(465) " If you are running the Amanda backup package on this machine or machines that will be MASQUERADED through this machine, then you may want to enable this feature. This allows the connection tracking and natting code to allow the sub-channels that Amanda requires for communication of the backup data, messages and index. If you want to compile it as a module, say M here and read . If unsure, say `Y'. " } [679]=> array(11) { ["entry_id"]=> string(3) "680" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Userspace queueing via NETLINK (EXPERIMENTAL)" ["name"]=> string(11) "IP_NF_QUEUE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(242) " Netfilter has the ability to queue packets to user space: the netlink device can be used to access them using this driver. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [680]=> array(11) { ["entry_id"]=> string(3) "681" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "IP tables support (required for filtering/masq/NAT)" ["name"]=> string(14) "IP_NF_IPTABLES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(338) " iptables is a general, extensible packet identification framework. The packet filtering and full NAT (masquerading, port forwarding, etc) subsystems now use this: say `Y' or `M' here if you want to use either of those. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [681]=> array(11) { ["entry_id"]=> string(3) "682" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "limit match support" ["name"]=> string(17) "IP_NF_MATCH_LIMIT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(321) " limit matching allows you to control the rate at which a rule can be matched: mainly useful in combination with the LOG target ("LOG target support", below) and to avoid some Denial of Service attacks. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [682]=> array(11) { ["entry_id"]=> string(3) "683" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "MAC address match support" ["name"]=> string(15) "IP_NF_MATCH_MAC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(212) " MAC matching allows you to match packets based on the source Ethernet address of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [683]=> array(11) { ["entry_id"]=> string(3) "684" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Packet type match support" ["name"]=> string(19) "IP_NF_MATCH_PKTTYPE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(285) " Packet type matching allows you to match a packet by its "class", eg. BROADCAST, MULTICAST, ... Typical usage: iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [684]=> array(11) { ["entry_id"]=> string(3) "685" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "netfilter MARK match support" ["name"]=> string(16) "IP_NF_MATCH_MARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(263) " Netfilter mark matching allows you to match packets based on the `nfmark' value in the packet. This can be set by the MARK target (see below). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [685]=> array(11) { ["entry_id"]=> string(3) "686" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Multiple port match support" ["name"]=> string(21) "IP_NF_MATCH_MULTIPORT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(283) " Multiport matching allows you to match TCP or UDP packets based on a series of source or destination ports: normally a rule can only match a single range of ports. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [686]=> array(11) { ["entry_id"]=> string(3) "687" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "TOS match support" ["name"]=> string(15) "IP_NF_MATCH_TOS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(214) " TOS matching allows you to match packets based on the Type Of Service fields of the IP packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [687]=> array(11) { ["entry_id"]=> string(3) "688" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "recent match support" ["name"]=> string(18) "IP_NF_MATCH_RECENT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(364) " This match is used for creating one or many lists of recently used addresses and then matching against that/those list(s). Short options are available by using 'iptables -m recent -h' Official Website: If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [688]=> array(11) { ["entry_id"]=> string(3) "689" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "ECN match support" ["name"]=> string(15) "IP_NF_MATCH_ECN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(214) " This option adds a `ECN' match, which allows you to match against the IPv4 and TCP header ECN fields. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [689]=> array(11) { ["entry_id"]=> string(3) "690" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "DSCP match support" ["name"]=> string(16) "IP_NF_MATCH_DSCP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(285) " This option adds a `DSCP' match, which allows you to match against the IPv4 header DSCP field (DSCP codepoint). The DSCP codepoint can have any value between 0x0 and 0x4f. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [690]=> array(11) { ["entry_id"]=> string(3) "691" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "AH/ESP match support" ["name"]=> string(18) "IP_NF_MATCH_AH_ESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(234) " These two match extensions (`ah' and `esp') allow you to match a range of SPIs inside AH or ESP headers of IPSec packets. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [691]=> array(11) { ["entry_id"]=> string(3) "692" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "LENGTH match support" ["name"]=> string(18) "IP_NF_MATCH_LENGTH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(219) " This option allows you to match the length of a packet against a specific value or range of values. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [692]=> array(11) { ["entry_id"]=> string(3) "693" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "TTL match support" ["name"]=> string(15) "IP_NF_MATCH_TTL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(213) " This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user to match packets by their TTL value. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [693]=> array(11) { ["entry_id"]=> string(3) "694" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "tcpmss match support" ["name"]=> string(18) "IP_NF_MATCH_TCPMSS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(275) " This option adds a `tcpmss' match, which allows you to examine the MSS value of TCP SYN packets, which control the maximum packet size for that connection. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [694]=> array(11) { ["entry_id"]=> string(3) "695" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Helper match support" ["name"]=> string(18) "IP_NF_MATCH_HELPER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(231) " Helper matching allows you to match packets in dynamic connections tracked by a conntrack-helper, ie. ip_conntrack_ftp If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `Y'. " } [695]=> array(11) { ["entry_id"]=> string(3) "696" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Connection state match support" ["name"]=> string(17) "IP_NF_MATCH_STATE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(301) " Connection state matching allows you to match packets based on their relationship to a tracked connection (ie. previous packets). This is a powerful tool for packet classification. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [696]=> array(11) { ["entry_id"]=> string(3) "697" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Connection tracking match support" ["name"]=> string(21) "IP_NF_MATCH_CONNTRACK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(347) " This is a general conntrack match module, a superset of the state match. It allows matching on additional conntrack information, which is useful in complex configurations, such as NAT gateways with multiple internet links or tunnels. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [697]=> array(11) { ["entry_id"]=> string(3) "698" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Unclean match support (EXPERIMENTAL)" ["name"]=> string(19) "IP_NF_MATCH_UNCLEAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(254) " Unclean packet matching matches any strange or invalid packets, by looking at a series of fields in the IP, TCP, UDP and ICMP headers. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [698]=> array(11) { ["entry_id"]=> string(3) "699" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Owner match support (EXPERIMENTAL)" ["name"]=> string(17) "IP_NF_MATCH_OWNER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(251) " Packet owner matching allows you to match locally-generated packets based on who created them: the user, group, process or session. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [699]=> array(11) { ["entry_id"]=> string(3) "700" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Physdev match support" ["name"]=> string(19) "IP_NF_MATCH_PHYSDEV" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(228) " Physdev packet matching matches against the physical bridge ports the IP packet arrived on or will leave by. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [700]=> array(11) { ["entry_id"]=> string(3) "701" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Packet filtering" ["name"]=> string(12) "IP_NF_FILTER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(298) " Packet filtering defines a table `filter', which has a series of rules for simple packet filtering at local input, forwarding and local output. See the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [701]=> array(11) { ["entry_id"]=> string(3) "702" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "REJECT target support" ["name"]=> string(19) "IP_NF_TARGET_REJECT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(279) " The REJECT target allows a filtering rule to specify that an ICMP error should be issued in response to an incoming packet, rather than silently being dropped. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [702]=> array(11) { ["entry_id"]=> string(3) "703" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "MIRROR target support (EXPERIMENTAL)" ["name"]=> string(19) "IP_NF_TARGET_MIRROR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(234) " The MIRROR target allows a filtering rule to specify that an incoming packet should be bounced back to the sender. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [703]=> array(11) { ["entry_id"]=> string(3) "704" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "Full NAT" ["name"]=> string(9) "IP_NF_NAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(318) " The Full NAT option allows masquerading, port forwarding and other forms of full Network Address Port Translation. It is controlled by the `nat' table in iptables: see the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [704]=> array(11) { ["entry_id"]=> string(3) "705" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "IP_NF_NAT_NEEDED" ["name"]=> string(16) "IP_NF_NAT_NEEDED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [705]=> array(11) { ["entry_id"]=> string(3) "706" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "MASQUERADE target support" ["name"]=> string(23) "IP_NF_TARGET_MASQUERADE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(431) " Masquerading is a special case of NAT: all outgoing connections are changed to seem to come from a particular interface's address, and if the interface goes down, those connections are lost. This is only useful for dialup accounts with dynamic IP address (ie. your IP address will be different on next dialup). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [706]=> array(11) { ["entry_id"]=> string(3) "707" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "REDIRECT target support" ["name"]=> string(21) "IP_NF_TARGET_REDIRECT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(347) " REDIRECT is a special case of NAT: all incoming connections are mapped onto the incoming interface's address, causing the packets to come to the local machine instead of passing through. This is useful for transparent proxies. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [707]=> array(11) { ["entry_id"]=> string(3) "708" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "NAT of local connections (READ HELP)" ["name"]=> string(15) "IP_NF_NAT_LOCAL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(396) " This option enables support for NAT of locally originated connections. Enable this if you need to use destination NAT on connections originating from local processes on the nat box itself. Please note that you will need a recent version (>= 1.2.6a) of the iptables userspace program in order to use this feature. See http://www.iptables.org/ for download instructions. If unsure, say 'N'. " } [708]=> array(11) { ["entry_id"]=> string(3) "709" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Basic SNMP-ALG support (EXPERIMENTAL)" ["name"]=> string(20) "IP_NF_NAT_SNMP_BASIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(477) " This module implements an Application Layer Gateway (ALG) for SNMP payloads. In conjunction with NAT, it allows a network management system to access multiple private networks with conflicting addresses. It works by modifying IP addresses inside SNMP payloads to match IP-layer NAT mapping. This is the "basic" form of SNMP-ALG, as described in RFC 2962 If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [709]=> array(11) { ["entry_id"]=> string(3) "710" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "IP_NF_NAT_IRC" ["name"]=> string(13) "IP_NF_NAT_IRC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [710]=> array(11) { ["entry_id"]=> string(3) "711" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "IP_NF_NAT_FTP" ["name"]=> string(13) "IP_NF_NAT_FTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [711]=> array(11) { ["entry_id"]=> string(3) "712" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "IP_NF_NAT_TFTP" ["name"]=> string(14) "IP_NF_NAT_TFTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [712]=> array(11) { ["entry_id"]=> string(3) "713" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "IP_NF_NAT_AMANDA" ["name"]=> string(16) "IP_NF_NAT_AMANDA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [713]=> array(11) { ["entry_id"]=> string(3) "714" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Packet mangling" ["name"]=> string(12) "IP_NF_MANGLE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(294) " This option adds a `mangle' table to iptables: see the man page for iptables(8). This table is used for various packet alterations which can effect how the packet is routed. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [714]=> array(11) { ["entry_id"]=> string(3) "715" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "TOS target support" ["name"]=> string(16) "IP_NF_TARGET_TOS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(279) " This option adds a `TOS' target, which allows you to create rules in the `mangle' table which alter the Type Of Service field of an IP packet prior to routing. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [715]=> array(11) { ["entry_id"]=> string(3) "716" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "ECN target support" ["name"]=> string(16) "IP_NF_TARGET_ECN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(429) " This option adds a `ECN' target, which can be used in the iptables mangle table. You can use this target to remove the ECN bits from the IPv4 header of an IP packet. This is particularly useful, if you need to work around existing ECN blackholes on the internet, but don't want to disable ECN support in general. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [716]=> array(11) { ["entry_id"]=> string(3) "717" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "DSCP target support" ["name"]=> string(17) "IP_NF_TARGET_DSCP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(285) " This option adds a `DSCP' match, which allows you to match against the IPv4 header DSCP field (DSCP codepoint). The DSCP codepoint can have any value between 0x0 and 0x4f. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [717]=> array(11) { ["entry_id"]=> string(3) "718" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "MARK target support" ["name"]=> string(17) "IP_NF_TARGET_MARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(449) " This option adds a `MARK' target, which allows you to create rules in the `mangle' table which alter the netfilter mark (nfmark) field associated with the packet prior to routing. This can change the routing method (see `Use netfilter MARK value as routing key') and can also be used by other subsystems to change their behavior. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [718]=> array(11) { ["entry_id"]=> string(3) "719" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "LOG target support" ["name"]=> string(16) "IP_NF_TARGET_LOG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(254) " This option adds a `LOG' target, which allows you to create rules in any iptables table which records the packet header to the syslog. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [719]=> array(11) { ["entry_id"]=> string(3) "720" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "ULOG target support" ["name"]=> string(17) "IP_NF_TARGET_ULOG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(458) " This option adds a `ULOG' target, which allows you to create rules in any iptables table. The packet is passed to a userspace logging daemon using netlink multicast sockets; unlike the LOG target which can only be viewed through syslog. The apropriate userspace logging daemon (ulogd) may be obtained from http://www.gnumonks.org/projects/ulogd If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [720]=> array(11) { ["entry_id"]=> string(3) "721" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "TCPMSS target support" ["name"]=> string(19) "IP_NF_TARGET_TCPMSS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(958) " This option adds a `TCPMSS' target, which allows you to alter the MSS value of TCP SYN packets, to control the maximum size for that connection (usually limiting it to your outgoing interface's MTU minus 40). This is used to overcome criminally braindead ISPs or servers which block ICMP Fragmentation Needed packets. The symptoms of this problem are that everything works fine from your Linux firewall/router, but machines behind it can never exchange large packets: 1) Web browsers connect, then hang with no data received. 2) Small mail works fine, but large emails hang. 3) ssh works fine, but scp hangs after initial handshaking. Workaround: activate this option and add a rule to your firewall configuration like: iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [721]=> array(11) { ["entry_id"]=> string(3) "722" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "ARP tables support" ["name"]=> string(15) "IP_NF_ARPTABLES" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [722]=> array(11) { ["entry_id"]=> string(3) "723" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "ARP packet filtering" ["name"]=> string(15) "IP_NF_ARPFILTER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [723]=> array(11) { ["entry_id"]=> string(3) "724" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "ARP payload mangling" ["name"]=> string(16) "IP_NF_ARP_MANGLE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(99) " Allows altering the ARP packet payload: source and destination hardware and network addresses. " } [724]=> array(11) { ["entry_id"]=> string(3) "725" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "ipchains (2.2-style) support" ["name"]=> string(21) "IP_NF_COMPAT_IPCHAINS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(415) " This option places ipchains (with masquerading and redirection support) back into the kernel, using the new netfilter infrastructure. It is not recommended for new installations (see `Packet filtering'). With this enabled, you should be able to use the ipchains tool exactly as in 2.2 kernels. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [725]=> array(11) { ["entry_id"]=> string(3) "726" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "ipfwadm (2.0-style) support" ["name"]=> string(20) "IP_NF_COMPAT_IPFWADM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(413) " This option places ipfwadm (with masquerading and redirection support) back into the kernel, using the new netfilter infrastructure. It is not recommended for new installations (see `Packet filtering'). With this enabled, you should be able to use the ipfwadm tool exactly as in 2.0 kernels. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [726]=> array(11) { ["entry_id"]=> string(3) "727" ["entry_type"]=> string(4) "MENU" ["text"]=> string(32) "IP: Virtual Server Configuration" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [727]=> array(11) { ["entry_id"]=> string(3) "728" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "IP virtual server support (EXPERIMENTAL)" ["name"]=> string(5) "IP_VS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(906) " IP Virtual Server support will let you build a high-performance virtual server based on cluster of two or more real servers. This option must be enabled for at least one of the clustered computers that will take care of intercepting incomming connections to a single IP address and scheduling them to real servers. Three request dispatching techniques are implemented, they are virtual server via NAT, virtual server via tunneling and virtual server via direct routing. The several scheduling algorithms can be used to choose which server the connection is directed to, thus load balancing can be achieved among the servers. For more information and its administration program, please visit the following URL: http://www.linuxvirtualserver.org/ If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [728]=> array(11) { ["entry_id"]=> string(3) "729" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "IP virtual server debugging" ["name"]=> string(11) "IP_VS_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(170) " Say Y here if you want to get additional messages useful in debugging the IP virtual server code. You can change the debug level in /proc/sys/net/ipv4/vs/debug_level " } [729]=> array(11) { ["entry_id"]=> string(3) "730" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(14) "IP_VS_TAB_BITS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(47) "IPVS connection table size (the Nth power of 2)" ["help_text"]=> NULL } [730]=> array(11) { ["entry_id"]=> string(3) "731" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "TCP load balancing support" ["name"]=> string(15) "IP_VS_PROTO_TCP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(92) " This option enables support for load balancing TCP transport protocol. Say Y if unsure. " } [731]=> array(11) { ["entry_id"]=> string(3) "732" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "UDP load balancing support" ["name"]=> string(15) "IP_VS_PROTO_UDP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(92) " This option enables support for load balancing UDP transport protocol. Say Y if unsure. " } [732]=> array(11) { ["entry_id"]=> string(3) "733" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "ESP load balancing support" ["name"]=> string(15) "IP_VS_PROTO_ESP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(124) " This option enables support for load balancing ESP (Encapsultion Security Payload) transport protocol. Say Y if unsure. " } [733]=> array(11) { ["entry_id"]=> string(3) "734" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "AH load balancing support" ["name"]=> string(14) "IP_VS_PROTO_AH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(115) " This option enables support for load balancing AH (Authentication Header) transport protocol. Say Y if unsure. " } [734]=> array(11) { ["entry_id"]=> string(3) "735" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "round-robin scheduling" ["name"]=> string(8) "IP_VS_RR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(276) " The robin-robin scheduling algorithm simply directs network connections to different real servers in a round-robin manner. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [735]=> array(11) { ["entry_id"]=> string(3) "736" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "weighted round-robin scheduling" ["name"]=> string(9) "IP_VS_WRR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(526) " The weighted robin-robin scheduling algorithm directs network connections to different real servers based on server weights in a round-robin manner. Servers with higher weights receive new connections first than those with less weights, and servers with higher weights get more connections than those with less weights and servers with equal weights get equal connections. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [736]=> array(11) { ["entry_id"]=> string(3) "737" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "least-connection scheduling scheduling" ["name"]=> string(8) "IP_VS_LC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(283) " The least-connection scheduling algorithm directs network connections to the server with the least number of active connections. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [737]=> array(11) { ["entry_id"]=> string(3) "738" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "weighted least-connection scheduling" ["name"]=> string(9) "IP_VS_WLC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(313) " The weighted least-connection scheduling algorithm directs network connections to the server with the least active connections normalized by the server weight. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [738]=> array(11) { ["entry_id"]=> string(3) "739" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "locality-based least-connection scheduling" ["name"]=> string(10) "IP_VS_LBLC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(600) " The locality-based least-connection scheduling algorithm is for destination IP load balancing. It is usually used in cache cluster. This algorithm usually directs packet destined for an IP address to its server if the server is alive and under load. If the server is overloaded (its active connection numbers is larger than its weight) and there is a server in its half load, then allocate the weighted least-connection server to this IP address. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [739]=> array(11) { ["entry_id"]=> string(3) "740" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "locality-based least-connection with replication scheduling" ["name"]=> string(11) "IP_VS_LBLCR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(861) " The locality-based least-connection with replication scheduling algorithm is also for destination IP load balancing. It is usually used in cache cluster. It differs from the LBLC scheduling as follows: the load balancer maintains mappings from a target to a set of server nodes that can serve the target. Requests for a target are assigned to the least-connection node in the target's server set. If all the node in the server set are over loaded, it picks up a least-connection node in the cluster and adds it in the sever set for the target. If the server set has not been modified for the specified time, the most loaded node is removed from the server set, in order to avoid high degree of replication. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [740]=> array(11) { ["entry_id"]=> string(3) "741" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "destination hashing scheduling" ["name"]=> string(8) "IP_VS_DH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(328) " The destination hashing scheduling algorithm assigns network connections to the servers through looking up a statically assigned hash table by their destination IP addresses. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [741]=> array(11) { ["entry_id"]=> string(3) "742" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "source hashing scheduling" ["name"]=> string(8) "IP_VS_SH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(318) " The source hashing scheduling algorithm assigns network connections to the servers through looking up a statically assigned hash table by their source IP addresses. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [742]=> array(11) { ["entry_id"]=> string(3) "743" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "shortest expected delay scheduling" ["name"]=> string(9) "IP_VS_SED" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(496) " The shortest expected delay scheduling algorithm assigns network connections to the server with the shortest expected delay. The expected delay that the job will experience is (Ci + 1) / Ui if sent to the ith server, in which Ci is the number of connections on the the ith server and Ui is the fixed service rate (weight) of the ith server. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [743]=> array(11) { ["entry_id"]=> string(3) "744" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "never queue scheduling" ["name"]=> string(8) "IP_VS_NQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(492) " The never queue scheduling algorithm adopts a two-speed model. When there is an idle server available, the job will be sent to the idle server, instead of waiting for a fast one. When there is no idle server available, the job will be sent to the server that minimize its expected delay (The Shortest Expected Delay scheduling algorithm). If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [744]=> array(11) { ["entry_id"]=> string(3) "745" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "FTP protocol helper" ["name"]=> string(9) "IP_VS_FTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(501) " FTP is a protocol that transfers IP address and/or port number in the payload. In the virtual server via Network Address Translation, the IP address and port number of real servers cannot be sent to clients in ftp connections directly, so FTP protocol helper is required for tracking the connection and mangling it back to that of virtual service. If you want to compile it in kernel, say Y. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. " } [745]=> array(11) { ["entry_id"]=> string(3) "746" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "The IPv6 protocol (EXPERIMENTAL)" ["name"]=> string(4) "IPV6" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1027) " This is experimental support for the next version of the Internet Protocol: IP version 6 (also called IPng "IP next generation"). Features of this new protocol include: expanded address space, authentication and privacy, and seamless interoperability with the current version of IP (IP version 4). For general information about IPv6, see ; for specific information about IPv6 under Linux read the HOWTO at and the file net/ipv6/README in the kernel source. If you want to use IPv6, please upgrade to the newest net-tools as given in . You will still be able to do regular IPv4 networking as well. This protocol support is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ipv6. If you want to compile it as a module, say M here and read . It is safe to say N here for now. " } [746]=> array(11) { ["entry_id"]=> string(3) "747" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "IPv6: Privacy Extensions (RFC 3041) support" ["name"]=> string(12) "IPV6_PRIVACY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(422) " Privacy Extensions for Stateless Address Autoconfiguration in IPv6 support. With this option, additional periodically-alter pseudo-random global-scope unicast address(es) will assigned to your interface(s). By default, kernel do not generate temporary addresses. To use temporary addresses, do echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr See for details. " } [747]=> array(11) { ["entry_id"]=> string(3) "748" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "IPv6: AH transformation" ["name"]=> string(8) "INET6_AH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(45) " Support for IPsec AH. If unsure, say Y. " } [748]=> array(11) { ["entry_id"]=> string(3) "749" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "IPv6: ESP transformation" ["name"]=> string(9) "INET6_ESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(46) " Support for IPsec ESP. If unsure, say Y. " } [749]=> array(11) { ["entry_id"]=> string(3) "750" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "IPv6: IPComp transformation" ["name"]=> string(12) "INET6_IPCOMP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(96) " Support for IP Paylod Compression (RFC3173), typically needed for IPsec. If unsure, say Y. " } [750]=> array(11) { ["entry_id"]=> string(3) "751" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "IPv6: IPv6-in-IPv6 tunnel" ["name"]=> string(11) "IPV6_TUNNEL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(79) " Support for IPv6-in-IPv6 tunnels described in RFC 2473. If unsure, say N. " } [751]=> array(11) { ["entry_id"]=> string(3) "752" ["entry_type"]=> string(4) "MENU" ["text"]=> string(29) "IPv6: Netfilter Configuration" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [752]=> array(11) { ["entry_id"]=> string(3) "753" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Userspace queueing via NETLINK (EXPERIMENTAL)" ["name"]=> string(12) "IP6_NF_QUEUE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(475) " This option adds a queue handler to the kernel for IPv6 packets which lets us to receive the filtered packets with QUEUE target using libiptc as we can do with the IPv4 now. (C) Fernando Anton 2001 IPv64 Project - Work based in IPv64 draft by Arturo Azcorra. Universidad Carlos III de Madrid Universidad Politecnica de Alcala de Henares email: fanton@it.uc3m.es If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [753]=> array(11) { ["entry_id"]=> string(3) "754" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(52) "IP6 tables support (required for filtering/masq/NAT)" ["name"]=> string(15) "IP6_NF_IPTABLES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(372) " ip6tables is a general, extensible packet identification framework. Currently only the packet filtering and packet mangling subsystem for IPv6 use this, but connection tracking is going to follow. Say 'Y' or 'M' here if you want to use either of those. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [754]=> array(11) { ["entry_id"]=> string(3) "755" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "limit match support" ["name"]=> string(18) "IP6_NF_MATCH_LIMIT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(321) " limit matching allows you to control the rate at which a rule can be matched: mainly useful in combination with the LOG target ("LOG target support", below) and to avoid some Denial of Service attacks. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [755]=> array(11) { ["entry_id"]=> string(3) "756" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "MAC address match support" ["name"]=> string(16) "IP6_NF_MATCH_MAC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(212) " mac matching allows you to match packets based on the source Ethernet address of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [756]=> array(11) { ["entry_id"]=> string(3) "757" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Routing header match support" ["name"]=> string(15) "IP6_NF_MATCH_RT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(202) " rt matching allows you to match packets based on the routing header of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [757]=> array(11) { ["entry_id"]=> string(3) "758" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "Hop-by-hop and Dst opts header match support" ["name"]=> string(17) "IP6_NF_MATCH_OPTS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(221) " This allows one to match packets based on the hop-by-hop and destination options headers of a packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [758]=> array(11) { ["entry_id"]=> string(3) "759" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Fragmentation header match support" ["name"]=> string(17) "IP6_NF_MATCH_FRAG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(210) " frag matching allows you to match packets based on the fragmentation header of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [759]=> array(11) { ["entry_id"]=> string(3) "760" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "HL match support" ["name"]=> string(15) "IP6_NF_MATCH_HL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(197) " HL matching allows you to match packets based on the hop limit of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [760]=> array(11) { ["entry_id"]=> string(3) "761" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Multiple port match support" ["name"]=> string(22) "IP6_NF_MATCH_MULTIPORT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(283) " Multiport matching allows you to match TCP or UDP packets based on a series of source or destination ports: normally a rule can only match a single range of ports. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [761]=> array(11) { ["entry_id"]=> string(3) "762" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Owner match support (EXPERIMENTAL)" ["name"]=> string(18) "IP6_NF_MATCH_OWNER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(251) " Packet owner matching allows you to match locally-generated packets based on who created them: the user, group, process or session. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [762]=> array(11) { ["entry_id"]=> string(3) "763" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "netfilter MARK match support" ["name"]=> string(17) "IP6_NF_MATCH_MARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(263) " Netfilter mark matching allows you to match packets based on the `nfmark' value in the packet. This can be set by the MARK target (see below). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [763]=> array(11) { ["entry_id"]=> string(3) "764" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "IPv6 Extension Headers Match (EXPERIMENTAL)" ["name"]=> string(23) "IP6_NF_MATCH_IPV6HEADER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(198) " This module allows one to match packets based upon the ipv6 extension headers. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [764]=> array(11) { ["entry_id"]=> string(3) "765" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "AH/ESP match support (EXPERIMENTAL)" ["name"]=> string(18) "IP6_NF_MATCH_AHESP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(171) " This module allows one to match AH and ESP packets. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [765]=> array(11) { ["entry_id"]=> string(3) "766" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Packet Length match support" ["name"]=> string(19) "IP6_NF_MATCH_LENGTH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(212) " This option allows you to match the length of a packet against a specific value or range of values. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [766]=> array(11) { ["entry_id"]=> string(3) "767" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "EUI64 address check (EXPERIMENTAL)" ["name"]=> string(18) "IP6_NF_MATCH_EUI64" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(251) " This module performs checking on the IPv6 source address Compares the last 64 bits with the EUI64 (delivered from the MAC address) address If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. " } [767]=> array(11) { ["entry_id"]=> string(3) "768" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Packet filtering" ["name"]=> string(13) "IP6_NF_FILTER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(298) " Packet filtering defines a table `filter', which has a series of rules for simple packet filtering at local input, forwarding and local output. See the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [768]=> array(11) { ["entry_id"]=> string(3) "769" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "LOG target support" ["name"]=> string(17) "IP6_NF_TARGET_LOG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(254) " This option adds a `LOG' target, which allows you to create rules in any iptables table which records the packet header to the syslog. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [769]=> array(11) { ["entry_id"]=> string(3) "770" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Packet mangling" ["name"]=> string(13) "IP6_NF_MANGLE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(294) " This option adds a `mangle' table to iptables: see the man page for iptables(8). This table is used for various packet alterations which can effect how the packet is routed. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [770]=> array(11) { ["entry_id"]=> string(3) "771" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "MARK target support" ["name"]=> string(18) "IP6_NF_TARGET_MARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(456) " This option adds a `MARK' target, which allows you to create rules in the `mangle' table which alter the netfilter mark (nfmark) field associated with the packet packet prior to routing. This can change the routing method (see `Use netfilter MARK value as routing key') and can also be used by other subsystems to change their behavior. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [771]=> array(11) { ["entry_id"]=> string(3) "772" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "IPsec user configuration interface" ["name"]=> string(9) "XFRM_USER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(99) " Support for IPsec user configuration interface used by native Linux tools. If unsure, say Y. " } [772]=> array(11) { ["entry_id"]=> string(3) "773" ["entry_type"]=> string(4) "MENU" ["text"]=> string(33) "SCTP Configuration (EXPERIMENTAL)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [773]=> array(11) { ["entry_id"]=> string(3) "774" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "IPV6_SCTP__" ["name"]=> string(11) "IPV6_SCTP__" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [774]=> array(11) { ["entry_id"]=> string(3) "775" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "The SCTP Protocol (EXPERIMENTAL)" ["name"]=> string(7) "IP_SCTP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(991) " Stream Control Transmission Protocol From RFC 2960 (http://www.ietf.org/rfc/rfc2960.txt) "SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP. It offers the following services to its users: -- acknowledged error-free non-duplicated transfer of user data, -- data fragmentation to conform to discovered path MTU size, -- sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, -- optional bundling of multiple user messages into a single SCTP packet, and -- network-level fault tolerance through supporting of multi- homing at either or both ends of an association." This protocol support is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called sctp. If you want to compile it as a module, say M here and read . If in doubt, say N. " } [775]=> array(11) { ["entry_id"]=> string(3) "776" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "SCTP: Use old checksum (Adler-32)" ["name"]=> string(12) "SCTP_ADLER32" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(293) " RCF2960 currently specifies the Adler-32 checksum algorithm for SCTP. This has been deprecated and replaced by an algorithm now referred to as crc32c. If you say Y, this will use the Adler-32 algorithm, this might be useful for interoperation with downlevel peers. If unsure, say N. " } [776]=> array(11) { ["entry_id"]=> string(3) "777" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "SCTP: Debug messages" ["name"]=> string(12) "SCTP_DBG_MSG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(181) " If you say Y, this will enable verbose debugging messages. If unsure, say N. However, if you are running into problems, use this option to gather detailed trace information " } [777]=> array(11) { ["entry_id"]=> string(3) "778" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "SCTP: Debug object counts" ["name"]=> string(15) "SCTP_DBG_OBJCNT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(298) " If you say Y, this will enable debugging support for counting the type of objects that are currently allocated. This is useful for identifying memory leaks. If the /proc filesystem is enabled this debug information can be viewed by 'cat /proc/net/sctp/sctp_dbg_objcnt' If unsure, say N " } [778]=> array(11) { ["entry_id"]=> string(3) "779" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "SCTP_HMAC_NONE" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(4) "None" ["help_text"]=> NULL } [779]=> array(11) { ["entry_id"]=> string(3) "780" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(14) "SCTP_HMAC_SHA1" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(9) "HMAC-SHA1" ["help_text"]=> NULL } [780]=> array(11) { ["entry_id"]=> string(3) "781" ["entry_type"]=> string(6) "OPTION" ["text"]=> NULL ["name"]=> string(13) "SCTP_HMAC_MD5" ["value"]=> string(1) "0" ["type"]=> NULL ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(8) "HMAC-MD5" ["help_text"]=> NULL } [781]=> array(11) { ["entry_id"]=> string(3) "782" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Asynchronous Transfer Mode (ATM) (EXPERIMENTAL)" ["name"]=> string(3) "ATM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(528) " ATM is a high-speed networking technology for Local Area Networks and Wide Area Networks. It uses a fixed packet size and is connection oriented, allowing for the negotiation of minimum bandwidth requirements. In order to participate in an ATM network, your Linux box needs an ATM networking card. If you have that, say Y here and to the driver of your ATM card below. Note that you need a set of user-space programs to actually make use of ATM. See the file for further details. " } [782]=> array(11) { ["entry_id"]=> string(3) "783" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Classical IP over ATM (EXPERIMENTAL)" ["name"]=> string(8) "ATM_CLIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(217) " Classical IP over ATM for PVCs and SVCs, supporting InARP and ATMARP. If you want to communication with other IP hosts on your ATM network, you will typically either say Y here or to "LAN Emulation (LANE)" below. " } [783]=> array(11) { ["entry_id"]=> string(3) "784" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Do NOT send ICMP if no neighbour (EXPERIMENTAL)" ["name"]=> string(16) "ATM_CLIP_NO_ICMP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(318) " Normally, an "ICMP host unreachable" message is sent if a neighbour cannot be reached because there is no VC to it in the kernel's ATMARP table. This may cause problems when ATMARP table entries are briefly removed during revalidation. If you say Y here, packets to such neighbours are silently discarded instead. " } [784]=> array(11) { ["entry_id"]=> string(3) "785" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "LAN Emulation (LANE) support (EXPERIMENTAL)" ["name"]=> string(8) "ATM_LANE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(272) " LAN Emulation emulates services of existing LANs across an ATM network. Besides operating as a normal ATM end station client, Linux LANE client can also act as an proxy client bridging packets between ELAN and Ethernet segments. You need LANE if you want to try MPOA. " } [785]=> array(11) { ["entry_id"]=> string(3) "786" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "Multi-Protocol Over ATM (MPOA) support (EXPERIMENTAL)" ["name"]=> string(8) "ATM_MPOA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(236) " Multi-Protocol Over ATM allows ATM edge devices such as routers, bridges and ATM attached hosts establish direct ATM VCs across subnetwork boundaries. These shortcut connections bypass routers enhancing overall network performance. " } [786]=> array(11) { ["entry_id"]=> string(3) "787" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "RFC1483/2684 Bridged protocols" ["name"]=> string(10) "ATM_BR2684" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(273) " ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483) This device will act like an ethernet from the kernels point of view, with the traffic being carried by ATM PVCs (currently 1 PVC/device). This is sometimes used over DSL lines. If in doubt, say N. " } [787]=> array(11) { ["entry_id"]=> string(3) "788" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Per-VC IP filter kludge" ["name"]=> string(19) "ATM_BR2684_IPFILTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(174) " This is an experimental mechanism for users who need to terminating a large number of IP-only vcc's. Do not enable this unless you are sure you know what you are doing. " } [788]=> array(11) { ["entry_id"]=> string(3) "789" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "802.1Q VLAN Support" ["name"]=> string(10) "VLAN_8021Q" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [789]=> array(11) { ["entry_id"]=> string(3) "790" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(54) "ANSI/IEEE 802.2 - aka LLC (IPX, Appletalk, Token Ring)" ["name"]=> string(3) "LLC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(375) " This is a Logical Link Layer protocol used for Appletalk, IPX, Token Ring devices, the linux-sna.org project and in the future by NetBEUI. It originally came from Procom Inc. that released the code for 2.0.36 and was heavily modified to work with 2.{4,5}. Select this if you want to have support for those protocols or if you want to have the sockets interface for LLC. " } [790]=> array(11) { ["entry_id"]=> string(3) "791" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "LLC sockets interface" ["name"]=> string(6) "LLC_UI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [791]=> array(11) { ["entry_id"]=> string(3) "801" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "IP to Appletalk-IP Encapsulation support" ["name"]=> string(11) "IPDDP_ENCAP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(452) " If you say Y here, the AppleTalk-IP code will be able to encapsulate IP packets inside AppleTalk frames; this is useful if your Linux box is stuck on an AppleTalk network (which hopefully contains a decapsulator somewhere). Please see for more information. If you said Y to "AppleTalk-IP driver support" above and you say Y here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation support", below. " } [792]=> array(11) { ["entry_id"]=> string(3) "802" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Appletalk-IP to IP Decapsulation support" ["name"]=> string(11) "IPDDP_DECAP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(432) " If you say Y here, the AppleTalk-IP code will be able to decapsulate AppleTalk-IP frames to IP packets; this is useful if you want your Linux box to act as an Internet gateway for an AppleTalk network. Please see for more information. If you said Y to "AppleTalk-IP driver support" above and you say Y here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation support", above. " } [793]=> array(11) { ["entry_id"]=> string(3) "792" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "The IPX protocol" ["name"]=> string(3) "IPX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1524) " This is support for the Novell networking protocol, IPX, commonly used for local networks of Windows machines. You need it if you want to access Novell NetWare file or print servers using the Linux Novell client ncpfs (available from ) or from within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from ). In order to do the former, you'll also have to say Y to "NCP file system support", below. IPX is similar in scope to IP, while SPX, which runs on top of IPX, is similar to TCP. There is also experimental support for SPX in Linux (see "SPX networking", below). To turn your Linux box into a fully featured NetWare file server and IPX router, say Y here and fetch either lwared from or mars_nwe from . For more information, read the IPX-HOWTO available from . General information about how to connect Linux, Windows machines and Macs is on the WWW at . The IPX driver would enlarge your kernel by about 16 KB. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ipx. If you want to compile it as a module, say M here and read . Unless you want to integrate your Linux box with a local Novell network, say N. " } [794]=> array(11) { ["entry_id"]=> string(3) "793" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "IPX: Full internal IPX network" ["name"]=> string(10) "IPX_INTERN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(1356) " Every IPX network has an address that identifies it. Sometimes it is useful to give an IPX "network" address to your Linux box as well (for example if your box is acting as a file server for different IPX networks: it will then be accessible from everywhere using the same address). The way this is done is to create a virtual internal "network" inside your box and to assign an IPX address to this network. Say Y here if you want to do this; read the IPX-HOWTO at for details. The full internal IPX network enables you to allocate sockets on different virtual nodes of the internal network. This is done by evaluating the field sipx_node of the socket address given to the bind call. So applications should always initialize the node field to 0 when binding a socket on the primary network. In this case the socket is assigned the default node that has been given to the kernel when the internal network was created. By enabling the full internal IPX network the cross-forwarding of packets targeted at 'special' sockets to sockets listening on the primary network is disabled. This might break existing applications, especially RIP/SAP daemons. A RIP/SAP daemon that works well with the full internal net can be found on . If you don't know what you are doing, say N. " } [795]=> array(11) { ["entry_id"]=> string(3) "794" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Appletalk protocol support" ["name"]=> string(5) "ATALK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1347) " AppleTalk is the protocol that Apple computers can use to communicate on a network. If your Linux box is connected to such a network and you wish to connect to it, say Y. You will need to use the netatalk package so that your Linux box can act as a print and file server for Macs as well as access AppleTalk printers. Check out on the WWW for details. EtherTalk is the name used for AppleTalk over Ethernet and the cheaper and slower LocalTalk is AppleTalk over a proprietary Apple network using serial links. EtherTalk and LocalTalk are fully supported by Linux. General information about how to connect Linux, Windows machines and Macs is on the WWW at . The NET-3-HOWTO, available from , contains valuable information as well. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called appletalk. If you want to compile it as a module, say M here and read . You almost certainly want to compile it as a module so you can restart your AppleTalk stack without rebooting your machine. I hear that the GNU boycott of Apple is over, so even politically correct people are allowed to say Y here. " } [796]=> array(11) { ["entry_id"]=> string(3) "795" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Appletalk interfaces support" ["name"]=> string(13) "DEV_APPLETALK" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(259) " AppleTalk is the protocol that Apple computers can use to communicate on a network. If your Linux box is connected to such a network, and wish to do IP over it, or you have a LocalTalk card and wish to use it to connect to the AppleTalk network, say Y. " } [797]=> array(11) { ["entry_id"]=> string(3) "796" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Apple/Farallon LocalTalk PC support" ["name"]=> string(4) "LTPC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(389) " This allows you to use the AppleTalk PC card to connect to LocalTalk networks. The card is also known as the Farallon PhoneNet PC card. If you are in doubt, this card is the one with the 65C02 chip on it. You also need version 1.3.3 or later of the netatalk package. This driver is experimental, which means that it may not work. See the file . " } [798]=> array(11) { ["entry_id"]=> string(3) "797" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "COPS LocalTalk PC support" ["name"]=> string(4) "COPS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(354) " This allows you to use COPS AppleTalk cards to connect to LocalTalk networks. You also need version 1.3.3 or later of the netatalk package. This driver is experimental, which means that it may not work. This driver will only work if you choose "AppleTalk DDP" networking support, above. Please read the file . " } [799]=> array(11) { ["entry_id"]=> string(3) "798" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Dayna firmware support" ["name"]=> string(10) "COPS_DAYNA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(167) " Support COPS compatible cards with Dayna style firmware (Dayna DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC III, Farallon PhoneNET PC II). " } [800]=> array(11) { ["entry_id"]=> string(3) "799" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Tangent firmware support" ["name"]=> string(12) "COPS_TANGENT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(119) " Support COPS compatible cards with Tangent style firmware (Tangent ATB_II, Novell NL-1000, Daystar Digital LT-200. " } [801]=> array(11) { ["entry_id"]=> string(3) "800" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Appletalk-IP driver support" ["name"]=> string(5) "IPDDP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(1087) " This allows IP networking for users who only have AppleTalk networking available. This feature is experimental. With this driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux box is stuck on an AppleTalk only network) or decapsulate (e.g. if you want your Linux box to act as an Internet gateway for a zoo of AppleTalk connected Macs). Please see the file for more information. If you say Y here, the AppleTalk-IP support will be compiled into the kernel. In this case, you can either use encapsulation or decapsulation, but not both. With the following two questions, you decide which one you want. If you say M here, the AppleTalk-IP support will be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want, read ). The module is called ipddp. In this case, you will be able to use both encapsulation and decapsulation simultaneously, by loading two copies of the module and specifying different values for the module option ipddp_mode. " } [802]=> array(11) { ["entry_id"]=> string(3) "803" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "DECnet Support" ["name"]=> string(6) "DECNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(796) " The DECnet networking protocol was used in many products made by Digital (now Compaq). It provides reliable stream and sequenced packet communications over which run a variety of services similar to those which run over TCP/IP. To find some tools to use with the kernel layer support, please look at Patrick Caulfield's web site: . More detailed documentation is available in . Be sure to say Y to "/proc file system support" and "Sysctl support" below when using DECnet, since you will need sysctl support to aid in configuration at run time. The DECnet code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called decnet. " } [803]=> array(11) { ["entry_id"]=> string(3) "804" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "DECnet: SIOCGIFCONF support" ["name"]=> string(18) "DECNET_SIOCGIFCONF" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(261) " This option should only be turned on if you are really sure that you know what you are doing. It can break other applications which use this system call and the proper way to get the information provided by this call is to use rtnetlink. If unsure, say N. " } [804]=> array(11) { ["entry_id"]=> string(3) "805" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "DECnet: router support (EXPERIMENTAL)" ["name"]=> string(13) "DECNET_ROUTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(587) " Add support for turning your DECnet Endnode into a level 1 or 2 router. This is an experimental, but functional option. If you do say Y here, then make sure that you also say Y to "Kernel/User network link driver", "Routing messages" and "Network packet filtering". The first two are required to allow configuration via rtnetlink (you will need Alexey Kuznetsov's iproute2 package from ). The "Network packet filtering" option will be required for the forthcoming routing daemon to work. See for more information. " } [805]=> array(11) { ["entry_id"]=> string(3) "806" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(54) "DECnet: use FWMARK value as routing key (EXPERIMENTAL)" ["name"]=> string(19) "DECNET_ROUTE_FWMARK" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(164) " If you say Y here, you will be able to specify different routes for packets with different FWMARK ("firewalling mark") values (see ipchains(8), "-m" argument). " } [806]=> array(11) { ["entry_id"]=> string(3) "807" ["entry_type"]=> string(4) "MENU" ["text"]=> string(31) "DECnet: Netfilter Configuration" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [807]=> array(11) { ["entry_id"]=> string(3) "808" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(56) "Routing message grabulator (for userland routing daemon)" ["name"]=> string(20) "DECNET_NF_GRABULATOR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(201) " Enable this module if you want to use the userland DECnet routing daemon. You will also need to enable routing support for DECnet unless you just want to monitor routing messages from other nodes. " } [808]=> array(11) { ["entry_id"]=> string(3) "809" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "802.1d Ethernet Bridging" ["name"]=> string(6) "BRIDGE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1118) " If you say Y here, then your Linux box will be able to act as an Ethernet bridge, which means that the different Ethernet segments it is connected to will appear as one Ethernet to the participants. Several such bridges can work together to create even larger networks of Ethernets using the IEEE 802.1 spanning tree algorithm. As this is a standard, Linux bridges will cooperate properly with other third party bridge products. In order to use the Ethernet bridge, you'll need the bridge configuration tools; see for location. Please read the Bridge mini-HOWTO for more information. If you enable iptables support along with the bridge support then you turn your bridge into a bridging firewall. iptables will then see the IP packets being bridged, so you need to take this into account when setting up your firewall rules. If you want to compile this code as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called bridge. If unsure, say N. " } [809]=> array(11) { ["entry_id"]=> string(3) "810" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Bridge: ebtables" ["name"]=> string(18) "BRIDGE_NF_EBTABLES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [810]=> array(11) { ["entry_id"]=> string(3) "811" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ebt: filter table support" ["name"]=> string(19) "BRIDGE_EBT_T_FILTER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(264) " The ebtables filter table is used to define frame filtering rules at local input, forwarding and local output. See the man page for ebtables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [811]=> array(11) { ["entry_id"]=> string(3) "812" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "ebt: nat table support" ["name"]=> string(16) "BRIDGE_EBT_T_NAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(288) " The ebtables nat table is used to define rules that alter the MAC source address (MAC SNAT) or the MAC destination address (MAC DNAT). See the man page for ebtables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [812]=> array(11) { ["entry_id"]=> string(3) "813" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "ebt: broute table support" ["name"]=> string(17) "BRIDGE_EBT_BROUTE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(334) " The ebtables broute table is used to define rules that decide between bridging and routing frames, giving Linux the functionality of a brouter. See the man page for ebtables(8) and examples on the ebtables website. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [813]=> array(11) { ["entry_id"]=> string(3) "814" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "ebt: log support" ["name"]=> string(14) "BRIDGE_EBT_LOG" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(247) " This option adds the log target, that you can use in any rule in any ebtables table. It records the frame header to the syslog. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [814]=> array(11) { ["entry_id"]=> string(3) "815" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "ebt: IP filter support" ["name"]=> string(13) "BRIDGE_EBT_IP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(196) " This option adds the IP match, which allows basic IP header field filtering. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [815]=> array(11) { ["entry_id"]=> string(3) "816" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "ebt: ARP filter support" ["name"]=> string(14) "BRIDGE_EBT_ARP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(201) " This option adds the ARP match, which allows ARP and RARP header field filtering. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [816]=> array(11) { ["entry_id"]=> string(3) "817" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "ebt: 802.1Q VLAN filter support" ["name"]=> string(15) "BRIDGE_EBT_VLAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(209) " This option adds the 802.1Q vlan match, which allows the filtering of 802.1Q vlan fields. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [817]=> array(11) { ["entry_id"]=> string(3) "818" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "ebt: mark filter support" ["name"]=> string(15) "BRIDGE_EBT_MARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(337) " This option adds the mark match, which allows matching frames based on the 'nfmark' value in the frame. This can be set by the mark target. This value is the same as the one used in the iptables mark match and target. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [818]=> array(11) { ["entry_id"]=> string(3) "819" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "ebt: packet type filter support" ["name"]=> string(18) "BRIDGE_EBT_PKTTYPE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(344) " This option adds the packet type match, which allows matching on the type of packet based on its Ethernet "class" (as determined by the generic networking code): broadcast, multicast, for this host alone or for another host. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [819]=> array(11) { ["entry_id"]=> string(3) "820" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "ebt: STP filter support" ["name"]=> string(14) "BRIDGE_EBT_STP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(211) " This option adds the Spanning Tree Protocol match, which allows STP header field filtering. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [820]=> array(11) { ["entry_id"]=> string(3) "821" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "ebt: snat target support" ["name"]=> string(15) "BRIDGE_EBT_SNAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(213) " This option adds the MAC SNAT target, which allows altering the MAC source address of frames. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [821]=> array(11) { ["entry_id"]=> string(3) "822" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "ebt: dnat target support" ["name"]=> string(15) "BRIDGE_EBT_DNAT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(218) " This option adds the MAC DNAT target, which allows altering the MAC destination address of frames. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [822]=> array(11) { ["entry_id"]=> string(3) "823" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "ebt: redirect target support" ["name"]=> string(19) "BRIDGE_EBT_REDIRECT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(259) " This option adds the MAC redirect target, which allows altering the MAC destination address of a frame to that of the device it arrived on. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [823]=> array(11) { ["entry_id"]=> string(3) "824" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "ebt: mark target support" ["name"]=> string(17) "BRIDGE_EBT_MARK_T" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(304) " This option adds the mark target, which allows marking frames by setting the 'nfmark' value in the frame. This value is the same as the one used in the iptables mark match and target. If you want to compile it as a module, say M here and read . If unsure, say `N'. " } [824]=> array(11) { ["entry_id"]=> string(3) "825" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "CCITT X.25 Packet Layer (EXPERIMENTAL)" ["name"]=> string(3) "X25" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1639) " X.25 is a set of standardized network protocols, similar in scope to frame relay; the one physical line from your box to the X.25 network entry point can carry several logical point-to-point connections (called "virtual circuits") to other computers connected to the X.25 network. Governments, banks, and other organizations tend to use it to connect to each other or to form Wide Area Networks (WANs). Many countries have public X.25 networks. X.25 consists of two protocols: the higher level Packet Layer Protocol (PLP) (say Y here if you want that) and the lower level data link layer protocol LAPB (say Y to "LAPB Data Link Driver" below if you want that). You can read more about X.25 at and . Information about X.25 for Linux is contained in the files and . One connects to an X.25 network either with a dedicated network card using the X.21 protocol (not yet supported by Linux) or one can do X.25 over a standard telephone line using an ordinary modem (say Y to "X.25 async driver" below) or over Ethernet using an ordinary Ethernet card and either the 802.2 LLC protocol (say Y to "802.2 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver" and "LAPB over Ethernet driver" below). If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called x25. If unsure, say N. " } [825]=> array(11) { ["entry_id"]=> string(3) "826" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "LAPB Data Link Driver (EXPERIMENTAL)" ["name"]=> string(4) "LAPB" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(888) " Link Access Procedure, Balanced (LAPB) is the data link layer (i.e. the lower) part of the X.25 protocol. It offers a reliable connection service to exchange data frames with one other host, and it is used to transport higher level protocols (mostly X.25 Packet Layer, the higher part of X.25, but others are possible as well). Usually, LAPB is used with specialized X.21 network cards, but Linux currently supports LAPB only over Ethernet connections. If you want to use LAPB connections over Ethernet, say Y here and to "LAPB over Ethernet driver" below. Read for technical details. If you want to compile this driver as a module though ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called lapb. If unsure, say N. " } [826]=> array(11) { ["entry_id"]=> string(3) "827" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Frame Diverter (EXPERIMENTAL)" ["name"]=> string(10) "NET_DIVERT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(761) " The Frame Diverter allows you to divert packets from the network, that are not aimed at the interface receiving it (in promisc. mode). Typically, a Linux box setup as an Ethernet bridge with the Frames Diverter on, can do some *really* transparent www caching using a Squid proxy for example. This is very useful when you don't want to change your router's config (or if you simply don't have access to it). The other possible usages of diverting Ethernet Frames are numberous: - reroute smtp traffic to another interface - traffic-shape certain network streams - transparently proxy smtp connections - etc... For more informations, please refer to: If unsure, say N. " } [827]=> array(11) { ["entry_id"]=> string(3) "828" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Acorn Econet/AUN protocols (EXPERIMENTAL)" ["name"]=> string(6) "ECONET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(780) " Econet is a fairly old and slow networking protocol mainly used by Acorn computers to access file and print servers. It uses native Econet network cards. AUN is an implementation of the higher level parts of Econet that runs over ordinary Ethernet connections, on top of the UDP packet protocol, which in turn runs on top of the Internet protocol IP. If you say Y here, you can choose with the next two options whether to send Econet/AUN traffic over a UDP Ethernet connection or over a native Econet network card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called econet. If you want to compile it as a module, say M here and read . " } [828]=> array(11) { ["entry_id"]=> string(3) "829" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "AUN over UDP" ["name"]=> string(13) "ECONET_AUNUDP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(195) " Say Y here if you want to send Econet/AUN traffic over a UDP connection (UDP is a packet based protocol that runs on top of the Internet protocol IP) using an ordinary Ethernet network card. " } [829]=> array(11) { ["entry_id"]=> string(3) "830" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "Native Econet" ["name"]=> string(13) "ECONET_NATIVE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(84) " Say Y here if you have a native Econet network card installed in your computer. " } [830]=> array(11) { ["entry_id"]=> string(3) "831" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "WAN router" ["name"]=> string(10) "WAN_ROUTER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1175) " Wide Area Networks (WANs), such as X.25, frame relay and leased lines, are used to interconnect Local Area Networks (LANs) over vast distances with data transfer rates significantly higher than those achievable with commonly used asynchronous modem connections. Usually, a quite expensive external device called a `WAN router' is needed to connect to a WAN. As an alternative, WAN routing can be built into the Linux kernel. With relatively inexpensive WAN interface cards available on the market, a perfectly usable router can be built for less than half the price of an external router. If you have one of those cards and wish to use your Linux box as a WAN router, say Y here and also to the WAN driver for your card, below. You will then need the wan-tools package which is available from . Read for more information. The WAN routing support is also available as a module called wanrouter ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . If unsure, say N. " } [831]=> array(11) { ["entry_id"]=> string(3) "832" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Fast switching (read help!)" ["name"]=> string(13) "NET_FASTROUTE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(612) " Saying Y here enables direct NIC-to-NIC (NIC = Network Interface Card) data transfers on the local network, which is fast. IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet filtering" (CONFIG_NETFILTER). Say N here if you say Y there. However, it will work with all options in the "Advanced router" section (except for "Use TOS value as routing key" and "Use FWMARK value as routing key"). At the moment, few devices support fast switching (tulip is one of them, a modified 8390 driver can be found at ). If unsure, say N. " } [832]=> array(11) { ["entry_id"]=> string(3) "833" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Forwarding between high speed interfaces" ["name"]=> string(18) "NET_HW_FLOWCONTROL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(548) " This option enables NIC (Network Interface Card) hardware throttling during periods of extremal congestion. At the moment only a couple of device drivers support it (really only one -- tulip, a modified 8390 driver can be found at ). Really, this option is applicable to any machine attached to a fast enough network, and even a 10 Mb NIC is able to kill a not very slow box, such as a 120MHz Pentium. However, do not say Y here if you did not experience any serious problems. " } [833]=> array(11) { ["entry_id"]=> string(3) "834" ["entry_type"]=> string(4) "MENU" ["text"]=> string(24) "QoS and/or fair queueing" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [834]=> array(11) { ["entry_id"]=> string(3) "835" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "QoS and/or fair queueing" ["name"]=> string(9) "NET_SCHED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1661) " When the kernel has several packets to send out over a network device, it has to decide which ones to send first, which ones to delay, and which ones to drop. This is the job of the packet scheduler, and several different algorithms for how to do this "fairly" have been proposed. If you say N here, you will get the standard packet scheduler, which is a FIFO (first come, first served). If you say Y here, you will be able to choose from among several alternative algorithms which can then be attached to different network devices. This is useful for example if some of your network devices are real time devices that need a certain minimum data flow rate, or if you need to limit the maximum data flow rate for traffic which matches specified criteria. This code is considered to be experimental. To administer these schedulers, you'll need the user-level utilities from the package iproute2+tc at . That package also contains some documentation; for more, check out . This Quality of Service (QoS) support will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router if you also say Y to "QoS support", "Packet classifier API" and to some classifiers below. Documentation and software is at . If you say Y here and to "/proc file system" below, you will be able to read status information about packet schedulers from the file /proc/net/psched. The available schedulers are listed in the following questions; you can say Y to as many as you like. If unsure, say N now. " } [835]=> array(11) { ["entry_id"]=> string(3) "836" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "CBQ packet scheduler" ["name"]=> string(11) "NET_SCH_CBQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1017) " Say Y here if you want to use the Class-Based Queueing (CBQ) packet scheduling algorithm for some of your network devices. This algorithm classifies the waiting packets into a tree-like hierarchy of classes; the leaves of this tree are in turn scheduled by separate algorithms (called "disciplines" in this context). See the top of for references about the CBQ algorithm. CBQ is a commonly used scheduler, so if you're unsure, you should say Y here. Then say Y to all the queueing algorithms below that you want to use as CBQ disciplines. Then say Y to "Packet classifier API" and say Y to all the classifiers you want to use; a classifier is a routine that allows you to sort your outgoing traffic into classes based on a certain criterion. This code is also available as a module called sch_cbq ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [836]=> array(11) { ["entry_id"]=> string(3) "837" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "HTB packet scheduler" ["name"]=> string(11) "NET_SCH_HTB" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(574) " Say Y here if you want to use the Hierarchical Token Buckets (HTB) packet scheduling algorithm for some of your network devices. See URL http://luxik.cdi.cz/~devik/qos/htb/ for complete manual and in-depth articles. HTB is very similar to the CBQ regarding its goals however is has different properties and different algorithm. This code is also available as a module called sch_htb ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [837]=> array(11) { ["entry_id"]=> string(3) "838" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "CSZ packet scheduler" ["name"]=> string(11) "NET_SCH_CSZ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(597) " Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet scheduling algorithm for some of your network devices. At the moment, this is the only algorithm that can guarantee service for real-time applications (see the top of for details and references about the algorithm). Note: this scheduler is currently broken. This code is also available as a module called sch_csz ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [838]=> array(11) { ["entry_id"]=> string(3) "839" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "ATM pseudo-scheduler" ["name"]=> string(11) "NET_SCH_ATM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(541) " Say Y here if you want to use the ATM pseudo-scheduler. This provides a framework for invoking classifiers (aka "filters"), which in turn select classes of this queuing discipline. Each class maps the flow(s) it is handling to a given virtual circuit (see the top of ). This code is also available as a module called sch_atm ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [839]=> array(11) { ["entry_id"]=> string(3) "840" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "The simplest PRIO pseudoscheduler" ["name"]=> string(12) "NET_SCH_PRIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(427) " Say Y here if you want to use an n-band priority queue packet "scheduler" for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm. If unsure, say Y. This code is also available as a module called sch_prio ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [840]=> array(11) { ["entry_id"]=> string(3) "841" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "RED queue" ["name"]=> string(11) "NET_SCH_RED" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(460) " Say Y here if you want to use the Random Early Detection (RED) packet scheduling algorithm for some of your network devices (see the top of for details and references about the algorithm). This code is also available as a module called sch_red ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [841]=> array(11) { ["entry_id"]=> string(3) "842" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "SFQ queue" ["name"]=> string(11) "NET_SCH_SFQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(526) " Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm (see the top of for details and references about the SFQ algorithm). This code is also available as a module called sch_sfq ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [842]=> array(11) { ["entry_id"]=> string(3) "843" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "TEQL queue" ["name"]=> string(12) "NET_SCH_TEQL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(582) " Say Y here if you want to use the True Link Equalizer (TLE) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm. This queueing discipline allows the combination of several physical devices into one virtual device. (see the top of for details). This code is also available as a module called sch_teql ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [843]=> array(11) { ["entry_id"]=> string(3) "844" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "TBF queue" ["name"]=> string(11) "NET_SCH_TBF" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(512) " Say Y here if you want to use the Simple Token Bucket Filter (TBF) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm (see the top of for a description of the TBF algorithm). This code is also available as a module called sch_tbf ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [844]=> array(11) { ["entry_id"]=> string(3) "845" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "GRED queue" ["name"]=> string(12) "NET_SCH_GRED" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(468) " Say Y here if you want to use the Generic Random Early Detection (RED) packet scheduling algorithm for some of your network devices (see the top of for details and references about the algorithm). This code is also available as a module called sch_gred ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [845]=> array(11) { ["entry_id"]=> string(3) "846" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Diffserv field marker" ["name"]=> string(14) "NET_SCH_DSMARK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(485) " Say Y if you want to schedule packets according to the Differentiated Services architecture proposed in RFC 2475. Technical information on this method, with pointers to associated RFCs, is available at . This code is also available as a module called sch_dsmark ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [846]=> array(11) { ["entry_id"]=> string(3) "847" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "Ingress Qdisc" ["name"]=> string(15) "NET_SCH_INGRESS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(395) " If you say Y here, you will be able to police incoming bandwidth and drop packets when this bandwidth exceeds your desired rate. If unsure, say Y. This code is also available as a module called cls_ingress ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [847]=> array(11) { ["entry_id"]=> string(3) "848" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "QoS support" ["name"]=> string(7) "NET_QOS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(641) " Say Y here if you want to include Quality Of Service scheduling features, which means that you will be able to request certain rate-of-flow limits for your network devices. This Quality of Service (QoS) support will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router if you also say Y to "Packet classifier API" and to some classifiers below. Documentation and software is at . Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about QoS support. " } [848]=> array(11) { ["entry_id"]=> string(3) "849" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "Rate estimator" ["name"]=> string(13) "NET_ESTIMATOR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(172) " In order for Quality of Service scheduling to work, the current rate-of-flow for a network device has to be estimated; if you say Y here, the kernel will do just that. " } [849]=> array(11) { ["entry_id"]=> string(3) "850" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Packet classifier API" ["name"]=> string(7) "NET_CLS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(470) " The CBQ scheduling algorithm requires that network packets which are scheduled to be sent out over a network device be classified according to some criterion. If you say Y here, you will get a choice of several different packet classifiers with the following questions. This will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router. Documentation and software is at . " } [850]=> array(11) { ["entry_id"]=> string(3) "851" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "TC index classifier" ["name"]=> string(15) "NET_CLS_TCINDEX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(468) " If you say Y here, you will be able to classify outgoing packets according to the tc_index field of the skb. You will want this feature if you want to implement Differentiated Services using sch_dsmark. If unsure, say Y. This code is also available as a module called cls_tcindex ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [851]=> array(11) { ["entry_id"]=> string(3) "852" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Routing table based classifier" ["name"]=> string(14) "NET_CLS_ROUTE4" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(378) " If you say Y here, you will be able to classify outgoing packets according to the route table entry they matched. If unsure, say Y. This code is also available as a module called cls_route ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [852]=> array(11) { ["entry_id"]=> string(3) "853" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "NET_CLS_ROUTE" ["name"]=> string(13) "NET_CLS_ROUTE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> NULL } [853]=> array(11) { ["entry_id"]=> string(3) "854" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Firewall based classifier" ["name"]=> string(10) "NET_CLS_FW" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(354) " If you say Y here, you will be able to classify outgoing packets according to firewall criteria you specified. This code is also available as a module called cls_fw ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [854]=> array(11) { ["entry_id"]=> string(3) "855" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "U32 classifier" ["name"]=> string(11) "NET_CLS_U32" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(367) " If you say Y here, you will be able to classify outgoing packets according to their destination address. If unsure, say Y. This code is also available as a module called cls_u32 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [855]=> array(11) { ["entry_id"]=> string(3) "856" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Special RSVP classifier" ["name"]=> string(12) "NET_CLS_RSVP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(537) " The Resource Reservation Protocol (RSVP) permits end systems to request a minimum and maximum data flow rate for a connection; this is important for real time data such as streaming sound or video. Say Y here if you want to be able to classify outgoing packets based on their RSVP requests. This code is also available as a module called cls_rsvp ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [856]=> array(11) { ["entry_id"]=> string(3) "857" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Special RSVP classifier for IPv6" ["name"]=> string(13) "NET_CLS_RSVP6" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(632) " The Resource Reservation Protocol (RSVP) permits end systems to request a minimum and maximum data flow rate for a connection; this is important for real time data such as streaming sound or video. Say Y here if you want to be able to classify outgoing packets based on their RSVP requests and you are using the new Internet Protocol IPv6 as opposed to the older and more common IPv4. This code is also available as a module called cls_rsvp6 ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [857]=> array(11) { ["entry_id"]=> string(3) "858" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Traffic policing (needed for in/egress)" ["name"]=> string(14) "NET_CLS_POLICE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(105) " Say Y to support traffic policing (bandwidth limits). Needed for ingress and egress rate limiting. " } [858]=> array(11) { ["entry_id"]=> string(3) "859" ["entry_type"]=> string(4) "MENU" ["text"]=> string(15) "Network testing" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [859]=> array(11) { ["entry_id"]=> string(3) "860" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Packet Generator (USE WITH CAUTION)" ["name"]=> string(10) "NET_PKTGEN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(595) " This module will inject preconfigured packets, at a configurable rate, out of a given interface. It is used for network interface stress testing and performance analysis. If you don't understand what was just said, you don't need it: say N. Documentation on how to use the packet generaor can be found at . This code is also available as a module called pktgen ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [860]=> array(11) { ["entry_id"]=> string(3) "861" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Network device support" ["name"]=> string(10) "NETDEVICES" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1556) " You can say N here if you don't intend to connect your Linux box to any other computer at all or if all your connections will be over a telephone line with a modem either via UUCP (UUCP is a protocol to forward mail and news between unix hosts over telephone lines; read the UUCP-HOWTO, available from ) or dialing up a shell account or a BBS, even using term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read ). You'll have to say Y if your computer contains a network card that you want to use under Linux (make sure you know its name because you will be asked for it and read the Ethernet-HOWTO (especially if you plan to use more than one network card under Linux)) or if you want to use SLIP (Serial Line Internet Protocol is the protocol used to send Internet traffic over telephone lines or null modem cables) or CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better and newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol is mainly used to create a mini network by connecting the parallel ports of two local machines) or AX.25/KISS (protocol for sending Internet traffic over amateur radio links). Make sure to read the NET-3-HOWTO. Eventually, you will have to read Olaf Kirch's excellent and free book "Network Administrator's Guide", to be found in . If unsure, say Y. " } [861]=> array(11) { ["entry_id"]=> string(3) "862" ["entry_type"]=> string(4) "MENU" ["text"]=> string(14) "ARCnet devices" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [862]=> array(11) { ["entry_id"]=> string(3) "863" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "ARCnet support" ["name"]=> string(6) "ARCNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(829) " If you have a network card of this type, say Y and check out the (arguably) beautiful poetry in . You need both this driver, and the driver for the particular ARCnet chipset of your card. If you don't know, then it's probably a COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset support" below. You might also want to have a look at the Ethernet-HOWTO, available from (even though ARCnet is not really Ethernet). This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called arcnet. If you want to compile it as a module, say M here and read as well as . " } [863]=> array(11) { ["entry_id"]=> string(3) "864" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Enable standard ARCNet packet format (RFC 1201)" ["name"]=> string(11) "ARCNET_1201" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(365) " This allows you to use RFC1201 with your ARCnet card via the virtual arc0 device. You need to say Y here to communicate with industry-standard RFC1201 implementations, like the arcether.com packet driver or most DOS/Windows ODI drivers. Please read the ARCnet documentation in for more information about using arc0. " } [864]=> array(11) { ["entry_id"]=> string(3) "865" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Enable old ARCNet packet format (RFC 1051)" ["name"]=> string(11) "ARCNET_1051" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(630) " This allows you to use RFC1051 with your ARCnet card via the virtual arc0s device. You only need arc0s if you want to talk to ARCnet software complying with the "old" standard, specifically, the DOS arcnet.com packet driver, Amigas running AmiTCP, and some variants of NetBSD. You do not need to say Y here to communicate with industry-standard RFC1201 implementations, like the arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201 is included automatically as the arc0 device. Please read the ARCnet documentation in for more information about using arc0e and arc0s. " } [865]=> array(11) { ["entry_id"]=> string(3) "866" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Enable raw mode packet interface" ["name"]=> string(10) "ARCNET_RAW" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(181) " ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely to work unless talking to a copy of the same Linux arcnet driver, but perhaps marginally faster in that case. " } [866]=> array(11) { ["entry_id"]=> string(3) "867" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "ARCnet COM90xx (normal) chipset driver" ["name"]=> string(14) "ARCNET_COM90xx" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(507) " This is the chipset driver for the standard COM90xx cards. If you have always used the old ARCnet driver without knowing what type of card you had, this is probably the one for you. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called com90xx. If you want to compile it as a module, say M here and read as well as . " } [867]=> array(11) { ["entry_id"]=> string(3) "868" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "ARCnet COM90xx (IO mapped) chipset driver" ["name"]=> string(16) "ARCNET_COM90xxIO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(530) " This is the chipset driver for the COM90xx cards, using them in IO-mapped mode instead of memory-mapped mode. This is slower than the normal driver. Only use it if your card doesn't support shared memory. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called com90io. If you want to compile it as a module, say M here and read as well as . " } [868]=> array(11) { ["entry_id"]=> string(3) "869" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "ARCnet COM90xx (RIM I) chipset driver" ["name"]=> string(12) "ARCNET_RIM_I" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(582) " This is yet another chipset driver for the COM90xx cards, but this time only using memory-mapped mode, and no IO ports at all. This driver is completely untested, so if you have one of these cards, please mail dwmw2@infradead.org, especially if it works! This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called arc-rimi. If you want to compile it as a module, say M here and read as well as . " } [869]=> array(11) { ["entry_id"]=> string(3) "870" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "ARCnet COM20020 chipset driver" ["name"]=> string(15) "ARCNET_COM20020" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(486) " This is the driver for the new COM20020 chipset. It supports such things as promiscuous mode, so packet sniffing is possible, and extra diagnostic information. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called com20020. If you want to compile it as a module, say M here and read as well as . " } [870]=> array(11) { ["entry_id"]=> string(3) "871" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Support for COM20020 on ISA" ["name"]=> string(19) "ARCNET_COM20020_ISA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [871]=> array(11) { ["entry_id"]=> string(3) "872" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Support for COM20020 on PCI" ["name"]=> string(19) "ARCNET_COM20020_PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [872]=> array(11) { ["entry_id"]=> string(3) "873" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Dummy net driver support" ["name"]=> string(5) "DUMMY" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(931) " This is essentially a bit-bucket device (i.e. traffic you send to this device is consigned into oblivion) with a configurable IP address. It is most commonly used in order to make your currently inactive SLIP address seem like a real address for local programs. If you use SLIP or PPP, you might want to say Y here. Since this thing often comes in handy, the default is Y. It won't enlarge your kernel either. What a deal. Read about it in the Network Administrator's Guide, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called dummy. If you want to use more than one dummy device at a time, you need to compile this driver as a module. Instead of 'dummy', the devices will then be called 'dummy0', 'dummy1' etc. " } [873]=> array(11) { ["entry_id"]=> string(3) "874" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Bonding driver support" ["name"]=> string(7) "BONDING" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(784) " Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet Channels together. This is called 'Etherchannel' by Cisco, 'Trunking' by Sun, and 'Bonding' in Linux. If you have two Ethernet connections to some other computer, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar Bonding Linux driver, a Cisco 5500 switch or a SunTrunking SunSoft driver. This is similar to the EQL driver, but it merges Ethernet segments instead of serial lines. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called bonding. " } [874]=> array(11) { ["entry_id"]=> string(3) "875" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "EQL (serial line load balancing) support" ["name"]=> string(9) "EQUALIZER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(914) " If you have two serial connections to some other computer (this usually requires two modems and two telephone lines) and you use SLIP (the protocol for sending Internet traffic over telephone lines) or PPP (a better SLIP) on them, you can make them behave like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you want this and read . You may also want to read section 6.2 of the NET-3-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eql. If you want to compile it as a module, say M here and read . If unsure, say N. " } [875]=> array(11) { ["entry_id"]=> string(3) "876" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Universal TUN/TAP device driver support" ["name"]=> string(3) "TUN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(960) " TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a program opens /dev/net/tun, driver creates and registers corresponding net device tunX or tapX. After a program closed above devices, driver will automatically delete tunXX or tapXX device and all routes corresponding to it. Please read for more information. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tun. If you want to compile it as a module, say M here and read . If you don't know what to use this for, you don't need it. " } [876]=> array(11) { ["entry_id"]=> string(3) "877" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Ethertap network tap (OBSOLETE)" ["name"]=> string(8) "ETHERTAP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(1164) " If you say Y here (and have said Y to "Kernel/User network link driver", above) and create a character special file /dev/tap0 with major number 36 and minor number 16 using mknod ("man mknod"), you will be able to have a user space program read and write raw Ethernet frames from/to that special file. tap0 can be configured with ifconfig and route like any other Ethernet device but it is not connected to any physical LAN; everything written by the user to /dev/tap0 is treated by the kernel as if it had come in from a LAN to the device tap0; everything the kernel wants to send out over the device tap0 can instead be read by the user from /dev/tap0: the user mode program replaces the LAN that would be attached to an ordinary Ethernet device. Please read the file for more information. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ethertap. If you want to compile it as a module, say M here and read . If you don't know what to use this for, you don't need it. " } [877]=> array(11) { ["entry_id"]=> string(3) "878" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "General Instruments Surfboard 1000" ["name"]=> string(10) "NET_SB1000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(849) " This is a driver for the General Instrument (also known as NextLevel) SURFboard 1000 internal cable modem. This is an ISA card which is used by a number of cable TV companies to provide cable modem access. It's a one-way downstream-only cable modem, meaning that your upstream net link is provided by your regular phone modem. At present this driver only compiles as a module, so say M here if you have this card. The module will be called sb1000. Then read for information on how to use this module, as it needs special ppp scripts for establishing a connection. Further documentation and the necessary scripts can be found at: If you don't have this card, of course say N. " } [878]=> array(11) { ["entry_id"]=> string(3) "879" ["entry_type"]=> string(4) "MENU" ["text"]=> string(24) "Ethernet (10 or 100Mbit)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [879]=> array(11) { ["entry_id"]=> string(3) "880" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Ethernet (10 or 100Mbit)" ["name"]=> string(12) "NET_ETHERNET" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1218) " Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common type of Local Area Network (LAN) in universities and companies. Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over coaxial cable, linking computers in a chain), 10BASE-T or twisted pair (10 Mbps over twisted pair cable, linking computers to central hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) [the 100BASE varieties are also known as Fast Ethernet], and Gigabit Ethernet (1 Gbps over optical fiber or short copper links). If your Linux machine will be connected to an Ethernet and you have an Ethernet network interface card (NIC) installed in your computer, say Y here and read the Ethernet-HOWTO, available from . You will then also have to say Y to the driver for your particular NIC. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Ethernet network cards. If unsure, say N. " } [880]=> array(11) { ["entry_id"]=> string(3) "881" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(50) "Generic Media Independent Interface device support" ["name"]=> string(3) "MII" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(161) " Most ethernet controllers have MII transceiver either as an external or internal device. It is safe to say Y or M here even if your ethernet card lack MII. " } [881]=> array(11) { ["entry_id"]=> string(3) "882" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "ARM EBSA110 AM79C961A support" ["name"]=> string(13) "ARM_AM79C961A" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(95) " If you wish to compile a kernel for the EBSA-110, then you should always answer Y to this. " } [882]=> array(11) { ["entry_id"]=> string(3) "883" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Acorn Ether1 support" ["name"]=> string(10) "ARM_ETHER1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(139) " If you have an Acorn system with one of these (AKA25) network cards, you should say Y to this option if you wish to use it with Linux. " } [883]=> array(11) { ["entry_id"]=> string(3) "884" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Acorn/ANT Ether3 support" ["name"]=> string(10) "ARM_ETHER3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(131) " If you have an Acorn system with one of these network cards, you should say Y to this option if you wish to use it with Linux. " } [884]=> array(11) { ["entry_id"]=> string(3) "885" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "I-cubed EtherH/ANT EtherM support" ["name"]=> string(10) "ARM_ETHERH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(131) " If you have an Acorn system with one of these network cards, you should say Y to this option if you wish to use it with Linux. " } [885]=> array(11) { ["entry_id"]=> string(3) "886" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Altera Ether00 support" ["name"]=> string(11) "ARM_ETHER00" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(507) " This is the driver for Altera's ether00 ethernet mac IP core. Say Y here if you want to build support for this into the kernel. It is also available as a module (say M here) that can be inserted/ removed from the kernel at the same time as the PLD is configured. If this driver is running on an epxa10 development board then it will generate a suitable hw address based on the board serial number (MTD support is required for this). Otherwise you will need to set a suitable hw address using ifconfig. " } [886]=> array(11) { ["entry_id"]=> string(3) "887" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "MACE (Power Mac ethernet) support" ["name"]=> string(4) "MACE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(429) " Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. This driver is also available as a module called mace ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [887]=> array(11) { ["entry_id"]=> string(3) "888" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Use AAUI port instead of TP by default" ["name"]=> string(14) "MACE_AAUI_PORT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(395) " Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. " } [888]=> array(11) { ["entry_id"]=> string(3) "889" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "BMAC (G3 ethernet) support" ["name"]=> string(4) "BMAC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(321) " Say Y for support of BMAC Ethernet interfaces. These are used on G3 computers. This driver is also available as a module called bmac ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [889]=> array(11) { ["entry_id"]=> string(3) "890" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "National DP83902AV (Oak ethernet) support" ["name"]=> string(6) "OAKNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(306) " Say Y if your machine has this type of Ethernet network card. This driver is also available as a module called oaknet ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [890]=> array(11) { ["entry_id"]=> string(3) "891" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Ariadne support" ["name"]=> string(7) "ARIADNE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(340) " If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called ariadne. If you want to compile it as a module, say M here and read . " } [891]=> array(11) { ["entry_id"]=> string(3) "892" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "A2065 support" ["name"]=> string(5) "A2065" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(331) " If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called a2065. If you want to compile it as a module, say M here and read . " } [892]=> array(11) { ["entry_id"]=> string(3) "893" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "Hydra support" ["name"]=> string(5) "HYDRA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(321) " If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called hydra. If you want to compile it as a module, say M here and read . " } [893]=> array(11) { ["entry_id"]=> string(3) "894" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Zorro NS8390-based Ethernet support" ["name"]=> string(9) "ZORRO8390" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(475) " This driver is for Zorro Ethernet cards using an NS8390-compatible chipset, like the Village Tronic Ariadne II and the Individual Computers X-Surf Ethernet cards. If you have such a card, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called zorro8390. If you want to compile it as a module, say M here and read . " } [894]=> array(11) { ["entry_id"]=> string(3) "895" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "PCMCIA NE2000 support" ["name"]=> string(4) "APNE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(331) " If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, say N. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called apne. If you want to compile it as a module, say M here and read . " } [895]=> array(11) { ["entry_id"]=> string(3) "896" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Apollo 3c505 support" ["name"]=> string(13) "APOLLO_ELPLUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(240) " Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card. If you don't have one made for Apollos, you can use one from a PC, except that your Apollo won't be able to boot from it (because the code in the ROM will be for a PC). " } [896]=> array(11) { ["entry_id"]=> string(3) "897" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Macintosh NS 8390 based ethernet cards" ["name"]=> string(7) "MAC8390" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(210) " If you want to include a driver to support Nubus or LC-PDS Ethernet cards using an NS8390 chipset or its equivalent, say Y and read the Ethernet-HOWTO, available from . " } [897]=> array(11) { ["entry_id"]=> string(3) "898" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Macintosh CS89x0 based ethernet cards" ["name"]=> string(7) "MAC89x0" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(492) " Support for CS89x0 chipset based Ethernet cards. If you have a Nubus or LC-PDS network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . This module will be called mac89x0. " } [898]=> array(11) { ["entry_id"]=> string(3) "899" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(55) "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" ["name"]=> string(8) "MACSONIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(579) " Support for NatSemi SONIC based Ethernet devices. This includes the onboard Ethernet in many Quadras as well as some LC-PDS, a few Nubus and all known Comm Slot Ethernet cards. If you have one of these say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . This module will be called macsonic. " } [899]=> array(11) { ["entry_id"]=> string(3) "900" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "Macintosh (AV) onboard MACE ethernet (EXPERIMENTAL)" ["name"]=> string(7) "MACMACE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(230) " Support for the onboard AMD 79C940 MACE Ethernet controller used in the 660AV and 840AV Macintosh. If you have one of these Macintoshes say Y and read the Ethernet-HOWTO, available from . " } [900]=> array(11) { ["entry_id"]=> string(3) "901" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "MVME147 (Lance) Ethernet support" ["name"]=> string(11) "MVME147_NET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(254) " Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . " } [901]=> array(11) { ["entry_id"]=> string(3) "902" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "MVME16x Ethernet support" ["name"]=> string(11) "MVME16x_NET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(264) " This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . " } [902]=> array(11) { ["entry_id"]=> string(3) "903" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "BVME6000 Ethernet support" ["name"]=> string(12) "BVME6000_NET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(246) " This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . " } [903]=> array(11) { ["entry_id"]=> string(3) "904" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Atari Lance support" ["name"]=> string(10) "ATARILANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(206) " Say Y to include support for several Atari Ethernet adapters based on the AMD Lance chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). " } [904]=> array(11) { ["entry_id"]=> string(3) "905" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "BioNet-100 support" ["name"]=> string(12) "ATARI_BIONET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(174) " Say Y to include support for BioData's BioNet-100 Ethernet adapter for the ACSI port. The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( " } [905]=> array(11) { ["entry_id"]=> string(3) "906" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "PAMsNet support" ["name"]=> string(13) "ATARI_PAMSNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(179) " Say Y to include support for the PAMsNet Ethernet adapter for the ACSI port ("ACSI node"). The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( " } [906]=> array(11) { ["entry_id"]=> string(3) "907" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Sun3/Sun3x on-board LANCE support" ["name"]=> string(9) "SUN3LANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(385) " Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) featured an AMD Lance 10Mbit Ethernet controller on board; say Y here to compile in the Linux driver for this and enable Ethernet. General Linux information on the Sun 3 and 3x series (now discontinued) is at . If you're not building a kernel for a Sun 3, say N. " } [907]=> array(11) { ["entry_id"]=> string(3) "908" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Sun3 on-board Intel 82586 support" ["name"]=> string(10) "SUN3_82586" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(214) " This driver enables support for the on-board Intel 82586 based Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note that this driver does not support 82586-based adapters on additional VME boards. " } [908]=> array(11) { ["entry_id"]=> string(3) "909" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "HP on-board LANCE support" ["name"]=> string(7) "HPLANCE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(96) " If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. " } [909]=> array(11) { ["entry_id"]=> string(3) "910" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "Lasi ethernet" ["name"]=> string(10) "LASI_82596" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(116) " Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines. " } [910]=> array(11) { ["entry_id"]=> string(3) "911" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "MIPS JAZZ onboard SONIC Ethernet support" ["name"]=> string(15) "MIPS_JAZZ_SONIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(132) " This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. " } [911]=> array(11) { ["entry_id"]=> string(3) "912" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "MIPS GT96100 Ethernet support" ["name"]=> string(15) "MIPS_GT96100ETH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(71) " Say Y here to support the Ethernet subsystem on your GT96100 card. " } [912]=> array(11) { ["entry_id"]=> string(3) "913" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "MIPS AU1000 Ethernet support" ["name"]=> string(16) "MIPS_AU1X00_ENET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(78) " If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N. " } [913]=> array(11) { ["entry_id"]=> string(3) "914" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "SB1250 Ethernet support" ["name"]=> string(14) "NET_SB1250_MAC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [914]=> array(11) { ["entry_id"]=> string(3) "915" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SGI IOC3 Ethernet" ["name"]=> string(12) "SGI_IOC3_ETH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . " } [915]=> array(11) { ["entry_id"]=> string(3) "916" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "SGI O2 MACE Fast Ethernet support" ["name"]=> string(14) "SGI_O2MACE_ETH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [916]=> array(11) { ["entry_id"]=> string(3) "917" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "National DP83902AV support" ["name"]=> string(5) "STNIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(269) " Support for cards based on the National Semiconductor DP83902AV ST-NIC Serial Network Interface Controller for Twisted Pair. This is a 10Mbit/sec Ethernet controller. Product overview and specs at . If unsure, say N. " } [917]=> array(11) { ["entry_id"]=> string(3) "918" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "Sun LANCE support" ["name"]=> string(8) "SUNLANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(468) " This driver supports the "le" interface present on all 32-bit Sparc systems, on some older Ultra systems and as an Sbus option. These cards are based on the AMD Lance chipset, which is better known via the NE2100 cards. This support is also available as a module called sunlance ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [918]=> array(11) { ["entry_id"]=> string(3) "919" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Sun Happy Meal 10/100baseT support" ["name"]=> string(9) "HAPPYMEAL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(508) " This driver supports the "hme" interface present on most Ultra systems and as an option on older Sbus systems. This driver supports both PCI and Sbus devices. This driver also supports the "qfe" quad 100baseT device available in both PCI and Sbus configurations. This support is also available as a module called sunhme ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [919]=> array(11) { ["entry_id"]=> string(3) "920" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Sun BigMAC 10/100baseT support (EXPERIMENTAL)" ["name"]=> string(7) "SUNBMAC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(361) " This driver supports the "be" interface available as an Sbus option. This is Sun's older 100baseT Ethernet device. This support is also available as a module called sunbmac ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [920]=> array(11) { ["entry_id"]=> string(3) "921" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Sun QuadEthernet support" ["name"]=> string(5) "SUNQE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(439) " This driver supports the "qe" 10baseT Ethernet device, available as an Sbus option. Note that this is not the same as Quad FastEthernet "qfe" which is supported by the Happy Meal driver instead. This support is also available as a module called sunqe ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [921]=> array(11) { ["entry_id"]=> string(3) "922" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Sun GEM support" ["name"]=> string(6) "SUNGEM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(152) " Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also . " } [922]=> array(11) { ["entry_id"]=> string(3) "923" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "3COM cards" ["name"]=> string(15) "NET_VENDOR_3COM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(400) " If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from . Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about 3COM cards. If you say Y, you will be asked for your specific card in the following questions. " } [923]=> array(11) { ["entry_id"]=> string(3) "924" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "3c501 "EtherLink" support" ["name"]=> string(3) "EL1" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(677) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Also, consider buying a new card, since the 3c501 is slow, broken, and obsolete: you will have problems. Some people suggest to ping ("man ping") a nearby machine every minute ("man cron") when using this card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c501. If you want to compile it as a module, say M here and read as well as . " } [924]=> array(11) { ["entry_id"]=> string(3) "925" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "3c503 "EtherLink II" support" ["name"]=> string(3) "EL2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(464) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c503. If you want to compile it as a module, say M here and read as well as . " } [925]=> array(11) { ["entry_id"]=> string(3) "926" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "3c505 "EtherLink Plus" support" ["name"]=> string(6) "ELPLUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(511) " Information about this network (Ethernet) card can be found in . If you have a card of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called 3c505. " } [926]=> array(11) { ["entry_id"]=> string(3) "927" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "3c507 "EtherLink 16" support (EXPERIMENTAL)" ["name"]=> string(4) "EL16" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(464) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c507. If you want to compile it as a module, say M here and read as well as . " } [927]=> array(11) { ["entry_id"]=> string(3) "928" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "3c509/3c529 (MCA)/3c569B (98)/3c579 "EtherLink III" support" ["name"]=> string(3) "EL3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(587) " If you have a network (Ethernet) card belonging to the 3Com EtherLinkIII series, say Y and read the Ethernet-HOWTO, available from . If your card is not working you may need to use the DOS setup disk to disable Plug & Play mode, and to select the default media type. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called 3c509. " } [928]=> array(11) { ["entry_id"]=> string(3) "929" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "3c515 ISA "Fast EtherLink"" ["name"]=> string(5) "3C515" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(453) " If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet network card, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called 3c515. " } [929]=> array(11) { ["entry_id"]=> string(3) "930" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "3c523 "EtherLink/MC" support" ["name"]=> string(4) "ELMC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(464) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c523. If you want to compile it as a module, say M here and read as well as . " } [930]=> array(11) { ["entry_id"]=> string(3) "931" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(46) "3c527 "EtherLink/MC 32" support (EXPERIMENTAL)" ["name"]=> string(7) "ELMC_II" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(464) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c527. If you want to compile it as a module, say M here and read as well as . " } [931]=> array(11) { ["entry_id"]=> string(3) "932" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "3c590/3c900 series (592/595/597) "Vortex/Boomerang" support" ["name"]=> string(6) "VORTEX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(933) " This option enables driver support for a large number of 10mbps and 10/100mbps EISA, PCI and PCMCIA 3Com network cards: "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI "Boomerang" (EtherLink XL 3c900 or 3c905) PCI "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus "Tornado" (3c905) PCI "Hurricane" (3c555/3cSOHO) PCI If you have such a card, say Y and read the Ethernet-HOWTO, available from . More specific information is in and in the comments at the beginning of . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . " } [932]=> array(11) { ["entry_id"]=> string(3) "933" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "3cr990 series "Typhoon" support" ["name"]=> string(7) "TYPHOON" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(705) " This option enables driver support for the 3cr990 series of cards: 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server, 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called typhoon.o. If you want to compile it as a module, say M here and read as well as . " } [933]=> array(11) { ["entry_id"]=> string(3) "934" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "AMD LANCE and PCnet (AT1500 and NE2100) support" ["name"]=> string(5) "LANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(430) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Some LinkSys cards are of this type. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called lance. " } [934]=> array(11) { ["entry_id"]=> string(3) "935" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Western Digital/SMC cards" ["name"]=> string(14) "NET_VENDOR_SMC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(411) " If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from . Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Western Digital cards. If you say Y, you will be asked for your specific card in the following questions. " } [935]=> array(11) { ["entry_id"]=> string(3) "936" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "WD80*3 support" ["name"]=> string(6) "WD80x3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(461) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wd. If you want to compile it as a module, say M here and read as well as . " } [936]=> array(11) { ["entry_id"]=> string(3) "937" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "SMC Ultra MCA support" ["name"]=> string(8) "ULTRAMCA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(509) " If you have a network (Ethernet) card of this type and are running an MCA based system (PS/2), say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-mca. If you want to compile it as a module, say M here and read as well as . " } [937]=> array(11) { ["entry_id"]=> string(3) "938" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SMC Ultra support" ["name"]=> string(5) "ULTRA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(815) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Important: There have been many reports that, with some motherboards mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, such as some BusLogic models) causes corruption problems with many operating systems. The Linux smc-ultra driver has a work-around for this but keep it in mind if you have such a SCSI card and have problems. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-ultra. If you want to compile it as a module, say M here and read as well as . " } [938]=> array(11) { ["entry_id"]=> string(3) "939" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "SMC Ultra32 EISA support" ["name"]=> string(7) "ULTRA32" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(470) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc-ultra32. If you want to compile it as a module, say M here and read as well as . " } [939]=> array(11) { ["entry_id"]=> string(3) "940" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "SMC 9194 support" ["name"]=> string(7) "SMC9194" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(674) " This is support for the SMC9xxx based Ethernet cards. Choose this option if you have a DELL laptop with the docking station, or another SMC9192/9194 based chipset. Say Y if you want it compiled into the kernel, and read the file and the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc9194. If you want to compile it as a module, say M here and read as well as . " } [940]=> array(11) { ["entry_id"]=> string(3) "941" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Racal-Interlan (Micom) NI cards" ["name"]=> string(16) "NET_VENDOR_RACAL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(436) " If you have a network (Ethernet) card belonging to this class, such as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, available from . Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about NI cards. If you say Y, you will be asked for your specific card in the following questions. " } [941]=> array(11) { ["entry_id"]=> string(3) "942" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "NI5010 support (EXPERIMENTAL)" ["name"]=> string(6) "NI5010" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(508) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Note that this is still experimental code. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni5010. If you want to compile it as a module, say M here and read as well as . " } [942]=> array(11) { ["entry_id"]=> string(3) "943" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "NI5210 support" ["name"]=> string(4) "NI52" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(463) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni52. If you want to compile it as a module, say M here and read as well as . " } [943]=> array(11) { ["entry_id"]=> string(3) "944" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "NI6510 support" ["name"]=> string(4) "NI65" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(463) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ni65. If you want to compile it as a module, say M here and read as well as . " } [944]=> array(11) { ["entry_id"]=> string(3) "945" ["entry_type"]=> string(4) "MENU" ["text"]=> string(35) "Tulip family network device support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [945]=> array(11) { ["entry_id"]=> string(3) "946" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) ""Tulip" family network device support" ["name"]=> string(9) "NET_TULIP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(63) " This selects the "Tulip" family of EISA/PCI network cards. " } [946]=> array(11) { ["entry_id"]=> string(3) "947" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(56) "Early DECchip Tulip (dc2104x) PCI support (EXPERIMENTAL)" ["name"]=> string(7) "DE2104X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(880) " This driver is developed for the SMC EtherPower series Ethernet cards and also works with cards based on the DECchip 21040 (Tulip series) chips. Some LinkSys PCI cards are of this type. (If your card is NOT SMC EtherPower 10/100 PCI (smc9332dst), you can also try the driver for "Generic DECchip" cards, above. However, most people with a network card of this type will say Y here.) Do read the Ethernet-HOWTO, available from . More specific information is contained in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tulip. If you want to compile it as a module, say M here and read as well as . " } [947]=> array(11) { ["entry_id"]=> string(3) "948" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "DECchip Tulip (dc2114x) PCI support" ["name"]=> string(5) "TULIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(879) " This driver is developed for the SMC EtherPower series Ethernet cards and also works with cards based on the DECchip 21140 (Tulip series) chips. Some LinkSys PCI cards are of this type. (If your card is NOT SMC EtherPower 10/100 PCI (smc9332dst), you can also try the driver for "Generic DECchip" cards, above. However, most people with a network card of this type will say Y here.) Do read the Ethernet-HOWTO, available from . More specific information is contained in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tulip. If you want to compile it as a module, say M here and read as well as . " } [948]=> array(11) { ["entry_id"]=> string(3) "949" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "New bus configuration (EXPERIMENTAL)" ["name"]=> string(9) "TULIP_MWI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(187) " This configures your Tulip card specifically for the card and system cache line size type you are using. This is experimental code, not yet tested on many boards. If unsure, say N. " } [949]=> array(11) { ["entry_id"]=> string(3) "950" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Use PCI shared mem for NIC registers" ["name"]=> string(10) "TULIP_MMIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(230) " Use PCI shared memory for the NIC registers, rather than going through the Tulip's PIO (programmed I/O ports). Faster, but could produce obscure bugs if your mainboard has memory controller timing issues. If in doubt, say N. " } [950]=> array(11) { ["entry_id"]=> string(3) "951" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(51) "Generic DECchip & DIGITAL EtherWORKS PCI/EISA" ["name"]=> string(5) "DE4X5" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(669) " This is support for the DIGITAL series of PCI/EISA Ethernet cards. These include the DE425, DE434, DE435, DE450 and DE500 models. If you have a network card of this type, say Y and read the Ethernet-HOWTO, available from . More specific information is contained in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called de4x5. If you want to compile it as a module, say M here and read as well as . " } [951]=> array(11) { ["entry_id"]=> string(3) "952" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Winbond W89c840 Ethernet support" ["name"]=> string(11) "WINBOND_840" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(219) " This driver is for the Winbond W89c840 chip. It also works with the TX9882 chip on the Compex RL100-ATX board. More specific information and updates are available from . " } [952]=> array(11) { ["entry_id"]=> string(3) "953" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Davicom DM910x/DM980x support" ["name"]=> string(6) "DM9102" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(568) " This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from Davicom (). If you have such a network (Ethernet) card, say Y. Some information is contained in the file . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dmfe. If you want to compile it as a module, say M here and read as well as . " } [953]=> array(11) { ["entry_id"]=> string(3) "954" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Xircom CardBus support (new driver)" ["name"]=> string(13) "PCMCIA_XIRCOM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(494) " This driver is for the Digital "Tulip" Ethernet CardBus adapters. It should work with most DEC 21*4*-based chips/ethercards, as well as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and ASIX. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called xircom_cb. If you want to compile it as a module, say M here and read . If unsure, say N. " } [954]=> array(11) { ["entry_id"]=> string(3) "955" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(46) "Xircom Tulip-like CardBus support (old driver)" ["name"]=> string(15) "PCMCIA_XIRTULIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(500) " This driver is for the Digital "Tulip" Ethernet CardBus adapters. It should work with most DEC 21*4*-based chips/ethercards, as well as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and ASIX. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called xircom_tulip_cb. If you want to compile it as a module, say M here and read . If unsure, say N. " } [955]=> array(11) { ["entry_id"]=> string(3) "956" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(52) "AT1700/1720/RE1000Plus(C-Bus) support (EXPERIMENTAL)" ["name"]=> string(6) "AT1700" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(465) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read as well as . The module will be called at1700. " } [956]=> array(11) { ["entry_id"]=> string(3) "957" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" ["name"]=> string(5) "DEPCA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(461) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from as well as . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called depca. " } [957]=> array(11) { ["entry_id"]=> string(3) "958" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "HP 10/100VG PCLAN (ISA, EISA, PCI) support" ["name"]=> string(5) "HP100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(423) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called hp100. " } [958]=> array(11) { ["entry_id"]=> string(3) "959" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Other ISA cards" ["name"]=> string(7) "NET_ISA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(597) " If your network (Ethernet) card hasn't been mentioned yet and its bus system (that's the way the cards talks to the other components of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. Make sure you know the name of your card. Read the Ethernet-HOWTO, available from . If unsure, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the remaining ISA network card questions. If you say Y, you will be asked for your specific card in the following questions. " } [959]=> array(11) { ["entry_id"]=> string(3) "960" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Cabletron E21xx support" ["name"]=> string(5) "E2100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(464) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e2100. If you want to compile it as a module, say M here and read as well as . " } [960]=> array(11) { ["entry_id"]=> string(3) "961" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "EtherWORKS 3 (DE203, DE204, DE205) support" ["name"]=> string(5) "EWRK3" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(539) " This driver supports the DE203, DE204 and DE205 network (Ethernet) cards. If this is for you, say Y and read in the kernel source as well as the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called ewrk3. " } [961]=> array(11) { ["entry_id"]=> string(3) "962" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "EtherExpress 16 support" ["name"]=> string(8) "EEXPRESS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(607) " If you have an EtherExpress16 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from . Note that the Intel EtherExpress16 card used to be regarded as a very poor choice because the driver was very unreliable. We now have a new driver that should do better. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called eexpress. " } [962]=> array(11) { ["entry_id"]=> string(3) "963" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(56) "EtherExpressPro support/EtherExpress 10 (i82595) support" ["name"]=> string(12) "EEXPRESS_PRO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(610) " If you have a network (Ethernet) card of this type, say Y. This driver supports intel i82595{FX,TX} based boards. Note however that the EtherExpress PRO/100 Ethernet card has its own separate driver. Please read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eepro. If you want to compile it as a module, say M here and read as well as . " } [963]=> array(11) { ["entry_id"]=> string(3) "964" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "FMV-181/182/183/184 support (OBSOLETE)" ["name"]=> string(6) "FMV18X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(591) " If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from . If you use an FMV-183 or FMV-184 and it is not working, you may need to disable Plug & Play mode of the card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fmv18x. If you want to compile it as a module, say M here and read as well as . " } [964]=> array(11) { ["entry_id"]=> string(3) "965" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "HP PCLAN+ (27247B and 27252A) support" ["name"]=> string(10) "HPLAN_PLUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(466) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called hp-plus. If you want to compile it as a module, say M here and read as well as . " } [965]=> array(11) { ["entry_id"]=> string(3) "966" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "HP PCLAN (27245 and other 27xxx series) support" ["name"]=> string(5) "HPLAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(461) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called hp. If you want to compile it as a module, say M here and read as well as . " } [966]=> array(11) { ["entry_id"]=> string(3) "967" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "LP486E on board Ethernet" ["name"]=> string(6) "LP486E" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(171) " Say Y here to support the 82596-based on-board Ethernet controller for the Panther motherboard, which is one of the two shipped in the Intel Professional Workstation. " } [967]=> array(11) { ["entry_id"]=> string(3) "968" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "ICL EtherTeam 16i/32 support" ["name"]=> string(6) "ETH16I" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(465) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eth16i. If you want to compile it as a module, say M here and read as well as . " } [968]=> array(11) { ["entry_id"]=> string(3) "969" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "NE2000/NE1000 support" ["name"]=> string(6) "NE2000" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(808) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Many Ethernet cards without a specific driver are compatible with NE2000. If you have a PCI NE2000 card however, say N here and Y to "PCI NE2000 support", above. If you have a NE2000 card and are running on an MCA system (a bus system used on some IBM PS/2 computers and laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", below. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne. If you want to compile it as a module, say M here and read as well as . " } [969]=> array(11) { ["entry_id"]=> string(3) "970" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Zenith Z-Note support (EXPERIMENTAL)" ["name"]=> string(4) "ZNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(295) " The Zenith Z-Note notebook computer has a built-in network (Ethernet) card, and this is the Linux driver for it. Note that the IBM Thinkpad 300 is compatible with the Z-Note and is also supported by this driver. Read the Ethernet-HOWTO, available from . " } [970]=> array(11) { ["entry_id"]=> string(3) "971" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "SEEQ8005 support (EXPERIMENTAL)" ["name"]=> string(8) "SEEQ8005" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(442) " This is a driver for the SEEQ 8005 network (Ethernet) card. If this is for you, read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called ewrk3. " } [971]=> array(11) { ["entry_id"]=> string(3) "972" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "SK_G16 support (OBSOLETE)" ["name"]=> string(6) "SK_G16" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(145) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . " } [972]=> array(11) { ["entry_id"]=> string(3) "973" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "NEC PC-9800 C-bus cards" ["name"]=> string(8) "NET_CBUS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(184) " If your network (Ethernet) card hasn't been mentioned yet and its bus system (that's the way the cards talks to the other components of your computer) is NEC PC-9800 C-Bus, say Y. " } [973]=> array(11) { ["entry_id"]=> string(3) "974" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Most NE2000-based Ethernet support" ["name"]=> string(9) "NE2K_CBUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [974]=> array(11) { ["entry_id"]=> string(3) "975" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Melco EGY-98 support" ["name"]=> string(15) "NE2K_CBUS_EGY98" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [975]=> array(11) { ["entry_id"]=> string(3) "976" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Melco LGY-98 support" ["name"]=> string(15) "NE2K_CBUS_LGY98" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [976]=> array(11) { ["entry_id"]=> string(3) "977" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "ICM IF-27xxET support" ["name"]=> string(13) "NE2K_CBUS_ICM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [977]=> array(11) { ["entry_id"]=> string(3) "978" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "I-O DATA LA-98 support" ["name"]=> string(16) "NE2K_CBUS_IOLA98" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [978]=> array(11) { ["entry_id"]=> string(3) "979" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Contec C-NET(98)E/L support" ["name"]=> string(18) "NE2K_CBUS_CNET98EL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [979]=> array(11) { ["entry_id"]=> string(3) "980" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(26) "NE2K_CBUS_CNET98EL_IO_BASE" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "0" ["level"]=> string(2) "20" ["content"]=> string(48) "C-NET(98)E/L I/O base address (0xaaed or 0x55ed)" ["help_text"]=> NULL } [980]=> array(11) { ["entry_id"]=> string(3) "981" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Allied Telesis LA-98 Support" ["name"]=> string(16) "NE2K_CBUS_ATLA98" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [981]=> array(11) { ["entry_id"]=> string(3) "982" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "ELECOM Laneed LD-BDN[123]A Support" ["name"]=> string(13) "NE2K_CBUS_BDN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [982]=> array(11) { ["entry_id"]=> string(3) "983" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "NEC PC-9801-108 Support" ["name"]=> string(16) "NE2K_CBUS_NEC108" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [983]=> array(11) { ["entry_id"]=> string(3) "984" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SKnet MCA support" ["name"]=> string(4) "SKMC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(691) " These are Micro Channel Ethernet adapters. You need to say Y to "MCA support" in order to use this driver. Supported cards are the SKnet Junior MC2 and the SKnet MC2(+). The driver automatically distinguishes between the two cards. Note that using multiple boards of different type hasn't been tested with this driver. Say Y if you have one of these Ethernet adapters. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module is called sk_mca. If you want to compile it as a module, say M here and read as well as . " } [984]=> array(11) { ["entry_id"]=> string(3) "985" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "NE/2 (ne2000 MCA version) support" ["name"]=> string(7) "NE2_MCA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(462) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne2. If you want to compile it as a module, say M here and read as well as . " } [985]=> array(11) { ["entry_id"]=> string(3) "986" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "IBM LAN Adapter/A support" ["name"]=> string(7) "IBMLANA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(711) " This is a Micro Channel Ethernet adapter. You need to set CONFIG_MCA to use this driver. It is both available as an in-kernel driver and as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read as well as . The only currently supported card is the IBM LAN Adapter/A for Ethernet. It will both support 16K and 32K memory windows, however a 32K window gives a better security against packet losses. Usage of multiple boards with this driver should be possible, but has not been tested up to now due to lack of hardware. " } [986]=> array(11) { ["entry_id"]=> string(3) "987" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "EISA, VLB, PCI and on board controllers" ["name"]=> string(7) "NET_PCI" ["value"]=> string(1) "y" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(479) " This is another class of network cards which attach directly to the bus. If you have one of those, say Y and read the Ethernet-HOWTO, available from . Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about this class of network cards. If you say Y, you will be asked for your specific card in the following questions. If you are unsure, say Y. " } [987]=> array(11) { ["entry_id"]=> string(3) "988" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "AMD PCnet32 PCI support" ["name"]=> string(7) "PCNET32" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(487) " If you have a PCnet32 or PCnetPCI based network (Ethernet) card, answer Y here and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called pcnet32. If you want to compile it as a module, say M here and read as well as . " } [988]=> array(11) { ["entry_id"]=> string(3) "989" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "AMD 8111 (new PCI lance) support" ["name"]=> string(11) "AMD8111_ETH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(478) " If you have an AMD 8111-based PCI lance ethernet card, answer Y here and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called amd8111e. If you want to compile it as a module, say M here and read as well as . " } [989]=> array(11) { ["entry_id"]=> string(3) "990" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Adaptec Starfire/DuraLAN support" ["name"]=> string(16) "ADAPTEC_STARFIRE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(461) " Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network adapter. The DuraLAN chip is used on the 64 bit PCI boards from Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip driver. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called starfire. " } [990]=> array(11) { ["entry_id"]=> string(3) "991" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Use Rx Polling (NAPI) (EXPERIMENTAL)" ["name"]=> string(21) "ADAPTEC_STARFIRE_NAPI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(354) " NAPI is a new driver API designed to reduce CPU and interrupt load when the driver is receiving lots of packets from the card. It is still somewhat experimental and thus not yet enabled by default. If your estimated Rx load is 10kpps or more, or if the card will be deployed on potentially unfriendly networks (e.g. in a firewall), then say Y here. " } [991]=> array(11) { ["entry_id"]=> string(3) "992" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "Ansel Communications EISA 3200 support (EXPERIMENTAL)" ["name"]=> string(6) "AC3200" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(465) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ac3200. If you want to compile it as a module, say M here and read as well as . " } [992]=> array(11) { ["entry_id"]=> string(3) "993" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Apricot Xen-II on board Ethernet" ["name"]=> string(7) "APRICOT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(431) " If you have a network (Ethernet) controller of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called apricot. " } [993]=> array(11) { ["entry_id"]=> string(3) "994" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Broadcom 4400 ethernet support (EXPERIMENTAL)" ["name"]=> string(3) "B44" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(427) " If you have a network (Ethernet) controller of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called b44. " } [994]=> array(11) { ["entry_id"]=> string(3) "995" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "CS89x0 support" ["name"]=> string(6) "CS89x0" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(526) " Support for CS89x0 chipset based Ethernet cards. If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from as well as . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called cs89x. " } [995]=> array(11) { ["entry_id"]=> string(3) "996" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "TOSHIBA TC35815 Ethernet support" ["name"]=> string(7) "TC35815" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [996]=> array(11) { ["entry_id"]=> string(3) "997" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Digi Intl. RightSwitch SE-X support" ["name"]=> string(4) "DGRS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(679) " This is support for the Digi International RightSwitch series of PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6 models. If you have a network card of this type, say Y and read the Ethernet-HOWTO, available from . More specific information is contained in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dgrs. If you want to compile it as a module, say M here and read as well as . " } [997]=> array(11) { ["entry_id"]=> string(3) "998" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(62) "EtherExpressPro/100 support (eepro100, original Becker driver)" ["name"]=> string(8) "EEPRO100" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(487) " If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eepro100. If you want to compile it as a module, say M here and read as well as . " } [998]=> array(11) { ["entry_id"]=> string(3) "999" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Use PIO instead of MMIO" ["name"]=> string(12) "EEPRO100_PIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(213) " This instructs the driver to use programmed I/O ports (PIO) instead of PCI shared memory (MMIO). This can possibly solve some problems in case your mainboard has memory consistency issues. If unsure, say N. " } [999]=> array(11) { ["entry_id"]=> string(4) "1000" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "EtherExpressPro/100 support (e100, Alternate Intel driver)" ["name"]=> string(4) "E100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(2311) " This driver supports Intel(R) PRO/100 family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82558 PRO/100+ PCI Adapter 668081-xxx, 689661-xxx 82558 PRO/100+ Management Adapter 691334-xxx, 701738-xxx, 721383-xxx 82558 PRO/100+ Dual Port Server Adapter 714303-xxx, 711269-xxx, A28276-xxx 82558 PRO/100+ PCI Server Adapter 710550-xxx 82550 PRO/100 S Server Adapter 752438-xxx 82559 A56831-xxx, A10563-xxx, A12171-xxx, A12321-xxx, A12320-xxx, A12170-xxx 748568-xxx 748565-xxx 82550 PRO/100 S Desktop Adapter 751767-xxx 82559 748592-xxx, A12167-xxx, A12318-xxx, A12317-xxx, A12165-xxx, 748569-xxx 82559 PRO/100+ Server Adapter 729757-xxx 82559 PRO/100 S Management Adapter 748566-xxx, 748564-xxx 82550 PRO/100 S Dual Port Server Adapter A56831-xxx 82551 PRO/100 M Desktop Adapter A80897-xxx PRO/100 S Advanced Management Adapter 747842-xxx, 745171-xxx CNR PRO/100 VE Desktop Adapter A10386-xxx, A10725-xxx, A23801-xxx, A19716-xxx PRO/100 VM Desktop Adapter A14323-xxx, A19725-xxx, A23801-xxx, A22220-xxx, A23796-xxx To verify that your adapter is supported, find the board ID number on the adapter. Look for a label that has a barcode and a number in the format 123456-001 (six digits hyphen three digits). Match this to the list of numbers above. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: http://support.intel.com/support/network/adapter/pro100/21397.htm For the latest Intel PRO/100 network driver for Linux, see: http://appsr.intel.com/scripts-df/support_intel.asp More specific information on configuring the driver is in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e100. If you want to compile it as a module, say M here and read as well as . " } [1000]=> array(11) { ["entry_id"]=> string(4) "1001" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Mylex EISA LNE390A/B support (EXPERIMENTAL)" ["name"]=> string(6) "LNE390" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(465) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called lne390. If you want to compile it as a module, say M here and read as well as . " } [1001]=> array(11) { ["entry_id"]=> string(4) "1002" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Myson MTD-8xx PCI Ethernet support" ["name"]=> string(6) "FEALNX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(149) " Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet cards. Specifications and data at . " } [1002]=> array(11) { ["entry_id"]=> string(4) "1003" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "National Semiconductor DP8381x series PCI Ethernet support" ["name"]=> string(7) "NATSEMI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(261) " This driver is for the National Semiconductor DP83810 series, which is used in cards from PureData, NetGear, Linksys and others, including the 83815 chip. More specific information and updates are available from . " } [1003]=> array(11) { ["entry_id"]=> string(4) "1004" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "PCI NE2000 and clones support (see help)" ["name"]=> string(8) "NE2K_PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(825) " This driver is for NE2000 compatible PCI cards. It will not work with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 support" below). If you have a PCI NE2000 network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from . This driver also works for the following NE2000 clone cards: RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond Holtek HT80232 Holtek HT80229 This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne2k-pci. If you want to compile it as a module, say M here and read as well as . " } [1004]=> array(11) { ["entry_id"]=> string(4) "1005" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(57) "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" ["name"]=> string(6) "NE3210" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(553) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . Note that this driver will NOT WORK for NE3200 cards as they are completely different. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ne3210. If you want to compile it as a module, say M here and read as well as . " } [1005]=> array(11) { ["entry_id"]=> string(4) "1006" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" ["name"]=> string(6) "ES3210" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(465) " If you have a network (Ethernet) card of this type, say Y and read the Ethernet-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called es3210. If you want to compile it as a module, say M here and read as well as . " } [1006]=> array(11) { ["entry_id"]=> string(4) "1007" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(68) "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" ["name"]=> string(6) "8139CP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(446) " This is a driver for the Fast Ethernet PCI network cards based on the RTL8139C+ chips. If you have one of those, say Y and read the Ethernet-HOWTO, available from . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. This is recommended. The module will be called 8139cp. " } [1007]=> array(11) { ["entry_id"]=> string(4) "1008" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(50) "RealTek RTL-8139 PCI Fast Ethernet Adapter support" ["name"]=> string(7) "8139TOO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(509) " This is a driver for the Fast Ethernet PCI network cards based on the RTL8139 chips. If you have one of those, say Y and read as well as the Ethernet-HOWTO, available from . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called 8139too. " } [1008]=> array(11) { ["entry_id"]=> string(4) "1009" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Use PIO instead of MMIO" ["name"]=> string(11) "8139TOO_PIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(213) " This instructs the driver to use programmed I/O ports (PIO) instead of PCI shared memory (MMIO). This can possibly solve some problems in case your mainboard has memory consistency issues. If unsure, say N. " } [1009]=> array(11) { ["entry_id"]=> string(4) "1010" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(69) "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" ["name"]=> string(20) "8139TOO_TUNE_TWISTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(342) " This implements a function which might come in handy in case you are using low quality on long cabling. It is required for RealTek RTL-8139 revision K boards, and totally unused otherwise. It tries to match the transceiver to the cable characteristics. This is experimental since hardly documented by the manufacturer. If unsure, say Y. " } [1010]=> array(11) { ["entry_id"]=> string(4) "1011" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Support for older RTL-8129/8130 boards" ["name"]=> string(12) "8139TOO_8129" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(253) " This enables support for the older and uncommon RTL-8129 and RTL-8130 chips, which support MII via an external transceiver, instead of an internal one. Disabling this option will save some memory by making the code size smaller. If unsure, say Y. " } [1011]=> array(11) { ["entry_id"]=> string(4) "1012" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Use older RX-reset method" ["name"]=> string(17) "8139_OLD_RX_RESET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(302) " The 8139too driver was recently updated to contain a more rapid reset sequence, in the face of severe receive errors. This "new" RX-reset method should be adequate for all boards. But if you experience problems, you can enable this option to restore the old RX-reset behavior. If unsure, say N. " } [1012]=> array(11) { ["entry_id"]=> string(4) "1013" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(46) "SiS 900/7016 PCI Fast Ethernet Adapter support" ["name"]=> string(6) "SIS900" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(773) " This is a driver for the Fast Ethernet PCI network cards based on the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in SiS 630 and SiS 540 chipsets. If you have one of those, say Y and read the Ethernet-HOWTO, available at . Please read and comments at the beginning of for more information. This driver also supports AMD 79C901 HomePNA so that you can use your phone line as a network cable. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called sis900. " } [1013]=> array(11) { ["entry_id"]=> string(4) "1014" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "SMC EtherPower II" ["name"]=> string(7) "EPIC100" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(214) " This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, which is based on the SMC83c17x (EPIC/100). More specific information and updates are available from . " } [1014]=> array(11) { ["entry_id"]=> string(4) "1015" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Sundance Alta support" ["name"]=> string(8) "SUNDANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(152) " This driver is for the Sundance "Alta" chip. More specific information and updates are available from . " } [1015]=> array(11) { ["entry_id"]=> string(4) "1016" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Use MMIO instead of PIO" ["name"]=> string(13) "SUNDANCE_MMIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(201) " Enable memory-mapped I/O for interaction with Sundance NIC registers. Do NOT enable this by default, PIO (enabled when MMIO is disabled) is known to solve bugs on certain chips. If unsure, say N. " } [1016]=> array(11) { ["entry_id"]=> string(4) "1017" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "TI ThunderLAN support" ["name"]=> string(4) "TLAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(753) " If you have a PCI Ethernet network card based on the ThunderLAN chip which is supported by this driver, say Y and read the Ethernet-HOWTO, available from . Devices currently supported by this driver are Compaq Netelligent, Compaq NetFlex and Olicom cards. Please read the file for more details. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tlan. If you want to compile it as a module, say M here and read as well as . Please email feedback to torben.mathiasen@compaq.com. " } [1017]=> array(11) { ["entry_id"]=> string(4) "1018" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "VIA Rhine support" ["name"]=> string(9) "VIA_RHINE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(425) " If you have a VIA "rhine" based network card (Rhine-I (3043) or Rhine-2 (VT86c100A)), say Y here. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called via-rhine. If you want to compile it as a module, say M here and read as well as . " } [1018]=> array(11) { ["entry_id"]=> string(4) "1019" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Use MMIO instead of PIO (EXPERIMENTAL)" ["name"]=> string(14) "VIA_RHINE_MMIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(330) " This instructs the driver to use PCI shared memory (MMIO) instead of programmed I/O ports (PIO). Enabling this gives an improvement in processing time in parts of the driver. It is not known if this works reliably on all "rhine" based cards, but it has been tested successfully on some DFE-530TX adapters. If unsure, say N. " } [1019]=> array(11) { ["entry_id"]=> string(4) "1020" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "Philips SAA9730 Ethernet support (EXPERIMENTAL)" ["name"]=> string(11) "LAN_SAA9730" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(208) " The SAA9730 is a combined multimedia and peripheral controller used in thin clients, Internet access terminals, and diskless workstations. See . " } [1020]=> array(11) { ["entry_id"]=> string(4) "1021" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Pocket and portable adapters" ["name"]=> string(10) "NET_POCKET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(934) " Cute little network (Ethernet) devices which attach to the parallel port ("pocket adapters"), commonly used with laptops. If you have one of those, say Y and read the Ethernet-HOWTO, available from . If you want to plug a network (or some other) card into the PCMCIA (or PC-card) slot of your laptop instead (PCMCIA is the standard for credit card size extension cards used by all modern laptops), you need the pcmcia-cs package (location contained in the file ) and you can say N here. Laptop users should read the Linux Laptop home page at . Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about this class of network devices. If you say Y, you will be asked for your specific device in the following questions. " } [1021]=> array(11) { ["entry_id"]=> string(4) "1022" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "AT-LAN-TEC/RealTek pocket adapter support" ["name"]=> string(3) "ATP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(590) " This is a network (Ethernet) device which attaches to your parallel port. Read as well as the Ethernet-HOWTO, available from , if you want to use this. If you intend to use this driver, you should have said N to the "Parallel printer support", because the two drivers don't like each other. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called atp. " } [1022]=> array(11) { ["entry_id"]=> string(4) "1023" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "D-Link DE600 pocket adapter support" ["name"]=> string(5) "DE600" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(605) " This is a network (Ethernet) device which attaches to your parallel port. Read as well as the Ethernet-HOWTO, available from , if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called de600. " } [1023]=> array(11) { ["entry_id"]=> string(4) "1024" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "D-Link DE620 pocket adapter support" ["name"]=> string(5) "DE620" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(605) " This is a network (Ethernet) device which attaches to your parallel port. Read as well as the Ethernet-HOWTO, available from , if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called de620. " } [1024]=> array(11) { ["entry_id"]=> string(4) "1025" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "SGI Seeq ethernet controller support" ["name"]=> string(7) "SGISEEQ" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(112) " Say Y here if you have an Seeq based Ethernet network card. This is used in many Silicon Graphics machines. " } [1025]=> array(11) { ["entry_id"]=> string(4) "1026" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "DEC LANCE ethernet controller support" ["name"]=> string(8) "DECLANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(201) " This driver is for the series of Ethernet controllers produced by DEC (now Compaq) based on the AMD Lance chipset, including the DEPCA series. (This chipset is better known via the NE2100 cards.) " } [1026]=> array(11) { ["entry_id"]=> string(4) "1027" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Baget AMD LANCE support" ["name"]=> string(10) "BAGETLANCE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(160) " Say Y to enable kernel support for AMD Lance Ethernet cards on the MIPS-32-based Baget embedded system. This chipset is better known via the NE2100 cards. " } [1027]=> array(11) { ["entry_id"]=> string(4) "1028" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Motorola 68360 ethernet controller" ["name"]=> string(10) "68360_ENET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(100) " Say Y here if you want to use the built-in ethernet controller of the Motorola 68360 processor. " } [1028]=> array(11) { ["entry_id"]=> string(4) "1029" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "FEC ethernet controller (of ColdFire 5272)" ["name"]=> string(3) "FEC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(120) " Say Y here if you want to use the built-in 10/100 Fast ethernet controller on the Motorola ColdFire 5272 processor. " } [1029]=> array(11) { ["entry_id"]=> string(4) "1030" ["entry_type"]=> string(4) "MENU" ["text"]=> string(20) "Ethernet (1000 Mbit)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1030]=> array(11) { ["entry_id"]=> string(4) "1031" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(54) "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" ["name"]=> string(6) "ACENIC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(584) " Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet adapter. The driver allows for using the Jumbo Frame option (9000 bytes/frame) however it requires that your switches can handle this as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig line. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called acenic. " } [1031]=> array(11) { ["entry_id"]=> string(4) "1032" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Omit support for old Tigon I based AceNICs" ["name"]=> string(19) "ACENIC_OMIT_TIGON_I" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(400) " Say Y here if you only have Tigon II based AceNICs and want to leave out support for the older Tigon I based cards which are no longer being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B version)). This will reduce the size of the driver object by app. 100KB. If you are not sure whether your card is a Tigon I or a Tigon II, say N here. The safe and default value for this is N. " } [1032]=> array(11) { ["entry_id"]=> string(4) "1033" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "D-Link DL2000-based Gigabit Ethernet support" ["name"]=> string(4) "DL2K" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(417) " This driver supports D-Link 2000-based gigabit ethernet cards, which includes D-Link DGE-550T Gigabit Ethernet Adapter. D-Link DL2000-based Gigabit Ethernet Adapter. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called dl2k. " } [1033]=> array(11) { ["entry_id"]=> string(4) "1034" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(42) "Intel(R) PRO/1000 Gigabit Ethernet support" ["name"]=> string(5) "E1000" ["value"]=> string(1) "y" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1720) " This driver supports Intel(R) PRO/1000 gigabit ethernet family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82542 PRO/1000 Gigabit Server Adapter 700262-xxx, 717037-xxx 82543 PRO/1000 F Server Adapter 738640-xxx, A38888-xxx 82543 PRO/1000 T Server Adapter A19845-xxx, A33948-xxx 82544 PRO/1000 XT Server Adapter A51580-xxx 82544 PRO/1000 XF Server Adapter A50484-xxx 82544 PRO/1000 T Desktop Adapter A62947-xxx 82540 PRO/1000 MT Desktop Adapter A78408-xxx 82541 PRO/1000 MT Desktop Adapter C91016-xxx 82545 PRO/1000 MT Server Adapter A92165-xxx 82546 PRO/1000 MT Dual Port Server Adapter A92111-xxx 82545 PRO/1000 MF Server Adapter A91622-xxx 82545 PRO/1000 MF Server Adapter(LX) A91624-xxx 82546 PRO/1000 MF Dual Port Server Adapter A91620-xxx For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: For general information and support, go to the Intel support website at: More specific information on configuring the driver is in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called e1000. If you want to compile it as a module, say M here and read as well as . " } [1034]=> array(11) { ["entry_id"]=> string(4) "1035" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Use Rx Polling (NAPI)" ["name"]=> string(10) "E1000_NAPI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [1035]=> array(11) { ["entry_id"]=> string(4) "1036" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "MyriCOM Gigabit Ethernet support" ["name"]=> string(9) "MYRI_SBUS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(314) " This driver supports MyriCOM Sbus gigabit Ethernet cards. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called myri_sbus. " } [1036]=> array(11) { ["entry_id"]=> string(4) "1037" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "National Semiconduct DP83820 support" ["name"]=> string(7) "NS83820" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(260) " This is a driver for the National Semiconductor DP83820 series of gigabit ethernet MACs. Cards using this chipset include the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of zero copy. " } [1037]=> array(11) { ["entry_id"]=> string(4) "1038" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Packet Engines Hamachi GNIC-II support" ["name"]=> string(7) "HAMACHI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(423) " If you have a Gigabit Ethernet card of this type, say Y and read the Ethernet-HOWTO, available from . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called hamachi. " } [1038]=> array(11) { ["entry_id"]=> string(4) "1039" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(59) "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" ["name"]=> string(9) "YELLOWFIN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(576) " Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is used by the Beowulf Linux cluster project. See for more information about this driver in particular and Beowulf in general. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called yellowfin. " } [1039]=> array(11) { ["entry_id"]=> string(4) "1040" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Realtek 8169 gigabit ethernet support" ["name"]=> string(5) "R8169" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(320) " Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called r8169. " } [1040]=> array(11) { ["entry_id"]=> string(4) "1041" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "SysKonnect SK-98xx support" ["name"]=> string(7) "SK98LIN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(996) " Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server Adapter. The following adapters are supported by this driver: - SK-9841 (single link 1000Base-LX) - SK-9842 (dual link 1000Base-LX) - SK-9843 (single link 1000Base-SX) - SK-9844 (dual link 1000Base-SX) - SK-9821 (single link 1000Base-T) - SK-9822 (dual link 1000Base-T) - SK-9861 (single link Volition connector) - SK-9862 (dual link Volition connector) The driver also supports the following adapters from Allied Telesyn: - AT2970... The dual link adapters support a link-failover feature. Read for information about optional driver parameters. Questions concerning this driver may be addressed to: linux@syskonnect.de If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called sk98lin. " } [1041]=> array(11) { ["entry_id"]=> string(4) "1042" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Broadcom Tigon3 support" ["name"]=> string(6) "TIGON3" ["value"]=> string(1) "m" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(317) " This driver supports Broadcom Tigon3 based gigabit Ethernet cards. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called tg3. " } [1042]=> array(11) { ["entry_id"]=> string(4) "1043" ["entry_type"]=> string(4) "MENU" ["text"]=> string(21) "Ethernet (10000 Mbit)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1043]=> array(11) { ["entry_id"]=> string(4) "1044" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Intel(R) PRO/10GbE support" ["name"]=> string(4) "IXGB" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(951) " This driver supports Intel(R) PRO/10GbE family of adapters, which includes: Controller Adapter Name Board IDs ---------- ------------ --------- 82597EX Intel(R) PRO/10GbE LR Server Adapter A82505-xxx For more information on how to identify your adapter, go to the Adapter & Driver ID Guide at: For general information and support, go to the Intel support website at: More specific information on configuring the driver is in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ixgb. If you want to compile it as a module, say M here and read as well as . " } [1044]=> array(11) { ["entry_id"]=> string(4) "1045" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Use Rx Polling (NAPI) (EXPERIMENTAL)" ["name"]=> string(9) "IXGB_NAPI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [1045]=> array(11) { ["entry_id"]=> string(4) "1046" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "iSeries Virtual Ethernet driver support" ["name"]=> string(4) "VETH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> NULL } [1046]=> array(11) { ["entry_id"]=> string(4) "1047" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "FDDI driver support" ["name"]=> string(4) "FDDI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(353) " Fiber Distributed Data Interface is a high speed local area network design; essentially a replacement for high speed Ethernet. FDDI can run over copper or fiber. If you are connected to such a network and want a driver for the FDDI card in your computer, say Y here (and then also Y to the driver for your FDDI card, below). Most people will say N. " } [1047]=> array(11) { ["entry_id"]=> string(4) "1048" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Digital DEFEA and DEFPA adapter support" ["name"]=> string(5) "DEFXX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(134) " This is support for the DIGITAL series of EISA (DEFEA) and PCI (DEFPA) controllers which can connect you to a local FDDI network. " } [1048]=> array(11) { ["entry_id"]=> string(4) "1049" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "SysKonnect FDDI PCI support" ["name"]=> string(4) "SKFP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(981) " Say Y here if you have a SysKonnect FDDI PCI adapter. The following adapters are supported by this driver: - SK-5521 (SK-NET FDDI-UP) - SK-5522 (SK-NET FDDI-UP DAS) - SK-5541 (SK-NET FDDI-FP) - SK-5543 (SK-NET FDDI-LP) - SK-5544 (SK-NET FDDI-LP DAS) - SK-5821 (SK-NET FDDI-UP64) - SK-5822 (SK-NET FDDI-UP64 DAS) - SK-5841 (SK-NET FDDI-FP64) - SK-5843 (SK-NET FDDI-LP64) - SK-5844 (SK-NET FDDI-LP64 DAS) - Netelligent 100 FDDI DAS Fibre SC - Netelligent 100 FDDI SAS Fibre SC - Netelligent 100 FDDI DAS UTP - Netelligent 100 FDDI SAS UTP - Netelligent 100 FDDI SAS Fibre MIC Read for information about the driver. Questions concerning this driver can be addressed to: linux@syskonnect.de If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called skfp. " } [1049]=> array(11) { ["entry_id"]=> string(4) "1050" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "HIPPI driver support (EXPERIMENTAL)" ["name"]=> string(5) "HIPPI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(532) " HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI can run over copper (25m) or fiber (300m on multi-mode or 10km on single-mode). HIPPI networks are commonly used for clusters and to connect to super computers. If you are connected to a HIPPI network and have a HIPPI network card in your computer that you want to use under Linux, say Y here (you must also remember to enable the driver for your HIPPI card below). Most people will say N here. " } [1050]=> array(11) { ["entry_id"]=> string(4) "1051" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(61) "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" ["name"]=> string(10) "ROADRUNNER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(335) " Say Y here if this is your PCI HIPPI network card. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called rrunner. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1051]=> array(11) { ["entry_id"]=> string(4) "1052" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Use large TX/RX rings (EXPERIMENTAL)" ["name"]=> string(22) "ROADRUNNER_LARGE_RINGS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(282) " If you say Y here, the RoadRunner driver will preallocate up to 2 MB of additional memory to allow for fastest operation, both for transmitting and receiving. This memory cannot be used by any other kernel code or by user space programs. Say Y here only if you have the memory. " } [1052]=> array(11) { ["entry_id"]=> string(4) "1053" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "PLIP (parallel port) support" ["name"]=> string(4) "PLIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(1775) " PLIP (Parallel Line Internet Protocol) is used to create a reasonably fast mini network consisting of two (or, rarely, more) local machines. A PLIP link from a Linux box is a popular means to install a Linux distribution on a machine which doesn't have a CD-ROM drive (a minimal system has to be transferred with floppies first). The kernels on both machines need to have this PLIP option enabled for this to work. The PLIP driver has two modes, mode 0 and mode 1. The parallel ports (the connectors at the computers with 25 holes) are connected with "null printer" or "Turbo Laplink" cables which can transmit 4 bits at a time (mode 0) or with special PLIP cables, to be used on bidirectional parallel ports only, which can transmit 8 bits at a time (mode 1); you can find the wiring of these cables in . The cables can be up to 15m long. Mode 0 works also if one of the machines runs DOS/Windows and has some PLIP software installed, e.g. the Crynwr PLIP packet driver () and winsock or NCSA's telnet. If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well as the NET-3-HOWTO, both available from . Note that the PLIP protocol has been changed and this PLIP driver won't work together with the PLIP support in Linux versions 1.0.x. This option enlarges your kernel by about 8 KB. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called plip. If unsure, say Y or M, in case you buy a laptop later. " } [1053]=> array(11) { ["entry_id"]=> string(4) "1054" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "PPP (point-to-point protocol) support" ["name"]=> string(3) "PPP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(1549) " PPP (Point to Point Protocol) is a newer and better SLIP. It serves the same purpose: sending Internet traffic over telephone (and other serial) lines. Ask your access provider if they support it, because otherwise you can't use it; most Internet access providers these days support PPP rather than SLIP. To use PPP, you need an additional program called pppd as described in the PPP-HOWTO, available at . Make sure that you have the version of pppd recommended in . The PPP option enlarges your kernel by about 16 KB. There are actually two versions of PPP: the traditional PPP for asynchronous lines, such as regular analog phone lines, and synchronous PPP which can be used over digital ISDN lines for example. If you want to use PPP over phone lines or other asynchronous serial lines, you need to say Y (or M) here and also to the next option, "PPP support for async serial ports". For PPP over synchronous lines, you should say Y (or M) here and to "Support synchronous PPP", below. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you said Y to "Version information on all symbols" above, then you cannot compile the PPP driver into the kernel; you can then only compile it as a module. The module will be called ppp_generic. If you want to compile it as a module, say M here and read as well as . " } [1054]=> array(11) { ["entry_id"]=> string(4) "1055" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "PPP multilink support (EXPERIMENTAL)" ["name"]=> string(13) "PPP_MULTILINK" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(350) " PPP multilink is a protocol (defined in RFC 1990) which allows you to combine several (logical or physical) lines into one logical PPP connection, so that you can utilize your full bandwidth. This has to be supported at the other end as well and you need a version of the pppd daemon which understands the multilink protocol. If unsure, say N. " } [1055]=> array(11) { ["entry_id"]=> string(4) "1056" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "PPP filtering" ["name"]=> string(10) "PPP_FILTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(388) " Say Y here if you want to be able to filter the packets passing over PPP interfaces. This allows you to control which packets count as activity (i.e. which packets will reset the idle timer or bring up a demand-dialled link) and which packets are to be dropped entirely. You need to say Y here if you wish to use the pass-filter and active-filter options to pppd. If unsure, say N. " } [1056]=> array(11) { ["entry_id"]=> string(4) "1057" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "PPP support for async serial ports" ["name"]=> string(9) "PPP_ASYNC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(449) " Say Y (or M) here if you want to be able to use PPP over standard asynchronous serial ports, such as COM1 or COM2 on a PC. If you use a modem (not a synchronous or ISDN modem) to contact your ISP, you need this option. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read . If unsure, say Y. " } [1057]=> array(11) { ["entry_id"]=> string(4) "1058" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "PPP support for sync tty ports" ["name"]=> string(12) "PPP_SYNC_TTY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(398) " Say Y (or M) here if you want to be able to use PPP over synchronous (HDLC) tty devices, such as the SyncLink adapter. These devices are often used for high-speed leased lines like T1/E1. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read . " } [1058]=> array(11) { ["entry_id"]=> string(4) "1059" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "PPP Deflate compression" ["name"]=> string(11) "PPP_DEFLATE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(592) " Support for the Deflate compression method for PPP, which uses the Deflate algorithm (the same algorithm that gzip uses) to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the Deflate compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. This code is also available as a module (code which can be inserted into and removed from the running kernel). If you want to compile it as a module, say M here and read . " } [1059]=> array(11) { ["entry_id"]=> string(4) "1060" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "PPP BSD-Compress compression" ["name"]=> string(11) "PPP_BSDCOMP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(704) " Support for the BSD-Compress compression method for PPP, which uses the LZW compression method to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the BSD-Compress compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. The PPP Deflate compression method ("PPP Deflate compression", above) is preferable to BSD-Compress, because it compresses better and is patent-free. Note that the BSD compression code will always be compiled as a module; it is called bsd_comp and will show up in the directory modules once you have said "make modules". If unsure, say N. " } [1060]=> array(11) { ["entry_id"]=> string(4) "1061" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "PPP over Ethernet (EXPERIMENTAL)" ["name"]=> string(5) "PPPOE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(307) " Support for PPP over Ethernet. This driver requires the latest version of pppd from the CVS repository at cvs.samba.org. Alternatively, see the RoaringPenguin package (http://www.roaringpenguin.com/pppoe) which contains instruction on how to use this driver (under the heading "Kernel mode PPPoE"). " } [1061]=> array(11) { ["entry_id"]=> string(4) "1062" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "PPP over ATM" ["name"]=> string(7) "PPPOATM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(239) " Support PPP (Point to Point Protocol) encapsulated in ATM frames. This implementation does not yet comply with section 8 of RFC2364, which can lead to bad results if the ATM peer loses state and changes its encapsulation unilaterally. " } [1062]=> array(11) { ["entry_id"]=> string(4) "1063" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "SLIP (serial line) support" ["name"]=> string(4) "SLIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(1551) " Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to connect to your Internet service provider or to connect to some other local Unix box or if you want to configure your Linux box as a Slip/CSlip server for other people to dial in. SLIP (Serial Line Internet Protocol) is a protocol used to send Internet traffic over serial connections such as telephone lines or null modem cables; nowadays, the protocol PPP is more commonly used for this same purpose. Normally, your access provider has to support SLIP in order for you to be able to use it, but there is now a SLIP emulator called SLiRP around (available from ) which allows you to use SLIP over a regular dial up shell connection. If you plan to use SLiRP, make sure to say Y to CSLIP, below. The NET-3-HOWTO, available from , explains how to configure SLIP. Note that you don't need this option if you just want to run term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read ). SLIP support will enlarge your kernel by about 4 KB. If unsure, say N. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read as well as . The module will be called slip. " } [1063]=> array(11) { ["entry_id"]=> string(4) "1064" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "CSLIP compressed headers" ["name"]=> string(15) "SLIP_COMPRESSED" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(625) " This protocol is faster than SLIP because it uses compression on the TCP/IP headers (not on the data itself), but it has to be supported on both ends. Ask your access provider if you are not sure and answer Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available from ) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-3-HOWTO, available from , explains how to configure CSLIP. This won't enlarge your kernel. " } [1064]=> array(11) { ["entry_id"]=> string(4) "1065" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Keepalive and linefill" ["name"]=> string(10) "SLIP_SMART" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(148) " Adds additional capabilities to the SLIP driver to support the RELCOM line fill and keepalive monitoring. Ideal on poor quality analogue lines. " } [1065]=> array(11) { ["entry_id"]=> string(4) "1066" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Six bit SLIP encapsulation" ["name"]=> string(15) "SLIP_MODE_SLIP6" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(455) " Just occasionally you may need to run IP over hostile serial networks that don't pass all control characters or are only seven bit. Saying Y here adds an extra mode you can use with SLIP: "slip6". In this mode, SLIP will only send normal ASCII symbols over the serial device. Naturally, this has to be supported at the other end of the link as well. It's good enough, for example, to run IP over the async ports of a Camtec JNT Pad. If unsure, say N. " } [1066]=> array(11) { ["entry_id"]=> string(4) "1067" ["entry_type"]=> string(4) "MENU" ["text"]=> string(27) "Wireless LAN (non-hamradio)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1067]=> array(11) { ["entry_id"]=> string(4) "1068" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(63) "Wireless LAN drivers (non-hamradio) & Wireless Extensions" ["name"]=> string(9) "NET_RADIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(995) " Support for wireless LANs and everything having to do with radio, but not with amateur radio or FM broadcasting. Saying Y here also enables the Wireless Extensions (creates /proc/net/wireless and enables iwconfig access). The Wireless Extension is a generic API allowing a driver to expose to the user space configuration and statistics specific to common Wireless LANs. The beauty of it is that a single set of tool can support all the variations of Wireless LANs, regardless of their type (as long as the driver supports Wireless Extension). Another advantage is that these parameters may be changed on the fly without restarting the driver (or Linux). If you wish to use Wireless Extensions with wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch the tools from . Some user-level drivers for scarab devices which don't require special kernel support are available from . " } [1068]=> array(11) { ["entry_id"]=> string(4) "1069" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "STRIP (Metricom starmode radio IP)" ["name"]=> string(5) "STRIP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1078) " Say Y if you have a Metricom radio and intend to use Starmode Radio IP. STRIP is a radio protocol developed for the MosquitoNet project (on the WWW at ) to send Internet traffic using Metricom radios. Metricom radios are small, battery powered, 100kbit/sec packet radio transceivers, about the size and weight of a cellular telephone. (You may also have heard them called "Metricom modems" but we avoid the term "modem" because it misleads many people into thinking that you can plug a Metricom modem into a phone line and use it as a modem.) You can use STRIP on any Linux machine with a serial port, although it is obviously most useful for people with laptop computers. If you think you might get a Metricom radio in the future, there is no harm in saying Y to STRIP now, except that it makes the kernel a bit bigger. You can also compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called strip. " } [1069]=> array(11) { ["entry_id"]=> string(4) "1070" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Aironet Arlan 655 & IC2200 DS support" ["name"]=> string(5) "ARLAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(504) " Aironet makes Arlan, a class of wireless LAN adapters. These use the www.Telxon.com chip, which is also used on several similar cards. This driver is tested on the 655 and IC2200 series cards. Look at for the latest information. The driver is built as two modules, arlan and arlan-proc. The latter is the /proc interface and is not needed most of time. On some computers the card ends up in non-valid state after some time. Use a ping-reset script to clear it. " } [1070]=> array(11) { ["entry_id"]=> string(4) "1071" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(66) "AT & T/Lucent old WaveLAN & DEC RoamAbout DS ISA support" ["name"]=> string(7) "WAVELAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1175) " The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is a Radio LAN (wireless Ethernet-like Local Area Network) using the radio frequencies 900 MHz and 2.4 GHz. This driver support the ISA version of the WaveLAN card. A separate driver for the PCMCIA (PC-card) hardware is available in David Hinds' pcmcia-cs package (see the file for location). If you want to use an ISA WaveLAN card under Linux, say Y and read the Ethernet-HOWTO, available from . Some more specific information is contained in and in the source code . You will also need the wireless tools package available from . Please read the man pages contained therein. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wavelan. If you want to compile it as a module, say M here and read as well as . " } [1071]=> array(11) { ["entry_id"]=> string(4) "1072" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "AT & T/Lucent old WaveLAN Pcmcia wireless support" ["name"]=> string(14) "PCMCIA_WAVELAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(469) " Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA (PC-card) wireless Ethernet networking card to your computer. This driver is for the non-IEEE-802.11 Wavelan cards. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wavelan_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1072]=> array(11) { ["entry_id"]=> string(4) "1073" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Xircom Netwave AirSurfer Pcmcia wireless support" ["name"]=> string(14) "PCMCIA_NETWAVE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(404) " Say Y here if you intend to attach this type of PCMCIA (PC-card) wireless Ethernet networking card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called netwave_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1073]=> array(11) { ["entry_id"]=> string(4) "1074" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "Aviator/Raytheon 2.4MHz wireless support" ["name"]=> string(12) "PCMCIA_RAYCS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(485) " Say Y here if you intend to attach an Aviator/Raytheon PCMCIA (PC-card) wireless Ethernet networking card to your computer. Please read the file for details. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ray_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1074]=> array(11) { ["entry_id"]=> string(4) "1075" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards" ["name"]=> string(4) "AIRO" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(540) " This is the standard Linux driver to support Cisco/Aironet ISA and PCI 802.11 wireless cards. It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X - with or without encryption) as well as card before the Cisco aquisition (Aironet 4500, Aironet 4800, Aironet 4800B). This driver support both the standard Linux Wireless Extensions and Cisco proprietary API, so both the Linux Wireless Tools and the Cisco Linux utilities can be used to configure the card. The driver can be compiled as a module and will be named "airo". " } [1075]=> array(11) { ["entry_id"]=> string(4) "1076" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(54) "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" ["name"]=> string(6) "HERMES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(987) " A driver for 802.11b wireless cards based based on the "Hermes" or Intersil HFA384x (Prism 2) MAC controller. This includes the vast majority of the PCMCIA 802.11b cards (which are nearly all rebadges) - except for the Cisco/Aironet cards. Cards supported include the Apple Airport (not a PCMCIA card), WavelanIEEE/Orinoco, Cabletron/EnteraSys Roamabout, ELSA AirLancer, MELCO Buffalo, Avaya, IBM High Rate Wireless, Farralon Syyline, Samsung MagicLAN, Netgear MA401, LinkSys WPC-11, D-Link DWL-650, 3Com AirConnect, Intel PRO/Wireless, and Symbol Spectrum24 High Rate amongst others. This option includes the guts of the driver, but in order to actually use a card you will also need to enable support for PCMCIA Hermes cards, PLX9052 based PCI adaptors or the Apple Airport below. You will also very likely also need the Wireless Tools in order to configure your card and that /etc/pcmcia/wireless.opts works : " } [1076]=> array(11) { ["entry_id"]=> string(4) "1077" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Apple Airport support (built-in)" ["name"]=> string(13) "APPLE_AIRPORT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(228) " Say Y here to support the Airport 802.11b wireless Ethernet hardware built into the Macintosh iBook and other recent PowerPC-based Macintosh machines. This is essentially a Lucent Orinoco card with a non-standard interface " } [1077]=> array(11) { ["entry_id"]=> string(4) "1078" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(79) "Hermes in PLX9052 based PCI adaptor support (Netgear MA301 etc.) (EXPERIMENTAL)" ["name"]=> string(10) "PLX_HERMES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(447) " Enable support for PCMCIA cards supported by the "Hermes" (aka orinoco) driver when used in PLX9052 based PCI adaptors. These adaptors are not a full PCMCIA controller but act as a more limited PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that 802.11b PCMCIA cards can be used in desktop machines. The Netgear MA301 is such an adaptor. Support for these adaptors is so far still incomplete and buggy. You have been warned. " } [1078]=> array(11) { ["entry_id"]=> string(4) "1079" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "Hermes in TMD7160 based PCI adaptor support (EXPERIMENTAL)" ["name"]=> string(10) "TMD_HERMES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(408) " Enable support for PCMCIA cards supported by the "Hermes" (aka orinoco) driver when used in TMD7160 based PCI adaptors. These adaptors are not a full PCMCIA controller but act as a more limited PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that 802.11b PCMCIA cards can be used in desktop machines. Support for these adaptors is so far still incomplete and buggy. You have been warned. " } [1079]=> array(11) { ["entry_id"]=> string(4) "1080" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(52) "Prism 2.5 PCI 802.11b adaptor support (EXPERIMENTAL)" ["name"]=> string(10) "PCI_HERMES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(280) " Enable support for PCI and mini-PCI 802.11b wireless NICs based on the Prism 2.5 chipset. These are true PCI cards, not the 802.11b PCMCIA cards bundled with PCI<->PCMCIA adaptors which are also common. Some of the built-in wireless adaptors in laptops are of this variety. " } [1080]=> array(11) { ["entry_id"]=> string(4) "1081" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Hermes PCMCIA card support" ["name"]=> string(13) "PCMCIA_HERMES" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(848) " A driver for "Hermes" chipset based PCMCIA wireless adaptors, such as the Lucent WavelanIEEE/Orinoco cards and their OEM (Cabletron/ EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and others). It should also be usable on various Prism II based cards such as the Linksys, D-Link and Farallon Skyline. It should also work on Symbol cards such as the 3Com AirConnect and Ericsson WLAN. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). You also want to check out the PCMCIA-HOWTO, available from . You will also very likely also need the Wireless Tools in order to configure your card and that /etc/pcmcia/wireless.opts works: . " } [1081]=> array(11) { ["entry_id"]=> string(4) "1082" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(44) "Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards" ["name"]=> string(7) "AIRO_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(890) " This is the standard Linux driver to support Cisco/Aironet PCMCIA 802.11 wireless cards. This driver is the same as the Aironet driver part of the Linux Pcmcia package. It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X - with or without encryption) as well as card before the Cisco aquisition (Aironet 4500, Aironet 4800, Aironet 4800B). It also supports OEM of Cisco such as the DELL TrueMobile 4800 and Xircom 802.11b cards. This driver support both the standard Linux Wireless Extensions and Cisco proprietary API, so both the Linux Wireless Tools and the Cisco Linux utilities can be used to configure the card. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). You also want to check out the PCMCIA-HOWTO, available from . " } [1082]=> array(11) { ["entry_id"]=> string(4) "1083" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Atmel at76c502/at76c504 PCMCIA cards" ["name"]=> string(12) "PCMCIA_ATMEL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(463) " A driver for PCMCIA 802.11 wireless cards based on the Atmel fast-vnet chips. This driver supports standard Linux wireless extensions. Many cards based on this chipset do not have flash memory and need their firmware loaded at start-up. If yours is one of these, you will need to provide a firmware image to be loaded into the card by the driver. The Atmel firmware package can be downloaded from http://www.thekelleys.org.uk/atmel/atmel_firmware.tar.gz " } [1083]=> array(11) { ["entry_id"]=> string(4) "1084" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Planet WL3501 PCMCIA cards" ["name"]=> string(13) "PCMCIA_WL3501" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(159) " A driver for WL3501 PCMCIA 802.11 wireless cards made by Planet. It has basic support for Linux wireless extensions and initial micro support for ethtool. " } [1084]=> array(11) { ["entry_id"]=> string(4) "1085" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "NET_WIRELESS" ["name"]=> string(12) "NET_WIRELESS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [1085]=> array(11) { ["entry_id"]=> string(4) "1086" ["entry_type"]=> string(4) "MENU" ["text"]=> string(37) "Token Ring devices (depends on LLC=y)" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1086]=> array(11) { ["entry_id"]=> string(4) "1087" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Token Ring driver support" ["name"]=> string(2) "TR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(464) " Token Ring is IBM's way of communication on a local network; the rest of the world uses Ethernet. To participate on a Token Ring network, you need a special Token ring network card. If you are connected to such a Token Ring network and want to use your Token Ring card under Linux, say Y here and to the driver for your particular card below and read the Token-Ring mini-HOWTO, available from . Most people can say N here. " } [1087]=> array(11) { ["entry_id"]=> string(4) "1088" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "IBM Tropic chipset based adapter support" ["name"]=> string(5) "IBMTR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(552) " This is support for all IBM Token Ring cards that don't use DMA. If you have such a beast, say Y and read the Token-Ring mini-HOWTO, available from . Warning: this driver will almost definitely fail if more than one active Token Ring card is present. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ibmtr. If you want to compile it as a module, say M here and read . " } [1088]=> array(11) { ["entry_id"]=> string(4) "1089" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "IBM Olympic chipset PCI adapter support" ["name"]=> string(5) "IBMOL" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(718) " This is support for all non-Lanstreamer IBM PCI Token Ring Cards. Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II Wake On Lan, and PCI 100/16/4 adapters. If you have such an adapter, say Y and read the Token-Ring mini-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called olympic. If you want to compile it as a module, say M here and read . Also read or check the Linux Token Ring Project site for the latest information at . " } [1089]=> array(11) { ["entry_id"]=> string(4) "1090" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "IBM Lanstreamer chipset PCI adapter support" ["name"]=> string(5) "IBMLS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(455) " This is support for IBM Lanstreamer PCI Token Ring Cards. If you have such an adapter, say Y and read the Token-Ring mini-HOWTO, available from . This driver is also available as a modules ( = code which can be inserted in and removed from the running kernel whenever you want). The modules will be called lanstreamer. If you want to compile it as a module, say M here and read . " } [1090]=> array(11) { ["entry_id"]=> string(4) "1091" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "3Com 3C359 Token Link Velocity XL adapter support" ["name"]=> string(5) "3C359" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(716) " This is support for the 3Com PCI Velocity XL cards, specifically the 3Com 3C359, please note this is not for the 3C339 cards, you should use the tms380 driver instead. If you have such an adapter, say Y and read the Token-Ring mini-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will will be called 3c359. If you want to compile it as a module, say M here and read Documentation/modules.txt. Also read the file or check the Linux Token Ring Project site for the latest information at " } [1091]=> array(11) { ["entry_id"]=> string(4) "1092" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Generic TMS380 Token Ring ISA/PCI adapter support" ["name"]=> string(8) "TMS380TR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1001) " This driver provides generic support for token ring adapters based on the Texas Instruments TMS380 series chipsets. This includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591), Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several Madge adapters. If you say Y here, you will be asked to select which cards to support below. If you're using modules, each class of card will be supported by a separate module. If you have such an adapter and would like to use it, say Y and read the Token-Ring mini-HOWTO, available from . Also read the file or check . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tms380tr. If you want to compile it as a module, say M here and read . " } [1092]=> array(11) { ["entry_id"]=> string(4) "1093" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Generic TMS380 PCI support" ["name"]=> string(6) "TMSPCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(473) " This tms380 module supports generic TMS380-based PCI cards. These cards are known to work: - Compaq 4/16 TR PCI - SysKonnect TR4/16 PCI (SK-4590/SK-4591) - Thomas-Conrad TC4048 PCI 4/16 - 3Com Token Link Velocity This driver is available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called tmspci. If you want to compile it as a module, say M here and read . " } [1093]=> array(11) { ["entry_id"]=> string(4) "1094" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "SysKonnect TR4/16 ISA support" ["name"]=> string(5) "SKISA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(381) " This tms380 module supports SysKonnect TR4/16 ISA cards. These cards are known to work: - SysKonnect TR4/16 ISA (SK-4190) This driver is available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called skisa. If you want to compile it as a module, say M here and read . " } [1094]=> array(11) { ["entry_id"]=> string(4) "1095" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Proteon ISA support" ["name"]=> string(7) "PROTEON" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(374) " This tms380 module supports Proteon ISA cards. These cards are known to work: - Proteon 1392 - Proteon 1392 plus This driver is available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called proteon. If you want to compile it as a module, say M here and read . " } [1095]=> array(11) { ["entry_id"]=> string(4) "1096" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Madge Smart 16/4 PCI Mk2 support" ["name"]=> string(5) "ABYSS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(330) " This tms380 module supports the Madge Smart 16/4 PCI Mk2 cards (51-02). This driver is available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called abyss. If you want to compile it as a module, say M here and read . " } [1096]=> array(11) { ["entry_id"]=> string(4) "1097" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(38) "Madge Smart 16/4 Ringnode MicroChannel" ["name"]=> string(7) "MADGEMC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(346) " This tms380 module supports the Madge Smart 16/4 MC16 and MC32 MicroChannel adapters. This driver is available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called madgemc. If you want to compile it as a module, say M here and read . " } [1097]=> array(11) { ["entry_id"]=> string(4) "1098" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "SMC ISA/MCA adapter support" ["name"]=> string(5) "SMCTR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(619) " This is support for the ISA and MCA SMC Token Ring cards, specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A (8115T/A) adapters. If you have such an adapter and would like to use it, say Y or M and read the Token-Ring mini-HOWTO, available from and the file . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smctr. If you want to compile it as a module, say M here and read . " } [1098]=> array(11) { ["entry_id"]=> string(4) "1099" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Fibre Channel driver support" ["name"]=> string(6) "NET_FC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(392) " Fibre Channel is a high speed serial protocol mainly used to connect large storage devices to the computer; it is compatible with and intended to replace SCSI. If you intend to use Fibre Channel, you need to have a Fibre channel adaptor card in your computer; say Y here and to the driver for your adaptor below. You also should have said Y to "SCSI support" and "SCSI generic support". " } [1099]=> array(11) { ["entry_id"]=> string(4) "1100" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "Interphase 5526 Tachyon chipset based adapter support" ["name"]=> string(10) "IPHASE5526" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> string(309) " Say Y here if you have a Fibre Channel adaptor of this kind. The driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called iph5526. For general information about modules read . " } [1100]=> array(11) { ["entry_id"]=> string(4) "1101" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Red Creek Hardware VPN (EXPERIMENTAL)" ["name"]=> string(5) "RCPCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(341) " This is a driver for hardware which provides a Virtual Private Network (VPN). Say Y if you have it. This code is also available as a module called rcpci ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [1101]=> array(11) { ["entry_id"]=> string(4) "1102" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Traffic Shaper (EXPERIMENTAL)" ["name"]=> string(6) "SHAPER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(891) " The traffic shaper is a virtual network device that allows you to limit the rate of outgoing data flow over some other network device. The traffic that you want to slow down can then be routed through these virtual devices. See for more information. An alternative to this traffic shaper is the experimental Class-Based Queueing (CBQ) scheduling support which you get if you say Y to "QoS and/or fair queueing" above. To set up and configure shaper devices, you need the shapecfg program, available from in the shaper package. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called shaper. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1102]=> array(11) { ["entry_id"]=> string(4) "1103" ["entry_type"]=> string(4) "MENU" ["text"]=> string(14) "Wan interfaces" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1103]=> array(11) { ["entry_id"]=> string(4) "1104" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Wan interfaces support" ["name"]=> string(3) "WAN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(623) " Wide Area Networks (WANs), such as X.25, frame relay and leased lines, are used to interconnect Local Area Networks (LANs) over vast distances with data transfer rates significantly higher than those achievable with commonly used asynchronous modem connections. Usually, a quite expensive external device called a `WAN router' is needed to connect to a WAN. As an alternative, a relatively inexpensive WAN interface card can allow your Linux box to directly connect to a WAN. If you have one of those cards and wish to use it under Linux, say Y here and also to the WAN driver for your card, below. If unsure, say N. " } [1104]=> array(11) { ["entry_id"]=> string(4) "1105" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Comtrol Hostess SV-11 support" ["name"]=> string(12) "HOSTESS_SV11" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(183) " This is a network card for low speed synchronous serial links, at up to 256Kbps. It supports both PPP and Cisco HDLC. At this point, the driver can only be compiled as a module. " } [1105]=> array(11) { ["entry_id"]=> string(4) "1106" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "COSA/SRP sync serial boards support" ["name"]=> string(4) "COSA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(990) " This is a driver for COSA and SRP synchronous serial boards. These boards allow to connect synchronous serial devices (for example base-band modems, or any other device with the X.21, V.24, V.35 or V.36 interface) to your Linux box. The cards can work as the character device, synchronous PPP network device, or the Cisco HDLC network device. To actually use the COSA or SRP board, you will need user-space utilities for downloading the firmware to the cards and to set them up. Look at the for more information about the cards (including the pointer to the user-space utilities). You can also read the comment at the top of the for details about the cards and the driver itself. The driver will be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cosa. For general information about modules read . " } [1106]=> array(11) { ["entry_id"]=> string(4) "1107" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(50) "MultiGate (COMX) synchronous serial boards support" ["name"]=> string(4) "COMX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(563) " Say Y if you want to use any board from the MultiGate (COMX) family. These boards are synchronous serial adapters for the PC, manufactured by ITConsult-Pro Co, Hungary. Read for help on configuring and using COMX interfaces. Further info on these cards can be found at or . You must say Y to "/proc file system support" (CONFIG_PROC_FS) to use this driver. If you want to compile this as a module, say M and read . The module will be called comx. " } [1107]=> array(11) { ["entry_id"]=> string(4) "1108" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Support for COMX/CMX/HiCOMX boards" ["name"]=> string(12) "COMX_HW_COMX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(357) " Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the MultiGate family. Say Y if you have one of these. You will need additional firmware to use these cards, which are downloadable from . If you want to compile this as a module, say M and read . The module will be called comx-hw-comx. " } [1108]=> array(11) { ["entry_id"]=> string(4) "1109" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Support for LoCOMX board" ["name"]=> string(14) "COMX_HW_LOCOMX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(241) " Hardware driver for the 'LoCOMX' board from the MultiGate family. Say Y if you have a board like this. If you want to compile this as a module, say M and read . The module will be called comx-hw-locomx. " } [1109]=> array(11) { ["entry_id"]=> string(4) "1110" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Support for MixCOM board" ["name"]=> string(14) "COMX_HW_MIXCOM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(586) " Hardware driver for the 'MixCOM' board from the MultiGate family. Say Y if you have a board like this. If you want to use the watchdog device on this card, you should select it in the Watchdog Cards section of the Character Devices configuration. The ISDN interface of this card is Teles 16.3 compatible, you should enable it in the ISDN configuration menu. The driver for the flash ROM of this card is available separately on . If you want to compile this as a module, say M and read . The module will be called comx-hw-mixcom. " } [1110]=> array(11) { ["entry_id"]=> string(4) "1111" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "Support for MUNICH based boards: SliceCOM, PCICOM (WelCOM)" ["name"]=> string(14) "COMX_HW_MUNICH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(555) " Hardware driver for the 'SliceCOM' (channelized E1) and 'PciCOM' boards (X21) from the MultiGate family. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called comx-hw-munich. If you want to compile it as a module, say M here and read Documentation/modules.txt. Read linux/Documentation/networking/slicecom.txt for help on configuring and using SliceCOM interfaces. Further info on these cards can be found at http://www.itc.hu or . " } [1111]=> array(11) { ["entry_id"]=> string(4) "1112" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(58) "Support for HDLC and syncPPP protocols on MultiGate boards" ["name"]=> string(14) "COMX_PROTO_PPP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(278) " Cisco-HDLC and synchronous PPP protocol driver for all MultiGate boards. Say Y if you want to use either protocol on your MultiGate boards. If you want to compile this as a module, say M and read . The module will be called comx-proto-ppp. " } [1112]=> array(11) { ["entry_id"]=> string(4) "1113" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(45) "Support for LAPB protocol on MultiGate boards" ["name"]=> string(15) "COMX_PROTO_LAPB" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(251) " LAPB protocol driver for all MultiGate boards. Say Y if you want to use this protocol on your MultiGate boards. If you want to compile this as a module, say M and read . The module will be called comx-proto-lapb. " } [1113]=> array(11) { ["entry_id"]=> string(4) "1114" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Support for Frame Relay on MultiGate boards" ["name"]=> string(13) "COMX_PROTO_FR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(256) " Frame Relay protocol driver for all MultiGate boards. Say Y if you want to use this protocol on your MultiGate boards. If you want to compile this as a module, say M and read . The module will be called comx-proto-fr. " } [1114]=> array(11) { ["entry_id"]=> string(4) "1115" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Etinc PCISYNC serial board support" ["name"]=> string(5) "DSCC4" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(498) " This is a driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens) DSCC4 chipset. It is supposed to work with the four ports card. Take a look at for further informations about the driver and his configuration. The driver will be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dscc4. For general information about modules read . " } [1115]=> array(11) { ["entry_id"]=> string(4) "1116" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(47) "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards" ["name"]=> string(8) "LANMEDIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(906) " This is a driver for the following Lan Media family of serial boards. LMC 1000 board allows you to connect synchronous serial devices (for example base-band modems, or any other device with the X.21, V.24, V.35 or V.36 interface) to your Linux box. LMC 1200 with on board DSU board allows you to connect your Linux box dirrectly to a T1 or E1 circuit. LMC 5200 board provides a HSSI interface capable of running up to 52 mbits per second. LMC 5245 board connects directly to a T3 circuit saving the additional external hardware. To change setting such as syncPPP vs cisco HDLC or clock source you will need lmcctl. It is available at . This code is also available as a module called lmc ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say M here and read . " } [1116]=> array(11) { ["entry_id"]=> string(4) "1117" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Sealevel Systems 4021 support" ["name"]=> string(13) "SEALEVEL_4021" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(281) " This is a driver for the Sealevel Systems ACB 56 serial I/O adapter. This driver can only be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to do that, say M here. The module will be called sealevel. " } [1117]=> array(11) { ["entry_id"]=> string(4) "1118" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "SyncLink HDLC/SYNCPPP support" ["name"]=> string(16) "SYNCLINK_SYNCPPP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(295) " Enables HDLC/SYNCPPP support for the SyncLink WAN driver. Normally the SyncLink WAN driver works with the main PPP driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use of the Cisco HDLC/PPP driver (syncppp.c). The SyncLink WAN driver (in character devices) must also be enabled. " } [1118]=> array(11) { ["entry_id"]=> string(4) "1119" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Generic HDLC layer" ["name"]=> string(4) "HDLC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(603) " Say Y to this option if your Linux box contains a WAN card supported by this driver and you are planning to connect the box to a WAN ( = Wide Area Network). You will need supporting software from . Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame Relay, synchronous Point-to-Point Protocol (PPP) and X.25. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called hdlc. If unsure, say N here. " } [1119]=> array(11) { ["entry_id"]=> string(4) "1120" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Raw HDLC support" ["name"]=> string(8) "HDLC_RAW" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(143) " Say Y to this option if you want generic HDLC driver to support raw HDLC over WAN (Wide Area Network) connections. If unsure, say N here. " } [1120]=> array(11) { ["entry_id"]=> string(4) "1121" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Raw HDLC Ethernet device support" ["name"]=> string(12) "HDLC_RAW_ETH" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(218) " Say Y to this option if you want generic HDLC driver to support raw HDLC Ethernet device emulation over WAN (Wide Area Network) connections. You will need it for Ethernet over HDLC bridges. If unsure, say N here. " } [1121]=> array(11) { ["entry_id"]=> string(4) "1122" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Cisco HDLC support" ["name"]=> string(10) "HDLC_CISCO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(145) " Say Y to this option if you want generic HDLC driver to support Cisco HDLC over WAN (Wide Area Network) connections. If unsure, say N here. " } [1122]=> array(11) { ["entry_id"]=> string(4) "1123" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Frame Relay support" ["name"]=> string(7) "HDLC_FR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(155) " Say Y to this option if you want generic HDLC driver to support Frame-Relay protocol over WAN (Wide Area Network) connections. If unsure, say N here. " } [1123]=> array(11) { ["entry_id"]=> string(4) "1124" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "Synchronous Point-to-Point Protocol (PPP) support" ["name"]=> string(8) "HDLC_PPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(138) " Say Y to this option if you want generic HDLC driver to support PPP over WAN (Wide Area Network) connections. If unsure, say N here. " } [1124]=> array(11) { ["entry_id"]=> string(4) "1125" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "X.25 protocol support" ["name"]=> string(8) "HDLC_X25" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(148) " Say Y to this option if you want generic HDLC driver to support X.25 protocol over WAN (Wide Area Network) connections. If unsure, say N here. " } [1125]=> array(11) { ["entry_id"]=> string(4) "1126" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(56) "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)" ["name"]=> string(5) "PC300" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(612) " This is a driver for the Cyclades-PC300 synchronous communication boards. These boards provide synchronous serial interfaces to your Linux box (interfaces currently available are RS-232/V.35, X.21 and T1/E1). If you wish to support Multilink PPP, please select the option below this one and read the file README.mlppp provided by PC300 package. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called pc300. If you haven't heard about it, it's safe to say N. " } [1126]=> array(11) { ["entry_id"]=> string(4) "1127" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Cyclades-PC300 MLPPP support" ["name"]=> string(11) "PC300_MLPPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(117) " Say 'Y' to this option if you are planning to use Multilink PPP over the PC300 synchronous communication boards. " } [1127]=> array(11) { ["entry_id"]=> string(4) "1128" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "SDL RISCom/N2 support" ["name"]=> string(2) "N2" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(489) " This driver is for RISCom/N2 single or dual channel ISA cards made by SDL Communications Inc. If you have such a card, say Y here and see . Note that N2csu and N2dds cards are not supported by this driver. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called n2. If unsure, say N here. " } [1128]=> array(11) { ["entry_id"]=> string(4) "1129" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "Moxa C101 support" ["name"]=> string(4) "C101" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(408) " This driver is for C101 SuperSync ISA cards made by Moxa Technologies Co., Ltd. If you have such a card, say Y here and see If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called c101. If unsure, say N here. " } [1129]=> array(11) { ["entry_id"]=> string(4) "1130" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "FarSync T-Series support" ["name"]=> string(7) "FARSYNC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(685) " This driver supports the FarSync T-Series X.21 (and V.35/V.24) cards from FarSite Communications Ltd. Synchronous communication is supported on all ports at speeds up to 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC, Frame Relay or X.25/LAPB. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want) say M here and read . The module will be called farsync and if you want the module to be automatically loaded when the interface is referenced then you should add "alias hdlcX farsync" to /etc/modules.conf for each interface, where X is 0, 1, 2, ... " } [1130]=> array(11) { ["entry_id"]=> string(4) "1131" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Frame relay DLCI support" ["name"]=> string(4) "DLCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(945) " This is support for the frame relay protocol; frame relay is a fast low-cost way to connect to a remote Internet access provider or to form a private wide area network. The one physical line from your box to the local "switch" (i.e. the entry point to the frame relay network, usually at the phone company) can carry several logical point-to-point connections to other computers connected to the frame relay network. For a general explanation of the protocol, check out on the WWW. To use frame relay, you need supporting hardware (called FRAD) and certain programs from the net-tools package as explained in . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called dlci. If you want to compile it as a module, say M here and read . " } [1131]=> array(11) { ["entry_id"]=> string(4) "1132" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(10) "DLCI_COUNT" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(13) "Max open DLCI" ["help_text"]=> NULL } [1132]=> array(11) { ["entry_id"]=> string(4) "1133" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(8) "DLCI_MAX" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(19) "Max DLCI per device" ["help_text"]=> NULL } [1133]=> array(11) { ["entry_id"]=> string(4) "1134" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "SDLA (Sangoma S502/S508) support" ["name"]=> string(4) "SDLA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(504) " Say Y here if you need a driver for the Sangoma S502A, S502E, and S508 Frame Relay Access Devices. These are multi-protocol cards, but only frame relay is supported by the driver at this time. Please read . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called sdla. If you want to compile it as a module, say M here and read . " } [1134]=> array(11) { ["entry_id"]=> string(4) "1135" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "WAN router drivers" ["name"]=> string(18) "WAN_ROUTER_DRIVERS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(626) " If you have a WAN interface card and you want your Linux box to act as a WAN router, thereby connecting you Local Area Network to the outside world over the WAN connection, say Y here and then to the driver for your card below. In addition, you need to say Y to "Wan Router". You will need the wan-tools package which is available from . Read for more information. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about WAN router drivers. If unsure, say N. " } [1135]=> array(11) { ["entry_id"]=> string(4) "1136" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Sangoma WANPIPE(tm) multiprotocol cards" ["name"]=> string(14) "VENDOR_SANGOMA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1001) " WANPIPE from Sangoma Technologies Inc. () is a family of intelligent multiprotocol WAN adapters with data transfer rates up to 4Mbps. They are also known as Synchronous Data Link Adapters (SDLA) and are designated as S514-PCI or S508-ISA. These cards support - X.25, Frame Relay, PPP, Cisco HDLC protocols. - API support for protocols like HDLC (LAPB), HDLC Streaming, X.25, Frame Relay and BiSync. - Ethernet Bridging over Frame Relay protocol. - MULTILINK PPP - Async PPP (Modem Dialup) If you have one or more of these cards, say M to this option; you may then also want to read the file . The next questions will ask you about the protocols you want the driver to support. The driver will be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wanpipe. For general information about modules read . " } [1136]=> array(11) { ["entry_id"]=> string(4) "1137" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "WANPIPE Cisco HDLC support" ["name"]=> string(13) "WANPIPE_CHDLC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(519) " Say Y to this option if you are planning to connect a WANPIPE card to a leased line using the Cisco HDLC protocol. This now supports Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards. This support also allows user to build applications using the HDLC streaming API. CHDLC Streaming driver also supports MULTILINK PPP support that can bind multiple WANPIPE T1 cards into a single logical channel. If you say N, the Cisco HDLC support and HDLC streaming API and MULTILINK PPP will not be included in the driver. " } [1137]=> array(11) { ["entry_id"]=> string(4) "1138" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "WANPIPE Frame Relay support" ["name"]=> string(10) "WANPIPE_FR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(481) " Say Y to this option if you are planning to connect a WANPIPE card to a frame relay network, or use frame relay API to develope custom applications over the Frame Relay protocol. This feature also contains the Ethernet Bridging over Frame Relay, where a WANPIPE frame relay link can be directly connected to the Linux kernel bridge. If you say N, the frame relay support will not be included in the driver. The Frame Relay option is supported on S514-PCI and S508-ISA cards. " } [1138]=> array(11) { ["entry_id"]=> string(4) "1139" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "WANPIPE X.25 support" ["name"]=> string(11) "WANPIPE_X25" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(335) " Say Y to this option if you are planning to connect a WANPIPE card to an X.25 network. Note, this feature also includes the X.25 API support used to develope custom applications over the X.25 protocol. If you say N, the X.25 support will not be included in the driver. The X.25 option is supported on S514-PCI and S508-ISA cards. " } [1139]=> array(11) { ["entry_id"]=> string(4) "1140" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "WANPIPE PPP support" ["name"]=> string(11) "WANPIPE_PPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(247) " Say Y to this option if you are planning to connect a WANPIPE card to a leased line using Point-to-Point protocol (PPP). If you say N, the PPP support will not be included in the driver. The PPP option is supported on S514-PCI/S508-ISA cards. " } [1140]=> array(11) { ["entry_id"]=> string(4) "1141" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "WANPIPE Multi-Port PPP support" ["name"]=> string(15) "WANPIPE_MULTPPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(526) " Say Y to this option if you are planning to connect a WANPIPE card to a leased line using Point-to-Point protocol (PPP). Note, the MultiPort PPP uses the Linux Kernel SyncPPP protocol over the Sangoma HDLC Streaming adapter. In this case each Sangoma adapter port can support an independent PPP connection. For example, a single Quad-Port PCI adapter can support up to four independent PPP links. If you say N,the PPP support will not be included in the driver. The PPP option is supported on S514-PCI/S508-ISA cards. " } [1141]=> array(11) { ["entry_id"]=> string(4) "1142" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Cyclom 2X(tm) cards (EXPERIMENTAL)" ["name"]=> string(13) "CYCLADES_SYNC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1230) " Cyclom 2X from Cyclades Corporation ( and ) is an intelligent multiprotocol WAN adapter with data transfer rates up to 512 Kbps. These cards support the X.25 and SNA related protocols. If you have one or more of these cards, say Y to this option. The next questions will ask you about the protocols you want the driver to support (for now only X.25 is supported). While no documentation is available at this time please grab the wanconfig tarball in (with minor changes to make it compile with the current wanrouter include files; efforts are being made to use the original package available at ). Feel free to contact me or the cycsyn-devel mailing list at acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for additional details, I hope to have documentation available as soon as possible. (Cyclades Brazil is writing the Documentation). The driver will be compiled as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called cyclomx. For general information about modules read . " } [1142]=> array(11) { ["entry_id"]=> string(4) "1143" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Cyclom 2X X.25 support (EXPERIMENTAL)" ["name"]=> string(11) "CYCLOMX_X25" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(198) " Say Y to this option if you are planning to connect a Cyclom 2X card to an X.25 network. If you say N, the X.25 support will not be included in the driver (saves about 11 KB of kernel memory). " } [1143]=> array(11) { ["entry_id"]=> string(4) "1144" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "LAPB over Ethernet driver (EXPERIMENTAL)" ["name"]=> string(9) "LAPBETHER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(549) " This is a driver for a pseudo device (typically called /dev/lapb0) which allows you to open an LAPB point-to-point connection to some other computer on your Ethernet network. In order to do this, you need to say Y or M to the driver for your Ethernet card as well as to "LAPB Data Link Driver". If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called lapbether. If unsure, say N. " } [1144]=> array(11) { ["entry_id"]=> string(4) "1145" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "X.25 async driver (EXPERIMENTAL)" ["name"]=> string(7) "X25_ASY" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(538) " This is a driver for sending and receiving X.25 frames over regular asynchronous serial lines such as telephone lines equipped with ordinary modems. Experts should note that this driver doesn't currently comply with the asynchronous HDLS framing protocols in CCITT recommendation X.25. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called x25_asy. If unsure, say N. " } [1145]=> array(11) { ["entry_id"]=> string(4) "1146" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Granch SBNI12 Leased Line adapter support" ["name"]=> string(4) "SBNI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(407) " This is a driver for ISA SBNI12-xx cards which are low cost alternatives to leased line modems. Say Y if you want to insert the driver into the kernel or say M to compile it as a module (the module will be called sbni). You can find more information and last versions of drivers and utilities at . If you have any question you can send email to sbni@granch.ru. Say N if unsure. " } [1146]=> array(11) { ["entry_id"]=> string(4) "1147" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Multiple line feature support" ["name"]=> string(14) "SBNI_MULTILINE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(267) " Schedule traffic for some parallel lines, via SBNI12 adapters. If you have two computers connected with two parallel lines it's possible to increase transfer rate nearly twice. You should have a program named 'sbniconfig' to configure adapters. Say N if unsure. " } [1147]=> array(11) { ["entry_id"]=> string(4) "1148" ["entry_type"]=> string(4) "MENU" ["text"]=> string(29) "PCMCIA network device support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1148]=> array(11) { ["entry_id"]=> string(4) "1149" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "PCMCIA network device support" ["name"]=> string(10) "NET_PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(554) " Say Y if you would like to include support for any PCMCIA or CardBus network adapters, then say Y to the driver for your particular card below. PCMCIA- or PC-cards are credit-card size devices often used with laptops computers; CardBus is the newer and faster version of PCMCIA. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). You also want to check out the PCMCIA-HOWTO, available from . If unsure, say N. " } [1149]=> array(11) { ["entry_id"]=> string(4) "1150" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "3Com 3c589 PCMCIA support" ["name"]=> string(12) "PCMCIA_3C589" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(396) " Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA (PC-card) Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c589_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1150]=> array(11) { ["entry_id"]=> string(4) "1151" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "3Com 3c574 PCMCIA support" ["name"]=> string(12) "PCMCIA_3C574" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(402) " Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA (PC-card) Fast Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called 3c574_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1151]=> array(11) { ["entry_id"]=> string(4) "1152" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Fujitsu FMV-J18x PCMCIA support" ["name"]=> string(14) "PCMCIA_FMVJ18X" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(404) " Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible PCMCIA (PC-card) Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called fmvj18x_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1152]=> array(11) { ["entry_id"]=> string(4) "1153" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "NE2000 compatible PCMCIA support" ["name"]=> string(12) "PCMCIA_PCNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(407) " Say Y here if you intend to attach an NE2000 compatible PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called pcnet_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1153]=> array(11) { ["entry_id"]=> string(4) "1154" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "New Media PCMCIA support" ["name"]=> string(13) "PCMCIA_NMCLAN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(404) " Say Y here if you intend to attach a New Media Ethernet or LiveWire PCMCIA (PC-card) Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called nmclan_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1154]=> array(11) { ["entry_id"]=> string(4) "1155" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "SMC 91Cxx PCMCIA support" ["name"]=> string(15) "PCMCIA_SMC91C92" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(413) " Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc91c92_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1155]=> array(11) { ["entry_id"]=> string(4) "1156" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "Xircom 16-bit PCMCIA support" ["name"]=> string(14) "PCMCIA_XIRC2PS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(404) " Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called xirc2ps_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1156]=> array(11) { ["entry_id"]=> string(4) "1157" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Asix AX88190 PCMCIA support" ["name"]=> string(12) "PCMCIA_AXNET" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(492) " Say Y here if you intend to attach an Asix AX88190-based PCMCIA (PC-card) Fast Ethernet card to your computer. These cards are nearly NE2000 compatible but need a separate driver due to a few misfeatures. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called axnet_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1157]=> array(11) { ["entry_id"]=> string(4) "1158" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "COM20020 ARCnet PCMCIA support" ["name"]=> string(18) "ARCNET_COM20020_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(373) " Say Y here if you intend to attach this type of ARCnet PCMCIA card to your computer. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called com20020_cs. If you want to compile it as a module, say M here and read . If unsure, say N. " } [1158]=> array(11) { ["entry_id"]=> string(4) "1159" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "IBM PCMCIA tokenring adapter support" ["name"]=> string(12) "PCMCIA_IBMTR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(416) " Say Y here if you intend to attach this type of Token Ring PCMCIA card to your computer. You then also need to say Y to "Token Ring driver support". This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ibmtr_cs. If you want to compile it as a module, say M here and read . " } [1159]=> array(11) { ["entry_id"]=> string(4) "1160" ["entry_type"]=> string(4) "MENU" ["text"]=> string(11) "ATM drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1160]=> array(11) { ["entry_id"]=> string(4) "1161" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "ATM over TCP" ["name"]=> string(7) "ATM_TCP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(94) " ATM over TCP driver. Useful mainly for development and for experiments. If unsure, say N. " } [1161]=> array(11) { ["entry_id"]=> string(4) "1162" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "Efficient Networks Speedstream 3010" ["name"]=> string(9) "ATM_LANAI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(244) " Supports ATM cards based on the Efficient Networks "Lanai" chipset such as the Speedstream 3010 and the ENI-25p. The Speedstream 3060 is currently not supported since we don't have the code to drive the on-board Alcatel DSL chipset (yet). " } [1162]=> array(11) { ["entry_id"]=> string(4) "1163" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "Efficient Networks ENI155P" ["name"]=> string(7) "ATM_ENI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(511) " Driver for the Efficient Networks ENI155p series and SMC ATM Power155 155 Mbps ATM adapters. Both, the versions with 512KB and 2MB on-board RAM (Efficient calls them "C" and "S", respectively), and the FPGA and the ASIC Tonga versions of the board are supported. The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D) adapters. This driver is also available as a module. If you want to compile it as a module, say M here and read . The module will be called eni. " } [1163]=> array(11) { ["entry_id"]=> string(4) "1164" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable extended debugging" ["name"]=> string(13) "ATM_ENI_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(331) " Extended debugging records various events and displays that list when an inconsistency is detected. This mechanism is faster than generally using printks, but still has some impact on performance. Note that extended debugging may create certain race conditions itself. Enable this ONLY if you suspect problems with the driver. " } [1164]=> array(11) { ["entry_id"]=> string(4) "1165" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Fine-tune burst settings" ["name"]=> string(18) "ATM_ENI_TUNE_BURST" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(898) " In order to obtain good throughput, the ENI NIC can transfer multiple words of data per PCI bus access cycle. Such a multi-word transfer is called a burst. The default settings for the burst sizes are suitable for most PCI chipsets. However, in some cases, large bursts may overrun buffers in the PCI chipset and cause data corruption. In such cases, large bursts must be disabled and only (slower) small bursts can be used. The burst sizes can be set independently in the send (TX) and receive (RX) direction. Note that enabling many different burst sizes in the same direction may increase the cost of setting up a transfer such that the resulting throughput is lower than when using only the largest available burst size. Also, sometimes larger bursts lead to lower throughput, e.g. on an Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed when going from 8W to 16W bursts. " } [1165]=> array(11) { ["entry_id"]=> string(4) "1166" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Enable 16W TX bursts (discouraged)" ["name"]=> string(20) "ATM_ENI_BURST_TX_16W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(137) " Burst sixteen words at once in the send direction. This may work with recent PCI chipsets, but is known to fail with older chipsets. " } [1166]=> array(11) { ["entry_id"]=> string(4) "1167" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Enable 8W TX bursts (recommended)" ["name"]=> string(19) "ATM_ENI_BURST_TX_8W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(82) " Burst eight words at once in the send direction. This is the default setting. " } [1167]=> array(11) { ["entry_id"]=> string(4) "1168" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Enable 4W TX bursts (optional)" ["name"]=> string(19) "ATM_ENI_BURST_TX_4W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(174) " Burst four words at once in the send direction. You may want to try this if you have disabled 8W bursts. Enabling 4W if 8W is also set may or may not improve throughput. " } [1168]=> array(11) { ["entry_id"]=> string(4) "1169" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Enable 2W TX bursts (optional)" ["name"]=> string(19) "ATM_ENI_BURST_TX_2W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(187) " Burst two words at once in the send direction. You may want to try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W are also set may or may not improve throughput. " } [1169]=> array(11) { ["entry_id"]=> string(4) "1170" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "Enable 16W RX bursts (discouraged)" ["name"]=> string(20) "ATM_ENI_BURST_RX_16W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(140) " Burst sixteen words at once in the receive direction. This may work with recent PCI chipsets, but is known to fail with older chipsets. " } [1170]=> array(11) { ["entry_id"]=> string(4) "1171" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Enable 8W RX bursts (discouraged)" ["name"]=> string(19) "ATM_ENI_BURST_RX_8W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(172) " Burst eight words at once in the receive direction. This may work with recent PCI chipsets, but is known to fail with older chipsets, such as the Intel Neptune series. " } [1171]=> array(11) { ["entry_id"]=> string(4) "1172" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Enable 4W RX bursts (recommended)" ["name"]=> string(19) "ATM_ENI_BURST_RX_4W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(149) " Burst four words at once in the receive direction. This is the default setting. Enabling 4W if 8W is also set may or may not improve throughput. " } [1172]=> array(11) { ["entry_id"]=> string(4) "1173" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Enable 2W RX bursts (optional)" ["name"]=> string(19) "ATM_ENI_BURST_RX_2W" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(190) " Burst two words at once in the receive direction. You may want to try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W are also set may or may not improve throughput. " } [1173]=> array(11) { ["entry_id"]=> string(4) "1174" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Fujitsu FireStream (FS50/FS155) " ["name"]=> string(14) "ATM_FIRESTREAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(272) " Driver for the Fujitsu FireStream 155 (MB86697) and FireStream 50 (MB86695) ATM PCI chips. This driver is also available as a module. If you want to compile it as a module, say M here and read . The module will be called firestream. " } [1174]=> array(11) { ["entry_id"]=> string(4) "1175" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "ZeitNet ZN1221/ZN1225" ["name"]=> string(8) "ATM_ZATM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(253) " Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM adapters. This driver is also available as a module. If you want to compile it as a module, say M here and read . The module will be called zatm. " } [1175]=> array(11) { ["entry_id"]=> string(4) "1176" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable extended debugging" ["name"]=> string(14) "ATM_ZATM_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(331) " Extended debugging records various events and displays that list when an inconsistency is detected. This mechanism is faster than generally using printks, but still has some impact on performance. Note that extended debugging may create certain race conditions itself. Enable this ONLY if you suspect problems with the driver. " } [1176]=> array(11) { ["entry_id"]=> string(4) "1177" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Enable usec resolution timestamps" ["name"]=> string(17) "ATM_ZATM_EXACT_TS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(421) " The uPD98401 SAR chip supports a high-resolution timer (approx. 30 MHz) that is used for very accurate reception timestamps. Because that timer overflows after 140 seconds, and also to avoid timer drift, time measurements need to be periodically synchronized with the normal system time. Enabling this feature will add some general overhead for timer synchronization and also per-packet overhead for time conversion. " } [1177]=> array(11) { ["entry_id"]=> string(4) "1178" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(34) "IDT 77201 (NICStAR) (ForeRunnerLE)" ["name"]=> string(11) "ATM_NICSTAR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(353) " The NICStAR chipset family is used in a large number of ATM NICs for 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE series. Say Y if you have one of those. This driver is also available as a module. If you want to compile it as a module, say M here and read . The module will be called nicstar. " } [1178]=> array(11) { ["entry_id"]=> string(4) "1179" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Use suni PHY driver (155Mbps)" ["name"]=> string(20) "ATM_NICSTAR_USE_SUNI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(424) " Support for the S-UNI and compatible PHYsical layer chips. These are found in most 155Mbps NICStAR based ATM cards, namely in the ForeRunner LE155 cards. This driver provides detection of cable~ removal and reinsertion and provides some statistics. This driver doesn't have removal capability when compiled as a module, so if you need that capability don't include S-UNI support (it's not needed to make the card work). " } [1179]=> array(11) { ["entry_id"]=> string(4) "1180" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "Use IDT77015 PHY driver (25Mbps)" ["name"]=> string(24) "ATM_NICSTAR_USE_IDT77105" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(339) " Support for the PHYsical layer chip in ForeRunner LE25 cards. In addition to cable removal/reinsertion detection, this driver allows you to control the loopback mode of the chip via a dedicated IOCTL. This driver is required for proper handling of temporary carrier loss, so if you have a 25Mbps NICStAR based ATM card you must say Y. " } [1180]=> array(11) { ["entry_id"]=> string(4) "1181" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "IDT 77252 (NICStAR II)" ["name"]=> string(12) "ATM_IDT77252" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(217) " Driver for the IDT 77252 ATM PCI chips. This driver is also available as a module. If you want to compile it as a module, say M here and read . The module will be called idt77252 " } [1181]=> array(11) { ["entry_id"]=> string(4) "1182" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable debugging messages" ["name"]=> string(18) "ATM_IDT77252_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(424) " Somewhat useful debugging messages are available. The choice of messages is controlled by a bitmap. This may be specified as a module argument. See the file for the meanings of the bits in the mask. When active, these messages can have a significant impact on the speed of the driver, and the size of your syslog files! When inactive, they will have only a modest impact on performance. " } [1182]=> array(11) { ["entry_id"]=> string(4) "1183" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Receive ALL cells in raw queue" ["name"]=> string(20) "ATM_IDT77252_RCV_ALL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(202) " Enable receiving of all cells on the ATM link, that do not match an open connection in the raw cell queue of the driver. Useful for debugging or special applications only, so the safe answer is N. " } [1183]=> array(11) { ["entry_id"]=> string(4) "1184" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "ATM_IDT77252_USE_SUNI" ["name"]=> string(21) "ATM_IDT77252_USE_SUNI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> NULL } [1184]=> array(11) { ["entry_id"]=> string(4) "1185" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "Madge Ambassador (Collage PCI 155 Server)" ["name"]=> string(14) "ATM_AMBASSADOR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(170) " This is a driver for ATMizer based ATM card produced by Madge Networks Ltd. Say Y (or M to compile as a module named ambassador) here if you have one of these cards. " } [1185]=> array(11) { ["entry_id"]=> string(4) "1186" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable debugging messages" ["name"]=> string(20) "ATM_AMBASSADOR_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(590) " Somewhat useful debugging messages are available. The choice of messages is controlled by a bitmap. This may be specified as a module argument (kernel command line argument as well?), changed dynamically using an ioctl (not yet) or changed by sending the string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file for the meanings of the bits in the mask. When active, these messages can have a significant impact on the speed of the driver, and the size of your syslog files! When inactive, they will have only a modest impact on performance. " } [1186]=> array(11) { ["entry_id"]=> string(4) "1187" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(65) "Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)" ["name"]=> string(11) "ATM_HORIZON" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(187) " This is a driver for the Horizon chipset ATM adapter cards once produced by Madge Networks Ltd. Say Y (or M to compile as a module named horizon) here if you have one of these cards. " } [1187]=> array(11) { ["entry_id"]=> string(4) "1188" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable debugging messages" ["name"]=> string(17) "ATM_HORIZON_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(587) " Somewhat useful debugging messages are available. The choice of messages is controlled by a bitmap. This may be specified as a module argument (kernel command line argument as well?), changed dynamically using an ioctl (not yet) or changed by sending the string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file for the meanings of the bits in the mask. When active, these messages can have a significant impact on the speed of the driver, and the size of your syslog files! When inactive, they will have only a modest impact on performance. " } [1188]=> array(11) { ["entry_id"]=> string(4) "1189" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "Interphase ATM PCI x575/x525/x531" ["name"]=> string(6) "ATM_IA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(552) " This is a driver for the Interphase (i)ChipSAR adapter cards which include a variety of variants in term of the size of the control memory (128K-1KVC, 512K-4KVC), the size of the packet memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3, UTP155, UTP25, DS3 and E3). Go to: for more info about the cards. Say Y (or M to compile as a module named iphase) here if you have one of these cards. See the file for further details. " } [1189]=> array(11) { ["entry_id"]=> string(4) "1190" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Enable debugging messages" ["name"]=> string(12) "ATM_IA_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(570) " Somewhat useful debugging messages are available. The choice of messages is controlled by a bitmap. This may be specified as a module argument (kernel command line argument as well?), changed dynamically using an ioctl (Get the debug utility, iadbg, from ). See the file for the meanings of the bits in the mask. When active, these messages can have a significant impact on the speed of the driver, and the size of your syslog files! When inactive, they will have only a modest impact on performance. " } [1190]=> array(11) { ["entry_id"]=> string(4) "1191" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "FORE Systems 200E-series" ["name"]=> string(18) "ATM_FORE200E_MAYBE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(456) " This is a driver for the FORE Systems 200E-series ATM adapter cards. It simultaneously supports PCA-200E and SBA-200E models on PCI and SBUS hosts. Say Y (or M to compile as a module named fore_200e) here if you have one of these ATM adapters. Note that the driver will actually be compiled only if you additionally enable the support for PCA-200E and/or SBA-200E cards. See the file for further details. " } [1191]=> array(11) { ["entry_id"]=> string(4) "1192" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "PCA-200E support" ["name"]=> string(16) "ATM_FORE200E_PCA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(61) " Say Y here if you want your PCA-200E cards to be probed. " } [1192]=> array(11) { ["entry_id"]=> string(4) "1193" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Use default PCA-200E firmware (normally enabled)" ["name"]=> string(27) "ATM_FORE200E_PCA_DEFAULT_FW" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(154) " Use the default PCA-200E firmware data shipped with the driver. Normal users do not have to deal with the firmware stuff, so they should say Y here. " } [1193]=> array(11) { ["entry_id"]=> string(4) "1194" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "ATM_FORE200E_PCA_FW" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> string(41) "Pathname of user-supplied binary firmware" ["help_text"]=> NULL } [1194]=> array(11) { ["entry_id"]=> string(4) "1195" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "SBA-200E support" ["name"]=> string(16) "ATM_FORE200E_SBA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(61) " Say Y here if you want your SBA-200E cards to be probed. " } [1195]=> array(11) { ["entry_id"]=> string(4) "1196" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Use default SBA-200E firmware (normally enabled)" ["name"]=> string(27) "ATM_FORE200E_SBA_DEFAULT_FW" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(154) " Use the default SBA-200E firmware data shipped with the driver. Normal users do not have to deal with the firmware stuff, so they should say Y here. " } [1196]=> array(11) { ["entry_id"]=> string(4) "1197" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(19) "ATM_FORE200E_SBA_FW" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "20" ["content"]=> string(41) "Pathname of user-supplied binary firmware" ["help_text"]=> NULL } [1197]=> array(11) { ["entry_id"]=> string(4) "1198" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(21) "ATM_FORE200E_TX_RETRY" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(28) "Maximum number of tx retries" ["help_text"]=> NULL } [1198]=> array(11) { ["entry_id"]=> string(4) "1199" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(18) "ATM_FORE200E_DEBUG" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> string(21) "Debugging level (0-3)" ["help_text"]=> NULL } [1199]=> array(11) { ["entry_id"]=> string(4) "1200" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "ATM_FORE200E" ["name"]=> string(12) "ATM_FORE200E" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [1200]=> array(11) { ["entry_id"]=> string(4) "1201" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "ForeRunner HE Series" ["name"]=> string(6) "ATM_HE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(130) " This is a driver for the Marconi ForeRunner HE-series ATM adapter cards. It simultaneously supports the 155 and 622 versions. " } [1201]=> array(11) { ["entry_id"]=> string(4) "1202" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "Use S/UNI PHY driver" ["name"]=> string(15) "ATM_HE_USE_SUNI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(137) " Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner HE cards. This driver provides carrier detection some statistics. " } [1202]=> array(11) { ["entry_id"]=> string(4) "1203" ["entry_type"]=> string(4) "MENU" ["text"]=> string(28) "S/390 network device drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1203]=> array(11) { ["entry_id"]=> string(4) "1204" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Lan Channel Station Interface" ["name"]=> string(3) "LCS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(293) " Select this option if you want to use LCS networking on IBM S/390 or zSeries. This device driver supports Token Ring (IEEE 802.5), FDDI (IEEE 802.7) and Ethernet. This option is also available as a module which will be called lcs.ko. If you do not know what it is, it's safe to say "Y". " } [1204]=> array(11) { ["entry_id"]=> string(4) "1205" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "CTC device support" ["name"]=> string(3) "CTC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(402) " Select this option if you want to use channel-to-channel networking on IBM S/390 or zSeries. This device driver supports real CTC coupling using ESCON. It also supports virtual CTCs when running under VM. It will use the channel device configuration if this is available. This option is also available as a module which will be called ctc.ko. If you do not know what it is, it's safe to say "Y". " } [1205]=> array(11) { ["entry_id"]=> string(4) "1206" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "IUCV device support (VM only)" ["name"]=> string(4) "IUCV" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(197) " Select this option if you want to use inter-user communication vehicle networking under VM or VIF. This option is also available as a module which will be called iucv.ko. If unsure, say "Y". " } [1206]=> array(11) { ["entry_id"]=> string(4) "1207" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Gigabit Ethernet device support" ["name"]=> string(4) "QETH" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(539) " This driver supports the IBM S/390 and zSeries OSA Express adapters in QDIO mode (all media types), HiperSockets interfaces and VM GuestLAN interfaces in QDIO and HIPER mode. For details please refer to the documentation provided by IBM at This driver is also available as a module (code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a module, say 'M' here and read file Documentation/modules.txt. " } [1207]=> array(11) { ["entry_id"]=> string(4) "1208" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "IPv6 support for gigabit ethernet" ["name"]=> string(9) "QETH_IPV6" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(100) " If CONFIG_QETH is switched on, this option will include IPv6 support in the qeth device driver. " } [1208]=> array(11) { ["entry_id"]=> string(4) "1209" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "VLAN support for gigabit ethernet" ["name"]=> string(9) "QETH_VLAN" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(112) " If CONFIG_QETH is switched on, this option will include IEEE 802.1q VLAN support in the qeth device driver. " } [1209]=> array(11) { ["entry_id"]=> string(4) "1210" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Performance statistics in /proc" ["name"]=> string(15) "QETH_PERF_STATS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(230) " When switched on, this option will add a file in the proc-fs (/proc/qeth_perf_stats) containing performance statistics. It may slightly impact performance, so this is only recommended for internal tuning of the device driver. " } [1210]=> array(11) { ["entry_id"]=> string(4) "1211" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "CCWGROUP" ["name"]=> string(8) "CCWGROUP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "0" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> NULL } [1211]=> array(11) { ["entry_id"]=> string(4) "1212" ["entry_type"]=> string(4) "MENU" ["text"]=> string(21) "Amateur Radio support" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1212]=> array(11) { ["entry_id"]=> string(4) "1213" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Amateur Radio support" ["name"]=> string(8) "HAMRADIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(376) " If you want to connect your Linux box to an amateur radio, answer Y here. You want to read and the AX25-HOWTO, available from . Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about amateur radio. " } [1213]=> array(11) { ["entry_id"]=> string(4) "1214" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "Amateur Radio AX.25 Level 2 protocol" ["name"]=> string(4) "AX25" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(1455) " This is the protocol used for computer communication over amateur radio. It is either used by itself for point-to-point links, or to carry other protocols such as tcp/ip. To use it, you need a device that connects your Linux box to your amateur radio. You can either use a low speed TNC (a Terminal Node Controller acts as a kind of modem connecting your computer's serial port to your radio's microphone input and speaker output) supporting the KISS protocol or one of the various SCC cards that are supported by the generic Z8530 or the DMA SCC driver. Another option are the Baycom modem serial and parallel port hacks or the sound card modem (supported by their own drivers). If you say Y here, you also have to say Y to one of those drivers. Information about where to get supporting software for Linux amateur radio as well as information about how to configure an AX.25 port is contained in the AX25-HOWTO, available from . You might also want to check out the file in the kernel source. More information about digital amateur radio in general is on the WWW at . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called ax25. If you want to compile it as a module, say M here and read . " } [1214]=> array(11) { ["entry_id"]=> string(4) "1215" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "AX.25 DAMA Slave support" ["name"]=> string(15) "AX25_DAMA_SLAVE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(401) " DAMA is a mechanism to prevent collisions when doing AX.25 networking. A DAMA server (called "master") accepts incoming traffic from clients (called "slaves") and redistributes it to other slaves. If you say Y here, your Linux box will act as a DAMA slave; this is transparent in that you don't have to do any special DAMA configuration. (Linux cannot yet act as a DAMA server.) If unsure, say N. " } [1215]=> array(11) { ["entry_id"]=> string(4) "1216" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Amateur Radio NET/ROM protocol" ["name"]=> string(6) "NETROM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(760) " NET/ROM is a network layer protocol on top of AX.25 useful for routing. A comprehensive listing of all the software for Linux amateur radio users as well as information about how to configure an AX.25 port is contained in the AX25-HOWTO, available from . You also might want to check out the file . More information about digital amateur radio in general is on the WWW at . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called netrom. If you want to compile it as a module, say M here and read . " } [1216]=> array(11) { ["entry_id"]=> string(4) "1217" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Amateur Radio X.25 PLP (Rose)" ["name"]=> string(4) "ROSE" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(869) " The Packet Layer Protocol (PLP) is a way to route packets over X.25 connections in general and amateur radio AX.25 connections in particular, essentially an alternative to NET/ROM. A comprehensive listing of all the software for Linux amateur radio users as well as information about how to configure an AX.25 port is contained in the AX25-HOWTO, available from . You also might want to check out the file . More information about digital amateur radio in general is on the WWW at . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called rose. If you want to compile it as a module, say M here and read . " } [1217]=> array(11) { ["entry_id"]=> string(4) "1218" ["entry_type"]=> string(4) "MENU" ["text"]=> string(28) "AX.25 network device drivers" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1218]=> array(11) { ["entry_id"]=> string(4) "1219" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Serial port KISS driver" ["name"]=> string(5) "MKISS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(683) " KISS is a protocol used for the exchange of data between a computer and a Terminal Node Controller (a small embedded system commonly used for networking over AX.25 amateur radio connections; it connects the computer's serial port with the radio's microphone input and speaker output). Although KISS is less advanced than the 6pack protocol, it has the advantage that it is already supported by most modern TNCs without the need for a firmware upgrade. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called mkiss. " } [1219]=> array(11) { ["entry_id"]=> string(4) "1220" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Serial port 6PACK driver" ["name"]=> string(5) "6PACK" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(785) " 6pack is a transmission protocol for the data exchange between your PC and your TNC (the Terminal Node Controller acts as a kind of modem connecting your computer's serial port to your radio's microphone input and speaker output). This protocol can be used as an alternative to KISS for networking over AX.25 amateur radio connections, but it has some extended functionality. Note that this driver is still experimental and might cause problems. For details about the features and the usage of the driver, read . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called 6pack. " } [1220]=> array(11) { ["entry_id"]=> string(4) "1221" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "BPQ Ethernet driver" ["name"]=> string(8) "BPQETHER" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(295) " AX.25 is the protocol used for computer communication over amateur radio. If you say Y here, you will be able to send and receive AX.25 traffic over Ethernet (also called "BPQ AX.25"), which could be useful if some other computer on your local network has a direct amateur radio connection. " } [1221]=> array(11) { ["entry_id"]=> string(4) "1222" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "High-speed (DMA) SCC driver for AX.25" ["name"]=> string(6) "DMASCC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(1503) " This is a driver for high-speed SCC boards, i.e. those supporting DMA on one port. You usually use those boards to connect your computer to an amateur radio modem (such as the WA4DSY 56kbps modem), in order to send and receive AX.25 packet radio network traffic. Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis PackeTwin, and S5SCC/DMA boards. They are detected automatically. If you have one of these cards, say Y here and read the AX25-HOWTO, available from . This driver can operate multiple boards simultaneously. If you compile it as a module (by saying M instead of Y), it will be called dmascc. If you don't pass any parameter to the driver, all possible I/O addresses are probed. This could irritate other devices that are currently not in use. You may specify the list of addresses to be probed by "dmascc=addr1,addr2,..." (when compiled into the kernel image) or "io=addr1,addr2,..." (when loaded as a module). The network interfaces will be called dmascc0 and dmascc1 for the board detected first, dmascc2 and dmascc3 for the second one, and so on. Before you configure each interface with ifconfig, you MUST set certain parameters, such as channel access timing, clock mode, and DMA channel. This is accomplished with a small utility program, dmascc_cfg, available at . Please be sure to get at least version 1.27 of dmascc_cfg, as older versions will not work with the current driver. " } [1222]=> array(11) { ["entry_id"]=> string(4) "1223" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Z8530 SCC driver" ["name"]=> string(3) "SCC" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(549) " These cards are used to connect your Linux box to an amateur radio in order to communicate with other computers. If you want to use this, read and the AX25-HOWTO, available from . Also make sure to say Y to "Amateur Radio AX.25 Level 2" support. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called scc. " } [1223]=> array(11) { ["entry_id"]=> string(4) "1224" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(53) "additional delay for PA0HZP OptoSCC compatible boards" ["name"]=> string(9) "SCC_DELAY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(172) " Say Y here if you experience problems with the SCC driver not working properly; please read for details. If unsure, say N. " } [1224]=> array(11) { ["entry_id"]=> string(4) "1225" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(49) "support for TRX that feedback the tx signal to rx" ["name"]=> string(11) "SCC_TRXECHO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(185) " Some transmitters feed the transmitted signal back to the receive line. Say Y here to foil this by explicitly disabling the receiver during data transmission. If in doubt, say Y. " } [1225]=> array(11) { ["entry_id"]=> string(4) "1226" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "BAYCOM ser12 fullduplex driver for AX.25" ["name"]=> string(14) "BAYCOM_SER_FDX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(948) " This is one of two drivers for Baycom style simple amateur radio modems that connect to a serial interface. The driver supports the ser12 design in full-duplex mode. In addition, it allows the baudrate to be set between 300 and 4800 baud (however not all modems support all baudrates). This is the preferred driver. The next driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old driver and still provided in case this driver does not work with your serial interface chip. To configure the driver, use the sethdlc utility available in the standard ax25 utilities package. For information on the modems, see and . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called baycom_ser_fdx. " } [1226]=> array(11) { ["entry_id"]=> string(4) "1227" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "BAYCOM ser12 halfduplex driver for AX.25" ["name"]=> string(14) "BAYCOM_SER_HDX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(786) " This is one of two drivers for Baycom style simple amateur radio modems that connect to a serial interface. The driver supports the ser12 design in full-duplex mode. This is the old driver. It is still provided in case your serial interface chip does not work with the full-duplex driver. This driver is depreciated. To configure the driver, use the sethdlc utility available in the standard ax25 utilities package. For information on the modems, see and . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called baycom_ser_hdx. " } [1227]=> array(11) { ["entry_id"]=> string(4) "1228" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(40) "BAYCOM picpar and par96 driver for AX.25" ["name"]=> string(10) "BAYCOM_PAR" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(622) " This is a driver for Baycom style simple amateur radio modems that connect to a parallel interface. The driver supports the picpar and par96 designs. To configure the driver, use the sethdlc utility available in the standard ax25 utilities package. For information on the modems, see and the file . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called baycom_par. " } [1228]=> array(11) { ["entry_id"]=> string(4) "1229" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "BAYCOM epp driver for AX.25" ["name"]=> string(10) "BAYCOM_EPP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(609) " This is a driver for Baycom style simple amateur radio modems that connect to a parallel interface. The driver supports the EPP designs. To configure the driver, use the sethdlc utility available in the standard ax25 utilities package. For information on the modems, see and the file . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . This is recommended. The module will be called baycom_par. " } [1229]=> array(11) { ["entry_id"]=> string(4) "1230" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(20) "YAM driver for AX.25" ["name"]=> string(3) "YAM" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(364) " The YAM is a modem for packet radio which connects to the serial port and includes some of the functions of a Terminal Node Controller. If you have one of those, say Y here. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . " } [1230]=> array(11) { ["entry_id"]=> string(4) "1231" ["entry_type"]=> string(4) "MENU" ["text"]=> string(14) "ISDN subsystem" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1231]=> array(11) { ["entry_id"]=> string(4) "1232" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(12) "ISDN support" ["name"]=> string(9) "ISDN_BOOL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(648) " ISDN ("Integrated Services Digital Networks", called RNIS in France) is a special type of fully digital telephone service; it's mostly used to connect to your Internet service provider (with SLIP or PPP). The main advantage is that the speed is higher than ordinary modem/telephone connections, and that you can have voice conversations while downloading stuff. It only works if your computer is equipped with an ISDN card and both you and your service provider purchased an ISDN line from the phone company. For details, read on the WWW. Select this option if you want your kernel to support ISDN. " } [1232]=> array(11) { ["entry_id"]=> string(4) "1233" ["entry_type"]=> string(4) "MENU" ["text"]=> string(14) "Old ISDN4Linux" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1233]=> array(11) { ["entry_id"]=> string(4) "1234" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Old ISDN4Linux (obsolete)" ["name"]=> string(4) "ISDN" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(740) " This driver allows you to use an ISDN-card for networking connections and as dialin/out device. The isdn-tty's have a built in AT-compatible modem emulator. Network devices support autodial, channel-bundling, callback and caller-authentication without having a daemon running. A reduced T.70 protocol is supported with tty's suitable for German BTX. On D-Channel, the protocols EDSS1 (Euro-ISDN) and 1TR6 (German style) are supported. See for more information. ISDN support in the linux kernel is moving towards a new API, called CAPI (Common ISDN Application Programming Interface). Therefore the old ISDN4Linux layer is becoming obsolete. It is still usable, though, if you select this option. " } [1234]=> array(11) { ["entry_id"]=> string(4) "1235" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) " Support raw-IP and other simple protocols" ["name"]=> string(15) "ISDN_NET_SIMPLE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(194) " This options enables 'raw IP over ISDN', 'ethernet over ISDN', 'raw IP with UI header' and 'IP + type field' encapsulations. If you never heard of any of those, you probably want to say N. " } [1235]=> array(11) { ["entry_id"]=> string(4) "1236" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) " Support CISCO router protocols" ["name"]=> string(14) "ISDN_NET_CISCO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(191) " This options enables 'CISCO HDLC' encapsulation with optional support for CISCO keep-alive frames. Unless you want to connect to a Cisco Router in HDLC mode, you probably want to say N. " } [1236]=> array(11) { ["entry_id"]=> string(4) "1237" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support synchronous PPP" ["name"]=> string(8) "ISDN_PPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(572) " Over digital connections such as ISDN, there is no need to synchronize sender and recipient's clocks with start and stop bits as is done over analog telephone lines. Instead, one can use "synchronous PPP". Saying Y here will include this protocol. This protocol is used by Cisco and Sun for example. So you want to say Y here if the other end of your ISDN connection supports it. You will need a special version of pppd (called ipppd) for using this feature. See and for more information. " } [1237]=> array(11) { ["entry_id"]=> string(4) "1238" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Use VJ-compression with synchronous PPP" ["name"]=> string(11) "ISDN_PPP_VJ" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(124) " This enables Van Jacobson header compression for synchronous PPP. Say Y if the other end of the connection supports it. " } [1238]=> array(11) { ["entry_id"]=> string(4) "1239" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Support generic MP (RFC 1717)" ["name"]=> string(8) "ISDN_MPP" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(198) " With synchronous PPP enabled, it is possible to increase throughput by bundling several ISDN-connections, using this protocol. See for more information. " } [1239]=> array(11) { ["entry_id"]=> string(4) "1240" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "Support BSD compression" ["name"]=> string(16) "ISDN_PPP_BSDCOMP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(363) " Support for the BSD-Compress compression method for PPP, which uses the LZW compression method to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the BSD-Compress compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. " } [1240]=> array(11) { ["entry_id"]=> string(4) "1241" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Support audio via ISDN" ["name"]=> string(10) "ISDN_AUDIO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(506) " If you say Y here, the modem-emulator will support a subset of the EIA Class 8 Voice commands. Using a getty with voice-support (mgetty+sendfax by gert@greenie.muc.de with an extension, available with the ISDN utility package for example), you will be able to use your Linux box as an ISDN-answering machine. Of course, this must be supported by the lowlevel driver also. Currently, the HiSax driver is the only voice-supporting driver. See for more information. " } [1241]=> array(11) { ["entry_id"]=> string(4) "1242" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(37) "Support AT-Fax Class 1 and 2 commands" ["name"]=> string(12) "ISDN_TTY_FAX" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(335) " If you say Y here, the modem-emulator will support a subset of the Fax Class 1 and 2 commands. Using a getty with fax-support (mgetty+sendfax, hylafax), you will be able to use your Linux box as an ISDN-fax-machine. This must be supported by the lowlevel driver also. See for more information. " } [1242]=> array(11) { ["entry_id"]=> string(4) "1243" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "X.25 PLP on top of ISDN" ["name"]=> string(8) "ISDN_X25" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(168) " This feature provides the X.25 protocol over ISDN connections. See for more information if you are thinking about using this. " } [1243]=> array(11) { ["entry_id"]=> string(4) "1244" ["entry_type"]=> string(4) "MENU" ["text"]=> string(23) "ISDN feature submodules" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1244]=> array(11) { ["entry_id"]=> string(4) "1245" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "isdnloop support" ["name"]=> string(13) "ISDN_DRV_LOOP" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(290) " This driver provides a virtual ISDN card. Its primary purpose is testing of linklevel features or configuration without getting charged by your service-provider for lots of phone calls. You need will need the loopctrl utility from the latest isdn4k-utils package to set up this driver. " } [1245]=> array(11) { ["entry_id"]=> string(4) "1246" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support isdn diversion services" ["name"]=> string(14) "ISDN_DIVERSION" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(609) " This option allows you to use some supplementary diversion services in conjunction with the HiSax driver on an EURO/DSS1 line. Supported options are CD (call deflection), CFU (Call forward unconditional), CFB (Call forward when busy) and CFNR (call forward not reachable). Additionally the actual CFU, CFB and CFNR state may be interrogated. The use of CFU, CFB, CFNR and interrogation may be limited to some countries. The keypad protocol is still not implemented. CD should work in all countries if the service has been subscribed to. Please read the file . " } [1246]=> array(11) { ["entry_id"]=> string(4) "1247" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "CAPI2.0 support" ["name"]=> string(9) "ISDN_CAPI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(241) " This provides the CAPI (Common ISDN Application Programming Interface, a standard making it easy for programs to access ISDN hardware, see . This is needed for AVM's set of active ISDN controllers like B1, T1, M1. " } [1247]=> array(11) { ["entry_id"]=> string(4) "1248" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(48) "Verbose reason code reporting (kernel size +=7K)" ["name"]=> string(29) "ISDN_DRV_AVMB1_VERBOSE_REASON" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(155) " If you say Y here, the AVM B1 driver will give verbose reasons for disconnecting. This will increase the size of the kernel by 7 KB. If unsure, say Y. " } [1248]=> array(11) { ["entry_id"]=> string(4) "1249" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(41) "CAPI2.0 Middleware support (EXPERIMENTAL)" ["name"]=> string(20) "ISDN_CAPI_MIDDLEWARE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(284) " This option will enhance the capabilities of the /dev/capi20 interface. It will provide a means of moving a data connection, established via the usual /dev/capi20 interface to a special tty device. If you want to use pppd with pppdcapiplugin to dial up to your ISP, say Y here. " } [1249]=> array(11) { ["entry_id"]=> string(4) "1250" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "CAPI2.0 /dev/capi support" ["name"]=> string(16) "ISDN_CAPI_CAPI20" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(202) " This option will provide the CAPI 2.0 interface to userspace applications via /dev/capi20. Applications should use the standardized libcapi20 to access this functionality. You should say Y/M here. " } [1250]=> array(11) { ["entry_id"]=> string(4) "1251" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(26) "CAPI2.0 filesystem support" ["name"]=> string(21) "ISDN_CAPI_CAPIFS_BOOL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "0" ["level"]=> string(2) "20" ["content"]=> NULL ["help_text"]=> NULL } [1251]=> array(11) { ["entry_id"]=> string(4) "1252" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "ISDN_CAPI_CAPIFS" ["name"]=> string(16) "ISDN_CAPI_CAPIFS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(5) "false" ["help"]=> string(1) "1" ["level"]=> string(2) "25" ["content"]=> NULL ["help_text"]=> string(240) " This option provides a special file system, similar to /dev/pts with device nodes for the special ttys established by using the middleware extension above. If you want to use pppd with pppdcapiplugin to dial up to your ISP, say Y here. " } [1252]=> array(11) { ["entry_id"]=> string(4) "1253" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(33) "CAPI2.0 capidrv interface support" ["name"]=> string(17) "ISDN_CAPI_CAPIDRV" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(252) " This option provides the glue code to hook up CAPI driven cards to the legacy isdn4linux link layer. If you have a card which is supported by a CAPI driver, but still want to use old features like ippp interfaces or ttyI emulation, say Y/M here. " } [1253]=> array(11) { ["entry_id"]=> string(4) "1254" ["entry_type"]=> string(4) "MENU" ["text"]=> string(16) "Active AVM cards" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1254]=> array(11) { ["entry_id"]=> string(4) "1255" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "Support AVM cards" ["name"]=> string(8) "CAPI_AVM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(46) " Enable support for AVM active ISDN cards. " } [1255]=> array(11) { ["entry_id"]=> string(4) "1256" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "AVM B1 ISA support" ["name"]=> string(20) "ISDN_DRV_AVMB1_B1ISA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(59) " Enable support for the ISA version of the AVM B1 card. " } [1256]=> array(11) { ["entry_id"]=> string(4) "1257" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "AVM B1 PCI support" ["name"]=> string(20) "ISDN_DRV_AVMB1_B1PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(59) " Enable support for the PCI version of the AVM B1 card. " } [1257]=> array(11) { ["entry_id"]=> string(4) "1258" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "AVM B1 PCI V4 support" ["name"]=> string(22) "ISDN_DRV_AVMB1_B1PCIV4" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(58) " Enable support for the V4 version of AVM B1 PCI card. " } [1258]=> array(11) { ["entry_id"]=> string(4) "1259" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "AVM T1/T1-B ISA support" ["name"]=> string(20) "ISDN_DRV_AVMB1_T1ISA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(95) " Enable support for the AVM T1 T1B card. Note: This is a PRI card and handle 30 B-channels. " } [1259]=> array(11) { ["entry_id"]=> string(4) "1260" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "AVM B1/M1/M2 PCMCIA support" ["name"]=> string(23) "ISDN_DRV_AVMB1_B1PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(62) " Enable support for the PCMCIA version of the AVM B1 card. " } [1260]=> array(11) { ["entry_id"]=> string(4) "1261" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "AVM B1/M1/M2 PCMCIA cs module" ["name"]=> string(21) "ISDN_DRV_AVMB1_AVM_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(71) " Enable the PCMCIA client driver for the AVM B1/M1/M2 PCMCIA cards. " } [1261]=> array(11) { ["entry_id"]=> string(4) "1262" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(23) "AVM T1/T1-B PCI support" ["name"]=> string(20) "ISDN_DRV_AVMB1_T1PCI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(95) " Enable support for the AVM T1 T1B card. Note: This is a PRI card and handle 30 B-channels. " } [1262]=> array(11) { ["entry_id"]=> string(4) "1263" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "AVM C4/C2 support" ["name"]=> string(17) "ISDN_DRV_AVMB1_C4" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(102) " Enable support for the AVM C4/C2 PCI cards. These cards handle 4/2 BRI ISDN lines (8/4 channels). " } [1263]=> array(11) { ["entry_id"]=> string(4) "1264" ["entry_type"]=> string(4) "MENU" ["text"]=> string(30) "Active Eicon DIVA Server cards" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1264]=> array(11) { ["entry_id"]=> string(4) "1265" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Support Eicon cards" ["name"]=> string(10) "CAPI_EICON" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(57) " Enable support for Eicon Networks active ISDN cards. " } [1265]=> array(11) { ["entry_id"]=> string(4) "1266" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "Support Eicon DIVA Server cards" ["name"]=> string(10) "ISDN_DIVAS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(202) " Say Y here if you have an Eicon Networks DIVA Server PCI ISDN card. In order to use this card, additional firmware is necessary, which has to be downloaded into the card using the divactrl utility. " } [1266]=> array(11) { ["entry_id"]=> string(4) "1267" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "DIVA Server BRI/PCI support" ["name"]=> string(17) "ISDN_DIVAS_BRIPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(44) " Enable support for DIVA Server BRI-PCI. " } [1267]=> array(11) { ["entry_id"]=> string(4) "1268" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(28) "DIVA Server 4BRI/PCI support" ["name"]=> string(18) "ISDN_DIVAS_4BRIPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(45) " Enable support for DIVA Server 4BRI-PCI. " } [1268]=> array(11) { ["entry_id"]=> string(4) "1269" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "DIVA Server PRI/PCI support" ["name"]=> string(17) "ISDN_DIVAS_PRIPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(44) " Enable support for DIVA Server PRI-PCI. " } [1269]=> array(11) { ["entry_id"]=> string(4) "1270" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "DIVA CAPI2.0 interface support" ["name"]=> string(19) "ISDN_DIVAS_DIVACAPI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(71) " You need this to provide the CAPI interface for DIVA Server cards. " } [1270]=> array(11) { ["entry_id"]=> string(4) "1271" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "DIVA Maint driver support" ["name"]=> string(16) "ISDN_DIVAS_MAINT" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(38) " Enable Divas Maintainance driver. " } [1271]=> array(11) { ["entry_id"]=> string(4) "1272" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(31) "DIVA User-IDI interface support" ["name"]=> string(18) "ISDN_DIVAS_USERIDI" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(48) " Enable support for user-mode IDI interface. " } [1272]=> array(11) { ["entry_id"]=> string(4) "1273" ["entry_type"]=> string(4) "MENU" ["text"]=> string(13) "Passive cards" ["name"]=> NULL ["value"]=> NULL ["type"]=> NULL ["prompt"]=> NULL ["help"]=> NULL ["level"]=> string(1) "0" ["content"]=> NULL ["help_text"]=> NULL } [1273]=> array(11) { ["entry_id"]=> string(4) "1274" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(35) "HiSax SiemensChipSet driver support" ["name"]=> string(14) "ISDN_DRV_HISAX" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(1) "5" ["content"]=> NULL ["help_text"]=> string(420) " This is a driver supporting the Siemens chipset on various ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many compatibles). HiSax is just the name of this driver, not the name of any hardware. If you have a card with such a chipset, you should say Y here and also to the configuration option of the driver for your particular card, below. " } [1274]=> array(11) { ["entry_id"]=> string(4) "1275" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "HiSax Support for EURO/DSS1" ["name"]=> string(10) "HISAX_EURO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(192) " Say Y or N according to the D-channel protocol which your local telephone service company provides. The call control protocol E-DSS1 is used in most European countries. If unsure, say Y. " } [1275]=> array(11) { ["entry_id"]=> string(4) "1276" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "Support for german chargeinfo" ["name"]=> string(6) "DE_AOC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(359) " If you want that the HiSax hardware driver sends messages to the upper level of the isdn code on each AOCD (Advice Of Charge, During the call -- transmission of the fee information during a call) and on each AOCE (Advice Of Charge, at the End of the call -- transmission of fee information at the end of the call), say Y here. This works only in Germany. " } [1276]=> array(11) { ["entry_id"]=> string(4) "1277" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "Disable sending complete" ["name"]=> string(21) "HISAX_NO_SENDCOMPLETE" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(94) " If you have trouble with some ugly exchanges or you live in Australia select this option. " } [1277]=> array(11) { ["entry_id"]=> string(4) "1278" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(39) "Disable sending low layer compatibility" ["name"]=> string(12) "HISAX_NO_LLC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(76) " If you have trouble with some ugly exchanges try to select this option. " } [1278]=> array(11) { ["entry_id"]=> string(4) "1279" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(30) "Disable keypad protocol option" ["name"]=> string(15) "HISAX_NO_KEYPAD" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "15" ["content"]=> NULL ["help_text"]=> string(117) " If you like to send special dial strings including * or # without using the keypad protocol, select this option. " } [1279]=> array(11) { ["entry_id"]=> string(4) "1280" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(29) "HiSax Support for german 1TR6" ["name"]=> string(10) "HISAX_1TR6" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(246) " Say Y or N according to the D-channel protocol which your local telephone service company provides. 1TR6 is an old call control protocol which was used in Germany before E-DSS1 was established. Nowadays, all new lines in Germany use E-DSS1. " } [1280]=> array(11) { ["entry_id"]=> string(4) "1281" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "HiSax Support for US NI1" ["name"]=> string(9) "HISAX_NI1" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(77) " Enable this if you like to use ISDN in US on a NI1 basic rate interface. " } [1281]=> array(11) { ["entry_id"]=> string(4) "1282" ["entry_type"]=> string(6) "STRING" ["text"]=> NULL ["name"]=> string(15) "HISAX_MAX_CARDS" ["value"]=> string(0) "" ["type"]=> string(6) "string" ["prompt"]=> NULL ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> string(42) "Maximum number of cards supported by HiSax" ["help_text"]=> NULL } [1282]=> array(11) { ["entry_id"]=> string(4) "1283" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "Teles 16.0/8.0" ["name"]=> string(10) "HISAX_16_0" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(259) " This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8 and many compatibles. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port/shmem settings. " } [1283]=> array(11) { ["entry_id"]=> string(4) "1284" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "Teles 16.3 or PNP or PCMCIA" ["name"]=> string(10) "HISAX_16_3" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(269) " This enables HiSax support for the Teles ISDN-cards S0-16.3 the Teles/Creatix PnP and the Teles PCMCIA. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1284]=> array(11) { ["entry_id"]=> string(4) "1285" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(9) "Teles PCI" ["name"]=> string(14) "HISAX_TELESPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(117) " This enables HiSax support for the Teles PCI. See on how to configure it. " } [1285]=> array(11) { ["entry_id"]=> string(4) "1286" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "Teles S0Box" ["name"]=> string(11) "HISAX_S0BOX" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(142) " This enables HiSax support for the Teles/Creatix parallel port S0BOX. See on how to configure it. " } [1286]=> array(11) { ["entry_id"]=> string(4) "1287" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(14) "AVM A1 (Fritz)" ["name"]=> string(12) "HISAX_AVM_A1" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(222) " This enables HiSax support for the AVM A1 (aka "Fritz"). See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1287]=> array(11) { ["entry_id"]=> string(4) "1288" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "AVM PnP/PCI (Fritz!PnP/PCI)" ["name"]=> string(14) "HISAX_FRITZPCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(139) " This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI". See on how to configure it. " } [1288]=> array(11) { ["entry_id"]=> string(4) "1289" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "AVM A1 PCMCIA (Fritz)" ["name"]=> string(19) "HISAX_AVM_A1_PCMCIA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(130) " This enables HiSax support for the AVM A1 "Fritz!PCMCIA"). See on how to configure it. " } [1289]=> array(11) { ["entry_id"]=> string(4) "1290" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(10) "Elsa cards" ["name"]=> string(10) "HISAX_ELSA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(279) " This enables HiSax support for the Elsa Mircolink ISA cards, for the Elsa Quickstep series cards and Elsa PCMCIA. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1290]=> array(11) { ["entry_id"]=> string(4) "1291" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(24) "ITK ix1-micro Revision 2" ["name"]=> string(16) "HISAX_IX1MICROR2" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(231) " This enables HiSax support for the ITK ix1-micro Revision 2 card. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1291]=> array(11) { ["entry_id"]=> string(4) "1292" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Eicon.Diehl Diva cards" ["name"]=> string(15) "HISAX_DIEHLDIVA" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(255) " This enables HiSax support for the Eicon.Diehl Diva none PRO versions passive ISDN cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1292]=> array(11) { ["entry_id"]=> string(4) "1293" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "ASUSCOM ISA cards" ["name"]=> string(13) "HISAX_ASUSCOM" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(255) " This enables HiSax support for the AsusCom and their OEM versions passive ISDN ISA cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1293]=> array(11) { ["entry_id"]=> string(4) "1294" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(13) "TELEINT cards" ["name"]=> string(13) "HISAX_TELEINT" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(233) " This enables HiSax support for the TELEINT SA1 semiactiv ISDN card. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1294]=> array(11) { ["entry_id"]=> string(4) "1295" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "HFC-S based cards" ["name"]=> string(10) "HISAX_HFCS" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(243) " This enables HiSax support for the HFC-S 2BDS0 based cards, like teles 16.3c. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1295]=> array(11) { ["entry_id"]=> string(4) "1296" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "Sedlbauer cards" ["name"]=> string(15) "HISAX_SEDLBAUER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(230) " This enables HiSax support for the Sedlbauer passive ISDN cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. " } [1296]=> array(11) { ["entry_id"]=> string(4) "1297" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "USR Sportster internal TA" ["name"]=> string(15) "HISAX_SPORTSTER" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(211) " This enables HiSax support for the USR Sportster internal TA card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1297]=> array(11) { ["entry_id"]=> string(4) "1298" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(8) "MIC card" ["name"]=> string(9) "HISAX_MIC" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(193) " This enables HiSax support for the ITH MIC card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1298]=> array(11) { ["entry_id"]=> string(4) "1299" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "NETjet card" ["name"]=> string(12) "HISAX_NETJET" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(214) " This enables HiSax support for the NetJet from Traverse Technologies. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1299]=> array(11) { ["entry_id"]=> string(4) "1300" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "NETspider U card" ["name"]=> string(14) "HISAX_NETJET_U" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(238) " This enables HiSax support for the Netspider U interface ISDN card from Traverse Technologies. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1300]=> array(11) { ["entry_id"]=> string(4) "1301" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Niccy PnP/PCI card" ["name"]=> string(11) "HISAX_NICCY" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(209) " This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1301]=> array(11) { ["entry_id"]=> string(4) "1302" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "Siemens I-Surf card" ["name"]=> string(11) "HISAX_ISURF" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(221) " This enables HiSax support for the Siemens I-Talk/I-Surf card with ISAR chip. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1302]=> array(11) { ["entry_id"]=> string(4) "1303" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "HST Saphir card" ["name"]=> string(15) "HISAX_HSTSAPHIR" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(196) " This enables HiSax support for the HST Saphir card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1303]=> array(11) { ["entry_id"]=> string(4) "1304" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(16) "Telekom A4T card" ["name"]=> string(13) "HISAX_BKM_A4T" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(197) " This enables HiSax support for the Telekom A4T card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1304]=> array(11) { ["entry_id"]=> string(4) "1305" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(18) "Scitel Quadro card" ["name"]=> string(16) "HISAX_SCT_QUADRO" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(199) " This enables HiSax support for the Scitel Quadro card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1305]=> array(11) { ["entry_id"]=> string(4) "1306" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(11) "Gazel cards" ["name"]=> string(11) "HISAX_GAZEL" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(192) " This enables HiSax support for the Gazel cards. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1306]=> array(11) { ["entry_id"]=> string(4) "1307" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(17) "HFC PCI-Bus cards" ["name"]=> string(13) "HISAX_HFC_PCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(143) " This enables HiSax support for the HFC-S PCI 2BDS0 based cards. For more informations see under . " } [1307]=> array(11) { ["entry_id"]=> string(4) "1308" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(25) "Winbond W6692 based cards" ["name"]=> string(11) "HISAX_W6692" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(211) " This enables HiSax support for Winbond W6692 based PCI ISDN cards. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. " } [1308]=> array(11) { ["entry_id"]=> string(4) "1309" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(32) "HFC-S+, HFC-SP, HFC-PCMCIA cards" ["name"]=> string(12) "HISAX_HFC_SX" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(107) " This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA cards. This code is not finished yet. " } [1309]=> array(11) { ["entry_id"]=> string(4) "1310" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(43) "Formula-n enter:now PCI card (EXPERIMENTAL)" ["name"]=> string(18) "HISAX_ENTERNOW_PCI" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(74) " This enables HiSax support for the Formula-n enter:now PCI ISDN card. " } [1310]=> array(11) { ["entry_id"]=> string(4) "1311" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(21) "Am7930 (EXPERIMENTAL)" ["name"]=> string(13) "HISAX_AMD7930" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(100) " This enables HiSax support for the AMD7930 chips on some SPARCs. This code is not finished yet. " } [1311]=> array(11) { ["entry_id"]=> string(4) "1312" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(15) "HiSax debugging" ["name"]=> string(11) "HISAX_DEBUG" ["value"]=> string(1) "n" ["type"]=> string(4) "bool" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(125) " This enables debugging code in the new-style HiSax drivers, i.e. the ST5481 USB driver currently. If in doubt, say yes. " } [1312]=> array(11) { ["entry_id"]=> string(4) "1313" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(22) "Sedlbauer PCMCIA cards" ["name"]=> string(18) "HISAX_SEDLBAUER_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(96) " This enables the PCMCIA client driver for the Sedlbauer Speed Star and Speed Star II cards. " } [1313]=> array(11) { ["entry_id"]=> string(4) "1314" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(27) "ELSA PCMCIA MicroLink cards" ["name"]=> string(13) "HISAX_ELSA_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(78) " This enables the PCMCIA client driver for the Elsa PCMCIA MicroLink card. " } [1314]=> array(11) { ["entry_id"]=> string(4) "1315" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(19) "AVM A1 PCMCIA cards" ["name"]=> string(15) "HISAX_AVM_A1_CS" ["value"]=> string(1) "n" ["type"]=> string(8) "tristate" ["prompt"]=> string(4) "true" ["help"]=> string(1) "1" ["level"]=> string(2) "10" ["content"]=> NULL ["help_text"]=> string(84) " This enables the PCMCIA client driver for the AVM A1 / Fritz!Card PCMCIA cards. " } [1315]=> array(11) { ["entry_id"]=> string(4) "1316" ["entry_type"]=> string(6) "SYMBOL" ["text"]=> string(36) "ST5481 USB ISDN modem (EXPERIMENTAL)" ["name"]=>