diff options
| author | Linus Torvalds <torvalds@home.transmeta.com> | 2002-10-29 05:09:28 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@penguin.transmeta.com> | 2002-10-29 05:09:28 -0800 |
| commit | 0e01a0dd1f8209c0a64cbbbf99eab467e7401df5 (patch) | |
| tree | 2d22a73ea158bb9fbc21bc1c5c4df9c2cdad9883 /drivers | |
| parent | 82fe246fb7291daaf2f71fdb8b61a07ce5e3678b (diff) | |
Delete old-style config files.
Diffstat (limited to 'drivers')
183 files changed, 0 insertions, 18495 deletions
diff --git a/drivers/acorn/block/Config.help b/drivers/acorn/block/Config.help deleted file mode 100644 index f6ee4eaa79fd..000000000000 --- a/drivers/acorn/block/Config.help +++ /dev/null @@ -1,18 +0,0 @@ -CONFIG_BLK_DEV_MFM - Support the MFM hard drives on the Acorn Archimedes both - on-board the A4x0 motherboards and via the Acorn MFM podules. - Drives up to 64MB are supported. If you haven't got one of these - machines or drives just say N. - -CONFIG_BLK_DEV_FD1772 - Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540, - R140 and R260) series of computers; it supports only 720K floppies - at the moment. If you don't have one of these machines just answer - N. - -CONFIG_BLK_DEV_MFM_AUTODETECT - If you answer Y, the MFM code will attempt to automatically detect - the cylinders/heads/sectors count on your hard drive. WARNING: This - sometimes doesn't work and it also does some dodgy stuff which - potentially might damage your drive. - diff --git a/drivers/acorn/block/Config.in b/drivers/acorn/block/Config.in deleted file mode 100644 index be2d2432ff20..000000000000 --- a/drivers/acorn/block/Config.in +++ /dev/null @@ -1,15 +0,0 @@ -# -# Block device driver configuration -# -mainmenu_option next_comment -comment 'Acorn-specific block devices' - -if [ "$CONFIG_ARCH_ARC" = "y" -o "$CONFIG_ARCH_A5K" = "y" ]; then - tristate 'Old Archimedes floppy (1772) support' CONFIG_BLK_DEV_FD1772 - tristate 'MFM harddisk support' CONFIG_BLK_DEV_MFM - if [ "$CONFIG_BLK_DEV_MFM" != "n" ]; then - bool ' Autodetect hard drive geometry' CONFIG_BLK_DEV_MFM_AUTODETECT - fi -fi - -endmenu diff --git a/drivers/acorn/net/Config.help b/drivers/acorn/net/Config.help deleted file mode 100644 index 88a39b0646aa..000000000000 --- a/drivers/acorn/net/Config.help +++ /dev/null @@ -1,12 +0,0 @@ -CONFIG_ARM_ETHER1 - 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. - -CONFIG_ARM_ETHER3 - 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. - -CONFIG_ARM_ETHERH - 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. - diff --git a/drivers/acorn/net/Config.in b/drivers/acorn/net/Config.in deleted file mode 100644 index 7331be5f0891..000000000000 --- a/drivers/acorn/net/Config.in +++ /dev/null @@ -1,7 +0,0 @@ -# -# Acorn Network device configuration -# These are for Acorn's Expansion card network interfaces -# -tristate ' Acorn Ether1 support' CONFIG_ARM_ETHER1 -tristate ' Acorn/ANT Ether3 support' CONFIG_ARM_ETHER3 -tristate ' I-cubed EtherH/ANT EtherM support' CONFIG_ARM_ETHERH diff --git a/drivers/acorn/scsi/Config.help b/drivers/acorn/scsi/Config.help deleted file mode 100644 index 08b10577bb6b..000000000000 --- a/drivers/acorn/scsi/Config.help +++ /dev/null @@ -1,53 +0,0 @@ -CONFIG_SCSI_ACORNSCSI_3 - 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. - -CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE - 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. - -CONFIG_SCSI_ACORNSCSI_SYNC - 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. - -CONFIG_SCSI_ARXESCSI - 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 - <http://www.cryton.demon.co.uk/acornbits/scsi_arxe.html> - Say Y here to compile in support for the SCSI controller. - -CONFIG_SCSI_OAK1 - This enables support for the Oak SCSI card. If you have an Acorn - system with one of these, say Y. If unsure, say N. - -CONFIG_SCSI_CUMANA_1 - 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. - -CONFIG_SCSI_CUMANA_2 - 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. - -CONFIG_SCSI_ECOSCSI - 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. - -CONFIG_SCSI_EESOXSCSI - This enables support for the EESOX SCSI card. If you have an Acorn - system with one of these, say Y, otherwise say N. - -CONFIG_SCSI_POWERTECSCSI - This enables support for the Powertec SCSI card on Acorn systems. If - you have one of these, say Y. If unsure, say N. - diff --git a/drivers/acorn/scsi/Config.in b/drivers/acorn/scsi/Config.in deleted file mode 100644 index 93ce7d3e4348..000000000000 --- a/drivers/acorn/scsi/Config.in +++ /dev/null @@ -1,23 +0,0 @@ -# -# SCSI driver configuration for Acorn -# -dep_tristate 'Acorn SCSI card (aka30) support' CONFIG_SCSI_ACORNSCSI_3 $CONFIG_SCSI -if [ "$CONFIG_SCSI_ACORNSCSI_3" != "n" ]; then - bool ' Support SCSI 2 Tagged queueing' CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE - bool ' Support SCSI 2 Synchronous Transfers' CONFIG_SCSI_ACORNSCSI_SYNC -fi -dep_tristate 'ARXE SCSI support' CONFIG_SCSI_ARXESCSI $CONFIG_SCSI -dep_tristate 'CumanaSCSI II support' CONFIG_SCSI_CUMANA_2 $CONFIG_SCSI -dep_tristate 'EESOX support' CONFIG_SCSI_EESOXSCSI $CONFIG_SCSI -dep_tristate 'PowerTec support' CONFIG_SCSI_POWERTECSCSI $CONFIG_SCSI - -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - comment 'The following drivers are not fully supported' - - dep_tristate 'CumanaSCSI I support (EXPERIMENTAL)' CONFIG_SCSI_CUMANA_1 $CONFIG_SCSI - if [ "$CONFIG_ARCH_ARC" = "y" -o "$CONFIG_ARCH_A5K" = "y" ]; then - dep_tristate 'EcoScsi support (EXPERIMENTAL)' CONFIG_SCSI_ECOSCSI $CONFIG_SCSI - fi - dep_tristate 'Oak SCSI support (EXPERIMENTAL)' CONFIG_SCSI_OAK1 $CONFIG_SCSI -fi - diff --git a/drivers/acpi/Config.help b/drivers/acpi/Config.help deleted file mode 100644 index ccb2e4aee766..000000000000 --- a/drivers/acpi/Config.help +++ /dev/null @@ -1,137 +0,0 @@ -CONFIG_ACPI - 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. - - Add "acpi=off" to the kernel command line to disable this feature. - (Try "man bootparam" or see the documentation of your boot loader - about how to pass options to the kernel at boot time.) - - ---------- - - The ACPI SourceForge project contains the latest source code, - documentation, tools, mailing list subscription, and other - information. This project is available at: - <http://sourceforge.net/projects/acpi> - - Linux support for ACPI is based on Intel Corporation's ACPI - Component Architecture (ACPI CA). For more information see: - <http://developer.intel.com/technology/iapc/acpi> - - ACPI is an open industry specification co-developed by Compaq, - Intel, Microsoft, Phoenix, and Toshiba. The specification is - available at: - <http://www.acpi.info> - -CONFIG_ACPI_HT_ONLY - 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. - - There is no command-line option to disable this, but the kernel - will fall back to the MPS table if the MADT is not present. - -CONFIG_ACPI_AC - 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. - -CONFIG_ACPI_BATTERY - This driver adds support for battery information through - /proc/acpi/battery. If you have a mobile system with a battery, - say Y. - -CONFIG_ACPI_BUTTON - 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. - -CONFIG_ACPI_EC - 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. - -CONFIG_ACPI_PROCESSOR - 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. - -CONFIG_ACPI_PROCESSOR_PERF - This driver adds support for CPU frequency scaling, if this is supported - by the hardware and the BIOS. If you are compiling for a mobile system, - say Y. - -CONFIG_ACPI_THERMAL - 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. - -CONFIG_ACPI_FAN - This driver adds support for ACPI fan devices, allowing user-mode - applications to perform basic fan control (on, off, status). - -CONFIG_ACPI_SYSTEM - This driver will enable your system to shut down using ACPI, and - dump your ACPI DSDT table using /proc/acpi/dsdt. - -CONFIG_ACPI_SLEEP - 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. - - -CONFIG_ACPI_DEBUG - 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. - -CONFIG_ACPI_TOSHIBA - 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 - <http://memebeam.org/toys/ToshibaAcpiDriver>. - - If you have a legacy free Toshiba laptop (such as the Libretto L1 - series), say Y. diff --git a/drivers/acpi/Config.in b/drivers/acpi/Config.in deleted file mode 100644 index 3f9635cb0f45..000000000000 --- a/drivers/acpi/Config.in +++ /dev/null @@ -1,84 +0,0 @@ -# -# ACPI Configuration -# - -mainmenu_option next_comment -comment 'ACPI Support' - -if [ "$CONFIG_X86" = "y" ]; then - bool 'ACPI Support' CONFIG_ACPI - if [ "$CONFIG_ACPI" = "y" ]; then - if [ "$CONFIG_X86_LOCAL_APIC" = "y" ]; then - bool 'CPU Enumeration Only' CONFIG_ACPI_HT_ONLY - fi - - define_bool CONFIG_ACPI_BOOT y - - if [ "$CONFIG_ACPI_HT_ONLY" != "y" ]; then - bool ' Sleep States' CONFIG_ACPI_SLEEP - tristate ' AC Adapter' CONFIG_ACPI_AC - tristate ' Battery' CONFIG_ACPI_BATTERY - tristate ' Button' CONFIG_ACPI_BUTTON - tristate ' Fan' CONFIG_ACPI_FAN - tristate ' Processor' CONFIG_ACPI_PROCESSOR - if [ "$CONFIG_ACPI_PROCESSOR" != "n" ]; then - dep_bool ' Processor Performance States' CONFIG_ACPI_PROCESSOR_PERF $CONFIG_CPU_FREQ - fi - dep_tristate ' Thermal Zone' CONFIG_ACPI_THERMAL $CONFIG_ACPI_PROCESSOR - if [ "$CONFIG_NUMA" = "y" ]; then - dep_bool ' NUMA support' CONFIG_ACPI_NUMA $CONFIG_NUMA - fi - tristate ' Toshiba Laptop Extras' CONFIG_ACPI_TOSHIBA - bool ' Debug Statements' CONFIG_ACPI_DEBUG - - define_bool CONFIG_ACPI_BOOT y - define_bool CONFIG_ACPI_BUS y - define_bool CONFIG_ACPI_INTERPRETER y - define_bool CONFIG_ACPI_EC y - define_bool CONFIG_ACPI_POWER y - define_bool CONFIG_ACPI_PCI $CONFIG_PCI - define_bool CONFIG_ACPI_SLEEP $CONFIG_SOFTWARE_SUSPEND - define_bool CONFIG_ACPI_SYSTEM y - fi - fi -fi - -if [ "$CONFIG_IA64" = "y" ]; then - if [ "$CONFIG_IA64_SGI_SN" = "y" ]; then - define_bool CONFIG_ACPI y - define_bool CONFIG_ACPI_EFI y - define_bool CONFIG_ACPI_BOOT y - define_bool CONFIG_ACPI_BUS n - define_bool CONFIG_ACPI_INTERPRETER n - define_bool CONFIG_ACPI_PCI n - define_bool CONFIG_ACPI_POWER n - define_bool CONFIG_ACPI_SYSTEM n - define_bool CONFIG_ACPI_SLEEP n - define_bool CONFIG_ACPI_BUTTON n - define_bool CONFIG_ACPI_FAN n - define_bool CONFIG_ACPI_PROCESSOR n - define_bool CONFIG_ACPI_THERMAL n - define_bool CONFIG_ACPI_NUMA y - fi - - if [ "$CONFIG_IA64_HP_SIM" = "n" ]; then - tristate ' Button' CONFIG_ACPI_BUTTON - tristate ' Fan' CONFIG_ACPI_FAN - tristate ' Processor' CONFIG_ACPI_PROCESSOR - dep_tristate ' Thermal Zone' CONFIG_ACPI_THERMAL $CONFIG_ACPI_PROCESSOR - if [ "$CONFIG_NUMA" = "y" ]; then - dep_bool ' NUMA support' CONFIG_ACPI_NUMA $CONFIG_NUMA - fi - bool ' Debug Statements' CONFIG_ACPI_DEBUG - define_bool CONFIG_ACPI_PCI $CONFIG_PCI - define_bool CONFIG_ACPI y - define_bool CONFIG_ACPI_EFI y - define_bool CONFIG_ACPI_BOOT y - define_bool CONFIG_ACPI_BUS y - define_bool CONFIG_ACPI_INTERPRETER y - define_bool CONFIG_ACPI_POWER y - define_bool CONFIG_ACPI_SYSTEM y - fi -fi - -endmenu diff --git a/drivers/atm/Config.help b/drivers/atm/Config.help deleted file mode 100644 index 88bd7d435ecd..000000000000 --- a/drivers/atm/Config.help +++ /dev/null @@ -1,296 +0,0 @@ -CONFIG_ATM_TCP - ATM over TCP driver. Useful mainly for development and for - experiments. If unsure, say N. - -CONFIG_ATM_ENI - 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 - <file:Documentation/modules.txt>. The module will be called eni.o. - -CONFIG_ATM_ENI_DEBUG - 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. - -CONFIG_ATM_ENI_TUNE_BURST - 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. - -CONFIG_ATM_ENI_BURST_TX_16W - Burst sixteen words at once in the send direction. This may work - with recent PCI chipsets, but is known to fail with older chipsets. - -CONFIG_ATM_ENI_BURST_TX_8W - Burst eight words at once in the send direction. This is the default - setting. - -CONFIG_ATM_ENI_BURST_TX_4W - 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. - -CONFIG_ATM_ENI_BURST_TX_2W - 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. - -CONFIG_ATM_ENI_BURST_RX_16W - Burst sixteen words at once in the receive direction. This may work - with recent PCI chipsets, but is known to fail with older chipsets. - -CONFIG_ATM_ENI_BURST_RX_8W - 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. - -CONFIG_ATM_ENI_BURST_RX_4W - 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. - -CONFIG_ATM_ENI_BURST_RX_2W - 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. - -CONFIG_ATM_ZATM - 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 - <file:Documentation/modules.txt>. The module will be called zatm.o. - -CONFIG_ATM_ZATM_DEBUG - 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. - -CONFIG_ATM_FIRESTREAM - 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 - <file:Documentation/modules.txt>. The module will be called - firestream.o. - -CONFIG_ATM_ZATM_EXACT_TS - 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. - -CONFIG_ATM_NICSTAR - 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 - <file:Documentation/modules.txt>. The module will be called - nicstar.o. - -CONFIG_ATM_NICSTAR_USE_SUNI - 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). - -CONFIG_ATM_NICSTAR_USE_IDT77105 - 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. - -CONFIG_ATM_IDT77252 - 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 - <file:Documentation/modules.txt>. The module will be called idt77252.o - -CONFIG_ATM_IDT77252_DEBUG - 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 <file:drivers/atm/idt77252.h> 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. - -CONFIG_ATM_IDT77252_RCV_ALL - 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. - -CONFIG_ATM_AMBASSADOR - 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.o) - here if you have one of these cards. - -CONFIG_ATM_AMBASSADOR_DEBUG - 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 - <file:drivers/atm/ambassador.h> 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. - -CONFIG_ATM_HORIZON - 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.o) here if you have one of these cards. - -CONFIG_ATM_HORIZON_DEBUG - 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 - <file:drivers/atm/horizon.h> 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. - -CONFIG_ATM_IA - 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: - <http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM> - for more info about the cards. Say Y (or M to compile as a module - named iphase.o) here if you have one of these cards. - - See the file <file:Documentation/networking/iphase.txt> for further - details. - -CONFIG_ATM_IA_DEBUG - 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 - <ftp://ftp.iphase.com/pub/atm/pci/>). - - See the file <file:drivers/atm/iphase.h> 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. - -CONFIG_ATM_FORE200E_MAYBE - 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.o) 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 <file:Documentation/networking/fore200e.txt> for - further details. - -CONFIG_ATM_FORE200E_PCA - Say Y here if you want your PCA-200E cards to be probed. - -CONFIG_ATM_FORE200E_PCA_DEFAULT_FW - 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. - -CONFIG_ATM_FORE200E_PCA_FW - This defines the pathname of an alternative PCA-200E binary - firmware image supplied by the user. This pathname may be - absolute or relative to the drivers/atm directory. - - The driver comes with an adequate firmware image, so normal users do - not have to supply an alternative one. They just say Y to "Use - default PCA-200E firmware" instead. - -CONFIG_ATM_FORE200E_SBA - Say Y here if you want your SBA-200E cards to be probed. - -CONFIG_ATM_FORE200E_SBA_DEFAULT_FW - 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. - -CONFIG_ATM_FORE200E_SBA_FW - This defines the pathname of an alternative SBA-200E binary - firmware image supplied by the user. This pathname may be - absolute or relative to the drivers/atm directory. - - The driver comes with an adequate firmware image, so normal users do - not have to supply an alternative one. They just say Y to "Use - default SBA-200E firmware", above. - -CONFIG_ATM_FORE200E_TX_RETRY - Specifies the number of times the driver attempts to transmit - a message before giving up, if the transmit queue of the ATM card - is transiently saturated. - - Saturation of the transmit queue may occur only under extreme - conditions, e.g. when a fast host continuously submits very small - frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter. - - Note that under common conditions, it is unlikely that you encounter - a saturation of the transmit queue, so the retry mechanism never - comes into play. - -CONFIG_ATM_FORE200E_DEBUG - Specifies the level of debugging messages issued by the driver. - The verbosity of the driver increases with the value of this - parameter. - - When active, these messages can have a significant impact on - the performances of the driver, and the size of your syslog files! - Keep the debugging level to 0 during normal operations. - diff --git a/drivers/atm/Config.in b/drivers/atm/Config.in deleted file mode 100644 index ae3d20e00b8d..000000000000 --- a/drivers/atm/Config.in +++ /dev/null @@ -1,95 +0,0 @@ -# -# ATM device configuration -# -mainmenu_option next_comment -comment 'ATM drivers' -if [ "$CONFIG_INET" = "y" ]; then - tristate 'ATM over TCP' CONFIG_ATM_TCP -fi -if [ "$CONFIG_PCI" = "y" ]; then - tristate 'Efficient Networks Speedstream 3010' CONFIG_ATM_LANAI - tristate 'Efficient Networks ENI155P' CONFIG_ATM_ENI - if [ "$CONFIG_ATM_ENI" != "n" ]; then - bool ' Enable extended debugging' CONFIG_ATM_ENI_DEBUG - bool ' Fine-tune burst settings' CONFIG_ATM_ENI_TUNE_BURST - if [ "$CONFIG_ATM_ENI_TUNE_BURST" = "y" ]; then - bool ' Enable 16W TX bursts (discouraged)' CONFIG_ATM_ENI_BURST_TX_16W - bool ' Enable 8W TX bursts (recommended)' CONFIG_ATM_ENI_BURST_TX_8W - bool ' Enable 4W TX bursts (optional)' CONFIG_ATM_ENI_BURST_TX_4W - bool ' Enable 2W TX bursts (optional)' CONFIG_ATM_ENI_BURST_TX_2W - bool ' Enable 16W RX bursts (discouraged)' CONFIG_ATM_ENI_BURST_RX_16W - bool ' Enable 8W RX bursts (discouraged)' CONFIG_ATM_ENI_BURST_RX_8W - bool ' Enable 4W RX bursts (recommended)' CONFIG_ATM_ENI_BURST_RX_4W - bool ' Enable 2W RX bursts (optional)' CONFIG_ATM_ENI_BURST_RX_2W - fi - fi - tristate 'Fujitsu FireStream (FS50/FS155) ' CONFIG_ATM_FIRESTREAM - tristate 'ZeitNet ZN1221/ZN1225' CONFIG_ATM_ZATM - if [ "$CONFIG_ATM_ZATM" != "n" ]; then - bool ' Enable extended debugging' CONFIG_ATM_ZATM_DEBUG - if [ "$CONFIG_X86" = "y" ]; then - bool ' Enable usec resolution timestamps' CONFIG_ATM_ZATM_EXACT_TS - fi - fi -# bool 'Rolfs TI TNETA1570' CONFIG_ATM_TNETA1570 y -# if [ "$CONFIG_ATM_TNETA1570" = "y" ]; then -# bool ' Enable extended debugging' CONFIG_ATM_TNETA1570_DEBUG n -# fi - tristate 'IDT 77201 (NICStAR) (ForeRunnerLE)' CONFIG_ATM_NICSTAR - if [ "$CONFIG_ATM_NICSTAR" != "n" ]; then - bool ' Use suni PHY driver (155Mbps)' CONFIG_ATM_NICSTAR_USE_SUNI - bool ' Use IDT77015 PHY driver (25Mbps)' CONFIG_ATM_NICSTAR_USE_IDT77105 - fi - tristate 'IDT 77252 (NICStAR II)' CONFIG_ATM_IDT77252 - if [ "$CONFIG_ATM_IDT77252" != "n" ]; then - bool ' Enable debugging messages' CONFIG_ATM_IDT77252_DEBUG - bool ' Receive ALL cells in raw queue' CONFIG_ATM_IDT77252_RCV_ALL - define_bool CONFIG_ATM_IDT77252_USE_SUNI y - fi - tristate 'Madge Ambassador (Collage PCI 155 Server)' CONFIG_ATM_AMBASSADOR - if [ "$CONFIG_ATM_AMBASSADOR" != "n" ]; then - bool ' Enable debugging messages' CONFIG_ATM_AMBASSADOR_DEBUG - fi - tristate 'Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)' CONFIG_ATM_HORIZON - if [ "$CONFIG_ATM_HORIZON" != "n" ]; then - bool ' Enable debugging messages' CONFIG_ATM_HORIZON_DEBUG - fi - tristate 'Interphase ATM PCI x575/x525/x531' CONFIG_ATM_IA - if [ "$CONFIG_ATM_IA" != "n" ]; then - bool ' Enable debugging messages' CONFIG_ATM_IA_DEBUG - fi -fi -if [ "$CONFIG_PCI" = "y" -o "$CONFIG_SBUS" = "y" ]; then - tristate 'FORE Systems 200E-series' CONFIG_ATM_FORE200E_MAYBE - if [ "$CONFIG_ATM_FORE200E_MAYBE" != "n" ]; then - if [ "$CONFIG_PCI" = "y" ]; then - bool ' PCA-200E support' CONFIG_ATM_FORE200E_PCA - if [ "$CONFIG_ATM_FORE200E_PCA" = "y" ]; then - bool ' Use default PCA-200E firmware (normally enabled)' CONFIG_ATM_FORE200E_PCA_DEFAULT_FW - if [ "$CONFIG_ATM_FORE200E_PCA_DEFAULT_FW" = "n" ]; then - string ' Pathname of user-supplied binary firmware' CONFIG_ATM_FORE200E_PCA_FW "" - fi - fi - fi - if [ "$CONFIG_SBUS" = "y" ]; then - bool ' SBA-200E support' CONFIG_ATM_FORE200E_SBA - if [ "$CONFIG_ATM_FORE200E_SBA" = "y" ]; then - bool ' Use default SBA-200E firmware (normally enabled)' CONFIG_ATM_FORE200E_SBA_DEFAULT_FW - if [ "$CONFIG_ATM_FORE200E_SBA_DEFAULT_FW" = "n" ]; then - string ' Pathname of user-supplied binary firmware' CONFIG_ATM_FORE200E_SBA_FW "" - fi - fi - fi - fi - if [ "$CONFIG_ATM_FORE200E_PCA" = "y" -o "$CONFIG_ATM_FORE200E_SBA" = "y" ]; \ - then - int ' Maximum number of tx retries' CONFIG_ATM_FORE200E_TX_RETRY 16 - int ' Debugging level (0-3)' CONFIG_ATM_FORE200E_DEBUG 0 - if [ "$CONFIG_ATM_FORE200E_MAYBE" = "y" ]; then - define_tristate CONFIG_ATM_FORE200E y - else - define_tristate CONFIG_ATM_FORE200E m - fi - fi -fi -endmenu diff --git a/drivers/block/Config.help b/drivers/block/Config.help deleted file mode 100644 index 0ded1e8a2b59..000000000000 --- a/drivers/block/Config.help +++ /dev/null @@ -1,264 +0,0 @@ -CONFIG_BLK_DEV_FD - 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 <file:Documentation/floppy.txt>. - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_BLK_DEV_RAM - 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 <file:Documentation/ramdisk.txt>. - - 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 <file:Documentation/modules.txt>. The module will be - called rd.o. - - Most normal users won't need the RAM disk functionality, and can - thus say N here. - -CONFIG_BLK_DEV_RAM_SIZE - The default value is 4096. Only change this if you know what are - you doing. If you are using IBM S/390, then set this to 8192. - -CONFIG_BLK_DEV_INITRD - 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 <file:Documentation/initrd.txt> - for details. - -CONFIG_BLK_DEV_LOOP - 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. - - 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. If you want to do this, you will first have - to acquire and install a kernel patch from - <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to - say Y to this option. - - Note that alternative ways to use encrypted file systems are - provided by the cfs package, which can be gotten from - <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs - package, available at <http://tcfs.dia.unisa.it/>. You do not need - to say Y here if you want to use one of these. However, using cfs - requires saying Y to "NFS file system support" below while using - tcfs requires applying a kernel patch. An alternative steganography - solution is provided by StegFS, also available from - <ftp://ftp.kerneli.org/pub/kerneli/net-source/>. - - To use the loop device, you need the losetup utility and a recent - version of the mount program, both contained in the util-linux - package. The location and current version number of util-linux is - contained in the file <file:Documentation/Changes>. - - 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 <file:Documentation/modules.txt>. The module - will be called loop.o. - - Most users will answer N here. - -Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL) -CONFIG_BLK_DEV_UMEM - 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.o. - - 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 - -CONFIG_BLK_DEV_NBD - Saying Y here will allow your computer to be a client for network - block devices, i.e. it will be able to use block devices exported by - servers (mount file systems on them etc.). Communication between - client and server works over TCP/IP networking, but to the client - program this is hidden: it looks like a regular local file access to - a block device special file such as /dev/nd0. - - Network block devices also allows you to run a block-device in - userland (making server and client physically the same computer, - communicating using the loopback network device). - - Read <file:Documentation/nbd.txt> for more information, especially - about where to find the server code, which runs in user space and - does not need special kernel support. - - Note that this has nothing to do with the network file systems NFS - or Coda; you can say N here even if you intend to use NFS or Coda. - - 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 <file:Documentation/modules.txt>. The module - will be called nbd.o. - - If unsure, say N. - -CONFIG_BLK_DEV_XD - 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 <file:Documentation/modules.txt>. The module - will be called xd.o. - - It's pretty unlikely that you have one of these: say N. - -CONFIG_BLK_DEV_PS2 - 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 <file:Documentation/modules.txt>. The module - will be called ps2esdi.o. - -CONFIG_BLK_DEV_DAC960 - This driver adds support for the Mylex DAC960, AcceleRAID, and - eXtremeRAID PCI RAID controllers. See the file - <file:Documentation/README.DAC960> 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 <file:Documentation/modules.txt>. The module - will be called DAC960.o. - -CONFIG_PARIDE - 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 <file:Documentation/paride.txt> 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.o. - - 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.). - -CONFIG_BLK_CPQ_CISS_DA - This is the driver for Compaq Smart Array 5xxx controllers. - Everyone using these boards should say Y here. - See <file:Documentation/cciss.txt> for the current list of - boards supported by this driver, and for further information - on the use of this driver. - -CONFIG_CISS_SCSI_TAPE - 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. - -CONFIG_BLK_DEV_SWIM_IOP - Say Y here to support the SWIM (Super Woz Integrated Machine) IOP - floppy controller on the Macintosh IIfx and Quadra 900/950. - -CONFIG_AMIGA_Z2RAM - 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.o. If you want - to compile it as a module, say M here and read - <file:Documentation/modules.txt>. - -CONFIG_ATARI_ACSI - 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.o. - -CONFIG_ACSI_MULTI_LUN - 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. - -CONFIG_ATARI_SLM - 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.o. Be warned: the driver needs much ST-RAM and can cause - problems due to that fact! - -CONFIG_BLK_CPQ_DA - This is the driver for Compaq Smart Array controllers. Everyone - using these boards should say Y here. See the file - <file:Documentation/cpqarray.txt> for the current list of boards - supported by this driver, and for further information on the use of - this driver. - -CONFIG_LBD - 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. diff --git a/drivers/block/Config.in b/drivers/block/Config.in deleted file mode 100644 index 23aab28fcf42..000000000000 --- a/drivers/block/Config.in +++ /dev/null @@ -1,54 +0,0 @@ -# -# Block device driver configuration -# -mainmenu_option next_comment -comment 'Block devices' - -tristate 'Normal floppy disk support' CONFIG_BLK_DEV_FD -if [ "$CONFIG_AMIGA" = "y" ]; then - tristate 'Amiga floppy support' CONFIG_AMIGA_FLOPPY -fi -if [ "$CONFIG_ATARI" = "y" ]; then - tristate 'Atari floppy support' CONFIG_ATARI_FLOPPY -fi -if [ "$CONFIG_MAC" = "y" ]; then - dep_bool 'Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)' CONFIG_BLK_DEV_SWIM_IOP $CONFIG_EXPERIMENTAL -fi -if [ "$CONFIG_MCA" = "y" ]; then - tristate 'PS/2 ESDI hard disk support' CONFIG_BLK_DEV_PS2 -fi -if [ "$CONFIG_ZORRO" = "y" ]; then - tristate 'Amiga Zorro II ramdisk support' CONFIG_AMIGA_Z2RAM -fi -if [ "$CONFIG_ATARI" = "y" ]; then - tristate 'Atari ACSI support' CONFIG_ATARI_ACSI - if [ "$CONFIG_ATARI_ACSI" != "n" ]; then - comment 'Some devices (e.g. CD jukebox) support multiple LUNs' - bool ' Probe all LUNs on each ACSI device' CONFIG_ACSI_MULTI_LUN - tristate ' Atari SLM laser printer support' CONFIG_ATARI_SLM - fi -fi -dep_tristate 'XT hard disk support' CONFIG_BLK_DEV_XD $CONFIG_ISA -dep_tristate 'Parallel port IDE device support' CONFIG_PARIDE $CONFIG_PARPORT -if [ "$CONFIG_PARIDE" = "y" -o "$CONFIG_PARIDE" = "m" ]; then - source drivers/block/paride/Config.in -fi -dep_tristate 'Compaq SMART2 support' CONFIG_BLK_CPQ_DA $CONFIG_PCI -dep_tristate 'Compaq Smart Array 5xxx support' CONFIG_BLK_CPQ_CISS_DA $CONFIG_PCI -dep_mbool ' SCSI tape drive support for Smart Array 5xxx' CONFIG_CISS_SCSI_TAPE $CONFIG_BLK_CPQ_CISS_DA $CONFIG_SCSI -dep_tristate 'Mylex DAC960/DAC1100 PCI RAID Controller support' CONFIG_BLK_DEV_DAC960 $CONFIG_PCI -dep_tristate 'Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)' CONFIG_BLK_DEV_UMEM $CONFIG_PCI $CONFIG_EXPERIMENTAL - -tristate 'Loopback device support' CONFIG_BLK_DEV_LOOP -dep_tristate 'Network block device support' CONFIG_BLK_DEV_NBD $CONFIG_NET - -tristate 'RAM disk support' CONFIG_BLK_DEV_RAM -if [ "$CONFIG_BLK_DEV_RAM" = "y" -o "$CONFIG_BLK_DEV_RAM" = "m" ]; then - int ' Default RAM disk size' CONFIG_BLK_DEV_RAM_SIZE 4096 -fi -dep_bool ' Initial RAM disk (initrd) support' CONFIG_BLK_DEV_INITRD $CONFIG_BLK_DEV_RAM - -if [ "$CONFIG_X86" = "y" ]; then - bool 'Support for Large Block Devices' CONFIG_LBD -fi -endmenu diff --git a/drivers/block/paride/Config.help b/drivers/block/paride/Config.help deleted file mode 100644 index 50102d7fe9cd..000000000000 --- a/drivers/block/paride/Config.help +++ /dev/null @@ -1,223 +0,0 @@ -CONFIG_PARIDE_PD - 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.o. 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. - -CONFIG_PARIDE_PCD - 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.o. 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. - -CONFIG_PARIDE_PF - 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.o. - 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. - -CONFIG_PARIDE_PT - 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.o. - 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. - -CONFIG_PARIDE_PG - 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.o. - - 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 <file:include/linux/pg.h>. for details. - - You can obtain the most recent version of cdrtools from - <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and - later fully support this driver. - -CONFIG_PARIDE_ATEN - 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.o. You must also - have a high-level driver for the type of device that you want to - support. - -CONFIG_PARIDE_BPCK - 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.o. You must also have a high-level driver for the type - of device that you want to support. - -CONFIG_PARIDE_BPCK6 - 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.o. You must also have a high-level driver for the type - of device that you want to support. - -CONFIG_PARIDE_COMM - 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.o. You must also have - a high-level driver for the type of device that you want to support. - -CONFIG_PARIDE_DSTR - 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.o. You must also have - a high-level driver for the type of device that you want to support. - -CONFIG_PARIDE_EPAT - 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.o. You must also - have a high-level driver for the type of device that you want to - support. - -CONFIG_PARIDE_EPATC8 - 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. - -CONFIG_PARIDE_EPIA - 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.o. You must also have a - high-level driver for the type of device that you want to support. - -CONFIG_PARIDE_FIT2 - 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.o. - You must also have a high-level driver for the type of device that - you want to support. - -CONFIG_PARIDE_FIT3 - 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.o. You must also have a high-level driver for the type - of device that you want to support. - -CONFIG_PARIDE_FRIQ - 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.o. You must also have a high-level driver for the type - of device that you want to support. - -CONFIG_PARIDE_FRPW - 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.o. You must also have a high-level driver for the type - of device that you want to support. - -CONFIG_PARIDE_KBIC - 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.o. You must also have a high-level driver - for the type of device that you want to support. - -CONFIG_PARIDE_KTTI - 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.o. You must also - have a high-level driver for the type of device that you want to - support. - -CONFIG_PARIDE_ON20 - 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.o. You must also have a high-level driver for the - type of device that you want to support. - -CONFIG_PARIDE_ON26 - 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.o. You must also have a high-level driver for the type - of device that you want to support. - diff --git a/drivers/block/paride/Config.in b/drivers/block/paride/Config.in deleted file mode 100644 index eccb773caa9e..000000000000 --- a/drivers/block/paride/Config.in +++ /dev/null @@ -1,43 +0,0 @@ -# -# PARIDE configuration -# - -# PARIDE doesn't need PARPORT, but if PARPORT is configured as a module, -# PARIDE must also be a module. The bogus CONFIG_PARIDE_PARPORT option -# controls the choices given to the user ... - -if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ]; then - define_tristate CONFIG_PARIDE_PARPORT y -else - define_tristate CONFIG_PARIDE_PARPORT m -fi - -comment 'Parallel IDE high-level drivers' -dep_tristate ' Parallel port IDE disks' CONFIG_PARIDE_PD $CONFIG_PARIDE -dep_tristate ' Parallel port ATAPI CD-ROMs' CONFIG_PARIDE_PCD $CONFIG_PARIDE -dep_tristate ' Parallel port ATAPI disks' CONFIG_PARIDE_PF $CONFIG_PARIDE -dep_tristate ' Parallel port ATAPI tapes' CONFIG_PARIDE_PT $CONFIG_PARIDE -dep_tristate ' Parallel port generic ATAPI devices' CONFIG_PARIDE_PG $CONFIG_PARIDE -comment 'Parallel IDE protocol modules' -dep_tristate ' ATEN EH-100 protocol' CONFIG_PARIDE_ATEN $CONFIG_PARIDE -dep_tristate ' MicroSolutions backpack (Series 5) protocol' CONFIG_PARIDE_BPCK $CONFIG_PARIDE -dep_tristate ' MicroSolutions backpack (Series 6) protocol' CONFIG_PARIDE_BPCK6 $CONFIG_PARIDE -dep_tristate ' DataStor Commuter protocol' CONFIG_PARIDE_COMM $CONFIG_PARIDE -dep_tristate ' DataStor EP-2000 protocol' CONFIG_PARIDE_DSTR $CONFIG_PARIDE -dep_tristate ' FIT TD-2000 protocol' CONFIG_PARIDE_FIT2 $CONFIG_PARIDE -dep_tristate ' FIT TD-3000 protocol' CONFIG_PARIDE_FIT3 $CONFIG_PARIDE -dep_tristate ' Shuttle EPAT/EPEZ protocol' CONFIG_PARIDE_EPAT $CONFIG_PARIDE -if [ "$CONFIG_PARIDE_EPAT" != "n" ]; then - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool ' Support c7/c8 chips (EXPERIMENTAL)' CONFIG_PARIDE_EPATC8 - fi -fi - -dep_tristate ' Shuttle EPIA protocol' CONFIG_PARIDE_EPIA $CONFIG_PARIDE -dep_tristate ' Freecom IQ ASIC-2 protocol' CONFIG_PARIDE_FRIQ $CONFIG_PARIDE -dep_tristate ' FreeCom power protocol' CONFIG_PARIDE_FRPW $CONFIG_PARIDE -dep_tristate ' KingByte KBIC-951A/971A protocols' CONFIG_PARIDE_KBIC $CONFIG_PARIDE -dep_tristate ' KT PHd protocol' CONFIG_PARIDE_KTTI $CONFIG_PARIDE -dep_tristate ' OnSpec 90c20 protocol' CONFIG_PARIDE_ON20 $CONFIG_PARIDE -dep_tristate ' OnSpec 90c26 protocol' CONFIG_PARIDE_ON26 $CONFIG_PARIDE -# diff --git a/drivers/bluetooth/Config.help b/drivers/bluetooth/Config.help deleted file mode 100644 index 212fec68fdb3..000000000000 --- a/drivers/bluetooth/Config.help +++ /dev/null @@ -1,88 +0,0 @@ -HCI UART driver -CONFIG_BT_HCIUART - Bluetooth HCI UART driver. - This driver is required if you want to use Bluetooth devices with - serial port interface. You will also need this driver if you have - UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card - adapter and BrainBoxes Bluetooth PC Card. - - Say Y here to compile support for Bluetooth UART devices into the - kernel or say M to compile it as module (hci_uart.o). - -HCI UART (H4) protocol support -CONFIG_BT_HCIUART_H4 - UART (H4) is serial protocol for communication between Bluetooth - device and host. This protocol is required for most Bluetooth devices - with UART interface, including PCMCIA and CF cards. - - Say Y here to compile support for HCI UART (H4) protocol. - -HCI BCSP protocol support -CONFIG_BT_HCIUART_BCSP - BCSP (BlueCore Serial Protocol) is serial protocol for communication - between Bluetooth device and host. This protocol is required for non - USB Bluetooth devices based on CSR BlueCore chip, including PCMCIA and - CF cards. - - Say Y here to compile support for HCI BCSP protocol. - -HCI USB driver -CONFIG_BT_HCIUSB - Bluetooth HCI USB driver. - This driver is required if you want to use Bluetooth devices with - USB interface. - - Say Y here to compile support for Bluetooth USB devices into the - kernel or say M to compile it as module (hci_usb.o). - -HCI USB zero packet support -CONFIG_BT_USB_ZERO_PACKET - Support for USB zero packets. - This option is provided only as a work around for buggy Bluetooth USB - devices. Do _not_ enable it unless you know for sure that your device - requires zero packets. - Most people should say N here. - -HCI VHCI Virtual HCI device driver -CONFIG_BT_HCIVHCI - Bluetooth Virtual HCI device driver. - This driver is required if you want to use HCI Emulation software. - - Say Y here to compile support for virtual HCI devices into the - kernel or say M to compile it as module (hci_vhci.o). - -HCI DTL1 (PC Card) device driver -CONFIG_BT_HCIDTL1 - Bluetooth HCI DTL1 (PC Card) driver. - This driver provides support for Bluetooth PCMCIA devices with - Nokia DTL1 interface: - Nokia Bluetooth Card - Socket Bluetooth CF Card - - Say Y here to compile support for HCI DTL1 devices into the - kernel or say M to compile it as module (dtl1_cs.o). - -HCI BT3C (PC Card) device driver -CONFIG_BT_HCIBT3C - Bluetooth HCI BT3C (PC Card) driver. - This driver provides support for Bluetooth PCMCIA devices with - 3Com BT3C interface: - 3Com Bluetooth Card (3CRWB6096) - HP Bluetooth Card - - The HCI BT3C driver uses external firmware loader program provided in - the BlueFW package. For more information, see <http://bluez.sf.net>. - - Say Y here to compile support for HCI BT3C devices into the - kernel or say M to compile it as module (bt3c_cs.o). - -HCI BlueCard (PC Card) device driver -CONFIG_BT_HCIBLUECARD - Bluetooth HCI BlueCard (PC Card) driver. - This driver provides support for Bluetooth PCMCIA devices with - Anycom BlueCard interface: - Anycom Bluetooth PC Card - Anycom Bluetooth CF Card - - Say Y here to compile support for HCI BlueCard devices into the - kernel or say M to compile it as module (bluecard_cs.o). diff --git a/drivers/bluetooth/Config.in b/drivers/bluetooth/Config.in deleted file mode 100644 index 46f37275ff76..000000000000 --- a/drivers/bluetooth/Config.in +++ /dev/null @@ -1,23 +0,0 @@ -mainmenu_option next_comment -comment 'Bluetooth device drivers' - -dep_tristate 'HCI USB driver' CONFIG_BT_HCIUSB $CONFIG_BT $CONFIG_USB -if [ "$CONFIG_BT_HCIUSB" != "n" ]; then - bool ' USB zero packet support' CONFIG_BT_USB_ZERO_PACKET -fi - -dep_tristate 'HCI UART driver' CONFIG_BT_HCIUART $CONFIG_BT -if [ "$CONFIG_BT_HCIUART" != "n" ]; then - bool ' UART (H4) protocol support' CONFIG_BT_HCIUART_H4 - bool ' BCSP protocol support' CONFIG_BT_HCIUART_BCSP -fi - -dep_tristate 'HCI DTL1 (PC Card) driver' CONFIG_BT_HCIDTL1 $CONFIG_PCMCIA $CONFIG_BT - -dep_tristate 'HCI BT3C (PC Card) driver' CONFIG_BT_HCIBT3C $CONFIG_PCMCIA $CONFIG_BT - -dep_tristate 'HCI BlueCard (PC Card) driver' CONFIG_BT_HCIBLUECARD $CONFIG_PCMCIA $CONFIG_BT - -dep_tristate 'HCI VHCI (Virtual HCI device) driver' CONFIG_BT_HCIVHCI $CONFIG_BT - -endmenu diff --git a/drivers/cdrom/Config.help b/drivers/cdrom/Config.help deleted file mode 100644 index 92e333a3a6fd..000000000000 --- a/drivers/cdrom/Config.help +++ /dev/null @@ -1,206 +0,0 @@ -CONFIG_CDU31A - These CD-ROM drives have a spring-pop-out caddyless drawer, and a - rectangular green LED centered beneath it. NOTE: these CD-ROM - drives will not be auto detected by the kernel at boot time; you - have to provide the interface address as an option to the kernel at - boot time as described in <file:Documentation/cdrom/cdu31a> or fill - in your parameters into <file:drivers/cdrom/cdu31a.c>. Try "man - bootparam" or see the documentation of your boot loader (lilo or - loadlin) about how to pass options to the kernel. - - If you say Y here, 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. - - 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 cdu31a.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MCD - This is the older of the two drivers for the older Mitsumi models - LU-005, FX-001 and FX-001D. This is not the right driver for the - FX-001DE and the triple or quad speed models (all these are - IDE/ATAPI models). Please also the file - <file:Documentation/cdrom/mcd>. - - With the old LU-005 model, the whole drive chassis slides out for cd - insertion. The FX-xxx models use a motorized tray type mechanism. - Note that this driver does not support XA or MultiSession CDs - (PhotoCDs). There is a new driver (next question) which can do - this. If you want that one, say N here. - - If you say Y here, 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. - - 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 mcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MCD_IRQ - This allows you to specify the default value of the IRQ used by the - driver. This setting can be overridden by passing the "mcd=" - parameter to the kernel at boot time (or at module load time if you - said M to "Standard Mitsumi CD-ROM support"). - -CONFIG_MCD_BASE - This allows you to specify the default value of the I/O base address - used by the driver. This setting can be overridden by passing the - "mcd=" parameter to the kernel at boot time (or at module load time - if you said M to "Standard Mitsumi CD-ROM support"). - -CONFIG_MCDX - Use this driver if you want to be able to read XA or MultiSession - CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005, - FX-001 or FX-001D CD-ROM drive. In addition, this driver uses much - less kernel memory than the old one, if that is a concern. This - driver is able to support more than one drive, but each drive needs - a separate interface card. Please read the file - <file:Documentation/cdrom/mcdx>. - - If you say Y here, 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. - - 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 mcdx.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SBPCD - This driver supports most of the drives which use the Panasonic or - Sound Blaster interface. Please read the file - <file:Documentation/cdrom/sbpcd>. - - The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives - (sometimes labeled "Creative"), the Creative Labs CD200, the - Longshine LCS-7260, the "IBM External ISA CD-ROM" (in fact a CR-56x - model), the TEAC CD-55A fall under this category. Some other - "electrically compatible" drives (Vertos, Genoa, some Funai models) - are currently not supported; for the Sanyo H94A drive currently a - separate driver (asked later) is responsible. Most drives have a - uniquely shaped faceplate, with a caddyless motorized drawer, but - without external brand markings. The older CR-52x drives have a - caddy and manual loading/eject, but still no external markings. The - driver is able to do an extended auto-probing for interface - addresses and drive types; this can help to find facts in cases you - are not sure, but can consume some time during the boot process if - none of the supported drives gets found. Once your drive got found, - you should enter the reported parameters into - <file:drivers/cdrom/sbpcd.h> and set "DISTRIBUTION 0" there. - - This driver can support up to four CD-ROM controller cards, and each - card can support up to four CD-ROM drives; if you say Y here, you - will be asked how many controller cards you have. If compiled as a - module, only one controller card (but with up to four drives) is - usable. - - If you say Y here, 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. - - 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 sbpcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_AZTCD - This is your driver if you have an Aztech CDA268-01A, Orchid - CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCD-ROM CR520 or - CR540 CD-ROM drive. This driver -- just like all these CD-ROM - drivers -- is NOT for CD-ROM drives with IDE/ATAPI interfaces, such - as Aztech CDA269-031SE. Please read the file - <file:Documentation/cdrom/aztcd>. - - If you say Y here, 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. - - 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 aztcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_CDU535 - This is the driver for the older Sony CDU-535 and CDU-531 CD-ROM - drives. Please read the file <file:Documentation/cdrom/sonycd535>. - - If you say Y here, 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. - - 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 sonycd535.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GSCD - If this is your CD-ROM drive, say Y here. As described in the file - <file:Documentation/cdrom/gscd>, you might have to change a setting - in the file <file:drivers/cdrom/gscd.h> before compiling the - kernel. Please read the file <file:Documentation/cdrom/gscd>. - - If you say Y here, 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. - - 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 gscd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_CM206 - If you have a Philips/LMS CD-ROM drive cm206 in combination with a - cm260 host adapter card, say Y here. Please also read the file - <file:Documentation/cdrom/cm206>. - - If you say Y here, 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. - - 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 cm206.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_OPTCD - This is the driver for the 'DOLPHIN' drive with a 34-pin Sony - compatible interface. It also works with the Lasermate CR328A. If - you have one of those, say Y. This driver does not work for the - Optics Storage 8001 drive; use the IDE-ATAPI CD-ROM driver for that - one. Please read the file <file:Documentation/cdrom/optcd>. - - If you say Y here, 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. - - 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 optcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SJCD - If this is your CD-ROM drive, say Y here and read the file - <file:Documentation/cdrom/sjcd>. You should then also say Y or M to - "ISO 9660 CD-ROM file system support" below, because that's the - file system used on 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 sjcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_ISP16_CDI - These are sound cards with built-in cdrom interfaces using the OPTi - 82C928 or 82C929 chips. Say Y here to have them detected and - possibly configured at boot time. In addition, You'll have to say Y - to a driver for the particular cdrom drive you have attached to the - card. Read <file:Documentation/cdrom/isp16> 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 isp16.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - diff --git a/drivers/cdrom/Config.in b/drivers/cdrom/Config.in deleted file mode 100644 index c1ff66af9566..000000000000 --- a/drivers/cdrom/Config.in +++ /dev/null @@ -1,18 +0,0 @@ -# -# CDROM driver configuration -# -tristate ' Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support' CONFIG_AZTCD -tristate ' Goldstar R420 CDROM support' CONFIG_GSCD -tristate ' Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support' CONFIG_SBPCD -tristate ' Mitsumi (standard) [no XA/Multisession] CDROM support' CONFIG_MCD -if [ "$CONFIG_MCD" != "n" ]; then - int 'MCD IRQ' CONFIG_MCD_IRQ 11 - hex 'MCD I/O base' CONFIG_MCD_BASE 300 -fi -tristate ' Mitsumi [XA/MultiSession] CDROM support' CONFIG_MCDX -tristate ' Optics Storage DOLPHIN 8000AT CDROM support' CONFIG_OPTCD -tristate ' Philips/LMS CM206 CDROM support' CONFIG_CM206 -tristate ' Sanyo CDR-H94A CDROM support' CONFIG_SJCD -tristate ' ISP16/MAD16/Mozart soft configurable cdrom interface support' CONFIG_ISP16_CDI -tristate ' Sony CDU31A/CDU33A CDROM support' CONFIG_CDU31A -tristate ' Sony CDU535 CDROM support' CONFIG_CDU535 diff --git a/drivers/char/Config.help b/drivers/char/Config.help deleted file mode 100644 index 34e204aca958..000000000000 --- a/drivers/char/Config.help +++ /dev/null @@ -1,969 +0,0 @@ -CONFIG_QTRONIX_KEYBOARD - Images of Qtronix keyboards are at - <http://www.qtronix.com/keyboard.html>. - -CONFIG_SERIAL_NONSTANDARD - Say Y here if you have any non-standard serial boards -- boards - which aren't supported using the standard "dumb" serial driver. - This includes intelligent serial boards such as Cyclades, - Digiboards, etc. These are usually used for systems that need many - serial ports because they serve many terminals or dial-in - connections. - - 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 non-standard serial boards. - - Most people can say N here. - -CONFIG_MWAVE - The ACP modem (Mwave) for Linux is a WinModem. It is composed of a - kernel driver and a user level application. Together these components - support direct attachment to public switched telephone networks (PSTNs) - and support selected world wide countries. - - This version of the ACP Modem driver supports the IBM Thinkpad 600E, - 600, and 770 that include on board ACP modem hardware. - - The modem also supports the standard communications port interface - (ttySx) and is compatible with the Hayes AT Command Set. - - The user level application needed to use this driver can be found at - the IBM Linux Technology Center (LTC) web site: - <http://www.ibm.com/linux/ltc/>. - - If you own one of the above IBM Thinkpads which has the Mwave chipset - in it, say Y. - - 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 mwave.o. If you want to compile it as - a module, say M here and read Documentation/modules.txt. - -CONFIG_I810_TCO - Hardware driver for the TCO timer built into the Intel i810 and i815 - chipset family. The TCO (Total Cost of Ownership) timer is a - watchdog timer that will reboot the machine after its second - expiration. The expiration time can be configured by commandline - argument "i810_margin=<n>" where <n> is the counter initial value. - It is decremented every 0.6 secs, the default is 50 which gives a - timeout of 30 seconds and one minute until reset. - - On some motherboards the driver may fail to reset the chipset's - NO_REBOOT flag which prevents the watchdog from rebooting the - machine. If this is the case you will get a kernel message like - "i810tco init: failed to reset NO_REBOOT flag". - - If you want to compile this as a module, say M and read - <file:Documentation/modules.txt>. The module will be called - i810-tco.o. - -CONFIG_VT - If you say Y here, you will get support for terminal devices with - display and keyboard devices. These are called "virtual" because you - can run several virtual terminals (also called virtual consoles) on - one physical terminal. This is rather useful, for example one - virtual terminal can collect system messages and warnings, another - one can be used for a text-mode user session, and a third could run - an X session, all in parallel. Switching between virtual terminals - is done with certain key combinations, usually Alt-<function key>. - - The setterm command ("man setterm") can be used to change the - properties (such as colors or beeping) of a virtual terminal. The - man page console_codes(4) ("man console_codes") contains the special - character sequences that can be used to change those properties - directly. The fonts used on virtual terminals can be changed with - the setfont ("man setfont") command and the key bindings are defined - with the loadkeys ("man loadkeys") command. - - You need at least one virtual terminal device in order to make use - of your keyboard and monitor. Therefore, only people configuring an - embedded system would want to say N here in order to save some - memory; the only way to log into such a system is then via a serial - or network connection. - - If unsure, say Y, or else you won't be able to do much with your new - shiny Linux system :-) - -CONFIG_VT_CONSOLE - The system console is the device which receives all kernel messages - and warnings and which allows logins in single user mode. If you - answer Y here, a virtual terminal (the device used to interact with - a physical terminal) can be used as system console. This is the most - common mode of operations, so you should say Y here unless you want - the kernel messages be output only to a serial port (in which case - you should say Y to "Console on serial port", below). - - If you do say Y here, by default the currently visible virtual - terminal (/dev/tty0) will be used as system console. You can change - that with a kernel command line option such as "console=tty3" which - would use the third virtual terminal as system console. (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.) - - If unsure, say Y. - -CONFIG_ROCKETPORT - This is a driver for the Comtrol Rocketport cards which provide - multiple serial ports. You would need something like this to connect - more than two modems to your Linux box, for instance in order to - become a dial-in server. - - If you want to compile this driver as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - rocket.o. - -CONFIG_DIGIEPCA - This is a driver for Digi International's Xx, Xeve, and Xem series - of cards which provide multiple serial ports. You would need - something like this to connect more than two modems to your Linux - box, for instance in order to become a dial-in server. This driver - supports the original PC (ISA) boards as well as PCI, and EISA. If - you have a card like this, say Y here and read the file - <file:Documentation/digiepca.txt>. - - NOTE: There is another, separate driver for the Digiboard PC boards: - "Digiboard PC/Xx Support" below. You should (and can) only select - one of the two drivers. - - If you want to compile this driver as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called epca.o. - -CONFIG_DIGI - This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards - that give you many serial ports. You would need something like this - to connect more than two modems to your Linux box, for instance in - order to become a dial-in server. If you have a card like that, say - Y here and read the file <file:Documentation/digiboard.txt>. - - If you want to compile this driver as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called pcxx.o. - -CONFIG_RISCOM8 - This is a driver for the SDL Communications RISCom/8 multiport card, - which gives you many serial ports. You would need something like - this to connect more than two modems to your Linux box, for instance - in order to become a dial-in server. If you have a card like that, - say Y here and read the file <file:Documentation/riscom8.txt>. - - Also it's possible to say M here and compile this driver as kernel - loadable module; the module will be called riscom8.o. - -CONFIG_COMPUTONE - This driver supports the entire family of Intelliport II/Plus - controllers with the exception of the MicroChannel controllers and - products previous to the Intelliport II. These are multiport cards, - which give you many serial ports. You would need something like this - to connect more than two modems to your Linux box, for instance in - order to become a dial-in server. If you have a card like that, say - Y here and read <file:Documentation/computone.txt>. - - 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 <file:Documentation/modules.txt>. You will get - two modules called ip2.o and ip2main.o. - -CONFIG_SPECIALIX - This is a driver for the Specialix IO8+ multiport card (both the - ISA and the PCI version) which gives you many serial ports. You - would need something like this to connect more than two modems to - your Linux box, for instance in order to become a dial-in server. - - If you have a card like that, say Y here and read the file - <file:Documentation/specialix.txt>. Also it's possible to say M here - and compile this driver as kernel loadable module which will be - called specialix.o. - -CONFIG_SPECIALIX_RTSCTS - The Specialix IO8+ card can only support either RTS or DTR. If you - say N here, the driver will use the pin as "DTR" when the tty is in - software handshake mode. If you say Y here or hardware handshake is - on, it will always be RTS. Read the file - <file:Documentation/specialix.txt> for more information. - -CONFIG_RIO - This is a driver for the Specialix RIO, a smart serial card which - drives an outboard box that can support up to 128 ports. Product - information is at <http://www.sphinxcst.co.uk/perle/multi.htm>. - There are both ISA and PCI versions. - -CONFIG_RIO_OLDPCI - Older RIO PCI cards need some initialization-time configuration to - determine the IRQ and some control addresses. If you have a RIO and - this doesn't seem to work, try setting this to Y. - -CONFIG_CYCLADES - This is a driver for a card that gives you many serial ports. You - would need something like this to connect more than two modems to - your Linux box, for instance in order to become a dial-in server. - For information about the Cyclades-Z card, read - <file:drivers/char/README.cycladesZ>. - - As of 1.3.9x kernels, this driver's minor numbers start at 0 instead - of 32. - - 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 <file:Documentation/modules.txt>. The module - will be called cyclades.o. - - If you haven't heard about it, it's safe to say N. - -CONFIG_CYZ_INTR - The Cyclades-Z family of multiport cards allows 2 (two) driver op - modes: polling and interrupt. In polling mode, the driver will check - the status of the Cyclades-Z ports every certain amount of time - (which is called polling cycle and is configurable). In interrupt - mode, it will use an interrupt line (IRQ) in order to check the - status of the Cyclades-Z ports. The default op mode is polling. If - unsure, say N. - -CONFIG_STALDRV - Stallion cards give you many serial ports. You would need something - like this to connect more than two modems to your Linux box, for - instance in order to become a dial-in server. If you say Y here, - you will be asked for your specific card model in the next - questions. Make sure to read <file:Documentation/stallion.txt> in - this case. If you have never heard about all this, it's safe to - say N. - -CONFIG_STALLION - If you have an EasyIO or EasyConnection 8/32 multiport Stallion - card, then this is for you; say Y. Make sure to read - <file:Documentation/stallion.txt>. - - 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 <file:Documentation/modules.txt>. The module - will be called stallion.o. - -CONFIG_ISTALLION - If you have an EasyConnection 8/64, ONboard, Brumby or Stallion - serial multiport card, say Y here. Make sure to read - <file:Documentation/stallion.txt>. - - 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 <file:Documentation/modules.txt>. The module will be called - istallion.o. - -CONFIG_SERIAL_TX3912 - The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core; - see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>. - Say Y here to enable kernel support for the on-board serial port. - -CONFIG_SERIAL_TX3912_CONSOLE - The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core; - see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>. - Say Y here to direct console I/O to the on-board serial port. - -CONFIG_AU1000_SERIAL_CONSOLE - If you have an Alchemy AU1000 processor (MIPS based) and you want - to use a console on a serial port, say Y. Otherwise, say N. - -CONFIG_AU1000_UART - If you have an Alchemy AU1000 processor (MIPS based) and you want - to use serial ports, say Y. Otherwise, say N. - -CONFIG_SYNCLINK - Provides support for the SyncLink ISA and PCI multiprotocol serial - adapters. These adapters support asynchronous and HDLC bit - synchronous communication up to 10Mbps (PCI adapter). - - This driver can only be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called synclink.o. If you want to do that, say M - here. - -CONFIG_SYNCLINKMP - Enable support for the SyncLink Multiport (2 or 4 ports) - serial adapter, running asynchronous and HDLC communications up - to 2.048Mbps. Each ports is independently selectable for - RS-232, V.35, RS-449, RS-530, and X.21 - - This driver may be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called synclinkmp.o. If you want to do that, say M - here. - -CONFIG_N_HDLC - Allows synchronous HDLC communications with tty device drivers that - support synchronous HDLC such as the Microgate SyncLink adapter. - - This driver can only be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called n_hdlc.o. If you want to do that, say M - here. - -CONFIG_SX - This is a driver for the SX and SI multiport serial cards. - Please read the file <file:Documentation/sx.txt> for details. - - This driver can only be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called sx.o. If you want to do that, say M here. - -CONFIG_ESPSERIAL - This is a driver which supports Hayes ESP serial ports. Both single - port cards and multiport cards are supported. Make sure to read - <file:Documentation/hayes-esp.txt>. - - 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 <file:Documentation/modules.txt>. The module will be - called esp.o. If unsure, say N. - -CONFIG_MOXA_INTELLIO - Say Y here if you have a Moxa Intellio multiport serial card. - - This driver can also be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called moxa.o. If you want to do that, say M - here. - -CONFIG_MOXA_SMARTIO - Say Y here if you have a Moxa SmartIO multiport serial card. - - This driver can also be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called mxser.o. If you want to do that, say M - here. - -CONFIG_ISI - This is a driver for the Multi-Tech cards which provide several - serial ports. The driver is experimental and can currently only be - built as a module ( = code which can be inserted in and removed from - the running kernel whenever you want). Please read - <file:Documentation/modules.txt>. The module will be called - isicom.o. - -CONFIG_UNIX98_PTYS - A pseudo terminal (PTY) is a software device consisting of two - halves: a master and a slave. The slave device behaves identical to - a physical terminal; the master device is used by a process to - read data from and write data to the slave, thereby emulating a - terminal. Typical programs for the master side are telnet servers - and xterms. - - Linux has traditionally used the BSD-like names /dev/ptyxx for - masters and /dev/ttyxx for slaves of pseudo terminals. This scheme - has a number of problems. The GNU C library glibc 2.1 and later, - however, supports the Unix98 naming standard: in order to acquire a - pseudo terminal, a process opens /dev/ptmx; the number of the pseudo - terminal is then made available to the process and the pseudo - terminal slave can be accessed as /dev/pts/<number>. What was - traditionally /dev/ttyp2 will then be /dev/pts/2, for example. - - The entries in /dev/pts/ are created on the fly by a virtual - file system; therefore, if you say Y here you should say Y to - "/dev/pts file system for Unix98 PTYs" as well. - - If you want to say Y here, you need to have the C library glibc 2.1 - or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*"). - Read the instructions in <file:Documentation/Changes> pertaining to - pseudo terminals. It's safe to say N. - -CONFIG_UNIX98_PTY_COUNT - The maximum number of Unix98 PTYs that can be used at any one time. - The default is 256, and should be enough for desktop systems. Server - machines which support incoming telnet/rlogin/ssh connections and/or - serve several X terminals may want to increase this: every incoming - connection and every xterm uses up one PTY. - - When not in use, each additional set of 256 PTYs occupy - approximately 8 KB of kernel memory on 32-bit architectures. - -CONFIG_PRINTER - If you intend to attach a printer to the parallel port of your Linux - box (as opposed to using a serial printer; if the connector at the - printer has 9 or 25 holes ["female"], then it's serial), say Y. - Also read the Printing-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - It is possible to share one parallel port among several devices - (e.g. printer and ZIP drive) 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 <file:Documentation/modules.txt> and - <file:Documentation/parport.txt>. The module will be called lp.o. - - If you have several parallel ports, you can specify which ports to - use with the "lp" kernel command line option. (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.) The syntax of the - "lp" command line option can be found in <file:drivers/char/lp.c>. - - If you have more than 8 printers, you need to increase the LP_NO - macro in lp.c and the PARPORT_MAX macro in parport.h. - -CONFIG_LP_CONSOLE - If you want kernel messages to be printed out as they occur, you - can have a console on the printer. This option adds support for - doing that; to actually get it to happen you need to pass the - option "console=lp0" to the kernel at boot time. - - If the printer is out of paper (or off, or unplugged, or too - busy..) the kernel will stall until the printer is ready again. - By defining CONSOLE_LP_STRICT to 0 (at your own risk) you - can make the kernel continue when this happens, - but it'll lose the kernel messages. - - If unsure, say N. - -CONFIG_PPDEV - Saying Y to this adds support for /dev/parport device nodes. This - is needed for programs that want portable access to the parallel - port, for instance deviceid (which displays Plug-and-Play device - IDs). - - This is the parallel port equivalent of SCSI generic support (sg). - It is safe to say N to this -- it is not needed for normal printing - or parallel port CD-ROM/disk support. - - This support is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - ppdev.o. - - If unsure, say N. - -CONFIG_BUSMOUSE - Say Y here if your machine has a bus mouse as opposed to a serial - mouse. Most people have a regular serial MouseSystem or - Microsoft mouse (made by Logitech) that plugs into a COM port - (rectangular with 9 or 25 pins). These people say N here. - - If you have a laptop, you either have to check the documentation or - experiment a bit to find out whether the trackball is a serial mouse - or not; it's best to say Y here for you. - - This is the generic bus mouse driver code. If you have a bus mouse, - you will have to say Y here and also to the specific driver for your - mouse below. - - 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 busmouse.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_QIC02_TAPE - If you have a non-SCSI tape drive like that, say Y. Or, 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 <file:Documentation/modules.txt>. The module will be called - tpqic02.o. - -CONFIG_QIC02_DYNCONF - You can either configure this driver once and for all by editing a - header file (<file:include/linux/tpqic02.h>), in which case you - should say N, or you can fetch a program via anonymous FTP which is - able to configure this driver during runtime. The program to do - this is called 'qic02conf' and it is part of the - tpqic02-support-X.Y.tar.gz support package. - - If you want to use the qic02conf program, say Y. - -CONFIG_FTAPE - If you have a tape drive that is connected to your floppy - controller, say Y here. - - Some tape drives (like the Seagate "Tape Store 3200" or the Iomega - "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed" - controller of their own. These drives (and their companion - controllers) are also supported if you say Y here. - - If you have a special controller (such as the CMS FC-10, FC-20, - Mountain Mach-II, or any controller that is based on the Intel 82078 - FDC like the high speed controllers by Seagate and Exabyte and - Iomega's "Ditto Dash") you must configure it by selecting the - appropriate entries from the "Floppy tape controllers" sub-menu - below and possibly modify the default values for the IRQ and DMA - channel and the IO base in ftape's configuration menu. - - If you want to use your floppy tape drive on a PCI-bus based system, - please read the file <file:drivers/char/ftape/README.PCI>. - - The ftape kernel driver is also available as a runtime loadable - 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>. The - module will be called ftape.o. - - Note that the Ftape-HOWTO is out of date (sorry) and documents the - older version 2.08 of this software but still contains useful - information. There is a web page with more recent documentation at - <http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page - always contains the latest release of the ftape driver and useful - information (backup software, ftape related patches and - documentation, FAQ). Note that the file system interface has - changed quite a bit compared to previous versions of ftape. Please - read <file:Documentation/ftape.txt>. - -CONFIG_DTLK - This driver is for the DoubleTalk PC, a speech synthesizer - manufactured by RC Systems (<http://www.rcsys.com/>). It is also - called the `internal DoubleTalk'. 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 - <file:Documentation/modules.txt>. The module will be called dtlk.o. - -CONFIG_R3964 - This driver allows synchronous communication with devices using the - Siemens R3964 packet protocol. Unless you are dealing with special - hardware like PLCs, you are unlikely to need this. - - 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 <file:Documentation/modules.txt>. The module will be called - n_r3964.o. - - If unsure, say N. - -CONFIG_APPLICOM - This driver provides the kernel-side support for the intelligent - fieldbus cards made by Applicom International. More information - about these cards can be found on the WWW at the address - <http://www.applicom-int.com/>, or by email from David Woodhouse - <dwmw2@infradead.org>. - - 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 <file:Documentation/modules.txt>. The module will be called - applicom.o. - - If unsure, say N. - -CONFIG_SONYPI - This driver enables access to the Sony Programmable I/O Control - Device which can be found in many (all ?) Sony Vaio laptops. - - If you have one of those laptops, read - <file:Documentation/sonypi.txt>, and say Y or M 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 <file:Documentation/modules.txt>. The module - will be called sonypi.o. - -CONFIG_INTEL_RNG - This driver provides kernel-side support for the Random Number - Generator hardware found on Intel i8xx-based motherboards. - - Both a character driver, used to read() entropy data, and a timer - function which automatically adds entropy directly into the - kernel pool, are exported by this driver. - - 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 <file:Documentation/modules.txt>. The module will be called - i810_rng.o. - - If unsure, say N. - -CONFIG_AMD_RNG - This driver provides kernel-side support for the Random Number - Generator hardware found on AMD 76x based motherboards. - - Both a character driver, used to read() entropy data, and a timer - function which automatically adds entropy directly into the - kernel pool, are exported by this driver. - - 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 <file:Documentation/modules.txt>. The module will be called - amd768_rng.o. - - If unsure, say N. - -CONFIG_WATCHDOG - If you say Y here (and to one of the following options) and create a - character special file /dev/watchdog with major number 10 and minor - number 130 using mknod ("man mknod"), you will get a watchdog, i.e.: - subsequently opening the file and then failing to write to it for - longer than 1 minute will result in rebooting the machine. This - could be useful for a networked machine that needs to come back - online as fast as possible after a lock-up. There's both a watchdog - implementation entirely in software (which can sometimes fail to - reboot the machine) and a driver for hardware watchdog boards, which - are more robust and can also keep track of the temperature inside - your computer. For details, read <file:Documentation/watchdog.txt> - in the kernel source. - - The watchdog is usually used together with the watchdog daemon - which is available from - <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can - also monitor NFS connections and can reboot the machine when the process - table is full. - - If unsure, say N. - -CONFIG_WATCHDOG_NOWAYOUT - The default watchdog behaviour (which you get if you say N here) is - to stop the timer if the process managing it closes the file - /dev/watchdog. It's always remotely possible that this process might - get killed. If you say Y here, the watchdog cannot be stopped once - it has been started. - -CONFIG_WDT - If you have a WDT500P or WDT501P watchdog board, say Y here, - otherwise N. It is not possible to probe for this board, which means - that you have to inform the kernel about the IO port and IRQ using - the "wdt=" kernel option (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). - - 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 <file:Documentation/modules.txt>. The module - will be called wdt.o. - -CONFIG_WDTPCI - If you have a PCI WDT500/501 watchdog board, say Y here, otherwise - N. It is not possible to probe for this board, which means that you - have to inform the kernel about the IO port and IRQ using the "wdt=" - kernel option (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). - - 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 <file:Documentation/modules.txt>. The module - will be called wdt_pci.o. - -CONFIG_WDT_501 - Saying Y here and creating a character special file /dev/temperature - with major number 10 and minor number 131 ("man mknod") will give - you a thermometer inside your computer: reading from - /dev/temperature yields one byte, the temperature in degrees - Fahrenheit. This works only if you have a WDT501P watchdog board - installed. - -CONFIG_WDT_501_FAN - Enable the Fan Tachometer on the WDT501. Only do this if you have a - fan tachometer actually set up. - -CONFIG_SOFT_WATCHDOG - A software monitoring watchdog. This will fail to reboot your system - from some situations that the hardware watchdog will recover - from. Equally it's a lot cheaper to install. - - 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>. The module will be called - softdog.o. - -CONFIG_PCWATCHDOG - This is the driver for the Berkshire Products PC Watchdog card. - This card simply watches your kernel to make sure it doesn't freeze, - and if it does, it reboots your computer after a certain amount of - time. This driver is like the WDT501 driver but for different - hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC - watchdog cards can be ordered from <http://www.berkprod.com/>. - - 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 pcwd.o. If you want to compile it as a module, - say M here and read <file:Documentation/modules.txt>. - - Most people will say N. - -CONFIG_ACQUIRE_WDT - This is the driver for the hardware watchdog on the PSC-6x86 Single - Board Computer produced by Acquire Inc (and others). This watchdog - simply watches your kernel to make sure it doesn't freeze, and if - it does, it reboots your computer after a certain amount of time. - - This driver is like the WDT501 driver but for different hardware. - 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 pscwdt.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. Most - people will say N. - -CONFIG_ADVANTECH_WDT - If you are configuring a Linux kernel for the Advantech single-board - computer, say `Y' here to support its built-in watchdog timer - feature. See the help for CONFIG_WATCHDOG for discussion. - -CONFIG_W83877F_WDT - This is the driver for the hardware watchdog on the W83877F chipset - as used in EMACS PC-104 motherboards (and likely others). This - watchdog simply watches your kernel to make sure it doesn't freeze, - and if it does, it reboots your computer after a certain amount of - 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 is called mixcomwd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. Most - people will say N. - -CONFIG_EUROTECH_WDT - Enable support for the watchdog timer on the Eurotech CPU-1220 and - CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product - information are at <http://www.eurotech.it/>. - -CONFIG_IB700_WDT - This is the driver for the hardware watchdog on the IB700 Single - Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog - simply watches your kernel to make sure it doesn't freeze, and if - it does, it reboots your computer after a certain amount of time. - - This driver is like the WDT501 driver but for slightly different hardware. - - 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 ib700wdt.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. Most people - will say N. - -CONFIG_MIXCOMWD - This is a driver for the Mixcom hardware watchdog cards. This - watchdog simply watches your kernel to make sure it doesn't freeze, - and if it does, it reboots your computer after a certain amount of - 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 is called mixcomwd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. Most - people will say N. - -CONFIG_SCx200_WDT - Enable the built-in watchdog timer support on the National - Semiconductor SCx200 processors. - - If compiled as a module, it will be called scx200_watchdog.o. - -CONFIG_MACHZ_WDT - If you are using a ZF Micro MachZ processor, say Y here, otherwise - N. This is the driver for the watchdog timer builtin on that - processor using ZF-Logic interface. This watchdog simply watches - your kernel to make sure it doesn't freeze, and if it does, it - reboots your computer after a certain amount of 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 is called machzwd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_60XX_WDT - This driver can be used with the watchdog timer found on some - single board computers, namely the 6010 PII based computer. - It may well work with other cards. It reads port 0x443 to enable - and re-set the watchdog timer, and reads port 0x45 to disable - the watchdog. If you have a card that behave in similar ways, - you can probably make this driver work with your card as well. - - You can compile this driver directly into the kernel, or use - it as a module. The module will be called sbc60xxwdt.o. - -CONFIG_RTC - If you say Y here and create a character special file /dev/rtc with - major number 10 and minor number 135 using mknod ("man mknod"), you - will get access to the real time clock (or hardware clock) built - into your computer. - - Every PC has such a clock built in. It can be used to generate - signals from as low as 1Hz up to 8192Hz, and can also be used - as a 24 hour alarm. It reports status information via the file - /proc/driver/rtc and its behaviour is set by various ioctls on - /dev/rtc. - - If you run Linux on a multiprocessor machine and said Y to - "Symmetric Multi Processing" above, you should say Y here to read - and set the RTC in an SMP compatible fashion. - - If you think you have a use for such a device (such as periodic data - sampling), then say Y here, and read <file:Documentation/rtc.txt> - 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 is called rtc.o. If you want to compile it as a module, - say M here and read <file:Documentation/modules.txt>. - -Generic Real Time Clock Support -CONFIG_GEN_RTC - If you say Y here and create a character special file /dev/rtc with - major number 10 and minor number 135 using mknod ("man mknod"), you - will get access to the real time clock (or hardware clock) built - into your computer. - - It reports status information via the file /proc/driver/rtc and its - behaviour is set by various ioctls on /dev/rtc. If you enable the - "extended RTC operation" below it will also provide an emulation - for RTC_UIE which is required by some programs and may improve - precision in some cases. - - 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 genrtc.o. If you want to compile it as a module, - say M here and read <file:Documentation/modules.txt>. To load the - module automaticaly add 'alias char-major-10-135 genrtc' to your - /etc/modules.conf - -Extended RTC operation -CONFIG_GEN_RTC_X - Provides an emulation for RTC_UIE which is required by some programs - and may improve precision of the generic RTC support in some cases. - -CONFIG_H8 - The Hitachi H8/337 is a microcontroller used to deal with the power - and thermal environment. If you say Y here, you will be able to - communicate with it via a character special device. - - If unsure, say N. - -CONFIG_NVRAM - If you say Y here and create a character special file /dev/nvram - with major number 10 and minor number 144 using mknod ("man mknod"), - you get read and write access to the extra bytes of non-volatile - memory in the real time clock (RTC), which is contained in every PC - and most Ataris. The actual number of bytes varies, depending on the - nvram in the system, but is usually 114 (128-14 for the RTC). - - This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" - on Ataris. /dev/nvram may be used to view settings there, or to - change them (with some utility). It could also be used to frequently - save a few bits of very important data that may not be lost over - power-off and for which writing to disk is too insecure. Note - however that most NVRAM space in a PC belongs to the BIOS and you - should NEVER idly tamper with it. See Ralf Brown's interrupt list - for a guide to the use of CMOS bytes by your BIOS. - - On Atari machines, /dev/nvram is always configured and does not need - to be selected. - - 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 nvram.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_NWBUTTON - If you say Y here and create a character device node /dev/nwbutton - with major and minor numbers 10 and 158 ("man mknod"), then every - time the orange button is pressed a number of times, the number of - times the button was pressed will be written to that device. - - This is most useful for applications, as yet unwritten, which - perform actions based on how many times the button is pressed in a - row. - - Do not hold the button down for too long, as the driver does not - alter the behaviour of the hardware reset circuitry attached to the - button; it will still execute a hard reset if the button is held - down for longer than approximately five seconds. - - 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>. The module will be called - nwbutton.o. - - Most people will answer Y to this question and "Reboot Using Button" - below to be able to initiate a system shutdown from the button. - -CONFIG_NWBUTTON_REBOOT - If you say Y here, then you will be able to initiate a system - shutdown and reboot by pressing the orange button a number of times. - The number of presses to initiate the shutdown is two by default, - but this can be altered by modifying the value of NUM_PRESSES_REBOOT - in nwbutton.h and recompiling the driver or, if you compile the - driver as a module, you can specify the number of presses at load - time with "insmod button reboot_count=<something>". - -CONFIG_A2232 - This option supports the 2232 7-port serial card shipped with the - Amiga 2000 and other Zorro-bus machines, dating from 1989. At - a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip - each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The - ports were connected with 8 pin DIN connectors on the card bracket, - for which 8 pin to DB25 adapters were supplied. The card also had - jumpers internally to toggle various pinning configurations. - - This driver can be built as a module; but then "generic_serial.o" - will also be built as a module. This has to be loaded before - "ser_a2232.o". If you want to do this, answer M here and read - "<file:Documentation/modules.txt>". - -CONFIG_DS1620 - Say Y here to include support for the thermal management hardware - found in the NetWinder. This driver allows the user to control the - temperature set points and to read the current temperature. - - It is also possible to say M here to build it as a module (ds1620.o) - It is recommended to be used on a NetWinder, but it is not a - necessity. - -CONFIG_NWFLASH - If you say Y here and create a character device /dev/flash with - major 10 and minor 160 you can manipulate the flash ROM containing - the NetWinder firmware. Be careful as accidentally overwriting the - flash contents can render your computer unbootable. On no account - allow random users access to this device. :-) - - 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 nwflash.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - If you're not sure, say N. - -CONFIG_21285_WATCHDOG - The Intel Footbridge chip contains a builtin watchdog circuit. Say Y - here if you wish to use this. Alternatively say M to compile the - driver as a module, which will be called wdt285.o. - - This driver does not work on all machines. In particular, early CATS - boards have hardware problems that will cause the machine to simply - lock up if the watchdog fires. - - "If in doubt, leave it out" - say N. - -CONFIG_977_WATCHDOG - Say Y here to include support for the WB977 watchdog included in - NetWinder machines. Alternatively say M to compile the driver as - a module, which will be called wdt977.o. - - Not sure? It's safe to say N. - -CONFIG_HVC_CONSOLE - pSeries machines when partitioned support a hypervisor virtual - console. This driver allows each pSeries partition to have a console - which is accessed via the HMC. - -CONFIG_RAW_DRIVER - The raw driver permits block devices to be bound to /dev/raw/rawN. - Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. - See the raw(8) manpage for more details. - -CONFIG_SCx200_GPIO - Give userspace access to the GPIO pins on the National - Semiconductor SCx200 processors. - - If compiled as a module, it will be called scx200_gpio.o. - -Texas Instruments parallel link cable support -CONFIG_TIPAR - If you own a Texas Instruments graphing calculator and use a - parallel link cable, then you might be interested in this driver. - - If you enable this driver, you will be able to communicate with - your calculator through a set of device nodes under /dev. The - main advantage of this driver is that you don't have to be root - to use this precise link cable (depending on the permissions on - the device nodes, though). - - 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 tipar.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. - - If you don't know what a parallel link cable is or what a Texas - Instruments graphing calculator is, then you probably don't need this - driver. - - If unsure, say N.
\ No newline at end of file diff --git a/drivers/char/Config.in b/drivers/char/Config.in deleted file mode 100644 index 84eec6579e76..000000000000 --- a/drivers/char/Config.in +++ /dev/null @@ -1,202 +0,0 @@ -# -# Character device configuration -# -mainmenu_option next_comment -comment 'Character devices' - -bool 'Virtual terminal' CONFIG_VT -if [ "$CONFIG_VT" = "y" ]; then - bool ' Support for console on virtual terminal' CONFIG_VT_CONSOLE -fi -if [ "$CONFIG_VT" = "y" -a "$CONFIG_S390" != "y" -a "$CONFIG_UM" != "y" ]; then - define_bool CONFIG_HW_CONSOLE y -fi -bool 'Non-standard serial port support' CONFIG_SERIAL_NONSTANDARD -if [ "$CONFIG_SERIAL_NONSTANDARD" = "y" ]; then - tristate ' Computone IntelliPort Plus serial support' CONFIG_COMPUTONE - tristate ' Comtrol Rocketport support' CONFIG_ROCKETPORT - tristate ' Cyclades async mux support' CONFIG_CYCLADES - if [ "$CONFIG_EXPERIMENTAL" = "y" -a "$CONFIG_CYCLADES" != "n" ]; then - bool ' Cyclades-Z interrupt mode operation (EXPERIMENTAL)' CONFIG_CYZ_INTR - fi - tristate ' Digiboard Intelligent Async Support' CONFIG_DIGIEPCA - if [ "$CONFIG_DIGIEPCA" = "n" ]; then - tristate ' Digiboard PC/Xx Support' CONFIG_DIGI - fi - dep_tristate ' Hayes ESP serial port support' CONFIG_ESPSERIAL $CONFIG_ISA - tristate ' Moxa Intellio support' CONFIG_MOXA_INTELLIO - tristate ' Moxa SmartIO support' CONFIG_MOXA_SMARTIO - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' Multi-Tech multiport card support (EXPERIMENTAL)' CONFIG_ISI m - fi - tristate ' Microgate SyncLink card support' CONFIG_SYNCLINK - tristate ' SyncLink Multiport support' CONFIG_SYNCLINKMP - tristate ' HDLC line discipline support' CONFIG_N_HDLC - tristate ' SDL RISCom/8 card support' CONFIG_RISCOM8 - tristate ' Specialix IO8+ card support' CONFIG_SPECIALIX - if [ "$CONFIG_SPECIALIX" != "n" ]; then - bool ' Specialix DTR/RTS pin is RTS' CONFIG_SPECIALIX_RTSCTS - fi - tristate ' Specialix SX (and SI) card support' CONFIG_SX - tristate ' Specialix RIO system support' CONFIG_RIO - if [ "$CONFIG_RIO" != "n" ]; then - bool ' Support really old RIO/PCI cards' CONFIG_RIO_OLDPCI - fi - bool ' Stallion multiport serial support' CONFIG_STALDRV - if [ "$CONFIG_STALDRV" = "y" ]; then - tristate ' Stallion EasyIO or EC8/32 support' CONFIG_STALLION - tristate ' Stallion EC8/64, ONboard, Brumby support' CONFIG_ISTALLION - fi - if [ "$CONFIG_MIPS" = "y" ]; then - bool ' TMPTX3912/PR31700 serial port support' CONFIG_SERIAL_TX3912 - dep_bool ' Console on TMPTX3912/PR31700 serial port' CONFIG_SERIAL_TX3912_CONSOLE $CONFIG_SERIAL_TX3912 - bool ' Enable Au1000 UART Support' CONFIG_AU1000_UART - if [ "$CONFIG_AU1000_UART" = "y" ]; then - bool ' Enable Au1000 serial console' CONFIG_AU1000_SERIAL_CONSOLE - fi - fi -fi -if [ "$CONFIG_IT8712" = "y" ]; then - bool 'Enable Qtronix 990P Keyboard Support' CONFIG_QTRONIX_KEYBOARD - if [ "$CONFIG_QTRONIX_KEYBOARD" = "y" ]; then - define_bool CONFIG_IT8172_CIR y - fi - bool 'Enable Smart Card Reader 0 Support ' CONFIG_IT8172_SCR0 - bool 'Enable Smart Card Reader 1 Support ' CONFIG_IT8172_SCR1 -fi -if [ "$CONFIG_EXPERIMENTAL" = "y" -a "$CONFIG_ZORRO" = "y" ]; then - tristate 'Commodore A2232 serial support (EXPERIMENTAL)' CONFIG_A2232 -fi - -source drivers/serial/Config.in - -bool 'Unix98 PTY support' CONFIG_UNIX98_PTYS -if [ "$CONFIG_UNIX98_PTYS" = "y" ]; then - int 'Maximum number of Unix98 PTYs in use (0-2048)' CONFIG_UNIX98_PTY_COUNT 256 -fi -if [ "$CONFIG_PARPORT" != "n" ]; then - dep_tristate 'Parallel printer support' CONFIG_PRINTER $CONFIG_PARPORT - if [ "$CONFIG_PRINTER" != "n" ]; then - bool ' Support for console on line printer' CONFIG_LP_CONSOLE - fi - dep_tristate 'Support for user-space parallel port device drivers' CONFIG_PPDEV $CONFIG_PARPORT - dep_tristate 'Texas Instruments parallel link cable support' CONFIG_TIPAR $CONFIG_PARPORT -fi -if [ "$CONFIG_PPC_PSERIES" = "y" ]; then - bool 'pSeries Hypervisor Virtual Console support' CONFIG_HVC_CONSOLE -fi - -source drivers/i2c/Config.in - -mainmenu_option next_comment -comment 'Mice' - tristate 'Bus Mouse Support' CONFIG_BUSMOUSE -endmenu - -tristate 'QIC-02 tape support' CONFIG_QIC02_TAPE -if [ "$CONFIG_QIC02_TAPE" != "n" ]; then - bool ' Do you want runtime configuration for QIC-02' CONFIG_QIC02_DYNCONF - if [ "$CONFIG_QIC02_DYNCONF" != "y" ]; then - comment ' Edit configuration parameters in ./include/linux/tpqic02.h!' - else - comment ' Setting runtime QIC-02 configuration is done with qic02conf' - comment ' from the tpqic02-support package. It is available at' - comment ' metalab.unc.edu or ftp://titus.cfw.com/pub/Linux/util/' - fi -fi - -mainmenu_option next_comment -comment 'Watchdog Cards' -bool 'Watchdog Timer Support' CONFIG_WATCHDOG -if [ "$CONFIG_WATCHDOG" != "n" ]; then - bool ' Disable watchdog shutdown on close' CONFIG_WATCHDOG_NOWAYOUT - tristate ' Software watchdog' CONFIG_SOFT_WATCHDOG - tristate ' WDT Watchdog timer' CONFIG_WDT - tristate ' WDT PCI Watchdog timer' CONFIG_WDTPCI - if [ "$CONFIG_WDT" != "n" ]; then - bool ' WDT501 features' CONFIG_WDT_501 - if [ "$CONFIG_WDT_501" = "y" ]; then - bool ' Fan Tachometer' CONFIG_WDT_501_FAN - fi - fi - tristate ' Berkshire Products PC Watchdog' CONFIG_PCWATCHDOG - tristate ' Acquire SBC Watchdog Timer' CONFIG_ACQUIRE_WDT - tristate ' Advantech SBC Watchdog Timer' CONFIG_ADVANTECH_WDT - if [ "$CONFIG_FOOTBRIDGE" = "y" ]; then - tristate ' DC21285 watchdog' CONFIG_21285_WATCHDOG - if [ "$CONFIG_ARCH_NETWINDER" = "y" ]; then - tristate ' NetWinder WB83C977 watchdog' CONFIG_977_WATCHDOG - fi - fi - tristate ' Eurotech CPU-1220/1410 Watchdog Timer' CONFIG_EUROTECH_WDT - tristate ' IB700 SBC Watchdog Timer' CONFIG_IB700_WDT - tristate ' Intel i810 TCO timer / Watchdog' CONFIG_I810_TCO - tristate ' Mixcom Watchdog' CONFIG_MIXCOMWD - tristate ' NatSemi SCx200 Watchdog' CONFIG_SCx200_WDT - tristate ' SBC-60XX Watchdog Timer' CONFIG_60XX_WDT - tristate ' W83877F (EMACS) Watchdog Timer' CONFIG_W83877F_WDT - tristate ' ZF MachZ Watchdog' CONFIG_MACHZ_WDT -fi -endmenu - -if [ "$CONFIG_ARCH_NETWINDER" = "y" ]; then - tristate 'NetWinder thermometer support' CONFIG_DS1620 - tristate 'NetWinder Button' CONFIG_NWBUTTON - if [ "$CONFIG_NWBUTTON" != "n" ]; then - bool ' Reboot Using Button' CONFIG_NWBUTTON_REBOOT - fi - tristate 'NetWinder flash support' CONFIG_NWFLASH -fi - -if [ "$CONFIG_X86" = "y" -o "$CONFIG_IA64" = "y" ]; then - dep_tristate 'Intel i8x0 Random Number Generator support' CONFIG_INTEL_RNG $CONFIG_PCI -fi -if [ "$CONFIG_X86" = "y" ]; then - dep_tristate 'AMD 768 Random Number Generator support' CONFIG_AMD_RNG $CONFIG_PCI -fi -tristate '/dev/nvram support' CONFIG_NVRAM -tristate 'Enhanced Real Time Clock Support' CONFIG_RTC -if [ "$CONFIG_RTC" != "y" ]; then - tristate 'Generic /dev/rtc emulation' CONFIG_GEN_RTC - if [ "$CONFIG_GEN_RTC" != "n" ]; then - bool ' Extended RTC operation' CONFIG_GEN_RTC_X - fi -fi -if [ "$CONFIG_IA64" = "y" ]; then - bool 'EFI Real Time Clock Services' CONFIG_EFI_RTC -fi -if [ "$CONFIG_OBSOLETE" = "y" -a "$CONFIG_ALPHA_BOOK1" = "y" ]; then - bool 'Tadpole ANA H8 Support (OBSOLETE)' CONFIG_H8 -fi - -tristate 'Double Talk PC internal speech card support' CONFIG_DTLK -tristate 'Siemens R3964 line discipline' CONFIG_R3964 -tristate 'Applicom intelligent fieldbus card support' CONFIG_APPLICOM -if [ "$CONFIG_EXPERIMENTAL" = "y" -a "$CONFIG_X86" = "y" ]; then - dep_tristate 'Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)' CONFIG_SONYPI $CONFIG_PCI -fi - -mainmenu_option next_comment -comment 'Ftape, the floppy tape device driver' -tristate 'Ftape (QIC-80/Travan) support' CONFIG_FTAPE -if [ "$CONFIG_FTAPE" != "n" ]; then - source drivers/char/ftape/Config.in -fi -endmenu - -source drivers/char/agp/Config.in -source drivers/char/drm/Config.in - -if [ "$CONFIG_HOTPLUG" = "y" -a "$CONFIG_PCMCIA" != "n" ]; then - source drivers/char/pcmcia/Config.in -fi - -if [ "$CONFIG_X86" = "y" ]; then - tristate 'ACP Modem (Mwave) support' CONFIG_MWAVE -fi - -dep_tristate 'NatSemi SCx200 GPIO Support' CONFIG_SCx200_GPIO $CONFIG_SCx200 - -tristate ' RAW driver (/dev/raw/rawN)' CONFIG_RAW_DRIVER - -endmenu diff --git a/drivers/char/agp/Config.help b/drivers/char/agp/Config.help deleted file mode 100644 index b6083743dad6..000000000000 --- a/drivers/char/agp/Config.help +++ /dev/null @@ -1,88 +0,0 @@ -CONFIG_AGP - AGP (Accelerated Graphics Port) is a bus system mainly used to - connect graphics cards to the rest of the system. - - If you have an AGP system and you say Y here, it will be possible to - use the AGP features of your 3D rendering video card. This code acts - as a sort of "AGP driver" for the motherboard's chipset. - - If you need more texture memory than you can get with the AGP GART - (theoretically up to 256 MB, but in practice usually 64 or 128 MB - due to kernel allocation issues), you could use PCI accesses - and have up to a couple gigs of texture space. - - Note that this is the only means to have XFree4/GLX use - write-combining with MTRR support on the AGP bus. Without it, OpenGL - direct rendering will be a lot slower but still faster than PIO. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - - This driver is available as a module. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. The - module will be called agpgart.o. - -CONFIG_AGP_INTEL - This option gives you AGP support for the GLX component of the - XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - -CONFIG_AGP_I810 - This option gives you AGP support for the Xserver on the Intel 810 - 815 and 830m chipset boards for their on-board integrated graphics. This - is required to do any useful video modes with these boards. - -CONFIG_AGP_I460 - This option gives you AGP GART support for the Intel 460GX chipset - for IA64 processors. - -CONFIG_AGP_VIA - This option gives you AGP support for the GLX component of the - XFree86 4.x on VIA MPV3/Apollo Pro chipsets. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - -CONFIG_AGP_AMD - This option gives you AGP support for the GLX component of the - XFree86 4.x on AMD Irongate, 761, and 762 chipsets. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - -CONFIG_AGP_SIS - This option gives you AGP support for the GLX component of the "soon - to be released" XFree86 4.x on Silicon Integrated Systems [SiS] - chipsets. - - Note that 5591/5592 AGP chipsets are NOT supported. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - -CONFIG_AGP_SWORKS - Say Y here to support the Serverworks AGP card. See - <http://www.serverworks.com/> for product descriptions and images. - -CONFIG_AGP_ALI - This option gives you AGP support for the GLX component of the - XFree86 4.x on the following ALi chipsets. The supported chipsets - include M1541, M1621, M1631, M1632, M1641,M1647,and M1651. - For the ALi-chipset question, ALi suggests you refer to - <http://www.ali.com.tw/eng/support/index.shtml>. - - The M1541 chipset can do AGP 1x and 2x, but note that there is an - acknowledged incompatibility with Matrox G200 cards. Due to - timing issues, this chipset cannot do AGP 2x with the G200. - This is a hardware limitation. AGP 1x seems to be fine, though. - - You should say Y here if you use XFree86 3.3.6 or 4.x and want to - use GLX or DRI. If unsure, say N. - -CONFIG_AGP_HP_ZX1 - This option gives you AGP GART support for the HP ZX1 chipset - for IA64 processors. - - diff --git a/drivers/char/agp/Config.in b/drivers/char/agp/Config.in deleted file mode 100644 index a6c13cb4ae4c..000000000000 --- a/drivers/char/agp/Config.in +++ /dev/null @@ -1,22 +0,0 @@ - -if [ "$CONFIG_GART_IOMMU" = "y" ]; then - dep_bool '/dev/agpgart (AGP Support)' CONFIG_AGP $CONFIG_DRM_AGP -else - dep_tristate '/dev/agpgart (AGP Support)' CONFIG_AGP $CONFIG_DRM_AGP -fi -if [ "$CONFIG_AGP" != "n" ]; then - bool ' Intel 440LX/BX/GX and I815/I820/I830M/I830MP/I840/I845/I850/I860 support' CONFIG_AGP_INTEL - bool ' Intel I810/I815/I830M (on-board) support' CONFIG_AGP_I810 - bool ' VIA chipset support' CONFIG_AGP_VIA - bool ' AMD Irongate, 761, and 762 support' CONFIG_AGP_AMD - bool ' Generic SiS support' CONFIG_AGP_SIS - bool ' ALI chipset support' CONFIG_AGP_ALI - bool ' Serverworks LE/HE support' CONFIG_AGP_SWORKS - if [ "$CONFIG_GART_IOMMU" != "y" ]; then - bool ' AMD 8151 support' CONFIG_AGP_AMD_8151 - fi - if [ "$CONFIG_IA64" = "y" ]; then - bool ' Intel 460GX support' CONFIG_AGP_I460 - bool ' HP ZX1 AGP support' CONFIG_AGP_HP_ZX1 - fi -fi diff --git a/drivers/char/drm/Config.help b/drivers/char/drm/Config.help deleted file mode 100644 index 043a032ff99e..000000000000 --- a/drivers/char/drm/Config.help +++ /dev/null @@ -1,39 +0,0 @@ -CONFIG_DRM - Kernel-level support for the Direct Rendering Infrastructure (DRI) - introduced in XFree86 4.0. If you say Y here, you need to select - the module that's right for your graphics card from the list below. - These modules provide support for synchronization, security, and - DMA transfers. Please see <http://dri.sourceforge.net/> for more - details. You should also select and configure AGP - (/dev/agpgart) support. - -CONFIG_DRM_TDFX - Choose this option if you have a 3dfx Banshee or Voodoo3 (or later), - graphics card. If M is selected, the module will be called tdfx.o. - -CONFIG_DRM_GAMMA - Choose this option if you have a 3dlabs GMX 2000 graphics card. - If M is selected, the module will be called gamma.o. - -CONFIG_DRM_R128 - Choose this option if you have an ATI Rage 128 graphics card. If M - is selected, the module will be called r128.o. AGP support for - this card is strongly suggested (unless you have a PCI version). - -CONFIG_DRM_RADEON - Choose this option if you have an ATI Radeon graphics card. There - are both PCI and AGP versions. You don't need to choose this to - run the Radeon in plain VGA mode. There is a product page at - <http://www.ati.com/na/pages/products/pc/radeon32/index.html>. - If M is selected, the module will be called radeon.o. - -CONFIG_DRM_I810 - Choose this option if you have an Intel I810 graphics card. If M is - selected, the module will be called i810.o. AGP support is required - for this driver to work. - -CONFIG_DRM_MGA - Choose this option if you have a Matrox G200, G400 or G450 graphics - card. If M is selected, the module will be called mga.o. AGP - support is required for this driver to work. - diff --git a/drivers/char/drm/Config.in b/drivers/char/drm/Config.in deleted file mode 100644 index 04eb8c6f2782..000000000000 --- a/drivers/char/drm/Config.in +++ /dev/null @@ -1,17 +0,0 @@ -# -# Drm device configuration -# -# This driver provides support for the -# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher. -# - -bool 'Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)' CONFIG_DRM -if [ "$CONFIG_DRM" != "n" ]; then - tristate ' 3dfx Banshee/Voodoo3+' CONFIG_DRM_TDFX -# tristate ' 3dlabs GMX 2000' CONFIG_DRM_GAMMA - tristate ' ATI Rage 128' CONFIG_DRM_R128 - dep_tristate ' ATI Radeon' CONFIG_DRM_RADEON $CONFIG_AGP - dep_tristate ' Intel I810' CONFIG_DRM_I810 $CONFIG_AGP - dep_tristate ' Intel 830M' CONFIG_DRM_I830 $CONFIG_AGP - dep_tristate ' Matrox g200/g400' CONFIG_DRM_MGA $CONFIG_AGP -fi diff --git a/drivers/char/ftape/Config.help b/drivers/char/ftape/Config.help deleted file mode 100644 index ed0b6b4bad43..000000000000 --- a/drivers/char/ftape/Config.help +++ /dev/null @@ -1,255 +0,0 @@ -CONFIG_ZFTAPE - Normally, you want to say Y or M. DON'T say N here or you - WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE. - - The ftape module itself no longer contains the routines necessary - to interface with the kernel VFS layer (i.e. to actually write data - to and read data from the tape drive). Instead the file system - interface (i.e. the hardware independent part of the driver) has - been moved to a separate module. - - If you say M zftape will be compiled as a runtime loadable - module ( = code which can be inserted in and removed from the - running kernel whenever you want). In this case you should read - <file:Documentation/modules.txt>. The module will be called - zftape.o. - - Regardless of whether you say Y or M here, an additional runtime - loadable module called `zft-compressor.o' which contains code to - support user transparent on-the-fly compression based on Ross - William's lzrw3 algorithm will be produced. If you have enabled the - kernel module loader (i.e. have said Y to "Kernel module loader - support", above) then `zft-compressor.o' will be loaded - automatically by zftape when needed. - - Despite its name, zftape does NOT use compression by default. The - file <file:Documentation/ftape.txt> contains a short description of - the most important changes in the file system interface compared to - previous versions of ftape. The ftape home page - <http://www.instmath.rwth-aachen.de/~heine/ftape/> contains - further information. - - IMPORTANT NOTE: zftape can read archives created by previous - versions of ftape and provide file mark support (i.e. fast skipping - between tape archives) but previous version of ftape will lack file - mark support when reading archives produced by zftape. - -CONFIG_ZFT_DFLT_BLK_SZ - If unsure leave this at its default value, i.e. 10240. Note that - you specify only the default block size here. The block size can be - changed at run time using the MTSETBLK tape operation with the - MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the - shell command line). - - The probably most striking difference between zftape and previous - versions of ftape is the fact that all data must be written or read - in multiples of a fixed block size. The block size defaults to - 10240 which is what GNU tar uses. The values for the block size - should be either 1 or multiples of 1024 up to a maximum value of - 63488 (i.e. 62 K). If you specify `1' then zftape's builtin - compression will be disabled. - - Reasonable values are `10240' (GNU tar's default block size), - `5120' (afio's default block size), `32768' (default block size some - backup programs assume for SCSI tape drives) or `1' (no restriction - on block size, but disables builtin compression). - -CONFIG_FT_NR_BUFFERS - Please leave this at `3' unless you REALLY know what you are doing. - It is not necessary to change this value. Values below 3 make the - proper use of ftape impossible, values greater than 3 are a waste of - memory. You can change the amount of DMA memory used by ftape at - runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer - wastes 32 KB of memory. Please note that this memory cannot be - swapped out. - -CONFIG_FT_PROC_FS - Optional. Saying Y will result in creation of a directory - `/proc/ftape' under the /proc file system. The files can be viewed - with your favorite pager (i.e. use "more /proc/ftape/history" or - "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The - file will contain some status information about the inserted - cartridge, the kernel driver, your tape drive, the floppy disk - controller and the error history for the most recent use of the - kernel driver. Saying Y will enlarge the size of the ftape driver - by approximately 2 KB. - - WARNING: When compiling ftape as a module (i.e. saying M to "Floppy - tape drive") it is dangerous to use ftape's /proc file system - interface. Accessing `/proc/ftape' while the module is unloaded will - result in a kernel Oops. This cannot be fixed from inside ftape. - -CONFIG_FT_NORMAL_DEBUG - This option controls the amount of debugging output the ftape driver - is ABLE to produce; it does not increase or diminish the debugging - level itself. If unsure, leave this at its default setting, - i.e. choose "Normal". - - Ftape can print lots of debugging messages to the system console - resp. kernel log files. Reducing the amount of possible debugging - output reduces the size of the kernel module by some KB, so it might - be a good idea to use "None" for emergency boot floppies. - - If you want to save memory then the following strategy is - recommended: leave this option at its default setting "Normal" until - you know that the driver works as expected, afterwards reconfigure - the kernel, this time specifying "Reduced" or "None" and recompile - and install the kernel as usual. Note that choosing "Excessive" - debugging output does not increase the amount of debugging output - printed to the console but only makes it possible to produce - "Excessive" debugging output. - - Please read <file:Documentation/ftape.txt> for a short description - how to control the amount of debugging output. - -CONFIG_FT_FULL_DEBUG - Extremely verbose output for driver debugging purposes. - -CONFIG_FT_NO_TRACE - Reduced tape driver debugging output. - -CONFIG_FT_NO_TRACE_AT_ALL - Suppress all debugging output from the tape drive. - -CONFIG_FT_STD_FDC - Only change this setting if you have a special controller. If you - didn't plug any add-on card into your computer system but just - plugged the floppy tape cable into the already existing floppy drive - controller then you don't want to change the default setting, - i.e. choose "Standard". - - Choose "MACH-2" if you have a Mountain Mach-2 controller. - Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20 - controller. - Choose "Alt/82078" if you have another controller that is located at - an IO base address different from the standard floppy drive - controller's base address of `0x3f0', or uses an IRQ (interrupt) - channel different from `6', or a DMA channel different from - `2'. This is necessary for any controller card that is based on - Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high - speed" controllers. - - If you choose something other than "Standard" then please make - sure that the settings for the IO base address and the IRQ and DMA - channel in the configuration menus below are correct. Use the manual - of your tape drive to determine the correct settings! - - If you are already successfully using your tape drive with another - operating system then you definitely should use the same settings - for the IO base, the IRQ and DMA channel that have proven to work - with that other OS. - - Note that this menu lets you specify only the default setting for - the hardware setup. The hardware configuration can be changed at - boot time (when ftape is compiled into the kernel, i.e. if you - have said Y to "Floppy tape drive") or module load time (i.e. if you - have said M to "Floppy tape drive"). - - Please read also the file <file:Documentation/ftape.txt> which - contains a short description of the parameters that can be set at - boot or load time. If you want to use your floppy tape drive on a - PCI-bus based system, please read the file - <file:drivers/char/ftape/README.PCI>. - -CONFIG_FT_FDC_BASE - You don't need to specify a value if the following default - settings for the base IO address are correct: - <<< MACH-2 : 0x1E0 >>> - <<< FC-10/FC-20: 0x180 >>> - <<< Secondary : 0x370 >>> - Secondary refers to a secondary FDC controller like the "high speed" - controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address - specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR - CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already - successfully using the tape drive with another operating system then - you definitely should use the same settings for the IO base that has - proven to work with that other OS. - - Note that this menu lets you specify only the default setting for - the IO base. The hardware configuration can be changed at boot time - (when ftape is compiled into the kernel, i.e. if you specified Y to - "Floppy tape drive") or module load time (i.e. if you have said M to - "Floppy tape drive"). - - Please read also the file <file:Documentation/ftape.txt> which - contains a short description of the parameters that can be set at - boot or load time. - -CONFIG_FT_FDC_IRQ - You don't need to specify a value if the following default - settings for the interrupt channel are correct: - <<< MACH-2 : 6 >>> - <<< FC-10/FC-20: 9 >>> - <<< Secondary : 6 >>> - Secondary refers to secondary a FDC controller like the "high speed" - controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address - specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR - CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already - successfully using the tape drive with another operating system then - you definitely should use the same settings for the IO base that has - proven to work with that other OS. - - Note that this menu lets you specify only the default setting for - the IRQ channel. The hardware configuration can be changed at boot - time (when ftape is compiled into the kernel, i.e. if you said Y to - "Floppy tape drive") or module load time (i.e. if you said M to - "Floppy tape drive"). - - Please read also the file <file:Documentation/ftape.txt> which - contains a short description of the parameters that can be set at - boot or load time. - -CONFIG_FT_FDC_DMA - You don't need to specify a value if the following default - settings for the DMA channel are correct: - <<< MACH-2 : 2 >>> - <<< FC-10/FC-20: 3 >>> - <<< Secondary : 2 >>> - Secondary refers to a secondary FDC controller like the "high speed" - controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address - specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR - CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already - successfully using the tape drive with another operating system then - you definitely should use the same settings for the IO base that has - proven to work with that other OS. - - Note that this menu lets you specify only the default setting for - the DMA channel. The hardware configuration can be changed at boot - time (when ftape is compiled into the kernel, i.e. if you said Y to - "Floppy tape drive") or module load time (i.e. if you said M to - "Floppy tape drive"). - - Please read also the file <file:Documentation/ftape.txt> which - contains a short description of the parameters that can be set at - boot or load time. - -CONFIG_FT_FDC_THR - Set the FIFO threshold of the FDC. If this is higher the DMA - controller may serve the FDC after a higher latency time. If this is - lower, fewer DMA transfers occur leading to less bus contention. - You may try to tune this if ftape annoys you with "reduced data - rate because of excessive overrun errors" messages. However, this - doesn't seem to have too much effect. - - If unsure, don't touch the initial value, i.e. leave it at "8". - -CONFIG_FT_FDC_MAX_RATE - With some motherboard/FDC combinations ftape will not be able to - run your FDC/tape drive combination at the highest available - speed. If this is the case you'll encounter "reduced data rate - because of excessive overrun errors" messages and lots of retries - before ftape finally decides to reduce the data rate. - - In this case it might be desirable to tell ftape beforehand that - it need not try to run the tape drive at the highest available - speed. If unsure, leave this disabled, i.e. leave it at 2000 - bits/sec. - -CONFIG_FT_ALPHA_CLOCK - On some DEC Alpha machines the CPU clock frequency cannot be - determined automatically, so you need to specify it here ONLY if - running a DEC Alpha, otherwise this setting has no effect. - diff --git a/drivers/char/ftape/Config.in b/drivers/char/ftape/Config.in deleted file mode 100644 index 7c275b5e9133..000000000000 --- a/drivers/char/ftape/Config.in +++ /dev/null @@ -1,42 +0,0 @@ -# -# Ftape configuration -# -dep_tristate ' Zftape, the VFS interface' CONFIG_ZFTAPE $CONFIG_FTAPE -if [ "$CONFIG_ZFTAPE" != "n" ]; then - int ' Default block size' CONFIG_ZFT_DFLT_BLK_SZ 10240 - comment ' The compressor will be built as a module only!' - define_tristate CONFIG_ZFT_COMPRESSOR m -fi -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - int ' Number of ftape buffers (EXPERIMENTAL)' CONFIG_FT_NR_BUFFERS 3 -fi -if [ "$CONFIG_PROC_FS" = "y" ]; then - bool ' Enable procfs status report (+2kb)' CONFIG_FT_PROC_FS -fi -choice 'Debugging output' \ - "Normal CONFIG_FT_NORMAL_DEBUG \ - Excessive CONFIG_FT_FULL_DEBUG \ - Reduced CONFIG_FT_NO_TRACE \ - None CONFIG_FT_NO_TRACE_AT_ALL" Normal -comment 'Hardware configuration' -choice 'Floppy tape controllers' \ - "Standard CONFIG_FT_STD_FDC \ - MACH-2 CONFIG_FT_MACH2 \ - FC-10/FC-20 CONFIG_FT_PROBE_FC10 \ - Alt/82078 CONFIG_FT_ALT_FDC" Standard -if [ "$CONFIG_FT_STD_FDC" != "y" ]; then - comment ' Consult the manuals of your tape drive for the correct settings!' - hex ' IO base of the floppy disk controller' CONFIG_FT_FDC_BASE 0 - int ' IRQ channel of the floppy disk controller' CONFIG_FT_FDC_IRQ 0 - int ' DMA channel of the floppy disk controller' CONFIG_FT_FDC_DMA 0 -fi -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - int ' Default FIFO threshold (EXPERIMENTAL)' CONFIG_FT_FDC_THR 8 - int ' Maximal data rate to use (EXPERIMENTAL)' CONFIG_FT_FDC_MAX_RATE 2000 -fi - -if [ "$CONFIG_ALPHA" = "y" ]; then - int ' CPU clock frequency of your DEC Alpha' CONFIG_FT_ALPHA_CLOCK 0 -else - define_int CONFIG_FT_ALPHA_CLOCK 0 -fi diff --git a/drivers/char/pcmcia/Config.help b/drivers/char/pcmcia/Config.help deleted file mode 100644 index c1a313121ea5..000000000000 --- a/drivers/char/pcmcia/Config.help +++ /dev/null @@ -1,21 +0,0 @@ -CONFIG_PCMCIA_SERIAL_CS - Say Y here to enable support for 16-bit PCMCIA serial devices, - including serial port cards, modems, and the modem functions of - multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are - credit-card size devices often used with laptops.) - - 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 serial_cs.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_SYNCLINK_CS - Enable support for the SyncLink PC Card serial adapter, running - asynchronous and HDLC communications up to 512Kbps. The port is - selectable for RS-232, V.35, RS-449, RS-530, and X.21 - - This driver may be built as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called synclinkmp.o. If you want to do that, say M - here. diff --git a/drivers/char/pcmcia/Config.in b/drivers/char/pcmcia/Config.in deleted file mode 100644 index e44fa2a25ec8..000000000000 --- a/drivers/char/pcmcia/Config.in +++ /dev/null @@ -1,11 +0,0 @@ -# -# PCMCIA character device configuration -# - -mainmenu_option next_comment -comment 'PCMCIA character devices' - -dep_tristate 'SyncLink PC Card support' CONFIG_SYNCLINK_CS $CONFIG_PCMCIA - -endmenu - diff --git a/drivers/fc4/Config.help b/drivers/fc4/Config.help deleted file mode 100644 index 21680ce33f18..000000000000 --- a/drivers/fc4/Config.help +++ /dev/null @@ -1,57 +0,0 @@ -CONFIG_FC4 - 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. - - This is an experimental support for storage arrays connected to your - computer using optical fibre cables and the "X3.269-199X Fibre - Channel Protocol for SCSI" specification. If you want to use this, - you need to say Y here and to "SCSI support" as well as to the - drivers for the storage array itself and for the interface adapter - such as SOC or SOC+. This subsystem could even serve for IP - networking, with some code extensions. - - If unsure, say N. - -CONFIG_FC4_SOC - Serial Optical Channel is an interface card with one or two Fibre - Optic ports, each of which can be connected to a disk array. Note - that if you have older firmware in the card, you'll need the - microcode from the Solaris driver to make it work. - - This support is also available as a module called soc.o ( = 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>. - -CONFIG_FC4_SOCAL - Serial Optical Channel Plus is an interface card with up to two - Fibre Optic ports. This card supports FC Arbitrated Loop (usually - A5000 or internal FC disks in E[3-6]000 machines through the - Interface Board). You'll probably need the microcode from the - Solaris driver to make it work. - - This support is also available as a module called socal.o ( = 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>. - -CONFIG_SCSI_PLUTO - If you never bought a disk array made by Sun, go with N. - - This support is also available as a module called pluto.o ( = 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>. - -CONFIG_SCSI_FCAL - This driver drives FC-AL disks connected through a Fibre Channel - card using the drivers/fc4 layer (currently only SOCAL). The most - common is either A5000 array or internal disks in E[3-6]000 - machines. - - This support is also available as a module called fcal.o ( = 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>. If unsure, say N. - diff --git a/drivers/fc4/Config.in b/drivers/fc4/Config.in deleted file mode 100644 index cbe1990fbb48..000000000000 --- a/drivers/fc4/Config.in +++ /dev/null @@ -1,27 +0,0 @@ -# -# FC4 device configuration -# -mainmenu_option next_comment -comment 'Fibre Channel support' - -tristate 'Fibre Channel and FC4 SCSI support' CONFIG_FC4 -if [ ! "$CONFIG_FC4" = "n" ]; then - comment 'FC4 drivers' - if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - tristate 'Sun SOC/Sbus' CONFIG_FC4_SOC - tristate 'Sun SOC+ (aka SOCAL)' CONFIG_FC4_SOCAL - fi - comment 'FC4 targets' - dep_tristate 'SparcSTORAGE Array 100 and 200 series' CONFIG_SCSI_PLUTO $CONFIG_SCSI - if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - dep_tristate 'Sun Enterprise Network Array (A5000 and EX500)' CONFIG_SCSI_FCAL $CONFIG_SCSI - else - dep_tristate 'Generic FC-AL disk driver' CONFIG_SCSI_FCAL $CONFIG_SCSI - fi -else - define_tristate CONFIG_FC4_SOC n - define_tristate CONFIG_FC4_SOCAL n - define_tristate CONFIG_SCSI_PLUTO n - define_tristate CONFIG_SCSI_FCAL n -fi -endmenu diff --git a/drivers/hotplug/Config.help b/drivers/hotplug/Config.help deleted file mode 100644 index b4532b9df578..000000000000 --- a/drivers/hotplug/Config.help +++ /dev/null @@ -1,53 +0,0 @@ -CONFIG_HOTPLUG_PCI - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - - When in doubt, say N. - -CONFIG_HOTPLUG_PCI_COMPAQ - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - - When in doubt, say N. - -CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM - 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. - -CONFIG_HOTPLUG_PCI_IBM - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - - When in doubt, say N. - -CONFIG_HOTPLUG_PCI_ACPI - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - - When in doubt, say N. - diff --git a/drivers/hotplug/Config.in b/drivers/hotplug/Config.in deleted file mode 100644 index aa635da0d947..000000000000 --- a/drivers/hotplug/Config.in +++ /dev/null @@ -1,16 +0,0 @@ -# -# PCI Hotplug support -# -mainmenu_option next_comment -comment 'PCI Hotplug Support' - -dep_tristate 'Support for PCI Hotplug (EXPERIMENTAL)' CONFIG_HOTPLUG_PCI $CONFIG_PCI $CONFIG_EXPERIMENTAL - -dep_tristate ' Compaq PCI Hotplug driver' CONFIG_HOTPLUG_PCI_COMPAQ $CONFIG_HOTPLUG_PCI $CONFIG_X86 -dep_mbool ' Save configuration into NVRAM on Compaq servers' CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM $CONFIG_HOTPLUG_PCI_COMPAQ -if [ "$CONFIG_X86_IO_APIC" = "y" ]; then - dep_tristate ' IBM PCI Hotplug driver' CONFIG_HOTPLUG_PCI_IBM $CONFIG_HOTPLUG_PCI $CONFIG_X86_IO_APIC $CONFIG_X86 -fi -dep_tristate ' ACPI PCI Hotplug driver' CONFIG_HOTPLUG_PCI_ACPI $CONFIG_APCI $CONFIG_HOTPLUG_PCI - -endmenu diff --git a/drivers/i2c/Config.help b/drivers/i2c/Config.help deleted file mode 100644 index b21fce5bd96a..000000000000 --- a/drivers/i2c/Config.help +++ /dev/null @@ -1,123 +0,0 @@ -CONFIG_I2C - I2C (pronounce: I-square-C) is a slow serial bus protocol used in - many micro controller applications and developed by Philips. SMBus, - or System Management Bus is a subset of the I2C protocol. More - information is contained in the directory <file:Documentation/i2c/>, - especially in the file called "summary" there. - - Both I2C and SMBus are supported here. You will need this for - hardware sensors support, and also for Video For Linux support. - Specifically, if you want to use a BT848 based frame grabber/overlay - boards under Linux, say Y here and also to "I2C bit-banging - interfaces", below. - - If you want I2C support, you should say Y here and also to the - specific driver for your bus adapter(s) below. If you say Y to - "/proc file system" below, you will then get a /proc interface which - is documented in <file:Documentation/i2c/proc-interface>. - - This I2C support is also available as a module. If you want to - compile it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-core.o. - -CONFIG_I2C_ALGOBIT - This allows you to use a range of I2C adapters called bit-banging - adapters. Say Y if you own an I2C adapter belonging to this class - and then say Y to the specific driver for you adapter below. - - This support is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-algo-bit.o. - -CONFIG_I2C_PHILIPSPAR - This supports parallel-port I2C adapters made by Philips. Say Y if - you own such an adapter. - - This driver is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-philips-par.o. - - Note that if you want support for different parallel port devices, - life will be much easier if you compile them all as modules. - -CONFIG_I2C_ELV - This supports parallel-port I2C adapters called ELV. Say Y if you - own such an adapter. - - This driver is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-elv.o. - -CONFIG_I2C_VELLEMAN - This supports the Velleman K9000 parallel-port I2C adapter. Say Y - if you own such an adapter. - - This driver is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-velleman.o. - -CONFIG_I2C_ALGOPCF - This allows you to use a range of I2C adapters called PCF adapters. - Say Y if you own an I2C adapter belonging to this class and then say - Y to the specific driver for you adapter below. - - This support is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-algo-pcf.o. - -CONFIG_I2C_ELEKTOR - This supports the PCF8584 ISA bus I2C adapter. Say Y if you own - such an adapter. - - This driver is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-elektor.o. - -CONFIG_I2C_CHARDEV - Say Y here to use i2c-* device files, usually found in the /dev - directory on your system. They make it possible to have user-space - programs use the I2C bus. Information on how to do this is - contained in the file <file:Documentation/i2c/dev-interface>. - - This code is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called i2c-dev.o. - -CONFIG_SCx200_I2C - Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. - - If you don't know what to do here, say N. - - If compiled as a module, it will be called scx200_i2c.o. - -CONFIG_SCx200_I2C_SCL - Enter the GPIO pin number used for the SCL signal. This value can - also be specified with a module parameter. - -CONFIG_SCx200_I2C_SDA - Enter the GPIO pin number used for the SSA signal. This value can - also be specified with a module parameter. - -CONFIG_SCx200_ACB - Enable the use of the ACCESS.bus controllers of a SCx200 processor. - - If you don't know what to do here, say N. - - If compiled as a module, it will be called scx200_acb.o. - -CONFIG_I2C_PROC - This provides support for i2c device entries in the /proc filesystem. - The entries will be found in /proc/sys/dev/sensors. - - This code is also available as a module. If you want to compile - it as a module, say M here and read <file:Documentation/modules.txt>. - The module will be called i2c-proc.o. - diff --git a/drivers/i2c/Config.in b/drivers/i2c/Config.in deleted file mode 100644 index 6054a16568bc..000000000000 --- a/drivers/i2c/Config.in +++ /dev/null @@ -1,55 +0,0 @@ -# -# Character device configuration -# -mainmenu_option next_comment -comment 'I2C support' - -tristate 'I2C support' CONFIG_I2C - -if [ "$CONFIG_I2C" != "n" ]; then - - dep_tristate 'I2C bit-banging interfaces' CONFIG_I2C_ALGOBIT $CONFIG_I2C - if [ "$CONFIG_I2C_ALGOBIT" != "n" ]; then - dep_tristate ' Philips style parallel port adapter' CONFIG_I2C_PHILIPSPAR $CONFIG_I2C_ALGOBIT $CONFIG_PARPORT - dep_tristate ' ELV adapter' CONFIG_I2C_ELV $CONFIG_I2C_ALGOBIT - dep_tristate ' Velleman K9000 adapter' CONFIG_I2C_VELLEMAN $CONFIG_I2C_ALGOBIT - dep_tristate ' NatSemi SCx200 I2C using GPIO pins' CONFIG_SCx200_I2C $CONFIG_SCx200 $CONFIG_I2C_ALGOBIT - if [ "$CONFIG_SCx200_I2C" != "n" ]; then - int ' GPIO pin used for SCL' CONFIG_SCx200_I2C_SCL 12 - int ' GPIO pin used for SDA' CONFIG_SCx200_I2C_SDA 13 - fi - dep_tristate ' NatSemi SCx200 ACCESS.bus' CONFIG_SCx200_ACB $CONFIG_I2C - fi - - dep_tristate 'I2C PCF 8584 interfaces' CONFIG_I2C_ALGOPCF $CONFIG_I2C - if [ "$CONFIG_I2C_ALGOPCF" != "n" ]; then - dep_tristate ' Elektor ISA card' CONFIG_I2C_ELEKTOR $CONFIG_I2C_ALGOPCF - fi - - if [ "$CONFIG_MIPS_ITE8172" = "y" ]; then - dep_tristate 'ITE I2C Algorithm' CONFIG_ITE_I2C_ALGO $CONFIG_I2C - if [ "$CONFIG_ITE_I2C_ALGO" != "n" ]; then - dep_tristate ' ITE I2C Adapter' CONFIG_ITE_I2C_ADAP $CONFIG_ITE_I2C_ALGO - fi - fi - if [ "$CONFIG_8xx" = "y" ]; then - dep_tristate 'MPC8xx CPM I2C interface' CONFIG_I2C_ALGO8XX $CONFIG_I2C - if [ "$CONFIG_RPXLITE" = "y" -o "$CONFIG_RPXCLASSIC" = "y" ]; then - dep_tristate ' Embedded Planet RPX Lite/Classic suppoort' CONFIG_I2C_RPXLITE $CONFIG_I2C_ALGO8XX - fi - fi - if [ "$CONFIG_IBM_OCP" = "y" ]; then - dep_tristate 'IBM on-chip I2C Algorithm' CONFIG_I2C_IBM_OCP_ALGO $CONFIG_I2C - if [ "$CONFIG_I2C_IBM_OCP_ALGO" != "n" ]; then - dep_tristate ' IBM on-chip I2C Adapter' CONFIG_I2C_IBM_OCP_ADAP $CONFIG_I2C_IBM_OCP_ALGO - fi - fi - -# This is needed for automatic patch generation: sensors code starts here -# This is needed for automatic patch generation: sensors code ends here - - dep_tristate 'I2C device interface' CONFIG_I2C_CHARDEV $CONFIG_I2C - dep_tristate 'I2C /proc interface (required for hardware sensors)' CONFIG_I2C_PROC $CONFIG_I2C $CONFIG_SYSCTL - -fi -endmenu diff --git a/drivers/ide/Config.help b/drivers/ide/Config.help deleted file mode 100644 index 584859759479..000000000000 --- a/drivers/ide/Config.help +++ /dev/null @@ -1,808 +0,0 @@ -CONFIG_BLK_DEV_IDE - If you say Y here, you will use the full-featured IDE driver to - control up to ten ATA/IDE interfaces, each being able to serve a - "master" and a "slave" device, for a total of up to twenty ATA/IDE - disk/cdrom/tape/floppy drives. - - Useful information about large (>540 MB) IDE disks, multiple - interfaces, what to do if ATA/IDE devices are not automatically - detected, sound card ATA/IDE ports, module support, and other - topics, is contained in <file:Documentation/ide.txt>. For detailed - information about hard drives, consult the Disk-HOWTO and the - Multi-Disk-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - To fine-tune ATA/IDE drive/interface parameters for improved - performance, look for the hdparm package at - <ftp://ibiblio.org/pub/Linux/system/hardware/>. - - 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 <file:Documentation/modules.txt> and - <file:Documentation/ide.txt>. The module will be called ide-mod.o. - 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. - -CONFIG_BLK_DEV_HD_ONLY - 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 - <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_BLK_DEV_HD_IDE - 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. - -CONFIG_BLK_DEV_IDEDISK - 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 <file:Documentation/modules.txt>. The module - will be called ide-disk.o. 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. - -CONFIG_IDEDISK_MULTI_MODE - 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. - -CONFIG_BLK_DEV_IDECS - Support for outboard IDE disks, tape drives, and CD-ROM drives - connected through a PCMCIA card. - -CONFIG_ATAPI - If you wish to enable basic support for devices attached to the system - through the ATA interface, and which are using using the ATAPI protocol - (CD-ROM, CD-RW, DVD, DVD-RW, LS120, ZIP, ...), say Y. - - 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 <file:Documentation/modules.txt>. The module - will be called atapi.o. - -CONFIG_BLK_DEV_IDECD - 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 - <ftp://brun.dyndns.org/pub/linux/lilo/>. - - 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 <file:Documentation/modules.txt>. The module - will be called ide-cd.o. - -CONFIG_BLK_DEV_IDETAPE - If you have an IDE tape drive using the ATAPI protocol, say Y. - ATAPI is a newer protocol used by IDE tape and CD-ROM drives, - similar to the SCSI protocol. If you have an SCSI tape drive - however, you can say N here. - - You should also say Y if you have an OnStream DI-30 tape drive; this - will not work with the SCSI protocol, until there is support for the - SC-30 and SC-50 versions. - - If you say Y here, the tape drive will be identified at boot time - along with other IDE devices, as "hdb" or "hdc", or something - similar, and will be mapped to a character device such as "ht0" - (check the boot messages with dmesg). Be sure to consult the - <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files - for usage information. - - 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 <file:Documentation/modules.txt>. The module - will be called ide-tape.o. - -CONFIG_BLK_DEV_IDEFLOPPY - 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 - <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>. - (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 <file:Documentation/modules.txt>. The module - will be called ide-floppy.o. - -CONFIG_BLK_DEV_IDESCSI - 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. - -CONFIG_BLK_DEV_ISAPNP - If you have an ISA EIDE card that is PnP (Plug and Play) and - requires setup first before scanning for devices, say Y here. - - If unsure, say N. - -CONFIG_BLK_DEV_CMD640 - 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 <file:Documentation/ide.txt>. - -CONFIG_BLK_DEV_CMD640_ENHANCED - This option includes support for setting/autotuning PIO modes and - prefetch on CMD640 IDE interfaces. For details, read - <file:Documentation/ide.txt>. If you have a CMD640 IDE interface - and your BIOS does not already do this for you, then say Y here. - Otherwise say N. - -CONFIG_BLK_DEV_RZ1000 - 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. - -CONFIG_IDEPCI_SHARE_IRQ - 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. - -CONFIG_BLK_DEV_IDEDMA_PCI - 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 - <ftp://ibiblio.org/pub/Linux/system/hardware/>. - - Read the comments at the beginning of <file:drivers/ide/ide-dma.c> - and the file <file:Documentation/ide.txt> for more information. - - It is safe to say Y to this question. - -CONFIG_IDEDMA_NEW_DRIVE_LISTINGS - 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. - -CONFIG_BLK_DEV_IDE_TCQ - 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. - -CONFIG_BLK_DEV_IDE_TCQ_DEPTH - Maximum size of commands to enable per-drive. Any value between 1 - and 32 is valid, with 32 being the maxium that the hardware supports. - - You probably just want the default of 32 here. If you enter an invalid - number, the default value will be used. - -CONFIG_BLK_DEV_IDE_TCQ_DEFAULT - 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. - -CONFIG_BLK_DEV_OFFBOARD - 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. - -CONFIG_IDEDMA_PCI_AUTO - 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. - -CONFIG_IDEDMA_IVB - 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. - -CONFIG_BLK_DEV_AEC62XX - 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. - -CONFIG_AEC6280_BURST - Use burst mode for DMA transfers. This helps to achieve higher - transfer rates, but causes more load on the PCI bus. - - If unsure, say N. - -CONFIG_BLK_DEV_ALI15X3 - 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 - <file:drivers/ide/alim15x3.c>. - - If unsure, say N. - -CONFIG_WDC_ALI15X3 - 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! - -CONFIG_BLK_DEV_AMD74XX - 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. - -CONFIG_BLK_DEV_CMD64X - Say Y here if you have an IDE controller which uses any of these - chipsets: CMD643, CMD646, or CMD648. - -CONFIG_BLK_DEV_CY82C693 - 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. - -CONFIG_BLK_DEV_CS5530 - 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. - - People with SCSI-only systems should say N here. If unsure, say Y. - -CONFIG_BLK_DEV_HPT34X - 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. - -CONFIG_HPT34X_AUTODMA - This is a dangerous thing to attempt currently! Please read the - comments at the top of <file:drivers/ide/hpt34x.c>. If you say Y - here, then say Y to "Use DMA by default when available" as well. - - If unsure, say N. - -CONFIG_BLK_DEV_HPT366 - 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. - -CONFIG_BLK_DEV_NS87415 - This driver adds detection and support for the NS87415 chip - (used in SPARC64, among others). - - Please read the comments at the top of <file:drivers/ide/ns87415.c>. - -CONFIG_BLK_DEV_OPTI621 - This is a driver for the OPTi 82C621 EIDE controller. - Please read the comments at the top of <file:drivers/ide/opti621.c>. - -CONFIG_BLK_DEV_SVWKS - This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5 - chipsets. - -CONFIG_BLK_DEV_PIIX - 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. - -CONFIG_BLK_DEV_PDC202XX - 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 - <file:drivers/ide/pdc202xx.c>. - - If unsure, say N. - -CONFIG_PDC202XX_BURST - 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 - <file:drivers/ide/pdc202xx.c>. - - If unsure, say N. - -CONFIG_PDC202XX_FORCE - For FastTrak enable overriding BIOS. - -CONFIG_BLK_DEV_SIS5513 - 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 <file:drivers/ide/sis5513.c>. - -CONFIG_BLK_DEV_SL82C105 - 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. - -CONFIG_BLK_DEV_TRM290 - 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 <file:drivers/ide/trm290.c>. - -CONFIG_BLK_DEV_VIA82CXXX - 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. - -CONFIG_BLK_DEV_IDE_RAPIDE - Say Y here if you want to support the Yellowstone RapIDE controller - manufactured for use with Acorn computers. - -CONFIG_IDE_CHIPSETS - 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 <file:Documentation/ide.txt>. - - People with SCSI-only systems can say N here. - -CONFIG_BLK_DEV_ALI14XX - 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 - <file:Documentation/ide.txt> and <file:drivers/ide/ali14xx.c> for - more info. - -CONFIG_BLK_DEV_DTC2278 - 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 <file:Documentation/ide.txt> and - <file:drivers/ide/dtc2278.c> files for more info. - -CONFIG_BLK_DEV_HT6560B - 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 <file:Documentation/ide.txt> and - <file:drivers/ide/ht6560b.c> files for more info. - -CONFIG_BLK_DEV_PDC4030 - 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:drivers/ide/pdc4030.c> file for more info. - -CONFIG_BLK_DEV_QD65XX - This driver is enabled at runtime using the "ide0=qd65xx" kernel - boot parameter. It permits faster I/O speeds to be set. See the - <file:Documentation/ide.txt> and <file:drivers/ide/qd65xx.c> for - more info. - -CONFIG_BLK_DEV_UMC8672 - 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 <file:Documentation/ide.txt> and - <file:drivers/ide/umc8672.c> for more info. - -CONFIG_BLK_DEV_GAYLE - 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. - -CONFIG_BLK_DEV_FALCON_IDE - 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. - -CONFIG_BLK_DEV_BUDDHA - 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. - -CONFIG_BLK_DEV_IDEDOUBLER - 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. - -CONFIG_BLK_DEV_IDE_PMAC - This driver provides support for the built-in IDE controller on - most of the recent Apple Power Macintoshes and PowerBooks. - If unsure, say Y. - -CONFIG_BLK_DEV_IDEDMA_PMAC - 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. - -CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO - 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. - -CONFIG_BLK_DEV_MAC_IDE - 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. - -CONFIG_BLK_DEV_Q40IDE - 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. - -CONFIG_BLK_DEV_IDE_ICSIDE - 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. - -CONFIG_BLK_DEV_IDEDMA_ICS - Say Y here if you want to add DMA (Direct Memory Access) support to - the ICS IDE driver. - -CONFIG_IDEDMA_ICS_AUTO - 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! - -CONFIG_BLK_DEV_ATARAID - Say Y or M if you have an IDE Raid controller and want linux - to use its softwareraid feature. You must also select an - appropriate for your board low-level driver below. - - Note, that Linux does not use the Raid implemetation in BIOS, and - the main purpose for this feature is to retain compatibility and - data integrity with other OS-es, using the same disk array. Linux - has its own Raid drivers, which you should use if you need better - performance. - -CONFIG_BLK_DEV_ATARAID_PDC - Say Y or M if you have a Promise Fasttrak (tm) Raid controller - and want linux to use the softwareraid feature of this card. - This driver uses /dev/ataraid/dXpY (X and Y numbers) as device - names. - - If you choose to compile this as a module, the module will be called - pdcraid.o. - -CONFIG_BLK_DEV_ATARAID_HPT - Say Y or M if you have a Highpoint HPT 370 Raid controller - and want linux to use the softwareraid feature of this card. - This driver uses /dev/ataraid/dXpY (X and Y numbers) as device - names. - - If you choose to compile this as a module, the module will be called - hptraid.o. - -CONFIG_BLK_DEV_MPC8xx_IDE - This option provides support for IDE on Motorola MPC8xx Systems. - Please see 'Type of MPC8xx IDE interface' for details. - - If unsure, say N. - -CONFIG_IDE_8xx_PCCARD - Select how the IDE devices are connected to the MPC8xx system: - - 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination - with a PC Card (e.g. ARGOSY portable Hard Disk Adapter), - ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL - systems) - - 8xx_DIRECT is used for directly connected IDE devices using the 8xx - internal PCMCIA interface (example: IVMS8 systems) - - EXT_DIRECT is used for IDE devices directly connected to the 8xx - bus using some glue logic, but _not_ the 8xx internal - PCMCIA interface (example: IDIF860 systems) - -CONFIG_IDEDISK_STROKE - 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: - <http://www.storage.ibm.com/hdd/support/download.htm>. - - If you are unsure, say N here. - -CONFIG_IDEDMA_ONLYDISK - This is used if you know your ATAPI Devices are going to fail DMA - Transfers. - - Generally say N here. - -CONFIG_BLK_DEV_IDE_TCQ - 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, 120GXP, and 180GXP (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). - - However, please, note that there are host chip controllers which will - not cooperate properly if TCQ is enabled. This may cause serious - data loss! - - Since enabling TCQ doesn't appear to have any noticeable performance - impact on Linux: [feel free to correct me if you wish too please] - - Generally say N here. - -CONFIG_BLK_DEV_IDE_TCQ_DEPTH - Maximum size of commands to enable per-drive. Any value between 1 - and 32 is valid, with 32 being the maxium that the hardware supports. - - You probably just want the default of 32 here. If you enter an invalid - number, the default value will be used. - -CONFIG_BLK_DEV_IDE_TCQ_DEFAULT - Enabled 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. - -CONFIG_BLK_DEV_IT8172 - Say Y here to support the on-board IDE controller on the Integrated - Technology Express, Inc. ITE8172 SBC. Vendor page at - <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the - board at <http://www.mvista.com/allies/semiconductor/ite.html>. - -CONFIG_IT8172_TUNING - Say Y here to support tuning the ITE8172's IDE interface. This makes - it possible to set DMA channel or PIO opration and the transfer rate. - -CONFIG_IT8172_REVC - Say Y here to support the older, Revision C version of the Integrated - Technology Express, Inc. ITE8172 SBC. Vendor page at - <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the - board at <http://www.mvista.com/allies/semiconductor/ite.html>. - -CONFIG_IT8172_SCR0 - Say Y here to support smart-card reader 0 (SCR0) on the Integrated - Technology Express, Inc. ITE8172 SBC. Vendor page at - <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the - board at <http://www.mvista.com/allies/semiconductor/ite.html>. - -CONFIG_IT8172_SCR1 - Say Y here to support smart-card reader 1 (SCR1) on the Integrated - Technology Express, Inc. ITE8172 SBC. Vendor page at - <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the - board at <http://www.mvista.com/allies/semiconductor/ite.html>. - diff --git a/drivers/ide/Config.in b/drivers/ide/Config.in deleted file mode 100644 index 8ef894e663ef..000000000000 --- a/drivers/ide/Config.in +++ /dev/null @@ -1,222 +0,0 @@ -# -# IDE ATA ATAPI Block device driver configuration -# -# Andre Hedrick <andre@linux-ide.org> -# -mainmenu_option next_comment -comment 'IDE, ATA and ATAPI Block devices' - -dep_tristate 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support' CONFIG_BLK_DEV_IDE $CONFIG_IDE -comment 'Please see Documentation/ide.txt for help/info on IDE drives' -if [ "$CONFIG_BLK_DEV_IDE" != "n" ]; then - dep_bool ' Use old disk-only driver on primary interface' CONFIG_BLK_DEV_HD_IDE $CONFIG_X86 - define_bool CONFIG_BLK_DEV_HD $CONFIG_BLK_DEV_HD_IDE - - dep_tristate ' Include IDE/ATA-2 DISK support' CONFIG_BLK_DEV_IDEDISK $CONFIG_BLK_DEV_IDE - dep_mbool ' Use multi-mode by default' CONFIG_IDEDISK_MULTI_MODE $CONFIG_BLK_DEV_IDEDISK - dep_mbool ' Auto-Geometry Resizing support' CONFIG_IDEDISK_STROKE $CONFIG_BLK_DEV_IDEDISK - - dep_tristate ' PCMCIA IDE support' CONFIG_BLK_DEV_IDECS $CONFIG_BLK_DEV_IDE $CONFIG_PCMCIA - dep_tristate ' Include IDE/ATAPI CDROM support' CONFIG_BLK_DEV_IDECD $CONFIG_BLK_DEV_IDE - #dep_tristate ' Include IDE/ATAPI TAPE support' CONFIG_BLK_DEV_IDETAPE $CONFIG_BLK_DEV_IDE - dep_tristate ' Include IDE/ATAPI FLOPPY support' CONFIG_BLK_DEV_IDEFLOPPY $CONFIG_BLK_DEV_IDE - dep_tristate ' SCSI emulation support' CONFIG_BLK_DEV_IDESCSI $CONFIG_BLK_DEV_IDE $CONFIG_SCSI - - bool ' IDE Taskfile Access' CONFIG_IDE_TASK_IOCTL - #bool ' IDE Taskfile IO' CONFIG_IDE_TASKFILE_IO - - comment 'IDE chipset support/bugfixes' - if [ "$CONFIG_BLK_DEV_IDE" != "n" ]; then - dep_bool ' CMD640 chipset bugfix/support' CONFIG_BLK_DEV_CMD640 $CONFIG_X86 - dep_bool ' CMD640 enhanced support' CONFIG_BLK_DEV_CMD640_ENHANCED $CONFIG_BLK_DEV_CMD640 - dep_bool ' ISA-PNP EIDE support' CONFIG_BLK_DEV_ISAPNP $CONFIG_ISAPNP - if [ "$CONFIG_PCI" = "y" ]; then - bool ' PCI IDE chipset support' CONFIG_BLK_DEV_IDEPCI - if [ "$CONFIG_BLK_DEV_IDEPCI" = "y" ]; then - dep_bool ' Generic PCI IDE Chipset Support' CONFIG_BLK_DEV_GENERIC $CONFIG_BLK_DEV_IDEPCI - bool ' Sharing PCI IDE interrupts support' CONFIG_IDEPCI_SHARE_IRQ - bool ' Generic PCI bus-master DMA support' CONFIG_BLK_DEV_IDEDMA_PCI - dep_bool ' ATA tagged command queueing (EXPERIMENTAL)' CONFIG_BLK_DEV_IDE_TCQ $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_EXPERIMENTAL - dep_bool ' TCQ on by default' CONFIG_BLK_DEV_IDE_TCQ_DEFAULT $CONFIG_BLK_DEV_IDE_TCQ - if [ "$CONFIG_BLK_DEV_IDE_TCQ" != "n" ]; then - int ' Default queue depth' CONFIG_BLK_DEV_IDE_TCQ_DEPTH 8 - fi - bool ' Boot off-board chipsets first support' CONFIG_BLK_DEV_OFFBOARD - dep_bool ' Force enable legacy 2.0.X HOSTS to use DMA' CONFIG_BLK_DEV_IDEDMA_FORCED $CONFIG_BLK_DEV_IDEDMA_PCI - dep_bool ' Use PCI DMA by default when available' CONFIG_IDEDMA_PCI_AUTO $CONFIG_BLK_DEV_IDEDMA_PCI - dep_bool ' Enable DMA only for disks ' CONFIG_IDEDMA_ONLYDISK $CONFIG_IDEDMA_PCI_AUTO - define_bool CONFIG_BLK_DEV_IDEDMA $CONFIG_BLK_DEV_IDEDMA_PCI - dep_bool ' ATA Work(s) In Progress (EXPERIMENTAL)' CONFIG_IDEDMA_PCI_WIP $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_EXPERIMENTAL - dep_bool ' Good-Bad DMA Model-Firmware (WIP)' CONFIG_IDEDMA_NEW_DRIVE_LISTINGS $CONFIG_IDEDMA_PCI_WIP - define_bool CONFIG_BLK_DEV_ADMA $CONFIG_BLK_DEV_IDEDMA_PCI - - dep_tristate ' AEC62XX chipset support' CONFIG_BLK_DEV_AEC62XX $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' ALI M15x3 chipset support' CONFIG_BLK_DEV_ALI15X3 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_mbool ' ALI M15x3 WDC support (DANGEROUS)' CONFIG_WDC_ALI15X3 $CONFIG_BLK_DEV_ALI15X3 - dep_tristate ' AMD Viper support' CONFIG_BLK_DEV_AMD74XX $CONFIG_BLK_DEV_IDEDMA_PCI - dep_mbool ' AMD Viper ATA-66 Override' CONFIG_AMD74XX_OVERRIDE $CONFIG_BLK_DEV_AMD74XX - dep_tristate ' CMD64{3|6|8|9} chipset support' CONFIG_BLK_DEV_CMD64X $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' CY82C693 chipset support' CONFIG_BLK_DEV_CY82C693 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' Cyrix CS5530 MediaGX chipset support' CONFIG_BLK_DEV_CS5530 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' HPT34X chipset support' CONFIG_BLK_DEV_HPT34X $CONFIG_BLK_DEV_IDEDMA_PCI - dep_mbool ' HPT34X AUTODMA support (WIP)' CONFIG_HPT34X_AUTODMA $CONFIG_BLK_DEV_HPT34X $CONFIG_IDEDMA_PCI_WIP - dep_tristate ' HPT366/368/370 chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' Intel PIIXn chipsets support' CONFIG_BLK_DEV_PIIX $CONFIG_BLK_DEV_IDEDMA_PCI - if [ "$CONFIG_MIPS_ITE8172" = "y" -o "$CONFIG_MIPS_IVR" = "y" ]; then - dep_mbool ' IT8172 IDE support' CONFIG_BLK_DEV_IT8172 $CONFIG_BLK_DEV_IDEDMA_PCI - fi - dep_tristate ' nVidia NFORCE support' CONFIG_BLK_DEV_NFORCE $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' NS87415 chipset support' CONFIG_BLK_DEV_NS87415 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' OPTi 82C621 chipset enhanced support (EXPERIMENTAL)' CONFIG_BLK_DEV_OPTI621 $CONFIG_EXPERIMENTAL - dep_tristate ' PROMISE PDC202{46|62|65|67} support' CONFIG_BLK_DEV_PDC202XX_OLD $CONFIG_BLK_DEV_IDEDMA_PCI - dep_bool ' Special UDMA Feature' CONFIG_PDC202XX_BURST $CONFIG_BLK_DEV_PDC202XX_OLD $CONFI_BLK_DEV_IDEDMA_PCI - dep_tristate ' PROMISE PDC202{68|69|70|71|75|76|77} support' CONFIG_BLK_DEV_PDC202XX_NEW $CONFIG_BLK_DEV_IDEDMA_PCI - # FIXME - probably wants to be one for old and for new - dep_bool ' Special FastTrak Feature' CONFIG_PDC202XX_FORCE $CONFIG_BLK_DEV_PDC202XX_NEW - dep_tristate ' RZ1000 chipset bugfix/support' CONFIG_BLK_DEV_RZ1000 $CONFIG_X86 - dep_tristate ' ServerWorks OSB4/CSB5/CSB6 chipsets support' CONFIG_BLK_DEV_SVWKS $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' Silicon Image chipset support' CONFIG_BLK_DEV_SIIMAGE $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' SiS5513 chipset support' CONFIG_BLK_DEV_SIS5513 $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86 - dep_tristate ' SLC90E66 chipset support' CONFIG_BLK_DEV_SLC90E66 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' Tekram TRM290 chipset support' CONFIG_BLK_DEV_TRM290 $CONFIG_BLK_DEV_IDEDMA_PCI - dep_tristate ' VIA82CXXX chipset support' CONFIG_BLK_DEV_VIA82CXXX $CONFIG_BLK_DEV_IDEDMA_PCI - if [ "$CONFIG_PPC" = "y" -o "$CONFIG_ARM" = "y" ]; then - dep_tristate ' Winbond SL82c105 support' CONFIG_BLK_DEV_SL82C105 $CONFIG_BLK_DEV_IDEPCI - fi - fi - fi - if [ "$CONFIG_ALL_PPC" = "y" ]; then - bool ' Builtin PowerMac IDE support' CONFIG_BLK_DEV_IDE_PMAC - dep_bool ' PowerMac IDE DMA support' CONFIG_BLK_DEV_IDEDMA_PMAC $CONFIG_BLK_DEV_IDE_PMAC - dep_bool ' Use DMA by default' CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO $CONFIG_BLK_DEV_IDEDMA_PMAC - if [ "$CONFIG_BLK_DEV_IDE_PMAC" = "y" ]; then - define_bool CONFIG_BLK_DEV_IDEDMA $CONFIG_BLK_DEV_IDEDMA_PMAC - fi - if [ "$CONFIG_BLK_DEV_IDEDMA_PMAC" = "y" ]; then - define_bool CONFIG_BLK_DEV_IDEPCI $CONFIG_BLK_DEV_IDEDMA_PMAC - fi - fi - if [ "$CONFIG_SIBYTE_SWARM" = "y" ]; then - bool ' SWARM onboard IDE support' CONFIG_BLK_DEV_IDE_SWARM - fi - if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' ICS IDE interface support' CONFIG_BLK_DEV_IDE_ICSIDE $CONFIG_ARCH_ACORN - dep_mbool ' ICS DMA support' CONFIG_BLK_DEV_IDEDMA_ICS $CONFIG_BLK_DEV_IDE_ICSIDE - dep_mbool ' Use ICS DMA by default' CONFIG_IDEDMA_ICS_AUTO $CONFIG_BLK_DEV_IDEDMA_ICS - define_bool CONFIG_BLK_DEV_IDEDMA $CONFIG_BLK_DEV_IDEDMA_ICS - dep_tristate ' RapIDE interface support' CONFIG_BLK_DEV_IDE_RAPIDE $CONFIG_ARCH_ACORN - fi - if [ "$CONFIG_AMIGA" = "y" ]; then - dep_bool ' Amiga Gayle IDE interface support' CONFIG_BLK_DEV_GAYLE $CONFIG_AMIGA - dep_mbool ' Amiga IDE Doubler support (EXPERIMENTAL)' CONFIG_BLK_DEV_IDEDOUBLER $CONFIG_BLK_DEV_GAYLE $CONFIG_EXPERIMENTAL - fi - if [ "$CONFIG_ZORRO" = "y" -a "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_mbool ' Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)' CONFIG_BLK_DEV_BUDDHA $CONFIG_ZORRO $CONFIG_EXPERIMENTAL - fi - if [ "$CONFIG_ATARI" = "y" ]; then - dep_bool ' Falcon IDE interface support' CONFIG_BLK_DEV_FALCON_IDE $CONFIG_ATARI - fi - if [ "$CONFIG_MAC" = "y" ]; then - dep_bool ' Macintosh Quadra/Powerbook IDE interface support' CONFIG_BLK_DEV_MAC_IDE $CONFIG_MAC - fi - if [ "$CONFIG_Q40" = "y" ]; then - dep_bool ' Q40/Q60 IDE interface support' CONFIG_BLK_DEV_Q40IDE $CONFIG_Q40 - fi - if [ "$CONFIG_8xx" = "y" ]; then - dep_bool ' MPC8xx IDE support' CONFIG_BLK_DEV_MPC8xx_IDE $CONFIG_8xx - fi - - if [ "$CONFIG_BLK_DEV_MPC8xx_IDE" = "y" ]; then - choice 'Type of MPC8xx IDE interface' \ - "8xx_PCCARD CONFIG_IDE_8xx_PCCARD \ - 8xx_DIRECT CONFIG_IDE_8xx_DIRECT \ - EXT_DIRECT CONFIG_IDE_EXT_DIRECT" 8xx_PCCARD - fi - - # no isa -> no vlb - dep_bool ' Other IDE chipset support' CONFIG_IDE_CHIPSETS $CONFIG_ISA - if [ "$CONFIG_IDE_CHIPSETS" = "y" ]; then - comment 'Note: most of these also require special kernel boot parameters' - bool ' Generic 4 drives/port support' CONFIG_BLK_DEV_4DRIVES - dep_tristate ' ALI M14xx support' CONFIG_BLK_DEV_ALI14XX $CONFIG_BLK_DEV_IDE - dep_tristate ' DTC-2278 support' CONFIG_BLK_DEV_DTC2278 $CONFIG_BLK_DEV_IDE - dep_tristate ' Holtek HT6560B support' CONFIG_BLK_DEV_HT6560B $CONFIG_BLK_DEV_IDE - dep_tristate ' PROMISE DC4030 support (EXPERIMENTAL)' CONFIG_BLK_DEV_PDC4030 $CONFIG_BLK_DEV_IDEDISK $CONFIG_EXPERIMENTAL - dep_tristate ' QDI QD65xx support' CONFIG_BLK_DEV_QD65XX $CONFIG_BLK_DEV_IDE - dep_tristate ' UMC-8672 support' CONFIG_BLK_DEV_UMC8672 $CONFIG_BLK_DEV_IDE - fi - fi -else - bool 'Old hard disk (MFM/RLL/IDE) driver' CONFIG_BLK_DEV_HD_ONLY - define_bool CONFIG_BLK_DEV_HD $CONFIG_BLK_DEV_HD_ONLY -fi - -if [ "$CONFIG_IDEDMA_PCI_AUTO" = "y" -o \ - "$CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO" = "y" -o \ - "$CONFIG_IDEDMA_ICS_AUTO" = "y" ]; then - define_bool CONFIG_IDEDMA_AUTO y -else - define_bool CONFIG_IDEDMA_AUTO n -fi - -if [ "$CONFIG_BLK_DEV_IDEDMA_PCI" = "y" -o \ - "$CONFIG_BLK_DEV_IDEDMA_PMAC" = "y" -o \ - "$CONFIG_BLK_DEV_IDEDMA_ICS" = "y" ]; then - bool ' IGNORE word93 Validation BITS' CONFIG_IDEDMA_IVB -fi - -if [ "$CONFIG_BLK_DEV_TIVO" = "y" ]; then - define_bool CONFIG_DMA_NONPCI y -else - define_bool CONFIG_DMA_NONPCI n -fi - -if [ "$CONFIG_BLK_DEV_IDEDMA_PCI" = "y" ]; then - if [ "$CONFIG_BLK_DEV_PDC202XX_OLD" != "n" -o \ - "$CONFIG_BLK_DEV_PDC202XX_NEW" != "n" ]; then - define_bool CONFIG_BLK_DEV_PDC202XX y - fi -fi - -##if [ "$CONFIG_IDE_TASKFILE_IO" = "y" ]; then -## dep_mbool CONFIG_BLK_DEV_TF_DISK $CONFIG_BLK_DEV_IDEDISK -##else -## dep_mbool CONFIG_BLK_DEV_NTF_DISK $CONFIG_BLK_DEV_IDEDISK -##fi - -if [ "$CONFIG_BLK_DEV_4DRIVES" = "y" -o \ - "$CONFIG_BLK_DEV_ALI14XX" != "n" -o \ - "$CONFIG_BLK_DEV_DTC2278" != "n" -o \ - "$CONFIG_BLK_DEV_HT6560B" != "n" -o \ - "$CONFIG_BLK_DEV_PDC4030" != "n" -o \ - "$CONFIG_BLK_DEV_QD65XX" != "n" -o \ - "$CONFIG_BLK_DEV_UMC8672" != "n" -o \ - "$CONFIG_BLK_DEV_AEC62XX" = "y" -o \ - "$CONFIG_BLK_DEV_ALI15X3" = "y" -o \ - "$CONFIG_BLK_DEV_AMD74XX" = "y" -o \ - "$CONFIG_BLK_DEV_CMD640" = "y" -o \ - "$CONFIG_BLK_DEV_CMD64X" = "y" -o \ - "$CONFIG_BLK_DEV_CS5530" = "y" -o \ - "$CONFIG_BLK_DEV_CY82C693" = "y" -o \ - "$CONFIG_BLK_DEV_HPT34X" = "y" -o \ - "$CONFIG_BLK_DEV_HPT366" = "y" -o \ - "$CONFIG_BLK_DEV_IDE_PMAC" = "y" -o \ - "$CONFIG_BLK_DEV_IT8172" = "y" -o \ - "$CONFIG_BLK_DEV_MPC8xx_IDE" = "y" -o \ - "$CONFIG_BLK_DEV_NFORCE" = "y" -o \ - "$CONFIG_BLK_DEV_OPTI621" = "y" -o \ - "$CONFIG_BLK_DEV_SVWKS" = "y" -o \ - "$CONFIG_BLK_DEV_PDC202XX" = "y" -o \ - "$CONFIG_BLK_DEV_PIIX" = "y" -o \ - "$CONFIG_BLK_DEV_SVWKS" = "y" -o \ - "$CONFIG_BLK_DEV_SIIMAGE" = "y" -o \ - "$CONFIG_BLK_DEV_SIS5513" = "y" -o \ - "$CONFIG_BLK_DEV_SL82C105" = "y" -o \ - "$CONFIG_BLK_DEV_SLC90E66" = "y" -o \ - "$CONFIG_BLK_DEV_VIA82CXXX" = "y" ]; then - define_bool CONFIG_BLK_DEV_IDE_MODES y -else - define_bool CONFIG_BLK_DEV_IDE_MODES n -fi - -endmenu diff --git a/drivers/ieee1394/Config.help b/drivers/ieee1394/Config.help deleted file mode 100644 index 808b4ae2b957..000000000000 --- a/drivers/ieee1394/Config.help +++ /dev/null @@ -1,126 +0,0 @@ -CONFIG_IEEE1394 - 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 <file:Documentation/modules.txt>. The module - will be called ieee1394.o. - -CONFIG_IEEE1394_PCILYNX - 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 <file:Documentation/modules.txt>. The module - will be called pcilynx.o. - -CONFIG_IEEE1394_PCILYNX_LOCALRAM - This option makes the PCILynx driver use local RAM available on some - PCILynx setups for Packet Control Lists. Local RAM is random access - memory which resides on the PCILynx board as opposed to on your - computer's motherboard. Local RAM may speed up command processing - because no PCI transfers are necessary during use of the Packet - Control Lists. - - Note that there are no known PCILynx systems providing local RAM - except for the evaluation boards by Texas Instruments and that the - PCILynx does not reliably report missing RAM. This means that it is - dangerous to say Y here if you are not absolutely sure that your - board provides 64KB of local RAM. - - If unsure, say N. - -CONFIG_IEEE1394_PCILYNX_PORTS - This option enables driver code to access the RAM, ROM and AUX ports - of the PCILynx through character devices in /dev. If you don't know - what this is about then you won't need it. - - If unsure, say N. - -CONFIG_IEEE1394_OHCI1394 - 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 <file:Documentation/modules.txt>. The module - will be called ohci1394.o. - -CONFIG_IEEE1394_VIDEO1394 - 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. - -CONFIG_IEEE1394_DV1394 - 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 <file:Documentation/modules.txt>. The module - will be called dv1394.o. - -CONFIG_IEEE1394_SBP2 - This option enables you to use SBP-2 devices connected to your IEEE - 1394 bus. SBP-2 devices include harddrives and DVD devices. - -CONFIG_IEEE1394_RAWIO - 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 <file:Documentation/modules.txt>. The module - will be called raw1394.o. - -CONFIG_IEEE1394_ETH1394 - Extremely Experimental! This driver is a Linux specific way to use your - IEEE1394 Host as an Ethernet type device. This is _NOT_ IP1394. - -CONFIG_IEEE1394_AMDTP - 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 <file:Documentation/modules.txt>. The module - will be called amdtp.o. - -CONFIG_IEEE1394_CMP - 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 <file:Documentation/modules.txt>. The module - will be called amdtp.o. - -CONFIG_IEEE1394_VERBOSEDEBUG - 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. diff --git a/drivers/ieee1394/Config.in b/drivers/ieee1394/Config.in deleted file mode 100644 index f6d555d0080d..000000000000 --- a/drivers/ieee1394/Config.in +++ /dev/null @@ -1,45 +0,0 @@ -# -*- shell-script -*- - -if [ "$CONFIG_PCI" = "y" -a "$CONFIG_EXPERIMENTAL" = "y" ]; then - mainmenu_option next_comment - comment 'IEEE 1394 (FireWire) support (EXPERIMENTAL)' - - dep_tristate 'IEEE 1394 (FireWire) support (EXPERIMENTAL)' CONFIG_IEEE1394 $CONFIG_PCI - - if [ "$CONFIG_IEEE1394" != "n" ]; then - - comment "Device Drivers" - - if [ "$CONFIG_I2C" = "n" -o "$CONFIG_I2C_ALGOBIT" = "n" ]; then - comment ' Texas Instruments PCILynx requires I2C bit-banging' - else - dep_tristate ' Texas Instruments PCILynx support' CONFIG_IEEE1394_PCILYNX $CONFIG_IEEE1394 $CONFIG_I2C $CONFIG_I2C_ALGOBIT - fi - - # Non-maintained pcilynx options - # if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then - # bool ' Use PCILynx local RAM' CONFIG_IEEE1394_PCILYNX_LOCALRAM - # bool ' Support for non-IEEE1394 local ports' CONFIG_IEEE1394_PCILYNX_PORTS - # fi - - dep_tristate ' OHCI-1394 support' CONFIG_IEEE1394_OHCI1394 $CONFIG_IEEE1394 - - comment "Protocol Drivers" - dep_tristate ' OHCI-1394 Video support' CONFIG_IEEE1394_VIDEO1394 $CONFIG_IEEE1394_OHCI1394 - dep_tristate ' SBP-2 support (Harddisks etc.)' CONFIG_IEEE1394_SBP2 $CONFIG_SCSI $CONFIG_IEEE1394 - if [ "$CONFIG_IEEE1394_SBP2" != "n" ]; then - bool ' Enable Phys DMA support for SBP2 (Debug)' CONFIG_IEEE1394_SBP2_PHYS_DMA - fi - dep_tristate ' Ethernet over 1394' CONFIG_IEEE1394_ETH1394 $CONFIG_IEEE1394 - dep_tristate ' OHCI-DV I/O support' CONFIG_IEEE1394_DV1394 $CONFIG_IEEE1394_OHCI1394 - dep_tristate ' Raw IEEE1394 I/O support' CONFIG_IEEE1394_RAWIO $CONFIG_IEEE1394 - dep_tristate ' IEC61883-1 Plug support' CONFIG_IEEE1394_CMP $CONFIG_IEEE1394 - - if [ "$CONFIG_IEEE1394_CMP" != "n" ]; then - dep_tristate ' IEC61883-6 (Audio transmission) support' CONFIG_IEEE1394_AMDTP $CONFIG_IEEE1394_OHCI1394 $CONFIG_IEEE1394_CMP - fi - - bool 'Excessive debugging output' CONFIG_IEEE1394_VERBOSEDEBUG - fi - endmenu -fi diff --git a/drivers/input/Config.help b/drivers/input/Config.help deleted file mode 100644 index 2e3ff3acd8c9..000000000000 --- a/drivers/input/Config.help +++ /dev/null @@ -1,90 +0,0 @@ -CONFIG_INPUT - Say Y here if you have any input device (mouse, keyboard, tablet, - joystick, steering wheel ...) connected to your system and want - it to be available to applications. This includes standard PS/2 - keyboard and mouse. - - Say N here if you have a headless (no monitor, no keyboard) system. - - More information is available: <file:Documentation/input/input.txt> - - If unsure, say Y. - - 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 input.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_MOUSEDEV - Say Y here if you want your mouse to be accessible as char devices - 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an - emulated IntelliMouse Explorer PS/2 mouse. That way, all user space - programs (includung SVGAlib, GPM and X) will be able to use your - mouse. - - If unsure, say Y. - - 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 mousedev.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_MOUSEDEV_SCREEN_X - If you're using a digitizer, or a graphic tablet, and want to use - it as a mouse then the mousedev driver needs to know the X window - screen resolution you are using to correctly scale the data. If - you're not using a digitizer, this value is ignored. - -CONFIG_INPUT_MOUSEDEV_SCREEN_Y - If you're using a digitizer, or a graphic tablet, and want to use - it as a mouse then the mousedev driver needs to know the X window - screen resolution you are using to correctly scale the data. If - you're not using a digitizer, this value is ignored. - -CONFIG_INPUT_JOYDEV - Say Y here if you want your joystick or gamepad to be - accessible as char device 13:0+ - /dev/input/jsX device. - - If unsure, say Y. - - More information is available: <file:Documentation/input/joystick.txt> - - 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 joydev.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_TSDEV - Say Y here if you have an application that only can understand the - Compaq touchscreen protocol for absolute pointer data. This is - useful namely for embedded configurations. - - If unsure, 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 tsdev.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_EVDEV - Say Y here if you want your input device events be accessible - under char device 13:64+ - /dev/input/eventX in a generic way. - - 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 evdev.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_EVBUG - Say Y here if you have a problem with the input subsystem and - want all events (keypresses, mouse movements), to be output to - the system log. While this is useful for debugging, it's also - a security threat - your keypresses include your passwords, of - course. - - If unsure, 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 joydev.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/input/Config.in b/drivers/input/Config.in deleted file mode 100644 index 1b7dff514529..000000000000 --- a/drivers/input/Config.in +++ /dev/null @@ -1,40 +0,0 @@ -# -# Input device configuration -# - -mainmenu_option next_comment -comment 'Input device support' - -define_tristate CONFIG_INPUT y - -comment 'Userland interfaces' -dep_tristate ' Mouse interface' CONFIG_INPUT_MOUSEDEV $CONFIG_INPUT -dep_mbool ' Provide legacy /dev/psaux device' CONFIG_INPUT_MOUSEDEV_PSAUX $CONFIG_INPUT_MOUSEDEV -if [ "$CONFIG_INPUT_MOUSEDEV" != "n" ]; then - int ' Horizontal screen resolution' CONFIG_INPUT_MOUSEDEV_SCREEN_X 1024 - int ' Vertical screen resolution' CONFIG_INPUT_MOUSEDEV_SCREEN_Y 768 -fi -dep_tristate ' Joystick interface' CONFIG_INPUT_JOYDEV $CONFIG_INPUT -dep_tristate ' Touchscreen interface' CONFIG_INPUT_TSDEV $CONFIG_INPUT -if [ "$CONFIG_INPUT_TSDEV" != "n" ]; then - int ' Horizontal screen resolution' CONFIG_INPUT_TSDEV_SCREEN_X 240 - int ' Vertical screen resolution' CONFIG_INPUT_TSDEV_SCREEN_Y 320 -fi -dep_tristate ' Event interface' CONFIG_INPUT_EVDEV $CONFIG_INPUT -dep_tristate ' Event debugging' CONFIG_INPUT_EVBUG $CONFIG_INPUT - - -comment 'Input I/O drivers' -source drivers/input/gameport/Config.in -source drivers/input/serio/Config.in - -comment 'Input Device Drivers' -if [ "$CONFIG_INPUT" != "n" ]; then - source drivers/input/keyboard/Config.in - source drivers/input/mouse/Config.in - source drivers/input/joystick/Config.in - source drivers/input/touchscreen/Config.in - source drivers/input/misc/Config.in -fi - -endmenu diff --git a/drivers/input/gameport/Config.help b/drivers/input/gameport/Config.help deleted file mode 100644 index 2d66d4e98260..000000000000 --- a/drivers/input/gameport/Config.help +++ /dev/null @@ -1,62 +0,0 @@ -CONFIG_GAMEPORT - Gameport support is for the standard 15-pin PC gameport. If you - have a joystick, gamepad, gameport card, a soundcard with a gameport - or anything else that uses the gameport, say Y or M here and also to - at least one of the hardware specific drivers. - - For Ensoniq AudioPCI (ES1370), AudioPCI 97 (ES1371), ESS Solo1, - S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport - support is provided by the sound drivers, so you won't need any - from the below listed modules. You still need to say Y here. - - If unsure, say Y. - - 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 gameport.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GAMEPORT_NS558 - Say Y here if you have an ISA or PnP gameport. - - If unsure, say Y. - - 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 ns558.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GAMEPORT_L4 - Say Y here if you have a PDPI Lightning 4 gamecard. - - 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 lightning.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GAMEPORT_EMU10K1 - Say Y here if you have a SoundBlaster Live! or SoundBlaster - Audigy card and want to use its gameport. - - 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 emu10k1-gp.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GAMEPORT_VORTEX - Say Y here if you have an Aureal Vortex 1 or 2 card and want - to use its gameport. - - 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 vortex.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GAMEPORT_CS461X - Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion" - PCI audio accelerator and want to use its gameport. - - 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 cs461x.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/input/gameport/Config.in b/drivers/input/gameport/Config.in deleted file mode 100644 index 25e5f8bb84d4..000000000000 --- a/drivers/input/gameport/Config.in +++ /dev/null @@ -1,19 +0,0 @@ -# -# Gameport configuration -# - -tristate 'Gameport support' CONFIG_GAMEPORT - -if [ "$CONFIG_GAMEPORT" = "m" ]; then - define_tristate CONFIG_SOUND_GAMEPORT m -fi -if [ "$CONFIG_GAMEPORT" != "m" ]; then - define_tristate CONFIG_SOUND_GAMEPORT y -fi - -dep_tristate ' Classic ISA and PnP gameport support' CONFIG_GAMEPORT_NS558 $CONFIG_GAMEPORT -dep_tristate ' PDPI Lightning 4 gamecard support' CONFIG_GAMEPORT_L4 $CONFIG_GAMEPORT -dep_tristate ' SB Live and Audigy gameport support' CONFIG_GAMEPORT_EMU10K1 $CONFIG_GAMEPORT -dep_tristate ' Aureal Vortex, Vortex 2 gameport support' CONFIG_GAMEPORT_VORTEX $CONFIG_GAMEPORT -dep_tristate ' ForteMedia FM801 gameport support' CONFIG_GAMEPORT_FM801 $CONFIG_GAMEPORT -dep_tristate ' Crystal SoundFusion gameport support' CONFIG_GAMEPORT_CS461x $CONFIG_GAMEPORT diff --git a/drivers/input/joystick/Config.help b/drivers/input/joystick/Config.help deleted file mode 100644 index 0ae13e6c582e..000000000000 --- a/drivers/input/joystick/Config.help +++ /dev/null @@ -1,223 +0,0 @@ -CONFIG_INPUT_JOYSTICK - If you have a joystick, 6dof controller, gamepad, steering wheel, - weapon control system or something like that you can say Y here - and the list of supported devices will be displayed. This option - doesn't affect the kernel. - - Please read the file <file:Documentation/input/joystick.txt> which - contains more information. - -CONFIG_JOYSTICK_ANALOG - Say Y here if you have a joystick that connects to the PC - gameport. In addition to the usual PC analog joystick, this driver - supports many extensions, including joysticks with throttle control, - with rudders, additional hats and buttons compatible with CH - Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or - Saitek Cyborg joysticks. - - Please read the file <file:Documentation/input/joystick.txt> which - contains 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 analog.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_A3D - Say Y here if you have an FPGaming or MadCatz controller using the - A3D protocol over the PC gameport. - - 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 a3d.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_ADI - Say Y here if you have a Logitech controller using the ADI - protocol over the PC gameport. - - 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 adi.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_COBRA - Say Y here if you have a Creative Labs Blaster Cobra gamepad. - - 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 cobra.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_GF2K - Say Y here if you have a Genius Flight2000 or MaxFighter digitally - communicating joystick or gamepad. - - 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 gf2k.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_GRIP - Say Y here if you have a Gravis controller using the GrIP protocol - over the PC gameport. - - 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 grip.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_GRIP_MP - Say Y here if you have the original Gravis GrIP MultiPort, a hub - that connects to the gameport and you connect gamepads to it. - - 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 grip_mp.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_GUILLEMOT - Say Y here if you have a Guillemot joystick using a digital - protocol over the PC gameport. - - 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 guillemot.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_INTERACT - Say Y here if you have an InterAct gameport or joystick - communicating digitally over the gameport. - - 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 interact.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_SIDEWINDER - Say Y here if you have a Microsoft controller using the Digital - Overdrive protocol over PC gameport. - - 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 sidewinder.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_TMDC - Say Y here if you have a ThrustMaster controller using the - DirectConnect (BSP) protocol over the PC gameport. - - 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 tmdc.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_WARRIOR - Say Y here if you have a Logitech WingMan Warrior joystick connected - to your computer's serial port. - - 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 warrior.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_MAGELLAN - Say Y here if you have a Magellan or Space Mouse 6DOF controller - connected to your computer's serial port. - - 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 magellan.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_SPACEORB - Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF - controller connected to your computer's serial port. - - 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 spaceorb.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_SPACEBALL - Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX - controller connected to your computer's serial port. For the - SpaceBall 4000 USB model, use the USB HID 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 spaceball.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_STINGER - Say Y here if you have a Gravis Stinger connected to one of your - serial ports. - - 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 stinger.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_TWIDDLER - Say Y here if you have a Handykey Twiddler connected to your - computer's serial port and want to use it as a joystick. - - 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 twidjoy.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_DB9 - Say Y here if you have a Sega Master System gamepad, Sega Genesis - gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga, - Commodore, Amstrad CPC joystick connected to your parallel port. - For more information on how to use the driver please read - <file:Documentation/input/joystick-parport.txt>. - - 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 db9.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_GAMECON - Say Y here if you have a Nintendo Entertainment System gamepad, - Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad, - Sony PlayStation gamepad or a Multisystem -- Atari, Amiga, - Commodore, Amstrad CPC joystick connected to your parallel port. - For more information on how to use the driver please read - <file:Documentation/input/joystick-parport.txt>. - - 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 gamecon.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_TURBOGRAFX - Say Y here if you have the TurboGraFX interface by Steffen Schwenke, - and want to use it with Multisystem -- Atari, Amiga, Commodore, - Amstrad CPC joystick. For more information on how to use the driver - please read <file:Documentation/input/joystick-parport.txt>. - - 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 turbografx.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_AMIGA - Say Y here if you have an Amiga with a digital joystick connected - to it. - - 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 amijoy.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_JOYDUMP - Say Y here if you want to dump data from your joystick into the system - log for debugging purposes. Say N if you are making a production - configuration or aren't sure. - - 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 joydump.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/input/joystick/Config.in b/drivers/input/joystick/Config.in deleted file mode 100644 index 832387fee1a3..000000000000 --- a/drivers/input/joystick/Config.in +++ /dev/null @@ -1,34 +0,0 @@ -# -# Joystick driver configuration -# - -bool 'Joysticks' CONFIG_INPUT_JOYSTICK - -dep_tristate ' Classic PC analog joysticks and gamepads' CONFIG_JOYSTICK_ANALOG $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Assasin 3D and MadCatz Panther devices' CONFIG_JOYSTICK_A3D $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Logitech ADI digital joysticks and gamepads' CONFIG_JOYSTICK_ADI $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Creative Labs Blaster Cobra gamepad' CONFIG_JOYSTICK_COBRA $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Genius Flight2000 Digital joysticks and gamepads' CONFIG_JOYSTICK_GF2K $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Gravis GrIP joysticks and gamepads' CONFIG_JOYSTICK_GRIP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Gravis GrIP MultiPort' CONFIG_JOYSTICK_GRIP_MP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Guillemot joysticks and gamepads' CONFIG_JOYSTICK_GUILLEMOT $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' InterAct digital joysticks and gamepads' CONFIG_JOYSTICK_INTERACT $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' Microsoft SideWinder digital joysticks and gamepads' CONFIG_JOYSTICK_SIDEWINDER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -dep_tristate ' ThrustMaster DirectConnect joysticks and gamepads' CONFIG_JOYSTICK_TMDC $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT -source drivers/input/joystick/iforce/Config.in -dep_tristate ' Logitech WingMan Warrior joystick' CONFIG_JOYSTICK_WARRIOR $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO -dep_tristate ' LogiCad3d Magellan/SpaceMouse 6dof controllers' CONFIG_JOYSTICK_MAGELLAN $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO -dep_tristate ' SpaceTec SpaceOrb/Avenger 6dof controllers' CONFIG_JOYSTICK_SPACEORB $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO -dep_tristate ' SpaceTec SpaceBall 6dof controllers' CONFIG_JOYSTICK_SPACEBALL $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO -dep_tristate ' Gravis Stinger gamepad' CONFIG_JOYSTICK_STINGER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO -dep_tristate ' Twiddler as a joystick' CONFIG_JOYSTICK_TWIDDLER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO - -dep_tristate ' Multisystem, Sega Genesis, Saturn joysticks and gamepads' CONFIG_JOYSTICK_DB9 $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT -dep_tristate ' Multisystem, NES, SNES, N64, PSX joysticks and gamepads' CONFIG_JOYSTICK_GAMECON $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT -dep_tristate ' Multisystem joysticks via TurboGraFX device' CONFIG_JOYSTICK_TURBOGRAFX $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT - -if [ "$CONFIG_AMIGA" = "y" ]; then - dep_tristate ' Amiga joysticks' CONFIG_JOYSTICK_AMIGA $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK -fi - -dep_tristate ' Gameport data dumper' CONFIG_INPUT_JOYDUMP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK diff --git a/drivers/input/joystick/iforce/Config.help b/drivers/input/joystick/iforce/Config.help deleted file mode 100644 index 3b823ee357e4..000000000000 --- a/drivers/input/joystick/iforce/Config.help +++ /dev/null @@ -1,21 +0,0 @@ -CONFIG_JOYSTICK_IFORCE - Say Y here if you have an I-Force joystick or steering wheel - - You also must choose at least one of the two options 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 iforce.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_JOYSTICK_IFORCE_USB - Say Y here if you have an I-Force joystick or steering wheel - connected to your USB port. - -CONFIG_JOYSTICK_IFORCE_232 - Say Y here if you have an I-Force joystick or steering wheel - connected to your serial (COM) port. - - You will need an additional utility called inputattach, see - Documentation/input/joystick.txt and ff.txt. - diff --git a/drivers/input/joystick/iforce/Config.in b/drivers/input/joystick/iforce/Config.in deleted file mode 100644 index 13cdf88f48b6..000000000000 --- a/drivers/input/joystick/iforce/Config.in +++ /dev/null @@ -1,14 +0,0 @@ -# -# I-Force driver configuration -# - -dep_tristate ' I-Force devices' CONFIG_JOYSTICK_IFORCE $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK - -if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_JOYSTICK_IFORCE" = "y" ]; then - if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_USB" = "y" ]; then - dep_mbool ' I-Force USB joysticks and wheels' CONFIG_JOYSTICK_IFORCE_USB $CONFIG_USB - fi - if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_SERIO" = "y" ]; then - dep_mbool ' I-Force Serial joysticks and wheels' CONFIG_JOYSTICK_IFORCE_232 $CONFIG_SERIO - fi -fi diff --git a/drivers/input/keyboard/Config.help b/drivers/input/keyboard/Config.help deleted file mode 100644 index 0a318a6b2365..000000000000 --- a/drivers/input/keyboard/Config.help +++ /dev/null @@ -1,66 +0,0 @@ -CONFIG_INPUT_KEYBOARD - Say Y here, and a list of supported keyboards will be displayed. - This option doesn't affect the kernel. - - If unsure, say Y. - -CONFIG_KEYBOARD_ATKBD - Say Y here if you want to use the standard AT keyboard. Usually - you'll need this, unless you have a different type keyboard (USB, - ADB or other). This also works for AT keyboards connected over - a PS/2 to serial converter. - - If unsure, say Y. - - 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 atkbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_KEYBOARD_SUNKBD - Say Y here if you want to use a Sun Type 4 or Type 5 keyboard, - connected either to the Sun keyboard connector or to an serial - (RS-232) port via a simple 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 sunkbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_KEYBOARD_XTKBD - Say Y here if you want to use the old IBM PC/XT keyboard (or - compatible) on your system. This is only possible with a - parallel port keyboard adapter, you cannot connect it to the - keyboard port on a PC that runs Linux. - - 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 xtkbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_KEYBOARD_NEWTON - Say Y here if you have a Newton keyboard on a serial port. - - 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 maple_keyb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_KEYBOARD_MAPLE - Say Y here if you have a DreamCast console running Linux and have - a keyboard attached to its Maple bus. - - 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 maple_keyb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_KEYBOARD_AMIGA - Say Y here if you are running Linux on any AMIGA and have a keyboard - attached. - - 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 amikbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - diff --git a/drivers/input/keyboard/Config.in b/drivers/input/keyboard/Config.in deleted file mode 100644 index 81138e1fe206..000000000000 --- a/drivers/input/keyboard/Config.in +++ /dev/null @@ -1,18 +0,0 @@ -# -# Input core configuration -# - -bool 'Keyboards' CONFIG_INPUT_KEYBOARD - -dep_tristate ' AT keyboard support' CONFIG_KEYBOARD_ATKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO -dep_tristate ' Sun Type 4 and Type 5 keyboard support' CONFIG_KEYBOARD_SUNKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO -dep_tristate ' XT Keyboard support' CONFIG_KEYBOARD_XTKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO -dep_tristate ' Newton keyboard' CONFIG_KEYBOARD_NEWTON $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO - -if [ "$CONFIG_SH_DREAMCAST" = "y" ]; then - dep_tristate ' Maple bus keyboard support' CONFIG_KEYBOARD_MAPLE $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_MAPLE -fi - -if [ "$CONFIG_AMIGA" = "y" ]; then - dep_tristate ' Amiga keyboard' CONFIG_KEYBOARD_AMIGA $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD -fi diff --git a/drivers/input/misc/Config.help b/drivers/input/misc/Config.help deleted file mode 100644 index b03e459be96d..000000000000 --- a/drivers/input/misc/Config.help +++ /dev/null @@ -1,39 +0,0 @@ -CONFIG_INPUT_MISC - - Say Y here, and a list of miscellaneous input drivers will be displayed. - Everything that didn't fit into the other categories is here. This option - doesn't affect the kernel. - - If unsure, say Y. - -CONFIG_INPUT_PCSPKR - Say Y here if you want the standard PC Speaker to be used for - bells and whistles. - - If unsure, say Y. - - 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 pcspkr.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_INPUT_SPARCSPKR - Say Y here if you want the standard Speaker on Sparc PCI systems - to be used for bells and whistles. - - If unsure, say Y. - - 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 pcspkr.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - -CONFIG_INPUT_UINPUT - Say Y here if you want to support user level drivers for input - subsystem accessible under char device 10:223 - /dev/input/uinput. - - 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 uinput.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/input/misc/Config.in b/drivers/input/misc/Config.in deleted file mode 100644 index af844186945d..000000000000 --- a/drivers/input/misc/Config.in +++ /dev/null @@ -1,14 +0,0 @@ -# -# Input misc drivers configuration -# - -bool 'Misc' CONFIG_INPUT_MISC - -dep_tristate ' PC Speaker support' CONFIG_INPUT_PCSPKR $CONFIG_INPUT $CONFIG_INPUT_MISC -if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - dep_tristate ' SPARC Speaker support' CONFIG_INPUT_SPARCSPKR $CONFIG_INPUT $CONFIG_INPUT_MISC -fi -if [ "$CONFIG_M68K" = "y" ]; then -dep_tristate ' M68k Beeper support' CONFIG_INPUT_M68K_BEEP $CONFIG_INPUT $CONFIG_INPUT_MISC -fi -dep_tristate ' User level driver support' CONFIG_INPUT_UINPUT $CONFIG_INPUT $CONFIG_INPUT_MISC diff --git a/drivers/input/mouse/Config.help b/drivers/input/mouse/Config.help deleted file mode 100644 index c5b191e2c0eb..000000000000 --- a/drivers/input/mouse/Config.help +++ /dev/null @@ -1,87 +0,0 @@ -CONFIG_INPUT_MOUSE - Say Y here, and a list of supported mice will be displayed. - This option doesn't affect the kernel. - - If unsure, say Y. - -CONFIG_MOUSE_PS2 - Say Y here if you have a PS/2 mouse connected to your system. This - includes the standard 2 or 3-button PS/2 mouse, as well as PS/2 - mice with wheels and extra buttons, Microsoft, Logitech or Genius - compatible. - - If unsure, say Y. - - 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 psmouse.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MOUSE_SERIAL - Say Y here if you have a serial (RS-232, COM port) mouse connected - to your system. This includes Sun, MouseSystems, Microsoft, - Logitech and all other compatible serial mice. - - If unsure, 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 sermouse.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MOUSE_INPORT - Say Y here if you have an InPort, Microsoft or ATI XL busmouse. - They are rather rare these days. - - 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 inport.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. - -CONFIG_MOUSE_ATIXL - Say Y here if your mouse is of the ATI XL variety. - -CONFIG_MOUSE_LOGIBM - Say Y here if you have a Logitech busmouse. - They are rather rare these days. - - 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 logibm.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. - -CONFIG_MOUSE_PC110PAD - Say Y if you have the IBM PC-110 micro-notebook and want its - touchpad supported. - - 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 pc110pad.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. - -CONFIG_MOUSE_MAPLE - Say Y if you have a DreamCast console and a mouse attached to - its Maple bus. - - 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 maplemouse.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. - -CONFIG_MOUSE_AMIGA - Say Y here if you have an Amiga and want its native mouse - supported by 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 will be called amimouse.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. - -CONFIG_MOUSE_ACORN - Say Y here if you have the Acorn RiscPC computer and want its - native mouse supported. - - 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 rpcmouse.o. If you want to compile it as a - module, say M here and read <file.:Documentation/modules.txt>. diff --git a/drivers/input/mouse/Config.in b/drivers/input/mouse/Config.in deleted file mode 100644 index d740c4188ebd..000000000000 --- a/drivers/input/mouse/Config.in +++ /dev/null @@ -1,24 +0,0 @@ -# -# Mouse driver configuration -# - -bool 'Mice' CONFIG_INPUT_MOUSE - -dep_tristate ' PS/2 mouse' CONFIG_MOUSE_PS2 $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_SERIO -dep_tristate ' Serial mouse' CONFIG_MOUSE_SERIAL $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_SERIO - -dep_tristate ' InPort/MS/ATIXL busmouse' CONFIG_MOUSE_INPORT $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA -if [ "$CONFIG_MOUSE_INPORT" != "n" ]; then - bool ' ATI XL variant' CONFIG_MOUSE_ATIXL -fi -dep_tristate ' Logitech busmouse' CONFIG_MOUSE_LOGIBM $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA -dep_tristate ' IBM PC110 touchpad' CONFIG_MOUSE_PC110PAD $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA -if [ "$CONFIG_SH_DREAMCAST" = "y" ]; then - dep_tristate ' Maple bus mouse' CONFIG_MOUSE_MAPLE $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_MAPLE -fi -if [ "$CONFIG_AMIGA" = "y" ]; then - dep_tristate ' Amiga mouse' CONFIG_MOUSE_AMIGA $CONFIG_INPUT $CONFIG_INPUT_MOUSE -fi -if [ "$CONFIG_ARCH_ACORN" = "y" ]; then - dep_tristate ' Acorn RiscPC mouse' CONFIG_MOUSE_ACORN $CONFIG_INPUT $CONFIG_INPUT_MOUSE -fi diff --git a/drivers/input/serio/Config.help b/drivers/input/serio/Config.help deleted file mode 100644 index ae97e4223fc0..000000000000 --- a/drivers/input/serio/Config.help +++ /dev/null @@ -1,73 +0,0 @@ -CONFIG_SERIO - Say Yes here if you have any input device that uses serial I/O to - communicate with the system. This includes the - * standard AT keyboard and PS/2 mouse * - as well as serial mice, Sun keyboards, some joysticks and 6dof - devices and more. - - If unsure, say Y. - - 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 serio.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SERIO_I8042 - i8042 is the chip over which the standard AT keyboard and PS/2 - mouse are connected to the computer. If you use these devices, - you'll need to say Y here. - - If unsure, say Y. - - 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 i8042.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SERIO_SERPORT - Say Y here if you plan to use an input device (mouse, joystick, - tablet, 6dof) that communicates over the RS232 serial (COM) port. - - More information is available: <file:Documentation/input/input.txt> - - If unsure, say Y. - - 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 serport.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SERIO_CT82C710 - Say Y here if you have a Texas Instruments TravelMate notebook - equipped with the ct82c710 chip and want to use a mouse connected - to the "QuickPort". - - If unsure, 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 ct82c710.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SERIO_PARKBD - Say Y here if you built a simple parallel port adapter to attach - an additional AT keyboard, XT keyboard or PS/2 mouse. - - More information is available: <file:Documentation/input/input.txt> - - If unsure, 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 parkbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SERIO_ACORN - Say Y here if you have the Acorn RiscPC and want to use an AT - keyboard connected to its keyboard controller. - - 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 rpckbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - diff --git a/drivers/input/serio/Config.in b/drivers/input/serio/Config.in deleted file mode 100644 index 919740e1fc0d..000000000000 --- a/drivers/input/serio/Config.in +++ /dev/null @@ -1,23 +0,0 @@ -# -# Input core configuration -# - -tristate 'Serial i/o support' CONFIG_SERIO - -dep_tristate ' i8042 PC Keyboard controller' CONFIG_SERIO_I8042 $CONFIG_SERIO -dep_tristate ' Serial port line discipline' CONFIG_SERIO_SERPORT $CONFIG_SERIO -dep_tristate ' ct82c710 Aux port controller' CONFIG_SERIO_CT82C710 $CONFIG_SERIO -if [ "$CONFIG_Q40" = "y" ]; then - dep_tristate ' Q40 keyboard controller' CONFIG_SERIO_Q40KBD $CONFIG_SERIO -fi -dep_tristate ' Parallel port keyboard adapter' CONFIG_SERIO_PARKBD $CONFIG_SERIO $CONFIG_PARPORT - -if [ "$CONFIG_ARCH_ACORN" = "y" ]; then - dep_tristate ' Acorn RiscPC keyboard controller' CONFIG_SERIO_ACORN $CONFIG_SERIO -fi -if [ "$CONFIG_ARCH_INTEGRATOR" = "y" ]; then - dep_tristate ' AMBA KMI keyboard controller' CONFIG_SERIO_AMBAKMI $CONFIG_SERIO -fi -if [ "$CONFIG_SA1111" = "y" ]; then - dep_tristate ' Intel SA1111 keyboard controller' CONFIG_SERIO_SA1111 $CONFIG_SERIO -fi diff --git a/drivers/input/touchscreen/Config.help b/drivers/input/touchscreen/Config.help deleted file mode 100644 index 4a8c1b7809eb..000000000000 --- a/drivers/input/touchscreen/Config.help +++ /dev/null @@ -1,26 +0,0 @@ -CONFIG_INPUT_TOUCHSCREEN - Say Y here, and a list of supported touchscreens will be displayed. - This option doesn't affect the kernel. - - If unsure, say Y. - -CONFIG_TOUCHSCREEN_GUNZE - Say Y here if you have the Gunze AHL-51 touchscreen connected to - your system. - - If unsure, 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 gunze.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_TOUCHSCREEN_BITSY - Say Y here if you have the h3600 (Bitsy) touchscreen. - - If unsure, 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 gunze.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/input/touchscreen/Config.in b/drivers/input/touchscreen/Config.in deleted file mode 100644 index 7e441d44e1e1..000000000000 --- a/drivers/input/touchscreen/Config.in +++ /dev/null @@ -1,10 +0,0 @@ -# -# Mouse driver configuration -# - -bool 'Touchscreens' CONFIG_INPUT_TOUCHSCREEN - -if [ "$CONFIG_SA1100_BITSY" = "y" ]; then - dep_tristate ' Compaq iPAQ H3600 (Bitsy) touchscreen input driver' CONFIG_TOUCHSCREEN_BITSY $CONFIG_INPUT $CONFIG_INPUT_TOUCHSCREEN $CONFIG_SERIO -fi -dep_tristate ' Gunze AHL-51S touchscreen' CONFIG_TOUCHSCREEN_GUNZE $CONFIG_INPUT $CONFIG_INPUT_TOUCHSCREEN $CONFIG_SERIO diff --git a/drivers/isdn/Config.help b/drivers/isdn/Config.help deleted file mode 100644 index 94fc7845b6ed..000000000000 --- a/drivers/isdn/Config.help +++ /dev/null @@ -1,13 +0,0 @@ -CONFIG_ISDN_BOOL - 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 <http://alumni.caltech.edu/~dank/isdn/> on the WWW. - - Select this option if you want your kernel to support ISDN. - diff --git a/drivers/isdn/Config.in b/drivers/isdn/Config.in deleted file mode 100644 index 46f177450d2f..000000000000 --- a/drivers/isdn/Config.in +++ /dev/null @@ -1,31 +0,0 @@ -# -# ISDN device configuration -# - -mainmenu_option next_comment -comment 'ISDN subsystem' -if [ "$CONFIG_NET" != "n" ]; then - bool 'ISDN support' CONFIG_ISDN_BOOL - - if [ "$CONFIG_ISDN_BOOL" = "y" ]; then - mainmenu_option next_comment - comment 'Old ISDN4Linux' - - tristate 'Old ISDN4Linux (obsolete)' CONFIG_ISDN - if [ "$CONFIG_ISDN" != "n" ]; then - source drivers/isdn/i4l/Config.in - fi - endmenu - - comment 'CAPI subsystem' - - tristate 'CAPI2.0 support' CONFIG_ISDN_CAPI - if [ "$CONFIG_ISDN_CAPI" != "n" ]; then - source drivers/isdn/capi/Config.in - fi - - source drivers/isdn/hardware/Config.in - fi -fi -endmenu - diff --git a/drivers/isdn/act2000/Config.help b/drivers/isdn/act2000/Config.help deleted file mode 100644 index 1798d313f191..000000000000 --- a/drivers/isdn/act2000/Config.help +++ /dev/null @@ -1,7 +0,0 @@ -CONFIG_ISDN_DRV_ACT2000 - Say Y here if you have an IBM Active 2000 ISDN card. In order to use - this card, additional firmware is necessary, which has to be loaded - into the card using a utility which is part of the latest - isdn4k-utils package. Please read the file - <file:Documentation/isdn/README.act2000> for more information. - diff --git a/drivers/isdn/act2000/Config.in b/drivers/isdn/act2000/Config.in deleted file mode 100644 index 78159f9e070e..000000000000 --- a/drivers/isdn/act2000/Config.in +++ /dev/null @@ -1,6 +0,0 @@ -# -# Config.in for IBM Active 2000 ISDN driver -# - -dep_tristate 'IBM Active 2000 support' CONFIG_ISDN_DRV_ACT2000 $CONFIG_ISDN $CONFIG_ISA - diff --git a/drivers/isdn/capi/Config.help b/drivers/isdn/capi/Config.help deleted file mode 100644 index 079f4b935c2c..000000000000 --- a/drivers/isdn/capi/Config.help +++ /dev/null @@ -1,31 +0,0 @@ -CONFIG_ISDN_CAPI - This provides the CAPI (Common ISDN Application Programming - Interface, a standard making it easy for programs to access ISDN - hardware, see <http://www.capi.org/>. This is needed for AVM's set - of active ISDN controllers like B1, T1, M1. - -CONFIG_ISDN_CAPI_CAPI20 - 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. - -CONFIG_ISDN_CAPI_MIDDLEWARE - 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. - -CONFIG_ISDN_CAPI_CAPIFS - 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. - -CONFIG_ISDN_CAPI_CAPIDRV - 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. - diff --git a/drivers/isdn/capi/Config.in b/drivers/isdn/capi/Config.in deleted file mode 100644 index 870024d2d42d..000000000000 --- a/drivers/isdn/capi/Config.in +++ /dev/null @@ -1,16 +0,0 @@ -# -# Config.in for the CAPI subsystem -# - -bool ' Verbose reason code reporting (kernel size +=7K)' CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON -dep_bool ' CAPI2.0 Middleware support (EXPERIMENTAL)' CONFIG_ISDN_CAPI_MIDDLEWARE $CONFIG_EXPERIMENTAL -dep_tristate ' CAPI2.0 /dev/capi support' CONFIG_ISDN_CAPI_CAPI20 $CONFIG_ISDN_CAPI -if [ "$CONFIG_ISDN_CAPI_MIDDLEWARE" = "y" ]; then - dep_mbool ' CAPI2.0 filesystem support' CONFIG_ISDN_CAPI_CAPIFS_BOOL $CONFIG_ISDN_CAPI_CAPI20 - if [ "$CONFIG_ISDN_CAPI_CAPIFS_BOOL" = "y" ]; then - define_tristate CONFIG_ISDN_CAPI_CAPIFS $CONFIG_ISDN_CAPI_CAPI20 - else - define_tristate CONFIG_ISDN_CAPI_CAPIFS n - fi -fi -dep_tristate ' CAPI2.0 capidrv interface support' CONFIG_ISDN_CAPI_CAPIDRV $CONFIG_ISDN_CAPI $CONFIG_ISDN diff --git a/drivers/isdn/eicon/Config.help b/drivers/isdn/eicon/Config.help deleted file mode 100644 index 2eed402e0db3..000000000000 --- a/drivers/isdn/eicon/Config.help +++ /dev/null @@ -1,30 +0,0 @@ -CONFIG_ISDN_DRV_EICON - Say Y here if you have an Eicon active ISDN card. In order to use - this card, additional firmware is necessary, which has to be loaded - into the card using the eiconctrl utility which is part of the - latest isdn4k-utils package. Please read the file - <file:Documentation/isdn/README.eicon> for more information. - -CONFIG_ISDN_DRV_EICON_OLD - Say Y here to use your Eicon active ISDN card with ISDN4Linux - isdn module. - -CONFIG_ISDN_DRV_EICON_PCI - Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN - card. Please read <file:Documentation/isdn/README.eicon> for more - information. - -CONFIG_ISDN_DRV_EICON_ISA - Say Y here if you have an old-type Eicon active ISDN card. In order - to use this card, additional firmware is necessary, which has to be - loaded into the card using the eiconctrl utility which is part of - the latest isdn4k-utils package. Please read the file - <file:Documentation/isdn/README.eicon> for more information. - -CONFIG_ISDN_DRV_EICON_DIVAS - Enable this option if you want the eicon driver as standalone - version with no interface to the ISDN4Linux isdn module. If you - say Y here, the eicon module only supports the Diva Server PCI - cards and will provide its own IDI interface. You should say N - here. - diff --git a/drivers/isdn/eicon/Config.in b/drivers/isdn/eicon/Config.in deleted file mode 100644 index 0654c1c74081..000000000000 --- a/drivers/isdn/eicon/Config.in +++ /dev/null @@ -1,20 +0,0 @@ -# -# Config.in for Eicon active ISDN support -# - -bool 'Eicon active card support' CONFIG_ISDN_DRV_EICON -if [ "$CONFIG_ISDN_DRV_EICON" != "n" ]; then - - if [ "$CONFIG_ISDN_DRV_EICON_OLD" != "y" ]; then - dep_tristate ' Build Eicon driver type standalone' CONFIG_ISDN_DRV_EICON_DIVAS $CONFIG_ISDN $CONFIG_PCI - fi - if [ "$CONFIG_ISDN_DRV_EICON_DIVAS" != "y" ]; then - dep_tristate ' Legacy Eicon driver' CONFIG_ISDN_DRV_EICON_OLD $CONFIG_ISDN - if [ "$CONFIG_ISDN_DRV_EICON_OLD" != "n" ]; then - dep_bool ' Eicon PCI DIVA Server BRI/PRI/4BRI support' CONFIG_ISDN_DRV_EICON_PCI $CONFIG_PCI - bool ' Eicon S,SX,SCOM,Quadro,S2M support' CONFIG_ISDN_DRV_EICON_ISA - fi - - fi -fi - diff --git a/drivers/isdn/hardware/Config.in b/drivers/isdn/hardware/Config.in deleted file mode 100644 index 10b4e88ec1e3..000000000000 --- a/drivers/isdn/hardware/Config.in +++ /dev/null @@ -1,28 +0,0 @@ -# -# ISDN hardware drivers -# - -if [ "$CONFIG_ISDN_CAPI" != "n" ]; then - comment 'CAPI hardware drivers' - source drivers/isdn/hardware/avm/Config.in - source drivers/isdn/hardware/eicon/Config.in -fi - -if [ "$CONFIG_ISDN" != "n" ]; then - comment 'ISDN4Linux hardware drivers' - - source drivers/isdn/hisax/Config.in - - mainmenu_option next_comment - comment 'Active cards' - - source drivers/isdn/icn/Config.in - source drivers/isdn/pcbit/Config.in - source drivers/isdn/sc/Config.in - source drivers/isdn/act2000/Config.in - source drivers/isdn/eicon/Config.in - source drivers/isdn/tpam/Config.in - source drivers/isdn/hysdn/Config.in - endmenu -fi - diff --git a/drivers/isdn/hardware/avm/Config.help b/drivers/isdn/hardware/avm/Config.help deleted file mode 100644 index 2a8ed7f03236..000000000000 --- a/drivers/isdn/hardware/avm/Config.help +++ /dev/null @@ -1,36 +0,0 @@ -CONFIG_CAPI_AVM - Enable support for AVM active ISDN cards. - -CONFIG_ISDN_DRV_AVMB1_B1ISA - Enable support for the ISA version of the AVM B1 card. - -CONFIG_ISDN_DRV_AVMB1_B1PCI - Enable support for the PCI version of the AVM B1 card. - -CONFIG_ISDN_DRV_AVMB1_B1PCIV4 - Enable support for the V4 version of AVM B1 PCI card. - -CONFIG_ISDN_DRV_AVMB1_T1ISA - Enable support for the AVM T1 T1B card. - Note: This is a PRI card and handle 30 B-channels. - -CONFIG_ISDN_DRV_AVMB1_B1PCMCIA - Enable support for the PCMCIA version of the AVM B1 card. - -CONFIG_ISDN_DRV_AVMB1_AVM_CS - Enable the PCMCIA client driver for the AVM B1/M1/M2 - PCMCIA cards. - -CONFIG_ISDN_DRV_AVMB1_T1PCI - Enable support for the AVM T1 T1B card. - Note: This is a PRI card and handle 30 B-channels. - -CONFIG_ISDN_DRV_AVMB1_C4 - Enable support for the AVM C4/C2 PCI cards. - These cards handle 4/2 BRI ISDN lines (8/4 channels). - -CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON - 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. - diff --git a/drivers/isdn/hardware/avm/Config.in b/drivers/isdn/hardware/avm/Config.in deleted file mode 100644 index 6c600139a640..000000000000 --- a/drivers/isdn/hardware/avm/Config.in +++ /dev/null @@ -1,27 +0,0 @@ -# -# ISDN AVM drivers -# - -mainmenu_option next_comment -comment 'Active AVM cards' - -bool 'Support AVM cards' CONFIG_CAPI_AVM - -if [ "$CONFIG_CAPI_AVM" != "n" ]; then - dep_tristate ' AVM B1 ISA support' CONFIG_ISDN_DRV_AVMB1_B1ISA $CONFIG_ISDN_CAPI $CONFIG_SA - - dep_tristate ' AVM B1 PCI support' CONFIG_ISDN_DRV_AVMB1_B1PCI $CONFIG_ISDN_CAPI $CONFIG_PCI - dep_mbool ' AVM B1 PCI V4 support' CONFIG_ISDN_DRV_AVMB1_B1PCIV4 $CONFIG_ISDN_DRV_AVMB1_B1PCI - - dep_tristate ' AVM T1/T1-B ISA support' CONFIG_ISDN_DRV_AVMB1_T1ISA $CONFIG_ISDN_CAPI $CONFIG_ISA - - dep_tristate ' AVM B1/M1/M2 PCMCIA support' CONFIG_ISDN_DRV_AVMB1_B1PCMCIA $CONFIG_ISDN_CAPI - - dep_tristate ' AVM B1/M1/M2 PCMCIA cs module' CONFIG_ISDN_DRV_AVMB1_AVM_CS $CONFIG_ISDN_DRV_AVMB1_B1PCMCIA $CONFIG_PCMCIA - - dep_tristate ' AVM T1/T1-B PCI support' CONFIG_ISDN_DRV_AVMB1_T1PCI $CONFIG_ISDN_CAPI $CONFIG_PCI - - dep_tristate ' AVM C4/C2 support' CONFIG_ISDN_DRV_AVMB1_C4 $CONFIG_ISDN_CAPI $CONFIG_PCI -fi - -endmenu diff --git a/drivers/isdn/hardware/eicon/Config.help b/drivers/isdn/hardware/eicon/Config.help deleted file mode 100644 index a116030c20ab..000000000000 --- a/drivers/isdn/hardware/eicon/Config.help +++ /dev/null @@ -1,31 +0,0 @@ -CONFIG_CAPI_EICON - Enable support for Eicon Networks active ISDN cards. - -CONFIG_ISDN_DIVAS - 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. - -CONFIG_ISDN_DIVAS_BRIPCI - Enable support for DIVA Server BRI-PCI. - -CONFIG_ISDN_DIVAS_4BRIPCI - Enable support for DIVA Server 4BRI-PCI. - -CONFIG_ISDN_DIVAS_PRIPCI - Enable support for DIVA Server PRI-PCI. - -CONFIG_ISDN_DIVAS_MAINT - Enable Divas Maintainance driver. - -CONFIG_ISDN_DIVAS_USERIDI - Enable support for user-mode IDI interface. - -CONFIG_ISDN_DIVAS_DIVACAPI - You need this to provide the CAPI interface - for DIVA Server cards. - -CONFIG_ISDN_DIVAS_DIVA2I4L - If you want to use the old isdn4linux module, you need - this enabled. - diff --git a/drivers/isdn/hardware/eicon/Config.in b/drivers/isdn/hardware/eicon/Config.in deleted file mode 100644 index 2b1ef29dd435..000000000000 --- a/drivers/isdn/hardware/eicon/Config.in +++ /dev/null @@ -1,20 +0,0 @@ -# -# ISDN DIVAS Eicon driver -# - -mainmenu_option next_comment -comment 'Active Eicon DIVA Server cards' - -bool 'Support Eicon cards' CONFIG_CAPI_EICON - -if [ "$CONFIG_CAPI_EICON" != "n" ]; then - dep_tristate 'Support Eicon DIVA Server cards' CONFIG_ISDN_DIVAS $CONFIG_PROC_FS $CONFIG_PCI m - dep_mbool ' DIVA Server BRI/PCI support' CONFIG_ISDN_DIVAS_BRIPCI $CONFIG_ISDN_DIVAS - dep_mbool ' DIVA Server 4BRI/PCI support' CONFIG_ISDN_DIVAS_4BRIPCI $CONFIG_ISDN_DIVAS - dep_mbool ' DIVA Server PRI/PCI support' CONFIG_ISDN_DIVAS_PRIPCI $CONFIG_ISDN_DIVAS - dep_tristate ' DIVA CAPI2.0 interface support' CONFIG_ISDN_DIVAS_DIVACAPI $CONFIG_ISDN_DIVAS $CONFIG_ISDN_CAPI - dep_tristate ' DIVA Maint driver support' CONFIG_ISDN_DIVAS_MAINT $CONFIG_ISDN_DIVAS - dep_tristate ' DIVA User-IDI interface support' CONFIG_ISDN_DIVAS_USERIDI $CONFIG_ISDN_DIVAS -fi - -endmenu diff --git a/drivers/isdn/hisax/Config.help b/drivers/isdn/hisax/Config.help deleted file mode 100644 index e21177586b38..000000000000 --- a/drivers/isdn/hisax/Config.help +++ /dev/null @@ -1,271 +0,0 @@ -CONFIG_ISDN_DRV_HISAX - 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. - -CONFIG_HISAX_EURO - 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. - -CONFIG_DE_AOC - 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. - -CONFIG_HISAX_NO_SENDCOMPLETE - If you have trouble with some ugly exchanges or you live in - Australia select this option. - -CONFIG_HISAX_NO_LLC - If you have trouble with some ugly exchanges try to select this - option. - -CONFIG_HISAX_NO_KEYPAD - If you like to send special dial strings including * or # without - using the keypad protocol, select this option. - -CONFIG_HISAX_1TR6 - 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. - -CONFIG_HISAX_NI1 - Enable this if you like to use ISDN in US on a NI1 basic rate - interface. - -CONFIG_HISAX_MAX_CARDS - This option allows you to specify the maximum number of cards which - the HiSax driver will be able to handle. - -CONFIG_HISAX_16_0 - This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8 - and many compatibles. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port/shmem settings. - -CONFIG_HISAX_16_3 - This enables HiSax support for the Teles ISDN-cards S0-16.3 the - Teles/Creatix PnP and the Teles PCMCIA. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_TELESPCI - This enables HiSax support for the Teles PCI. - See <file:Documentation/isdn/README.HiSax> on how to configure it. - -CONFIG_HISAX_S0BOX - This enables HiSax support for the Teles/Creatix parallel port - S0BOX. See <file:Documentation/isdn/README.HiSax> on how to - configure it. - -CONFIG_HISAX_AVM_A1 - This enables HiSax support for the AVM A1 (aka "Fritz"). - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_FRITZPCI - This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI". - See <file:Documentation/isdn/README.HiSax> on how to configure it. - -CONFIG_HISAX_AVM_A1_PCMCIA - This enables HiSax support for the AVM A1 "Fritz!PCMCIA"). - See <file:Documentation/isdn/README.HiSax> on how to configure it. - -CONFIG_HISAX_ELSA - This enables HiSax support for the Elsa Mircolink ISA cards, for the - Elsa Quickstep series cards and Elsa PCMCIA. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_IX1MICROR2 - This enables HiSax support for the ITK ix1-micro Revision 2 card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_DIEHLDIVA - This enables HiSax support for the Eicon.Diehl Diva none PRO - versions passive ISDN cards. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_ASUSCOM - This enables HiSax support for the AsusCom and their OEM versions - passive ISDN ISA cards. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_TELEINT - This enables HiSax support for the TELEINT SA1 semiactiv ISDN card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_HFCS - This enables HiSax support for the HFC-S 2BDS0 based cards, like - teles 16.3c. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_SEDLBAUER - This enables HiSax support for the Sedlbauer passive ISDN cards. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using the different cards, a different D-channel protocol, or - non-standard IRQ/port settings. - -CONFIG_HISAX_SPORTSTER - This enables HiSax support for the USR Sportster internal TA card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_MIC - This enables HiSax support for the ITH MIC card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_NETJET - This enables HiSax support for the NetJet from Traverse - Technologies. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_NETJET_U - This enables HiSax support for the Netspider U interface ISDN card - from Traverse Technologies. - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_NICCY - This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_ISURF - This enables HiSax support for the Siemens I-Talk/I-Surf card with - ISAR chip. - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_HSTSAPHIR - This enables HiSax support for the HST Saphir card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_BKM_A4T - This enables HiSax support for the Telekom A4T card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_SCT_QUADRO - This enables HiSax support for the Scitel Quadro card. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_GAZEL - This enables HiSax support for the Gazel cards. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_HFC_PCI - This enables HiSax support for the HFC-S PCI 2BDS0 based cards. - - For more informations see under - <file:Documentation/isdn/README.hfc-pci>. - -CONFIG_HISAX_W6692 - This enables HiSax support for Winbond W6692 based PCI ISDN cards. - - See <file:Documentation/isdn/README.HiSax> on how to configure it - using a different D-channel protocol, or non-standard IRQ/port - settings. - -CONFIG_HISAX_HFC_SX - This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA - cards. This code is not finished yet. - -CONFIG_HISAX_AMD7930 - This enables HiSax support for the AMD7930 chips on some SPARCs. - This code is not finished yet. - -CONFIG_HISAX_DEBUG - This enables debugging code in the new-style HiSax drivers, i.e. - the ST5481 USB driver currently. - If in doubt, say yes. - -CONFIG_HISAX_ELSA_CS - This enables the PCMCIA client driver for the Elsa PCMCIA MicroLink - card. - -CONFIG_HISAX_SEDLBAUER_CS - This enables the PCMCIA client driver for the Sedlbauer Speed Star - and Speed Star II cards. - -CONFIG_HISAX_AVM_A1_CS - This enables the PCMCIA client driver for the AVM A1 / Fritz!Card - PCMCIA cards. - -CONFIG_HISAX_ST5481 - This enables the driver for ST5481 based USB ISDN adapters, - e.g. the BeWan Gazel 128 USB - -CONFIG_HISAX_FRITZ_PCIPNP - This enables the driver for the AVM Fritz!Card PCI, Fritz!Card PCI v2 - and Fritz!Card PnP. - (the latter also needs you to select "ISA Plug and Play support" - from the menu "Plug and Play configuration") - -CONFIG_HISAX_FRITZ_CLASSIC - This enables the driver for the AVM Fritz!Card classic, formerly - known as AVM A1. - diff --git a/drivers/isdn/hisax/Config.in b/drivers/isdn/hisax/Config.in deleted file mode 100644 index 61ed4769baac..000000000000 --- a/drivers/isdn/hisax/Config.in +++ /dev/null @@ -1,62 +0,0 @@ -mainmenu_option next_comment -comment 'Passive cards' -dep_tristate 'HiSax SiemensChipSet driver support' CONFIG_ISDN_DRV_HISAX $CONFIG_ISDN -if [ "$CONFIG_ISDN_DRV_HISAX" != "n" ]; then - comment ' D-channel protocol features' - bool ' HiSax Support for EURO/DSS1' CONFIG_HISAX_EURO - if [ "$CONFIG_HISAX_EURO" != "n" ]; then - bool ' Support for german chargeinfo' CONFIG_DE_AOC - bool ' Disable sending complete' CONFIG_HISAX_NO_SENDCOMPLETE - bool ' Disable sending low layer compatibility' CONFIG_HISAX_NO_LLC - bool ' Disable keypad protocol option' CONFIG_HISAX_NO_KEYPAD - fi - bool ' HiSax Support for german 1TR6' CONFIG_HISAX_1TR6 - bool ' HiSax Support for US NI1' CONFIG_HISAX_NI1 - int ' Maximum number of cards supported by HiSax' CONFIG_HISAX_MAX_CARDS 8 - comment ' HiSax supported cards' - dep_bool ' Teles 16.0/8.0' CONFIG_HISAX_16_0 $CONFIG_ISA - bool ' Teles 16.3 or PNP or PCMCIA' CONFIG_HISAX_16_3 - bool ' Teles PCI' CONFIG_HISAX_TELESPCI - bool ' Teles S0Box' CONFIG_HISAX_S0BOX - dep_bool ' AVM A1 (Fritz)' CONFIG_HISAX_AVM_A1 $CONFIG_ISA - bool ' AVM PnP/PCI (Fritz!PnP/PCI)' CONFIG_HISAX_FRITZPCI - bool ' AVM A1 PCMCIA (Fritz)' CONFIG_HISAX_AVM_A1_PCMCIA - bool ' Elsa cards' CONFIG_HISAX_ELSA - dep_bool ' ITK ix1-micro Revision 2' CONFIG_HISAX_IX1MICROR2 $CONFIG_ISA - bool ' Eicon.Diehl Diva cards' CONFIG_HISAX_DIEHLDIVA - dep_bool ' ASUSCOM ISA cards' CONFIG_HISAX_ASUSCOM $CONFIG_ISA - dep_bool ' TELEINT cards' CONFIG_HISAX_TELEINT $CONFIG_ISA - dep_bool ' HFC-S based cards' CONFIG_HISAX_HFCS $CONFIG_ISA - bool ' Sedlbauer cards' CONFIG_HISAX_SEDLBAUER - dep_bool ' USR Sportster internal TA' CONFIG_HISAX_SPORTSTER $CONFIG_ISA - dep_bool ' MIC card' CONFIG_HISAX_MIC $CONFIG_ISA - bool ' NETjet card' CONFIG_HISAX_NETJET - bool ' NETspider U card' CONFIG_HISAX_NETJET_U - bool ' Niccy PnP/PCI card' CONFIG_HISAX_NICCY - dep_bool ' Siemens I-Surf card' CONFIG_HISAX_ISURF $CONFIG_ISA - dep_bool ' HST Saphir card' CONFIG_HISAX_HSTSAPHIR $CONFIG_ISA - bool ' Telekom A4T card' CONFIG_HISAX_BKM_A4T - bool ' Scitel Quadro card' CONFIG_HISAX_SCT_QUADRO - bool ' Gazel cards' CONFIG_HISAX_GAZEL - bool ' HFC PCI-Bus cards' CONFIG_HISAX_HFC_PCI - bool ' Winbond W6692 based cards' CONFIG_HISAX_W6692 - bool ' HFC-S+, HFC-SP, HFC-PCMCIA cards' CONFIG_HISAX_HFC_SX - if [ "$CONFIG_EXPERIMENTAL" != "n" ]; then -# bool ' TESTEMULATOR (EXPERIMENTAL)' CONFIG_HISAX_TESTEMU - bool ' Formula-n enter:now PCI card (EXPERIMENTAL)' CONFIG_HISAX_ENTERNOW_PCI - if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - bool ' Am7930 (EXPERIMENTAL)' CONFIG_HISAX_AMD7930 - fi - fi - bool ' HiSax debugging' CONFIG_HISAX_DEBUG - - dep_tristate 'Sedlbauer PCMCIA cards' CONFIG_HISAX_SEDLBAUER_CS $CONFIG_ISDN_DRV_HISAX $CONFIG_PCMCIA - dep_tristate 'ELSA PCMCIA MicroLink cards' CONFIG_HISAX_ELSA_CS $CONFIG_ISDN_DRV_HISAX $CONFIG_PCMCIA - dep_tristate 'AVM A1 PCMCIA cards' CONFIG_HISAX_AVM_A1_CS $CONFIG_ISDN_DRV_HISAX $CONFIG_PCMCIA - dep_tristate 'ST5481 USB ISDN modem (EXPERIMENTAL)' CONFIG_HISAX_ST5481 $CONFIG_ISDN_DRV_HISAX $CONFIG_USB $CONFIG_EXPERIMENTAL - dep_tristate 'AVM Fritz!Card PCI/PCIv2/PnP support (EXPERIMENTAL)' CONFIG_HISAX_FRITZ_PCIPNP $CONFIG_ISDN_DRV_HISAX $CONFIG_EXPERIMENTAL - dep_tristate 'AVM Fritz!Card classic support (EXPERIMENTAL)' CONFIG_HISAX_FRITZ_CLASSIC $CONFIG_ISDN_DRV_HISAX $CONFIG_EXPERIMENTAL - dep_tristate 'HFC PCI support (EXPERIMENTAL)' CONFIG_HISAX_HFCPCI $CONFIG_ISDN_DRV_HISAX $CONFIG_EXPERIMENTAL -fi -endmenu - diff --git a/drivers/isdn/hysdn/Config.help b/drivers/isdn/hysdn/Config.help deleted file mode 100644 index 82489f801ba0..000000000000 --- a/drivers/isdn/hysdn/Config.help +++ /dev/null @@ -1,9 +0,0 @@ -CONFIG_HYSDN - Say Y here if you have one of Hypercope's active PCI ISDN cards - Champ, Ergo and Metro. You will then get a module called hysdn.o. - Please read the file <file:Documentation/isdn/README.hysdn> for more - information. - -CONFIG_HYSDN_CAPI - Say Y here if you like to use Hypercope's CAPI 2.0 interface. - diff --git a/drivers/isdn/hysdn/Config.in b/drivers/isdn/hysdn/Config.in deleted file mode 100644 index 280c90b9a0db..000000000000 --- a/drivers/isdn/hysdn/Config.in +++ /dev/null @@ -1,6 +0,0 @@ -# -# Config.in for HYSDN ISDN driver -# - -dep_tristate ' Hypercope HYSDN cards (Champ, Ergo, Metro) support (module only)' CONFIG_HYSDN m $CONFIG_PROC_FS -dep_mbool ' HYSDN CAPI 2.0 support' CONFIG_HYSDN_CAPI $CONFIG_HYSDN $CONFIG_ISDN_CAPI diff --git a/drivers/isdn/i4l/Config.help b/drivers/isdn/i4l/Config.help deleted file mode 100644 index 2e709216d004..000000000000 --- a/drivers/isdn/i4l/Config.help +++ /dev/null @@ -1,88 +0,0 @@ -CONFIG_ISDN - 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 - <file:Documentation/isdn/README> 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. - -CONFIG_ISDN_PPP - 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 <file:Documentation/isdn/README.syncppp> and - <file:Documentation/isdn/syncPPP.FAQ> for more information. - -CONFIG_ISDN_MPP - With synchronous PPP enabled, it is possible to increase throughput - by bundling several ISDN-connections, using this protocol. See - <file:Documentation/isdn/README.syncppp> for more information. - -CONFIG_ISDN_PPP_VJ - This enables Van Jacobson header compression for synchronous PPP. - Say Y if the other end of the connection supports it. - -CONFIG_ISDN_PPP_BSDCOMP - 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. - -CONFIG_ISDN_AUDIO - 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 - <file:Documentation/isdn/README.audio> for more information. - -CONFIG_ISDN_X25 - This feature provides the X.25 protocol over ISDN connections. - See <file:Documentation/isdn/README.x25> for more information - if you are thinking about using this. - -CONFIG_ISDN_DIVERSION - 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 <file:Documentation/isdn/README.diversion>. - -CONFIG_ISDN_TTY_FAX - 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 <file:Documentation/isdn/README.fax> for more information. - -CONFIG_ISDN_DRV_LOOP - 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. - diff --git a/drivers/isdn/i4l/Config.in b/drivers/isdn/i4l/Config.in deleted file mode 100644 index 2b19e0eddf6c..000000000000 --- a/drivers/isdn/i4l/Config.in +++ /dev/null @@ -1,26 +0,0 @@ -# -# Old ISDN4Linux config -# - -if [ "$CONFIG_INET" != "n" ]; then - bool ' Support synchronous PPP' CONFIG_ISDN_PPP - if [ "$CONFIG_ISDN_PPP" != "n" ]; then - bool ' Use VJ-compression with synchronous PPP' CONFIG_ISDN_PPP_VJ - bool ' Support generic MP (RFC 1717)' CONFIG_ISDN_MPP - dep_tristate ' Support BSD compression' CONFIG_ISDN_PPP_BSDCOMP $CONFIG_ISDN - fi -fi -bool ' Support audio via ISDN' CONFIG_ISDN_AUDIO -if [ "$CONFIG_ISDN_AUDIO" != "n" ]; then - bool ' Support AT-Fax Class 1 and 2 commands' CONFIG_ISDN_TTY_FAX -fi -if [ "$CONFIG_X25" != "n" ]; then - bool ' X.25 PLP on top of ISDN' CONFIG_ISDN_X25 -fi - -mainmenu_option next_comment -comment 'ISDN feature submodules' - dep_tristate 'isdnloop support' CONFIG_ISDN_DRV_LOOP $CONFIG_ISDN - dep_tristate 'Support isdn diversion services' CONFIG_ISDN_DIVERSION $CONFIG_ISDN -endmenu - diff --git a/drivers/isdn/icn/Config.help b/drivers/isdn/icn/Config.help deleted file mode 100644 index f49d7655d60c..000000000000 --- a/drivers/isdn/icn/Config.help +++ /dev/null @@ -1,10 +0,0 @@ -CONFIG_ISDN_DRV_ICN - This enables support for two kinds of ISDN-cards made by a German - company called ICN. 2B is the standard version for a single ISDN - line with two B-channels, 4B supports two ISDN lines. For running - this card, additional firmware is necessary, which has to be - downloaded into the card using a utility which is distributed - separately. See <file:Documentation/isdn/README> and - <file:Documentation/isdn/README.icn> for more - information. - diff --git a/drivers/isdn/icn/Config.in b/drivers/isdn/icn/Config.in deleted file mode 100644 index 99be93adf38e..000000000000 --- a/drivers/isdn/icn/Config.in +++ /dev/null @@ -1,5 +0,0 @@ -# -# Config.in for ICN ISDN driver -# - -dep_tristate 'ICN 2B and 4B support' CONFIG_ISDN_DRV_ICN $CONFIG_ISDN $CONFIG_ISA diff --git a/drivers/isdn/pcbit/Config.help b/drivers/isdn/pcbit/Config.help deleted file mode 100644 index dcb62722593d..000000000000 --- a/drivers/isdn/pcbit/Config.help +++ /dev/null @@ -1,8 +0,0 @@ -CONFIG_ISDN_DRV_PCBIT - This enables support for the PCBIT ISDN-card. This card is - manufactured in Portugal by Octal. For running this card, - additional firmware is necessary, which has to be downloaded into - the card using a utility which is distributed separately. See - <file:Documentation/isdn/README> and - <file:Documentation/isdn/README.pcbit> for more information. - diff --git a/drivers/isdn/pcbit/Config.in b/drivers/isdn/pcbit/Config.in deleted file mode 100644 index e3d09f96065f..000000000000 --- a/drivers/isdn/pcbit/Config.in +++ /dev/null @@ -1,5 +0,0 @@ -# -# Config.in for PCBIT ISDN driver -# - -dep_tristate 'PCBIT-D support' CONFIG_ISDN_DRV_PCBIT $CONFIG_ISDN $CONFIG_ISA diff --git a/drivers/isdn/sc/Config.help b/drivers/isdn/sc/Config.help deleted file mode 100644 index f98b62cb0530..000000000000 --- a/drivers/isdn/sc/Config.help +++ /dev/null @@ -1,8 +0,0 @@ -CONFIG_ISDN_DRV_SC - This enables support for the Spellcaster BRI ISDN boards. This - driver currently builds only in a modularized version ( = code which - can be inserted in and removed from the running kernel whenever you - want, details in <file:Documentation/modules.txt>); the module will - be called sc.o. See <file:Documentation/isdn/README.sc> and - <http://www.spellcast.com/> for more information. - diff --git a/drivers/isdn/sc/Config.in b/drivers/isdn/sc/Config.in deleted file mode 100644 index 08dc7b12d416..000000000000 --- a/drivers/isdn/sc/Config.in +++ /dev/null @@ -1,5 +0,0 @@ -# -# Config.in for Spellcaster ISDN driver -# - -dep_tristate 'Spellcaster support' CONFIG_ISDN_DRV_SC $CONFIG_ISDN $CONFIG_ISA diff --git a/drivers/isdn/tpam/Config.help b/drivers/isdn/tpam/Config.help deleted file mode 100644 index ff17962ef770..000000000000 --- a/drivers/isdn/tpam/Config.help +++ /dev/null @@ -1,8 +0,0 @@ -CONFIG_ISDN_DRV_TPAM - This enables support for the Auvertech TurboPAM ISDN-card. - For running this card, additional firmware is necessary, which has - to be downloaded into the card using a utility which is distributed - separately from the Auvertech's web site: <http://www.auvertech.fr/>. - - Please redirect all support questions to support@auvertech.fr. - diff --git a/drivers/isdn/tpam/Config.in b/drivers/isdn/tpam/Config.in deleted file mode 100644 index b0f0cfe3479f..000000000000 --- a/drivers/isdn/tpam/Config.in +++ /dev/null @@ -1,7 +0,0 @@ -# -# Config.in for Auvertech TurboPAM ISDN driver -# - -if [ "$CONFIG_EXPERIMENTAL" != "n" ]; then - dep_tristate 'Auvertech TurboPAM support (EXPERIMENTAL)' CONFIG_ISDN_DRV_TPAM $CONFIG_ISDN $CONFIG_PCI -fi diff --git a/drivers/md/Config.help b/drivers/md/Config.help deleted file mode 100644 index e55fc64d6bbb..000000000000 --- a/drivers/md/Config.help +++ /dev/null @@ -1,117 +0,0 @@ -CONFIG_MD - Support multiple physical spindles through a single logical device. - Required for RAID and logical volume management. - -CONFIG_BLK_DEV_MD - 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 - <http://www.linuxdoc.org/docs.html#howto>. There you will also learn - where to get the supporting user space utilities raidtools. - - If unsure, say N. - -CONFIG_MD_LINEAR - 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 <file:Documentation/modules.txt>. The module - will be called linear.o. - - If unsure, say Y. - -CONFIG_MD_RAID0 - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:Documentation/modules.txt>. The module - will be called raid0.o. - - If unsure, say Y. - -CONFIG_MD_RAID1 - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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.o ( = 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>. - - If unsure, say Y. - -CONFIG_MD_RAID5 - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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.o ( = 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>. - - If unsure, say Y. - -CONFIG_MD_MULTIPATH - 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. - -CONFIG_BLK_DEV_DM - 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 - <file:Documentation/modules.txt>. The module will be called dm-mod.o. - - If unsure, say N. diff --git a/drivers/md/Config.in b/drivers/md/Config.in deleted file mode 100644 index e0b3445556e7..000000000000 --- a/drivers/md/Config.in +++ /dev/null @@ -1,17 +0,0 @@ -# -# Block device driver configuration -# -mainmenu_option next_comment -comment 'Multi-device support (RAID and LVM)' - -bool 'Multiple devices driver support (RAID and LVM)' CONFIG_MD - -dep_tristate ' RAID support' CONFIG_BLK_DEV_MD $CONFIG_MD -dep_tristate ' Linear (append) mode' CONFIG_MD_LINEAR $CONFIG_BLK_DEV_MD -dep_tristate ' RAID-0 (striping) mode' CONFIG_MD_RAID0 $CONFIG_BLK_DEV_MD -dep_tristate ' RAID-1 (mirroring) mode' CONFIG_MD_RAID1 $CONFIG_BLK_DEV_MD -dep_tristate ' RAID-4/RAID-5 mode' CONFIG_MD_RAID5 $CONFIG_BLK_DEV_MD -dep_tristate ' Multipath I/O support' CONFIG_MD_MULTIPATH $CONFIG_BLK_DEV_MD -dep_tristate ' Device mapper support' CONFIG_BLK_DEV_DM $CONFIG_MD - -endmenu diff --git a/drivers/media/Config.help b/drivers/media/Config.help deleted file mode 100644 index 6a439f48337a..000000000000 --- a/drivers/media/Config.help +++ /dev/null @@ -1,15 +0,0 @@ -CONFIG_VIDEO_DEV - Support for audio/video capture and overlay devices and FM radio - cards. The exact capabilities of each device vary. User tools for - this are available from - <ftp://ftp.uk.linux.org/pub/linux/video4linux/>. - - If you are interested in writing a driver for such an audio/video - device or user software interacting with such a driver, please read - the file <file:Documentation/video4linux/API.html>. - - This driver is also available as a module called videodev.o ( = 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>. - diff --git a/drivers/media/Config.in b/drivers/media/Config.in deleted file mode 100644 index 67b663158c03..000000000000 --- a/drivers/media/Config.in +++ /dev/null @@ -1,14 +0,0 @@ -# -# Multimedia device configuration -# -mainmenu_option next_comment -comment 'Multimedia devices' - -tristate 'Video For Linux' CONFIG_VIDEO_DEV -if [ "$CONFIG_VIDEO_DEV" != "n" ]; then - source drivers/media/video/Config.in - source drivers/media/radio/Config.in - source drivers/media/dvb/Config.in -fi - -endmenu diff --git a/drivers/media/dvb/Config.help b/drivers/media/dvb/Config.help deleted file mode 100644 index d2699b18f31a..000000000000 --- a/drivers/media/dvb/Config.help +++ /dev/null @@ -1,21 +0,0 @@ -CONFIG_DVB - Support Digital Video Broadcasting hardware. Enable this if you - own a DVB adapter and want to use it or if you compile Linux for - a digital SetTopBox. - - API specs and user tools and are available for example from - <http://www.linuxtv.org/>. - - Please report problems regarding this driver to the LinuxDVB - mailing list. - - You might want add the following lines to your /etc/modules.conf: - - alias char-major-250 dvb - alias dvb dvb-ttpci - below dvb-ttpci alps_bsru6 alps_bsrv2 \ - grundig_29504-401 grundig_29504-491 \ - ves1820 - - If unsure say N. - diff --git a/drivers/media/dvb/Config.in b/drivers/media/dvb/Config.in deleted file mode 100644 index 40cce4668b71..000000000000 --- a/drivers/media/dvb/Config.in +++ /dev/null @@ -1,17 +0,0 @@ -# -# Multimedia device configuration -# -mainmenu_option next_comment -comment 'Digital Video Broadcasting Devices' - -bool 'DVB For Linux' CONFIG_DVB - -if [ "$CONFIG_DVB" != "n" ]; then - source drivers/media/dvb/dvb-core/Config.in - source drivers/media/dvb/frontends/Config.in - - comment 'Supported DVB Adapters' - source drivers/media/dvb/av7110/Config.in -fi - -endmenu diff --git a/drivers/media/dvb/av7110/Config.help b/drivers/media/dvb/av7110/Config.help deleted file mode 100644 index db5d87a05569..000000000000 --- a/drivers/media/dvb/av7110/Config.help +++ /dev/null @@ -1,21 +0,0 @@ -CONFIG_DVB_AV7110 - Support for SAA7146 and AV7110 based DVB cards as produced - by Fujitsu-Siemens, Technotrend, Hauppauge and others. - - Simple cards like so called Budget- or Nova-PCI cards are - supported as well as fullfeatured cards with onboard MPEG2 - decoder. - - Say Y if you own such a card and want to use it. - - -CONFIG_DVB_AV7110_OSD - The AV7110 firmware provides some code to generate an OnScreenDisplay - on the video output. This is kind of nonstandard and not guaranteed to - be maintained. - - Anyway, some popular DVB software like VDR uses this OSD to render - its menus, so say Y if you want to use this software. - - All other people say N. - diff --git a/drivers/media/dvb/av7110/Config.in b/drivers/media/dvb/av7110/Config.in deleted file mode 100644 index 95c1dc819d70..000000000000 --- a/drivers/media/dvb/av7110/Config.in +++ /dev/null @@ -1,6 +0,0 @@ -dep_tristate ' SAA7146 based AV7110 and Nova/budget cards' CONFIG_DVB_AV7110 $CONFIG_VIDEO_DEV $CONFIG_DVB_CORE - -if [ "$CONFIG_DVB_AV7110" != "n" ]; then - bool ' AV7110 OSD support' CONFIG_DVB_AV7110_OSD -fi - diff --git a/drivers/media/dvb/dvb-core/Config.help b/drivers/media/dvb/dvb-core/Config.help deleted file mode 100644 index ad3c23d740fe..000000000000 --- a/drivers/media/dvb/dvb-core/Config.help +++ /dev/null @@ -1,13 +0,0 @@ -CONFIG_DVB_CORE - DVB core utility functions for device handling, software fallbacks etc. - - Say Y when you have a DVB card and want to use it. If unsure say N. - - -CONFIG_DVB_DEVFS_ONLY - Drop support for old major/minor device scheme and support only devfs - systems. This saves some code. - - If unsure say N. - - diff --git a/drivers/media/dvb/dvb-core/Config.in b/drivers/media/dvb/dvb-core/Config.in deleted file mode 100644 index 9c43c6498cf3..000000000000 --- a/drivers/media/dvb/dvb-core/Config.in +++ /dev/null @@ -1,7 +0,0 @@ - -dep_tristate ' DVB Core Support' CONFIG_DVB_CORE $CONFIG_DVB - -if [ "$CONFIG_DVB_CORE" != "n" ]; then - dep_bool ' devfs only' CONFIG_DVB_DEVFS_ONLY $CONFIG_DVB_CORE $CONFIG_DEVFS_FS -fi - diff --git a/drivers/media/dvb/frontends/Config.help b/drivers/media/dvb/frontends/Config.help deleted file mode 100644 index dd7cdc2d8496..000000000000 --- a/drivers/media/dvb/frontends/Config.help +++ /dev/null @@ -1,39 +0,0 @@ -CONFIG_DVB_ALPS_BSRU6 - A DVB-S tuner module. - - Say Y when you want to support this frontend. - - If you don't know what tuner module is soldered on your - DVB adapter simply enable all supported frontends, the - right one will get autodetected. - -CONFIG_DVB_ALPS_BSRV2 - A DVB-S tuner module. Say Y when you want to support this frontend. - - If you don't know what tuner module is soldered on your - DVB adapter simply enable all supported frontends, the - right one will get autodetected. - -CONFIG_DVB_GRUNDIG_29504_491 - A DVB-S tuner module. Say Y when you want to support this frontend. - - If you don't know what tuner module is soldered on your - DVB adapter simply enable all supported frontends, the - right one will get autodetected. - -CONFIG_DVB_GRUNDIG_29504_401 - A DVB-T tuner module. Say Y when you want to support this frontend. - - If you don't know what tuner module is soldered on your - DVB adapter simply enable all supported frontends, the - right one will get autodetected. - -CONFIG_DVB_VES1820 - The VES1820 Demodulator is used on many DVB-C PCI cards and in some - DVB-C SetTopBoxes. Say Y when you see this demodulator chip near your - tuner module. - - If you don't know what tuner module is soldered on your - DVB adapter simply enable all supported frontends, the - right one will get autodetected. - diff --git a/drivers/media/dvb/frontends/Config.in b/drivers/media/dvb/frontends/Config.in deleted file mode 100644 index 638a9462ca04..000000000000 --- a/drivers/media/dvb/frontends/Config.in +++ /dev/null @@ -1,9 +0,0 @@ - -comment 'Supported Frontend Modules' - -dep_tristate ' Alps BSRU6 (QPSK)' CONFIG_DVB_ALPS_BSRU6 $CONFIG_DVB_CORE -dep_tristate ' Alps BSRV2 (QPSK)' CONFIG_DVB_ALPS_BSRV2 $CONFIG_DVB_CORE -dep_tristate ' Grundig 29504-491 (QPSK)' CONFIG_DVB_GRUNDIG_29504_491 $CONFIG_DVB_CORE -dep_tristate ' Grundig 29504-401 (OFDM)' CONFIG_DVB_GRUNDIG_29504_401 $CONFIG_DVB_CORE -dep_tristate ' Frontends with external VES1820 demodulator (QAM)' CONFIG_DVB_VES1820 $CONFIG_DVB_CORE - diff --git a/drivers/media/radio/Config.help b/drivers/media/radio/Config.help deleted file mode 100644 index 5ff2f66ea337..000000000000 --- a/drivers/media/radio/Config.help +++ /dev/null @@ -1,274 +0,0 @@ -CONFIG_RADIO_RTRACK - Choose Y here if you have one of these FM radio cards, and then fill - in the port address below. - - Note that newer AIMSlab RadioTrack cards have a different chipset - and are not supported by this driver. For these cards, use the - RadioTrack II driver below. - - If you have a GemTeks combined (PnP) sound- and radio card you must - use this driver as a module and setup the card with isapnptools. - You must also pass the module a suitable io parameter, 0x248 has - been reported to be used by these cards. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. More - information is contained in the file - <file:Documentation/video4linux/radiotrack.txt>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-aimslab.o. - -CONFIG_RADIO_RTRACK_PORT - Enter either 0x30f or 0x20f here. The card default is 0x30f, if you - haven't changed the jumper setting on the card. - -CONFIG_RADIO_RTRACK2 - Choose Y here if you have this FM radio card, and then fill in the - port address below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-rtrack2.o. - -CONFIG_RADIO_RTRACK2_PORT - Enter either 0x30c or 0x20c here. The card default is 0x30c, if you - haven't changed the jumper setting on the card. - -CONFIG_RADIO_AZTECH - Choose Y here if you have one of these FM radio cards, and then fill - in the port address below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-aztech.o. - -CONFIG_RADIO_AZTECH_PORT - Enter either 0x350 or 0x358 here. The card default is 0x350, if you - haven't changed the setting of jumper JP3 on the card. Removing the - jumper sets the card to 0x358. - -CONFIG_RADIO_CADET - Choose Y here if you have one of these AM/FM radio cards, and then - fill in the port address below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - Further documentation on this driver can be found on the WWW at - <http://linux.blackhawke.net/cadet.html>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-cadet.o. - -CONFIG_RADIO_SF16FMI - Choose Y here if you have one of these FM radio cards. If you - compile the driver into the kernel and your card is not PnP one, you - have to add "sf16fm=<io>" to the kernel command line (I/O address is - 0x284 or 0x384). - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-sf16fmi.o. - -CONFIG_RADIO_TYPHOON - Choose Y here if you have one of these FM radio cards, and then fill - in the port address and the frequency used for muting below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-typhoon.o. - -CONFIG_RADIO_TYPHOON_PROC_FS - Say Y here if you want the typhoon radio card driver to write - status information (frequency, volume, muted, mute frequency, - base address) to /proc/radio-typhoon. The file can be viewed with - your favorite pager (i.e. use "more /proc/radio-typhoon" or "less - /proc/radio-typhoon" or simply "cat /proc/radio-typhoon"). - -CONFIG_RADIO_TYPHOON_PORT - Enter the I/O port of your Typhoon or EcoRadio radio card. - -CONFIG_RADIO_TYPHOON_MUTEFREQ - Enter the frequency used for muting the radio. The device is never - completely silent. If the volume is just turned down, you can still - hear silent voices and music. For that reason, the frequency of the - radio device is set to the frequency you can enter here whenever - the device is muted. There should be no local radio station at that - frequency. - -CONFIG_RADIO_ZOLTRIX - Choose Y here if you have one of these FM radio cards, and then fill - in the port address below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-zoltrix.o. - -CONFIG_RADIO_ZOLTRIX_PORT - Enter the I/O port of your Zoltrix radio card. - -CONFIG_RADIO_MIROPCM20 - Choose Y here if you have this FM radio card. You also need to say Y - to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound") - for this to work. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called miropcm20.o. - -CONFIG_RADIO_MIROPCM20_RDS - Choose Y here if you want to see RDS/RBDS information like - RadioText, Programme Service name, Clock Time and date, Programme - TYpe and Traffic Announcement/Programme identification. You also - need to say Y to "miroSOUND PCM20 radio" and devfs! - - It's not possible to read the raw RDS packets from the device, so - the driver cant provide an V4L interface for this. But the - availability of RDS is reported over V4L by the basic driver - already. Here RDS can be read from files in /dev/v4l/rds. - - As module the driver will be called miropcm20-rds.o. - -CONFIG_RADIO_MAESTRO - Say Y here to directly support the on-board radio tuner on the - Maestro 2 or 2E sound card. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-maestro.o. - -CONFIG_RADIO_MAXIRADIO - Choose Y here if you have this radio card. This card may also be - found as Gemtek PCI FM. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-maxiradio.o. - -CONFIG_RADIO_GEMTEK - Choose Y here if you have this FM radio card, and then fill in the - port address below. - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-gemtek.o. - -CONFIG_RADIO_GEMTEK_PORT - Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is - 0x34c, if you haven't changed the jumper setting on the card. On - Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the I/O - port is 0x28c. - -CONFIG_RADIO_GEMTEK_PCI - Choose Y here if you have this PCI FM radio card. - - In order to control your radio card, you will need to use programs - that are compatible with the Video for Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-gemtek-pci.o. - -CONFIG_RADIO_TERRATEC - Choose Y here if you have this FM radio card, and then fill in the - port address below. (TODO) - - Note: This driver is in its early stages. Right now volume and - frequency control and muting works at least for me, but - unfortunately I have not found anybody who wants to use this card - with Linux. So if it is this what YOU are trying to do right now, - PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de) - - In order to control your radio card, you will need to use programs - that are compatible with the Video For Linux API. Information on - this API and pointers to "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 <file:Documentation/modules.txt>. The module - will be called radio-terratec.o. - -CONFIG_RADIO_TERRATEC_PORT - Fill in the I/O port of your TerraTec FM radio card. If unsure, go - with the default. - -CONFIG_RADIO_TRUST - This is a driver for the Trust FM radio cards. Say Y if you have - such a card and want to use it under Linux. - - This driver is also available as a module called radio-trust.o ( = - 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>. - -CONFIG_RADIO_TRUST_PORT - Enter the I/O port of your Trust FM radio card. If unsure, try the - values "0x350" or "0x358". - diff --git a/drivers/media/radio/Config.in b/drivers/media/radio/Config.in deleted file mode 100644 index 0bd40d7fa5dc..000000000000 --- a/drivers/media/radio/Config.in +++ /dev/null @@ -1,57 +0,0 @@ -# -# Multimedia Video device configuration -# -mainmenu_option next_comment -comment 'Radio Adapters' - -if [ "$CONFIG_ISA" = "y" ]; then -dep_tristate ' ADS Cadet AM/FM Tuner' CONFIG_RADIO_CADET $CONFIG_VIDEO_DEV -dep_tristate ' AIMSlab RadioTrack (aka RadioReveal) support' CONFIG_RADIO_RTRACK $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_RTRACK" = "y" ]; then - hex ' RadioTrack i/o port (0x20f or 0x30f)' CONFIG_RADIO_RTRACK_PORT 20f -fi -dep_tristate ' AIMSlab RadioTrack II support' CONFIG_RADIO_RTRACK2 $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_RTRACK2" = "y" ]; then - hex ' RadioTrack II i/o port (0x20c or 0x30c)' CONFIG_RADIO_RTRACK2_PORT 30c -fi -dep_tristate ' Aztech/Packard Bell Radio' CONFIG_RADIO_AZTECH $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_AZTECH" = "y" ]; then - hex ' Aztech/Packard Bell I/O port (0x350 or 0x358)' CONFIG_RADIO_AZTECH_PORT 350 -fi -dep_tristate ' GemTek Radio Card support' CONFIG_RADIO_GEMTEK $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_GEMTEK" = "y" ]; then - hex ' GemTek i/o port (0x20c, 0x30c, 0x24c or 0x34c)' CONFIG_RADIO_GEMTEK_PORT 34c -fi -fi -dep_tristate ' GemTek PCI Radio Card support' CONFIG_RADIO_GEMTEK_PCI $CONFIG_VIDEO_DEV $CONFIG_PCI -dep_tristate ' Guillemot MAXI Radio FM 2000 radio' CONFIG_RADIO_MAXIRADIO $CONFIG_VIDEO_DEV -dep_tristate ' Maestro on board radio' CONFIG_RADIO_MAESTRO $CONFIG_VIDEO_DEV -if [ "$CONFIG_ISA" = "y" ]; then -dep_tristate ' miroSOUND PCM20 radio' CONFIG_RADIO_MIROPCM20 $CONFIG_VIDEO_DEV $CONFIG_SOUND_ACI_MIXER -dep_tristate ' miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)' CONFIG_RADIO_MIROPCM20_RDS $CONFIG_RADIO_MIROPCM20 $CONFIG_EXPERIMENTAL -dep_tristate ' SF16FMI Radio' CONFIG_RADIO_SF16FMI $CONFIG_VIDEO_DEV -dep_tristate ' TerraTec ActiveRadio ISA Standalone' CONFIG_RADIO_TERRATEC $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_TERRATEC" = "y" ]; then - hex ' Terratec i/o port (normally 0x590)' CONFIG_RADIO_TERRATEC_PORT 590 -fi -dep_tristate ' Trust FM radio card' CONFIG_RADIO_TRUST $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_TRUST" = "y" ]; then - hex ' Trust i/o port (usually 0x350 or 0x358)' CONFIG_RADIO_TRUST_PORT 350 -fi -dep_tristate ' Typhoon Radio (a.k.a. EcoRadio)' CONFIG_RADIO_TYPHOON $CONFIG_VIDEO_DEV -if [ "$CONFIG_PROC_FS" = "y" ]; then - if [ "$CONFIG_RADIO_TYPHOON" != "n" ]; then - bool ' Support for /proc/radio-typhoon' CONFIG_RADIO_TYPHOON_PROC_FS - fi -fi -if [ "$CONFIG_RADIO_TYPHOON" = "y" ]; then - hex ' Typhoon I/O port (0x316 or 0x336)' CONFIG_RADIO_TYPHOON_PORT 316 - int ' Typhoon frequency set when muting the device (kHz)' CONFIG_RADIO_TYPHOON_MUTEFREQ 87500 -fi -dep_tristate ' Zoltrix Radio' CONFIG_RADIO_ZOLTRIX $CONFIG_VIDEO_DEV -if [ "$CONFIG_RADIO_ZOLTRIX" = "y" ]; then - hex ' ZOLTRIX I/O port (0x20c or 0x30c)' CONFIG_RADIO_ZOLTRIX_PORT 20c -fi -fi - -endmenu diff --git a/drivers/media/video/Config.help b/drivers/media/video/Config.help deleted file mode 100644 index d3d527aa21b8..000000000000 --- a/drivers/media/video/Config.help +++ /dev/null @@ -1,153 +0,0 @@ -CONFIG_VIDEO_PROC_FS - If you say Y here, you are able to access video device information - in /proc/video. - - To use this option, you have to check, that the "/proc file system - support" (CONFIG_PROC_FS) is enabled too. - -CONFIG_I2C_PARPORT - I2C is a simple serial bus system used in many micro controller - applications. Saying Y here will allow you to use your parallel - port as an I2C interface. - - 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 <file:Documentation/modules.txt>. The module - will be called i2c-parport.o. - -CONFIG_VIDEO_PLANB - PlanB is the V4L driver for the PowerMac 7x00/8x00 series video - input hardware. If you want to experiment with this, say Y. - Otherwise, or if you don't understand a word, say N. - See <http://www.cpu.lu/~mlan/planb.html> for more info. - - Saying M will compile this driver as a module (planb.o). - -CONFIG_VIDEO_BT848 - Support for BT848 based frame grabber/overlay boards. This includes - the Miro, Hauppauge and STB boards. Please read the material in - <file:Documentation/video4linux/bttv> for more information. - - If you say Y or M here, you need to say Y or M to "I2C support" and - "I2C bit-banging interfaces" in the character device section. - - This driver is available as a module called bttv.o ( = 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>. - -CONFIG_VIDEO_VINO - Say Y here to build in support for the Vino video input system found - on SGI Indy machines. - -CONFIG_VIDEO_STRADIS - Say Y here to enable support for the Stradis 4:2:2 MPEG-2 video - driver for PCI. There is a product page at - <http://www.stradis.com/decoder.html>. - -CONFIG_VIDEO_ZORAN - Say Y here to include support for video cards based on the Zoran - ZR36057/36060 encoder/decoder chip (including the Iomega Buz and the - Miro DC10 and DC30 video capture cards). - -CONFIG_VIDEO_ZORAN_BUZ - Say Y here to include support for the Iomega Buz video card. There - is a Buz/Linux homepage at <http://www.lysator.liu.se/~gz/buz/>. - -CONFIG_VIDEO_ZR36120 - Support for ZR36120/ZR36125 based frame grabber/overlay boards. - This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV, - and Buster boards. Please read the material in - <file:Documentation/video4linux/zr36120.txt> for more information. - - This driver is also available as a module called zr36120.o ( = 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>. - -CONFIG_VIDEO_SAA5249 - Support for I2C bus based teletext using the SAA5249 chip. At the - moment this is only useful on some European WinTV cards. - - This driver is also available as a module called saa5249.o ( = 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>. - -CONFIG_VIDEO_BWQCAM - Say Y have if you the black and white version of the QuickCam - camera. See the next option for the color version. - - This driver is also available as a module called bw-qcam.o ( = 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>. - -CONFIG_VIDEO_CQCAM - This is the video4linux driver for the colour version of the - Connectix QuickCam. If you have one of these cameras, say Y here, - otherwise say N. This driver does not work with the original - monochrome QuickCam, QuickCam VC or QuickClip. It is also available - as a module (c-qcam.o). - Read <file:Documentation/video4linux/CQcam.txt> for more information. - -CONFIG_VIDEO_W9966 - Video4linux driver for Winbond's w9966 based Webcams. - Currently tested with the LifeView FlyCam Supra. - If you have one of these cameras, say Y here - otherwise say N. - This driver is also available as a module (w9966.o). - - Check out <file:Documentation/video4linux/w9966.txt> for more - information. - -CONFIG_VIDEO_CPIA - This is the video4linux driver for cameras based on Vision's CPiA - (Colour Processor Interface ASIC), such as the Creative Labs Video - Blaster Webcam II. If you have one of these cameras, say Y here - and select parallel port and/or USB lowlevel support below, - otherwise say N. This will not work with the Creative Webcam III. - - Please read <file:Documentation/video4linux/README.cpia> for more - information. - - This driver is also available as a module (cpia.o). - -CONFIG_VIDEO_CPIA_PP - This is the lowlevel parallel port support for cameras based on - Vision's CPiA (Colour Processor Interface ASIC), such as the - Creative Webcam II. If you have the parallel port version of one - of these cameras, say Y here, otherwise say N. It is also available - as a module (cpia_pp.o). - -CONFIG_VIDEO_CPIA_USB - This is the lowlevel USB support for cameras based on Vision's CPiA - (Colour Processor Interface ASIC), such as the Creative Webcam II. - If you have the USB version of one of these cameras, say Y here, - otherwise say N. This will not work with the Creative Webcam III. - It is also available as a module (cpia_usb.o). - -CONFIG_VIDEO_PMS - Say Y if you have such a thing. This driver is also available as a - module called pms.o ( = 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>. - -CONFIG_VIDEO_MEYE - This is the video4linux driver for the Motion Eye camera found - in the Vaio Picturebook laptops. Please read the material in - <file:Documentation/video4linux/meye.txt> for more information. - - If you say Y or M here, you need to say Y or M to "Sony Programmable - I/O Control Device" in the character device section. - - This driver is available as a module called meye.o ( = 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>. - -CONFIG_TUNER_3036 - Say Y here to include support for Philips SAB3036 compatible tuners. - If in doubt, say N. - diff --git a/drivers/media/video/Config.in b/drivers/media/video/Config.in deleted file mode 100644 index 512b756f7663..000000000000 --- a/drivers/media/video/Config.in +++ /dev/null @@ -1,54 +0,0 @@ -# -# Multimedia Video device configuration -# -mainmenu_option next_comment -comment 'Video For Linux' - -dep_bool ' V4L information in proc filesystem' CONFIG_VIDEO_PROC_FS $CONFIG_PROC_FS - -comment 'Video Adapters' -if [ "$CONFIG_I2C_ALGOBIT" = "y" -o "$CONFIG_I2C_ALGOBIT" = "m" ]; then - dep_tristate ' BT848 Video For Linux' CONFIG_VIDEO_BT848 $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C_ALGOBIT -fi -dep_tristate ' Mediavision Pro Movie Studio Video For Linux' CONFIG_VIDEO_PMS $CONFIG_VIDEO_DEV -if [ "$CONFIG_ALL_PPC" = "y" ]; then - dep_tristate ' PlanB Video-In on PowerMac' CONFIG_VIDEO_PLANB $CONFIG_VIDEO_DEV -fi -if [ "$CONFIG_PARPORT" != "n" ]; then - dep_tristate ' Quickcam BW Video For Linux' CONFIG_VIDEO_BWQCAM $CONFIG_VIDEO_DEV $CONFIG_PARPORT - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' QuickCam Colour Video For Linux (EXPERIMENTAL)' CONFIG_VIDEO_CQCAM $CONFIG_VIDEO_DEV $CONFIG_PARPORT - fi -fi -if [ "$CONFIG_PARPORT" != "n" ]; then - if [ "$CONFIG_PARPORT_1284" != "n" ]; then - dep_tristate ' W9966CF Webcam (FlyCam Supra and others) Video For Linux' CONFIG_VIDEO_W9966 $CONFIG_VIDEO_DEV $CONFIG_PARPORT - fi -fi -dep_tristate ' CPiA Video For Linux' CONFIG_VIDEO_CPIA $CONFIG_VIDEO_DEV -if [ "$CONFIG_VIDEO_CPIA" != "n" ]; then - if [ "$CONFIG_PARPORT_1284" != "n" ]; then - dep_tristate ' CPiA Parallel Port Lowlevel Support' CONFIG_VIDEO_CPIA_PP $CONFIG_VIDEO_CPIA $CONFIG_PARPORT - fi - if [ "$CONFIG_USB" != "n" ]; then - dep_tristate ' CPiA USB Lowlevel Support' CONFIG_VIDEO_CPIA_USB $CONFIG_VIDEO_CPIA $CONFIG_USB - fi -fi -dep_tristate ' SAA5249 Teletext processor' CONFIG_VIDEO_SAA5249 $CONFIG_VIDEO_DEV $CONFIG_I2C -dep_tristate ' SAB3036 tuner' CONFIG_TUNER_3036 $CONFIG_VIDEO_DEV $CONFIG_I2C -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - if [ "$CONFIG_SGI" = "y" ]; then - dep_tristate ' SGI Vino Video For Linux (EXPERIMENTAL)' CONFIG_VIDEO_VINO $CONFIG_VIDEO_DEV $CONFIG_SGI - fi - dep_tristate ' Stradis 4:2:2 MPEG-2 video driver (EXPERIMENTAL)' CONFIG_VIDEO_STRADIS $CONFIG_VIDEO_DEV $CONFIG_PCI -fi -dep_tristate ' Zoran ZR36057/36060 Video For Linux' CONFIG_VIDEO_ZORAN $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C -dep_tristate ' Iomega Buz support' CONFIG_VIDEO_ZORAN_BUZ $CONFIG_VIDEO_ZORAN $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C -dep_tristate ' Miro DC10(+) support' CONFIG_VIDEO_ZORAN_DC10 $CONFIG_VIDEO_ZORAN $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C -dep_tristate ' Linux Media Labs LML33 support' CONFIG_VIDEO_ZORAN_LML33 $CONFIG_VIDEO_ZORAN $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C -dep_tristate ' Zoran ZR36120/36125 Video For Linux' CONFIG_VIDEO_ZR36120 $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' Sony Vaio Picturebook Motion Eye Video For Linux (EXPERIMENTAL)' CONFIG_VIDEO_MEYE $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_SONYPI -fi - -endmenu diff --git a/drivers/message/fusion/Config.help b/drivers/message/fusion/Config.help deleted file mode 100644 index 53204e11c7c0..000000000000 --- a/drivers/message/fusion/Config.help +++ /dev/null @@ -1,130 +0,0 @@ -CONFIG_FUSION - 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. - <Y> = build lib (fusion.o), and link [static] into the kernel [2] - proper - <M> = compiled as [dynamic] modules [3] named: (mptbase.o, - mptscsih.o) - - [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 - <file:Documentation/modules.txt>. - - 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: - <M> Enhanced SCSI error reporting (isense.o) - <M> Fusion MPT misc device (ioctl) driver (mptctl.o) - <M> Fusion MPT LAN driver (mptlan.o) - - --- - Fusion MPT is trademark of LSI Logic Corporation, and its - architecture is based on LSI Logic's Message Passing Interface (MPI) - specification. - -Maximum number of scatter gather entries -CONFIG_FUSION_MAX_SGE - This option allows you to specify the maximum number of scatter- - gather entries per I/O. The driver defaults to 40, a reasonable number - for most systems. However, the user may increase this up to 128. - Increasing this parameter will require significantly more memory - on a per controller instance. Increasing the parameter is not - necessary (or recommended) unless the user will be running - large I/O's via the raw interface. - -CONFIG_FUSION_ISENSE - 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.o. - - NOTE: Support for building this feature into the kernel is not - available, due to kernel size considerations. - -CONFIG_FUSION_CTL - 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.o - will be compiled. - - If unsure whether you really want or need this, say N. - -CONFIG_FUSION_LAN - 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.o - 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. - -CONFIG_NET_FC - 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". - diff --git a/drivers/message/fusion/Config.in b/drivers/message/fusion/Config.in deleted file mode 100644 index 39274207f6f4..000000000000 --- a/drivers/message/fusion/Config.in +++ /dev/null @@ -1,38 +0,0 @@ -mainmenu_option next_comment -comment 'Fusion MPT device support' - -dep_tristate "Fusion MPT (base + ScsiHost) drivers" CONFIG_FUSION $CONFIG_SCSI $CONFIG_BLK_DEV_SD - -if [ "$CONFIG_FUSION" = "y" -o "$CONFIG_FUSION" = "m" ]; then - - if [ "$CONFIG_BLK_DEV_SD" = "y" -a "$CONFIG_FUSION" = "y" ]; then - define_bool CONFIG_FUSION_BOOT y - else - define_bool CONFIG_FUSION_BOOT n - fi - int " Maximum number of scatter gather entries" CONFIG_FUSION_MAX_SGE 40 - - if [ "$CONFIG_MODULES" = "y" ]; then - # How can we force these options to module or nothing? - dep_tristate " Enhanced SCSI error reporting" CONFIG_FUSION_ISENSE $CONFIG_FUSION m - dep_tristate " Fusion MPT misc device (ioctl) driver" CONFIG_FUSION_CTL $CONFIG_FUSION m - fi - - dep_tristate " Fusion MPT LAN driver" CONFIG_FUSION_LAN $CONFIG_FUSION $CONFIG_NET - if [ "$CONFIG_FUSION_LAN" != "n" ]; then - define_bool CONFIG_NET_FC y - fi - -else - - define_bool CONFIG_FUSION_BOOT n - # These <should> be define_tristate, but we leave them define_bool - # for backward compatibility with pre-linux-2.2.15 kernels. - # (Bugzilla:fibrebugs, #384) - define_bool CONFIG_FUSION_ISENSE n - define_bool CONFIG_FUSION_CTL n - define_bool CONFIG_FUSION_LAN n - -fi - -endmenu diff --git a/drivers/message/i2o/Config.help b/drivers/message/i2o/Config.help deleted file mode 100644 index 9093e746e67e..000000000000 --- a/drivers/message/i2o/Config.help +++ /dev/null @@ -1,71 +0,0 @@ -CONFIG_I2O - 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 - <file:Documentation/modules.txt>. You will get modules called - i2o_core.o and i2o_config.o. - - If unsure, say N. - -CONFIG_I2O_PCI - 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.o ( = 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>. - -CONFIG_I2O_BLOCK - 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.o ( = - 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>. - -CONFIG_I2O_LAN - Include support for the LAN OSM. You will also need to include - support for token ring or FDDI if you wish to use token ring or FDDI - I2O cards with this driver. - - This support is also available as a module called i2o_lan.o ( = 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>. - -CONFIG_I2O_SCSI - 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.o ( = - 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>. - -CONFIG_I2O_PROC - 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.o ( = - 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>. - diff --git a/drivers/message/i2o/Config.in b/drivers/message/i2o/Config.in deleted file mode 100644 index f324f074dc0c..000000000000 --- a/drivers/message/i2o/Config.in +++ /dev/null @@ -1,16 +0,0 @@ -mainmenu_option next_comment -comment 'I2O device support' - -tristate 'I2O support' CONFIG_I2O - -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate ' I2O PCI support' CONFIG_I2O_PCI $CONFIG_I2O -fi -dep_tristate ' I2O Block OSM' CONFIG_I2O_BLOCK $CONFIG_I2O -if [ "$CONFIG_NET" = "y" ]; then - dep_tristate ' I2O LAN OSM' CONFIG_I2O_LAN $CONFIG_I2O -fi -dep_tristate ' I2O SCSI OSM' CONFIG_I2O_SCSI $CONFIG_I2O $CONFIG_SCSI -dep_tristate ' I2O /proc support' CONFIG_I2O_PROC $CONFIG_I2O - -endmenu diff --git a/drivers/misc/Config.in b/drivers/misc/Config.in deleted file mode 100644 index 944e94ec629b..000000000000 --- a/drivers/misc/Config.in +++ /dev/null @@ -1,7 +0,0 @@ -# -# Misc strange devices -# -mainmenu_option next_comment -comment 'Misc devices' - -endmenu diff --git a/drivers/mtd/Config.help b/drivers/mtd/Config.help deleted file mode 100644 index 83e9b5c7d44b..000000000000 --- a/drivers/mtd/Config.help +++ /dev/null @@ -1,160 +0,0 @@ -CONFIG_MTD - 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. - -CONFIG_MTD_DEBUG - This turns on low-level debugging for the entire MTD sub-system. - Normally, you should say 'N'. - -CONFIG_MTD_PARTITIONS - 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. - -CONFIG_MTD_CONCAT - 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'. - -CONFIG_MTD_REDBOOT_PARTS - 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. - -CONFIG_MTD_CMDLINE_PARTS - 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=<mtddef>[;<mtddef] - <mtddef> := <mtd-id>:<partdef>[,<partdef>] - <partdef> := <size>[@offset][<name>][ro] - <mtd-id> := unique id used in mapping driver/device - <size> := standard linux memsize OR "-" to denote all - remaining space - <name> := (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'. - -CONFIG_MTD_AFS_PARTS - 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. - -CONFIG_MTD_DEBUG_VERBOSE - Determines the verbosity level of the MTD debugging messages. - -CONFIG_MTD_CHAR - 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. - -CONFIG_MTD_BLOCK - 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. - -CONFIG_MTD_BLOCK_RO - 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. - -CONFIG_FTL - 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. - -CONFIG_NFTL - 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. - -CONFIG_NFTL_RW - If you're lucky, this will actually work. Don't whinge if it - doesn't. Send mail to the MTD mailing list - <linux-mtd@lists.infradead.org> if you want to help to make it more - reliable. - diff --git a/drivers/mtd/Config.in b/drivers/mtd/Config.in deleted file mode 100644 index 7e3d3ffd2983..000000000000 --- a/drivers/mtd/Config.in +++ /dev/null @@ -1,44 +0,0 @@ - -# $Id: Config.in,v 1.74 2002/04/23 13:52:14 mag Exp $ - -mainmenu_option next_comment -comment 'Memory Technology Devices (MTD)' - -tristate 'Memory Technology Device (MTD) support' CONFIG_MTD - -if [ "$CONFIG_MTD" = "y" -o "$CONFIG_MTD" = "m" ]; then - bool 'Debugging' CONFIG_MTD_DEBUG - if [ "$CONFIG_MTD_DEBUG" = "y" ]; then - int ' Debugging verbosity (0 = quiet, 3 = noisy)' CONFIG_MTD_DEBUG_VERBOSE 0 - fi - dep_tristate ' MTD partitioning support' CONFIG_MTD_PARTITIONS $CONFIG_MTD - dep_tristate ' MTD concatenating support' CONFIG_MTD_CONCAT $CONFIG_MTD - dep_tristate ' RedBoot partition table parsing' CONFIG_MTD_REDBOOT_PARTS $CONFIG_MTD_PARTITIONS - dep_tristate ' Command line partition table parsing' CONFIG_MTD_CMDLINE_PARTS $CONFIG_MTD_PARTITIONS - if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' ARM Firmware Suite partition parsing' CONFIG_MTD_AFS_PARTS $CONFIG_MTD_PARTITIONS - fi - -comment 'User Modules And Translation Layers' - dep_tristate ' Direct char device access to MTD devices' CONFIG_MTD_CHAR $CONFIG_MTD - dep_tristate ' Caching block device access to MTD devices' CONFIG_MTD_BLOCK $CONFIG_MTD - if [ "$CONFIG_MTD_BLOCK" = "n" -o "$CONFIG_MTD_BLOCK" = "m" ]; then - dep_tristate ' Readonly block device access to MTD devices' CONFIG_MTD_BLOCK_RO $CONFIG_MTD - fi - dep_tristate ' FTL (Flash Translation Layer) support' CONFIG_FTL $CONFIG_MTD - dep_tristate ' NFTL (NAND Flash Translation Layer) support' CONFIG_NFTL $CONFIG_MTD - if [ "$CONFIG_NFTL" = "y" -o "$CONFIG_NFTL" = "m" ]; then - bool ' Write support for NFTL (BETA)' CONFIG_NFTL_RW - fi - - source drivers/mtd/chips/Config.in - - source drivers/mtd/maps/Config.in - - source drivers/mtd/devices/Config.in - - source drivers/mtd/nand/Config.in - -fi - -endmenu diff --git a/drivers/mtd/chips/Config.help b/drivers/mtd/chips/Config.help deleted file mode 100644 index 854560690aae..000000000000 --- a/drivers/mtd/chips/Config.help +++ /dev/null @@ -1,130 +0,0 @@ -CONFIG_MTD_CFI - 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 <http://www.amd.com/products/nvd/overview/cfi.html> - for more information on CFI. - -CONFIG_MTD_CFI_ADV_OPTIONS - 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'. - -CONFIG_MTD_CFI_GEOMETRY - 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. - -CONFIG_MTD_CFI_B1 - If you wish to support CFI devices on a physical bus which is - 8 bits wide, say 'Y'. - -CONFIG_MTD_CFI_B2 - If you wish to support CFI devices on a physical bus which is - 16 bits wide, say 'Y'. - -CONFIG_MTD_CFI_B4 - If you wish to support CFI devices on a physical bus which is - 32 bits wide, say 'Y'. - -CONFIG_MTD_CFI_I1 - If your flash chips are not interleaved - i.e. you only have one - flash chip addressed by each bus cycle, then say 'Y'. - -CONFIG_MTD_CFI_I2 - If your flash chips are interleaved in pairs - i.e. you have two - flash chips addressed by each bus cycle, then say 'Y'. - -CONFIG_MTD_CFI_I4 - If your flash chips are interleaved in fours - i.e. you have four - flash chips addressed by each bus cycle, then say 'Y'. - -CONFIG_MTD_CFI_NOSWAP - This option defines the way in which the CPU attempts to arrange - data bits when writing the 'magic' commands to the chips. Saying - 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't - enabled, means that the CPU will not do any swapping; the chips - are expected to be wired to the CPU in 'host-endian' form. - Specific arrangements are possible with the BIG_ENDIAN_BYTE and - LITTLE_ENDIAN_BYTE, if the bytes are reversed. - - If you have a LART, on which the data (and address) lines were - connected in a fashion which ensured that the nets were as short - as possible, resulting in a bit-shuffling which seems utterly - random to the untrained eye, you need the LART_ENDIAN_BYTE option. - - Yes, there really exists something sicker than PDP-endian :) - -CONFIG_MTD_CFI_INTELEXT - 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. - -CONFIG_MTD_CFI_AMDSTD - 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 - chips including the AMD Am29LV320. - -CONFIG_MTD_SHARP - 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. - -CONFIG_MTD_AMDSTD - 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. - -CONFIG_MTD_RAM - This option enables basic support for RAM chips accessed through - a bus mapping driver. - -CONFIG_MTD_ROM - This option enables basic support for ROM chips accessed through - a bus mapping driver. - -CONFIG_MTD_JEDEC - 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 - <http://www.jedec.org/> distributes the identification codes for the - chips. WARNING!!!! This code does not compile and is incomplete as - are the specific JEDEC devices drivers. - -CONFIG_MTD_ABSENT - 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. - -CONFIG_MTD_JEDECPROBE - 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) - -CONFIG_MTD_OBSOLETE_CHIPS - 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_JEDEC_PROBE 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_JEDEC_PROBE method and reported its failure - to the MTD mailing list at <linux-mtd@lists.infradead.org> - diff --git a/drivers/mtd/chips/Config.in b/drivers/mtd/chips/Config.in deleted file mode 100644 index 5767a5110242..000000000000 --- a/drivers/mtd/chips/Config.in +++ /dev/null @@ -1,57 +0,0 @@ -# drivers/mtd/chips/Config.in - -# $Id: Config.in,v 1.12 2001/09/23 15:35:21 dwmw2 Exp $ - -mainmenu_option next_comment - -comment 'RAM/ROM/Flash chip drivers' - -dep_tristate ' Detect flash chips by Common Flash Interface (CFI) probe' CONFIG_MTD_CFI $CONFIG_MTD -#dep_tristate ' Detect non-CFI Intel-compatible flash chips' CONFIG_MTD_INTELPROBE $CONFIG_MTD -dep_tristate ' Detect non-CFI AMD/JEDEC-compatible flash chips' CONFIG_MTD_JEDECPROBE $CONFIG_MTD - -if [ "$CONFIG_MTD_CFI" = "y" -o "$CONFIG_MTD_INTELPROBE" = "y" -o "$CONFIG_MTD_JEDECPROBE" = "y" ]; then - define_bool CONFIG_MTD_GEN_PROBE y -else - if [ "$CONFIG_MTD_CFI" = "m" -o "$CONFIG_MTD_INTELPROBE" = "m" -o "$CONFIG_MTD_JEDECPROBE" = "m" ]; then - define_bool CONFIG_MTD_GEN_PROBE m - else - define_bool CONFIG_MTD_GEN_PROBE n - fi -fi -if [ "$CONFIG_MTD_GEN_PROBE" = "y" -o "$CONFIG_MTD_GEN_PROBE" = "m" ]; then - bool ' Flash chip driver advanced configuration options' CONFIG_MTD_CFI_ADV_OPTIONS - if [ "$CONFIG_MTD_CFI_ADV_OPTIONS" = "y" ]; then - choice 'Flash cmd/query data swapping' \ - "NO CONFIG_MTD_CFI_NOSWAP \ - BIG_ENDIAN_BYTE CONFIG_MTD_CFI_BE_BYTE_SWAP \ - LITTLE_ENDIAN_BYTE CONFIG_MTD_CFI_LE_BYTE_SWAP" NO - bool ' Specific CFI Flash geometry selection' CONFIG_MTD_CFI_GEOMETRY - if [ "$CONFIG_MTD_CFI_GEOMETRY" = "y" ]; then - bool ' Support 8-bit buswidth' CONFIG_MTD_CFI_B1 - bool ' Support 16-bit buswidth' CONFIG_MTD_CFI_B2 - bool ' Support 32-bit buswidth' CONFIG_MTD_CFI_B4 - if [ "$CONFIG_MTD_CFI_B1" = "y" ]; then - define_bool CONFIG_MTD_CFI_I1 y - else - bool ' Support 1-chip flash interleave' CONFIG_MTD_CFI_I1 - fi - bool ' Support 2-chip flash interleave' CONFIG_MTD_CFI_I2 - bool ' Support 4-chip flash interleave' CONFIG_MTD_CFI_I4 - fi - fi -fi -dep_tristate ' Support for Intel/Sharp flash chips' CONFIG_MTD_CFI_INTELEXT $CONFIG_MTD_GEN_PROBE -dep_tristate ' Support for AMD/Fujitsu flash chips' CONFIG_MTD_CFI_AMDSTD $CONFIG_MTD_GEN_PROBE - -dep_tristate ' Support for RAM chips in bus mapping' CONFIG_MTD_RAM $CONFIG_MTD -dep_tristate ' Support for ROM chips in bus mapping' CONFIG_MTD_ROM $CONFIG_MTD -dep_tristate ' Support for absent chips in bus mapping' CONFIG_MTD_ABSENT $CONFIG_MTD - -bool ' Older (theoretically obsoleted now) drivers for non-CFI chips' CONFIG_MTD_OBSOLETE_CHIPS -dep_tristate ' AMD compatible flash chip support (non-CFI)' CONFIG_MTD_AMDSTD $CONFIG_MTD $CONFIG_MTD_OBSOLETE_CHIPS -dep_tristate ' pre-CFI Sharp chip support' CONFIG_MTD_SHARP $CONFIG_MTD $CONFIG_MTD_OBSOLETE_CHIPS -dep_tristate ' JEDEC device support' CONFIG_MTD_JEDEC $CONFIG_MTD $CONFIG_MTD_OBSOLETE_CHIPS - - -endmenu diff --git a/drivers/mtd/devices/Config.help b/drivers/mtd/devices/Config.help deleted file mode 100644 index 1604a1eb6e0f..000000000000 --- a/drivers/mtd/devices/Config.help +++ /dev/null @@ -1,137 +0,0 @@ -CONFIG_MTD_DOC1000 - This provides an MTD device driver for the M-Systems DiskOnChip - 1000 devices, which are obsolete so you probably want to say 'N'. - -CONFIG_MTD_DOC2000 - 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 <file:drivers/mtd/devices/docprobe.c> 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. - -CONFIG_MTD_DOC2001 - 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 <file:drivers/mtd/devices/docprobe.c>. - - 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. - -CONFIG_MTD_DOCPROBE - This isn't a real config option, it's derived. - -CONFIG_MTD_DOCPROBE_ADVANCED - 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'. - -CONFIG_MTD_DOCPROBE_55AA - 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. - -CONFIG_MTD_DOCPROBE_ADDRESS - By default, the probe for DiskOnChip devices will look for a - DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. - This option allows you to specify a single address at which to probe - for the device, which is useful if you have other devices in that - range which get upset when they are probed. - - (Note that on PowerPC, the normal probe will only check at - 0xE4000000.) - - Normally, you should leave this set to zero, to allow the probe at - the normal addresses. - -CONFIG_MTD_DOCPROBE_HIGH - 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'. - -CONFIG_MTD_PMC551 - This provides a MTD device driver for the Ramix PMC551 RAM PCI card - from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>. - 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. - -CONFIG_MTD_PMC551_BUGFIX - 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. - -CONFIG_MTD_PMC551_DEBUG - 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. - -CONFIG_MTD_SLRAM - 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. - -CONFIG_MTD_MTDRAM - This enables a test MTD device driver which uses vmalloc() to - provide storage. You probably want to say 'N' unless you're - testing stuff. - -CONFIG_MTDRAM_ERASE_SIZE - This allows you to configure the size of the erase blocks in the - device emulated by the MTDRAM driver. If the MTDRAM driver is built - as a module, it is also possible to specify this as a parameter when - loading the module. - -CONFIG_MTDRAM_TOTAL_SIZE - This allows you to configure the total size of the MTD device - emulated by the MTDRAM driver. If the MTDRAM driver is built - as a module, it is also possible to specify this as a parameter when - loading the module. - -CONFIG_MTDRAM_ABS_POS - If you have system RAM accessible by the CPU but not used by Linux - in normal operation, you can give the physical address at which the - available RAM starts, and the MTDRAM driver will use it instead of - allocating space from Linux's available memory. Otherwise, leave - this set to zero. Most people will want to leave this as zero. - -CONFIG_MTD_BLKMTD - 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). - -CONFIG_MTD_LART - 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 (: - diff --git a/drivers/mtd/devices/Config.in b/drivers/mtd/devices/Config.in deleted file mode 100644 index 2e24a7d3e0d3..000000000000 --- a/drivers/mtd/devices/Config.in +++ /dev/null @@ -1,55 +0,0 @@ -# drivers/mtd/maps/Config.in - -# $Id: Config.in,v 1.5 2001/09/23 15:33:10 dwmw2 Exp $ - -mainmenu_option next_comment - -comment 'Self-contained MTD device drivers' -dep_tristate ' Ramix PMC551 PCI Mezzanine RAM card support' CONFIG_MTD_PMC551 $CONFIG_MTD $CONFIG_PCI -if [ "$CONFIG_MTD_PMC551" = "y" -o "$CONFIG_MTD_PMC551" = "m" ]; then - bool ' PMC551 256M DRAM Bugfix' CONFIG_MTD_PMC551_BUGFIX - bool ' PMC551 Debugging' CONFIG_MTD_PMC551_DEBUG -fi -dep_tristate ' Uncached system RAM' CONFIG_MTD_SLRAM $CONFIG_MTD -if [ "$CONFIG_SA1100_LART" = "y" ]; then - dep_tristate ' 28F160xx flash driver for LART' CONFIG_MTD_LART $CONFIG_MTD -fi -dep_tristate ' Test driver using RAM' CONFIG_MTD_MTDRAM $CONFIG_MTD -if [ "$CONFIG_MTD_MTDRAM" = "y" -o "$CONFIG_MTD_MTDRAM" = "m" ]; then - int 'MTDRAM device size in KiB' CONFIG_MTDRAM_TOTAL_SIZE 4096 - int 'MTDRAM erase block size in KiB' CONFIG_MTDRAM_ERASE_SIZE 128 - if [ "$CONFIG_MTD_MTDRAM" = "y" ]; then #If not a module (I don't want to test it as a module) - hex 'SRAM Hexadecimal Absolute position or 0' CONFIG_MTDRAM_ABS_POS 0 - fi -fi -dep_tristate ' MTD emulation using block device' CONFIG_MTD_BLKMTD $CONFIG_MTD - -comment 'Disk-On-Chip Device Drivers' - dep_tristate ' M-Systems Disk-On-Chip 1000' CONFIG_MTD_DOC1000 $CONFIG_MTD - dep_tristate ' M-Systems Disk-On-Chip 2000 and Millennium' CONFIG_MTD_DOC2000 $CONFIG_MTD - dep_tristate ' M-Systems Disk-On-Chip Millennium-only alternative driver (see help)' CONFIG_MTD_DOC2001 $CONFIG_MTD - if [ "$CONFIG_MTD_DOC2001" = "y" -o "$CONFIG_MTD_DOC2000" = "y" ]; then - define_bool CONFIG_MTD_DOCPROBE y - else - if [ "$CONFIG_MTD_DOC2001" = "m" -o "$CONFIG_MTD_DOC2000" = "m" ]; then - define_bool CONFIG_MTD_DOCPROBE m - else - define_bool CONFIG_MTD_DOCPROBE n - fi - fi - - if [ "$CONFIG_MTD_DOCPROBE" = "y" -o "$CONFIG_MTD_DOCPROBE" = "m" ]; then - bool ' Advanced detection options for DiskOnChip' CONFIG_MTD_DOCPROBE_ADVANCED - if [ "$CONFIG_MTD_DOCPROBE_ADVANCED" = "n" ]; then - define_hex CONFIG_MTD_DOCPROBE_ADDRESS 0 - define_bool CONFIG_MTD_DOCPROBE_HIGH n - define_bool CONFIG_MTD_DOCPROBE_55AA n - else - hex ' Physical address of DiskOnChip' CONFIG_MTD_DOCPROBE_ADDRESS 0x0000 - bool ' Probe high addresses' CONFIG_MTD_DOCPROBE_HIGH - bool ' Probe for 0x55 0xAA BIOS Extension Signature' CONFIG_MTD_DOCPROBE_55AA - fi - fi - - -endmenu diff --git a/drivers/mtd/maps/Config.help b/drivers/mtd/maps/Config.help deleted file mode 100644 index d4cc1af6505e..000000000000 --- a/drivers/mtd/maps/Config.help +++ /dev/null @@ -1,220 +0,0 @@ -CONFIG_MTD_CDB89712 - This enables access to the flash or ROM chips on the CDB89712 board. - If you have such a board, say 'Y'. - -CONFIG_MTD_CEIVA - This enables access to the flash chips on the Ceiva/Polaroid - PhotoMax Digital Picture Frame. - If you have such a device, say 'Y'. - -CONFIG_MTD_FORTUNET - This enables access to the Flash on the FortuNet board. If you - have such a board, say 'Y'. - -CONFIG_MTD_AUTCPU12 - This enables access to the NV-RAM on autronix autcpu12 board. - If you have such a board, say 'Y'. - -CONFIG_MTD_EDB7312 - This enables access to the CFI Flash on the Cogent EDB7312 board. - If you have such a board, say 'Y' here. - -CONFIG_MTD_NAND_EDB7312 - This enables access to the NAND Flash on the Cogent EDB7312 board. - If you have such a board, say 'Y' here. - -CONFIG_MTD_IMPA7 - This enables access to the NOR Flash on the impA7 board of - implementa GmbH. If you have such a board, say 'Y' here. - -CONFIG_MTD_SA1100 - 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'. - -CONFIG_MTD_PHYSMAP - 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. - -CONFIG_MTD_PHYSMAP_START - This is the physical memory location at which the flash chips - are mapped on your particular target board. Refer to the - memory map which should hopefully be in the documentation for - your board. - -CONFIG_MTD_PHYSMAP_LEN - This is the total length of the mapping of the flash chips on - your particular board. If there is space, or aliases, in the - physical memory map between the chips, this could be larger - than the total amount of flash present. Refer to the memory - map which should hopefully be in the documentation for your - board. - -CONFIG_MTD_PHYSMAP_BUSWIDTH - This is the total width of the data bus of the flash devices - in octets. For example, if you have a data bus width of 32 - bits, you would set the bus width octect value to 4. This is - used internally by the CFI drivers. - -CONFIG_MTD_SUN_UFLASH - 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. - -CONFIG_MTD_NORA - If you had to ask, you don't have one. Say 'N'. - -CONFIG_MTD_L440GX - 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. - -CONFIG_MTD_PNC2000 - PNC-2000 is the name of Network Camera product from PHOTRON - Ltd. in Japan. It uses CFI-compliant flash. - -CONFIG_MTD_RPXLITE - 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 - <http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm>. - -CONFIG_MTD_TQM8XXL - 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 - <http://www.denx.de/embedded-ppc-en.html>. - -CONFIG_MTD_SC520CDP - 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. - -CONFIG_MTD_SBC_GXX - 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 - <http://www.arcomcontrols.com/products/icp/pc104/processors/>. - -CONFIG_MTD_DBOX2 - 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'. - -CONFIG_MTD_IQ80310 - 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'. - -CONFIG_MTD_NETSC520 - 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'. - -CONFIG_MTD_OCELOT - 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'. - -CONFIG_MTD_ELAN_104NC - 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 - <http://www.arcomcontrols.com/products/icp/pc104/processors/>. - -CONFIG_MTD_DC21285 - This provides a driver for the flash accessed using Intel's - 21285 bridge used with Intel's StrongARM processors. More info at - <http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm>. - -CONFIG_MTD_CSTM_MIPS_IXX - 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. - -CONFIG_MTD_CSTM_MIPS_IXX_START - This is the physical memory location that the MTD driver will - use for the flash chips on your particular target board. - Refer to the memory map which should hopefully be in the - documentation for your board. - -CONFIG_MTD_CSTM_MIPS_IXX_LEN - This is the total length that the MTD driver will use for the - flash chips on your particular board. Refer to the memory - map which should hopefully be in the documentation for your - board. - -CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH - This is the total bus width of the mapping of the flash chips - on your particular board. - -CONFIG_MTD_MIXMEM - This supports the paging arrangement for access to flash chips - on the MixCOM piggyback card, allowing the flash chip drivers - to get on with their job of driving the flash chips without - having to know about the paging. If you have one of these boards, - you probably want to enable this mapping driver. More info is at - <http://www.itc.hu/>. - -CONFIG_MTD_SCx200_DOCFLASH - 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.o. - -CONFIG_MTD_OCTAGON - 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 - <http://www.octagonsystems.com/Products/5066/5066.html>. - -CONFIG_MTD_PCMCIA - 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. - -CONFIG_MTD_VMAX - 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 - <http://www.tempustech.com/tt301.htm>. - -CONFIG_MTD_CFI_FLAGADM - Mapping for the Flaga digital module. If you don´t have one, ignore - this setting. - -CONFIG_MTD_SOLUTIONENGINE - 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. - -CONFIG_MTD_EPXA10DB - 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'. - -CONFIG_MTD_PCI - 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. diff --git a/drivers/mtd/maps/Config.in b/drivers/mtd/maps/Config.in deleted file mode 100644 index e0668372fa79..000000000000 --- a/drivers/mtd/maps/Config.in +++ /dev/null @@ -1,73 +0,0 @@ -# drivers/mtd/maps/Config.in - -# $Id: Config.in,v 1.16 2001/09/19 18:28:37 dwmw2 Exp $ - -mainmenu_option next_comment - -comment 'Mapping drivers for chip access' - -dep_tristate ' CFI Flash device in physical memory map' CONFIG_MTD_PHYSMAP $CONFIG_MTD_CFI -if [ "$CONFIG_MTD_PHYSMAP" = "y" -o "$CONFIG_MTD_PHYSMAP" = "m" ]; then - hex ' Physical start address of flash mapping' CONFIG_MTD_PHYSMAP_START 0x8000000 - hex ' Physical length of flash mapping' CONFIG_MTD_PHYSMAP_LEN 0x4000000 - int ' Bus width in octets' CONFIG_MTD_PHYSMAP_BUSWIDTH 2 -fi - -if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - dep_tristate ' Sun Microsystems userflash support' CONFIG_MTD_SUN_UFLASH $CONFIG_MTD_CFI -fi - -if [ "$CONFIG_X86" = "y" ]; then - dep_tristate ' CFI Flash device mapped on Photron PNC-2000' CONFIG_MTD_PNC2000 $CONFIG_MTD_CFI $CONFIG_MTD_PARTITIONS - dep_tristate ' CFI Flash device mapped on AMD SC520 CDP' CONFIG_MTD_SC520CDP $CONFIG_MTD_CFI - dep_tristate ' CFI Flash device mapped on AMD NetSc520' CONFIG_MTD_NETSC520 $CONFIG_MTD_CFI $CONFIG_MTD_PARTITIONS - dep_tristate ' CFI Flash device mapped on Arcom SBC-GXx boards' CONFIG_MTD_SBC_GXX $CONFIG_MTD_CFI_INTELEXT $CONFIG_MTD_PARTITIONS - dep_tristate ' CFI Flash device mapped on Arcom ELAN-104NC' CONFIG_MTD_ELAN_104NC $CONFIG_MTD_CFI_INTELEXT $CONFIG_MTD_PARTITIONS - dep_tristate ' JEDEC Flash device mapped on Mixcom piggyback card' CONFIG_MTD_MIXMEM $CONFIG_MTD_JEDEC - dep_tristate ' JEDEC Flash device mapped on Octagon 5066 SBC' CONFIG_MTD_OCTAGON $CONFIG_MTD_JEDEC - dep_tristate ' JEDEC Flash device mapped on Tempustech VMAX SBC301' CONFIG_MTD_VMAX $CONFIG_MTD_JEDEC - dep_tristate ' Flash device mapped with DOCCS on NatSemi SCx200' CONFIG_MTD_SCx200_DOCFLASH $CONFIG_MTD_CFI - dep_tristate ' BIOS flash chip on Intel L440GX boards' CONFIG_MTD_L440GX $CONFIG_MTD_JEDEC -fi - -if [ "$CONFIG_PPC" = "y" ]; then - dep_tristate ' CFI Flash device mapped on TQM8XXL' CONFIG_MTD_TQM8XXL $CONFIG_MTD_CFI $CONFIG_TQM8xxL $CONFIG_PPC - dep_tristate ' CFI Flash device mapped on RPX Lite or CLLF' CONFIG_MTD_RPXLITE $CONFIG_MTD_CFI $CONFIG_PPC - dep_tristate ' CFI Flash device mapped on D-Box2' CONFIG_MTD_DBOX2 $CONFIG_MTD_CFI_INTELSTD $CONFIG_MTD_CFI_INTELEXT $CONFIG_MTD_CFI_AMDSTD - dep_tristate ' CFI Flash device mapping on FlagaDM' CONFIG_MTD_CFI_FLAGADM $CONFIG_MTD_CFI -fi - -if [ "$CONFIG_MIPS" = "y" ]; then - dep_tristate ' Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board' CONFIG_MTD_CSTM_MIPS_IXX $CONFIG_MTD_CFI $CONFIG_MTD_JEDEC $CONFIG_MTD_PARTITIONS - if [ "$CONFIG_MTD_CSTM_MIPS_IXX" = "y" -o "$CONFIG_MTD_CSTM_MIPS_IXX" = "m" ]; then - hex ' Physical start address of flash mapping' CONFIG_MTD_CSTM_MIPS_IXX_START 0x8000000 - hex ' Physical length of flash mapping' CONFIG_MTD_CSTM_MIPS_IXX_LEN 0x4000000 - int ' Bus width in octets' CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH 2 - fi - dep_tristate ' Momenco Ocelot boot flash device' CONFIG_MTD_OCELOT $CONFIG_MOMENCO_OCELOT -fi - -if [ "$CONFIG_SUPERH" = "y" ]; then - dep_tristate ' CFI Flash device mapped on Hitachi SolutionEngine' CONFIG_MTD_SOLUTIONENGINE $CONFIG_MTD_CFI $CONFIG_MTD_REDBOOT_PARTS -fi - -if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' CFI Flash device mapped on Nora' CONFIG_MTD_NORA $CONFIG_MTD_CFI - dep_tristate ' CFI Flash device mapped on ARM Integrator/P720T' CONFIG_MTD_ARM_INTEGRATOR $CONFIG_MTD_CFI - dep_tristate ' Cirrus CDB89712 evaluation board mappings' CONFIG_MTD_CDB89712 $CONFIG_MTD_CFI $CONFIG_ARCH_CDB89712 - dep_tristate ' CFI Flash device mapped on StrongARM SA11x0' CONFIG_MTD_SA1100 $CONFIG_MTD_CFI $CONFIG_ARCH_SA1100 $CONFIG_MTD_PARTITIONS - dep_tristate ' CFI Flash device mapped on DC21285 Footbridge' CONFIG_MTD_DC21285 $CONFIG_MTD_CFI $CONFIG_ARCH_FOOTBRIDGE - dep_tristate ' CFI Flash device mapped on the XScale IQ80310 board' CONFIG_MTD_IQ80310 $CONFIG_MTD_CFI $CONFIG_ARCH_IQ80310 - dep_tristate ' CFI Flash device mapped on Epxa10db' CONFIG_MTD_EPXA10DB $CONFIG_MTD_CFI $CONFIG_MTD_PARTITIONS $CONFIG_ARCH_CAMELOT - dep_tristate ' CFI Flash device mapped on the FortuNet board' CONFIG_MTD_FORTUNET $CONFIG_MTD_CFI $CONFIG_MTD_PARTITIONS $CONFIG_SA1100_FORTUNET - dep_tristate ' NV-RAM mapping AUTCPU12 board' CONFIG_MTD_AUTCPU12 $CONFIG_ARCH_AUTCPU12 - dep_tristate ' CFI Flash device mapped on EDB7312' CONFIG_MTD_EDB7312 $CONFIG_MTD_CFI - dep_tristate ' JEDEC Flash device mapped on impA7' CONFIG_MTD_IMPA7 $CONFIG_MTD_JEDECPROBE - dep_tristate ' JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame' CONFIG_MTD_CEIVA $CONFIG_MTD_JEDECPROBE $CONFIG_ARCH_CEIVA -fi - -# This needs CFI or JEDEC, depending on the cards found. -dep_tristate ' PCI MTD driver' CONFIG_MTD_PCI $CONFIG_MTD $CONFIG_PCI -dep_tristate ' PCMCIA MTD driver' CONFIG_MTD_PCMCIA $CONFIG_MTD $CONFIG_PCMCIA - -endmenu diff --git a/drivers/mtd/nand/Config.help b/drivers/mtd/nand/Config.help deleted file mode 100644 index 4341dbf6b66d..000000000000 --- a/drivers/mtd/nand/Config.help +++ /dev/null @@ -1,21 +0,0 @@ -CONFIG_MTD_NAND - This enables support for accessing all type of NAND flash - devices. - -CONFIG_MTD_NAND_ECC - This enables software-based ECC for use with NAND flash chips. It - can detect and correct 1 bit errors per 256 byte blocks. This - should be used to increase the reliability of the data stored and - read on the device. - -CONFIG_MTD_NAND_VERIFY_WRITE - 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, gamma rays, whatever. - Enable this if you are really paranoid. - -CONFIG_MTD_NAND_SPIA - If you had to ask, you don't have one. Say 'N'. - diff --git a/drivers/mtd/nand/Config.in b/drivers/mtd/nand/Config.in deleted file mode 100644 index 29d7e585277f..000000000000 --- a/drivers/mtd/nand/Config.in +++ /dev/null @@ -1,18 +0,0 @@ -# drivers/mtd/nand/Config.in - -# $Id: Config.in,v 1.4 2001/09/19 09:35:23 dwmw2 Exp $ - -mainmenu_option next_comment - -comment 'NAND Flash Device Drivers' - -dep_tristate ' NAND Device Support' CONFIG_MTD_NAND $CONFIG_MTD -if [ "$CONFIG_MTD_NAND" = "y" -o "$CONFIG_MTD_NAND" = "m" ]; then - bool ' Enable ECC correction algorithm' CONFIG_MTD_NAND_ECC - bool ' Verify NAND page writes' CONFIG_MTD_NAND_VERIFY_WRITE -fi -if [ "$CONFIG_ARM" = "y" -a "$CONFIG_ARCH_P720T" = "y" ]; then - dep_tristate ' NAND Flash device on SPIA board' CONFIG_MTD_NAND_SPIA $CONFIG_MTD_NAND -fi - -endmenu diff --git a/drivers/net/Config.help b/drivers/net/Config.help deleted file mode 100644 index 66465083cc6f..000000000000 --- a/drivers/net/Config.help +++ /dev/null @@ -1,1821 +0,0 @@ -CONFIG_BAGETLANCE - 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. - -CONFIG_LASI_82596 - Say Y here to support the on-board Intel 82596 ethernet controller - built into Hewlett-Packard PA-RISC machines. - -CONFIG_MIPS_JAZZ_SONIC - This is the driver for the onboard card of MIPS Magnum 4000, - Acer PICA, Olivetti M700-10 and a few other identical OEM systems. - -CONFIG_MIPS_GT96100ETH - Say Y here to support the Ethernet subsystem on your GT96100 card. - -CONFIG_DUMMY - 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 - <http://www.linuxdoc.org/docs.html#guide>. - - 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 <file:Documentation/modules.txt>. The module - will be called dummy.o. 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. - -CONFIG_BONDING - 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 <file:Documentation/modules.txt>. The module - will be called bonding.o. - -CONFIG_SLIP - 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 - <ftp://ibiblio.org/pub/Linux/system/network/serial/>) 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 - <http://www.linuxdoc.org/docs.html#howto>, 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 - <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called slip.o. - -CONFIG_SLIP_COMPRESSED - 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 - <ftp://ibiblio.org/pub/Linux/system/network/serial/>) 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 - <http://www.linuxdoc.org/docs.html#howto>, explains how to configure - CSLIP. This won't enlarge your kernel. - -CONFIG_SLIP_SMART - Adds additional capabilities to the SLIP driver to support the - RELCOM line fill and keepalive monitoring. Ideal on poor quality - analogue lines. - -CONFIG_SLIP_MODE_SLIP6 - 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. - -CONFIG_PPP - PPP (Point to Point Protocol) is a newer and better SLIP. It serves - the same purpose: sending Internet traffic over telephone (and other - serial) lines. Ask your access provider if they support it, because - otherwise you can't use it; most Internet access providers these - days support PPP rather than SLIP. - - To use PPP, you need an additional program called pppd as described - in the PPP-HOWTO, available at - <http://www.linuxdoc.org/docs.html#howto>. Make sure that you have - the version of pppd recommended in <file:Documentation/Changes>. - The PPP option enlarges your kernel by about 16 KB. - - There are actually two versions of PPP: the traditional PPP for - asynchronous lines, such as regular analog phone lines, and - synchronous PPP which can be used over digital ISDN lines for - example. If you want to use PPP over phone lines or other - asynchronous serial lines, you need to say Y (or M) here and also to - the next option, "PPP support for async serial ports". For PPP over - synchronous lines, you should say Y (or M) here and to "Support - synchronous PPP", below. - - 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.o. - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. - -CONFIG_PPP_MULTILINK - 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. - -CONFIG_PPP_FILTER - 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. - -CONFIG_PPP_ASYNC - 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 <file:Documentation/modules.txt>. - - If unsure, say Y. - -CONFIG_PPP_SYNC_TTY - 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 - <file:Documentation/modules.txt>. - -CONFIG_PPP_DEFLATE - 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 - <file:Documentation/modules.txt>. - -CONFIG_PPP_BSDCOMP - 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.o and will show up in the directory - modules once you have said "make modules". If unsure, say N. - -CONFIG_PPPOE - Support for PPP over Ethernet. - - This driver requires a specially patched pppd daemon. The patch to - pppd, along with binaries of a patched pppd package can be found at: - <http://www.shoshin.uwaterloo.ca/~mostrows/>. - -CONFIG_PPPOATM - 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. - -CONFIG_NET_RADIO - 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 ifconfig 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 - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. - - Some user-level drivers for scarab devices which don't require - special kernel support are available from - <ftp://shadow.cabi.net/pub/Linux/>. - -CONFIG_STRIP - 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 <http://mosquitonet.stanford.edu/>) 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 <file:Documentation/modules.txt>. The module will be - called strip.o. - -CONFIG_ARLAN - 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 - <http://www.ylenurme.ee/~elmer/655/> 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. - -CONFIG_AIRONET4500 - www.aironet.com (recently bought by Cisco) makes these 802.11 DS - adapters. Driver by Elmer Joandi (elmer@ylenurme.ee). - - Say Y here if you have such an adapter, and then say Y below to - the option that applies to your particular type of card (PCI, ISA, - or PCMCIA). - - 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 aironet4500_core.o. If you want to - compile it as a module, say M here and read - <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. - - quick config parameters: - SSID=tsunami - "The Password" - adhoc=1 there are no Access Points around - master=1 Adhoc master (the one who creates network - sync) - slave=1 Adhoc slave (btw, it is still forming own net - sometimes, and has problems with firmware... - change IbssJoinNetTimeout from /proc...) - channel=1..? meaningful in adhoc mode - - If you have problems with screwing up card, both_bap_lock=1 is a - conservative value (performance hit 15%). - - All other parameters can be set via the proc interface. - -CONFIG_AIRONET4500_NONCS - If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN - card, say Y here, and then also to the options below that apply - to 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 aironet4500_card.o. If you want to - compile it as a module, say M here and read - <file:Documentation/modules.txt>. - -CONFIG_AIRONET4500_PNP - If you have an ISA Aironet 4500/4800 card which you want to use in - PnP (Plug and Play) mode, say Y here. This is the recommended mode - for ISA cards. Remember however to enable the PnP jumper on the - board if you say Y here. - -CONFIG_AIRONET4500_PCI - If you have an PCI Aironet 4500/4800 card, say Y here. - -CONFIG_AIRONET4500_ISA - If you have an ISA Aironet 4500/4800 card which you want to run in - non-PnP mode, say Y here. This is not recommended and does not work - correctly at this point. Say N. - -CONFIG_AIRONET4500_I365 - If you have a PCMCIA Aironet 4500/4800 card which you want to use - without the standard PCMCIA cardservices provided by the pcmcia-cs - package, say Y here. This is not recommended, so say N. - -CONFIG_AIRONET4500_PROC - If you say Y here (and to the "/proc file system" below), you will - be able to configure your Aironet card via the - /proc/sys/aironet4500 interface. - - Additional info: look in <file:drivers/net/aironet4500_rid.c>. - - 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 aironet4500_proc.o. If you want to - compile it as a module, say M here and read - <file:Documentation/modules.txt>. - - NOTE: the proc interface uses a lot of memory, so it is recommended - to compile it as a module and remove the module after - configuration. - -CONFIG_PLIP - 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 - <file:Documentation/networking/PLIP.txt>. 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 (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called plip.o. If unsure, say Y or M, in case you buy a laptop - later. - -CONFIG_EQUALIZER - 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 - <file:Documentation/networking/eql.txt>. You may also want to read - section 6.2 of the NET-3-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_TUN - 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 <file:Documentation/networking/tuntap.txt> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - If you don't know what to use this for, you don't need it. - -CONFIG_ETHERTAP - 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 - <file:Documentation/networking/ethertap.txt> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - If you don't know what to use this for, you don't need it. - -CONFIG_NET_FC - 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". - -CONFIG_IPHASE5526 - 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.o. For general information about - modules read <file:Documentation/modules.txt>. - -CONFIG_RCPCI - 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.o ( = 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>. - -CONFIG_NET_ETHERNET - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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. - -CONFIG_NET_VENDOR_SMC - If you have a network (Ethernet) card belonging to this class, say Y - and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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. - -CONFIG_WD80x3 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ULTRAMCA - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ULTRA - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ULTRA32 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_SMC9194 - 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 - <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NE2K_PCI - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NET_VENDOR_RACAL - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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. - -CONFIG_NI5010 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NI52 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NI65 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_8139CP - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. - -CONFIG_8139TOO - 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 - <file:Documentation/networking/8139too.txt> as well as the - Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called 8139too.o. - -CONFIG_8139TOO_PIO - 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. - -CONFIG_8139TOO_TUNE_TWISTER - 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. - -CONFIG_8139TOO_8129 - 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. - -CONFIG_8139_OLD_RX_RESET - 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. - -CONFIG_SIS900 - 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 - <http://www.linuxdoc.org/docs.html#howto>. Please read - <file:Documentation/networking/sis900.txt> and comments at the - beginning of <file:drivers/net/sis900.c> 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called sis900.o. - -CONFIG_YELLOWFIN - 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 - <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called yellowfin.o. - -CONFIG_NET_SB1000 - 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.o. Then read - <file:Documentation/networking/README.sb1000> 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: - - <http://www.jacksonville.net/~fventuri/> - <http://home.adelphia.net/~siglercm/sb1000.html> - <http://linuxpower.cx/~cable/> - - If you don't have this card, of course say N. - -CONFIG_ADAPTEC_STARFIRE - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called starfire.o. - -CONFIG_ACENIC - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called acenic.o. - -CONFIG_ACENIC_OMIT_TIGON_I - 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. - -CONFIG_SK98LIN - 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 - <file:Documentation/networking/sk98lin.txt> 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called sk98lin.o. - -CONFIG_SUNGEM - Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also - <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>. - -CONFIG_TIGON3 - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called tg3.o. - -CONFIG_MYRI_SBUS - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called myri_sbus.o. - -CONFIG_DL2K - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called dl2k.o. - -CONFIG_E1000 - 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 - 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: - - <http://support.intel.com/support/network/adapter/pro100/21397.htm> - - For general information and support, go to the Intel support - website at: - - <http://support.intel.com> - - More specific information on configuring the driver is in - <file:Documentation/networking/e1000.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_LANCE - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called lance.o. - -CONFIG_MIPS_AU1000_ENET - If you have an Alchemy Semi AU1000 ethernet controller - on an SGI MIPS system, say Y. Otherwise, say N. - -CONFIG_SGI_IOC3_ETH - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_STNIC - 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 - <http://www.national.com/pf/DP/DP83902A.html>. - - If unsure, say N. - -CONFIG_NET_VENDOR_3COM - If you have a network (Ethernet) card belonging to this class, say Y - and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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. - -CONFIG_EL1 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EL2 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ELPLUS - Information about this network (Ethernet) card can be found in - <file:Documentation/networking/3c505.txt>. If you have a card of - this type, say Y and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called 3c505.o. - -CONFIG_EL16 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ELMC - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ELMC_II - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EL3 - If you have a network (Ethernet) card belonging to the 3Com - EtherLinkIII series, say Y and read the Ethernet-HOWTO, available - from <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called 3c509.o. - -CONFIG_3C515 - If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet - network card, say Y and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called 3c515.o. - -CONFIG_VORTEX - 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 <http://www.linuxdoc.org/docs.html#howto>. More - specific information is in - <file:Documentation/networking/vortex.txt> and in the comments at - the beginning of <file:drivers/net/3c59x.c>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. - -CONFIG_NET_ISA - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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. - -CONFIG_E2100 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_CS89x0 - 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 - <http://www.linuxdoc.org/docs.html#howto> as well as - <file:Documentation/networking/cs89x0.txt>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called cs89x.o. - -CONFIG_DEPCA - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto> as well as - <file:drivers/net/depca.c>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called - depca.o. - -CONFIG_EWRK3 - This driver supports the DE203, DE204 and DE205 network (Ethernet) - cards. If this is for you, say Y and read - <file:Documentation/networking/ewrk3.txt> in the kernel source as - well as the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called ewrk3.o. - -CONFIG_SEEQ8005 - This is a driver for the SEEQ 8005 network (Ethernet) card. If this - is for you, read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called ewrk3.o. - -CONFIG_AT1700 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called at1700.o. - -CONFIG_FMV18X - If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card, - say Y and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EEXPRESS_PRO - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EEXPRESS - If you have an EtherExpress16 network (Ethernet) card, say Y and - read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called eexpress.o. - -CONFIG_HAMACHI - If you have a Gigabit Ethernet card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called hamachi.o. - -CONFIG_HPLAN_PLUS - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_HPLAN - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_HP100 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called hp100.o. - -CONFIG_NE2000 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NATSEMI - 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 - <http://www.scyld.com/network/natsemi.html>. - -CONFIG_SK_G16 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_NE2_MCA - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_SKMC - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_IBMLANA - 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 <file:Documentation/modules.txt> - as well as <file:Documentation/networking/net-modules.txt>. 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. - -CONFIG_NET_PCI - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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. - -CONFIG_PCNET32 - If you have a PCnet32 or PCnetPCI based network (Ethernet) card, - answer Y here and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_AC3200 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_LNE390 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_NE3210 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_APRICOT - If you have a network (Ethernet) controller of this type, say Y and - read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt> as well as - <file:Documentation/networking/net-modules.txt>. The module will be - called apricot.o. - -CONFIG_DGRS - 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 - <http://www.linuxdoc.org/docs.html#howto>. More specific - information is contained in <file:Documentation/networking/dgrs.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EEPRO100 - If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) - card, say Y and read the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_E100 - 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 - <file:Documentation/networking/e100.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_FEALNX - Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet - cards. Specifications and data at - <http://www.myson.com.hk/mtd/datasheet/>. - -CONFIG_LP486E - 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. - -CONFIG_ETH16I - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_TLAN - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - Devices currently supported by this driver are Compaq Netelligent, - Compaq NetFlex and Olicom cards. Please read the file - <file:Documentation/networking/tlan.txt> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - - Please email feedback to torben.mathiasen@compaq.com. - -CONFIG_VIA_RHINE - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_VIA_RHINE_MMIO - 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. - -CONFIG_ES3210 - If you have a network (Ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_EPIC100 - 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 - <http://www.scyld.com/network/epic100.html>. - -CONFIG_DECLANCE - 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.) - -CONFIG_SGISEEQ - Say Y here if you have an Seeq based Ethernet network card. This is - used in many Silicon Graphics machines. - -CONFIG_SUNDANCE - This driver is for the Sundance "Alta" chip. - More specific information and updates are available from - <http://www.scyld.com/network/sundance.html>. - -CONFIG_SUNDANCE_MMIO - 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. - -CONFIG_ZNET - 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 - <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_LAN_SAA9730 - The SAA9730 is a combined multimedia and peripheral controller used - in thin clients, Internet access terminals, and diskless - workstations. - See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>. - -CONFIG_NET_POCKET - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - 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 - <file:Documentation/Changes>) and you can say N here. - - Laptop users should read the Linux Laptop home page at - <http://www.cs.utexas.edu/users/kharker/linux-laptop/>. - - 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. - -CONFIG_ATP - This is a network (Ethernet) device which attaches to your parallel - port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>, 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 - <file:Documentation/modules.txt>. The module will be called atp.o. - -CONFIG_DE600 - This is a network (Ethernet) device which attaches to your parallel - port. Read <file:Documentation/networking/DLINK.txt> as well as the - Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, 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 - <file:Documentation/modules.txt>. - The module will be called de600.o. - -CONFIG_DE620 - This is a network (Ethernet) device which attaches to your parallel - port. Read <file:Documentation/networking/DLINK.txt> as well as the - Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, 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 - <file:Documentation/modules.txt>. - The module will be called de620.o. - -CONFIG_HAPPYMEAL - 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.o ( = 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>. - -CONFIG_SUNLANCE - 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.o ( = - 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>. - -CONFIG_SUNBMAC - 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.o ( = 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>. - -CONFIG_SUNQE - 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.o ( = 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>. - -CONFIG_SHAPER - 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 - <file:Documentation/networking/shaper.txt> 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 <ftp://shadow.cabi.net/pub/Linux/> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_FDDI - 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. - -CONFIG_DEFXX - This is support for the DIGITAL series of EISA (DEFEA) and PCI - (DEFPA) controllers which can connect you to a local FDDI network. - -CONFIG_SKFP - 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 <file:Documentation/networking/skfp.txt> 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called skfp.o. - -CONFIG_HIPPI - 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. - -CONFIG_ROADRUNNER - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_ROADRUNNER_LARGE_RINGS - 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. - -CONFIG_ARM_AM79C961A - If you wish to compile a kernel for the EBSA-110, then you should - always answer Y to this. - -CONFIG_ARIADNE - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_A2065 - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_HYDRA - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MACE - 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.o ( = 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>. - -CONFIG_MACE_AAUI_PORT - 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. - -CONFIG_BMAC - Say Y for support of BMAC Ethernet interfaces. These are used on G3 - computers. - - This driver is also available as a module called bmac.o ( = 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>. - -CONFIG_GMAC - Say Y for support of GMAC Ethernet interfaces. These are used on G4 - and iBook computers. - - This driver is also available as a module called gmac.o ( = 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>. - -CONFIG_OAKNET - Say Y if your machine has this type of Ethernet network card. - - This driver is also available as a module called oaknet.o ( = 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>. - -CONFIG_NS83820 - 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. - diff --git a/drivers/net/Config.in b/drivers/net/Config.in deleted file mode 100644 index eab594b51f33..000000000000 --- a/drivers/net/Config.in +++ /dev/null @@ -1,326 +0,0 @@ -# -# Network device configuration -# - -source drivers/net/arcnet/Config.in - -tristate 'Dummy net driver support' CONFIG_DUMMY -tristate 'Bonding driver support' CONFIG_BONDING -tristate 'EQL (serial line load balancing) support' CONFIG_EQUALIZER -tristate 'Universal TUN/TAP device driver support' CONFIG_TUN -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - tristate 'Ethertap network tap (OBSOLETE)' CONFIG_ETHERTAP -fi - -if [ "$CONFIG_ISAPNP" = "y" -o "$CONFIG_ISAPNP" = "m" ]; then - dep_tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 $CONFIG_ISAPNP -fi - -# -# Ethernet -# - -mainmenu_option next_comment -comment 'Ethernet (10 or 100Mbit)' -bool 'Ethernet (10 or 100Mbit)' CONFIG_NET_ETHERNET -if [ "$CONFIG_NET_ETHERNET" = "y" ]; then - if [ "$CONFIG_ARM" = "y" ]; then - dep_bool ' ARM EBSA110 AM79C961A support' CONFIG_ARM_AM79C961A $CONFIG_ARCH_EBSA110 - if [ "$CONFIG_ARCH_ACORN" = "y" ]; then - source drivers/acorn/net/Config.in - fi - fi - if [ "$CONFIG_PPC" = "y" ]; then - dep_tristate ' MACE (Power Mac ethernet) support' CONFIG_MACE $CONFIG_ALL_PPC - if [ "$CONFIG_MACE" != "n" ]; then - bool ' Use AAUI port instead of TP by default' CONFIG_MACE_AAUI_PORT - fi - dep_tristate ' BMAC (G3 ethernet) support' CONFIG_BMAC $CONFIG_ALL_PPC - tristate ' National DP83902AV (Oak ethernet) support' CONFIG_OAKNET - fi - if [ "$CONFIG_ZORRO" = "y" ]; then - tristate ' Ariadne support' CONFIG_ARIADNE - tristate ' Ariadne II and X-Surf support' CONFIG_NE2K_ZORRO - tristate ' A2065 support' CONFIG_A2065 - tristate ' Hydra support' CONFIG_HYDRA - fi - if [ "$CONFIG_PARISC" = "y" ]; then - dep_tristate ' Lasi ethernet' CONFIG_LASI_82596 $CONFIG_GSC_LASI - fi - if [ "$CONFIG_MIPS_JAZZ" = "y" ]; then - tristate ' MIPS JAZZ onboard SONIC Ethernet support' CONFIG_MIPS_JAZZ_SONIC - fi - if [ "$CONFIG_MIPS_GT96100" = "y" ]; then - bool ' MIPS GT96100 Ethernet support' CONFIG_MIPS_GT96100ETH - fi - if [ "$CONFIG_MIPS_AU1000" = "y" ]; then - bool ' MIPS AU1000 Ethernet support' CONFIG_MIPS_AU1000_ENET - fi - if [ "$CONFIG_SIBYTE_SB1250" = "y" ]; then - tristate ' SB1250 Ethernet support' CONFIG_NET_SB1250_MAC - fi - if [ "$CONFIG_SGI_IP27" = "y" ]; then - bool ' SGI IOC3 Ethernet' CONFIG_SGI_IOC3_ETH - fi - if [ "$CONFIG_IA64_SGI_SN1" = "y" ]; then - bool ' SGI IOC3 Ethernet' CONFIG_SGI_IOC3_ETH - fi - if [ "$CONFIG_SUPERH" = "y" ]; then - tristate ' National DP83902AV support' CONFIG_STNIC - fi - dep_tristate ' Sun LANCE support' CONFIG_SUNLANCE $CONFIG_SBUS - if [ "$CONFIG_SBUS" = "y" -o "$CONFIG_PCI" = "y" ]; then - tristate ' Sun Happy Meal 10/100baseT support' CONFIG_HAPPYMEAL - fi - dep_tristate ' Sun BigMAC 10/100baseT support (EXPERIMENTAL)' CONFIG_SUNBMAC $CONFIG_SBUS $CONFIG_EXPERIMENTAL - dep_tristate ' Sun QuadEthernet support' CONFIG_SUNQE $CONFIG_SBUS - dep_tristate ' Sun GEM support' CONFIG_SUNGEM $CONFIG_PCI - bool ' 3COM cards' CONFIG_NET_VENDOR_3COM - if [ "$CONFIG_NET_VENDOR_3COM" = "y" ]; then - dep_tristate ' 3c501 "EtherLink" support' CONFIG_EL1 $CONFIG_ISA - dep_tristate ' 3c503 "EtherLink II" support' CONFIG_EL2 $CONFIG_ISA - dep_tristate ' 3c505 "EtherLink Plus" support' CONFIG_ELPLUS $CONFIG_ISA - dep_tristate ' 3c507 "EtherLink 16" support (EXPERIMENTAL)' CONFIG_EL16 $CONFIG_ISA $CONFIG_EXPERIMENTAL - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - tristate ' 3c509/3c529 (MCA)/3c579 "EtherLink III" support' CONFIG_EL3 - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' 3c515 ISA "Fast EtherLink"' CONFIG_3C515 - fi - dep_tristate ' 3c523 "EtherLink/MC" support' CONFIG_ELMC $CONFIG_MCA - dep_tristate ' 3c527 "EtherLink/MC 32" support (EXPERIMENTAL)' CONFIG_ELMC_II $CONFIG_MCA $CONFIG_EXPERIMENTAL - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' 3c590/3c900 series (592/595/597) "Vortex/Boomerang" support' CONFIG_VORTEX - fi - fi - dep_tristate ' AMD LANCE and PCnet (AT1500 and NE2100) support' CONFIG_LANCE $CONFIG_ISA - bool ' Western Digital/SMC cards' CONFIG_NET_VENDOR_SMC - if [ "$CONFIG_NET_VENDOR_SMC" = "y" ]; then - dep_tristate ' WD80*3 support' CONFIG_WD80x3 $CONFIG_ISA - dep_tristate ' SMC Ultra MCA support' CONFIG_ULTRAMCA $CONFIG_MCA - dep_tristate ' SMC Ultra support' CONFIG_ULTRA $CONFIG_ISA - dep_tristate ' SMC Ultra32 EISA support' CONFIG_ULTRA32 $CONFIG_EISA - dep_tristate ' SMC 9194 support' CONFIG_SMC9194 $CONFIG_ISA - fi - bool ' Racal-Interlan (Micom) NI cards' CONFIG_NET_VENDOR_RACAL - if [ "$CONFIG_NET_VENDOR_RACAL" = "y" ]; then - dep_tristate ' NI5010 support (EXPERIMENTAL)' CONFIG_NI5010 $CONFIG_ISA $CONFIG_EXPERIMENTAL - dep_tristate ' NI5210 support' CONFIG_NI52 $CONFIG_ISA - dep_tristate ' NI6510 support' CONFIG_NI65 $CONFIG_ISA - fi - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_CARDBUS" != "n" ]; then - source drivers/net/tulip/Config.in - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - dep_tristate ' AT1700/1720 support (EXPERIMENTAL)' CONFIG_AT1700 $CONFIG_EXPERIMENTAL - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - tristate ' DEPCA, DE10x, DE200, DE201, DE202, DE422 support' CONFIG_DEPCA - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_PCI" = "y" ]; then - tristate ' HP 10/100VG PCLAN (ISA, EISA, PCI) support' CONFIG_HP100 - fi - dep_bool ' Other ISA cards' CONFIG_NET_ISA $CONFIG_ISA - if [ "$CONFIG_NET_ISA" = "y" ]; then - tristate ' Cabletron E21xx support' CONFIG_E2100 - tristate ' EtherWORKS 3 (DE203, DE204, DE205) support' CONFIG_EWRK3 - tristate ' EtherExpress 16 support' CONFIG_EEXPRESS - tristate ' EtherExpressPro support/EtherExpress 10 (i82595) support' CONFIG_EEXPRESS_PRO - if [ "$CONFIG_OBSOLETE" = "y" ]; then - tristate ' FMV-181/182/183/184 support (OBSOLETE)' CONFIG_FMV18X - fi - tristate ' HP PCLAN+ (27247B and 27252A) support' CONFIG_HPLAN_PLUS - tristate ' HP PCLAN (27245 and other 27xxx series) support' CONFIG_HPLAN - tristate ' LP486E on board Ethernet' CONFIG_LP486E - tristate ' ICL EtherTeam 16i/32 support' CONFIG_ETH16I - tristate ' NE2000/NE1000 support' CONFIG_NE2000 - dep_tristate ' Zenith Z-Note support (EXPERIMENTAL)' CONFIG_ZNET $CONFIG_EXPERIMENTAL - if [ "$CONFIG_OBSOLETE" = "y" ]; then - dep_tristate ' SEEQ8005 support (EXPERIMENTAL)' CONFIG_SEEQ8005 $CONFIG_EXPERIMENTAL - fi - if [ "$CONFIG_OBSOLETE" = "y" ]; then - tristate ' SK_G16 support (OBSOLETE)' CONFIG_SK_G16 - fi - fi - if [ "$CONFIG_MCA" = "y" ]; then - tristate ' SKnet MCA support' CONFIG_SKMC - tristate ' NE/2 (ne2000 MCA version) support' CONFIG_NE2_MCA - tristate ' IBM LAN Adapter/A support' CONFIG_IBMLANA - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_PCI" = "y" ]; then - bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI - else - define_bool CONFIG_NET_PCI n - fi - if [ "$CONFIG_NET_PCI" = "y" ]; then - dep_tristate ' AMD PCnet32 PCI support' CONFIG_PCNET32 $CONFIG_PCI - dep_tristate ' Adaptec Starfire/DuraLAN support' CONFIG_ADAPTEC_STARFIRE $CONFIG_PCI - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" ]; then - dep_tristate ' Ansel Communications EISA 3200 support (EXPERIMENTAL)' CONFIG_AC3200 $CONFIG_EXPERIMENTAL - fi - - dep_tristate ' Apricot Xen-II on board Ethernet' CONFIG_APRICOT $CONFIG_ISA - dep_tristate ' CS89x0 support' CONFIG_CS89x0 $CONFIG_ISA - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' Digi Intl. RightSwitch SE-X support' CONFIG_DGRS - fi - dep_tristate ' EtherExpressPro/100 support (eepro100, original Becker driver)' CONFIG_EEPRO100 $CONFIG_PCI - dep_tristate ' EtherExpressPro/100 support (e100, Alternate Intel driver)' CONFIG_E100 $CONFIG_PCI - dep_tristate ' Mylex EISA LNE390A/B support (EXPERIMENTAL)' CONFIG_LNE390 $CONFIG_EISA $CONFIG_EXPERIMENTAL - dep_tristate ' Myson MTD-8xx PCI Ethernet support' CONFIG_FEALNX $CONFIG_PCI - dep_tristate ' National Semiconductor DP8381x series PCI Ethernet support' CONFIG_NATSEMI $CONFIG_PCI - dep_tristate ' PCI NE2000 and clones support (see help)' CONFIG_NE2K_PCI $CONFIG_PCI - dep_tristate ' Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)' CONFIG_NE3210 $CONFIG_EISA $CONFIG_EXPERIMENTAL - dep_tristate ' Racal-Interlan EISA ES3210 support (EXPERIMENTAL)' CONFIG_ES3210 $CONFIG_EISA $CONFIG_EXPERIMENTAL - dep_tristate ' RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)' CONFIG_8139CP $CONFIG_PCI $CONFIG_EXPERIMENTAL - dep_tristate ' RealTek RTL-8139 PCI Fast Ethernet Adapter support' CONFIG_8139TOO $CONFIG_PCI - dep_mbool ' Use PIO instead of MMIO' CONFIG_8139TOO_PIO $CONFIG_8139TOO - dep_mbool ' Support for uncommon RTL-8139 rev. K (automatic channel equalization)' CONFIG_8139TOO_TUNE_TWISTER $CONFIG_8139TOO - dep_mbool ' Support for older RTL-8129/8130 boards' CONFIG_8139TOO_8129 $CONFIG_8139TOO - dep_mbool ' Use older RX-reset method' CONFIG_8139_OLD_RX_RESET $CONFIG_8139TOO - dep_tristate ' SiS 900/7016 PCI Fast Ethernet Adapter support' CONFIG_SIS900 $CONFIG_PCI - dep_tristate ' SMC EtherPower II' CONFIG_EPIC100 $CONFIG_PCI - dep_tristate ' Sundance Alta support' CONFIG_SUNDANCE $CONFIG_PCI - dep_mbool ' Use MMIO instead of PIO' CONFIG_SUNDANCE_MMIO $CONFIG_SUNDANCE - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' TI ThunderLAN support' CONFIG_TLAN - fi - dep_tristate ' VIA Rhine support' CONFIG_VIA_RHINE $CONFIG_PCI - dep_mbool ' Use MMIO instead of PIO (EXPERIMENTAL)' CONFIG_VIA_RHINE_MMIO $CONFIG_VIA_RHINE $CONFIG_EXPERIMENTAL - if [ "$CONFIG_EXPERIMENTAL" = "y" -a "$CONFIG_MIPS" = "y" ]; then - bool ' Philips SAA9730 Ethernet support (EXPERIMENTAL)' CONFIG_LAN_SAA9730 - fi - fi - bool ' Pocket and portable adapters' CONFIG_NET_POCKET - if [ "$CONFIG_NET_POCKET" = "y" ]; then - if [ "$CONFIG_ISA" = "y" -a "$CONFIG_X86" = "y" ]; then - tristate ' AT-LAN-TEC/RealTek pocket adapter support' CONFIG_ATP - fi - dep_tristate ' D-Link DE600 pocket adapter support' CONFIG_DE600 $CONFIG_ISA - dep_tristate ' D-Link DE620 pocket adapter support' CONFIG_DE620 $CONFIG_ISA - fi - if [ "$CONFIG_SGI_IP22" = "y" ]; then - bool ' SGI Seeq ethernet controller support' CONFIG_SGISEEQ - fi - if [ "$CONFIG_DECSTATION" = "y" ]; then - bool ' DEC LANCE ethernet controller support' CONFIG_DECLANCE - fi - if [ "$CONFIG_BAGET_MIPS" = "y" ]; then - tristate ' Baget AMD LANCE support' CONFIG_BAGETLANCE - fi -fi - -endmenu - -# -# Gigabit Ethernet -# - -mainmenu_option next_comment -comment 'Ethernet (1000 Mbit)' - -dep_tristate 'Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support' CONFIG_ACENIC $CONFIG_PCI -if [ "$CONFIG_ACENIC" != "n" ]; then - bool ' Omit support for old Tigon I based AceNICs' CONFIG_ACENIC_OMIT_TIGON_I -fi -dep_tristate 'D-Link DL2000-based Gigabit Ethernet support' CONFIG_DL2K $CONFIG_PCI -dep_tristate 'Intel(R) PRO/1000 Gigabit Ethernet support' CONFIG_E1000 $CONFIG_PCI -dep_mbool ' Use Rx Polling (NAPI) (EXPERIMENTAL)' CONFIG_E1000_NAPI $CONFIG_E1000 $CONFIG_EXPERIMENTAL -dep_tristate 'MyriCOM Gigabit Ethernet support' CONFIG_MYRI_SBUS $CONFIG_SBUS -dep_tristate 'National Semiconduct DP83820 support' CONFIG_NS83820 $CONFIG_PCI -dep_tristate 'Packet Engines Hamachi GNIC-II support' CONFIG_HAMACHI $CONFIG_PCI -dep_tristate 'Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)' CONFIG_YELLOWFIN $CONFIG_PCI $CONFIG_EXPERIMENTAL -dep_tristate 'SysKonnect SK-98xx support' CONFIG_SK98LIN $CONFIG_PCI -dep_tristate 'Broadcom Tigon3 support' CONFIG_TIGON3 $CONFIG_PCI - -endmenu - -if [ "$CONFIG_PPC_ISERIES" = "y" ]; then - dep_tristate 'iSeries Virtual Ethernet driver support' CONFIG_VETH $CONFIG_PPC_ISERIES -fi - -bool 'FDDI driver support' CONFIG_FDDI -if [ "$CONFIG_FDDI" = "y" ]; then - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' Digital DEFEA and DEFPA adapter support' CONFIG_DEFXX - fi - dep_tristate ' SysKonnect FDDI PCI support' CONFIG_SKFP $CONFIG_PCI -fi - -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - if [ "$CONFIG_INET" = "y" ]; then - bool 'HIPPI driver support (EXPERIMENTAL)' CONFIG_HIPPI - if [ "$CONFIG_HIPPI" = "y" -a "$CONFIG_PCI" = "y" ]; then - dep_tristate ' Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)' CONFIG_ROADRUNNER $CONFIG_PCI - if [ "$CONFIG_ROADRUNNER" != "n" ]; then - bool ' Use large TX/RX rings (EXPERIMENTAL)' CONFIG_ROADRUNNER_LARGE_RINGS - fi - fi - fi -fi - -dep_tristate 'PLIP (parallel port) support' CONFIG_PLIP $CONFIG_PARPORT - -tristate 'PPP (point-to-point protocol) support' CONFIG_PPP -if [ ! "$CONFIG_PPP" = "n" ]; then - dep_bool ' PPP multilink support (EXPERIMENTAL)' CONFIG_PPP_MULTILINK $CONFIG_EXPERIMENTAL - dep_bool ' PPP filtering' CONFIG_PPP_FILTER $CONFIG_FILTER - dep_tristate ' PPP support for async serial ports' CONFIG_PPP_ASYNC $CONFIG_PPP - dep_tristate ' PPP support for sync tty ports' CONFIG_PPP_SYNC_TTY $CONFIG_PPP - dep_tristate ' PPP Deflate compression' CONFIG_PPP_DEFLATE $CONFIG_PPP - dep_tristate ' PPP BSD-Compress compression' CONFIG_PPP_BSDCOMP $CONFIG_PPP - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' PPP over Ethernet (EXPERIMENTAL)' CONFIG_PPPOE $CONFIG_PPP - fi - if [ ! "$CONFIG_ATM" = "n" ]; then - dep_tristate ' PPP over ATM' CONFIG_PPPOATM $CONFIG_PPP - fi -fi - -tristate 'SLIP (serial line) support' CONFIG_SLIP -if [ "$CONFIG_SLIP" != "n" ]; then - bool ' CSLIP compressed headers' CONFIG_SLIP_COMPRESSED - bool ' Keepalive and linefill' CONFIG_SLIP_SMART - bool ' Six bit SLIP encapsulation' CONFIG_SLIP_MODE_SLIP6 -fi - -mainmenu_option next_comment -comment 'Wireless LAN (non-hamradio)' - -bool 'Wireless LAN (non-hamradio)' CONFIG_NET_RADIO -if [ "$CONFIG_NET_RADIO" = "y" ]; then - dep_tristate ' STRIP (Metricom starmode radio IP)' CONFIG_STRIP $CONFIG_INET - tristate ' Aironet Arlan 655 & IC2200 DS support' CONFIG_ARLAN - tristate ' Aironet 4500/4800 series adapters' CONFIG_AIRONET4500 - dep_tristate ' Aironet 4500/4800 ISA/PCI/PNP/365 support ' CONFIG_AIRONET4500_NONCS $CONFIG_AIRONET4500 - if [ "$CONFIG_AIRONET4500" != "n" -a "$CONFIG_AIRONET4500_NONCS" != "n" ]; then - bool ' Aironet 4500/4800 PNP support ' CONFIG_AIRONET4500_PNP - dep_bool ' Aironet 4500/4800 PCI support ' CONFIG_AIRONET4500_PCI $CONFIG_PCI - dep_bool ' Aironet 4500/4800 ISA broken support (EXPERIMENTAL)' CONFIG_AIRONET4500_ISA $CONFIG_EXPERIMENTAL - dep_bool ' Aironet 4500/4800 I365 broken support (EXPERIMENTAL)' CONFIG_AIRONET4500_I365 $CONFIG_EXPERIMENTAL - fi - dep_tristate ' Aironet 4500/4800 PROC interface ' CONFIG_AIRONET4500_PROC $CONFIG_AIRONET4500 m - -# New directory for Wireless LAN devices - cards above will move there - source drivers/net/wireless/Config.in -fi - -endmenu - -source drivers/net/tokenring/Config.in - -bool 'Fibre Channel driver support' CONFIG_NET_FC -if [ "$CONFIG_NET_FC" = "y" ]; then - dep_tristate ' Interphase 5526 Tachyon chipset based adapter support' CONFIG_IPHASE5526 $CONFIG_SCSI $CONFIG_PCI -fi - -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate 'Red Creek Hardware VPN (EXPERIMENTAL)' CONFIG_RCPCI $CONFIG_PCI - tristate 'Traffic Shaper (EXPERIMENTAL)' CONFIG_SHAPER -fi - -source drivers/net/wan/Config.in - -if [ "$CONFIG_HOTPLUG" = "y" -a "$CONFIG_PCMCIA" != "n" ]; then - source drivers/net/pcmcia/Config.in -fi diff --git a/drivers/net/appletalk/Config.help b/drivers/net/appletalk/Config.help deleted file mode 100644 index c5b1ebff2005..000000000000 --- a/drivers/net/appletalk/Config.help +++ /dev/null @@ -1,72 +0,0 @@ -CONFIG_DEV_APPLETALK - 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. - -CONFIG_IPDDP - 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 - <file:Documentation/networking/ipddp.txt> 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 - <file:Documentation/modules.txt>). The module is called ipddp.o. - 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. - -CONFIG_IPDDP_ENCAP - 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 - <file:Documentation/networking/ipddp.txt> 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. - -CONFIG_IPDDP_DECAP - 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 <file:Documentation/networking/ipddp.txt> 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. - -CONFIG_LTPC - 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 <file:Documentation/networking/ltpc.txt>. - -CONFIG_COPS - 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 <file:Documentation/networking/cops.txt>. - -CONFIG_COPS_DAYNA - 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). - -CONFIG_COPS_TANGENT - Support COPS compatible cards with Tangent style firmware (Tangent - ATB_II, Novell NL-1000, Daystar Digital LT-200. - diff --git a/drivers/net/appletalk/Config.in b/drivers/net/appletalk/Config.in deleted file mode 100644 index 27f1b808fd09..000000000000 --- a/drivers/net/appletalk/Config.in +++ /dev/null @@ -1,19 +0,0 @@ -# -# Appletalk driver configuration -# - -dep_mbool 'Appletalk interfaces support' CONFIG_DEV_APPLETALK $CONFIG_ATALK -if [ "$CONFIG_DEV_APPLETALK" = "y" ]; then - tristate ' Apple/Farallon LocalTalk PC support' CONFIG_LTPC - tristate ' COPS LocalTalk PC support' CONFIG_COPS - if [ "$CONFIG_COPS" != "n" ]; then - bool ' Dayna firmware support' CONFIG_COPS_DAYNA - bool ' Tangent firmware support' CONFIG_COPS_TANGENT - fi - dep_tristate ' Appletalk-IP driver support' CONFIG_IPDDP $CONFIG_ATALK - if [ "$CONFIG_IPDDP" != "n" ]; then - bool ' IP to Appletalk-IP Encapsulation support' CONFIG_IPDDP_ENCAP - bool ' Appletalk-IP to IP Decapsulation support' CONFIG_IPDDP_DECAP - fi -fi - diff --git a/drivers/net/arcnet/Config.help b/drivers/net/arcnet/Config.help deleted file mode 100644 index 2412e6adc999..000000000000 --- a/drivers/net/arcnet/Config.help +++ /dev/null @@ -1,91 +0,0 @@ -CONFIG_ARCNET - If you have a network card of this type, say Y and check out the - (arguably) beautiful poetry in - <file:Documentation/networking/arcnet.txt>. - - 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 <http://www.linuxdoc.org/docs.html#howto>(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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ARCNET_1051 - 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 <file:Documentation/networking/arcnet.txt> for more - information about using arc0e and arc0s. - -CONFIG_ARCNET_1201 - 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 <file:Documentation/networking/arcnet.txt> - for more information about using arc0. - -CONFIG_ARCNET_RAW - 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. - -CONFIG_ARCNET_COM90xx - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ARCNET_COM90xxIO - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ARCNET_RIM_I - 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.o. If you want to compile - it as a module, say M here and read <file:Documentation/modules.txt> - as well as <file:Documentation/networking/net-modules.txt>. - -CONFIG_ARCNET_COM20020 - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt> as - well as <file:Documentation/networking/net-modules.txt>. - diff --git a/drivers/net/arcnet/Config.in b/drivers/net/arcnet/Config.in deleted file mode 100644 index 3a4e7ff9d578..000000000000 --- a/drivers/net/arcnet/Config.in +++ /dev/null @@ -1,21 +0,0 @@ -# -# Arcnet configuration -# - -mainmenu_option next_comment -comment 'ARCnet devices' - -tristate 'ARCnet support' CONFIG_ARCNET -if [ "$CONFIG_ARCNET" != "n" ]; then - dep_tristate 'Enable standard ARCNet packet format (RFC 1201)' CONFIG_ARCNET_1201 $CONFIG_ARCNET - dep_tristate 'Enable old ARCNet packet format (RFC 1051)' CONFIG_ARCNET_1051 $CONFIG_ARCNET - dep_tristate 'Enable raw mode packet interface' CONFIG_ARCNET_RAW $CONFIG_ARCNET - dep_tristate 'ARCnet COM90xx (normal) chipset driver' CONFIG_ARCNET_COM90xx $CONFIG_ARCNET - dep_tristate 'ARCnet COM90xx (IO mapped) chipset driver' CONFIG_ARCNET_COM90xxIO $CONFIG_ARCNET - dep_tristate 'ARCnet COM90xx (RIM I) chipset driver' CONFIG_ARCNET_RIM_I $CONFIG_ARCNET - dep_tristate 'ARCnet COM20020 chipset driver' CONFIG_ARCNET_COM20020 $CONFIG_ARCNET - dep_tristate ' Support for COM20020 on ISA' CONFIG_ARCNET_COM20020_ISA $CONFIG_ARCNET_COM20020 $CONFIG_ISA - dep_tristate ' Support for COM20020 on PCI' CONFIG_ARCNET_COM20020_PCI $CONFIG_ARCNET_COM20020 $CONFIG_PCI -fi - -endmenu diff --git a/drivers/net/hamradio/Config.help b/drivers/net/hamradio/Config.help deleted file mode 100644 index 66f13f50865c..000000000000 --- a/drivers/net/hamradio/Config.help +++ /dev/null @@ -1,247 +0,0 @@ -CONFIG_MKISS - 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 <file:Documentation/modules.txt>. The module - will be called mkiss.o. - -CONFIG_6PACK - 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 <file:Documentation/networking/6pack.txt>. - - 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 <file:Documentation/modules.txt>. The module - will be called 6pack.o. - -CONFIG_BPQETHER - 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. - -CONFIG_DMASCC - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. 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 - <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get - at least version 1.27 of dmascc_cfg, as older versions will not - work with the current driver. - -CONFIG_SCC - 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 <file:Documentation/networking/z8530drv.txt> and the - AX25-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:Documentation/modules.txt>. The module - will be called scc.o. - -CONFIG_SCC_TRXECHO - 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. - -CONFIG_SCC_DELAY - Say Y here if you experience problems with the SCC driver not - working properly; please read - <file:Documentation/networking/z8530drv.txt> for details. If unsure, - say N. - -CONFIG_YAM - 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 <file:Documentation/modules.txt>. - -CONFIG_BAYCOM_PAR - 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 <http://www.baycom.de/> and the file - <file:Documentation/networking/baycom.txt>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called baycom_par.o. - -CONFIG_BAYCOM_EPP - 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 <http://www.baycom.de/> and the file - <file:Documentation/networking/baycom.txt>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called baycom_par.o. - -CONFIG_BAYCOM_SER_FDX - 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 <http://www.baycom.de/> and - <file:Documentation/networking/baycom.txt>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called baycom_ser_fdx.o. - -CONFIG_BAYCOM_SER_HDX - 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 - <http://www.baycom.de/> and - <file:Documentation/networking/baycom.txt>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called baycom_ser_hdx.o. - -CONFIG_SOUNDMODEM - This experimental driver allows a standard Sound Blaster or - WindowsSoundSystem compatible sound card to be used as a packet - radio modem (NOT as a telephone modem!), to send digital traffic - over amateur radio. - - To configure the driver, use the sethdlc, smdiag and smmixer - utilities available in the standard ax25 utilities package. For - information on how to key the transmitter, see - <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and - <file:Documentation/networking/soundmodem.txt>. - - 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 <file:Documentation/modules.txt>. This is - recommended. The module will be called soundmodem.o. - -CONFIG_SOUNDMODEM_SBC - This option enables the soundmodem driver to use Sound Blaster and - compatible cards. If you have a dual mode card (i.e. a WSS cards - with a Sound Blaster emulation) you should say N here and Y to - "Sound card modem support for WSS and Crystal cards", below, because - this usually results in better performance. This option also - supports SB16/32/64 in full-duplex mode. - -CONFIG_SOUNDMODEM_WSS - This option enables the soundmodem driver to use WindowsSoundSystem - compatible cards. These cards feature a codec chip from either - Analog Devices (such as AD1848, AD1845, AD1812) or Crystal - Semiconductors (such as CS4248, CS423x). This option also supports - the WSS full-duplex operation which currently works with Crystal - CS423x chips. If you don't need full-duplex operation, do not enable - it to save performance. - -CONFIG_SOUNDMODEM_AFSK1200 - This option enables the soundmodem driver 1200 baud AFSK modem, - compatible to popular modems using TCM3105 or AM7911. The - demodulator requires about 12% of the CPU power of a Pentium 75 CPU - per channel. - -CONFIG_SOUNDMODEM_AFSK2400_7 - This option enables the soundmodem driver 2400 baud AFSK modem, - compatible to TCM3105 modems (over-)clocked with a 7.3728MHz - crystal. Note that the availability of this driver does _not_ imply - that I recommend building such links. It is only here since users - especially in eastern Europe have asked me to do so. In fact this - modulation scheme has many disadvantages, mainly its incompatibility - with many transceiver designs and the fact that the TCM3105 (if - used) is operated widely outside its specifications. - -CONFIG_SOUNDMODEM_AFSK2400_8 - This option enables the soundmodem driver 2400 baud AFSK modem, - compatible to TCM3105 modems (over-)clocked with an 8MHz crystal. - Note that the availability of this driver does _not_ imply that I - recommend building such links. It is only here since users - especially in eastern Europe have asked me to do so. In fact this - modulation scheme has many disadvantages, mainly its incompatibility - with many transceiver designs and the fact that the TCM3105 (if - used) is operated widely outside its specifications. - -CONFIG_SOUNDMODEM_AFSK2666 - This option enables the soundmodem driver 2666 baud AFSK modem. - This modem is experimental, and not compatible to anything - else I know of. - -CONFIG_SOUNDMODEM_PSK4800 - This option enables the soundmodem driver 4800 baud 8PSK modem. - This modem is experimental, and not compatible to anything - else I know of. - -CONFIG_SOUNDMODEM_HAPN4800 - This option enables the soundmodem driver 4800 baud HAPN-1 - compatible modem. This modulation seems to be widely used 'down - under' and in the Netherlands. Here, nobody uses it, so I could not - test if it works. It is compatible to itself, however :-) - -CONFIG_SOUNDMODEM_FSK9600 - This option enables the soundmodem driver 9600 baud FSK modem, - compatible to the G3RUH standard. The demodulator requires about 4% - of the CPU power of a Pentium 75 CPU per channel. You can say Y to - both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you - can only use one protocol at a time, depending on what the other end - can understand). - diff --git a/drivers/net/hamradio/Config.in b/drivers/net/hamradio/Config.in deleted file mode 100644 index b87ba01bb373..000000000000 --- a/drivers/net/hamradio/Config.in +++ /dev/null @@ -1,34 +0,0 @@ - -dep_tristate 'Serial port KISS driver' CONFIG_MKISS $CONFIG_AX25 -dep_tristate 'Serial port 6PACK driver' CONFIG_6PACK $CONFIG_AX25 -dep_tristate 'BPQ Ethernet driver' CONFIG_BPQETHER $CONFIG_AX25 - -if [ "$CONFIG_ISA" = "y" ]; then - dep_tristate 'High-speed (DMA) SCC driver for AX.25' CONFIG_DMASCC $CONFIG_AX25 - dep_tristate 'Z8530 SCC driver' CONFIG_SCC $CONFIG_AX25 -fi -if [ "$CONFIG_SCC" != "n" ]; then - bool ' additional delay for PA0HZP OptoSCC compatible boards' CONFIG_SCC_DELAY - bool ' support for TRX that feedback the tx signal to rx' CONFIG_SCC_TRXECHO -fi - -dep_tristate 'BAYCOM ser12 fullduplex driver for AX.25' CONFIG_BAYCOM_SER_FDX $CONFIG_AX25 -dep_tristate 'BAYCOM ser12 halfduplex driver for AX.25' CONFIG_BAYCOM_SER_HDX $CONFIG_AX25 -dep_tristate 'BAYCOM picpar and par96 driver for AX.25' CONFIG_BAYCOM_PAR $CONFIG_PARPORT $CONFIG_AX25 -dep_tristate 'BAYCOM epp driver for AX.25' CONFIG_BAYCOM_EPP $CONFIG_PARPORT $CONFIG_AX25 - -dep_tristate 'Soundcard modem driver' CONFIG_SOUNDMODEM $CONFIG_PARPORT $CONFIG_AX25 -if [ "$CONFIG_SOUNDMODEM" != "n" ]; then - bool ' soundmodem support for Soundblaster and compatible cards' CONFIG_SOUNDMODEM_SBC - bool ' soundmodem support for WSS and Crystal cards' CONFIG_SOUNDMODEM_WSS - bool ' soundmodem support for 1200 baud AFSK modulation' CONFIG_SOUNDMODEM_AFSK1200 - bool ' soundmodem support for 2400 baud AFSK modulation (7.3728MHz crystal)' CONFIG_SOUNDMODEM_AFSK2400_7 - bool ' soundmodem support for 2400 baud AFSK modulation (8MHz crystal)' CONFIG_SOUNDMODEM_AFSK2400_8 - bool ' soundmodem support for 2666 baud AFSK modulation' CONFIG_SOUNDMODEM_AFSK2666 - bool ' soundmodem support for 4800 baud HAPN-1 modulation' CONFIG_SOUNDMODEM_HAPN4800 - bool ' soundmodem support for 4800 baud PSK modulation' CONFIG_SOUNDMODEM_PSK4800 - bool ' soundmodem support for 9600 baud FSK G3RUH modulation' CONFIG_SOUNDMODEM_FSK9600 -fi - -dep_tristate 'YAM driver for AX.25' CONFIG_YAM $CONFIG_AX25 - diff --git a/drivers/net/irda/Config.help b/drivers/net/irda/Config.help deleted file mode 100644 index e8ec1552be78..000000000000 --- a/drivers/net/irda/Config.help +++ /dev/null @@ -1,192 +0,0 @@ -CONFIG_IRTTY_SIR - Say Y here if you want to build support for the IrTTY line - discipline. If you want to compile it as a module (irtty.o), say M - here and read <file:Documentation/modules.txt>. IrTTY makes it - possible to use Linux's own serial driver for all IrDA ports that - are 16550 compatible. Most IrDA chips are 16550 compatible so you - should probably say Y to this option. Using IrTTY will however - limit the speed of the connection to 115200 bps (IrDA SIR mode). - - If unsure, say Y. - -CONFIG_IRPORT_SIR - Say Y here if you want to build support for the IrPORT IrDA device - driver. If you want to compile it as a module (irport.o), say M here - and read <file:Documentation/modules.txt>. IrPORT can be used - instead of IrTTY and sometimes this can be better. One example is - if your IrDA port does not have echo-canceling, which will work OK - with IrPORT since this driver is working in half-duplex mode only. - You don't need to use irattach with IrPORT, but you just insert it - the same way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice - that IrPORT is a SIR device driver which means that speed is limited - to 115200 bps. - - If unsure, say Y. - -CONFIG_USB_IRDA - Say Y here if you want to build support for the USB IrDA FIR Dongle - device driver. If you want to compile it as a module (irda-usb.o), - say M here and read <file:Documentation/modules.txt>. IrDA-USB - support the various IrDA USB dongles available and most of their - pecularities. Those dongles plug in the USB port of your computer, - are plug and play, and support SIR and FIR (4Mbps) speeds. On the - other hand, those dongles tend to be less efficient than a FIR - chipset. - - Please note that the driver is still experimental. And of course, - you will need both USB and IrDA support in your kernel... - -CONFIG_WINBOND_FIR - Say Y here if you want to build IrDA support for the Winbond - W83977AF super-io chipset. This driver should be used for the IrDA - chipset in the Corel NetWinder. The driver supports SIR, MIR and - FIR (4Mbps) speeds. - - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - w83977af_ir.o. - -CONFIG_NSC_FIR - Say Y here if you want to build support for the NSC PC87108 and - PC87338 IrDA chipsets. This driver supports SIR, - MIR and FIR (4Mbps) speeds. - - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - nsc-ircc.o. - -CONFIG_TOSHIBA_OLD - Say Y here if you want to build support for the Toshiba Type-O IR - chipset. This chipset is used by the Toshiba Libretto 100CT, and - many more laptops. This driver is obsolete, will no more be - maintained and will be removed in favor of the new driver. - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called toshoboe.o. - -CONFIG_TOSHIBA_FIR - Say Y here if you want to build support for the Toshiba Type-O IR - and Donau oboe chipsets. These chipsets are used by the Toshiba - Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops. - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. - The module will be called donauboe.o. - -CONFIG_SMC_IRCC_FIR - Say Y here if you want to build support for the SMC Infrared - Communications Controller. It is used in the Fujitsu Lifebook 635t - and Sony PCG-505TX. If you want to compile it as a module, say M - here and read <file:Documentation/modules.txt>. The module will be - called smc-ircc.o. - -CONFIG_ALI_FIR - Say Y here if you want to build support for the ALi M5123 FIR - Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C, - M1535, M1535D, M1535+, M1535D Sourth Bridge. This driver supports - SIR, MIR and FIR (4Mbps) speeds. - - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - ali-ircc.o. - -CONFIG_VLSI_FIR - Say Y here if you want to build support for the VLSI 82C147 - PCI-IrDA Controller. This controller is used by the HP OmniBook 800 - and 5500 notebooks. The driver provides support for SIR, MIR and - FIR (4Mbps) speeds. - - If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called vlsi_ir.o. - -CONFIG_DONGLE - Say Y here if you have an infrared device that connects to your - computer's serial port. These devices are called dongles. Then say Y - or M to the driver for your particular dongle below. - - 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 serial dongles. - -CONFIG_ESI_DONGLE - Say Y here if you want to build support for the Extended Systems - JetEye PC dongle. If you want to compile it as a module, say M here - and read <file:Documentation/modules.txt>. The ESI dongle attaches - to the normal 9-pin serial port connector, and can currently only be - used by IrTTY. To activate support for ESI dongles you will have to - start irattach like this: "irattach -d esi". - -CONFIG_ACTISYS_DONGLE - Say Y here if you want to build support for the ACTiSYS IR-220L and - IR220L+ dongles. If you want to compile it as a module, say M here - and read <file:Documentation/modules.txt>. The ACTiSYS dongles - attaches to the normal 9-pin serial port connector, and can - currently only be used by IrTTY. To activate support for ACTiSYS - dongles you will have to start irattach like this: - "irattach -d actisys" or "irattach -d actisys+". - -CONFIG_TEKRAM_DONGLE - Say Y here if you want to build support for the Tekram IrMate 210B - dongle. If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The Tekram dongle attaches to the - normal 9-pin serial port connector, and can currently only be used - by IrTTY. To activate support for Tekram dongles you will have to - start irattach like this: "irattach -d tekram". - -CONFIG_GIRBIL_DONGLE - Say Y here if you want to build support for the Greenwich GIrBIL - dongle. If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The Greenwich dongle attaches to - the normal 9-pin serial port connector, and can currently only be - used by IrTTY. To activate support for Greenwich dongles you will - have to insert "irattach -d girbil" in the /etc/irda/drivers script. - -CONFIG_LITELINK_DONGLE - Say Y here if you want to build support for the Parallax Litelink - dongle. If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The Parallax dongle attaches to - the normal 9-pin serial port connector, and can currently only be - used by IrTTY. To activate support for Parallax dongles you will - have to start irattach like this "irattach -d litelink". - -Microchip MCP2120 dongle -CONFIG_MCP2120_DONGLE - Say Y here if you want to build support for the Microchip MCP2120 - dongle. If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The MCP2120 dongle attaches to - the normal 9-pin serial port connector, and can currently only be - used by IrTTY. To activate support for MCP2120 dongles you will - have to insert "irattach -d mcp2120" in the /etc/irda/drivers script. - - You must build this dongle yourself. For more information see: - <http://www.eyetap.org/~tangf/irda_sir_linux.html> - -CONFIG_OLD_BELKIN_DONGLE - Say Y here if you want to build support for the Adaptec Airport 1000 - and 2000 dongles. If you want to compile it as a module, say M here - and read <file:Documentation/modules.txt>. The module will be - called old_belkin.o. Some information is contained in the comments - at the top of <file:drivers/net/irda/old_belkin.c>. - -ACTiSYS IR-200L dongle (Experimental) -CONFIG_ACT200L_DONGLE - Say Y here if you want to build support for the ACTiSYS IR-200L - dongle. If you want to compile it as a module, say M here and read - Documentation/modules.txt. The ACTiSYS IR-200L dongle attaches to - the normal 9-pin serial port connector, and can currently only be - used by IrTTY. To activate support for ACTiSYS IR-200L dongles - you will have to start irattach like this: "irattach -d act200l". - -Mobile Action MA600 dongle (Experimental) -CONFIG_MA600_DONGLE - Say Y here if you want to build support for the Mobile Action MA600 - dongle. If you want to compile it as a module, say M here and read - <file:Documentation/modules.txt>. The MA600 dongle attaches to - the normal 9-pin serial port connector, and can currently only be - tested on IrCOMM. To activate support for MA600 dongles you will - have to insert "irattach -d ma600" in the /etc/irda/drivers script. - Note: irutils 0.9.15 requires no modification. irutils 0.9.9 needs - modification. For more information, download the following tar gzip - file. - - There is a pre-compiled module on - <http://engsvr.ust.hk/~eetwl95/download/ma600-2.4.x.tar.gz> diff --git a/drivers/net/irda/Config.in b/drivers/net/irda/Config.in deleted file mode 100644 index 34da5d77e4c8..000000000000 --- a/drivers/net/irda/Config.in +++ /dev/null @@ -1,42 +0,0 @@ -mainmenu_option next_comment -comment 'Infrared-port device drivers' - -comment 'SIR device drivers' -dep_tristate 'IrTTY (uses Linux serial driver)' CONFIG_IRTTY_SIR $CONFIG_IRDA -dep_tristate 'IrPORT (IrDA serial driver)' CONFIG_IRPORT_SIR $CONFIG_IRDA - -comment 'Dongle support' -bool 'Serial dongle support' CONFIG_DONGLE -if [ "$CONFIG_DONGLE" != "n" ]; then - dep_tristate ' ESI JetEye PC dongle' CONFIG_ESI_DONGLE $CONFIG_IRDA - dep_tristate ' ACTiSYS IR-220L and IR220L+ dongle' CONFIG_ACTISYS_DONGLE $CONFIG_IRDA - dep_tristate ' Tekram IrMate 210B dongle' CONFIG_TEKRAM_DONGLE $CONFIG_IRDA - dep_tristate ' Greenwich GIrBIL dongle' CONFIG_GIRBIL_DONGLE $CONFIG_IRDA - dep_tristate ' Parallax LiteLink dongle' CONFIG_LITELINK_DONGLE $CONFIG_IRDA - dep_tristate ' Microchip MCP2120' CONFIG_MCP2120_DONGLE $CONFIG_IRDA - dep_tristate ' Old Belkin dongle' CONFIG_OLD_BELKIN_DONGLE $CONFIG_IRDA - if [ "$CONFIG_ARCH_EP7211" = "y" ]; then - dep_tristate ' EP7211 I/R support' CONFIG_EP7211_IR $CONFIG_IRDA - fi - if [ "$CONFIG_EXPERIMENTAL" != "n" ]; then - dep_tristate ' ACTiSYS IR-200L dongle (EXPERIMENTAL)' CONFIG_ACT200L_DONGLE $CONFIG_IRDA - dep_tristate ' Mobile Action MA600 dongle (EXPERIMENTAL)' CONFIG_MA600_DONGLE $CONFIG_IRDA - fi -fi - -comment 'FIR device drivers' -dep_tristate 'IrDA USB dongles (EXPERIMENTAL)' CONFIG_USB_IRDA $CONFIG_IRDA $CONFIG_USB $CONFIG_EXPERIMENTAL -dep_tristate 'NSC PC87108/PC87338' CONFIG_NSC_FIR $CONFIG_IRDA -dep_tristate 'Winbond W83977AF (IR)' CONFIG_WINBOND_FIR $CONFIG_IRDA -dep_tristate 'Toshiba Type-O IR Port (old driver)' CONFIG_TOSHIBA_OLD $CONFIG_IRDA -dep_tristate 'Toshiba Type-O IR Port' CONFIG_TOSHIBA_FIR $CONFIG_IRDA -if [ "$CONFIG_EXPERIMENTAL" != "n" ]; then -dep_tristate 'SMC IrCC (EXPERIMENTAL)' CONFIG_SMC_IRCC_FIR $CONFIG_IRDA -dep_tristate 'ALi M5123 FIR (EXPERIMENTAL)' CONFIG_ALI_FIR $CONFIG_IRDA -dep_tristate 'VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)' CONFIG_VLSI_FIR $CONFIG_IRDA -fi -if [ "$CONFIG_ARCH_SA1100" = "y" ]; then - dep_tristate 'SA1100 Internal IR' CONFIG_SA1100_FIR $CONFIG_IRDA -fi - -endmenu diff --git a/drivers/net/pcmcia/Config.help b/drivers/net/pcmcia/Config.help deleted file mode 100644 index d7304d7bceca..000000000000 --- a/drivers/net/pcmcia/Config.help +++ /dev/null @@ -1,173 +0,0 @@ -CONFIG_AIRONET4500_CS - Say Y here if you have a PCMCIA Aironet 4500/4800 card which you - want to use with the standard PCMCIA cardservices provided by the - pcmcia-cs 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 aironet4500_cs.o. If you want to - compile it as a module, say M here and read - <file:Documentation/modules.txt>. - -CONFIG_NET_PCMCIA - 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 <file:Documentation/Changes> - for location). You also want to check out the PCMCIA-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>. - - If unsure, say N. - -CONFIG_PCMCIA_3C589 - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_PCMCIA_3C574 - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_PCMCIA_FMVJ18X - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_PCMCIA_PCNET - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_PCMCIA_NMCLAN - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_PCMCIA_SMC91C92 - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_PCMCIA_XIRC2PS - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_PCMCIA_AXNET - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_ARCNET_COM20020_CS - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_PCMCIA_IBMTR - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_PCMCIA_XIRCOM - 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.o. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. If unsure, say N. - -CONFIG_PCMCIA_XIRTULIP - 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.o. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. If unsure, say N. - -CONFIG_NET_PCMCIA_RADIO - Say Y here if you would like to use a PCMCIA (PC-card) device to - connect to a wireless local area network. Then say Y to the driver - for your particular card below. - - To use your PC-cards, you will need supporting software from David - Hinds' pcmcia-cs package (see the file <file:Documentation/Changes> - for location). You also want to check out the PCMCIA-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_PCMCIA_RAYCS - 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 <file:Documentation/networking/ray_cs.txt> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - diff --git a/drivers/net/pcmcia/Config.in b/drivers/net/pcmcia/Config.in deleted file mode 100644 index e412a1cb4028..000000000000 --- a/drivers/net/pcmcia/Config.in +++ /dev/null @@ -1,30 +0,0 @@ -# -# PCMCIA Network device configuration -# - -mainmenu_option next_comment -comment 'PCMCIA network device support' - -bool 'PCMCIA network device support' CONFIG_NET_PCMCIA -if [ "$CONFIG_NET_PCMCIA" = "y" ]; then - dep_tristate ' 3Com 3c589 PCMCIA support' CONFIG_PCMCIA_3C589 $CONFIG_PCMCIA - dep_tristate ' 3Com 3c574 PCMCIA support' CONFIG_PCMCIA_3C574 $CONFIG_PCMCIA - dep_tristate ' Fujitsu FMV-J18x PCMCIA support' CONFIG_PCMCIA_FMVJ18X $CONFIG_PCMCIA - dep_tristate ' NE2000 compatible PCMCIA support' CONFIG_PCMCIA_PCNET $CONFIG_PCMCIA - dep_tristate ' New Media PCMCIA support' CONFIG_PCMCIA_NMCLAN $CONFIG_PCMCIA - dep_tristate ' SMC 91Cxx PCMCIA support' CONFIG_PCMCIA_SMC91C92 $CONFIG_PCMCIA - dep_tristate ' Xircom 16-bit PCMCIA support' CONFIG_PCMCIA_XIRC2PS $CONFIG_PCMCIA - dep_tristate ' broken NS8390-cards support' CONFIG_PCMCIA_AXNET $CONFIG_PCMCIA - dep_tristate ' COM20020 ARCnet PCMCIA support' CONFIG_ARCNET_COM20020_CS $CONFIG_ARCNET_COM20020 $CONFIG_ARCNET $CONFIG_PCMCIA - if [ "$CONFIG_IBMTR" != "y" ]; then - dep_tristate ' IBM PCMCIA tokenring adapter support' CONFIG_PCMCIA_IBMTR $CONFIG_TR $CONFIG_PCMCIA - fi - - bool ' Pcmcia Wireless LAN' CONFIG_NET_PCMCIA_RADIO - if [ "$CONFIG_NET_PCMCIA_RADIO" = "y" ]; then - dep_tristate ' Aviator/Raytheon 2.4MHz wireless support' CONFIG_PCMCIA_RAYCS $CONFIG_PCMCIA - dep_tristate ' Aironet 4500/4800 PCMCIA support' CONFIG_AIRONET4500_CS $CONFIG_AIRONET4500 $CONFIG_PCMCIA - fi -fi - -endmenu diff --git a/drivers/net/tokenring/Config.help b/drivers/net/tokenring/Config.help deleted file mode 100644 index 7c760925220f..000000000000 --- a/drivers/net/tokenring/Config.help +++ /dev/null @@ -1,149 +0,0 @@ -CONFIG_TR - 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 <http://www.linuxdoc.org/docs.html#howto>. Most people can - say N here. - -CONFIG_IBMTR - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_IBMOL - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - - Also read <file:Documentation/networking/olympic.txt> or check the - Linux Token Ring Project site for the latest information at - <http://www.linuxtr.net/>. - -CONFIG_IBMLS - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_TMS380TR - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - Also read the file <file:Documentation/networking/tms380tr.txt> or - check <http://www.auk.cx/tms380tr/>. - - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_TMSPCI - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_TMSISA - This tms380 module supports generic TMS380-based 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 tmsisa.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_ABYSS - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_MADGEMC - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SMCTR - 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 - <http://www.linuxdoc.org/docs.html#howto> and the file - <file:Documentation/networking/smctr.txt>. - - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -3COM 3C359 Token Link Velocity XL PCI adapter support -CONFIG_3C359 - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it - as a module, say M here and read Documentation/modules.txt. - - Also read the file <file:Documentation/networking/3c359.txt> or check the - Linux Token Ring Project site for the latest information at - <http://www.linuxtr.net> - diff --git a/drivers/net/tokenring/Config.in b/drivers/net/tokenring/Config.in deleted file mode 100644 index f996a3dd9542..000000000000 --- a/drivers/net/tokenring/Config.in +++ /dev/null @@ -1,34 +0,0 @@ -# -# Token Ring driver configuration -# - -mainmenu_option next_comment -comment 'Token Ring devices' - -# So far, we only have PCI, ISA, and MCA token ring devices -if [ "$CONFIG_PCI" = "y" -o "$CONFIG_ISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - bool 'Token Ring driver support' CONFIG_TR -else - define_bool CONFIG_TR n -fi - -if [ "$CONFIG_TR" != "n" ]; then - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - tristate ' IBM Tropic chipset based adapter support' CONFIG_IBMTR - fi - dep_tristate ' IBM Olympic chipset PCI adapter support' CONFIG_IBMOL $CONFIG_TR $CONFIG_PCI - dep_tristate ' IBM Lanstreamer chipset PCI adapter support' CONFIG_IBMLS $CONFIG_TR $CONFIG_PCI - dep_tristate ' 3Com 3C359 Token Link Velocity XL adapter support' CONFIG_3C359 $CONFIG_TR $CONFIG_PCI - tristate ' Generic TMS380 Token Ring ISA/PCI adapter support' CONFIG_TMS380TR - if [ "$CONFIG_TMS380TR" != "n" ]; then - dep_tristate ' Generic TMS380 PCI support' CONFIG_TMSPCI $CONFIG_PCI - dep_tristate ' Generic TMS380 ISA support' CONFIG_TMSISA $CONFIG_ISA - dep_tristate ' Madge Smart 16/4 PCI Mk2 support' CONFIG_ABYSS $CONFIG_PCI - dep_tristate ' Madge Smart 16/4 Ringnode MicroChannel' CONFIG_MADGEMC $CONFIG_MCA - fi - if [ "$CONFIG_ISA" = "y" -o "$CONFIG_MCA" = "y" ]; then - tristate ' SMC ISA/MCA adapter support' CONFIG_SMCTR - fi -fi - -endmenu diff --git a/drivers/net/tulip/Config.help b/drivers/net/tulip/Config.help deleted file mode 100644 index 670ac0585970..000000000000 --- a/drivers/net/tulip/Config.help +++ /dev/null @@ -1,110 +0,0 @@ -CONFIG_PCMCIA_XIRCOM - 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.o. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. If unsure, say N. - -CONFIG_PCMCIA_XIRTULIP - 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.o. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. If unsure, say N. - -CONFIG_DE2104X - 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 - <http://www.linuxdoc.org/docs.html#howto>. More specific - information is contained in - <file:Documentation/DocBook/tulip-user.tmpl>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_TULIP - This driver is developed for the SMC EtherPower series Ethernet - cards and also works with cards based on the DECchip - 21040/21041/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 - <http://www.linuxdoc.org/docs.html#howto>. More specific - information is contained in - <file:Documentation/networking/tulip.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_TULIP_MWI - 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. - -CONFIG_TULIP_MMIO - 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. - -CONFIG_NET_TULIP - This selects the "Tulip" family of EISA/PCI network cards. - -CONFIG_DE4X5 - 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 - <http://www.linuxdoc.org/docs.html#howto>. More specific - information is contained in - <file:Documentation/networking/de4x5.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_WINBOND_840 - 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 - <http://www.scyld.com/network/drivers.html>. - -CONFIG_DM9102 - This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from - Davicom (<http://www.davicom.com.tw/>). If you have such a network - (Ethernet) card, say Y. Some information is contained in the file - <file:Documentation/networking/dmfe.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - diff --git a/drivers/net/tulip/Config.in b/drivers/net/tulip/Config.in deleted file mode 100644 index a77d781fd196..000000000000 --- a/drivers/net/tulip/Config.in +++ /dev/null @@ -1,27 +0,0 @@ -# -# Tulip family network device configuration -# - -mainmenu_option next_comment -comment 'Tulip family network device support' - -bool '"Tulip" family network device support' CONFIG_NET_TULIP -if [ "$CONFIG_NET_TULIP" = "y" ]; then - dep_tristate ' Early DECchip Tulip (dc2104x) PCI support (EXPERIMENTAL)' CONFIG_DE2104X $CONFIG_PCI $CONFIG_EXPERIMENTAL - dep_tristate ' DECchip Tulip (dc2114x) PCI support' CONFIG_TULIP $CONFIG_PCI - if [ "$CONFIG_TULIP" = "y" -o "$CONFIG_TULIP" = "m" ]; then - dep_bool ' New bus configuration (EXPERIMENTAL)' CONFIG_TULIP_MWI $CONFIG_EXPERIMENTAL - bool ' Use PCI shared mem for NIC registers' CONFIG_TULIP_MMIO - fi - if [ "$CONFIG_PCI" = "y" -o "$CONFIG_EISA" = "y" ]; then - tristate ' Generic DECchip & DIGITAL EtherWORKS PCI/EISA' CONFIG_DE4X5 - fi - dep_tristate ' Winbond W89c840 Ethernet support' CONFIG_WINBOND_840 $CONFIG_PCI - dep_tristate ' Davicom DM910x/DM980x support' CONFIG_DM9102 $CONFIG_PCI - if [ "$CONFIG_CARDBUS" = "y" ]; then - tristate ' Xircom CardBus support (new driver)' CONFIG_PCMCIA_XIRCOM - tristate ' Xircom Tulip-like CardBus support (old driver)' CONFIG_PCMCIA_XIRTULIP - fi -fi - -endmenu diff --git a/drivers/net/wan/Config.help b/drivers/net/wan/Config.help deleted file mode 100644 index f88c2782115c..000000000000 --- a/drivers/net/wan/Config.help +++ /dev/null @@ -1,481 +0,0 @@ -CONFIG_LAPBETHER - 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 <file:Documentation/modules.txt>. The module - will be called lapbether.o. If unsure, say N. - -CONFIG_X25_ASY - 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 <file:Documentation/modules.txt>. The module - will be called x25_asy.o. If unsure, say N. - -CONFIG_SEALEVEL_4021 - 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.o. - -CONFIG_SYNCLINK_SYNCPPP - 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. - -CONFIG_FARSYNC - 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 <file:Documentation/modules.txt>. - The module will be called farsync.o 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, ... - -CONFIG_DLCI - 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 - <http://www.frforum.com/> on the WWW. To use frame relay, you need - supporting hardware (called FRAD) and certain programs from the - net-tools package as explained in - <file:Documentation/networking/framerelay.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_DLCI_COUNT - This is the maximal number of logical point-to-point frame relay - connections (the identifiers of which are called DCLIs) that - the driver can handle. The default is probably fine. - -CONFIG_DLCI_MAX - You can specify here how many logical point-to-point frame relay - connections (the identifiers of which are called DCLIs) should be - handled by each of your hardware frame relay access devices. Go with - the default. - -CONFIG_SDLA - 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 <file:Documentation/framerelay.txt>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_WAN - 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. - -CONFIG_HOSTESS_SV11 - 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. - -CONFIG_COSA - 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 <http://www.fi.muni.cz/~kas/cosa/> 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 - <file:drivers/net/wan/cosa.c> 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.o. For general information about - modules read <file:Documentation/modules.txt>. - -CONFIG_DSCC4 - 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 <http://www.cogenit.fr/dscc4/> - 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.o. For general information about - modules read <file:Documentation/modules.txt>. - -CONFIG_LANMEDIA - 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 <ftp://ftp.lanmedia.com/>. - - This code is also available as a module called lmc.o ( = 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>. - -CONFIG_SBNI - 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.o). - - You can find more information and last versions of drivers and - utilities at <http://www.granch.ru/>. If you have any question you - can send email to sbni@granch.ru. - - Say N if unsure. - -CONFIG_SBNI_MULTILINE - 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. - -CONFIG_WAN_ROUTER_DRIVERS - 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 - <ftp://ftp.sangoma.com/>. Read - <file:Documentation/networking/wan-router.txt> 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. - -CONFIG_VENDOR_SANGOMA - WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com/>) - 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 - <file:Documentation/networking/wanpipe.txt>. 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.o. For general information about - modules read <file:Documentation/modules.txt>. - -CONFIG_WANPIPE_X25 - 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. - -CONFIG_WANPIPE_FR - 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. - -CONFIG_WANPIPE_PPP - 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. - -CONFIG_WANPIPE_MULTPPP - 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. - -CONFIG_WANPIPE_CHDLC - 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. - -CONFIG_COMX - 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 <file:Documentation/networking/comx.txt> for help on - configuring and using COMX interfaces. Further info on these cards - can be found at <http://www.itc.hu/> or <info@itc.hu>. - - 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 - <file:Documentation/modules.txt>. The module will be called comx.o. - -CONFIG_COMX_HW_COMX - 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 <ftp://ftp.itc.hu/>. - - If you want to compile this as a module, say M and read - <file:Documentation/modules.txt>. The module will be called - comx-hw-comx.o. - -CONFIG_COMX_HW_LOCOMX - 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 - <file:Documentation/modules.txt>. The module will be called - comx-hw-locomx.o. - -CONFIG_COMX_HW_MIXCOM - 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 - <ftp://ftp.itc.hu/>. - - If you want to compile this as a module, say M and read - <file:Documentation/modules.txt>. The module will be called - comx-hw-mixcom.o. - -CONFIG_COMX_PROTO_PPP - 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 - <file:Documentation/modules.txt>. The module will be called - comx-proto-ppp.o. - -CONFIG_COMX_PROTO_LAPB - 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 - <file:Documentation/modules.txt>. The module will be called - comx-proto-lapb.o. - -CONFIG_COMX_PROTO_FR - 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 - <file:Documentation/modules.txt>. The module will be called - comx-proto-fr.o. - -CONFIG_CYCLADES_SYNC - Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com/> and - <http://www.cyclades.com.br/>) 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 - <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes - to make it compile with the current wanrouter include files; efforts - are being made to use the original package available at - <ftp://ftp.sangoma.com/>). - - 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.o. For general information about - modules read <file:Documentation/modules.txt>. - -CONFIG_CYCLOMX_X25 - 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). - -CONFIG_HDLC - 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 - <http://hq.pm.waw.pl/hdlc/>. - Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame - Relay, synchronous Point-to-Point Protocol (PPP) and X.25. - - If unsure, say N here. - -CONFIG_COMX_HW_MUNICH - 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.o. 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 <info@itc.hu>. - -CONFIG_HDLC_RAW - 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. - -CONFIG_HDLC_CISCO - 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. - -CONFIG_HDLC_FR - 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. - -CONFIG_HDLC_PPP - 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. - -CONFIG_HDLC_X25 - 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. - -CONFIG_N2 - 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 <http://hq.pm.waw.pl/pub/hdlc/>. - - Note that N2csu and N2dds cards are not supported by this driver. - - If unsure, say N here. - -CONFIG_C101 - 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 <http://hq.pm.waw.pl/pub/hdlc/> - - If unsure, say N here. - -Cyclades-PC300 support -CONFIG_PC300 - 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.o. - - If you haven't heard about it, it's safe to say N. - -Cyclades-PC300 Sync TTY (to MLPPP) support -CONFIG_PC300_MLPPP - Say 'Y' to this option if you are planning to use Multilink PPP over the - PC300 synchronous communication boards. - - diff --git a/drivers/net/wan/Config.in b/drivers/net/wan/Config.in deleted file mode 100644 index f2cbe616d83e..000000000000 --- a/drivers/net/wan/Config.in +++ /dev/null @@ -1,136 +0,0 @@ -# -# wan devices configuration -# - -mainmenu_option next_comment -comment 'Wan interfaces' - -bool 'Wan interfaces support' CONFIG_WAN -if [ "$CONFIG_WAN" = "y" ]; then -# There is no way to detect a comtrol sv11 - force it modular for now. - - if [ "$CONFIG_ISA" = "y" ]; then - dep_tristate ' Comtrol Hostess SV-11 support' CONFIG_HOSTESS_SV11 m -# The COSA/SRP driver has not been tested as non-modular yet. - - dep_tristate ' COSA/SRP sync serial boards support' CONFIG_COSA m - fi - -# -# COMX drivers -# - - tristate ' MultiGate (COMX) synchronous serial boards support' CONFIG_COMX - if [ "$CONFIG_COMX" != "n" ]; then - dep_tristate ' Support for COMX/CMX/HiCOMX boards' CONFIG_COMX_HW_COMX $CONFIG_COMX - dep_tristate ' Support for LoCOMX board' CONFIG_COMX_HW_LOCOMX $CONFIG_COMX - dep_tristate ' Support for MixCOM board' CONFIG_COMX_HW_MIXCOM $CONFIG_COMX - dep_tristate ' Support for MUNICH based boards: SliceCOM, PCICOM (WelCOM)' CONFIG_COMX_HW_MUNICH $CONFIG_COMX - dep_tristate ' Support for HDLC and syncPPP protocols on MultiGate boards' CONFIG_COMX_PROTO_PPP $CONFIG_COMX - if [ "$CONFIG_LAPB" = "y" ]; then - dep_tristate ' Support for LAPB protocol on MultiGate boards' CONFIG_COMX_PROTO_LAPB $CONFIG_COMX - fi - if [ "$CONFIG_LAPB" = "m" ]; then - dep_tristate ' Support for LAPB protocol on MultiGate boards' CONFIG_COMX_PROTO_LAPB $CONFIG_LAPB - fi - dep_tristate ' Support for Frame Relay on MultiGate boards' CONFIG_COMX_PROTO_FR $CONFIG_COMX - fi -# -# The Etinc driver has not been tested as non-modular yet. -# - - dep_tristate ' Etinc PCISYNC serial board support' CONFIG_DSCC4 m - - -# -# Lan Media's board. Currently 1000, 1200, 5200, 5245 -# - - tristate ' LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards' CONFIG_LANMEDIA - -# There is no way to detect a Sealevel board. Force it modular - - dep_tristate ' Sealevel Systems 4021 support' CONFIG_SEALEVEL_4021 m - - tristate ' SyncLink HDLC/SYNCPPP support' CONFIG_SYNCLINK_SYNCPPP - -# Generic HDLC - - tristate ' Generic HDLC layer' CONFIG_HDLC - if [ "$CONFIG_HDLC" != "n" ]; then - bool ' Raw HDLC support' CONFIG_HDLC_RAW - bool ' Cisco HDLC support' CONFIG_HDLC_CISCO - bool ' Frame Relay support' CONFIG_HDLC_FR - bool ' Synchronous Point-to-Point Protocol (PPP) support' CONFIG_HDLC_PPP - if [ "$CONFIG_LAPB" = "m" -a "$CONFIG_HDLC" = "m" -o "$CONFIG_LAPB" = "y" ]; then - bool ' X.25 protocol support' CONFIG_HDLC_X25 - else - comment ' X.25/LAPB support is disabled' - fi - - dep_tristate ' Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)' CONFIG_PC300 $CONFIG_HDLC $CONFIG_PCI - if [ "$CONFIG_PC300" != "n" ]; then - if [ "$CONFIG_PPP" != "n" -a "$CONFIG_PPP_MULTILINK" != "n" -a \ - "$CONFIG_PPP_SYNC_TTY" != "n" -a "$CONFIG_HDLC_PPP" = "y" ]; then - bool ' Cyclades-PC300 MLPPP support' CONFIG_PC300_MLPPP - else - comment 'Cyclades-PC300 MLPPP support is disabled.' - comment 'Refer to the file README.mlppp, provided by PC300 package.' - fi - fi - - dep_tristate ' SDL RISCom/N2 support' CONFIG_N2 $CONFIG_HDLC - dep_tristate ' Moxa C101 support' CONFIG_C101 $CONFIG_HDLC - dep_tristate ' FarSync T-Series support' CONFIG_FARSYNC $CONFIG_HDLC - bool ' Debug received/transmitted packets' CONFIG_HDLC_DEBUG_PKT - bool ' Debug hard_header routines' CONFIG_HDLC_DEBUG_HARD_HEADER - bool ' Debug FECN/BECN conditions' CONFIG_HDLC_DEBUG_ECN - bool ' Debug RX/TX packet rings' CONFIG_HDLC_DEBUG_RINGS - fi - - tristate ' Frame relay DLCI support' CONFIG_DLCI - if [ "$CONFIG_DLCI" != "n" ]; then - int ' Max open DLCI' CONFIG_DLCI_COUNT 24 - int ' Max DLCI per device' CONFIG_DLCI_MAX 8 - dep_tristate ' SDLA (Sangoma S502/S508) support' CONFIG_SDLA $CONFIG_DLCI - fi - -# Wan router core. - - if [ "$CONFIG_WAN_ROUTER" != "n" ]; then - bool ' WAN router drivers' CONFIG_WAN_ROUTER_DRIVERS - if [ "$CONFIG_WAN_ROUTER_DRIVERS" = "y" ]; then - dep_tristate ' Sangoma WANPIPE(tm) multiprotocol cards' CONFIG_VENDOR_SANGOMA $CONFIG_WAN_ROUTER - if [ "$CONFIG_VENDOR_SANGOMA" != "n" ]; then - bool ' WANPIPE Cisco HDLC support' CONFIG_WANPIPE_CHDLC - bool ' WANPIPE Frame Relay support' CONFIG_WANPIPE_FR - bool ' WANPIPE X.25 support' CONFIG_WANPIPE_X25 - bool ' WANPIPE PPP support' CONFIG_WANPIPE_PPP - bool ' WANPIPE Multi-Port PPP support' CONFIG_WANPIPE_MULTPPP - fi - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' Cyclom 2X(tm) cards (EXPERIMENTAL)' CONFIG_CYCLADES_SYNC $CONFIG_WAN_ROUTER_DRIVERS - if [ "$CONFIG_CYCLADES_SYNC" != "n" ]; then - bool ' Cyclom 2X X.25 support (EXPERIMENTAL)' CONFIG_CYCLOMX_X25 - fi - fi - fi - fi - - -# X.25 network drivers - - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' LAPB over Ethernet driver (EXPERIMENTAL)' CONFIG_LAPBETHER $CONFIG_LAPB $CONFIG_X25 - dep_tristate ' X.25 async driver (EXPERIMENTAL)' CONFIG_X25_ASY $CONFIG_LAPB $CONFIG_X25 - fi - - if [ "$CONFIG_X86" = "y" ]; then - tristate ' Granch SBNI12 Leased Line adapter support' CONFIG_SBNI - if [ "$CONFIG_SBNI" != "n" ]; then - bool ' Multiple line feature support' CONFIG_SBNI_MULTILINE - fi - fi -fi - -endmenu diff --git a/drivers/net/wireless/Config.help b/drivers/net/wireless/Config.help deleted file mode 100644 index c96b810f2296..000000000000 --- a/drivers/net/wireless/Config.help +++ /dev/null @@ -1,140 +0,0 @@ -CONFIG_WAVELAN - 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 <file:Documentation/Changes> - for location). - - If you want to use an ISA WaveLAN card under Linux, say Y and read - the Ethernet-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. Some more specific - information is contained in - <file:Documentation/networking/wavelan.txt> and in the source code - <file:drivers/net/wavelan.p.h>. - - You will also need the wireless tools package available from - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> as well - as <file:Documentation/networking/net-modules.txt>. - -CONFIG_HERMES - 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 : - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html> - -CONFIG_PLX_HERMES - Enable support for PCMCIA cards supported by the "Hermes" (aka - orinoco_cs) 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. - -CONFIG_PCI_HERMES - 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. - -CONFIG_PCMCIA_HERMES - 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 <file:Documentation/Changes> - for location). You also want to check out the PCMCIA-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>. - - You will also very likely also need the Wireless Tools in order to - configure your card and that /etc/pcmcia/wireless.opts works: - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. - -CONFIG_AIRO - 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.o". - -CONFIG_AIRO_CS - 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 <file:Documentation/Changes> - for location). You also want to check out the PCMCIA-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>. - -CONFIG_APPLE_AIRPORT - 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 - -CONFIG_PCMCIA_NETWAVE - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_PCMCIA_WAVELAN - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - diff --git a/drivers/net/wireless/Config.in b/drivers/net/wireless/Config.in deleted file mode 100644 index ec5997a1cea8..000000000000 --- a/drivers/net/wireless/Config.in +++ /dev/null @@ -1,45 +0,0 @@ -# -# Wireless LAN device configuration -# - -comment 'Wireless ISA/PCI cards support' - -# Good old obsolete Wavelan. -tristate ' AT&T/Lucent old WaveLAN & DEC RoamAbout DS ISA support' CONFIG_WAVELAN - -# 802.11b cards -if [ "$CONFIG_ISA" = "y" -o "$CONFIG_PCI" = "y" ]; then - tristate ' Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards' CONFIG_AIRO -fi - -tristate ' Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)' CONFIG_HERMES - -if [ "$CONFIG_ALL_PPC" = "y" ]; then - dep_tristate ' Apple Airport support (built-in)' CONFIG_APPLE_AIRPORT $CONFIG_HERMES -fi - -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate ' Hermes in PLX9052 based PCI adaptor support (Netgear MA301 etc.) (EXPERIMENTAL)' CONFIG_PLX_HERMES $CONFIG_HERMES $CONFIG_EXPERIMENTAL - dep_tristate ' Prism 2.5 PCI 802.11b adaptor support (EXPERIMENTAL)' CONFIG_PCI_HERMES $CONFIG_HERMES $CONFIG_EXPERIMENTAL -fi - -# If Pcmcia is compiled in, offer Pcmcia cards... -if [ "$CONFIG_PCMCIA" != "n" ]; then - comment 'Wireless Pcmcia/Cardbus cards support' - -# Obsolete cards - dep_tristate ' Xircom Netwave AirSurfer Pcmcia wireless support' CONFIG_PCMCIA_NETWAVE $CONFIG_PCMCIA - dep_tristate ' AT&T/Lucent old Wavelan Pcmcia wireless support' CONFIG_PCMCIA_WAVELAN $CONFIG_PCMCIA - -# 802.11b cards - dep_tristate ' Hermes PCMCIA card support' CONFIG_PCMCIA_HERMES $CONFIG_HERMES - dep_tristate ' Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards' CONFIG_AIRO_CS $CONFIG_PCMCIA -fi - -# yes, this works even when no drivers are selected -if [ "$CONFIG_ISA" = "y" -o "$CONFIG_PCI" = "y" -o \ - "$CONFIG_ALL_PPC" = "y" -o "$CONFIG_PCMCIA" != "n" ]; then - define_bool CONFIG_NET_WIRELESS y -else - define_bool CONFIG_NET_WIRELESS n -fi diff --git a/drivers/parport/Config.help b/drivers/parport/Config.help deleted file mode 100644 index ef949a8a96fe..000000000000 --- a/drivers/parport/Config.help +++ /dev/null @@ -1,99 +0,0 @@ -CONFIG_PARPORT - 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 - <file:Documentation/parport.txt> and - <file:drivers/parport/BUGS-parport>. - - For extensive information about drivers for many devices attaching - to the parallel port see <http://www.torque.net/linux-pp.html> 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 - <file:Documentation/modules.txt>. The module will be called - parport.o. 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 <file:Documentation/parport.txt>. - - If unsure, say Y. - -CONFIG_PARPORT_PC - 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. - - 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 - <file:Documentation/modules.txt>. The module will be called - parport_pc.o. - - If unsure, say Y. - -CONFIG_PARPORT_SERIAL - 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.o. - -CONFIG_PARPORT_PC_FIFO - 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 <file:Documentation/parport.txt> to find out how to - specify which IRQ/DMA to use. - -CONFIG_PARPORT_PC_SUPERIO - 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. - -CONFIG_PARPORT_PC_PCMCIA - Say Y here if you need PCMCIA support for your PC-style parallel - ports. If unsure, say N. - -CONFIG_PARPORT_OTHER - 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. - -CONFIG_PARPORT_AMIGA - 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.o. If in doubt, saying N is the safe plan. - -CONFIG_PARPORT_ATARI - 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.o. If in doubt, saying N is the safe plan. - -CONFIG_PARPORT_MFC3 - 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.o. If in doubt, saying N is the safe plan. - -CONFIG_PARPORT_1284 - 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. - -CONFIG_PARPORT_SUNBPP - 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. - -CONFIG_PARPORT_GSC - Say Y here to build in low-level parallel-support for PC-style - hardware integrated in the LASI-Controller (on the GSC Bus) for - HP-PARISC workstations. - diff --git a/drivers/parport/Config.in b/drivers/parport/Config.in deleted file mode 100644 index eb13f0748e0e..000000000000 --- a/drivers/parport/Config.in +++ /dev/null @@ -1,71 +0,0 @@ -# -# For a description of the syntax of this configuration file, -# see Documentation/kbuild/config-language.txt. -# -# Parport configuration. -# - -mainmenu_option next_comment -comment 'Parallel port support' - -tristate 'Parallel port support' CONFIG_PARPORT -if [ "$CONFIG_PARPORT" != "n" ]; then - dep_tristate ' PC-style hardware' CONFIG_PARPORT_PC $CONFIG_PARPORT - if [ "$CONFIG_PARPORT_PC" != "n" -a "$CONFIG_SERIAL" != "n" ]; then - if [ "$CONFIG_SERIAL" = "m" ]; then - define_tristate CONFIG_PARPORT_PC_CML1 m - else - define_tristate CONFIG_PARPORT_PC_CML1 $CONFIG_PARPORT_PC - fi - dep_tristate ' Multi-IO cards (parallel and serial)' CONFIG_PARPORT_SERIAL $CONFIG_PARPORT_PC_CML1 - fi - if [ "$CONFIG_PARPORT_PC" != "n" ]; then - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool ' Use FIFO/DMA if available (EXPERIMENTAL)' CONFIG_PARPORT_PC_FIFO - bool ' SuperIO chipset support (EXPERIMENTAL)' CONFIG_PARPORT_PC_SUPERIO - fi - if [ "$CONFIG_HOTPLUG" = "y" -a "$CONFIG_PCMCIA" != "n" ]; then - if [ "$CONFIG_PARPORT_PC" = "y" ]; then - dep_tristate ' Support for PCMCIA management for PC-style ports' CONFIG_PARPORT_PC_PCMCIA $CONFIG_PCMCIA - else - dep_tristate ' Support for PCMCIA management for PC-style ports' CONFIG_PARPORT_PC_PCMCIA $CONFIG_PARPORT_PC - fi - fi - fi - if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' Archimedes hardware' CONFIG_PARPORT_ARC $CONFIG_PARPORT - fi - if [ "$CONFIG_AMIGA" = "y" ]; then - dep_tristate ' Amiga builtin port' CONFIG_PARPORT_AMIGA $CONFIG_PARPORT - if [ "$CONFIG_ZORRO" != "n" ]; then - dep_tristate ' Multiface III parallel port' CONFIG_PARPORT_MFC3 $CONFIG_PARPORT - fi - else - define_tristate CONFIG_PARPORT_AMIGA n - define_tristate CONFIG_PARPORT_MFC3 n - fi - if [ "$CONFIG_ATARI" = "y" ]; then - dep_tristate ' Atari hardware' CONFIG_PARPORT_ATARI $CONFIG_PARPORT - else - define_tristate CONFIG_PARPORT_ATARI n - fi - if [ "$CONFIG_GSC_LASI" = "y" ]; then - dep_tristate ' LASI/ASP builtin parallel-port' CONFIG_PARPORT_GSC $CONFIG_PARPORT - else - define_tristate CONFIG_PARPORT_GSC n - fi - - if [ "$CONFIG_SBUS" = "y" -a "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate ' Sparc hardware (EXPERIMENTAL)' CONFIG_PARPORT_SUNBPP $CONFIG_PARPORT - else - define_tristate CONFIG_PARPORT_SUNBPP n - fi - - # If exactly one hardware type is selected then parport will optimise away - # support for loading any others. Defeat this if the user is keen. - bool ' Support foreign hardware' CONFIG_PARPORT_OTHER - - bool ' IEEE 1284 transfer modes' CONFIG_PARPORT_1284 -fi - -endmenu diff --git a/drivers/pci/Config.help b/drivers/pci/Config.help deleted file mode 100644 index bc4eaa6816e3..000000000000 --- a/drivers/pci/Config.help +++ /dev/null @@ -1,12 +0,0 @@ -CONFIG_PCI_NAMES - 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, but it gets freed after the - system boots up, so it doesn't take up kernel memory. 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. - diff --git a/drivers/pci/Config.in b/drivers/pci/Config.in deleted file mode 100644 index de540640446a..000000000000 --- a/drivers/pci/Config.in +++ /dev/null @@ -1,7 +0,0 @@ -# -# PCI configuration -# - -if [ "$CONFIG_PCI" = "y" ]; then - bool 'PCI device name database' CONFIG_PCI_NAMES -fi diff --git a/drivers/pcmcia/Config.help b/drivers/pcmcia/Config.help deleted file mode 100644 index d8bf86f2a746..000000000000 --- a/drivers/pcmcia/Config.help +++ /dev/null @@ -1,53 +0,0 @@ -CONFIG_PCMCIA - 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 <file:Documentation/Changes> - for location). Please also read the PCMCIA-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o - and ds.o. If you want to compile it as a module, say M here and - read <file:Documentation/modules.txt>. - -CONFIG_CARDBUS - 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 <file:Documentation/Changes> - for location). - - If unsure, say Y. - -CONFIG_I82092 - 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. - -CONFIG_I82365 - 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. - -CONFIG_TCIC - 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. - diff --git a/drivers/pcmcia/Config.in b/drivers/pcmcia/Config.in deleted file mode 100644 index 4f8bfb546424..000000000000 --- a/drivers/pcmcia/Config.in +++ /dev/null @@ -1,27 +0,0 @@ -# -# PCMCIA bus subsystem configuration -# -# Right now the non-CardBus choices are not supported -# by the integrated kernel driver. -# -mainmenu_option next_comment -comment 'PCMCIA/CardBus support' - -tristate 'PCMCIA/CardBus support' CONFIG_PCMCIA -if [ "$CONFIG_PCMCIA" != "n" ]; then - if [ "$CONFIG_PCI" != "n" ]; then - bool ' CardBus support' CONFIG_CARDBUS - fi - dep_tristate ' i82092 compatible bridge support' CONFIG_I82092 $CONFIG_PCMCIA $CONFIG_PCI - dep_tristate ' i82365 compatible bridge support' CONFIG_I82365 $CONFIG_PCMCIA - dep_tristate ' Databook TCIC host bridge support' CONFIG_TCIC $CONFIG_PCMCIA - if [ "$CONFIG_HD64465" = "y" ]; then - dep_tristate ' HD64465 host bridge support' CONFIG_HD64465_PCMCIA $CONFIG_PCMCIA - fi - if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' SA1100 support' CONFIG_PCMCIA_SA1100 $CONFIG_ARCH_SA1100 $CONFIG_PCMCIA - dep_tristate ' SA1111 support' CONFIG_PCMCIA_SA1111 $CONFIG_PCMCIA_SA1100 $CONFIG_SA1111 $CONFIG_PCMCIA - fi -fi - -endmenu diff --git a/drivers/pnp/Config.help b/drivers/pnp/Config.help deleted file mode 100644 index 6c9448d08b1c..000000000000 --- a/drivers/pnp/Config.help +++ /dev/null @@ -1,52 +0,0 @@ -CONFIG_PNP - 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. - -CONFIG_PNP_NAMES - 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. - -CONFIG_PNP_DEBUG - 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. - -CONFIG_ISAPNP - Say Y here if you would like support for ISA Plug and Play devices. - Some information is in <file:Documentation/isapnp.txt>. - - This support is also available as a module called isapnp.o ( = - 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>. - - If unsure, say Y. - -CONFIG_PNPBIOS - 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. - diff --git a/drivers/pnp/Config.in b/drivers/pnp/Config.in deleted file mode 100644 index 9e9f25ebac81..000000000000 --- a/drivers/pnp/Config.in +++ /dev/null @@ -1,20 +0,0 @@ -# -# Plug and Play configuration -# -mainmenu_option next_comment -comment 'Plug and Play configuration' - -bool 'Plug and Play support' CONFIG_PNP - -if [ "$CONFIG_PNP" = "y" ]; then - bool ' Plug and Play device name database' CONFIG_PNP_NAMES - bool ' PnP Debug Messages' CONFIG_PNP_DEBUG - - comment 'Protocols' - - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool ' ISA Plug and Play support (EXPERIMENTAL)' CONFIG_ISAPNP - bool ' Plug and Play BIOS support (EXPERIMENTAL)' CONFIG_PNPBIOS - fi -fi -endmenu diff --git a/drivers/s390/Config.help b/drivers/s390/Config.help deleted file mode 100644 index 12d6f6d390a6..000000000000 --- a/drivers/s390/Config.help +++ /dev/null @@ -1,460 +0,0 @@ -CONFIG_BLK_DEV_RAM - 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 <file:Documentation/ramdisk.txt>. - - 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 <file:Documentation/modules.txt>. The module will be - called rd.o. - - Most normal users won't need the RAM disk functionality, and can - thus say N here. - -CONFIG_BLK_DEV_RAM_SIZE - The default value is 4096. Only change this if you know what are - you doing. If you are using IBM S/390, then set this to 8192. - -CONFIG_BLK_DEV_INITRD - 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 <file:Documentation/initrd.txt> - for details. - -CONFIG_BLK_DEV_LOOP - 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. - - 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. If you want to do this, you will first have - to acquire and install a kernel patch from - <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to - say Y to this option. - - Note that alternative ways to use encrypted file systems are - provided by the cfs package, which can be gotten from - <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs - package, available at <http://tcfs.dia.unisa.it/>. You do not need - to say Y here if you want to use one of these. However, using cfs - requires saying Y to "NFS file system support" below while using - tcfs requires applying a kernel patch. An alternative steganography - solution is provided by StegFS, also available from - <ftp://ftp.kerneli.org/pub/kerneli/net-source/>. - - To use the loop device, you need the losetup utility and a recent - version of the mount program, both contained in the util-linux - package. The location and current version number of util-linux is - contained in the file <file:Documentation/Changes>. - - 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 <file:Documentation/modules.txt>. The module - will be called loop.o. - - Most users will answer N here. - -CONFIG_BLK_DEV_NBD - Saying Y here will allow your computer to be a client for network - block devices, i.e. it will be able to use block devices exported by - servers (mount file systems on them etc.). Communication between - client and server works over TCP/IP networking, but to the client - program this is hidden: it looks like a regular local file access to - a block device special file such as /dev/nd0. - - Network block devices also allows you to run a block-device in - userland (making server and client physically the same computer, - communicating using the loopback network device). - - Read <file:Documentation/nbd.txt> for more information, especially - about where to find the server code, which runs in user space and - does not need special kernel support. - - Note that this has nothing to do with the network file systems NFS - or Coda; you can say N here even if you intend to use NFS or Coda. - - 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 <file:Documentation/modules.txt>. The module - will be called nbd.o. - - If unsure, say N. - -CONFIG_HOTPLUG - 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 <http://linux-hotplug.sourceforge.net/>) 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. - -CONFIG_NETDEVICES - 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 - <http://www.linuxdoc.org/docs.html#howto>) 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 - <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). - - 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 <http://www.linuxdoc.org/docs.html#guide>. If - unsure, say Y. - -CONFIG_DUMMY - 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 - <http://www.linuxdoc.org/docs.html#guide>. - - 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 <file:Documentation/modules.txt>. The module - will be called dummy.o. 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. - -CONFIG_BONDING - 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 <file:Documentation/modules.txt>. The module - will be called bonding.o. - -CONFIG_EQUALIZER - 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 - <file:Documentation/networking/eql.txt>. You may also want to read - section 6.2 of the NET-3-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. If - unsure, say N. - -CONFIG_TUN - 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 <file:Documentation/networking/tuntap.txt> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - If you don't know what to use this for, you don't need it. - -CONFIG_NET_ETHERNET - 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 - <http://www.linuxdoc.org/docs.html#howto>. 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. - -CONFIG_TR - 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 <http://www.linuxdoc.org/docs.html#howto>. Most people can - say N here. - -CONFIG_FDDI - 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. - -CONFIG_UNIX98_PTYS - A pseudo terminal (PTY) is a software device consisting of two - halves: a master and a slave. The slave device behaves identical to - a physical terminal; the master device is used by a process to - read data from and write data to the slave, thereby emulating a - terminal. Typical programs for the master side are telnet servers - and xterms. - - Linux has traditionally used the BSD-like names /dev/ptyxx for - masters and /dev/ttyxx for slaves of pseudo terminals. This scheme - has a number of problems. The GNU C library glibc 2.1 and later, - however, supports the Unix98 naming standard: in order to acquire a - pseudo terminal, a process opens /dev/ptmx; the number of the pseudo - terminal is then made available to the process and the pseudo - terminal slave can be accessed as /dev/pts/<number>. What was - traditionally /dev/ttyp2 will then be /dev/pts/2, for example. - - The entries in /dev/pts/ are created on the fly by a virtual - file system; therefore, if you say Y here you should say Y to - "/dev/pts file system for Unix98 PTYs" as well. - - If you want to say Y here, you need to have the C library glibc 2.1 - or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*"). - Read the instructions in <file:Documentation/Changes> pertaining to - pseudo terminals. It's safe to say N. - -CONFIG_UNIX98_PTY_COUNT - The maximum number of Unix98 PTYs that can be used at any one time. - The default is 256, and should be enough for desktop systems. Server - machines which support incoming telnet/rlogin/ssh connections and/or - serve several X terminals may want to increase this: every incoming - connection and every xterm uses up one PTY. - - When not in use, each additional set of 256 PTYs occupy - approximately 8 KB of kernel memory on 32-bit architectures. - -CONFIG_DASD - Enable this option if you want to access DASDs directly utilizing - S/390s channel subsystem commands. This is necessary for running - natively on a single image or an LPAR. - -CONFIG_DASD_ECKD - ECKD devices are the most commonly used devices. you should enable - this option unless you are very sure to have no ECKD device. - -CONFIG_DASD_CKD - CKD devices are currently unsupported. - -CONFIG_DASD_FBA - FBA devices are currently unsupported. - -CONFIG_DASD_AUTO_DIAG - Enable this option if you want your DIAG discipline module loaded - on DASD driver startup. - -CONFIG_DASD_AUTO_ECKD - Enable this option if you want your ECKD discipline module loaded - on DASD driver startup. - -CONFIG_DASD_AUTO_FBA - Enable this option if you want your FBA discipline module loaded - on DASD driver startup. - -CONFIG_TN3215 - Include support for IBM 3215 line-mode terminals. - -CONFIG_TN3215_CONSOLE - Include support for using an IBM 3215 line-mode terminal as a - Linux system console. - -CONFIG_TN3270 - Include support for IBM 3270 line-mode terminals. - -CONFIG_TN3270_CONSOLE - Include support for using an IBM 3270 line-mode terminal as a Linux - system console. Available only if 3270 support is compiled in - statically. - -CONFIG_HWC - Include support for IBM HWC line-mode terminals. - -CONFIG_HWC_CONSOLE - Include support for using an IBM HWC line-mode terminal as the Linux - system console. - -CONFIG_HWC_CPI - This option enables the hardware console interface for system - identification This is commonly used for workload management and - gives you a nice name for the system on the service element. - Please select this option as a module since built-in operation is - completely untested. - You should only select this option if you know what you are doing, - need this feature and intend to run your kernel in LPAR. - -CONFIG_S390_TAPE - Select this option if you want to access channel-attached tape - devices on IBM S/390 or zSeries. - If you select this option you will also want to select at - least one of the tape interface options and one of the tape - hardware options in order to access a tape device. - This option is also available as a module. The module will be - called tape390.o and include all selected interfaces and - hardware drivers. - -CONFIG_S390_TAPE_CHAR - Select this option if you want to access your channel-attached - tape devices using the character device interface. - This interface is similar to other Linux tape devices like - SCSI-Tapes (st) and the floppy tape device (ftape). - If unsure, say "Y". - -CONFIG_S390_TAPE_BLOCK - Select this option if you want to access your channel-attached tape - devices using the block device interface. This interface is similar - to CD-ROM devices on other platforms. The tapes can only be - accessed read-only when using this interface. Have a look at - Documentation/s390/TAPE for further information about creating - volumes for and using this interface. It is safe to say "Y" here. - -CONFIG_S390_TAPE_3490 - Select this option if you want to access IBM 3480 magnetic - tape subsystems and 100% compatibles. - It is safe to say "Y" here. - -CONFIG_S390_TAPE_3480 - Select this option if you want to access IBM 3490 magnetic - tape subsystems and 100% compatibles. - -CONFIG_CTC - 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.o. If you do not know what it is, it's safe to say "Y". - -CONFIG_DASD_DIAG - Select this option if you want to use CMS reserved Disks under VM - with the Diagnose250 command. If you are not running under VM or - unsure what it is, say "N". - -CONFIG_BLK_DEV_XPRAM - Select this option if you want to use your expanded storage on S/390 - or zSeries as a disk. This is useful as a _fast_ swap device if you - want to access more than 2G of memory when running in 31 bit mode. - This option is also available as a module which will be called - xpram.o. If unsure, say "N". - -CONFIG_IUCV - 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.o. If unsure, say "Y". - -CONFIG_CHANDEV - The channel device layer is a layer to provide a consistent - interface for configuration & default machine check (devices - appearing & disappearing) handling on Linux for s/390 & z/Series - channel devices. - - s/390 & z/Series channel devices include among others - - lcs (the most common ethernet/token ring/fddi standard on - zSeries) - ctc/escon hi speed like serial link standard on zSeries - claw used to talk to cisco routers. - qeth gigabit ethernet. - - These devices use two channels one read & one write for - configuration & communication (& a third channel, the data - channel the case of gigabit ethernet). The motivation - behind developing this layer was that there was a lot of - duplicate code among the channel device drivers for - configuration. - - Also the lcs & ctc drivers tended to fight over - 3088/08's & 3088/1F's which could be either 2216/3172 - channel attached lcs compatible devices or escon/ctc pipes - had to be configured separately as they couldn't autodetect, - this is now simplified by doing the configuration in a single - place (the channel device layer). - - This layer isn't invasive & it is quite okay to use channel - drivers which don't use the channel device layer in - conjunction with drivers which do. - - For more info see the chandev manpage usually distributed in - <file:Documentation/s390/chandev.8> in the Linux source tree. - diff --git a/drivers/s390/Config.in b/drivers/s390/Config.in deleted file mode 100644 index c8b96d6a17ea..000000000000 --- a/drivers/s390/Config.in +++ /dev/null @@ -1,99 +0,0 @@ -mainmenu_option next_comment -comment 'Block device drivers' - -tristate 'Loopback device support' CONFIG_BLK_DEV_LOOP -dep_tristate 'Network block device support' CONFIG_BLK_DEV_NBD $CONFIG_NET -tristate 'RAM disk support' CONFIG_BLK_DEV_RAM -if [ "$CONFIG_BLK_DEV_RAM" = "y" -o "$CONFIG_BLK_DEV_RAM" = "m" ]; then - int ' Default RAM disk size' CONFIG_BLK_DEV_RAM_SIZE 24576 -fi -dep_bool ' Initial RAM disk (initrd) support' CONFIG_BLK_DEV_INITRD $CONFIG_BLK_DEV_RAM -tristate 'XPRAM disk support' CONFIG_BLK_DEV_XPRAM - -comment 'S/390 block device drivers' - -tristate 'Support for DASD devices' CONFIG_DASD -if [ "$CONFIG_DASD" != "n" ]; then - dep_tristate ' Support for ECKD Disks' CONFIG_DASD_ECKD $CONFIG_DASD - if [ "$CONFIG_DASD_ECKD" = "m" ]; then - bool ' Automatic activation of ECKD module' CONFIG_DASD_AUTO_ECKD - fi - dep_tristate ' Support for FBA Disks' CONFIG_DASD_FBA $CONFIG_DASD - if [ "$CONFIG_DASD_FBA" = "m" ]; then - bool ' Automatic activation of FBA module' CONFIG_DASD_AUTO_FBA - fi -# dep_tristate ' Support for CKD Disks' CONFIG_DASD_CKD $CONFIG_DASD - if [ "$CONFIG_ARCH_S390X" != "y" ]; then - dep_tristate ' Support for DIAG access to CMS reserved Disks' CONFIG_DASD_DIAG $CONFIG_DASD - if [ "$CONFIG_DASD_DIAG" = "m" ]; then - bool ' Automatic activation of DIAG module' CONFIG_DASD_AUTO_DIAG - fi - fi -fi - -endmenu - -source drivers/md/Config.in - -mainmenu_option next_comment -comment 'Character device drivers' -bool 'Unix98 PTY support' CONFIG_UNIX98_PTYS -if [ "$CONFIG_UNIX98_PTYS" = "y" ]; then - int 'Maximum number of Unix98 PTYs in use (0-2048)' CONFIG_UNIX98_PTY_COUNT 256 -fi - -comment 'S/390 character device drivers' - -tristate 'Support for locally attached 3270 tubes' CONFIG_TN3270 -if [ "$CONFIG_TN3270" = "y" ]; then - bool 'Support for console on 3270 line mode terminal' CONFIG_TN3270_CONSOLE -fi -bool 'Support for 3215 line mode terminal' CONFIG_TN3215 -if [ "$CONFIG_TN3215" = "y" ]; then - bool 'Support for console on 3215 line mode terminal' CONFIG_TN3215_CONSOLE -fi -bool 'Support for HWC line mode terminal' CONFIG_HWC -if [ "$CONFIG_HWC" = "y" ]; then - bool ' console on HWC line mode terminal' CONFIG_HWC_CONSOLE - tristate ' Control-Program Identification' CONFIG_HWC_CPI -fi -tristate 'S/390 tape device support' CONFIG_S390_TAPE -if [ "$CONFIG_S390_TAPE" != "n" ]; then - comment 'S/390 tape interface support' - bool ' Support for tape character devices' CONFIG_S390_TAPE_CHAR - bool ' Support for tape block devices' CONFIG_S390_TAPE_BLOCK - comment 'S/390 tape hardware support' - dep_tristate ' Support for 3490 tape hardware' CONFIG_S390_TAPE_3490 $CONFIG_S390_TAPE - dep_tristate ' Support for 3480 tape hardware' CONFIG_S390_TAPE_3480 $CONFIG_S390_TAPE -fi -endmenu - -if [ "$CONFIG_NET" = "y" ]; then - mainmenu_option next_comment - comment 'Network device drivers' - bool 'Network device support' CONFIG_NETDEVICES - - if [ "$CONFIG_NETDEVICES" = "y" ]; then - tristate 'Dummy net driver support' CONFIG_DUMMY - tristate 'Bonding driver support' CONFIG_BONDING - tristate 'EQL (serial line load balancing) support' CONFIG_EQUALIZER - tristate 'Universal TUN/TAP device driver support' CONFIG_TUN - bool 'Ethernet (10 or 100Mbit)' CONFIG_NET_ETHERNET - bool 'Token Ring driver support' CONFIG_TR - bool 'FDDI driver support' CONFIG_FDDI - comment 'S/390 network device drivers' - bool 'Channel Device Configuration' CONFIG_CHANDEV - if [ "$CONFIG_CHANDEV" = "y" ]; then - define_bool CONFIG_HOTPLUG y - fi - - if [ "$CONFIG_NET_ETHERNET" != "n" -o "$CONFIG_TR" != "n" ]; then - tristate 'Lan Channel Station Interface' CONFIG_LCS - fi - - tristate 'CTC device support' CONFIG_CTC - tristate 'IUCV device support (VM only)' CONFIG_IUCV - fi - endmenu -fi - diff --git a/drivers/sbus/char/Config.help b/drivers/sbus/char/Config.help deleted file mode 100644 index 402d0067be13..000000000000 --- a/drivers/sbus/char/Config.help +++ /dev/null @@ -1,80 +0,0 @@ -CONFIG_APM_RTC_IS_GMT - Say Y here if your RTC (Real Time Clock a.k.a. hardware clock) - stores the time in GMT (Greenwich Mean Time). Say N if your RTC - stores localtime. - - It is in fact recommended to store GMT in your RTC, because then you - don't have to worry about daylight savings time changes. The only - reason not to use GMT in your RTC is if you also run a broken OS - that doesn't understand GMT. - -CONFIG_RTC - If you say Y here and create a character special file /dev/rtc with - major number 10 and minor number 135 using mknod ("man mknod"), you - will get access to the real time clock (or hardware clock) built - into your computer. - - Every PC has such a clock built in. It can be used to generate - signals from as low as 1Hz up to 8192Hz, and can also be used - as a 24 hour alarm. It reports status information via the file - /proc/driver/rtc and its behaviour is set by various ioctls on - /dev/rtc. - - If you run Linux on a multiprocessor machine and said Y to - "Symmetric Multi Processing" above, you should say Y here to read - and set the RTC in an SMP compatible fashion. - - If you think you have a use for such a device (such as periodic data - sampling), then say Y here, and read <file:Documentation/rtc.txt> - 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 is called rtc.o. If you want to compile it as a module, - say M here and read <file:Documentation/modules.txt>. - -CONFIG_SUN_OPENPROMIO - This driver provides user programs with an interface to the SPARC - PROM device tree. The driver implements a SunOS-compatible - interface and a NetBSD-compatible interface. - - 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 <file:Documentation/modules.txt>. If unsure, say Y. - -CONFIG_SUN_MOSTEK_RTC - The Mostek RTC chip is used on all known Sun computers except - some JavaStations. For a JavaStation you need to say Y both here - and to "Enhanced Real Time Clock Support". - - Say Y here unless you are building a special purpose kernel. - -CONFIG_OBP_FLASH - The OpenBoot PROM on Ultra systems is flashable. If you want to be - able to upgrade the OBP firmware, say Y here. - -CONFIG_SUN_JSFLASH - If you say Y here, you will be able to boot from your JavaStation's - Flash memory. - -CONFIG_SUN_VIDEOPIX - Say Y here to support the Videopix Frame Grabber from Sun - Microsystems, commonly found on SPARCstations. This card, which is - based on the Phillips SAA9051, can handle NTSC and PAL/SECAM and - SVIDEO signals. - -CONFIG_SUN_BPP - Say Y here to support Sun's obsolete variant of IEEE1284 - bidirectional parallel port protocol as /dev/bppX. Can be built on - x86 machines. - -CONFIG_SUN_AURORA - The Aurora Multiboard is a multi-port high-speed serial controller. - If you have one of these, say Y. - -CONFIG_TADPOLE_TS102_UCTRL - Say Y here to directly support the TS102 Microcontroller interface - on the Tadpole Sparcbook 3. This device handles power-management - events, and can also notice the attachment/detachment of external - monitors and mice. - diff --git a/drivers/sbus/char/Config.in b/drivers/sbus/char/Config.in deleted file mode 100644 index 38134ad13134..000000000000 --- a/drivers/sbus/char/Config.in +++ /dev/null @@ -1,25 +0,0 @@ -mainmenu_option next_comment -comment 'Misc Linux/SPARC drivers' -tristate '/dev/openprom device support' CONFIG_SUN_OPENPROMIO -tristate 'Mostek real time clock support' CONFIG_SUN_MOSTEK_RTC -if [ "$CONFIG_SPARC64" = "y" ]; then - tristate 'OBP Flash Device support' CONFIG_OBP_FLASH -fi - -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - tristate 'Bidirectional parallel port support (OBSOLETE)' CONFIG_SUN_BPP - tristate 'Videopix Frame Grabber (EXPERIMENTAL)' CONFIG_SUN_VIDEOPIX - tristate 'Aurora Multiboard 1600se (EXPERIMENTAL)' CONFIG_SUN_AURORA - - if [ "$CONFIG_SPARC32" = "y" ]; then - tristate 'Tadpole TS102 Microcontroller support (EXPERIMENTAL)' CONFIG_TADPOLE_TS102_UCTRL - - tristate 'JavaStation OS Flash SIMM (EXPERIMENTAL)' CONFIG_SUN_JSFLASH - # XXX Why don't we do "source drivers/char/Config.in" somewhere? - if [ "$CONFIG_PCI" = "y" ]; then - define_bool CONFIG_APM_RTC_IS_GMT y # no shit - tristate 'PC-style Real Time Clock Support' CONFIG_RTC - fi - fi -fi -endmenu diff --git a/drivers/scsi/Config.help b/drivers/scsi/Config.help deleted file mode 100644 index 0498d1412f94..000000000000 --- a/drivers/scsi/Config.help +++ /dev/null @@ -1,1397 +0,0 @@ -CONFIG_BLK_DEV_3W_XXXX_RAID - 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!!! - - <http://www.3ware.com/> - - Please read the comments at the top of - <file:drivers/scsi/3w-xxxx.c>. - -CONFIG_WARPENGINE_SCSI - Support for MacroSystem Development's WarpEngine Amiga SCSI-2 - controller. Info at - <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>. - -CONFIG_JAZZ_ESP - 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. - -CONFIG_BLK_DEV_SD - If you want to use a SCSI hard disk or the SCSI or parallel port - version of the IOMEGA ZIP drive under Linux, say Y and read the - SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> and - <file:Documentation/scsi.txt>. 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. - -CONFIG_CHR_DEV_ST - If you want to use a SCSI tape drive under Linux, say Y and read the - SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, and - <file:drivers/scsi/README.st> 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> and - <file:Documentation/scsi.txt>. - -CONFIG_CHR_DEV_OSST - 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 - <http://www.linuxdoc.org/docs.html#howto> and - <file:drivers/scsi/README.osst> in the kernel source. - More info on the OnStream driver may be found on - <http://linux1.onstream.nl/test/> - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> and - <file:Documentation/scsi.txt>. - -CONFIG_BLK_DEV_SR - If you want to use a SCSI CD-ROM under Linux, say Y and read the - SCSI-HOWTO and the CD-ROM-HOWTO at - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt> and - <file:Documentation/scsi.txt>. - -CONFIG_SR_EXTRA_DEVS - This controls the amount of additional space allocated in tables for - drivers that are loaded as modules after the kernel is booted. In - the event that the SCSI core itself was loaded as a module, this - value is the number of additional CD-ROMs that can be loaded after - the first host driver is loaded. - - Admittedly this isn't pretty, but there are tons of race conditions - involved with resizing the internal arrays on the fly. Someday this - flag will go away, and everything will work automatically. - - If you don't understand what's going on, go with the default. - -CONFIG_BLK_DEV_SR_VENDOR - 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. - -CONFIG_CHR_DEV_SG - 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 (<http://www.mostang.com/sane/>). For CD - writer software look at Cdrtools - (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>) - and for burning a "disk at once": CDRDAO - (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high - quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>). - For other devices, it's possible that you'll have to write the - driver software yourself. Please read the file - <file:Documentation/scsi-generic.txt> 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 <file:Documentation/modules.txt> and - <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure, - say N. - -CONFIG_SCSI_MULTI_LUN - 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. - -CONFIG_SCSI_REPORT_LUNS - If you want to build with SCSI REPORT LUNS support in the kernel, 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. - -CONFIG_SCSI_CONSTANTS - 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. - -CONFIG_SCSI_LOGGING - 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: <file:drivers/scsi/scsi.c>), 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. - -CONFIG_SCSI_DECNCR - Say Y here to support the NCR53C94 SCSI controller chips on IOASIC - based TURBOchannel DECstations and TURBOchannel PMAZ-A cards. - -CONFIG_SCSI_ADVANSYS - This is a driver for all SCSI host adapters manufactured by - AdvanSys. It is documented in the kernel source in - <file:drivers/scsi/advansys.c>. - - 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>. The module will be called - advansys.o. - -CONFIG_SCSI_AHA152X - 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 - <http://www.linuxdoc.org/docs.html#howto>. You might also want to - read the file <file:drivers/scsi/README.aha152x>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_AHA1542 - This is support for a SCSI host adapter. It is explained in section - 3.4 of the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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 <file:drivers/scsi/aha1542.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 <file:Documentation/modules.txt>. The module - will be called aha1542.o. - -CONFIG_SCSI_AHA1740 - This is support for a SCSI host adapter. It is explained in section - 3.5 of the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/aha1740.h>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_DPT_I2O - 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 <file:drivers/scsi/README.dpti>. - - 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>. The module will be called - dpt_i2o.o. - -CONFIG_SCSI_AIC7XXX_OLD - 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 - <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before - contacting the maintainer with any questions. The SCSI-HOWTO, - available from <http://www.linuxdoc.org/docs.html#howto>, 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 <file:Documentation/modules.txt>. The module - will be called aic7xxx_old.o. - -CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT - This option causes the aic7xxx driver to attempt to use Tagged - Command Queueing (TCQ) on all devices that claim to support it. - - TCQ 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. Because the device is - intelligent, it can optimize its operations (like head positioning) - based on its own request queue. Not all devices implement this - correctly. - - If you say Y here, you can still turn off TCQ on troublesome devices - with the use of the tag_info boot parameter. See the file - <file:drivers/scsi/README.aic7xxx> for more information on that and - other aic7xxx setup commands. If this option is turned off, you may - still enable TCQ on known good devices by use of the tag_info boot - parameter. - - If you are unsure about your devices then it is safest to say N - here. - - However, TCQ can increase performance on some hard drives by as much - as 50% or more, so it is recommended that if you say N here, you - should at least read the <file:drivers/scsi/README.aic7xxx> file so - you will know how to enable this option manually should your drives - prove to be safe in regards to TCQ. - - Conversely, certain drives are known to lock up or cause bus resets - when TCQ is enabled on them. If you have a Western Digital - Enterprise SCSI drive for instance, then don't even bother to enable - TCQ on it as the drive will become unreliable, and it will actually - reduce performance. - -CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE - Specify the number of commands you would like to allocate per SCSI - device when Tagged Command Queueing (TCQ) is enabled on that device. - - Reasonable figures are in the range of 8 to 24 commands per device, - but depending on hardware could be increased or decreased from that - figure. If the number is too high for any particular device, the - driver will automatically compensate usually after only 10 minutes - of uptime. It will not hinder performance if some of your devices - eventually have their command depth reduced, but is a waste of - memory if all of your devices end up reducing this number down to a - more reasonable figure. - - NOTE: Certain very broken drives are known to lock up when given - more commands than they like to deal with. Quantum Fireball drives - are the most common in this category. For the Quantum Fireball - drives it is suggested to use no more than 8 commands per device. - - Default: 8 - -CONFIG_AIC7XXX_OLD_PROC_STATS - This option tells the driver to keep track of how many commands have - been sent to each particular device and report that information to - the user via the /proc/scsi/aic7xxx/n file, where n is the number of - the aic7xxx controller you want the information on. This adds a - small amount of overhead to each and every SCSI command the aic7xxx - driver handles, so if you aren't really interested in this - information, it is best to leave it disabled. This will only work if - you also say Y to "/proc file system support", below. - - If unsure, say N. - -CONFIG_SCSI_IPS - This is support for the IBM ServeRAID hardware RAID controllers. - See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html> - 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 <file:Documentation/modules.txt>. - The module will be called ips.o. - -CONFIG_SCSI_BUSLOGIC - This is support for BusLogic MultiMaster and FlashPoint SCSI Host - Adapters. Consult the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, and the files - <file:drivers/scsi/README.BusLogic> and - <file:drivers/scsi/README.FlashPoint> 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 <file:Documentation/modules.txt>. - The module will be called BusLogic.o. - -CONFIG_SCSI_OMIT_FLASHPOINT - 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. - -CONFIG_SCSI_CPQFCTS - Say Y here to compile in support for the Compaq StorageWorks Fibre - Channel 64-bit/66Mhz Host Bus Adapter. - -CONFIG_SCSI_DMX3191D - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_DTC3280 - This is support for DTC 3180/3280 SCSI Host Adapters. Please read - the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, and the file - <file:drivers/scsi/README.dtc3x80>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_EATA_DMA - This is support for the EATA-DMA protocol compliant SCSI Host - Adapters like the SmartCache III/IV, SmartRAID controller families - and the DPT PM2011B and PM2012B controllers. - - Note that this driver is obsolete; if you have one of the above - SCSI Host Adapters, you should normally say N here and Y to "EATA - ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available - from <http://www.linuxdoc.org/docs.html#howto>. - - 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 eata_dma.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_EATA_PIO - 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 <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. The module - will be called eata_pio.o. - -CONFIG_SCSI_U14_34F - This is support for the UltraStor 14F and 34F SCSI-2 host adapters. - The source at <file:drivers/scsi/u14-34f.c> contains some - information about this hardware. If the driver doesn't work out of - the box, you may have to change some settings in - <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_U14_34F_LINKED_COMMANDS - 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... - - The safe answer is N. - -CONFIG_SCSI_U14_34F_MAX_TAGS - This specifies how many SCSI commands can be maximally queued for - each probed SCSI device. You should reduce the default value of 8 - only if you have disks with buggy or limited tagged command support. - Minimum is 2 and maximum is 14. This value is also the window size - used by the elevator sorting option above. The effective value used - by the driver for each probed SCSI device is reported at boot time. - -CONFIG_SCSI_FUTURE_DOMAIN - 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 - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_FD_MCS - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_GENERIC_NCR5380 - 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 - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/g_NCR5380.h>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_GENERIC_NCR5380_MMIO - 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 - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/g_NCR5380.h>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_GENERIC_NCR53C400 - 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 - <file:drivers/scsi/README.g_NCR5380> for details. - -CONFIG_SCSI_NCR_D700 - 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. - -CONFIG_SCSI_LASI700 - This is a driver for the lasi baseboard in some parisc machines - which is based on the 53c700 chip. Will also support LASI subsystems - based on the 710 chip using 700 emulation mode. - - Unless you know you have a 53c700 or 53c710 based lasi, say N here - -CONFIG_SCSI_NCR53C7xx - This is a driver for the 53c7 and 8xx NCR family of SCSI - controllers, not to be confused with the NCR 5380 controllers. It - is explained in section 3.8 of the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/53c7,8xx.h>. Please read - <file:drivers/scsi/README.ncr53c7xx> for the available boot time - command line options. - - Note: there is another driver for the 53c8xx family of controllers - ("NCR53C8XX SCSI support" below). If you want to use them both, you - need to say M to both and build them as modules, but only one may be - active at a time. If you have a 53c8xx board, it's better to use the - other 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 53c7,8xx.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_NCR53C7xx_sync - In general, this is good; however, it is a bit dangerous since there - are some broken SCSI devices out there. Take your chances. Safe bet - is N. - -CONFIG_SCSI_NCR53C7xx_FAST - 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. - -CONFIG_SCSI_NCR53C7xx_DISCONNECT - This enables the disconnect/reconnect feature of the NCR SCSI - controller. When you say Y here, a slow SCSI device will not lock - the SCSI bus while processing a request, allowing simultaneous use - of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and - providing much better performance when using slow and fast SCSI - devices at the same time. Some devices, however, do not operate - properly with this option enabled, and will cause your SCSI system - to hang, which might cause a system crash. The safe answer - therefore is to say N. - -CONFIG_SCSI_SYM53C8XX_2 - 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. - - If your system has problems using this new major version of the - SYM53C8XX driver, you may switch back to driver version 1. - - Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more - information. - -CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE - This option only applies to PCI-SCSI chip that are PCI DAC capable - (875A, 895A, 896, 1010-33, 1010-66, 1000). - - When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed. - When set to 1, 40 bit DMA addressing (with upper 24 bits of address - set to zero) is supported. The addressable range is here 1 TB. - When set to 2, full 64 bits of address for DMA are supported, but only - 16 segments of 4 GB can be addressed. The addressable range is so - limited to 64 GB. - - The safest value is 0 (32 bit DMA addressing) that is guessed to still - fit most of real machines. - - The preferred value 1 (40 bit DMA addressing) should make happy - properly engineered PCI DAC capable host bridges. You may configure - this option for Intel platforms with more than 4 GB of memory. - - The still experimental value 2 (64 bit DMA addressing with 16 x 4GB - segments limitation) can be used on systems that require PCI address - bits past bit 39 to be set for the addressing of memory using PCI - DAC cycles. - -CONFIG_SCSI_SYM53C8XX_IOMAPPED - If you say Y here, the driver will preferently use normal IO rather than - memory mapped IO. - -CONFIG_SCSI_SYM53C8XX_MAX_TAGS - This option allows you to specify the maximum number of commands - that can be queued to any device, when tagged command queuing is - possible. The driver supports up to 256 queued commands per device. - This value is used as a compiled-in hard limit. - -CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS - This is the default value of the command queue depth the driver will - announce to the generic SCSI layer for devices that support tagged - command queueing. This value can be changed from the boot command line. - This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS. - -CONFIG_SCSI_NCR53C8XX - This is the BSD ncr driver adapted to Linux for the NCR53C8XX family - of PCI-SCSI controllers. This driver supports parity checking, - tagged command queuing and fast synchronous data transfers up to 80 - MB/s with wide FAST-40 LVD devices and controllers. - - Recent versions of the 53C8XX chips are better supported by the - option "SYM53C8XX SCSI support", below. - - Note: there is yet another driver for the 53c8xx family of - controllers ("NCR53c7,8xx SCSI support" above). If you want to use - them both, you need to say M to both and build them as modules, but - only one may be active at a time. If you have a 53c8xx board, you - probably do not want to use the "NCR53c7,8xx SCSI support". - - Please read <file:drivers/scsi/README.ncr53c8xx> for more - information. - -CONFIG_SCSI_SYM53C8XX - 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 <file:drivers/scsi/README.ncr53c8xx> for more - information. - -CONFIG_SCSI_NCR53C8XX_SYNC - The SCSI Parallel Interface-2 Standard defines 5 classes of transfer - rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers - are respectively the maximum data transfer rates in mega-transfers - per second for each class. For example, a FAST-20 Wide 16 device is - able to transfer data at 20 million 16 bit packets per second for a - total rate of 40 MB/s. - - You may specify 0 if you want to only use asynchronous data - transfers. This is the safest and slowest option. Otherwise, specify - a value between 5 and 80, depending on the capability of your SCSI - controller. The higher the number, the faster the data transfer. - Note that 80 should normally be ok since the driver decreases the - value automatically according to the controller's capabilities. - - Your answer to this question is ignored for controllers with NVRAM, - since the driver will get this information from the user set-up. It - also can be overridden using a boot setup option, as follows - (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate - for FAST-20 synchronous data transfer (20 mega-transfers per - second). - - The normal answer therefore is not to go with the default but to - select the maximum value 80 allowing the driver to use the maximum - value supported by each controller. If this causes problems with - your SCSI devices, you should come back and decrease the value. - - There is no safe option other than using good cabling, right - terminations and SCSI conformant devices. - -CONFIG_SCSI_NCR53C8XX_IOMAPPED - 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. - -CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT - 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. - -CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS - "Tagged command queuing" 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. - Because the device is intelligent, it can optimize its operations - (like head positioning) based on its own request queue. Some SCSI - devices don't implement this properly; if you want to disable this - feature, enter 0 or 1 here (it doesn't matter which). - - The default value is 8 and should be supported by most hard disks. - This value can be overridden from the boot command line using the - 'tags' option as follows (example): - 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to - 4, set queue depth to 16 for target 2 and target 3 on controller 0 - and set queue depth to 10 for target 0 / lun 2 on controller 1. - - The normal answer therefore is to go with the default 8 and to use - a boot command line option for devices that need to use a different - command queue depth. - - There is no safe option other than using good SCSI devices. - -CONFIG_SCSI_NCR53C8XX_MAX_TAGS - This option allows you to specify the maximum number of commands - that can be queued to any device, when tagged command queuing is - possible. The default value is 32. Minimum is 2, maximum is 64. - Modern hard disks are able to support 64 tags and even more, but - do not seem to be faster when more than 32 tags are being used. - - So, the normal answer here is to go with the default value 32 unless - you are using very large hard disks with large cache (>= 1 MB) that - are able to take advantage of more than 32 tagged commands. - - There is no safe option and the default answer is recommended. - -CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT - 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. - -CONFIG_SCSI_NCR53C8XX_PROFILE - 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. - -CONFIG_SCSI_NCR53C8XX_PQS_PDS - 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. - -CONFIG_SCSI_NSP32 - This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus - SCSI host adapter. Please read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. The module - will be called nsp32.o. - -CONFIG_SCSI_IBMMCA - 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 - <file:Documentation/mca.txt>. - - 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=<pun>' kernel - option, where <pun> 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 <file:Documentation/modules.txt>. The module - will be called ibmmca.o. - -CONFIG_IBMMCA_SCSI_ORDER_STANDARD - 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. - -CONFIG_IBMMCA_SCSI_DEV_RESET - 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. - -CONFIG_SCSI_MCA_53C9X - 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 <file:Documentation/modules.txt>. The module will - be called mca_53c9x.o. - -CONFIG_SCSI_IN2000 - This is support for an ISA bus SCSI host adapter. You'll find more - information in <file:drivers/scsi/README.in2000>. 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 <file:Documentation/modules.txt>. The module - will be called in2000.o. - -CONFIG_SCSI_INITIO - This is support for the Initio 91XXU(W) SCSI host adapter. Please - read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. The module - will be called initio.o. - -CONFIG_SCSI_PAS16 - This is support for a SCSI host adapter. It is explained in section - 3.10 of the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/pas16.h>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_INIA100 - This is support for the Initio INI-A100U2W SCSI host adapter. - Please read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. The module - will be called a100u2w.o. - -CONFIG_SCSI_PCI2000 - This is support for the PCI2000I EIDE interface card which acts as a - SCSI host adapter. Please read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - This driver is also available as a module called pci2000.o ( = 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>. - -CONFIG_SCSI_PCI2220I - This is support for the PCI2220i EIDE interface card which acts as a - SCSI host adapter. Please read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - This driver is also available as a module called pci2220i.o ( = 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>. - -CONFIG_SCSI_PSI240I - This is support for the PSI240i EIDE interface card which acts as a - SCSI host adapter. Please read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - This driver is also available as a module called psi240i.o ( = 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>. - -CONFIG_SCSI_QLOGIC_FAS - 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 - <file:drivers/scsi/README.qlogicfas>. You should also read the - SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_QLOGIC_ISP - 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 <file:drivers/scsi/README.qlogicisp>. You - should also read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_QLOGIC_FC - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_QLOGIC_1280 - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_SEAGATE - 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 <http://www.linuxdoc.org/docs.html#howto>. If it - doesn't work out of the box, you may have to change some settings in - <file:drivers/scsi/seagate.h>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_T128 - This is support for a SCSI host adapter. It is explained in section - 3.11 of the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/t128.h>. 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_ULTRASTOR - 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 - <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out - of the box, you may have to change some settings in - <file:drivers/scsi/ultrastor.h>. - - 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 <file:Documentation/modules.txt>. The module - will be called ultrastor.o. - -CONFIG_SCSI_7000FASST - This driver supports the Western Digital 7000 SCSI host adapter - family. Some information is in the source: - <file:drivers/scsi/wd7000.c>. - - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_ACARD - 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.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_SCSI_EATA - 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. If you chose "BIOS" at the question "PCI access mode", - the addresses of all the PCI SCSI controllers reported by the PCI - subsystem are probed as well. - - You want to read the start of <file:drivers/scsi/eata.c> and the - SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - Note that there is also another driver for the same hardware - available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, - Alphatronix) support". You should say Y to only one of them. - - 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 <file:Documentation/modules.txt>. The module - will be called eata.o. - -CONFIG_SCSI_EATA_TAGGED_QUEUE - 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. Most EATA adapters negotiate - this feature automatically with the device, even if your answer is - N. The safe answer is N. - -CONFIG_SCSI_EATA_LINKED_COMMANDS - 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... - The safe answer is N. - -CONFIG_SCSI_EATA_MAX_TAGS - This specifies how many SCSI commands can be maximally queued for - each probed SCSI device. You should reduce the default value of 16 - only if you have disks with buggy or limited tagged command support. - Minimum is 2 and maximum is 62. This value is also the window size - used by the elevator sorting option above. The effective value used - by the driver for each probed SCSI device is reported at boot time. - -CONFIG_SCSI_NCR53C406A - This is support for the NCR53c406a SCSI host adapter. For user - configurable parameters, check out <file:drivers/scsi/NCR53c406a.c> - in the kernel source. Also read the SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>. - - 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 <file:Documentation/modules.txt>. The module - will be called NCR53c406.o. - -CONFIG_SCSI_SYM53C416 - 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=<base>,<irq> [sym53c416_1=<base>,<irq>] - - 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 <file:Documentation/modules.txt>. The module will be called - sym53c416.o. - -CONFIG_SCSI_SIM710 - This is a simple driver for NCR53c710 based SCSI host adapters. - - More complex drivers for this chip are available ("NCR53c7,8xx SCSI - support", above), but they require that the scsi chip be able to do - DMA block moves between memory and on-chip registers, which can - cause problems under certain conditions. This driver is designed to - avoid these problems and is intended to work with any Intel machines - using 53c710 chips, including various Compaq and NCR machines. - - Please read the comments at the top of the file - <file:drivers/scsi/sim710.c> for more information. - - 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 <file:Documentation/modules.txt>. The module - will be called sim710.o. - -CONFIG_SCSI_DC390T - 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 <file:drivers/scsi/README.tmscsim>. - - 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 <file:Documentation/modules.txt>. The module - will be called tmscsim.o. - -CONFIG_SCSI_DC390T_NOGENSUPP - 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 <file:drivers/scsi/README.tmscsim>. - - 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. - -CONFIG_SCSI_AM53C974 - This is support for the AM53/79C974 SCSI host adapters. Please read - <file:drivers/scsi/README.AM53C974> for details. Also, the - SCSI-HOWTO, available from - <http://www.linuxdoc.org/docs.html#howto>, 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 <file:Documentation/modules.txt>. The module - will be called AM53C974.o. - -CONFIG_SCSI_MEGARAID - 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 <file:Documentation/modules.txt>. The module - will be called megaraid.o. - -CONFIG_SCSI_GDTH - 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 <file:drivers/scsi/gdth.c> and - <file:drivers/scsi/gdth.h.> - - 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>. - -CONFIG_SCSI_PPA - 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 <file:drivers/scsi/README.ppa>. You should also read - the SCSI-HOWTO, which is available from - <http://www.linuxdoc.org/docs.html#howto>. 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 - <file:Documentation/modules.txt>. The module will be called ppa.o. - -CONFIG_SCSI_IMM - 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 <file:drivers/scsi/README.ppa>. You should also read - the SCSI-HOWTO, which is available from - <http://www.linuxdoc.org/docs.html#howto>. 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 - <file:Documentation/modules.txt>. The module will be called imm.o. - -CONFIG_SCSI_IZIP_EPP16 - 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. - -CONFIG_SCSI_IZIP_SLOW_CTR - 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. - -CONFIG_SCSI_DEBUG - This is a host adapter simulator that can be programmed to simulate - a large number of conditions that could occur on a real bus. The - advantage is that many hard to reproduce problems can be tested in a - controlled environment where there is reduced risk of losing - important data. This is primarily of use to people trying to debug - the middle and upper layers of the SCSI subsystem. If unsure, say N. - -CONFIG_A4000T_SCSI - Support for the NCR53C710 SCSI controller on the Amiga 4000T. - -CONFIG_A4091_SCSI - 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. - -CONFIG_A3000_SCSI - 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.o. If you want to compile it as a module, say M here - and read <file:Documentation/modules.txt>. - -CONFIG_A2091_SCSI - 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.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_GVP11_SCSI - 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.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_CYBERSTORM_SCSI - If you have an Amiga with an original (MkI) Phase5 Cyberstorm - accelerator board and the optional Cyberstorm SCSI controller, - answer Y. Otherwise, say N. - -CONFIG_CYBERSTORMII_SCSI - If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board - and the optional Cyberstorm SCSI controller, say Y. Otherwise, - answer N. - -CONFIG_BLZ2060_SCSI - 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. - -CONFIG_BLZ1230_SCSI - 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. - -CONFIG_BLZ603EPLUS_SCSI - If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+ - accelerator, say Y. Otherwise, say N. - -CONFIG_FASTLANE_SCSI - 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. - -CONFIG_OKTAGON_SCSI - 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 - <http://amiga.multigraph.com/photos/oktagon.html>. - -CONFIG_SCSI_MESH - 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.o - ( = 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>. - -CONFIG_SCSI_MESH_SYNC_RATE - On Power Macintoshes (and clones) where the MESH SCSI bus adaptor - drives a bus which is entirely internal to the machine (such as the - 7500, 7600, 8500, etc.), the MESH is capable of synchronous - operation at up to 10 MB/s. On machines where the SCSI bus - controlled by the MESH can have external devices connected, it is - usually rated at 5 MB/s. 5 is a safe value here unless you know the - MESH SCSI bus is internal only; in that case you can say 10. Say 0 - to disable synchronous operation. - -CONFIG_SCSI_MAC53C94 - 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.o ( = 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>. - diff --git a/drivers/scsi/Config.in b/drivers/scsi/Config.in deleted file mode 100644 index c352ba966c66..000000000000 --- a/drivers/scsi/Config.in +++ /dev/null @@ -1,261 +0,0 @@ -comment 'SCSI support type (disk, tape, CD-ROM)' - -dep_tristate ' SCSI disk support' CONFIG_BLK_DEV_SD $CONFIG_SCSI - -dep_tristate ' SCSI tape support' CONFIG_CHR_DEV_ST $CONFIG_SCSI - -dep_tristate ' SCSI OnStream SC-x0 tape support' CONFIG_CHR_DEV_OSST $CONFIG_SCSI - -dep_tristate ' SCSI CDROM support' CONFIG_BLK_DEV_SR $CONFIG_SCSI - -if [ "$CONFIG_BLK_DEV_SR" != "n" ]; then - bool ' Enable vendor-specific extensions (for SCSI CDROM)' CONFIG_BLK_DEV_SR_VENDOR - int 'Maximum number of CDROM devices that can be loaded as modules' CONFIG_SR_EXTRA_DEVS 2 -fi -dep_tristate ' SCSI generic support' CONFIG_CHR_DEV_SG $CONFIG_SCSI - -comment 'Some SCSI devices (e.g. CD jukebox) support multiple LUNs' - -bool ' Probe all LUNs on each SCSI device' CONFIG_SCSI_MULTI_LUN -bool ' Build with SCSI REPORT LUNS support' CONFIG_SCSI_REPORT_LUNS - -bool ' Verbose SCSI error reporting (kernel size +=12K)' CONFIG_SCSI_CONSTANTS -bool ' SCSI logging facility' CONFIG_SCSI_LOGGING - -mainmenu_option next_comment -comment 'SCSI low-level drivers' - -if [ "$CONFIG_SGI_IP22" = "y" ]; then - dep_tristate 'SGI WD93C93 SCSI Driver' CONFIG_SGIWD93_SCSI $CONFIG_SCSI -fi -if [ "$CONFIG_DECSTATION" = "y" ]; then - if [ "$CONFIG_TC" = "y" ]; then - dep_tristate 'DEC NCR53C94 Scsi Driver' CONFIG_SCSI_DECNCR $CONFIG_SCSI - fi - dep_tristate 'DEC SII Scsi Driver' CONFIG_SCSI_DECSII $CONFIG_SCSI -fi - -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate '3ware Hardware ATA-RAID support' CONFIG_BLK_DEV_3W_XXXX_RAID $CONFIG_SCSI -fi -dep_tristate '7000FASST SCSI support' CONFIG_SCSI_7000FASST $CONFIG_SCSI $CONFIG_ISA -dep_tristate 'ACARD SCSI support' CONFIG_SCSI_ACARD $CONFIG_SCSI -if [ "$CONFIG_ISA" = "y" ]; then - dep_tristate 'Adaptec AHA152X/2825 support' CONFIG_SCSI_AHA152X $CONFIG_SCSI - dep_tristate 'Adaptec AHA1542 support' CONFIG_SCSI_AHA1542 $CONFIG_SCSI -fi -if [ "$CONFIG_EISA" = "y" ]; then - dep_tristate 'Adaptec AHA1740 support' CONFIG_SCSI_AHA1740 $CONFIG_SCSI -fi -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate 'Adaptec AACRAID support (EXPERIMENTAL)' CONFIG_SCSI_AACRAID $CONFIG_SCSI $CONFIG_PCI -fi -source drivers/scsi/aic7xxx/Config.in -if [ "$CONFIG_SCSI_AIC7XXX" != "y" ]; then - dep_tristate 'Old Adaptec AIC7xxx support' CONFIG_SCSI_AIC7XXX_OLD $CONFIG_SCSI -fi -# All the I2O code and drivers do not seem to be 64bit safe. -if [ "$CONFIG_X86_64" != "y" ]; then - dep_tristate 'Adaptec I2O RAID support ' CONFIG_SCSI_DPT_I2O $CONFIG_SCSI -fi -dep_tristate 'AdvanSys SCSI support' CONFIG_SCSI_ADVANSYS $CONFIG_SCSI -dep_tristate 'Always IN2000 SCSI support' CONFIG_SCSI_IN2000 $CONFIG_SCSI -# does not use pci dma and seems to be isa/onboard only for old machines -if [ "$CONFIG_X86_64" != "y" ]; then - dep_tristate 'AM53/79C974 PCI SCSI support' CONFIG_SCSI_AM53C974 $CONFIG_SCSI $CONFIG_PCI -fi -dep_tristate 'AMI MegaRAID support' CONFIG_SCSI_MEGARAID $CONFIG_SCSI - -dep_tristate 'BusLogic SCSI support' CONFIG_SCSI_BUSLOGIC $CONFIG_SCSI -if [ "$CONFIG_SCSI_BUSLOGIC" != "n" ]; then - bool ' Omit FlashPoint support' CONFIG_SCSI_OMIT_FLASHPOINT -fi -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate 'Compaq Fibre Channel 64-bit/66Mhz HBA support' CONFIG_SCSI_CPQFCTS $CONFIG_SCSI -fi -dep_tristate 'DMX3191D SCSI support' CONFIG_SCSI_DMX3191D $CONFIG_SCSI $CONFIG_PCI -dep_tristate 'DTC3180/3280 SCSI support' CONFIG_SCSI_DTC3280 $CONFIG_SCSI $CONFIG_ISA -dep_tristate 'EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support' CONFIG_SCSI_EATA $CONFIG_SCSI -if [ "$CONFIG_SCSI_EATA" != "n" ]; then - bool ' enable tagged command queueing' CONFIG_SCSI_EATA_TAGGED_QUEUE - bool ' enable elevator sorting' CONFIG_SCSI_EATA_LINKED_COMMANDS - int ' maximum number of queued commands' CONFIG_SCSI_EATA_MAX_TAGS 16 -fi -dep_tristate 'EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support' CONFIG_SCSI_EATA_DMA $CONFIG_SCSI -dep_tristate 'EATA-PIO (old DPT PM2001, PM2012A) support' CONFIG_SCSI_EATA_PIO $CONFIG_SCSI -dep_tristate 'Future Domain 16xx SCSI/AHA-2920A support' CONFIG_SCSI_FUTURE_DOMAIN $CONFIG_SCSI -if [ "$CONFIG_MCA" = "y" ]; then - dep_tristate 'Future Domain MCS-600/700 SCSI support' CONFIG_SCSI_FD_MCS $CONFIG_SCSI -fi -dep_tristate 'Intel/ICP (former GDT SCSI Disk Array) RAID Controller support' CONFIG_SCSI_GDTH $CONFIG_SCSI -dep_tristate 'Generic NCR5380/53c400 SCSI PIO support' CONFIG_SCSI_GENERIC_NCR5380 $CONFIG_SCSI -dep_tristate 'Generic NCR5380/53c400 SCSI MMIO support' CONFIG_SCSI_GENERIC_NCR5380_MMIO $CONFIG_SCSI -if [ "$CONFIG_SCSI_GENERIC_NCR5380" != "n" ]; then - bool ' Enable NCR53c400 extensions' CONFIG_SCSI_GENERIC_NCR53C400 -fi -if [ "$CONFIG_MCA" = "y" ]; then - dep_tristate 'IBMMCA SCSI support' CONFIG_SCSI_IBMMCA $CONFIG_SCSI - if [ "$CONFIG_SCSI_IBMMCA" != "n" ]; then - bool ' Standard SCSI-order' CONFIG_IBMMCA_SCSI_ORDER_STANDARD - bool ' Reset SCSI-devices at boottime' CONFIG_IBMMCA_SCSI_DEV_RESET - fi -fi -if [ "$CONFIG_X86" = "y" ]; then - dep_tristate 'IBM ServeRAID support' CONFIG_SCSI_IPS $CONFIG_SCSI $CONFIG_PCI -fi -dep_tristate 'Initio 9100U(W) support' CONFIG_SCSI_INITIO $CONFIG_SCSI $CONFIG_PCI -dep_tristate 'Initio INI-A100U2W support' CONFIG_SCSI_INIA100 $CONFIG_SCSI $CONFIG_PCI -if [ "$CONFIG_PARPORT" != "n" ]; then - dep_tristate 'IOMEGA parallel port (ppa - older drives)' CONFIG_SCSI_PPA $CONFIG_SCSI $CONFIG_PARPORT - dep_tristate 'IOMEGA parallel port (imm - newer drives)' CONFIG_SCSI_IMM $CONFIG_SCSI $CONFIG_PARPORT - if [ "$CONFIG_SCSI_PPA" != "n" -o "$CONFIG_SCSI_IMM" != "n" ]; then - bool ' ppa/imm option - Use slow (but safe) EPP-16' CONFIG_SCSI_IZIP_EPP16 - bool ' ppa/imm option - Assume slow parport control register' CONFIG_SCSI_IZIP_SLOW_CTR - fi -fi -dep_tristate 'NCR53c406a SCSI support' CONFIG_SCSI_NCR53C406A $CONFIG_SCSI $CONFIG_ISA -if [ "$CONFIG_MCA" = "y" ]; then - dep_tristate 'NCR Dual 700 MCA SCSI support' CONFIG_SCSI_NCR_D700 $CONFIG_SCSI - if [ "$CONFIG_SCSI_NCR_D700" != "n" ]; then - define_bool CONFIG_53C700_IO_MAPPED y - fi -fi -if [ "$CONFIG_PARISC" = "y" ]; then - dep_tristate 'HP LASI SCSI support for 53c700/710' CONFIG_SCSI_LASI700 $CONFIG_SCSI - if [ "$CONFIG_SCSI_LASI700" != "n" ]; then - define_bool CONFIG_53C700_MEM_MAPPED y - define_bool CONFIG_53C700_LE_ON_BE y - define_bool CONFIG_53C700_USE_CONSISTENT y - fi -fi -dep_tristate 'NCR53c7,8xx SCSI support' CONFIG_SCSI_NCR53C7xx $CONFIG_SCSI $CONFIG_PCI -if [ "$CONFIG_SCSI_NCR53C7xx" != "n" ]; then - bool ' always negotiate synchronous transfers' CONFIG_SCSI_NCR53C7xx_sync - bool ' allow FAST-SCSI [10MHz]' CONFIG_SCSI_NCR53C7xx_FAST - bool ' allow DISCONNECT' CONFIG_SCSI_NCR53C7xx_DISCONNECT -fi -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate 'SYM53C8XX Version 2 SCSI support' CONFIG_SCSI_SYM53C8XX_2 $CONFIG_SCSI - if [ "$CONFIG_SCSI_SYM53C8XX_2" != "n" ]; then - int ' DMA addressing mode' CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE 1 - int ' default tagged command queue depth' CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS 16 - int ' maximum number of queued commands' CONFIG_SCSI_SYM53C8XX_MAX_TAGS 64 - bool ' use normal IO' CONFIG_SCSI_SYM53C8XX_IOMAPPED - fi -fi -if [ "$CONFIG_PCI" = "y" -a "$CONFIG_SCSI_SYM53C8XX_2" != "y" ]; then - dep_tristate 'NCR53C8XX SCSI support' CONFIG_SCSI_NCR53C8XX $CONFIG_SCSI - dep_tristate 'SYM53C8XX SCSI support' CONFIG_SCSI_SYM53C8XX $CONFIG_SCSI - if [ "$CONFIG_SCSI_NCR53C8XX" != "n" -o "$CONFIG_SCSI_SYM53C8XX" != "n" ]; then - int ' default tagged command queue depth' CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS 8 - int ' maximum number of queued commands' CONFIG_SCSI_NCR53C8XX_MAX_TAGS 32 - int ' synchronous transfers frequency in MHz' CONFIG_SCSI_NCR53C8XX_SYNC 20 - bool ' enable profiling' CONFIG_SCSI_NCR53C8XX_PROFILE - bool ' use normal IO' CONFIG_SCSI_NCR53C8XX_IOMAPPED - if [ "$CONFIG_SCSI_SYM53C8XX" != "n" ]; then - bool ' include support for the NCR PQS/PDS SCSI card' CONFIG_SCSI_NCR53C8XX_PQS_PDS - fi - if [ "$CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS" = "0" ]; then - bool ' not allow targets to disconnect' CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT - fi - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool ' assume boards are SYMBIOS compatible (EXPERIMENTAL)' CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT - fi - fi -fi -if [ "$CONFIG_MCA" = "y" ]; then - dep_tristate 'NCR MCA 53C9x SCSI support' CONFIG_SCSI_MCA_53C9X $CONFIG_SCSI -fi -dep_tristate 'PAS16 SCSI support' CONFIG_SCSI_PAS16 $CONFIG_SCSI $CONFIG_ISA -dep_tristate 'PCI2000 support' CONFIG_SCSI_PCI2000 $CONFIG_SCSI -dep_tristate 'PCI2220i support' CONFIG_SCSI_PCI2220I $CONFIG_SCSI -dep_tristate 'PSI240i support' CONFIG_SCSI_PSI240I $CONFIG_SCSI $CONFIG_ISA -dep_tristate 'Qlogic FAS SCSI support' CONFIG_SCSI_QLOGIC_FAS $CONFIG_SCSI $CONFIG_ISA -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate 'Qlogic ISP SCSI support' CONFIG_SCSI_QLOGIC_ISP $CONFIG_SCSI - dep_tristate 'Qlogic ISP FC SCSI support' CONFIG_SCSI_QLOGIC_FC $CONFIG_SCSI - if [ "$CONFIG_SCSI_QLOGIC_FC" != "n" ]; then - bool ' Include loadable firmware in driver' CONFIG_SCSI_QLOGIC_FC_FIRMWARE - fi - dep_tristate 'Qlogic QLA 1280 SCSI support' CONFIG_SCSI_QLOGIC_1280 $CONFIG_SCSI -fi -if [ "$CONFIG_X86" = "y" -a "$CONFIG_ISA" = "y" ]; then - dep_tristate 'Seagate ST-02 and Future Domain TMC-8xx SCSI support' CONFIG_SCSI_SEAGATE $CONFIG_SCSI -fi -# definitely looks note 64bit safe: -if [ "$CONFIG_ISA" = "y" -o "$CONFIG_MCA" = "y" -a "$CONFIG_X86_64" != "y" ]; then - dep_tristate 'Simple 53c710 SCSI support (Compaq, NCR machines)' CONFIG_SCSI_SIM710 $CONFIG_SCSI -fi -dep_tristate 'Symbios 53c416 SCSI support' CONFIG_SCSI_SYM53C416 $CONFIG_SCSI $CONFIG_ISA -if [ "$CONFIG_PCI" = "y" ]; then - dep_tristate 'Tekram DC390(T) and Am53/79C974 SCSI support' CONFIG_SCSI_DC390T $CONFIG_SCSI - if [ "$CONFIG_SCSI_DC390T" != "n" ]; then - bool ' _omit_ support for non-DC390 adapters' CONFIG_SCSI_DC390T_NOGENSUPP - fi -fi -dep_tristate 'Trantor T128/T128F/T228 SCSI support' CONFIG_SCSI_T128 $CONFIG_SCSI $CONFIG_ISA -dep_tristate 'UltraStor 14F/34F support' CONFIG_SCSI_U14_34F $CONFIG_SCSI -if [ "$CONFIG_SCSI_U14_34F" != "n" ]; then - bool ' enable elevator sorting' CONFIG_SCSI_U14_34F_LINKED_COMMANDS - int ' maximum number of queued commands' CONFIG_SCSI_U14_34F_MAX_TAGS 8 -fi -if [ "$CONFIG_X86" = "y" -a "$CONFIG_ISA" = "y" ]; then - dep_tristate 'UltraStor SCSI support' CONFIG_SCSI_ULTRASTOR $CONFIG_SCSI -fi -dep_tristate 'Workbit NinjaSCSI-32Bi/UDE support' CONFIG_SCSI_NSP32 $CONFIG_SCSI -# -# Note - this is a very special 'host' adapter that simulates the presence of some disks. -# It can come in very handy for troubleshooting. Anyone else is welcome to use it - all -# you do is hack it to simulate the condition you want to test for, and then use it. -# -# The actual configuration in any kernel release could change at any time as I hack it to -# simulate various conditions that I am testing. -# -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - dep_tristate 'SCSI debugging host simulator (EXPERIMENTAL)' CONFIG_SCSI_DEBUG $CONFIG_SCSI -fi -if [ "$CONFIG_ALL_PPC" = "y" ]; then - dep_tristate 'MESH (Power Mac internal SCSI) support' CONFIG_SCSI_MESH $CONFIG_SCSI - if [ "$CONFIG_SCSI_MESH" != "n" ]; then - int ' maximum synchronous transfer rate (MB/s) (0 = async)' CONFIG_SCSI_MESH_SYNC_RATE 5 - int ' initial bus reset delay (ms) (0 = no reset)' CONFIG_SCSI_MESH_RESET_DELAY_MS 4000 - fi - dep_tristate '53C94 (Power Mac external SCSI) support' CONFIG_SCSI_MAC53C94 $CONFIG_SCSI -fi -if [ "$CONFIG_ARCH_ACORN" = "y" ]; then - source drivers/acorn/scsi/Config.in -fi -if [ "$CONFIG_MIPS_JAZZ" = "y" ]; then - bool 'MIPS JAZZ FAS216 SCSI support' CONFIG_JAZZ_ESP -fi - -if [ "$CONFIG_AMIGA" = "y" ]; then - dep_tristate 'A3000 WD33C93A support' CONFIG_A3000_SCSI $CONFIG_SCSI - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool 'A4000T SCSI support (EXPERIMENTAL)' CONFIG_A4000T_SCSI - fi -fi -if [ "$CONFIG_ZORRO" = "y" ]; then - dep_tristate 'A2091/A590 WD33C93A support' CONFIG_A2091_SCSI $CONFIG_SCSI - dep_tristate 'GVP Series II WD33C93A support' CONFIG_GVP11_SCSI $CONFIG_SCSI - dep_tristate 'CyberStorm SCSI support' CONFIG_CYBERSTORM_SCSI $CONFIG_SCSI - dep_tristate 'CyberStorm Mk II SCSI support' CONFIG_CYBERSTORMII_SCSI $CONFIG_SCSI - dep_tristate 'Blizzard 2060 SCSI support' CONFIG_BLZ2060_SCSI $CONFIG_SCSI - dep_tristate 'Blizzard 1230IV/1260 SCSI support' CONFIG_BLZ1230_SCSI $CONFIG_SCSI - dep_tristate 'Fastlane SCSI support' CONFIG_FASTLANE_SCSI $CONFIG_SCSI - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool 'A4091 SCSI support (EXPERIMENTAL)' CONFIG_A4091_SCSI - bool 'WarpEngine SCSI support (EXPERIMENTAL)' CONFIG_WARPENGINE_SCSI - bool 'Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)' CONFIG_BLZ603EPLUS_SCSI - dep_tristate 'BSC Oktagon SCSI support (EXPERIMENTAL)' CONFIG_OKTAGON_SCSI $CONFIG_SCSI -# bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI -# bool 'GVP Turbo 040/060 SCSI support (EXPERIMENTAL)' CONFIG_GVP_TURBO_SCSI - fi -fi - -endmenu - -if [ "$CONFIG_HOTPLUG" = "y" -a "$CONFIG_PCMCIA" != "n" ]; then - source drivers/scsi/pcmcia/Config.in -fi - diff --git a/drivers/scsi/aic7xxx/Config.help b/drivers/scsi/aic7xxx/Config.help deleted file mode 100644 index c9f2666dbdfe..000000000000 --- a/drivers/scsi/aic7xxx/Config.help +++ /dev/null @@ -1,39 +0,0 @@ -CONFIG_SCSI_AIC7XXX - This driver supports all of Adaptec's PCI based SCSI controllers - (not the hardware RAID controllers though) as well as the aic7770 - based EISA and VLB SCSI controllers (the 274x and 284x series). - This is an Adaptec sponsored driver written by Justin Gibbs. It is - intended to replace the previous aic7xxx driver maintained by Doug - Ledford since Doug is no longer maintaining that driver. - -CONFIG_AIC7XXX_CMDS_PER_DEVICE - Specify the number of commands you would like to allocate per SCSI - device when Tagged Command Queueing (TCQ) is enabled on that device. - - This is an upper bound value for the number of tagged transactions - to be used for any device. The aic7xxx driver will automatically - vary this number based on device behavior. For devices with a - fixed maximum, the driver will eventually lock to this maximum - and display a console message inidicating this value. - - Note: Unless you experience some type of device failure, the default - value, no enforced limit, should work for you. - - Default: 253 - -CONFIG_AIC7XXX_RESET_DELAY_MS - The number of milliseconds to delay after an initial bus reset. - The bus settle delay following all error recovery actions is - dictated by the SCSI layer and is not affected by this value. - - Default: 15000 (15 seconds) - -CONFIG_AIC7XXX_BUILD_FIRMWARE - 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 make file or the files it includes if your - build environment is different than that of the author. - diff --git a/drivers/scsi/aic7xxx/Config.in b/drivers/scsi/aic7xxx/Config.in deleted file mode 100644 index cba211350d52..000000000000 --- a/drivers/scsi/aic7xxx/Config.in +++ /dev/null @@ -1,8 +0,0 @@ -if [ "$CONFIG_SCSI_AIC7XXX_OLD" != "y" ]; then - dep_tristate 'Adaptec AIC7xxx support' CONFIG_SCSI_AIC7XXX $CONFIG_SCSI - if [ "$CONFIG_SCSI_AIC7XXX" != "n" ]; then - int ' Maximum number of TCQ commands per device' CONFIG_AIC7XXX_CMDS_PER_DEVICE 253 - int ' Initial bus reset delay in milli-seconds' CONFIG_AIC7XXX_RESET_DELAY_MS 15000 - bool ' Build Adapter Firmware with Kernel Build' CONFIG_AIC7XXX_BUILD_FIRMWARE - fi -fi diff --git a/drivers/scsi/pcmcia/Config.help b/drivers/scsi/pcmcia/Config.help deleted file mode 100644 index c7aa46f608a8..000000000000 --- a/drivers/scsi/pcmcia/Config.help +++ /dev/null @@ -1,46 +0,0 @@ -CONFIG_SCSI_PCMCIA - Say Y here if you intend to attach a PCMCIA or CardBus card to your - computer which acts as a SCSI host adapter. These are credit card - size devices often used with laptops. - - 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 PCMCIA SCSI host adapters. - -CONFIG_PCMCIA_NINJA_SCSI - If you intend to attach this type of PCMCIA SCSI host adapter to - your computer, say Y here and read - <file:Documentation/README.nsp_cs.eng>. - - This driver is also available as a module called nsp_cs.o ( = - 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>. - -CONFIG_PCMCIA_AHA152X - 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.o ( = - 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>. - -CONFIG_PCMCIA_QLOGIC - 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.o ( = - 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>. - -CONFIG_PCMCIA_FDOMAIN - 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.o ( = - 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>. - diff --git a/drivers/scsi/pcmcia/Config.in b/drivers/scsi/pcmcia/Config.in deleted file mode 100644 index 9f32e3fb7e53..000000000000 --- a/drivers/scsi/pcmcia/Config.in +++ /dev/null @@ -1,21 +0,0 @@ -# -# PCMCIA SCSI adapter configuration -# - -mainmenu_option next_comment -comment 'PCMCIA SCSI adapter support' - -bool 'PCMCIA SCSI adapter support' CONFIG_SCSI_PCMCIA -if [ "$CONFIG_SCSI_PCMCIA" = "y" ]; then - dep_tristate ' Adaptec AHA152X PCMCIA support' CONFIG_PCMCIA_AHA152X m - dep_tristate ' Future Domain PCMCIA support' CONFIG_PCMCIA_FDOMAIN m - dep_tristate ' NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support' CONFIG_PCMCIA_NINJA_SCSI m - dep_tristate ' Qlogic PCMCIA support' CONFIG_PCMCIA_QLOGIC m -fi - -if [ "$CONFIG_PCMCIA_QLOGIC" = "y" -o "$CONFIG_PCMCIA_AHA152X" = "y" -o \ - "$CONFIG_PCMCIA_FDOMAIN" = "y" -o "$CONFIG_PCMCIA_NINJA_SCSI" = "y" ]; then - define_bool CONFIG_PCMCIA_SCSICARD y -fi - -endmenu diff --git a/drivers/serial/Config.help b/drivers/serial/Config.help deleted file mode 100644 index fccf27c710f9..000000000000 --- a/drivers/serial/Config.help +++ /dev/null @@ -1,231 +0,0 @@ -# $Id: Config.help,v 1.5 2002/07/06 17:16:24 rmk Exp $ - -CONFIG_SERIAL_8250 - This selects whether you want to include the driver for the standard - serial ports. The standard answer is Y. People who might say N - here are those that are setting up dedicated Ethernet WWW/FTP - servers, or users that have one of the various bus mice instead of a - serial mouse and don't intend to use their machine's standard serial - port for anything. (Note that the Cyclades and Stallion multi - serial port drivers do not need this driver built in for them to - work.) - - If you want to compile this driver as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - serial.o. - [WARNING: Do not compile this driver as a module if you are using - non-standard serial ports, since the configuration information will - be lost when the driver is unloaded. This limitation may be lifted - in the future.] - - BTW1: If you have a mouseman serial mouse which is not recognized by - the X window system, try running gpm first. - - BTW2: If you intend to use a software modem (also called Winmodem) - under Linux, forget it. These modems are crippled and require - proprietary drivers which are only available under Windows. - - Most people will say Y or M here, so that they can use serial mice, - modems and similar devices connecting to the standard serial ports. - -CONFIG_SERIAL_8250_CONSOLE - If you say Y here, it will be possible to use a serial port as the - system console (the system console is the device which receives all - kernel messages and warnings and which allows logins in single user - mode). This could be useful if some terminal or printer is connected - to that serial port. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyS1". (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.) - - If you don't have a VGA card installed and you say Y here, the - kernel will automatically use the first serial line, /dev/ttyS0, as - system console. - - If unsure, say N. - -CONFIG_SERIAL_8250_CS - Say Y here to enable support for 16-bit PCMCIA serial devices, - including serial port cards, modems, and the modem functions of - multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are - credit-card size devices often used with laptops.) - - 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 serial_cs.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - If unsure, say N. - -CONFIG_SERIAL_8250_EXTENDED - If you wish to use any non-standard features of the standard "dumb" - driver, say Y here. This includes HUB6 support, shared serial - interrupts, special multiport support, support for more than the - four COM 1/2/3/4 boards, etc. - - 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 serial driver options. If unsure, say N. - -CONFIG_SERIAL_8250_MANY_PORTS - Say Y here if you have dumb serial boards other than the four - standard COM 1/2/3/4 ports. This may happen if you have an AST - FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available - from <http://www.linuxdoc.org/docs.html#howto>), or other custom - serial port hardware which acts similar to standard serial port - hardware. If you only use the standard COM 1/2/3/4 ports, you can - say N here to save some memory. You can also say Y if you have an - "intelligent" multiport card such as Cyclades, Digiboards, etc. - -CONFIG_SERIAL_8250_SHARE_IRQ - Some serial boards have hardware support which allows multiple dumb - serial ports on the same board to share a single IRQ. To enable - support for this in the serial driver, say Y here. - -CONFIG_SERIAL_8250_DETECT_IRQ - Say Y here if you want the kernel to try to guess which IRQ - to use for your serial port. - - This is considered unsafe; it is far better to configure the IRQ in - a boot script using the setserial command. - - If unsure, say N. - -CONFIG_SERIAL_8250_MULTIPORT - Some multiport serial ports have special ports which are used to - signal when there are any serial ports on the board which need - servicing. Say Y here to enable the serial driver to take advantage - of those special I/O ports. - -CONFIG_SERIAL_8250_RSA - ::: To be written ::: - -CONFIG_SERIAL_8250_ACORN - If you have an Atomwide Serial card or Serial Port card for an Acorn - system, say Y to this option. The driver can handle 1, 2, or 3 port - cards. If unsure, say N. - -CONFIG_SERIAL_ANAKIN - ::: To be written ::: - -CONFIG_SERIAL_ANAKIN_CONSOLE - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyAN0". (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.) - -CONFIG_ANAKIN_DEFAULT_BAUDRATE - ::: To be written ::: - -CONFIG_SERIAL_AMBA - This selects the ARM(R) AMBA(R) PrimeCell UART. If you have an - Integrator platform, say Y or M here. - - If unsure, say N. - -CONFIG_SERIAL_AMBA_CONSOLE - Say Y here if you wish to use an AMBA PrimeCell UART as the system - console (the system console is the device which receives all kernel - messages and warnings and which allows logins in single user mode). - - Even if you say Y here, the currently visible framebuffer console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyAM0". (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.) - -CONFIG_SERIAL_CLPS711X - ::: To be written ::: - -CONFIG_SERIAL_CLPS711X_CONSOLE - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyCL1". (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.) - -CONFIG_SERIAL_CLPS711X_OLD_NAME - ::: To be written ::: - -CONFIG_SERIAL_21285 - If you have a machine based on a 21285 (Footbridge) StrongARM(R)/ - PCI bridge you can enable its onboard serial port by enabling this - option. - -CONFIG_SERIAL_21285_OLD - Use the old /dev/ttyS name, major 4 minor 64. This is obsolete - and will be removed during later 2.5 development. - -CONFIG_SERIAL_21285_CONSOLE - If you have enabled the serial port on the 21285 footbridge you can - make it the console by answering Y to this option. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyFB". (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.) - -CONFIG_SERIAL_UART00 - Say Y here if you want to use the hard logic uart on Excalibur. This - driver also supports soft logic implentations of this uart core. - -CONFIG_SERIAL_UART00_CONSOLE - Say Y here if you want to support a serial console on an Excalibur - hard logic uart or uart00 IP core. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyS1". (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.) - -CONFIG_SERIAL_SA1100 - If you have a machine based on a SA1100/SA1110 StrongARM(R) CPU you - can enable its onboard serial port by enabling this option. - Please read <file:Documentation/arm/SA1100/serial_UART> for further - info. - -CONFIG_SERIAL_SA1100_CONSOLE - If you have enabled the serial port on the SA1100/SA1110 StrongARM - CPU you can make it the console by answering Y to this option. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttySA0". (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.) - -#CONFIG_SERIAL_L7200 -# If you have a LinkUp Systems L7200 board you can enable its two -# onboard serial ports by enabling this option. The device numbers -# are major ID 4 with minor 64 and 65 respectively. -# -#CONFIG_SERIAL_L7200_CONSOLE -# If you have enabled the serial ports on the L7200 development board -# you can make the first serial port the console by answering Y to -# this option. - -CONFIG_SERIAL_SUNZILOG - This driver supports the Zilog8530 serial ports found on many Sparc - systems. Say Y or M if you want to be able to these serial ports. - -CONFIG_SERIAL_SUNSU - This driver supports the 8250 serial ports that run the keyboard and - mouse on (PCI) UltraSPARC systems. Say Y or M if you want to be able - to these serial ports. - -CONFIG_SERIAL_SUNSAB - This driver supports the Siemens SAB82532 DUSCC serial ports on newer - (PCI) UltraSPARC systems. Say Y or M if you want to be able to these - serial ports. diff --git a/drivers/serial/Config.in b/drivers/serial/Config.in deleted file mode 100644 index 71637638d4d8..000000000000 --- a/drivers/serial/Config.in +++ /dev/null @@ -1,86 +0,0 @@ -# -# Serial device configuration -# -# $Id: Config.in,v 1.15 2002/07/06 17:16:24 rmk Exp $ -# -mainmenu_option next_comment -comment 'Serial drivers' - -# -# The new 8250/16550 serial drivers -dep_tristate '8250/16550 and compatible serial support (EXPERIMENTAL)' CONFIG_SERIAL_8250 $CONFIG_EXPERIMENTAL -dep_bool ' Console on 8250/16550 and compatible serial port (EXPERIMENTAL)' CONFIG_SERIAL_8250_CONSOLE $CONFIG_SERIAL_8250 $CONFIG_EXPERIMENTAL -dep_tristate ' 8250/16550 PCMCIA device support' CONFIG_SERIAL_8250_CS $CONFIG_PCMCIA $CONFIG_SERIAL_8250 - -dep_mbool 'Extended 8250/16550 serial driver options' CONFIG_SERIAL_8250_EXTENDED $CONFIG_SERIAL_8250 -dep_bool ' Support more than 4 serial ports' CONFIG_SERIAL_8250_MANY_PORTS $CONFIG_SERIAL_8250_EXTENDED -dep_bool ' Support for sharing serial interrupts' CONFIG_SERIAL_8250_SHARE_IRQ $CONFIG_SERIAL_8250_EXTENDED -dep_bool ' Autodetect IRQ on standard ports (unsafe)' CONFIG_SERIAL_8250_DETECT_IRQ $CONFIG_SERIAL_8250_EXTENDED -dep_bool ' Support special multiport boards' CONFIG_SERIAL_8250_MULTIPORT $CONFIG_SERIAL_8250_EXTENDED -dep_bool ' Support RSA serial ports' CONFIG_SERIAL_8250_RSA $CONFIG_SERIAL_8250_EXTENDED - -comment 'Non-8250 serial port support' - -if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate 'Acorn expansion card serial port support' CONFIG_SERIAL_8250_ACORN $CONFIG_ARCH_ACORN $CONFIG_SERIAL_8250 - dep_bool 'Anakin serial port support' CONFIG_SERIAL_ANAKIN $CONFIG_ARCH_ANAKIN - dep_bool ' Console on Anakin serial port' CONFIG_SERIAL_ANAKIN_CONSOLE $CONFIG_SERIAL_ANAKIN - if [ "$CONFIG_SERIAL_ANAKIN" = "y" ]; then - int ' Default Anakin serial baudrate' CONFIG_ANAKIN_DEFAULT_BAUDRATE 9600 - fi - - dep_tristate 'ARM AMBA serial port support' CONFIG_SERIAL_AMBA $CONFIG_ARCH_INTEGRATOR - dep_bool ' Support for console on AMBA serial port' CONFIG_SERIAL_AMBA_CONSOLE $CONFIG_SERIAL_AMBA - if [ "$CONFIG_SERIAL_AMBA" = "y" ]; then - define_bool CONFIG_SERIAL_INTEGRATOR y - fi - - dep_tristate 'CLPS711X serial port support' CONFIG_SERIAL_CLPS711X $CONFIG_ARCH_CLPS711X - dep_bool ' Support for console on CLPS711X serial port' CONFIG_SERIAL_CLPS711X_CONSOLE $CONFIG_SERIAL_CLPS711X - dep_bool ' Use the old 2.4 names for CLPS711X serial port' CONFIG_SERIAL_CLPS711X_OLD_NAME $CONFIG_SERIAL_CLPS711X - - dep_tristate 'DC21285 serial port support' CONFIG_SERIAL_21285 $CONFIG_FOOTBRIDGE - dep_bool ' Use /dev/ttyS0 device (OBSOLETE)' CONFIG_SERIAL_21285_OLD $CONFIG_SERIAL_21285 $CONFIG_OBSOLETE - dep_bool ' Console on DC21285 serial port' CONFIG_SERIAL_21285_CONSOLE $CONFIG_SERIAL_21285 - - dep_bool 'Excalibur serial port (uart00) support' CONFIG_SERIAL_UART00 $CONFIG_ARCH_CAMELOT - dep_bool ' Support for console on Excalibur serial port' CONFIG_SERIAL_UART00_CONSOLE $CONFIG_SERIAL_UART00 - - dep_bool 'SA1100 serial port support' CONFIG_SERIAL_SA1100 $CONFIG_ARCH_SA1100 - dep_bool ' Console on SA1100 serial port' CONFIG_SERIAL_SA1100_CONSOLE $CONFIG_SERIAL_SA1100 -fi - -if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - define_bool CONFIG_SERIAL_SUNCORE y - tristate 'Sun Zilog8530 serial support' CONFIG_SERIAL_SUNZILOG - dep_tristate 'Sun SU serial support' CONFIG_SERIAL_SUNSU $CONFIG_PCI - dep_tristate 'Sun Siemens SAB82532 serial support' CONFIG_SERIAL_SUNSAB $CONFIG_PCI -fi - -if [ "$CONFIG_SERIAL_AMBA" = "y" -o "$CONFIG_SERIAL_CLPS711X" = "y" -o \ - "$CONFIG_SERIAL_21285" = "y" -o "$CONFIG_SERIAL_SA1100" = "y" -o \ - "$CONFIG_SERIAL_ANAKIN" = "y" -o "$CONFIG_SERIAL_UART00" = "y" -o \ - "$CONFIG_SERIAL_8250" = "y" -o "$CONFIG_SERIAL_ROCKETPORT" = "y" -o \ - "$CONFIG_SERIAL_SUNCORE" = "y" ]; then - define_bool CONFIG_SERIAL_CORE y -else - if [ "$CONFIG_SERIAL_AMBA" = "m" -o "$CONFIG_SERIAL_CLPS711X" = "m" -o \ - "$CONFIG_SERIAL_21285" = "m" -o "$CONFIG_SERIAL_SA1100" = "m" -o \ - "$CONFIG_SERIAL_ANAKIN" = "m" -o "$CONFIG_SERIAL_UART00" = "m" -o \ - "$CONFIG_SERIAL_8250" = "m" -o "$CONFIG_SERIAL_ROCKETPORT" = "m" -o \ - "$CONFIG_SERIAL_SUNCORE" = "m" ]; then - define_bool CONFIG_SERIAL_CORE m - fi -fi -if [ "$CONFIG_SERIAL_AMBA_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_CLPS711X_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_21285_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_SA1100_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_ANAKIN_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_UART00_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_8250_CONSOLE" = "y" -o \ - "$CONFIG_SERIAL_SUNCORE" = "y" ]; then - define_bool CONFIG_SERIAL_CORE_CONSOLE y -fi - -endmenu diff --git a/drivers/sgi/Config.help b/drivers/sgi/Config.help deleted file mode 100644 index 78ff4c19fc6b..000000000000 --- a/drivers/sgi/Config.help +++ /dev/null @@ -1,38 +0,0 @@ -CONFIG_SGI_SERIAL - If you want to use your SGI's built-in serial ports under Linux, - answer Y. - -CONFIG_SGI_NEWPORT_GFX - If you have an SGI machine and you want to compile the graphics - drivers, say Y here. This will include the code for the - /dev/graphics and /dev/gfx drivers into the kernel for supporting - virtualized access to your graphics hardware. - -CONFIG_SGI_DS1286 - If you say Y here and create a character special file /dev/rtc with - major number 10 and minor number 135 using mknod ("man mknod"), you - will get access to the real time clock built into your computer. - Every SGI has such a clock built in. It reports status information - via the file /proc/rtc and its behaviour is set by various ioctls on - /dev/rtc. - -CONFIG_SERIAL_CONSOLE - If you say Y here, it will be possible to use a serial port as the - system console (the system console is the device which receives all - kernel messages and warnings and which allows logins in single user - mode). This could be useful if some terminal or printer is connected - to that serial port. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyS1". (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.) - - If you don't have a VGA card installed and you say Y here, the - kernel will automatically use the first serial line, /dev/ttyS0, as - system console. - - If unsure, say N. - diff --git a/drivers/sgi/Config.in b/drivers/sgi/Config.in deleted file mode 100644 index 082be90d44c2..000000000000 --- a/drivers/sgi/Config.in +++ /dev/null @@ -1,17 +0,0 @@ -# -# Character device configuration -# -mainmenu_option next_comment -comment 'SGI devices' - -bool 'SGI Zilog85C30 serial support' CONFIG_SGI_SERIAL -if [ "$CONFIG_SGI_SERIAL" = "y" ]; then - bool ' Support for console on serial port' CONFIG_SERIAL_CONSOLE -fi -bool 'SGI DS1286 RTC support' CONFIG_SGI_DS1286 - -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - tristate 'SGI Newport Graphics support (EXPERIMENTAL)' CONFIG_SGI_NEWPORT_GFX -fi - -endmenu diff --git a/drivers/telephony/Config.help b/drivers/telephony/Config.help deleted file mode 100644 index 0fd20fdc6ae9..000000000000 --- a/drivers/telephony/Config.help +++ /dev/null @@ -1,33 +0,0 @@ -CONFIG_PHONE - Say Y here if you have a telephony card, which for example allows - you to use a regular phone for voice-over-IP applications. - - Note: this has nothing to do with modems. You do not need to say Y - here in order to be able to use a modem under Linux. - - This support is also available as a module. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. The module will be called - phonedev.o. - -CONFIG_PHONE_IXJ - Say M if you have a telephony card manufactured by Quicknet - Technologies, Inc. These include the Internet PhoneJACK and - Internet LineJACK Telephony Cards. You will get a module called - ixj.o. - - For the ISA versions of these products, you can configure the - cards using the isapnp tools (pnpdump/isapnp) or you can use the - isapnp support. Please read <file:Documentation/telephony/ixj.txt>. - - For more information on these cards, see Quicknet's web site at: - <http://www.quicknet.net/>. - - If you do not have any Quicknet telephony cards, you can safely - say N here. - -CONFIG_PHONE_IXJ_PCMCIA - Say Y here to configure in PCMCIA service support for the Quicknet - cards manufactured by Quicknet Technologies, Inc. This changes the - card initialization code to work with the card manager daemon. - diff --git a/drivers/telephony/Config.in b/drivers/telephony/Config.in deleted file mode 100644 index d13601df6dc5..000000000000 --- a/drivers/telephony/Config.in +++ /dev/null @@ -1,10 +0,0 @@ -# -# Telephony device configuration -# -mainmenu_option next_comment -comment 'Telephony Support' - -tristate 'Linux telephony support' CONFIG_PHONE -dep_tristate 'QuickNet Internet LineJack/PhoneJack support' CONFIG_PHONE_IXJ $CONFIG_PHONE -dep_tristate 'QuickNet Internet LineJack/PhoneJack PCMCIA support' CONFIG_PHONE_IXJ_PCMCIA $CONFIG_PHONE_IXJ -endmenu diff --git a/drivers/usb/Config.help b/drivers/usb/Config.help deleted file mode 100644 index 034627ab0e43..000000000000 --- a/drivers/usb/Config.help +++ /dev/null @@ -1,84 +0,0 @@ -CONFIG_USB - Universal Serial Bus (USB) is a specification for a serial bus - subsystem which offers higher speeds and more features than the - traditional PC serial port. The bus supplies power to peripherals - and allows for hot swapping. Up to 127 USB peripherals can be - connected to a single USB port in a tree structure. The USB port is - the root of the tree, the peripherals are the leaves and the inner - nodes are special USB devices called hubs. Many newer PC's have USB - ports and newer peripherals such as scanners, keyboards, mice, - modems, and printers support the USB protocol and can be connected - to the PC via those ports. - - Say Y here if your computer has a USB port and you want to use USB - devices. You then need to say Y to at least one of "UHCI HCD support" - or "OHCI HCD support" below (the type of interface that the USB hardware - in your computer provides to the operating system) and then choose - from amongst the drivers for USB peripherals. You may want to check - out the information provided in <file:Documentation/usb/> and - especially the links given in <file:Documentation/usb/usb-help.txt>. - - If you have a new USB 2.0 High Speed system, you should also choose - "EHCI HCD (USB 2.0) support" as well as at least one of UHCI or OHCI. - - It doesn't normally hurt to select them all if you are not certain. - - 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 usbcore.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_DEBUG - Say Y here if you want the USB core & hub drivers to produce a bunch - of debug messages to the system log. Select this if you are having a - problem with USB support and want to see more of what is going on. - -CONFIG_USB_LONG_TIMEOUT - This option makes the standard time out a bit longer. Basically, - some devices are just slow to respond, so this makes usb more - patient. There should be no harm in selecting this, but it is - needed for some MGE Ellipse UPSes. - - If you have an MGE Ellipse UPS, or you see timeouts in HID - transactions, say Y; otherwise say N. - -CONFIG_USB_DEVICEFS - If you say Y here (and to "/proc file system support" in the "File - systems" section, above), you will get a file /proc/bus/usb/devices - which lists the devices currently connected to your USB bus or - busses, a file /proc/bus/usb/drivers which lists the USB kernel - client drivers currently loaded, and for every connected device a - file named "/proc/bus/usb/xxx/yyy", where xxx is the bus number and - yyy the device number; the latter files can be used by user space - programs to talk directly to the device. These files are "virtual", - meaning they are generated on the fly and not stored on the hard - drive. - - You may need to mount the usbfs file system to see the files, use - mount -t usbfs none /proc/bus/usb - - For the format of the various /proc/bus/usb/ files, please read - <file:Documentation/usb/proc_usb_info.txt>. - - Please note that this code is completely unrelated to devfs, the - "/dev file system support". - - Most users want to say Y here. - -CONFIG_USB_BANDWIDTH - If you say Y here, the USB subsystem enforces USB bandwidth - allocation and will prevent some device opens from succeeding - if they would cause USB bandwidth usage to go above 90% of - the bus bandwidth. - - If you say N here, these conditions will cause warning messages - about USB bandwidth usage to be logged and some devices or - drivers may not work correctly. - -CONFIG_USB_DYNAMIC_MINORS - If you say Y here, the USB subsystem will use dynamic minor - allocation for any device that uses the USB major number. - This means that you can have more than 16 of a single type - of device (like USB printers). - - If you are unsure about this, say N here. diff --git a/drivers/usb/Config.in b/drivers/usb/Config.in deleted file mode 100644 index 47dcd1ce0172..000000000000 --- a/drivers/usb/Config.in +++ /dev/null @@ -1,38 +0,0 @@ -# -# USB device configuration -# -mainmenu_option next_comment -comment 'USB support' - -# ARM SA1111 chips have a non-PCI based "OHCI-compatible" USB host interface. -if [ "$CONFIG_PCI" = "y" -o "$CONFIG_SA1111" = "y" ]; then - tristate 'Support for USB' CONFIG_USB -else - define_bool CONFIG_USB n -fi - -if [ "$CONFIG_USB" = "y" -o "$CONFIG_USB" = "m" ]; then - source drivers/usb/core/Config.in - - source drivers/usb/host/Config.in - - source drivers/usb/class/Config.in - - source drivers/usb/storage/Config.in - - source drivers/usb/input/Config.in - - source drivers/usb/image/Config.in - - source drivers/usb/media/Config.in - - source drivers/usb/net/Config.in - - comment 'USB port drivers' - dep_tristate ' USS720 parport driver' CONFIG_USB_USS720 $CONFIG_USB $CONFIG_PARPORT - - source drivers/usb/serial/Config.in - - source drivers/usb/misc/Config.in -fi -endmenu diff --git a/drivers/usb/class/Config.help b/drivers/usb/class/Config.help deleted file mode 100644 index d745878ca6f6..000000000000 --- a/drivers/usb/class/Config.help +++ /dev/null @@ -1,68 +0,0 @@ -CONFIG_USB_ACM - This driver supports USB modems and ISDN adapters which support the - Communication Device Class Abstract Control Model interface. - Please read <file:Documentation/usb/acm.txt> for details. - - If your modem only reports "Cls=ff(vend.)" in the descriptors in - /proc/bus/usb/devices, then your modem will not work with this - driver. - - 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 acm.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_AUDIO - Say Y here if you want to connect USB audio equipment such as - speakers to your computer's USB port. - - 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 audio.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_BLUETOOTH_TTY - Say Y here if you want to connect a USB Bluetooth device to your - computer's USB port. You will need the Bluetooth stack (available - at <http://developer.axis.com/software/index.shtml>) to fully use - the device. - - This driver implements a tty inteface to a Bluetooth device. If - you want to use a socket based Bluetooth stack (like the BlueZ - stack), do not use this driver. - - If in doubt, say N here. - - 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 bluetty.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_MIDI - Say Y here if you want to connect a USB MIDI device to your - computer's USB port. This driver is for devices that comply with - 'Universal Serial Bus Device Class Definition for MIDI Device'. - - The following devices are known to work: - * Steinberg USB2MIDI - * Roland MPU64 - * Roland PC-300 - * Roland SC8850 - * Roland UM-1 - * Roland UM-2 - * Roland UA-100 - * Yamaha MU1000 - - 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 usb-midi.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_PRINTER - Say Y here if you want to connect a USB printer to your computer's - USB port. - - 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 printer.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/class/Config.in b/drivers/usb/class/Config.in deleted file mode 100644 index 3ec8aef9881c..000000000000 --- a/drivers/usb/class/Config.in +++ /dev/null @@ -1,9 +0,0 @@ -# -# USB Class driver configuration -# -comment 'USB Device Class drivers' -dep_tristate ' USB Audio support' CONFIG_USB_AUDIO $CONFIG_USB $CONFIG_SOUND -dep_tristate ' USB Bluetooth TTY support' CONFIG_USB_BLUETOOTH_TTY $CONFIG_USB -dep_tristate ' USB MIDI support' CONFIG_USB_MIDI $CONFIG_USB -dep_tristate ' USB Modem (CDC ACM) support' CONFIG_USB_ACM $CONFIG_USB -dep_tristate ' USB Printer support' CONFIG_USB_PRINTER $CONFIG_USB diff --git a/drivers/usb/core/Config.in b/drivers/usb/core/Config.in deleted file mode 100644 index d1415e679f10..000000000000 --- a/drivers/usb/core/Config.in +++ /dev/null @@ -1,11 +0,0 @@ -# -# USB Core configuration -# -bool ' USB verbose debug messages' CONFIG_USB_DEBUG - -comment 'Miscellaneous USB options' - bool ' USB device filesystem' CONFIG_USB_DEVICEFS - bool ' Long timeout for slow-responding devices (some MGE Ellipse UPSes)' CONFIG_USB_LONG_TIMEOUT -dep_bool ' Enforce USB bandwidth allocation (EXPERIMENTAL)' CONFIG_USB_BANDWIDTH $CONFIG_EXPERIMENTAL -dep_bool ' Dynamic USB minor allocation (EXPERIMENTAL)' CONFIG_USB_DYNAMIC_MINORS $CONFIG_EXPERIMENTAL - diff --git a/drivers/usb/host/Config.help b/drivers/usb/host/Config.help deleted file mode 100644 index e344fde05e8f..000000000000 --- a/drivers/usb/host/Config.help +++ /dev/null @@ -1,63 +0,0 @@ -CONFIG_USB_EHCI_HCD - The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0 - "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware. - If your USB host controller supports USB 2.0, you will likely want to - configure this Host Controller Driver. At this writing, the primary - implementation of EHCI is a chip from NEC, widely available in add-on - PCI cards, but implementations are in the works from other vendors - including Intel and Philips. Motherboard support is appearing. - - EHCI controllers are packaged with "companion" host controllers (OHCI - or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports - will connect to EHCI if it the device is high speed, otherwise they - connect to a companion controller. If you configure EHCI, you should - probably configure the OHCI (for NEC and some other vendors) USB Host - Controller Driver or UHCI (for Via motherboards) Host Controller - Driver too. - - You may want to read <file:Documentation/usb/ehci.txt>. - - 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 ehci-hcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_OHCI_HCD - The Open Host Controller Interface (OHCI) is a standard for accessing - USB 1.1 host controller hardware. It does more in hardware than Intel's - UHCI specification. If your USB host controller follows the OHCI spec, - say Y. On most non-x86 systems, and on x86 hardware that's not using a - USB controller from Intel or VIA, this is appropriate. If your host - controller doesn't use PCI, this is probably appropriate. For a PCI - based system where you're not sure, the "lspci -v" entry will list the - right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI. - - 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 ohci-hcd.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_UHCI_HCD_ALT - The Universal Host Controller Interface is a standard by Intel for - accessing the USB hardware in the PC (which is also called the USB - host controller). If your USB host controller conforms to this - standard, you may want to say Y, but see below. All recent boards - with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX, - i810, i820) conform to this standard. Also all VIA PCI chipsets - (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro - 133). If unsure, say Y. - - 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 uhci-hcd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SL811HS - Say Y here if you have a SL811HS USB host controller in your system. - - If you do not know what this is, please say N. - - 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 hc_sl811.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/host/Config.in b/drivers/usb/host/Config.in deleted file mode 100644 index 0a6f97342a77..000000000000 --- a/drivers/usb/host/Config.in +++ /dev/null @@ -1,10 +0,0 @@ -# -# USB Host Controller Drivers -# -comment 'USB Host Controller Drivers' -dep_tristate ' EHCI HCD (USB 2.0) support' CONFIG_USB_EHCI_HCD $CONFIG_USB -dep_tristate ' OHCI HCD support' CONFIG_USB_OHCI_HCD $CONFIG_USB -dep_tristate ' UHCI HCD (most Intel and VIA) support' CONFIG_USB_UHCI_HCD_ALT $CONFIG_USB -if [ "$CONFIG_ARM" = "y" ]; then - dep_tristate ' SL811HS support' CONFIG_USB_SL811HS $CONFIG_USB -fi diff --git a/drivers/usb/image/Config.help b/drivers/usb/image/Config.help deleted file mode 100644 index 46666cdbbd65..000000000000 --- a/drivers/usb/image/Config.help +++ /dev/null @@ -1,36 +0,0 @@ -CONFIG_USB_MDC800 - Say Y here if you want to connect this type of still camera to - your computer's USB port. This driver can be used with gphoto 0.4.3 - and higher (look at <http://www.gphoto.org/>). - To use it create a device node with "mknod /dev/mustek c 180 32" and - configure it in your software. - - 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 mdc800.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_HPUSBSCSI - Say Y here if you want support for the HP 53xx series of scanners - and the Minolta Scan Dual. This driver is experimental. - The scanner will be accessible as a SCSI device. - This can be compiled as a module, called hpusbscsi.o. - -CONFIG_USB_MICROTEK - Say Y here if you want support for the Microtek X6USB and - possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L. - Support for anything but the X6 is experimental. - Please report failures and successes. - The scanner will appear as a scsi generic device to the rest - of the system. Scsi support is required. - This driver can be compiled as a module, called microtek.o. - -CONFIG_USB_SCANNER - Say Y here if you want to connect a USB scanner to your computer's - USB port. Please read <file:Documentation/usb/scanner.txt> and - <file:Documentation/usb/scanner-hp-sane.txt> for more information. - - 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 scanner.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/image/Config.in b/drivers/usb/image/Config.in deleted file mode 100644 index f9e60d7af52d..000000000000 --- a/drivers/usb/image/Config.in +++ /dev/null @@ -1,8 +0,0 @@ -# -# USB Imageing devices configuration -# -comment 'USB Imaging devices' -dep_tristate ' USB Mustek MDC800 Digital Camera support (EXPERIMENTAL)' CONFIG_USB_MDC800 $CONFIG_USB $CONFIG_EXPERIMENTAL -dep_tristate ' USB Scanner support' CONFIG_USB_SCANNER $CONFIG_USB -dep_tristate ' Microtek X6USB scanner support' CONFIG_USB_MICROTEK $CONFIG_USB $CONFIG_SCSI -dep_tristate ' HP53xx USB scanner support (EXPERIMENTAL)' CONFIG_USB_HPUSBSCSI $CONFIG_USB $CONFIG_SCSI $CONFIG_EXPERIMENTAL diff --git a/drivers/usb/input/Config.help b/drivers/usb/input/Config.help deleted file mode 100644 index d6b6afe5c57e..000000000000 --- a/drivers/usb/input/Config.help +++ /dev/null @@ -1,139 +0,0 @@ -CONFIG_USB_HID - Say Y here if you want full HID support to connect keyboards, - mice, joysticks, graphic tablets, or any other HID based devices - to your computer via USB. You also need to select HID Input layer - support (below) if you want to use keyboards, mice, joysticks and - the like. - - You can't use this driver and the HIDBP (Boot Protocol) keyboard - and mouse drivers at the same time. More information is available: - <file:Documentation/input/input.txt>. - - If unsure, say Y. - - 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 hid.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_HIDINPUT - Say Y here if you want to use a USB keyboard, mouse or joystick, - or any other HID input device. You also need "Input core support", - (CONFIG_INPUT), which you select under "Input device support", above. - - If unsure, say Y. - -CONFIG_HID_FF - Say Y here is you want force feedback support for a few HID devices. See - below for a list of supported devices. - See Documentation/input/ff.txt for a description of the force feedback API. - - If unsure, say N. - -CONFIG_LOGITECH_FF - Say Y here if you have one of these devices: - - Logitech WingMan Cordless RumblePad - - Logitech WingMan Force 3D - and if you want to enable force feedback for them. - Note: if you say N here, this device will still be supported, but without - force feedback. - -CONFIG_HID_PID - Say Y here if you have a PID-compliant joystick and wish to enable force - feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such - device. - -CONFIG_LOGITECH_3D - Say Y here if you have a Logitech force feedback device from the - *3D family. - -CONFIG_USB_HIDDEV - Say Y here if you want to support HID devices (from the USB - specification standpoint) that aren't strictly user interface - devices, like monitor controls and Uninterruptable Power Supplies. - - This module supports these devices separately using a separate - event interface on /dev/usb/hiddevX (char 180:96 to 180:111). - This driver requires CONFIG_USB_HID. - - If unsure, say Y. - -CONFIG_USB_KBD - Say Y here only if you are absolutely sure that you don't want - to use the generic HID driver for your USB keyboard and prefer - to use the keyboard in its limited Boot Protocol mode instead. - - This is almost certainly not what you want. This is mostly - useful for embedded applications or simple keyboards. - - 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 usbkbd.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - - If even remotely unsure, say N. - -CONFIG_USB_MOUSE - Say Y here only if you are absolutely sure that you don't want - to use the generic HID driver for your USB keyboard and prefer - to use the keyboard in its limited Boot Protocol mode instead. - - This is almost certainly not what you want. This is mostly - useful for embedded applications or simple mice. - - 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 usbmouse.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - - If even remotely unsure, say N. - -CONFIG_USB_AIPTEK - Say Y here if you want to use the USB version of the Aiptek 6000U - or Aiptek 8000U tablet. Make sure to say Y to "Mouse support" - (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" - (CONFIG_INPUT_EVDEV) 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 aiptek.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_WACOM - Say Y here if you want to use the USB version of the Wacom Intuos - or Graphire tablet. Make sure to say Y to "Mouse support" - (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" - (CONFIG_INPUT_EVDEV) 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 wacom.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_POWERMATE - Say Y here if you want to use Griffin PowerMate or Contour Jog devices. - These are stainless steel dials which can measure clockwise and - anticlockwise rotation. The dial also acts as a pushbutton. The base - contains an LED which can be instructed to pulse or to switch to a - particular intensity. - - You can download userspace tools from http://sowerbutts.com/powermate/ - - 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 powermate.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_XPAD - Say Y here if you want to use the X-Box pad with your computer. - Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV) - and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. - - For information about how to connect the X-Box pad to USB, see - Documentation/input/xpad.txt. - - 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 wacom.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - diff --git a/drivers/usb/input/Config.in b/drivers/usb/input/Config.in deleted file mode 100644 index 318ee15e075b..000000000000 --- a/drivers/usb/input/Config.in +++ /dev/null @@ -1,28 +0,0 @@ -# -# USB Input driver configuration -# -comment 'USB Human Interface Devices (HID)' -dep_tristate ' USB Human Interface Device (full HID) support' CONFIG_USB_HID $CONFIG_USB - -if [ "$CONFIG_INPUT" = "n" ]; then - comment ' Input core support is needed for USB HID input layer or HIDBP support' -fi - -dep_mbool ' HID input layer support' CONFIG_USB_HIDINPUT $CONFIG_INPUT $CONFIG_USB_HID -dep_mbool ' Force feedback support (EXPERIMENTAL)' CONFIG_HID_FF $CONFIG_USB_HIDINPUT $CONFIG_EXPERIMENTAL -dep_mbool ' PID Devices' CONFIG_HID_PID $CONFIG_USB_HID $CONFIG_HID_FF -dep_mbool ' Logitech WingMan *3D support' CONFIG_LOGITECH_FF $CONFIG_USB_HID $CONFIG_HID_FF -dep_mbool ' /dev/hiddev raw HID device support' CONFIG_USB_HIDDEV $CONFIG_USB_HID - -if [ "$CONFIG_USB_HID" != "y" ]; then - mainmenu_option next_comment - comment 'USB HID Boot Protocol drivers' - dep_tristate ' USB HIDBP Keyboard (simple Boot) support' CONFIG_USB_KBD $CONFIG_USB $CONFIG_INPUT - dep_tristate ' USB HIDBP Mouse (simple Boot) support' CONFIG_USB_MOUSE $CONFIG_USB $CONFIG_INPUT - endmenu -fi - -dep_tristate ' Aiptek 6000U/8000U tablet support' CONFIG_USB_AIPTEK $CONFIG_USB $CONFIG_INPUT -dep_tristate ' Wacom Intuos/Graphire tablet support' CONFIG_USB_WACOM $CONFIG_USB $CONFIG_INPUT -dep_tristate ' Griffin PowerMate and Contour Jog support' CONFIG_USB_POWERMATE $CONFIG_USB $CONFIG_INPUT -dep_tristate ' X-Box gamepad support' CONFIG_USB_XPAD $CONFIG_USB $CONFIG_INPUT diff --git a/drivers/usb/media/Config.help b/drivers/usb/media/Config.help deleted file mode 100644 index 127c0797854a..000000000000 --- a/drivers/usb/media/Config.help +++ /dev/null @@ -1,148 +0,0 @@ -CONFIG_USB_DABUSB - A Digital Audio Broadcasting (DAB) Receiver for USB and Linux - brought to you by the DAB-Team (<http://dab.in.tum.de/>). This - driver can be taken as an example for URB-based bulk, control, and - isochronous transactions. URB's are explained in - <file:Documentation/usb/URB.txt>. - - 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 dabusb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_DSBR - Say Y here if you want to connect this type of radio to your - computer's USB port. Note that the audio is not digital, and - you must connect the line out connector to a sound card or a - set of speakers. - - This driver uses the Video For Linux API. You must enable - (Y or M in config) Video For Linux (under Character Devices) - to use this driver. Information on this API and pointers to - "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 dsbr100.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_IBMCAM - Say Y here if you want to connect a IBM "C-It" camera, also known as - "Xirlink PC Camera" to your computer's USB port. For more - information, read <file:Documentation/usb/ibmcam.txt>. - - This driver uses the Video For Linux API. You must enable - (Y or M in config) Video For Linux (under Character Devices) - to use this driver. Information on this API and pointers to - "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 ibmcam.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. This - camera has several configuration options which can be specified when - you load the module. Read <file:Documentation/usb/ibmcam.txt> to - learn more. - -CONFIG_USB_KONICAWC - Say Y here if you want support for webcams based on a Konica - chipset. This is known to work with the Intel YC76 webcam. - - This driver uses the Video For Linux API. You must enable - (Y or M in config) Video For Linux (under Character Devices) - to use this driver. Information on this API and pointers to - "v4l" programs may be found on the WWW at - <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 konicawc.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_OV511 - Say Y here if you want to connect this type of camera to your - computer's USB port. See <file:Documentation/usb/ov511.txt> for more - information and for a list of supported cameras. - - This driver uses the Video For Linux API. You must say Y or M to - "Video For Linux" (under Character Devices) to use this driver. - Information on this API and pointers to "v4l" programs may be found - on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 ov511.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_PWC - Say Y or M here if you want to use one of these Philips USB webcams: - PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or - the Askey VC010. The PCA635, PCVC665 and PCVC720 are not supported - by this driver and never will be. - - This driver has an optional plugin, which is distributed as a binary - module only. It contains code that allow you to use higher - resolutions and framerates but may not be distributed as source. - But even without this plugin you can these cams for most - applications. - - See <file:Documentation/usb/philips.txt> for more information and - installation instructions. - - The built-in microphone is enabled by selecting USB Audio support. - - This driver uses the Video For Linux API. You must say Y or M to - "Video For Linux" (under Character Devices) to use this driver. - Information on this API and pointers to "v4l" programs may be found - on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 pwc.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SE401 - Say Y here if you want to connect this type of camera to your - computer's USB port. See <file:Documentation/usb/se401.txt> for more - information and for a list of supported cameras. - - This driver uses the Video For Linux API. You must say Y or M to - "Video For Linux" (under Multimedia Devices) to use this driver. - Information on this API and pointers to "v4l" programs may be found - on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 se401.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_STV680 - Say Y here if you want to connect this type of camera to your - computer's USB port. This includes the Pencam line of cameras. - See <file:Documentation/usb/stv680.txt> for more information and for - a list of supported cameras. - - This driver uses the Video For Linux API. You must say Y or M to - "Video For Linux" (under Multimedia Devices) to use this driver. - Information on this API and pointers to "v4l" programs may be found - on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 stv680.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_VICAM - Say Y here if you have 3com homeconnect camera (vicam). - - This driver uses the Video For Linux API. You must say Y or M to - "Video For Linux" (under Multimedia Devices) to use this driver. - Information on this API and pointers to "v4l" programs may be found - on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. - - 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 vicam.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/media/Config.in b/drivers/usb/media/Config.in deleted file mode 100644 index 79fccfe4623e..000000000000 --- a/drivers/usb/media/Config.in +++ /dev/null @@ -1,16 +0,0 @@ -# -# USB Multimedia device configuration -# -comment 'USB Multimedia devices' -dep_tristate ' DABUSB driver' CONFIG_USB_DABUSB $CONFIG_USB -if [ "$CONFIG_VIDEO_DEV" = "n" ]; then - comment ' Video4Linux support is needed for USB Multimedia device support' -fi -dep_tristate ' USB 3com HomeConnect (aka vicam) support (EXPERIMENTAL)' CONFIG_USB_VICAM $CONFIG_USB $CONFIG_VIDEO_DEV $CONFIG_EXPERIMENTAL -dep_tristate ' D-Link USB FM radio support (EXPERIMENTAL)' CONFIG_USB_DSBR $CONFIG_USB $CONFIG_VIDEO_DEV $CONFIG_EXPERIMENTAL -dep_tristate ' USB IBM (Xirlink) C-it Camera support' CONFIG_USB_IBMCAM $CONFIG_USB $CONFIG_VIDEO_DEV -dep_tristate ' USB Konica Webcam support' CONFIG_USB_KONICAWC $CONFIG_USB $CONFIG_VIDEO_DEV -dep_tristate ' USB OV511 Camera support' CONFIG_USB_OV511 $CONFIG_USB $CONFIG_VIDEO_DEV -dep_tristate ' USB Philips Cameras' CONFIG_USB_PWC $CONFIG_USB $CONFIG_VIDEO_DEV -dep_tristate ' USB SE401 Camera support' CONFIG_USB_SE401 $CONFIG_USB $CONFIG_VIDEO_DEV -dep_tristate ' USB STV680 (Pencam) Camera support' CONFIG_USB_STV680 $CONFIG_USB $CONFIG_VIDEO_DEV diff --git a/drivers/usb/misc/Config.help b/drivers/usb/misc/Config.help deleted file mode 100644 index fadb396f6206..000000000000 --- a/drivers/usb/misc/Config.help +++ /dev/null @@ -1,130 +0,0 @@ -CONFIG_USB_AUERSWALD - Say Y here if you want to connect an Auerswald USB ISDN Device - to your computer's USB port. - - 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 auerswald.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_BRLVGER - Say Y here if you want to use the Voyager USB Braille display from - Tieman. See <file:Documentation/usb/brlvger.txt> for more - information. - - 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 brlvger.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_EMI26 - This driver loads firmware to Emagic EMI 2|6 low latency USB - Audio interface. - - After firmware load the device is handled with standard linux - USB Audio driver. - - 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 audio.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_RIO500 - Say Y here if you want to connect a USB Rio500 mp3 player to your - computer's USB port. Please read <file:Documentation/usb/rio.txt> - for more information. - - 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 rio500.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_TIGL - If you own a Texas Instruments graphing calculator and use a - TI-GRAPH LINK USB cable (aka SilverLink), then you might be - interested in this driver. - - If you enable this driver, you will be able to communicate with - your calculator through a set of device nodes under /dev. - - 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 tiglusb.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. - - If you don't know what the SilverLink cable is or what a Texas - Instruments graphing calculator is, then you probably don't need this - driver. - - If unsure, say N. - -CONFIG_USB_USS720 - This driver is for USB parallel port adapters that use the Lucent - Technologies USS-720 chip. These cables are plugged into your USB - port and provide USB compatibility to peripherals designed with - parallel port interfaces. - - The chip has two modes: automatic mode and manual mode. In automatic - mode, it looks to the computer like a standard USB printer. Only - printers may be connected to the USS-720 in this mode. The generic - USB printer driver ("USB Printer support", above) may be used in - that mode, and you can say N here if you want to use the chip only - in this mode. - - Manual mode is not limited to printers, any parallel port - device should work. This driver utilizes manual mode. - Note however that some operations are three orders of magnitude - slower than on a PCI/ISA Parallel Port, so timing critical - applications might not work. - - Say Y here if you own an USS-720 USB->Parport cable and intend to - connect anything other than a printer to it. - - 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 uss720.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SPEEDTCH - - This driver provides support for the Alcatel SpeedTouch ADSL USB - modem. - - The driver requires the ATM interface and ATM SAR so you need to - enable ATM (under Networking options) and the ATM SAR option. You - will also need PPP over ATM (under Network device support). - - This driver is a slightly revised version of Johan Verrept's 1.5 - SpeedTouch Driver which has been altered to work on the 2.5 series - kernels. - - To use the device you also need a user-mode daemon that downloads - the firmware and (re)initializes the modem. The offical version is - a closed source one from Alcatel that you can get at - <http://www.alcateldsl.com/support.htm>. - - A piece of code has recently been sent to linux-usb-devel which - allows the open source user space driver's firmware program - modem_run to be used with this driver instead. You will still - need the Alcatel daemon package to extract the modem firmware from - it (or the windows drivers instead). - - For more information, see Johan Verrept's webpages at - <http://linux-usb.sourceforge.net/SpeedTouch/>. - -CONFIG_USB_TEST - - This driver is for testing host controller software. It is used - with specialized device firmware for regression and stress testing, - to help prevent problems from cropping up with 'real" drivers. - -CONFIG_USB_LCD - Say Y here if you want to connect an USBLCD to your computer's - USB port. The USBLCD is a small USB interface board for - alphanumeric LCD modules. See <http://www.usblcd.de> for more - information. - - 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 usblcd.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/misc/Config.in b/drivers/usb/misc/Config.in deleted file mode 100644 index 7a8c2574e9fc..000000000000 --- a/drivers/usb/misc/Config.in +++ /dev/null @@ -1,12 +0,0 @@ -# -# USB Miscellaneous driver configuration -# -comment 'USB Miscellaneous drivers' -dep_tristate ' EMI 2|6 USB Audio interface support' CONFIG_USB_EMI26 $CONFIG_USB_AUDIO -dep_tristate ' Texas Instruments Graph Link USB (aka SilverLink) cable support' CONFIG_USB_TIGL $CONFIG_USB -dep_tristate ' USB Auerswald ISDN support (EXPERIMENTAL)' CONFIG_USB_AUERSWALD $CONFIG_USB $CONFIG_EXPERIMENTAL -dep_tristate ' USB Diamond Rio500 support (EXPERIMENTAL)' CONFIG_USB_RIO500 $CONFIG_USB $CONFIG_EXPERIMENTAL -dep_tristate ' Tieman Voyager USB Braille display support (EXPERIMENTAL)' CONFIG_USB_BRLVGER $CONFIG_USB $CONFIG_EXPERIMENTAL -dep_tristate ' USB LCD driver support' CONFIG_USB_LCD $CONFIG_USB -dep_tristate ' Alcatel Speedtouch ADSL USB Modem' CONFIG_USB_SPEEDTOUCH $CONFIG_USB $CONFIG_ATM -dep_tristate ' USB testing driver (DEVELOPMENT)' CONFIG_USB_TEST $CONFIG_USB_DEVICEFS $CONFIG_EXPERIMENTAL diff --git a/drivers/usb/net/Config.help b/drivers/usb/net/Config.help deleted file mode 100644 index 6d37db685b96..000000000000 --- a/drivers/usb/net/Config.help +++ /dev/null @@ -1,118 +0,0 @@ -CONFIG_USB_CATC - Say Y if you want to use one of the following 10Mbps USB Ethernet - device based on the EL1210A chip. Supported devices are: - Belkin F5U011 - Belkin F5U111 - CATC NetMate - CATC NetMate II - smartBridges smartNIC - - This driver makes the adapter appear as a normal Ethernet interface, - typically on eth0, if it is the only ethernet device, or perhaps on - eth1, if you have a PCI or ISA ethernet card installed. - - 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 catc.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_CDCETHER - This driver supports devices conforming to the Communication Device - Class Ethernet Control Model. This is used in some cable modems. - For more details on the specification, get the Communication Device - Class specification from <http://www.usb.org/>. - - This driver should work with the following devices: - * Ericsson PipeRider (all variants) - * Motorola (DM100 and SB4100) - * Broadcom Cable Modem (reference design) - * Toshiba PCX1100U and possibly other cable modems - - The device creates a network device (ethX, where X depends on what - other networking devices you have in use), as for a normal PCI - or ISA based ethernet network 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 cdc-ether.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_KAWETH - Say Y here if you want to use one of the following 10Mbps only - USB Ethernet adapters based on the KLSI KL5KUSB101B chipset: - 3Com 3C19250 - ADS USB-10BT - ATEN USB Ethernet - ASANTE USB To Ethernet Adapter - AOX Endpoints USB Ethernet - Correga K.K. - D-Link DSB-650C and DU-E10 - Entrega / Portgear E45 - I-O DATA USB-ET/T - Jaton USB Ethernet Device Adapter - Kingston Technology USB Ethernet Adapter - Linksys USB10T - Mobility USB-Ethernet Adapter - NetGear EA-101 - Peracom Enet and Enet2 - Portsmith Express Ethernet Adapter - Shark Pocket Adapter - SMC 2202USB - Sony Vaio port extender - - This driver is likely to work with most 10Mbps only USB Ethernet - adapters, including some "no brand" devices. It does NOT work on - SmartBridges smartNIC or on Belkin F5U111 devices - you should use - the CATC NetMate driver for those. If you are not sure which one - you need, select both, and the correct one should be selected for - you. - - This driver makes the adapter appear as a normal Ethernet interface, - typically on eth0, if it is the only ethernet device, or perhaps on - eth1, if you have a PCI or ISA ethernet card installed. - - 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 kaweth.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_PEGASUS - Say Y here if you know you have Pegasus or Pegasus-II based adapter. - If in doubt then look at linux/drivers/usb/pegasus.h for the complete - list of supported devices. - If your particular adapter is not in the list and you are _sure_ it - is Pegasus or Pegasus II based then send me (petkan@users.sourceforge.net) - vendor and device IDs. - - 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 pegasus.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_RTL8150 - Say Y here if you have RTL8150 based usb-ethernet adapter. - Send me (petkan@users.sourceforge.net) any comments you may have. - You can also check for updates at http://pegasus2.sourceforge.net/ - - 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 rtl8150.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_USBNET - This driver supports network links over USB with USB "Network" - or "data transfer" cables, often used to network laptops to PCs. - Such cables have chips from suppliers such as Belkin/eTEK, GeneSys - (GeneLink), NetChip and Prolific. Intelligent USB devices could also - use this approach to provide Internet access, using standard USB - cabling. You can find these chips also on some motherboards with - USB PC2PC support. - - These links will have names like "usb0", "usb1", etc. They act - like two-node Ethernets, so you can use 802.1d Ethernet Bridging - (CONFIG_BRIDGE) to simplify your network routing. - - This code is also available as a kernel module (code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called usbnet.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. diff --git a/drivers/usb/net/Config.in b/drivers/usb/net/Config.in deleted file mode 100644 index 6f4d4563b379..000000000000 --- a/drivers/usb/net/Config.in +++ /dev/null @@ -1,14 +0,0 @@ -# -# USB Network devices configuration -# -comment 'USB Network adaptors' -if [ "$CONFIG_NET" = "n" ]; then - comment ' Networking support is needed for USB Networking device support' -else - dep_tristate ' USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)' CONFIG_USB_CATC $CONFIG_USB $CONFIG_NET $CONFIG_EXPERIMENTAL - dep_tristate ' USB CDC Ethernet support (EXPERIMENTAL)' CONFIG_USB_CDCETHER $CONFIG_USB $CONFIG_NET $CONFIG_EXPERIMENTAL - dep_tristate ' USB KLSI KL5USB101-based ethernet device support' CONFIG_USB_KAWETH $CONFIG_USB $CONFIG_NET - dep_tristate ' USB Pegasus/Pegasus-II based ethernet device support' CONFIG_USB_PEGASUS $CONFIG_USB $CONFIG_NET - dep_tristate ' USB RTL8150 based ethernet device support (EXPERIMENTAL)' CONFIG_USB_RTL8150 $CONFIG_USB $CONFIG_NET $CONFIG_EXPERIMENTAL - dep_tristate ' USB-to-USB Networking cable device support' CONFIG_USB_USBNET $CONFIG_USB $CONFIG_NET -fi diff --git a/drivers/usb/serial/Config.help b/drivers/usb/serial/Config.help deleted file mode 100644 index 3a00c995da1b..000000000000 --- a/drivers/usb/serial/Config.help +++ /dev/null @@ -1,299 +0,0 @@ -CONFIG_USB_SERIAL - Say Y here if you have a USB device that provides normal serial - ports, or acts like a serial device, and you want to connect it to - your USB bus. - - Please read <file:Documentation/usb/usb-serial.txt> for more - information on the specifics of the different devices that are - supported, and on how to use them. - - 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 usbserial.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_CONSOLE - If you say Y here, it will be possible to use a USB to serial - converter port as the system console (the system console is the - device which receives all kernel messages and warnings and which - allows logins in single user mode). This could be useful if some - terminal or printer is connected to that serial port. - - Even if you say Y here, the currently visible virtual console - (/dev/tty0) will still be used as the system console by default, but - you can alter that using a kernel command line option such as - "console=ttyUSB0". (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.) - - If you don't have a VGA card installed and you say Y here, the - kernel will automatically use the first USB to serial converter - port, /dev/ttyUSB0, as system console. - - If unsure, say N. - -CONFIG_USB_SERIAL_GENERIC - Say Y here if you want to use the generic USB serial driver. Please - read <file:Documentation/usb/usb-serial.txt> for more information on - using this driver. It is recommended that the "USB Serial converter - support" be compiled as a module for this driver to be used - properly. - -CONFIG_USB_SERIAL_WHITEHEAT - Say Y here if you want to use a ConnectTech WhiteHEAT 4 port - USB to serial converter device. - - 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 whiteheat.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_VISOR - Say Y here if you want to connect to your HandSpring Visor, Palm - m500 or m505 through its USB docking station. See - <http://usbvisor.sourceforge.net/> for more information on using this - driver. - - 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 visor.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_IPAQ - Say Y here if you want to connect to your Compaq iPAQ, HP Jornada - 548/568 or Casio EM500 running Windows CE 3.0 or PocketPC 2002 - using a USB cradle/cable. For information on using the driver, - read <file:Documentation/usb/usb-serial.txt>. - - 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 ipaq.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_IR - Say Y here if you want to enable simple serial support for USB IrDA - devices. This is useful if you do not want to use the full IrDA - stack. - - 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 ir-usb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_IR - Say Y here if you want to enable simple serial support for USB IrDA - devices. This is useful if you do not want to use the full IrDA - stack. - - 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 ir-usb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_BELKIN - Say Y here if you want to use a Belkin USB Serial single port - adaptor (F5U103 is one of the model numbers) or the Peracom single - port USB to serial adapter. - - 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 belkin_sa.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_FTDI_SIO - Say Y here if you want to use a FTDI SIO single port USB to serial - converter device. The implementation I have is called the USC-1000. - This driver has also be tested with the 245 and 232 devices. - - See <http://ftdi-usb-sio.sourceforge.net/> for more - information on this driver and the device. - - 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 ftdi_sio.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_KEYSPAN_PDA - Say Y here if you want to use a Keyspan PDA single port USB to - serial converter device. This driver makes use of firmware - developed from scratch by Brian Warner. - - 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 keyspan_pda.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_XIRCOM - Say Y here if you want to use a Xircom or Entregra single port USB to - serial converter device. This driver makes use of firmware - developed from scratch by Brian Warner. - - 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 keyspan_pda.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_KEYSPAN - Say Y here if you want to use Keyspan USB to serial converter - devices. This driver makes use of Keyspan's official firmware - and was developed with their support. You must also include - firmware to support your particular device(s). - - See <http://misc.nu/hugh/keyspan.html> for more information. - - 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 keyspan.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_KEYSPAN_USA28 - Say Y here to include firmware for the USA-28 converter. - -CONFIG_USB_SERIAL_KEYSPAN_USA28X - Say Y here to include firmware for the USA-28X converter. - Be sure you have a USA-28X, there are also 28XA and 28XB - models, the label underneath has the actual part number. - -CONFIG_USB_SERIAL_KEYSPAN_USA28XA - Say Y here to include firmware for the USA-28XA converter. - Be sure you have a USA-28XA, there are also 28X and 28XB - models, the label underneath has the actual part number. - -CONFIG_USB_SERIAL_KEYSPAN_USA28XB - Say Y here to include firmware for the USA-28XB converter. - Be sure you have a USA-28XB, there are also 28X and 28XA - models, the label underneath has the actual part number. - -CONFIG_USB_SERIAL_KEYSPAN_USA19 - Say Y here to include firmware for the USA-19 converter. - -CONFIG_USB_SERIAL_KEYSPAN_USA18X - Say Y here to include firmware for the USA-18X converter. - -CONFIG_USB_SERIAL_KEYSPAN_USA19W - Say Y here to include firmware for the USA-19W converter. - -CONFIG_USB_SERIAL_KEYSPAN_USA49W - Say Y here to include firmware for the USA-49W converter. - -CONFIG_USB_SERIAL_OMNINET - Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA. - - 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 omninet.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_DIGI_ACCELEPORT - Say Y here if you want to use Digi AccelePort USB 2 or 4 devices, - 2 port (plus parallel port) and 4 port USB serial converters. The - parallel port on the USB 2 appears as a third serial port on Linux. - The Digi Acceleport USB 8 is not yet supported by this driver. - - This driver works under SMP with the usb-uhci driver. It does not - work under SMP with the uhci driver. - - 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 digi_acceleport.o. If you want to compile - it as a module, say M here and read - <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_EMPEG - Say Y here if you want to connect to your Empeg empeg-car Mark I/II - mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...} - device node. See <file:Documentation/usb/usb-serial.txt> for more - tidbits of information. - - 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 empeg.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_MCT_U232 - Say Y here if you want to use a USB Serial single port adapter from - Magic Control Technology Corp. (U232 is one of the model numbers). - - This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB - BAY devices. - - 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 mct_u232.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_PL2303 - Say Y here if you want to use the PL2303 USB Serial single port - adapter from Prolific. - - 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 pl2303.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_CYBERJACK - Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard - reader. This is an interface to ISO 7816 compatible contactbased - chipcards, e.g. GSM SIMs. - - 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 cyberjack.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - - If unsure, say N. - -CONFIG_USB_SERIAL_EDGEPORT - Say Y here if you want to use any of the following devices from - Inside Out Networks (Digi): - Edgeport/4 - Rapidport/4 - Edgeport/4t - Edgeport/2 - Edgeport/4i - Edgeport/2i - Edgeport/421 - Edgeport/21 - Edgeport/8 - Edgeport/8 Dual - Edgeport/2D8 - Edgeport/4D8 - Edgeport/8i - Edgeport/2 DIN - Edgeport/4 DIN - Edgeport/16 Dual - - 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 io_edgeport.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_EDGEPORT_TI - Say Y here if you want to use any of the devices from Inside Out - Networks (Digi) that are not supported by the io_edgeport driver. - This includes the Edgeport/1 device. - - 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 io_ti.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_KLSI - Say Y here if you want to use a KL5KUSB105 - based single port - serial adapter. The most widely known -- and currently the only - tested -- device in this category is the PalmConnect USB Serial - adapter sold by Palm Inc. for use with their Palm III and Palm V - series PDAs. - - Please read <file:Documentation/usb/usb-serial.txt> for more - information. - - 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 kl5kusb105.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_SERIAL_DEBUG - Say Y here if you want verbose debug messages from the USB Serial - Drivers sent to the kernel debug log. - diff --git a/drivers/usb/serial/Config.in b/drivers/usb/serial/Config.in deleted file mode 100644 index 7a486f72eaa1..000000000000 --- a/drivers/usb/serial/Config.in +++ /dev/null @@ -1,44 +0,0 @@ -# -# USB Serial device configuration -# -mainmenu_option next_comment -comment 'USB Serial Converter support' - -dep_tristate 'USB Serial Converter support' CONFIG_USB_SERIAL $CONFIG_USB -if [ "$CONFIG_USB_SERIAL" = "y" ]; then - dep_mbool ' USB Serial Converter verbose debug' CONFIG_USB_SERIAL_DEBUG $CONFIG_USB_SERIAL - dep_mbool ' USB Serial Console device support (EXPERIMENTAL)' CONFIG_USB_SERIAL_CONSOLE $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL -fi -dep_mbool ' USB Generic Serial Driver' CONFIG_USB_SERIAL_GENERIC $CONFIG_USB_SERIAL -dep_tristate ' USB Belkin and Peracom Single Port Serial Driver' CONFIG_USB_SERIAL_BELKIN $CONFIG_USB_SERIAL -dep_tristate ' USB ConnectTech WhiteHEAT Serial Driver' CONFIG_USB_SERIAL_WHITEHEAT $CONFIG_USB_SERIAL -dep_tristate ' USB Digi International AccelePort USB Serial Driver' CONFIG_USB_SERIAL_DIGI_ACCELEPORT $CONFIG_USB_SERIAL -dep_tristate ' USB Empeg empeg-car Mark I/II Driver' CONFIG_USB_SERIAL_EMPEG $CONFIG_USB_SERIAL -dep_tristate ' USB FTDI Single Port Serial Driver (EXPERIMENTAL)' CONFIG_USB_SERIAL_FTDI_SIO $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL -dep_tristate ' USB Handspring Visor / Palm m50x / Sony Clie Driver' CONFIG_USB_SERIAL_VISOR $CONFIG_USB_SERIAL -dep_tristate ' USB Compaq iPAQ / HP Jornada / Casio EM500 Driver' CONFIG_USB_SERIAL_IPAQ $CONFIG_USB_SERIAL -dep_tristate ' USB IR Dongle Serial Driver (EXPERIMENTAL)' CONFIG_USB_SERIAL_IR $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL -dep_tristate ' USB Inside Out Edgeport Serial Driver' CONFIG_USB_SERIAL_EDGEPORT $CONFIG_USB_SERIAL -dep_tristate ' USB Inside Out Edgeport Serial Driver (TI devices)' CONFIG_USB_SERIAL_EDGEPORT_TI $CONFIG_USB_SERIAL -dep_tristate ' USB Keyspan PDA Single Port Serial Driver' CONFIG_USB_SERIAL_KEYSPAN_PDA $CONFIG_USB_SERIAL -dep_tristate ' USB Keyspan USA-xxx Serial Driver' CONFIG_USB_SERIAL_KEYSPAN $CONFIG_USB_SERIAL - dep_mbool ' USB Keyspan USA-28 Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA28 $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-28X Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA28X $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-28XA Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA28XA $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-28XB Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA28XB $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-19 Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA19 $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-18X Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA18X $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-19W Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA19W $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-19QW Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA19QW $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-19QI Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA19QI $CONFIG_USB_SERIAL_KEYSPAN - dep_mbool ' USB Keyspan USA-49W Firmware' CONFIG_USB_SERIAL_KEYSPAN_USA49W $CONFIG_USB_SERIAL_KEYSPAN -dep_tristate ' USB KL5KUSB105 (Palmconnect) Driver (EXPERIMENTAL)' CONFIG_USB_SERIAL_KLSI $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL -dep_tristate ' USB MCT Single Port Serial Driver' CONFIG_USB_SERIAL_MCT_U232 $CONFIG_USB_SERIAL -dep_tristate ' USB Prolific 2303 Single Port Serial Driver' CONFIG_USB_SERIAL_PL2303 $CONFIG_USB_SERIAL -dep_tristate ' USB Safe Serial (Encapsulated) Driver (EXPERIMENTAL)' CONFIG_USB_SERIAL_SAFE $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL - dep_mbool ' USB Secure Encapsulated Driver - Padded' CONFIG_USB_SERIAL_SAFE_PADDED $CONFIG_USB_SERIAL_SAFE -dep_tristate ' USB REINER SCT cyberJack pinpad/e-com chipcard reader (EXPERIMENTAL)' CONFIG_USB_SERIAL_CYBERJACK $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL -dep_tristate ' USB Xircom / Entregra Single Port Serial Driver' CONFIG_USB_SERIAL_XIRCOM $CONFIG_USB_SERIAL -dep_tristate ' USB ZyXEL omni.net LCD Plus Driver (EXPERIMENTAL)' CONFIG_USB_SERIAL_OMNINET $CONFIG_USB_SERIAL $CONFIG_EXPERIMENTAL - -endmenu diff --git a/drivers/usb/storage/Config.help b/drivers/usb/storage/Config.help deleted file mode 100644 index 81131aef0bce..000000000000 --- a/drivers/usb/storage/Config.help +++ /dev/null @@ -1,57 +0,0 @@ -CONFIG_USB_STORAGE - Say Y here if you want to connect USB mass storage devices to your - computer's USB port. This is the driver you need for USB floppy drives, - USB hard disks, USB tape drives and USB CD-ROMs, along with - similar devices. This driver may also be used for some cameras and - card readers. - - 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 usb-storage.o. If you want to compile it - as a module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_USB_STORAGE_DEBUG - Say Y here in order to have the USB Mass Storage code generate - verbose debugging messages. - -CONFIG_USB_STORAGE_ISD200 - Say Y here if you want to use USB Mass Store devices based - on the In-Systems Design ISD-200 USB/ATA bridge. - - Some of the products that use this chip are: - - - Archos Jukebox 6000 - - ISD SmartCable for Storage - - Taiwan Skymaster CD530U/DEL-0241 IDE bridge - - Sony CRX10U CD-R/RW drive - - CyQ've CQ8060A CDRW drive - - Planex eXtreme Drive RX-25HU USB-IDE cable (not model RX-25U) - -CONFIG_USB_STORAGE_FREECOM - Support for the Freecom USB to IDE/ATAPI adaptor. - Freecom has a web page at <http://www.freecom.de/>. - -CONFIG_USB_STORAGE_DATAFAB - Support for certain Datafab CompactFlash readers. - Datafab has a web page at <http://www.datafabusa.com/>. - -CONFIG_USB_STORAGE_DPCM - Say Y here to support the Microtech ZiO! CompactFlash reader. - There is a web page at <http://www.microtechint.com/zio/index.html>. - -CONFIG_USB_STORAGE_SDDR09 - Say Y here to include additional code to support the Sandisk SDDR-09 - SmartMedia reader in the USB Mass Storage driver. - Also works for the Microtech Zio! SmartMedia reader. - -CONFIG_USB_STORAGE_SDDR55 - Say Y here to include additional code to support the Sandisk SDDR-55 - SmartMedia reader in the USB Mass Storage driver. - -CONFIG_USB_STORAGE_HP8200e - Say Y here to include additional code to support Hewlett-Packard - 8200e/8210e/8230e CD-Writer Plus drives. - -CONFIG_USB_STORAGE_JUMPSHOT - Say Y here to include additional code to support the Lexar Jumpshot - USB CompactFlash reader. diff --git a/drivers/usb/storage/Config.in b/drivers/usb/storage/Config.in deleted file mode 100644 index 6b67604160ca..000000000000 --- a/drivers/usb/storage/Config.in +++ /dev/null @@ -1,16 +0,0 @@ -# -# USB Storage driver configuration -# -if [ "$CONFIG_SCSI" = "n" ]; then - comment ' SCSI support is needed for USB Storage' -fi -dep_tristate ' USB Mass Storage support' CONFIG_USB_STORAGE $CONFIG_USB $CONFIG_SCSI - dep_mbool ' USB Mass Storage verbose debug' CONFIG_USB_STORAGE_DEBUG $CONFIG_USB_STORAGE - dep_mbool ' Datafab Compact Flash Reader support (EXPERIMENTAL)' CONFIG_USB_STORAGE_DATAFAB $CONFIG_USB_STORAGE $CONFIG_EXPERIMENTAL - dep_mbool ' Freecom USB/ATAPI Bridge support' CONFIG_USB_STORAGE_FREECOM $CONFIG_USB_STORAGE - dep_mbool ' ISD-200 USB/ATA Bridge support' CONFIG_USB_STORAGE_ISD200 $CONFIG_USB_STORAGE - dep_mbool ' Microtech CompactFlash/SmartMedia support' CONFIG_USB_STORAGE_DPCM $CONFIG_USB_STORAGE - dep_mbool ' HP CD-Writer 82xx support (EXPERIMENTAL)' CONFIG_USB_STORAGE_HP8200e $CONFIG_USB_STORAGE $CONFIG_EXPERIMENTAL - dep_mbool ' SanDisk SDDR-09 (and other SmartMedia) support (EXPERIMENTAL)' CONFIG_USB_STORAGE_SDDR09 $CONFIG_USB_STORAGE $CONFIG_EXPERIMENTAL - dep_mbool ' SanDisk SDDR-55 SmartMedia support (EXPERIMENTAL)' CONFIG_USB_STORAGE_SDDR55 $CONFIG_USB_STORAGE $CONFIG_EXPERIMENTAL - dep_mbool ' Lexar Jumpshot Compact Flash Reader (EXPERIMENTAL)' CONFIG_USB_STORAGE_JUMPSHOT $CONFIG_USB_STORAGE $CONFIG_EXPERIMENTAL diff --git a/drivers/video/Config.help b/drivers/video/Config.help deleted file mode 100644 index 7a079fff6d58..000000000000 --- a/drivers/video/Config.help +++ /dev/null @@ -1,724 +0,0 @@ -CONFIG_FB_SGIVW - SGI Visual Workstation support for framebuffer graphics. - -CONFIG_VIDEO_SELECT - This enables support for text mode selection on kernel startup. If - you want to take advantage of some high-resolution text mode your - card's BIOS offers, but the traditional Linux utilities like - SVGATextMode don't, you can say Y here and set the mode using the - "vga=" option from your boot loader (lilo or loadlin) or set - "vga=ask" which brings up a video mode menu on kernel startup. (Try - "man bootparam" or see the documentation of your boot loader about - how to pass options to the kernel.) - - Read the file <file:Documentation/svga.txt> for more information - about the Video mode selection support. If unsure, say N. - -CONFIG_FB - The frame buffer device provides an abstraction for the graphics - hardware. It represents the frame buffer of some video hardware and - allows application software to access the graphics hardware through - a well-defined interface, so the software doesn't need to know - anything about the low-level (hardware register) stuff. - - Frame buffer devices work identically across the different - architectures supported by Linux and make the implementation of - application programs easier and more portable; at this point, an X - server exists which uses the frame buffer device exclusively. - On several non-X86 architectures, the frame buffer device is the - only way to use the graphics hardware. - - The device is accessed through special device nodes, usually located - in the /dev directory, i.e. /dev/fb*. - - You need an utility program called fbset to make full use of frame - buffer devices. Please read <file:Documentation/fb/framebuffer.txt> - and the Framebuffer-HOWTO at - <http://www.tahallah.demon.co.uk/programming/prog.html> for more - information. - - Say Y here and to the driver for your graphics board below if you - are compiling a kernel for a non-x86 architecture. - - If you are compiling for the x86 architecture, you can say Y if you - want to play with it, but it is not essential. Please note that - running graphical applications that directly touch the hardware - (e.g. an accelerated X server) and that are not frame buffer - device-aware may cause unexpected results. If unsure, say N. - -CONFIG_FB_ACORN - This is the frame buffer device driver for the Acorn VIDC graphics - hardware found in Acorn RISC PCs and other ARM-based machines. If - unsure, say N. - -CONFIG_FB_PM2 - This is the frame buffer device driver for the Permedia2 AGP frame - buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a - product page at - <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>. - -CONFIG_FB_PM2_FIFO_DISCONNECT - Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2). - -CONFIG_FB_PM2_PCI - Say Y to enable support for Permedia2 AGP frame buffer card from - 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus. - -CONFIG_FB_PM2_CVPPC - Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC - framebuffer cards. Phase 5 is no longer with us, alas. - -CONFIG_FB_AMIGA - This is the frame buffer device driver for the builtin graphics - chipset found in Amigas. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called amifb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_PM3 - This is the frame buffer device driver for the 3DLabs Permedia3 - chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & - similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 - and maybe other boards. - -CONFIG_FB_AMIGA_OCS - This enables support for the original Agnus and Denise video chips, - found in the Amiga 1000 and most A500's and A2000's. If you intend - to run Linux on any of these systems, say Y; otherwise say N. - -CONFIG_FB_AMIGA_ECS - This enables support for the Enhanced Chip Set, found in later - A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If - you intend to run Linux on any of these systems, say Y; otherwise - say N. - -CONFIG_FB_AMIGA_AGA - This enables support for the Advanced Graphics Architecture (also - known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T - and CD32. If you intend to run Linux on any of these systems, say Y; - otherwise say N. - -CONFIG_FB_CYBER - This enables support for the Cybervision 64 graphics card from - Phase5. Please note that its use is not all that intuitive (i.e. if - you have any questions, be sure to ask!). Say N unless you have a - Cybervision 64 or plan to get one before you next recompile the - kernel. Please note that this driver DOES NOT support the - Cybervision 64 3D card, as they use incompatible video chips. - -CONFIG_FB_CYBER2000 - This enables support for the Integraphics CyberPro 20x0 and 5000 - VGA chips used in the Rebel.com Netwinder and other machines. - Say Y if you have a NetWinder or a graphics card containing this - device, otherwise say N. - -CONFIG_FB_VIRGE - This enables support for the Cybervision 64/3D graphics card from - Phase5. Please note that its use is not all that intuitive (i.e. if - you have any questions, be sure to ask!). Say N unless you have a - Cybervision 64/3D or plan to get one before you next recompile the - kernel. Please note that this driver DOES NOT support the older - Cybervision 64 card, as they use incompatible video chips. - -CONFIG_FB_RETINAZ3 - This enables support for the Retina Z3 graphics card. Say N unless - you have a Retina Z3 or plan to get one before you next recompile - the kernel. - -CONFIG_FB_CLGEN - This enables support for Cirrus Logic GD542x/543x based boards on - Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. - - If you have a PCI-based system, this enables support for these - chips: GD-543x, GD-544x, GD-5480. - - Please read the file <file:Documentation/fb/clgenfb.txt>. - - Say N unless you have such a graphics board or plan to get one - before you next recompile the kernel. - -CONFIG_FB_ATARI - This is the frame buffer device driver for the builtin graphics - chipset found in Ataris. - -CONFIG_FB_FM2 - This is the frame buffer device driver for the Amiga FrameMaster - card from BSC (exhibited 1992 but not shipped as a CBM product). - -CONFIG_FB_OF - Say Y if you want support with Open Firmware for your graphics - board. - -CONFIG_FB_S3TRIO - If you have a S3 Trio say Y. Say N for S3 Virge. - -CONFIG_FB_3DFX - This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 - chips. Say Y if you have such a graphics board. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called tdfxfb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_RIVA - This driver supports graphics boards with the nVidia Riva/Geforce - chips. - Say Y if you have such a graphics board. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called rivafb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_ATY - This driver supports graphics boards with the ATI Mach64 chips. - Say Y if you have such a graphics board. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called atyfb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_ATY128 - This driver supports graphics boards with the ATI Rage128 chips. - Say Y if you have such a graphics board and read - <file:Documentation/fb/aty128fb.txt>. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called aty128fb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_MAXINE - Say Y here to directly support the on-board framebuffer in the - Maxine (5000/20, /25, /33) version of the DECstation. There is a - page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>. - -CONFIG_FB_PMAG_BA - Say Y here to directly support the on-board PMAG-BA framebuffer in - the 5000/1xx versions of the DECstation. There is a page dedicated - to Linux on DECstations at <http://decstation.unix-ag.org/>. - -CONFIG_FB_PMAGB_B - Say Y here to directly support the on-board PMAGB-B framebuffer in - the 5000/1xx versions of the DECstation. There is a page dedicated - to Linux on DECstations at <http://decstation.unix-ag.org/>. - -CONFIG_FB_NEOMAGIC - This driver supports notebooks with NeoMagic PCI chips. - Say Y if you have such a graphics card. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called neofb.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. - -CONFIG_FB_CONTROL - This driver supports a frame buffer for the graphics adapter in the - Power Macintosh 7300 and others. - -CONFIG_FB_PLATINUM - This driver supports a frame buffer for the "platinum" graphics - adapter in some Power Macintoshes. - -CONFIG_FB_VALKYRIE - This driver supports a frame buffer for the "valkyrie" graphics - adapter in some Power Macintoshes. - -CONFIG_FB_CT65550 - This is the frame buffer device driver for the Chips & Technologies - 65550 graphics chip in PowerBooks. - -CONFIG_FB_TGA - This is the frame buffer device driver for generic TGA graphic - cards. Say Y if you have one of those. - -CONFIG_FB_VESA - This is the frame buffer device driver for generic VESA 2.0 - compliant graphic cards. The older VESA 1.2 cards are not supported. - You will get a boot time penguin logo at no additional cost. Please - read <file:Documentation/fb/vesafb.txt>. If unsure, say Y. - -CONFIG_FBCON_VGA_PLANES - This low level frame buffer console driver enable the kernel to use - the 16-color planar modes of the old VGA cards where the bits of - each pixel are separated into 4 planes. - - Only answer Y here if you have a (very old) VGA card that isn't VESA - 2 compatible. - -CONFIG_FB_VGA16 - This is the frame buffer device driver for VGA 16 color graphic - cards. Say Y if you have such a card. - - 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 - <file:Documentation/modules.txt>. The module will be called - vga16fb.o. - -CONFIG_FB_STI - STI refers to the HP "Standard Text Interface" which is a set of - BIOS routines contained in a ROM chip in HP PA-RISC based machines. - Enabling this option will implement the linux framebuffer device and - an fbcon color text console using calls to the STI BIOS routines. - The HP framebuffer device is usually planar, uses a strange memory - layout, and changing the plane mask to create colored pixels - requires a call to the STI routines, so do not expect /dev/fb to - actually be useful. However, it is the best we have as far as - graphics on the HP chipsets due to lack of hardware level - documentation for the various on-board HP chipsets used in these - systems. It is sufficient for basic text console functions, - including fonts. - - You should probably enable this option, unless you are having - trouble getting video when booting the kernel (make sure it isn't - just that you are running the console on the serial port, though). - Really old HP boxes may not have STI, and must use the PDC BIOS - console or the IODC BIOS. - -CONFIG_FBCON_FONTS - Say Y here if you would like to use fonts other than the default - your frame buffer console usually use. - - 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 foreign fonts. - - If unsure, say N (the default choices are safe). - -CONFIG_FONT_8x16 - This is the "high resolution" font for the VGA frame buffer (the one - provided by the VGA text console 80x25 mode. - - If unsure, say Y. - -CONFIG_FBCON_FONTWIDTH8_ONLY - Answer Y here will make the kernel provide only the 8x8 fonts (these - are the less readable). - - If unsure, say N. - -CONFIG_FONT_SUN8x16 - This is the high resolution console font for Sun machines. Say Y. - -CONFIG_FONT_SUN12x22 - This is the high resolution console font for Sun machines with very - big letters (like the letters used in the SPARC PROM). If the - standard font is unreadable for you, say Y, otherwise say N. - -CONFIG_FONT_8x8 - This is the "high resolution" font for the VGA frame buffer (the one - provided by the text console 80x50 (and higher) modes). - - Note that this is a poor quality font. The VGA 8x16 font is quite a - lot more readable. - - Given the resolution provided by the frame buffer device, answer N - here is safe. - -CONFIG_FONT_6x11 - Small console font with Macintosh-style high-half glyphs. Some Mac - framebuffer drivers don't support this one at all. - -CONFIG_FONT_PEARL_8x8 - Small console font with PC-style control-character and high-half - glyphs. - -CONFIG_FONT_ACORN_8x8 - Small console font with PC-style control characters and high-half - glyphs. - -CONFIG_FB_HGA - Say Y here if you have a Hercules mono graphics card. - - This driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). - The module will be called hgafb.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - - As this card technology is 15 years old, most people will answer N - here. - -CONFIG_FB_E1355 - Build in support for the SED1355 Epson Research Embedded RAMDAC - LCD/CRT Controller (since redesignated as the S1D13505) as a - framebuffer. Product specs at - <http://www.erd.epson.com/vdc/html/products.htm>. - -CONFIG_E1355_REG_BASE - Epson SED1355/S1D13505 LCD/CRT controller register base address. - See the manuals at - <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for - discussion. - -CONFIG_E1355_FB_BASE - Epson SED1355/S1D13505 LCD/CRT controller memory base address. See - the manuals at - <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for - discussion. - -CONFIG_FB_PVR2 - Say Y here if you have a PowerVR 2 card in your box. If you plan to - run linux on your Dreamcast, you will have to say Y here. - This driver may or may not work on other PowerVR 2 cards, but is - totally untested. Use at your own risk. If unsure, say N. - - This driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). - The module will be called pvr2fb.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - - You can pass several parameters to the driver at boot time or at - module load time. The parameters look like "video=pvr2:XXX", where - the meaning of XXX can be found at the end of the main source file - (<file:drivers/video/pvr2fb.c>). Please see the file - <file:Documentation/fb/pvr2fb.txt>. - -CONFIG_FB_PVR2_DEBUG - Say Y here if you wish for the pvr2fb driver to print out debugging - messages. Most people will want to say N here. If unsure, you will - also want to say N. - -CONFIG_FB_MATROX - Say Y here if you have a Matrox Millennium, Matrox Millennium II, - Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox - Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, - Matrox G400, G450 or G550 card in your box. - - This driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). - The module will be called matroxfb.o. If you want to compile it as - a module, say M here and read <file:Documentation/modules.txt>. - - You can pass several parameters to the driver at boot time or at - module load time. The parameters look like "video=matrox:XXX", and - are described in <file:Documentation/fb/matroxfb.txt>. - -CONFIG_FB_MATROX_MILLENIUM - Say Y here if you have a Matrox Millennium or Matrox Millennium II - video card. If you select "Advanced lowlevel driver options" below, - you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp - packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can - also use font widths different from 8. - -CONFIG_FB_MATROX_MYSTIQUE - Say Y here if you have a Matrox Mystique or Matrox Mystique 220 - video card. If you select "Advanced lowlevel driver options" below, - you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp - packed pixel and 32 bpp packed pixel. You can also use font widths - different from 8. - -CONFIG_FB_MATROX_G450 - Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based - video card. If you select "Advanced lowlevel driver options", you - should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed - pixel and 32 bpp packed pixel. You can also use font widths - different from 8. - - If you need support for G400 secondary head, you must first say Y to - "I2C support" and "I2C bit-banging support" in the character devices - section, and then to "Matrox I2C support" and "G400 second head - support" here in the framebuffer section. G450/G550 secondary head - and digital output are supported without additional modules. - - The driver starts in monitor mode. You must use the matroxset tool - (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to - swap primary and secondary head outputs, or to change output mode. - Secondary head driver always start in 640x480 resolution and you - must use fbset to change it. - - Do not forget that second head supports only 16 and 32 bpp - packed pixels, so it is a good idea to compile them into the kernel - too. You can use only some font widths, as the driver uses generic - painting procedures (the secondary head does not use acceleration - engine). - - G450/G550 hardware can display TV picture only from secondary CRTC, - and it performs no scaling, so picture must have 525 or 625 lines. - -CONFIG_FB_MATROX_G100A - Say Y here if you have a Matrox G100, G200 or G400 based - video card. If you select "Advanced lowlevel driver options", you - should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed - pixel and 32 bpp packed pixel. You can also use font widths - different from 8. - - If you need support for G400 secondary head, you must first say Y to - "I2C support" and "I2C bit-banging support" in the character devices - section, and then to "Matrox I2C support" and "G400 second head - support" here in the framebuffer section. - -CONFIG_FB_MATROX_I2C - This drivers creates I2C buses which are needed for accessing the - DDC (I2C) bus present on all Matroxes, an I2C bus which - interconnects Matrox optional devices, like MGA-TVO on G200 and - G400, and the secondary head DDC bus, present on G400 only. - - You can say Y or M here if you want to experiment with monitor - detection code. You must say Y or M here if you want to use either - second head of G400 or MGA-TVO on G200 or G400. - - If you compile it as module, it will create a module named - i2c-matroxfb.o. - -CONFIG_FB_MATROX_MAVEN - WARNING !!! This support does not work with G450 !!! - - Say Y or M here if you want to use a secondary head (meaning two - monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary - head is not compatible with accelerated XFree 3.3.x SVGA servers - - secondary head output is blanked while you are in X. With XFree - 3.9.17 preview you can use both heads if you use SVGA over fbdev or - the fbdev driver on first head and the fbdev driver on second head. - - If you compile it as module, two modules are created, - matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for - both G200 and G400, matroxfb_crtc2 is needed only by G400. You must - also load i2c-matroxfb to get it to run. - - The driver starts in monitor mode and you must use the matroxset - tool (available at - <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to - PAL or NTSC or to swap primary and secondary head outputs. - Secondary head driver also always start in 640x480 resolution, you - must use fbset to change it. - - Also do not forget that second head supports only 16 and 32 bpp - packed pixels, so it is a good idea to compile them into the kernel - too. You can use only some font widths, as the driver uses generic - painting procedures (the secondary head does not use acceleration - engine). - -CONFIG_FB_MATROX_MULTIHEAD - Say Y here if you have more than one (supported) Matrox device in - your computer and you want to use all of them for different monitors - ("multihead"). If you have only one device, you should say N because - the driver compiled with Y is larger and a bit slower, especially on - ia32 (ix86). - - If you said M to "Matrox unified accelerated driver" and N here, you - will still be able to use several Matrox devices simultaneously: - insert several instances of the module matroxfb.o into the kernel - with insmod, supplying the parameter "dev=N" where N is 0, 1, etc. - for the different Matrox devices. This method is slightly faster but - uses 40 KB of kernel memory per Matrox card. - - There is no need for enabling 'Matrox multihead support' if you have - only one Matrox card in the box. - -CONFIG_FB_VOODOO1 - Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or - Voodoo2 (cvg) based graphics card. - - This driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). - The module will be called sstfb.o. If you want to compile it as - a module, say M here and read Documentation/modules.txt. - - WARNING: Do not use any application that uses the 3D engine - (namely glide) while using this driver. - Please read the file Documentation/fb/README-sstfb.txt for supported - options and other important info support. - -CONFIG_FB_TRIDENT - This driver is supposed to support graphics boards with the - Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops - but also on some motherboards. For more information, read - <file:Documentation/fb/tridentfb.txt> - - Say Y if you have such a graphics board. - - The driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called rivafb.o. If you want to compile it as a - module, say M here and read <file:Documentation/modules.txt>. - -CONFIG_FB_SBUS - Say Y if you want support for SBUS or UPA based frame buffer device. - -CONFIG_FB_CREATOR - This is the frame buffer device driver for the Creator and Creator3D - graphics boards. - -CONFIG_FB_CGSIX - This is the frame buffer device driver for the CGsix (GX, TurboGX) - frame buffer. - -CONFIG_FB_BWTWO - This is the frame buffer device driver for the BWtwo frame buffer. - -CONFIG_FB_CGTHREE - This is the frame buffer device driver for the CGthree frame buffer. - -CONFIG_FB_CGFOURTEEN - This is the frame buffer device driver for the CGfourteen frame - buffer on Desktop SPARCsystems with the SX graphics option. - -CONFIG_FB_P9100 - This is the frame buffer device driver for the P9100 card - supported on Sparcbook 3 machines. - -CONFIG_FB_LEO - This is the frame buffer device driver for the SBUS-based Sun ZX - (leo) frame buffer cards. - -CONFIG_FB_IGA - This is the framebuffer device for the INTERGRAPHICS 1680 and - successor frame buffer cards. - -CONFIG_FB_TCX - This is the frame buffer device driver for the TCX 24/8bit frame - buffer. - -CONFIG_FB_HIT - This is the frame buffer device driver for the Hitachi HD64461 LCD - frame buffer card. - -CONFIG_FB_SIS - This is the frame buffer device driver for the SiS 630 and 640 Super - Socket 7 UMA cards. Specs available at <http://www.sis.com.tw/>. - -CONFIG_FB_SIS_300 - This is the frame buffer device driver for the SiS 630 and related - Super Socket 7 UMA cards. Specs available at - <http://www.sis.com.tw/>. - -CONFIG_FB_SIS_315 - This is the frame buffer device driver for the SiS 315 graphics - card. Specs available at <http://www.sis.com.tw/>. - -CONFIG_FB_IMSTT - The IMS Twin Turbo is a PCI-based frame buffer card bundled with - many Macintosh and compatible computers. - -CONFIG_FB_TX3912 - The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core - see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>. - - Say Y here to enable kernel support for the on-board framebuffer. - -CONFIG_FB_VIRTUAL - This is a `virtual' frame buffer device. It operates on a chunk of - unswappable kernel memory instead of on the memory of a graphics - board. This means you cannot see any output sent to this frame - buffer device, while it does consume precious memory. The main use - of this frame buffer device is testing and debugging the frame - buffer subsystem. Do NOT enable it for normal systems! To protect - the innocent, it has to be enabled explicitly at boot time using the - kernel option `video=vfb:'. - - This driver is also available as a module ( = code which can be - inserted and removed from the running kernel whenever you want). The - module will be called vfb.o. If you want to compile it as a module, - say M here and read <file:Documentation/modules.txt>. - - If unsure, say N. - -CONFIG_FB_ATY_CT - Say Y here to support use of ATI's 64-bit Rage boards (or other - boards based on the Mach64 CT, VT, GT, and LT chipsets) as a - framebuffer device. The ATI product support page for these boards - is at <http://support.ati.com/products/pc/mach64/>. - -CONFIG_FB_ATY_GX - Say Y here to support use of the ATI Mach64 Graphics Expression - board (or other boards based on the Mach64 GX chipset) as a - framebuffer device. The ATI product support page for these boards - is at - <http://support.ati.com/products/pc/mach64/graphics_xpression.html>. - -CONFIG_FB_RADEON - Choose this option if you want to use an ATI Radeon graphics card as - a framebuffer device. There are both PCI and AGP versions. You - don't need to choose this to run the Radeon in plain VGA mode. - There is a product page at - <http://www.ati.com/na/pages/products/pc/radeon32/index.html>. - -CONFIG_FB_SA1100 - This is a framebuffer device for the SA-1100 LCD Controller. - See <http://www.linux-fbdev.org/> for information on framebuffer - devices. - - If you plan to use the LCD display with your SA-1100 system, say - Y here. - -CONFIG_FBCON_ADVANCED - The frame buffer console uses character drawing routines that are - tailored to the specific organization of pixels in the memory of - your graphics hardware. These are called the low level frame buffer - console drivers. Note that they are used for text console output - only; they are NOT needed for graphical applications. - - If you say N here, the needed low level drivers are automatically - enabled, depending on what frame buffer devices you selected above. - This is recommended for most users. - - If you say Y here, you have more fine-grained control over which low - level drivers are enabled. You can e.g. leave out low level drivers - for color depths you do not intend to use for text consoles. - - Low level frame buffer console drivers can be modules ( = code which - can be inserted and removed from the running kernel whenever you - want). The modules will be called fbcon-*.o. If you want to compile - (some of) them as modules, read <file:Documentation/modules.txt>. - - If unsure, say N. - -CONFIG_FBCON_MFB - This is the low level frame buffer console driver for monochrome - (2 colors) packed pixels. - -CONFIG_FBCON_CFB2 - This is the low level frame buffer console driver for 2 bits per - pixel (4 colors) packed pixels. - -CONFIG_FBCON_CFB4 - This is the low level frame buffer console driver for 4 bits per - pixel (16 colors) packed pixels. - -CONFIG_FBCON_CFB8 - This is the low level frame buffer console driver for 8 bits per - pixel (256 colors) packed pixels. - -CONFIG_FBCON_CFB16 - This is the low level frame buffer console driver for 15 or 16 bits - per pixel (32K or 64K colors, also known as `hicolor') packed - pixels. - -CONFIG_FBCON_CFB24 - This is the low level frame buffer console driver for 24 bits per - pixel (16M colors, also known as `truecolor') packed pixels. It is - NOT for `sparse' 32 bits per pixel mode. - -CONFIG_FBCON_CFB32 - This is the low level frame buffer console driver for 32 bits per - pixel (16M colors, also known as `truecolor') sparse packed pixels. - -CONFIG_FBCON_AFB - This is the low level frame buffer console driver for 1 to 8 - bitplanes (2 to 256 colors) on Amiga. - -CONFIG_FBCON_ILBM - This is the low level frame buffer console driver for 1 to 8 - interleaved bitplanes (2 to 256 colors) on Amiga. - -CONFIG_FBCON_IPLAN2P2 - This is the low level frame buffer console driver for 2 interleaved - bitplanes (4 colors) on Atari. - -CONFIG_FBCON_IPLAN2P4 - This is the low level frame buffer console driver for 4 interleaved - bitplanes (16 colors) on Atari. - -CONFIG_FBCON_IPLAN2P8 - This is the low level frame buffer console driver for 8 interleaved - bitplanes (256 colors) on Atari. - -CONFIG_FBCON_HGA - This is the low level frame buffer console driver for Hercules mono - graphics cards. - diff --git a/drivers/video/Config.in b/drivers/video/Config.in deleted file mode 100644 index 3fe4402c78fb..000000000000 --- a/drivers/video/Config.in +++ /dev/null @@ -1,457 +0,0 @@ -# -# Video configuration -# - -mainmenu_option next_comment -comment 'Frame-buffer support' - -bool 'Support for frame buffer devices (EXPERIMENTAL)' CONFIG_FB - -if [ "$CONFIG_FB" = "y" ]; then - define_bool CONFIG_DUMMY_CONSOLE y - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - if [ "$CONFIG_AMIGA" = "y" -o "$CONFIG_PCI" = "y" ]; then - tristate ' Cirrus Logic support (EXPERIMENTAL)' CONFIG_FB_CLGEN - tristate ' Permedia2 support (EXPERIMENTAL)' CONFIG_FB_PM2 - if [ "$CONFIG_FB_PM2" = "y" -o "$CONFIG_FB_PM2" = "m" ]; then - if [ "$CONFIG_PCI" = "y" ]; then - bool ' enable FIFO disconnect feature' CONFIG_FB_PM2_FIFO_DISCONNECT - bool ' generic Permedia2 PCI board support' CONFIG_FB_PM2_PCI - fi - if [ "$CONFIG_AMIGA" = "y" ]; then - bool ' Phase5 CVisionPPC/BVisionPPC support' CONFIG_FB_PM2_CVPPC - fi - fi - fi - fi - if [ "$CONFIG_ARM" = "y" ]; then - dep_bool ' Acorn VIDC support' CONFIG_FB_ACORN $CONFIG_ARCH_ACORN - dep_bool ' Anakin LCD support' CONFIG_FB_ANAKIN $CONFIG_ARCH_ANAKIN - dep_bool ' CLPS711X LCD support' CONFIG_FB_CLPS711X $CONFIG_ARCH_CLPS711X - dep_bool ' SA-1100 LCD support' CONFIG_FB_SA1100 $CONFIG_ARCH_SA1100 - if [ "$CONFIG_FB_SA1100" = "y" -a "$CONFIG_SA1100_CERF" = "y" ]; then - choice 'CerfBoard LCD Display Size' \ - "3.8_Color CONFIG_CERF_LCD_38_A \ - 3.8_Mono CONFIG_CERF_LCD_38_B \ - 5.7 CONFIG_CERF_LCD_57_A \ - 7.2 CONFIG_CERF_LCD_72_A" 5.7 - fi - if [ "$CONFIG_FB_SA1100" = "y" -a "$CONFIG_SA1100_CERF_CPLD" = "y" ]; then - bool 'Cerfboard Backlight (CerfPDA)' CONFIG_SA1100_CERF_LCD_BACKLIGHT - fi - fi - dep_tristate ' CyberPro 2000/2010/5000 support' CONFIG_FB_CYBER2000 $CONFIG_PCI - if [ "$CONFIG_APOLLO" = "y" ]; then - define_bool CONFIG_FB_APOLLO y - fi - if [ "$CONFIG_Q40" = "y" ]; then - define_bool CONFIG_FB_Q40 y - fi - if [ "$CONFIG_AMIGA" = "y" ]; then - tristate ' Amiga native chipset support' CONFIG_FB_AMIGA - if [ "$CONFIG_FB_AMIGA" != "n" ]; then - bool ' Amiga OCS chipset support' CONFIG_FB_AMIGA_OCS - bool ' Amiga ECS chipset support' CONFIG_FB_AMIGA_ECS - bool ' Amiga AGA chipset support' CONFIG_FB_AMIGA_AGA - fi - fi - if [ "$CONFIG_ZORRO" = "y" ]; then - tristate ' Amiga CyberVision support' CONFIG_FB_CYBER - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - bool ' Amiga CyberVision3D support (EXPERIMENTAL)' CONFIG_FB_VIRGE - tristate ' Amiga RetinaZ3 support (EXPERIMENTAL)' CONFIG_FB_RETINAZ3 - bool ' Amiga FrameMaster II/Rainbow II support (EXPERIMENTAL)' CONFIG_FB_FM2 - fi - fi - if [ "$CONFIG_ATARI" = "y" ]; then - bool ' Atari native chipset support' CONFIG_FB_ATARI - tristate ' ATI Mach64 display support' CONFIG_FB_ATY - if [ "$CONFIG_FB_ATY" != "n" ]; then - define_bool CONFIG_FB_ATY_GX y - fi - fi - if [ "$CONFIG_PPC" = "y" ]; then - dep_bool ' Open Firmware frame buffer device support' CONFIG_FB_OF $CONFIG_ALL_PPC - dep_bool ' Apple "control" display support' CONFIG_FB_CONTROL $CONFIG_ALL_PPC - dep_bool ' Apple "platinum" display support' CONFIG_FB_PLATINUM $CONFIG_ALL_PPC - dep_bool ' Apple "valkyrie" display support' CONFIG_FB_VALKYRIE $CONFIG_ALL_PPC - bool ' Chips 65550 display support' CONFIG_FB_CT65550 - bool ' IMS Twin Turbo display support' CONFIG_FB_IMSTT - bool ' S3 Trio display support' CONFIG_FB_S3TRIO - tristate ' VGA 16-color graphics console' CONFIG_FB_VGA16 - fi - if [ "$CONFIG_PARISC" = "y" ]; then - bool ' Generic STI frame buffer device support' CONFIG_FB_STI - fi - if [ "$CONFIG_MAC" = "y" ]; then - define_bool CONFIG_FB_MAC y - bool ' Apple "valkyrie" display support' CONFIG_FB_VALKYRIE -# bool ' Apple DAFB display support' CONFIG_FB_DAFB - fi - if [ "$CONFIG_HP300" = "y" ]; then - define_bool CONFIG_FB_HP300 y - fi - if [ "$CONFIG_ALPHA" = "y" ]; then - tristate ' TGA framebuffer support' CONFIG_FB_TGA - fi - if [ "$CONFIG_X86" = "y" ]; then - bool ' VESA VGA graphics console' CONFIG_FB_VESA - tristate ' VGA 16-color graphics console' CONFIG_FB_VGA16 - tristate ' Hercules mono graphics console (EXPERIMENTAL)' CONFIG_FB_HGA - define_bool CONFIG_VIDEO_SELECT y - fi - if [ "$CONFIG_VISWS" = "y" ]; then - tristate ' SGI Visual Workstation framebuffer support' CONFIG_FB_SGIVW - define_bool CONFIG_BUS_I2C y - fi - if [ "$CONFIG_SUN3" = "y" -o "$CONFIG_SUN3X" = "y" ]; then - bool ' Sun3 framebuffer support' CONFIG_FB_SUN3 - if [ "$CONFIG_FB_SUN3" != "n" ]; then - bool ' BWtwo support' CONFIG_FB_BWTWO - bool ' CGthree support' CONFIG_FB_CGTHREE - bool ' CGsix (GX,TurboGX) support' CONFIG_FB_CGSIX - fi - fi - if [ "$CONFIG_SH_DREAMCAST" = "y" ]; then - tristate ' NEC PowerVR 2 display support' CONFIG_FB_PVR2 - dep_bool ' Debug pvr2fb' CONFIG_FB_PVR2_DEBUG $CONFIG_FB_PVR2 - fi - if [ "$CONFIG_SUPERH" = "y" ]; then - bool ' Epson 1355 framebuffer support' CONFIG_FB_E1355 - if [ "$CONFIG_FB_E1355" = "y" ]; then - hex ' Register Base Address' CONFIG_E1355_REG_BASE a8000000 - hex ' Framebuffer Base Address' CONFIG_E1355_FB_BASE a8200000 - fi - fi - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - if [ "$CONFIG_PCI" != "n" ]; then - tristate ' nVidia Riva support (EXPERIMENTAL)' CONFIG_FB_RIVA - tristate ' Matrox acceleration (EXPERIMENTAL)' CONFIG_FB_MATROX - if [ "$CONFIG_FB_MATROX" != "n" ]; then - bool ' Millennium I/II support' CONFIG_FB_MATROX_MILLENIUM - bool ' Mystique support' CONFIG_FB_MATROX_MYSTIQUE - bool ' G100/G200/G400/G450/G550 support' CONFIG_FB_MATROX_G450 - if [ "$CONFIG_FB_MATROX_G450" = "n" ]; then - bool ' G100/G200/G400 support' CONFIG_FB_MATROX_G100A - fi - if [ "$CONFIG_FB_MATROX_G450" = "y" -o "$CONFIG_FB_MATROX_G100A" = "y" ]; then - define_bool CONFIG_FB_MATROX_G100 y - fi - if [ "$CONFIG_I2C" != "n" ]; then - dep_tristate ' Matrox I2C support' CONFIG_FB_MATROX_I2C $CONFIG_FB_MATROX $CONFIG_I2C_ALGOBIT - if [ "$CONFIG_FB_MATROX_G100" = "y" ]; then - dep_tristate ' G400 second head support' CONFIG_FB_MATROX_MAVEN $CONFIG_FB_MATROX_I2C - fi - fi - bool ' Multihead support' CONFIG_FB_MATROX_MULTIHEAD - fi - tristate ' ATI Mach64 display support (EXPERIMENTAL)' CONFIG_FB_ATY - if [ "$CONFIG_FB_ATY" != "n" ]; then - bool ' Mach64 GX support (EXPERIMENTAL)' CONFIG_FB_ATY_GX - bool ' Mach64 CT/VT/GT/LT (incl. 3D RAGE) support' CONFIG_FB_ATY_CT - fi - tristate ' ATI Radeon display support (EXPERIMENTAL)' CONFIG_FB_RADEON - tristate ' ATI Rage128 display support (EXPERIMENTAL)' CONFIG_FB_ATY128 - tristate ' SIS acceleration (EXPERIMENTAL)' CONFIG_FB_SIS - if [ "$CONFIG_FB_SIS" != "n" ]; then - bool ' SIS 630/540/730 support' CONFIG_FB_SIS_300 - bool ' SIS 315H/315 support' CONFIG_FB_SIS_315 - fi - tristate ' NeoMagic display support (EXPERIMENTAL)' CONFIG_FB_NEOMAGIC - tristate ' 3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)' CONFIG_FB_3DFX - tristate ' 3Dfx Voodoo Graphics (sst1) support (EXPERIMENTAL)' CONFIG_FB_VOODOO1 - tristate ' Trident support (EXPERIMENTAL)' CONFIG_FB_TRIDENT - tristate ' Permedia3 support (EXPERIMENTAL)' CONFIG_FB_PM3 - fi - fi - if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - bool ' SBUS and UPA framebuffers' CONFIG_FB_SBUS - if [ "$CONFIG_FB_SBUS" != "n" ]; then - if [ "$CONFIG_SPARC64" = "y" ]; then - bool ' Creator/Creator3D support' CONFIG_FB_CREATOR - fi - bool ' CGsix (GX,TurboGX) support' CONFIG_FB_CGSIX - bool ' BWtwo support' CONFIG_FB_BWTWO - bool ' CGthree support' CONFIG_FB_CGTHREE - if [ "$CONFIG_SPARC32" = "y" ]; then - bool ' TCX (SS4/SS5 only) support' CONFIG_FB_TCX - bool ' CGfourteen (SX) support' CONFIG_FB_CGFOURTEEN - bool ' P9100 (Sparcbook 3 only) support' CONFIG_FB_P9100 - fi - bool ' Leo (ZX) support' CONFIG_FB_LEO - fi - fi - if [ "$CONFIG_SPARC32" = "y" ]; then - if [ "$CONFIG_PCI" != "n" ]; then - bool ' PCI framebuffers' CONFIG_FB_PCI - if [ "$CONFIG_FB_PCI" != "n" ]; then - bool ' IGA 168x display support' CONFIG_FB_IGA - fi - fi - fi - if [ "$CONFIG_SPARC64" = "y" ]; then - if [ "$CONFIG_PCI" != "n" ]; then - bool ' PCI framebuffers' CONFIG_FB_PCI - if [ "$CONFIG_FB_PCI" != "n" ]; then - tristate ' ATI Mach64 display support' CONFIG_FB_ATY - if [ "$CONFIG_FB_ATY" != "n" ]; then - define_bool CONFIG_FB_ATY_CT y - fi - fi - fi - fi - if [ "$CONFIG_HD64461" = "y" ]; then - tristate ' HD64461 Frame Buffer support' CONFIG_FB_HIT - fi - if [ "$CONFIG_DECSTATION" = "y" ]; then - if [ "$CONFIG_TC" = "y" ]; then - bool ' PMAG-BA TURBOchannel framebuffer support' CONFIG_FB_PMAG_BA - bool ' PMAGB-B TURBOchannel framebuffer spport' CONFIG_FB_PMAGB_B - bool ' Maxine (Personal DECstation) onboard framebuffer spport' CONFIG_FB_MAXINE - fi - fi - if [ "$CONFIG_NINO" = "y" ]; then - bool ' TMPTX3912/PR31700 frame buffer support' CONFIG_FB_TX3912 - fi - if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then - tristate ' Virtual Frame Buffer support (ONLY FOR TESTING!) (EXPERIMENTAL)' CONFIG_FB_VIRTUAL - fi - - bool ' Advanced low level driver options' CONFIG_FBCON_ADVANCED - if [ "$CONFIG_FBCON_ADVANCED" = "y" ]; then - tristate ' Monochrome support' CONFIG_FBCON_MFB - tristate ' 2 bpp packed pixels support' CONFIG_FBCON_CFB2 - tristate ' 4 bpp packed pixels support' CONFIG_FBCON_CFB4 - tristate ' 8 bpp packed pixels support' CONFIG_FBCON_CFB8 - tristate ' 16 bpp packed pixels support' CONFIG_FBCON_CFB16 - tristate ' 24 bpp packed pixels support' CONFIG_FBCON_CFB24 - tristate ' 32 bpp packed pixels support' CONFIG_FBCON_CFB32 - tristate ' Hardware acceleration support' CONFIG_FBCON_ACCEL - tristate ' Amiga bitplanes support' CONFIG_FBCON_AFB - tristate ' Amiga interleaved bitplanes support' CONFIG_FBCON_ILBM - tristate ' Atari interleaved bitplanes (2 planes) support' CONFIG_FBCON_IPLAN2P2 - tristate ' Atari interleaved bitplanes (4 planes) support' CONFIG_FBCON_IPLAN2P4 - tristate ' Atari interleaved bitplanes (8 planes) support' CONFIG_FBCON_IPLAN2P8 -# tristate ' Atari interleaved bitplanes (16 planes) support' CONFIG_FBCON_IPLAN2P16 - tristate ' VGA 16-color planar support' CONFIG_FBCON_VGA_PLANES - tristate ' HGA monochrome support (EXPERIMENTAL)' CONFIG_FBCON_HGA - else - # Guess what we need - if [ "$CONFIG_FB_ACORN" = "y" -o "$CONFIG_FB_AMIGA" = "y" -o \ - "$CONFIG_FB_ATARI" = "y" -o "$CONFIG_FB_CYBER" = "y" -o \ - "$CONFIG_FB_BWTWO" = "y" -o "$CONFIG_FB_RETINAZ3" = "y" -o \ - "$CONFIG_FB_VIRGE" = "y" -o "$CONFIG_FB_CLGEN" = "y" ]; then - define_tristate CONFIG_FBCON_MFB y - else - if [ "$CONFIG_FB_ACORN" = "m" -o "$CONFIG_FB_AMIGA" = "m" -o \ - "$CONFIG_FB_ATARI" = "m" -o "$CONFIG_FB_CYBER" = "m" -o \ - "$CONFIG_FB_BWTWO" = "m" -o "$CONFIG_FB_RETINAZ3" = "m" -o \ - "$CONFIG_FB_VIRGE" = "m" -o "$CONFIG_FB_CLGEN" = "m" ]; then - define_tristate CONFIG_FBCON_MFB m - fi - fi - if [ "$CONFIG_FB_ACORN" = "y" -o "$CONFIG_FB_SA1100" = "y" ]; then - define_tristate CONFIG_FBCON_CFB2 y - define_tristate CONFIG_FBCON_CFB4 y - else - if [ "$CONFIG_FB_ACORN" = "m" -o "$CONFIG_FB_SA1100" = "m" ]; then - define_tristate CONFIG_FBCON_CFB2 m - define_tristate CONFIG_FBCON_CFB4 m - fi - fi - if [ "$CONFIG_FB_ACORN" = "y" -o "$CONFIG_FB_ATARI" = "y" -o \ - "$CONFIG_FB_P9100" = "y" -o "$CONFIG_FB_CYBER2000" = "y" -o \ - "$CONFIG_FB_RADEON" = "y" -o "$CONFIG_FB_TGA" = "y" -o \ - "$CONFIG_FB_SIS" = "y" -o "$CONFIG_FB_PM3" = "y" -o \ - "$CONFIG_FB_TCX" = "y" -o "$CONFIG_FB_CGTHREE" = "y" -o \ - "$CONFIG_FB_CONTROL" = "y" -o "$CONFIG_FB_CLGEN" = "y" -o \ - "$CONFIG_FB_CGFOURTEEN" = "y" -o "$CONFIG_FB_TRIDENT" = "y" -o \ - "$CONFIG_FB_VIRGE" = "y" -o "$CONFIG_FB_CYBER" = "y" -o \ - "$CONFIG_FB_VALKYRIE" = "y" -o "$CONFIG_FB_PLATINUM" = "y" -o \ - "$CONFIG_FB_IGA" = "y" -o "$CONFIG_FB_MATROX" = "y" -o \ - "$CONFIG_FB_CT65550" = "y" -o "$CONFIG_FB_PM2" = "y" -o \ - "$CONFIG_FB_SA1100" = "y" ]; then - define_tristate CONFIG_FBCON_CFB8 y - else - if [ "$CONFIG_FB_ACORN" = "m" -o "$CONFIG_FB_ATARI" = "m" -o \ - "$CONFIG_FB_P9100" = "m" -o "$CONFIG_FB_CYBER2000" = "m" -o \ - "$CONFIG_FB_RADEON" = "m" -o "$CONFIG_FB_TGA" = "m" -o \ - "$CONFIG_FB_SIS" = "m" -o "$CONFIG_FB_PM3" = "m" -o \ - "$CONFIG_FB_TCX" = "m" -o "$CONFIG_FB_CGTHREE" = "m" -o \ - "$CONFIG_FB_CONTROL" = "m" -o "$CONFIG_FB_CLGEN" = "m" -o \ - "$CONFIG_FB_CGFOURTEEN" = "m" -o "$CONFIG_FB_TRIDENT" = "m" -o \ - "$CONFIG_FB_VIRGE" = "m" -o "$CONFIG_FB_CYBER" = "m" -o \ - "$CONFIG_FB_VALKYRIE" = "m" -o "$CONFIG_FB_PLATINUM" = "m" -o \ - "$CONFIG_FB_IGA" = "m" -o "$CONFIG_FB_MATROX" = "m" -o \ - "$CONFIG_FB_CT65550" = "m" -o "$CONFIG_FB_PM2" = "m" -o \ - "$CONFIG_FB_SA1100" = "m" ]; then - define_tristate CONFIG_FBCON_CFB8 m - fi - fi - if [ "$CONFIG_FB_ATARI" = "y" -o "$CONFIG_FB_PM3" = "y" -o \ - "$CONFIG_FB_SIS" = "y" -o "$CONFIG_FB_PVR2" = "y" -o \ - "$CONFIG_FB_TRIDENT" = "y" -o "$CONFIG_FB_TBOX" = "y" -o \ - "$CONFIG_FB_VOODOO1" = "y" -o "$CONFIG_FB_RADEON" = "y" -o \ - "$CONFIG_FB_CONTROL" = "y" -o "$CONFIG_FB_CLGEN" = "y" -o \ - "$CONFIG_FB_VIRGE" = "y" -o "$CONFIG_FB_CYBER" = "y" -o \ - "$CONFIG_FB_VALKYRIE" = "y" -o "$CONFIG_FB_PLATINUM" = "y" -o \ - "$CONFIG_FB_CT65550" = "y" -o "$CONFIG_FB_MATROX" = "y" -o \ - "$CONFIG_FB_PM2" = "y" -o "$CONFIG_FB_CYBER2000" = "y" -o \ - "$CONFIG_FB_SA1100" = "y" ]; then - define_tristate CONFIG_FBCON_CFB16 y - else - if [ "$CONFIG_FB_ATARI" = "m" -o "$CONFIG_FB_SIS" = "m" -o \ - "$CONFIG_FB_RADEON" = "m" -o "$CONFIG_FB_PVR2" = "m" -o \ - "$CONFIG_FB_TRIDENT" = "m" -o "$CONFIG_FB_TBOX" = "m" -o \ - "$CONFIG_FB_VOODOO1" = "m" -o "$CONFIG_FB_PM3" = "m" -o \ - "$CONFIG_FB_CONTROL" = "m" -o "$CONFIG_FB_CLGEN" = "m" -o \ - "$CONFIG_FB_VIRGE" = "m" -o "$CONFIG_FB_CYBER" = "m" -o \ - "$CONFIG_FB_VALKYRIE" = "m" -o "$CONFIG_FB_PLATINUM" = "m" -o \ - "$CONFIG_FB_CT65550" = "m" -o "$CONFIG_FB_MATROX" = "m" -o \ - "$CONFIG_FB_PM2" = "m" -o "$CONFIG_FB_CYBER2000" = "m" -o \ - "$CONFIG_FB_SA1100" = "y" ]; then - define_tristate CONFIG_FBCON_CFB16 m - fi - fi - if [ "$CONFIG_FB_ATY" = "y" -o "$CONFIG_FB_VIRTUAL" = "y" -o \ - "$CONFIG_FB_CLGEN" = "y" -o "$CONFIG_FB_VESA" = "y" -o \ - "$CONFIG_FB_MATROX" = "y" -o "$CONFIG_FB_PM2" = "y" -o \ - "$CONFIG_FB_ATY128" = "y" -o "$CONFIG_FB_RADEON" = "y" -o \ - "$CONFIG_FB_CYBER2000" = "y" -o "$CONFIG_FB_PVR2" = "y" -o \ - "$CONFIG_FB_VOODOO1" = "y" -o "$CONFIG_FB_NEOMAGIC" = "y" ]; then - define_tristate CONFIG_FBCON_CFB24 y - else - if [ "$CONFIG_FB_ATY" = "m" -o "$CONFIG_FB_VIRTUAL" = "m" -o \ - "$CONFIG_FB_CLGEN" = "m" -o "$CONFIG_FB_VESA" = "m" -o \ - "$CONFIG_FB_MATROX" = "m" -o "$CONFIG_FB_PM2" = "m" -o \ - "$CONFIG_FB_ATY128" = "m" -o "$CONFIG_FB_RADEON" = "m" -o \ - "$CONFIG_FB_CYBER2000" = "m" -o "$CONFIG_FB_PVR2" = "m" -o \ - "$CONFIG_FB_VOODOO1" = "m" -o "$CONFIG_FB_NEOMAGIC" = "y" ]; then - define_tristate CONFIG_FBCON_CFB24 m - fi - fi - if [ "$CONFIG_FB_ATARI" = "y" -o "$CONFIG_FB_RADEON" = "y" -o \ - "$CONFIG_FB_VOODOO1" = "y" -o "$CONFIG_FB_TRIDENT" = "y" -o \ - "$CONFIG_FB_CONTROL" = "y" -o "$CONFIG_FB_CLGEN" = "y" -o \ - "$CONFIG_FB_TGA" = "y" -o "$CONFIG_FB_PLATINUM" = "y" -o \ - "$CONFIG_FB_MATROX" = "y" -o "$CONFIG_FB_PM2" = "y" -o \ - "$CONFIG_FB_PVR2" = "y" -o "$CONFIG_FB_PM3" = "y" -o \ - "$CONFIG_FB_SIS" = "y" ]; then - define_tristate CONFIG_FBCON_CFB32 y - else - if [ "$CONFIG_FB_ATARI" = "m" -o "$CONFIG_FB_RADEON" = "m" -o \ - "$CONFIG_FB_VOODOO1" = "m" -o "$CONFIG_FB_TRIDENT" = "m" -o \ - "$CONFIG_FB_CONTROL" = "m" -o "$CONFIG_FB_CLGEN" = "m" -o \ - "$CONFIG_FB_TGA" = "m" -o "$CONFIG_FB_PLATINUM" = "m" -o \ - "$CONFIG_FB_MATROX" = "m" -o "$CONFIG_FB_PM2" = "m" -o \ - "$CONFIG_FB_SIS" = "m" -o "$CONFIG_FB_PVR2" = "m" -o \ - "$CONFIG_FB_PM3" = "m" ]; then - define_tristate CONFIG_FBCON_CFB32 m - fi - fi - if [ "$CONFIG_FB_NEOMAGIC" = "y" -o "$CONFIG_FB_VESA" = "y" -o \ - "$CONFIG_FB_FM2" = "y" -o "$CONFIG_FB_HIT" = "y" -o \ - "$CONFIG_FB_HP300" = "y" -o "$CONFIG_FB_Q40" = "y" -o \ - "$CONFIG_FB_ANAKIN" = "y" -o "$CONFIG_FB_G364" = "y" -o \ - "$CONFIG_FB_VIRTUAL" = "y" -o "$CONFIG_FB_CLPS711X" = "y" -o \ - "$CONFIG_FB_PMAG_BA" = "y" -o "$CONFIG_FB_PMAGB_B" = "y" -o \ - "$CONFIG_FB_3DFX" = "y" -o "$CONFIG_FB_TX3912" = "y" -o \ - "$CONFIG_FB_MAXINE" = "y" -o "$CONFIG_FB_APOLLO" = "y" -o \ - "$CONFIG_FB_ATY" = "y" -o "$CONFIG_FB_MAC" = "y" -o \ - "$CONFIG_FB_RIVA" = "y" -o "$CONFIG_FB_OF" = "y" -o \ - "$CONFIG_FB_SGIVW" = "y" ]; then - define_tristate CONFIG_FBCON_ACCEL y - else - if [ "$CONFIG_FB_NEOMAGIC" = "m" -o "$CONFIG_FB_HIT" = "m" -o \ - "$CONFIG_FB_G364" = "m" -o "$CONFIG_FB_VIRTUAL" = "m" -o \ - "$CONFIG_FB_CLPS711X" = "m" -o "$CONFIG_FB_3DFX" = "m" -o \ - "$CONFIG_FB_RIVA" = "m" -o "$CONFIG_FB_SGIVW" = "m" ]; then - define_tristate CONFIG_FBCON_ACCEL m - fi - fi - if [ "$CONFIG_FB_AMIGA" = "y" ]; then - define_tristate CONFIG_FBCON_AFB y - define_tristate CONFIG_FBCON_ILBM y - else - if [ "$CONFIG_FB_AMIGA" = "m" ]; then - define_tristate CONFIG_FBCON_AFB m - define_tristate CONFIG_FBCON_ILBM m - fi - fi - if [ "$CONFIG_FB_ATARI" = "y" ]; then - define_tristate CONFIG_FBCON_IPLAN2P2 y - define_tristate CONFIG_FBCON_IPLAN2P4 y - define_tristate CONFIG_FBCON_IPLAN2P8 y - else - if [ "$CONFIG_FB_ATARI" = "m" ]; then - define_tristate CONFIG_FBCON_IPLAN2P2 m - define_tristate CONFIG_FBCON_IPLAN2P4 m - define_tristate CONFIG_FBCON_IPLAN2P8 m - fi - fi - if [ "$CONFIG_FB_VGA16" = "y" ]; then - define_tristate CONFIG_FBCON_VGA_PLANES y - else - if [ "$CONFIG_FB_VGA16" = "m" ]; then - define_tristate CONFIG_FBCON_VGA_PLANES m - fi - fi - if [ "$CONFIG_FB_HGA" = "y" ]; then - define_tristate CONFIG_FBCON_HGA y - else - if [ "$CONFIG_FB_HGA" = "m" ]; then - define_tristate CONFIG_FBCON_HGA m - fi - fi - if [ "$CONFIG_FB_STI" = "y" ]; then - define_tristate CONFIG_FBCON_STI y - fi - fi - bool ' Support only 8 pixels wide fonts' CONFIG_FBCON_FONTWIDTH8_ONLY - if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then - bool ' Sparc console 8x16 font' CONFIG_FONT_SUN8x16 - if [ "$CONFIG_FBCON_FONTWIDTH8_ONLY" = "n" ]; then - bool ' Sparc console 12x22 font (not supported by all drivers)' CONFIG_FONT_SUN12x22 - fi - bool ' Select other fonts' CONFIG_FBCON_FONTS - if [ "$CONFIG_FBCON_FONTS" = "y" ]; then - bool ' VGA 8x8 font' CONFIG_FONT_8x8 - bool ' VGA 8x16 font' CONFIG_FONT_8x16 - if [ "$CONFIG_FBCON_FONTWIDTH8_ONLY" = "n" ]; then - bool ' Mac console 6x11 font (not supported by all drivers)' CONFIG_FONT_6x11 - fi - bool ' Pearl (old m68k) console 8x8 font' CONFIG_FONT_PEARL_8x8 - bool ' Acorn console 8x8 font' CONFIG_FONT_ACORN_8x8 - fi - else - bool ' Select compiled-in fonts' CONFIG_FBCON_FONTS - if [ "$CONFIG_FBCON_FONTS" = "y" ]; then - bool ' VGA 8x8 font' CONFIG_FONT_8x8 - bool ' VGA 8x16 font' CONFIG_FONT_8x16 - bool ' Sparc console 8x16 font' CONFIG_FONT_SUN8x16 - if [ "$CONFIG_FBCON_FONTWIDTH8_ONLY" = "n" ]; then - bool ' Sparc console 12x22 font (not supported by all drivers)' CONFIG_FONT_SUN12x22 - bool ' Mac console 6x11 font (not supported by all drivers)' CONFIG_FONT_6x11 - fi - bool ' Pearl (old m68k) console 8x8 font' CONFIG_FONT_PEARL_8x8 - bool ' Acorn console 8x8 font' CONFIG_FONT_ACORN_8x8 - bool ' Mini 4x6 font' CONFIG_FONT_MINI_4x6 - else - define_bool CONFIG_FONT_8x8 y - define_bool CONFIG_FONT_8x16 y - if [ "$CONFIG_MAC" = "y" ]; then - if [ "$CONFIG_FBCON_FONTWIDTH8_ONLY" = "n" ]; then - define_bool CONFIG_FONT_6x11 y - fi - fi - if [ "$CONFIG_AMIGA" = "y" ]; then - define_bool CONFIG_FONT_PEARL_8x8 y - fi - if [ "$CONFIG_ARM" = "y" -a "$CONFIG_ARCH_ACORN" = "y" ]; then - define_bool CONFIG_FONT_ACORN_8x8 y - fi - fi - fi -fi - -endmenu diff --git a/drivers/zorro/Config.help b/drivers/zorro/Config.help deleted file mode 100644 index 2ee2a70a51da..000000000000 --- a/drivers/zorro/Config.help +++ /dev/null @@ -1,12 +0,0 @@ -CONFIG_ZORRO_NAMES - By default, the kernel contains a database of all known Zorro device - names to make the information in /proc/iomem comprehensible to the - user. This database increases the size of the kernel image by about - 15KB, but it gets freed after the system boots up, so it doesn't - take up kernel memory. 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. - diff --git a/drivers/zorro/Config.in b/drivers/zorro/Config.in deleted file mode 100644 index dc91f84b4617..000000000000 --- a/drivers/zorro/Config.in +++ /dev/null @@ -1,7 +0,0 @@ -# -# Zorro configuration -# - -if [ "$CONFIG_ZORRO" = "y" ]; then - bool 'Zorro device name database' CONFIG_ZORRO_NAMES -fi |