891 lines · 29.1 KB · Text
RawDownload
## IDE ATA ATAPI Block device driver configuration# # Select HAVE_IDE if IDE is supportedconfig HAVE_IDE	bool menuconfig IDE	tristate "ATA/ATAPI/MFM/RLL support (DEPRECATED)"	depends on HAVE_IDE	depends on BLOCK	---help---	  If you say Y here, your kernel will be able to manage ATA/(E)IDE and	  ATAPI units. The most common cases are IDE hard drives and ATAPI	  CD-ROM drives. 	  This subsystem is currently in maintenance mode with only bug fix	  changes applied. Users of ATA hardware are encouraged to migrate to	  the newer ATA subsystem ("Serial ATA (prod) and Parallel ATA	  (experimental) drivers") which is more actively maintained. 	  To compile this driver as a module, choose M here: the	  module will be called ide-core. 	  For further information, please read <file:Documentation/ide/ide.txt>. 	  If unsure, say N. if IDE comment "Please see Documentation/ide/ide.txt for help/info on IDE drives" config IDE_XFER_MODE	bool config IDE_TIMINGS	bool	select IDE_XFER_MODE config IDE_ATAPI	bool config IDE_LEGACY	bool config BLK_DEV_IDE_SATA	bool "Support for SATA (deprecated; conflicts with libata SATA driver)"	default n	---help---	  There are two drivers for Serial ATA controllers. 	  The main driver, "libata", uses the SCSI subsystem	  and supports most modern SATA controllers. In order to use it	  you may take a look at "Serial ATA (prod) and Parallel ATA	  (experimental) drivers". 	  The IDE driver (which you are currently configuring) supports	  a few first-generation SATA controllers. 	  In order to eliminate conflicts between the two subsystems,	  this config option enables the IDE driver's SATA support.	  Normally this is disabled, as it is preferred that libata	  supports SATA controllers, and this (IDE) driver supports	  PATA controllers. 	  If unsure, say N. config IDE_GD	tristate "generic ATA/ATAPI disk support"	default y	help	  Support for ATA/ATAPI disks (including ATAPI floppy drives). 	  To compile this driver as a module, choose M here.	  The module will be called ide-gd_mod. 	  If unsure, say Y. config IDE_GD_ATA	bool "ATA disk support"	depends on IDE_GD	default y	help	  This will include support for ATA hard disks. 	  If unsure, say Y. config IDE_GD_ATAPI	bool "ATAPI floppy support"	depends on IDE_GD	select IDE_ATAPI	help	  This will include support for ATAPI floppy drives	  (i.e. Iomega ZIP or MKE LS-120). 	  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>. 	  If unsure, say N. config BLK_DEV_IDECS	tristate "PCMCIA IDE support"	depends on PCMCIA	help	  Support for Compact Flash cards, outboard IDE disks, tape drives,	  and CD-ROM drives connected through a PCMCIA card. config BLK_DEV_DELKIN	tristate "Cardbus IDE support (Delkin/ASKA/Workbit)"	depends on CARDBUS && PCI	help	  Support for Delkin, ASKA, and Workbit Cardbus CompactFlash	  Adapters.  This may also work for similar SD and XD adapters. config BLK_DEV_IDECD	tristate "Include IDE/ATAPI CDROM support"	select IDE_ATAPI	---help---	  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". 	  To compile this driver as a module, choose M here: the	  module will be called ide-cd. config BLK_DEV_IDECD_VERBOSE_ERRORS	bool "Verbose error logging for IDE/ATAPI CDROM driver" if EXPERT	depends on BLK_DEV_IDECD	default y	help	  Turn this on to have the driver print out the meanings of the	  ATAPI error codes.  This will use up additional 8kB of kernel-space	  memory, though. config BLK_DEV_IDETAPE	tristate "Include IDE/ATAPI TAPE support"	select IDE_ATAPI	help	  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/ide.txt>	  files for usage information. 	  To compile this driver as a module, choose M here: the	  module will be called ide-tape. config BLK_DEV_IDEACPI	bool "IDE ACPI support"	depends on ACPI	---help---	  Implement ACPI support for generic IDE devices. On modern	  machines ACPI support is required to properly handle ACPI S3 states. config IDE_TASK_IOCTL	bool "IDE Taskfile Access"	help	  This is a direct raw access to the media.  It is a complex but	  elegant solution to test and validate the domain of the hardware and	  perform below the driver data recovery if needed.  This is the most	  basic form of media-forensics. 	  If you are unsure, say N here. config IDE_PROC_FS	bool "legacy /proc/ide/ support"	depends on IDE && PROC_FS	default y	help	  This option enables support for the various files in	  /proc/ide.  In Linux 2.6 this has been superseded by	  files in sysfs but many legacy applications rely on this. 	  If unsure say Y. comment "IDE chipset support/bugfixes" config IDE_GENERIC	tristate "generic/default IDE chipset support"	depends on ALPHA || X86 || IA64 || M32R || MIPS || ARCH_RPC || ARCH_SHARK	default ARM && (ARCH_RPC || ARCH_SHARK)	help	  This is the generic IDE driver.  This driver attaches to the	  fixed legacy ports (e.g. on PCs 0x1f0/0x170, 0x1e8/0x168 and	  so on).  Please note that if this driver is built into the	  kernel or loaded before other ATA (IDE or libata) drivers	  and the controller is located at legacy ports, this driver	  may grab those ports and thus can prevent the controller	  specific driver from attaching. 	  Also, currently, IDE generic doesn't allow IRQ sharing	  meaning that the IRQs it grabs won't be available to other	  controllers sharing those IRQs which usually makes drivers	  for those controllers fail.  Generally, it's not a good idea	  to load IDE generic driver on modern systems. 	  If unsure, say N. config BLK_DEV_PLATFORM	tristate "Platform driver for IDE interfaces"	help	  This is the platform IDE driver, used mostly for Memory Mapped	  IDE devices, like Compact Flashes running in True IDE mode. 	  If unsure, say N. config BLK_DEV_CMD640	tristate "CMD640 chipset bugfix/support"	depends on X86	select IDE_TIMINGS	---help---	  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: "cmd640.probe_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/ide.txt>. config BLK_DEV_CMD640_ENHANCED	bool "CMD640 enhanced support"	depends on BLK_DEV_CMD640	help	  This option includes support for setting/autotuning PIO modes and	  prefetch on CMD640 IDE interfaces.  For details, read	  <file:Documentation/ide/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_IDEPNP	tristate "PNP EIDE support"	depends on PNP	help	  If you have a PnP (Plug and Play) compatible EIDE card and	  would like the kernel to automatically detect and activate	  it, say Y here. config BLK_DEV_IDEDMA_SFF	bool if PCI comment "PCI IDE chipsets support" config BLK_DEV_IDEPCI	bool config IDEPCI_PCIBUS_ORDER	bool "Probe IDE PCI devices in the PCI bus order (DEPRECATED)"	depends on IDE=y && BLK_DEV_IDEPCI	default y	help	  Probe IDE PCI devices in the order in which they appear on the	  PCI bus (i.e. 00:1f.1 PCI device before 02:01.0 PCI device)	  instead of the order in which IDE PCI host drivers are loaded. 	  Please note that this method of assuring stable naming of	  IDE devices is unreliable and use other means for achieving	  it (i.e. udev). 	  If in doubt, say N. # TODO: split it on per host driver config options (or module parameters)config BLK_DEV_OFFBOARD	bool "Boot off-board chipsets first support (DEPRECATED)"	depends on BLK_DEV_IDEPCI && (BLK_DEV_AEC62XX || BLK_DEV_GENERIC || BLK_DEV_HPT366 || BLK_DEV_PDC202XX_NEW || BLK_DEV_PDC202XX_OLD || BLK_DEV_TC86C001)	help	  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. 	  Note that, if you do this, the order of the hd* devices will be	  rearranged which may require modification of fstab and other files. 	  Please also note that this method of assuring stable naming of	  IDE devices is unreliable and use other means for achieving it	  (i.e. udev). 	  If in doubt, say N. config BLK_DEV_GENERIC	tristate "Generic PCI IDE Chipset Support"	select BLK_DEV_IDEPCI        help          This option provides generic support for various PCI IDE Chipsets          which otherwise might not be supported. config BLK_DEV_OPTI621	tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)"	depends on EXPERIMENTAL	select BLK_DEV_IDEPCI	help	  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_RZ1000	tristate "RZ1000 chipset bugfix/support"	depends on X86	select BLK_DEV_IDEPCI	help	  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 BLK_DEV_IDEDMA_PCI	bool	select BLK_DEV_IDEPCI	select BLK_DEV_IDEDMA_SFF config BLK_DEV_AEC62XX	tristate "AEC62XX chipset support"	select BLK_DEV_IDEDMA_PCI	help	  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 BLK_DEV_ALI15X3	tristate "ALI M15x3 chipset support"	select IDE_TIMINGS	select BLK_DEV_IDEDMA_PCI	help	  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. 	  Please read the comments at the top of	  <file:drivers/ide/alim15x3.c>. 	  If unsure, say N. config BLK_DEV_AMD74XX	tristate "AMD and nVidia IDE support"	depends on !ARM	select IDE_TIMINGS	select BLK_DEV_IDEDMA_PCI	help	  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_ATIIXP	tristate "ATI IXP chipset IDE support"	depends on X86	select BLK_DEV_IDEDMA_PCI	help	  This driver adds explicit support for ATI IXP chipset.	  This allows the kernel to change PIO, DMA and UDMA speeds	  and to configure the chip to optimum performance. 	  Say Y here if you have an ATI IXP chipset IDE controller. config BLK_DEV_CMD64X	tristate "CMD64{3|6|8|9} chipset support"	select IDE_TIMINGS	select BLK_DEV_IDEDMA_PCI	help	  Say Y here if you have an IDE controller which uses any of these	  chipsets: CMD643, CMD646, or CMD648. config BLK_DEV_TRIFLEX	tristate "Compaq Triflex IDE support"	select BLK_DEV_IDEDMA_PCI	help	  Say Y here if you have a Compaq Triflex IDE controller, such	  as those commonly found on Compaq Pentium-Pro systems config BLK_DEV_CY82C693	tristate "CY82C693 chipset support"	depends on ALPHA	select IDE_TIMINGS	select BLK_DEV_IDEDMA_PCI	help	  This driver adds detection and support for the CY82C693 chipset	  used on Digital's PC-Alpha 164SX boards. config BLK_DEV_CS5520	tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)"	depends on EXPERIMENTAL	select BLK_DEV_IDEDMA_PCI	help	  Include support for PIO tuning and virtual DMA on the Cyrix MediaGX	  5510/5520 chipset. This will automatically be detected and	  configured if found. 	  It is safe to say Y to this question. config BLK_DEV_CS5530	tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support"	select BLK_DEV_IDEDMA_PCI	help	  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. config BLK_DEV_CS5535	tristate "AMD CS5535 chipset support"	depends on X86 && !X86_64	select BLK_DEV_IDEDMA_PCI	help	  Include support for UDMA on the NSC/AMD CS5535 companion chipset.	  This will automatically be detected and configured if found. 	  It is safe to say Y to this question. config BLK_DEV_CS5536	tristate "CS5536 chipset support"	depends on X86_32	select BLK_DEV_IDEDMA_PCI	help	  This option enables support for the AMD CS5536	  companion chip used with the Geode LX processor family. 	  If unsure, say N. config BLK_DEV_HPT366	tristate "HPT36X/37X chipset support"	select BLK_DEV_IDEDMA_PCI	help	  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. 	  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_JMICRON	tristate "JMicron JMB36x support"	select BLK_DEV_IDEDMA_PCI	help	  Basic support for the JMicron ATA controllers. For full support	  use the libata drivers. config BLK_DEV_SC1200	tristate "National SCx200 chipset support"	select BLK_DEV_IDEDMA_PCI	help	  This driver adds support for the on-board IDE controller on the	  National SCx200 series of embedded x86 "Geode" systems. config BLK_DEV_PIIX	tristate "Intel PIIX/ICH chipsets support"	select BLK_DEV_IDEDMA_PCI	help	  This driver adds explicit support for Intel PIIX and ICH chips.

Lines 1–500 of 891.