Kconfig revision 8cb1f567f4c0a2fde9cbf77c2af888a28cab3423
1# 2# IDE ATA ATAPI Block device driver configuration 3# 4# Andre Hedrick <andre@linux-ide.org> 5# 6 7menuconfig IDE 8 tristate "ATA/ATAPI/MFM/RLL support" 9 depends on BLOCK 10 depends on HAS_IOMEM 11 ---help--- 12 If you say Y here, your kernel will be able to manage low cost mass 13 storage units such as ATA/(E)IDE and ATAPI units. The most common 14 cases are IDE hard drives and ATAPI CD-ROM drives. 15 16 If your system is pure SCSI and doesn't use these interfaces, you 17 can say N here. 18 19 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard 20 for mass storage units such as hard disks. It was designed by 21 Western Digital and Compaq Computer in 1984. It was then named 22 ST506. Quite a number of disks use the IDE interface. 23 24 AT Attachment (ATA) is the superset of the IDE specifications. 25 ST506 was also called ATA-1. 26 27 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is 28 ATA-3. It provides support for larger disks (up to 8.4GB by means of 29 the LBA standard), more disks (4 instead of 2) and for other mass 30 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is 31 ATA-4 and provides faster (and more CPU friendly) transfer modes 32 than previous PIO (Programmed processor Input/Output) from previous 33 ATA/IDE standards by means of fast DMA controllers. 34 35 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and 36 CD-ROM drives, similar in many respects to the SCSI protocol. 37 38 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was 39 designed in order to prevent data corruption and disk crash by 40 detecting pre hardware failure conditions (heat, access time, and 41 the like...). Disks built since June 1995 may follow this standard. 42 The kernel itself doesn't manage this; however there are quite a 43 number of user programs such as smart that can query the status of 44 SMART parameters from disk drives. 45 46 To compile this driver as a module, choose M here: the 47 module will be called ide. 48 49 For further information, please read <file:Documentation/ide.txt>. 50 51 If unsure, say Y. 52 53if IDE 54 55config IDE_MAX_HWIFS 56 int "Max IDE interfaces" 57 depends on ALPHA || SUPERH || IA64 || EMBEDDED 58 range 1 10 59 default 4 60 help 61 This is the maximum number of IDE hardware interfaces that will 62 be supported by the driver. Make sure it is at least as high as 63 the number of IDE interfaces in your system. 64 65config BLK_DEV_IDE 66 tristate "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support" 67 ---help--- 68 If you say Y here, you will use the full-featured IDE driver to 69 control up to ten ATA/IDE interfaces, each being able to serve a 70 "master" and a "slave" device, for a total of up to twenty ATA/IDE 71 disk/cdrom/tape/floppy drives. 72 73 Useful information about large (>540 MB) IDE disks, multiple 74 interfaces, what to do if ATA/IDE devices are not automatically 75 detected, sound card ATA/IDE ports, module support, and other 76 topics, is contained in <file:Documentation/ide.txt>. For detailed 77 information about hard drives, consult the Disk-HOWTO and the 78 Multi-Disk-HOWTO, available from 79 <http://www.tldp.org/docs.html#howto>. 80 81 To fine-tune ATA/IDE drive/interface parameters for improved 82 performance, look for the hdparm package at 83 <ftp://ibiblio.org/pub/Linux/system/hardware/>. 84 85 To compile this driver as a module, choose M here and read 86 <file:Documentation/ide.txt>. The module will be called ide-mod. 87 Do not compile this driver as a module if your root file system (the 88 one containing the directory /) is located on an IDE device. 89 90 If you have one or more IDE drives, say Y or M here. If your system 91 has no IDE drives, or if memory requirements are really tight, you 92 could say N here, and select the "Old hard disk driver" below 93 instead to save about 13 KB of memory in the kernel. 94 95if BLK_DEV_IDE 96 97comment "Please see Documentation/ide.txt for help/info on IDE drives" 98 99config BLK_DEV_IDE_SATA 100 bool "Support for SATA (deprecated; conflicts with libata SATA driver)" 101 default n 102 ---help--- 103 There are two drivers for Serial ATA controllers. 104 105 The main driver, "libata", uses the SCSI subsystem 106 and supports most modern SATA controllers. In order to use it 107 you may take a look at "Serial ATA (prod) and Parallel ATA 108 (experimental) drivers". 109 110 The IDE driver (which you are currently configuring) supports 111 a few first-generation SATA controllers. 112 113 In order to eliminate conflicts between the two subsystems, 114 this config option enables the IDE driver's SATA support. 115 Normally this is disabled, as it is preferred that libata 116 supports SATA controllers, and this (IDE) driver supports 117 PATA controllers. 118 119 If unsure, say N. 120 121config BLK_DEV_HD_IDE 122 bool "Use old disk-only driver on primary interface" 123 depends on (X86 || SH_MPC1211) 124 ---help--- 125 There are two drivers for MFM/RLL/IDE disks. Most people use just 126 the new enhanced driver by itself. This option however installs the 127 old hard disk driver to control the primary IDE/disk interface in 128 the system, leaving the new enhanced IDE driver to take care of only 129 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from 130 having an IDE/ATAPI CD-ROM or tape drive connected to the primary 131 IDE interface. Choosing this option may be useful for older systems 132 which have MFM/RLL/ESDI controller+drives at the primary port 133 address (0x1f0), along with IDE drives at the secondary/3rd/4th port 134 addresses. 135 136 Normally, just say N here; you will then use the new driver for all 137 4 interfaces. 138 139config BLK_DEV_IDEDISK 140 tristate "Include IDE/ATA-2 DISK support" 141 ---help--- 142 This will include enhanced support for MFM/RLL/IDE hard disks. If 143 you have a MFM/RLL/IDE disk, and there is no special reason to use 144 the old hard disk driver instead, say Y. If you have an SCSI-only 145 system, you can say N here. 146 147 To compile this driver as a module, choose M here: the 148 module will be called ide-disk. 149 Do not compile this driver as a module if your root file system 150 (the one containing the directory /) is located on the IDE disk. 151 152 If unsure, say Y. 153 154config IDEDISK_MULTI_MODE 155 bool "Use multi-mode by default" 156 help 157 If you get this error, try to say Y here: 158 159 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } 160 hda: set_multmode: error=0x04 { DriveStatusError } 161 162 If in doubt, say N. 163 164config BLK_DEV_IDECS 165 tristate "PCMCIA IDE support" 166 depends on PCMCIA 167 help 168 Support for Compact Flash cards, outboard IDE disks, tape drives, 169 and CD-ROM drives connected through a PCMCIA card. 170 171config BLK_DEV_DELKIN 172 tristate "Cardbus IDE support (Delkin/ASKA/Workbit)" 173 depends on CARDBUS && PCI 174 help 175 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash 176 Adapters. This may also work for similar SD and XD adapters. 177 178config BLK_DEV_IDECD 179 tristate "Include IDE/ATAPI CDROM support" 180 ---help--- 181 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is 182 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the 183 SCSI protocol. Most new CD-ROM drives use ATAPI, including the 184 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI 185 double(2X) or better speed drives. 186 187 If you say Y here, the CD-ROM drive will be identified at boot time 188 along with other IDE devices, as "hdb" or "hdc", or something 189 similar (check the boot messages with dmesg). If this is your only 190 CD-ROM drive, you can say N to all other CD-ROM options, but be sure 191 to say Y or M to "ISO 9660 CD-ROM file system support". 192 193 Note that older versions of LILO (LInux LOader) cannot properly deal 194 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from 195 <http://lilo.go.dyndns.org/>. 196 197 To compile this driver as a module, choose M here: the 198 module will be called ide-cd. 199 200config BLK_DEV_IDETAPE 201 tristate "Include IDE/ATAPI TAPE support (EXPERIMENTAL)" 202 depends on EXPERIMENTAL 203 help 204 If you have an IDE tape drive using the ATAPI protocol, say Y. 205 ATAPI is a newer protocol used by IDE tape and CD-ROM drives, 206 similar to the SCSI protocol. If you have an SCSI tape drive 207 however, you can say N here. 208 209 You should also say Y if you have an OnStream DI-30 tape drive; this 210 will not work with the SCSI protocol, until there is support for the 211 SC-30 and SC-50 versions. 212 213 If you say Y here, the tape drive will be identified at boot time 214 along with other IDE devices, as "hdb" or "hdc", or something 215 similar, and will be mapped to a character device such as "ht0" 216 (check the boot messages with dmesg). Be sure to consult the 217 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files 218 for usage information. 219 220 To compile this driver as a module, choose M here: the 221 module will be called ide-tape. 222 223config BLK_DEV_IDEFLOPPY 224 tristate "Include IDE/ATAPI FLOPPY support" 225 ---help--- 226 If you have an IDE floppy drive which uses the ATAPI protocol, 227 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy 228 drives, similar to the SCSI protocol. 229 230 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by 231 this driver. For information about jumper settings and the question 232 of when a ZIP drive uses a partition table, see 233 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>. 234 (ATAPI PD-CD/CDR drives are not supported by this driver; support 235 for PD-CD/CDR drives is available if you answer Y to 236 "SCSI emulation support", below). 237 238 If you say Y here, the FLOPPY drive will be identified along with 239 other IDE devices, as "hdb" or "hdc", or something similar (check 240 the boot messages with dmesg). 241 242 To compile this driver as a module, choose M here: the 243 module will be called ide-floppy. 244 245config BLK_DEV_IDESCSI 246 tristate "SCSI emulation support" 247 depends on SCSI 248 ---help--- 249 WARNING: ide-scsi is no longer needed for cd writing applications! 250 The 2.6 kernel supports direct writing to ide-cd, which eliminates 251 the need for ide-scsi + the entire scsi stack just for writing a 252 cd. The new method is more efficient in every way. 253 254 This will provide SCSI host adapter emulation for IDE ATAPI devices, 255 and will allow you to use a SCSI device driver instead of a native 256 ATAPI driver. 257 258 This is useful if you have an ATAPI device for which no native 259 driver has been written (for example, an ATAPI PD-CD drive); 260 you can then use this emulation together with an appropriate SCSI 261 device driver. In order to do this, say Y here and to "SCSI support" 262 and "SCSI generic support", below. You must then provide the kernel 263 command line "hdx=ide-scsi" (try "man bootparam" or see the 264 documentation of your boot loader (lilo or loadlin) about how to 265 pass options to the kernel at boot time) for devices if you want the 266 native EIDE sub-drivers to skip over the native support, so that 267 this SCSI emulation can be used instead. 268 269 Note that this option does NOT allow you to attach SCSI devices to a 270 box that doesn't have a SCSI host adapter installed. 271 272 If both this SCSI emulation and native ATAPI support are compiled 273 into the kernel, the native support will be used. 274 275config BLK_DEV_IDEACPI 276 bool "IDE ACPI support" 277 depends on ACPI 278 ---help--- 279 Implement ACPI support for generic IDE devices. On modern 280 machines ACPI support is required to properly handle ACPI S3 states. 281 282config IDE_TASK_IOCTL 283 bool "IDE Taskfile Access" 284 help 285 This is a direct raw access to the media. It is a complex but 286 elegant solution to test and validate the domain of the hardware and 287 perform below the driver data recovery if needed. This is the most 288 basic form of media-forensics. 289 290 If you are unsure, say N here. 291 292config IDE_PROC_FS 293 bool "legacy /proc/ide/ support" 294 depends on IDE && PROC_FS 295 default y 296 help 297 This option enables support for the various files in 298 /proc/ide. In Linux 2.6 this has been superseded by 299 files in sysfs but many legacy applications rely on this. 300 301 If unsure say Y. 302 303comment "IDE chipset support/bugfixes" 304 305config IDE_GENERIC 306 tristate "generic/default IDE chipset support" 307 default H8300 308 help 309 If unsure, say N. 310 311config BLK_DEV_PLATFORM 312 tristate "Platform driver for IDE interfaces" 313 help 314 This is the platform IDE driver, used mostly for Memory Mapped 315 IDE devices, like Compact Flashes running in True IDE mode. 316 317 If unsure, say N. 318 319config BLK_DEV_CMD640 320 bool "CMD640 chipset bugfix/support" 321 depends on X86 322 ---help--- 323 The CMD-Technologies CMD640 IDE chip is used on many common 486 and 324 Pentium motherboards, usually in combination with a "Neptune" or 325 "SiS" chipset. Unfortunately, it has a number of rather nasty 326 design flaws that can cause severe data corruption under many common 327 conditions. Say Y here to include code which tries to automatically 328 detect and correct the problems under Linux. This option also 329 enables access to the secondary IDE ports in some CMD640 based 330 systems. 331 332 This driver will work automatically in PCI based systems (most new 333 systems have PCI slots). But if your system uses VESA local bus 334 (VLB) instead of PCI, you must also supply a kernel boot parameter 335 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man 336 bootparam" or see the documentation of your boot loader about how to 337 pass options to the kernel.) 338 339 The CMD640 chip is also used on add-in cards by Acculogic, and on 340 the "CSA-6400E PCI to IDE controller" that some people have. For 341 details, read <file:Documentation/ide.txt>. 342 343config BLK_DEV_CMD640_ENHANCED 344 bool "CMD640 enhanced support" 345 depends on BLK_DEV_CMD640 346 help 347 This option includes support for setting/autotuning PIO modes and 348 prefetch on CMD640 IDE interfaces. For details, read 349 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface 350 and your BIOS does not already do this for you, then say Y here. 351 Otherwise say N. 352 353config BLK_DEV_IDEPNP 354 bool "PNP EIDE support" 355 depends on PNP 356 select IDE_GENERIC 357 help 358 If you have a PnP (Plug and Play) compatible EIDE card and 359 would like the kernel to automatically detect and activate 360 it, say Y here. 361 362config BLK_DEV_IDEPCI 363 bool "PCI IDE chipset support" if PCI 364 default BLK_DEV_IDEDMA_PMAC if PPC_PMAC && BLK_DEV_IDEDMA_PMAC 365 help 366 Say Y here for PCI systems which use IDE drive(s). 367 This option helps the IDE driver to automatically detect and 368 configure all PCI-based IDE interfaces in your system. 369 370config IDEPCI_SHARE_IRQ 371 bool "Sharing PCI IDE interrupts support" 372 depends on PCI && BLK_DEV_IDEPCI 373 help 374 Some ATA/IDE chipsets have hardware support which allows for 375 sharing a single IRQ with other cards. To enable support for 376 this in the ATA/IDE driver, say Y here. 377 378 It is safe to say Y to this question, in most cases. 379 If unsure, say N. 380 381config IDEPCI_PCIBUS_ORDER 382 def_bool PCI && BLK_DEV_IDE=y && BLK_DEV_IDEPCI 383 384config BLK_DEV_OFFBOARD 385 bool "Boot off-board chipsets first support" 386 depends on PCI && BLK_DEV_IDEPCI 387 help 388 Normally, IDE controllers built into the motherboard (on-board 389 controllers) are assigned to ide0 and ide1 while those on add-in PCI 390 cards (off-board controllers) are relegated to ide2 and ide3. 391 Answering Y here will allow you to reverse the situation, with 392 off-board controllers on ide0/1 and on-board controllers on ide2/3. 393 This can improve the usability of some boot managers such as lilo 394 when booting from a drive on an off-board controller. 395 396 If you say Y here, and you actually want to reverse the device scan 397 order as explained above, you also need to issue the kernel command 398 line option "ide=reverse". (Try "man bootparam" or see the 399 documentation of your boot loader (lilo or loadlin) about how to 400 pass options to the kernel at boot time.) 401 402 Note that, if you do this, the order of the hd* devices will be 403 rearranged which may require modification of fstab and other files. 404 405 If in doubt, say N. 406 407config BLK_DEV_GENERIC 408 tristate "Generic PCI IDE Chipset Support" 409 depends on BLK_DEV_IDEPCI 410 help 411 This option provides generic support for various PCI IDE Chipsets 412 which otherwise might not be supported. 413 414config BLK_DEV_OPTI621 415 tristate "OPTi 82C621 chipset enhanced support (EXPERIMENTAL)" 416 depends on PCI && BLK_DEV_IDEPCI && EXPERIMENTAL 417 help 418 This is a driver for the OPTi 82C621 EIDE controller. 419 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>. 420 421config BLK_DEV_RZ1000 422 tristate "RZ1000 chipset bugfix/support" 423 depends on PCI && BLK_DEV_IDEPCI && X86 424 help 425 The PC-Technologies RZ1000 IDE chip is used on many common 486 and 426 Pentium motherboards, usually along with the "Neptune" chipset. 427 Unfortunately, it has a rather nasty design flaw that can cause 428 severe data corruption under many conditions. Say Y here to include 429 code which automatically detects and corrects the problem under 430 Linux. This may slow disk throughput by a few percent, but at least 431 things will operate 100% reliably. 432 433config BLK_DEV_IDEDMA_PCI 434 bool "Generic PCI bus-master DMA support" 435 depends on PCI && BLK_DEV_IDEPCI 436 ---help--- 437 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and 438 is capable of bus-master DMA operation (most Pentium PCI systems), 439 you will want to say Y here to reduce CPU overhead. You can then use 440 the "hdparm" utility to enable DMA for drives for which it was not 441 enabled automatically. By default, DMA is not enabled automatically 442 for these drives, but you can change that by saying Y to the 443 following question "Use DMA by default when available". You can get 444 the latest version of the hdparm utility from 445 <ftp://ibiblio.org/pub/Linux/system/hardware/>. 446 447 Read the comments at the beginning of <file:drivers/ide/ide-dma.c> 448 and the file <file:Documentation/ide.txt> for more information. 449 450 It is safe to say Y to this question. 451 452if BLK_DEV_IDEDMA_PCI 453 454config BLK_DEV_IDEDMA_FORCED 455 bool "Force enable legacy 2.0.X HOSTS to use DMA" 456 help 457 This is an old piece of lost code from Linux 2.0 Kernels. 458 459 Generally say N here. 460 461config IDEDMA_ONLYDISK 462 bool "Enable DMA only for disks " 463 help 464 This is used if you know your ATAPI Devices are going to fail DMA 465 Transfers. 466 467 Generally say N here. 468 469config BLK_DEV_AEC62XX 470 tristate "AEC62XX chipset support" 471 help 472 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx) 473 IDE controllers. This allows the kernel to change PIO, DMA and UDMA 474 speeds and to configure the chip to optimum performance. 475 476config BLK_DEV_ALI15X3 477 tristate "ALI M15x3 chipset support" 478 help 479 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C 480 onboard chipsets. It also tests for Simplex mode and enables 481 normal dual channel support. 482 483 If you say Y here, you also need to say Y to "Use DMA by default 484 when available", above. Please read the comments at the top of 485 <file:drivers/ide/pci/alim15x3.c>. 486 487 If unsure, say N. 488 489config WDC_ALI15X3 490 bool "ALI M15x3 WDC support (DANGEROUS)" 491 depends on BLK_DEV_ALI15X3 492 ---help--- 493 This allows for UltraDMA support for WDC drives that ignore CRC 494 checking. You are a fool for enabling this option, but there have 495 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF 496 YOU ENABLE THIS! No one will listen, just laugh for ignoring this 497 SERIOUS WARNING. 498 499 Using this option can allow WDC drives to run at ATA-4/5 transfer 500 rates with only an ATA-2 support structure. 501 502 SAY N! 503 504config BLK_DEV_AMD74XX 505 tristate "AMD and nVidia IDE support" 506 help 507 This driver adds explicit support for AMD-7xx and AMD-8111 chips 508 and also for the nVidia nForce chip. This allows the kernel to 509 change PIO, DMA and UDMA speeds and to configure the chip to 510 optimum performance. 511 512config BLK_DEV_ATIIXP 513 tristate "ATI IXP chipset IDE support" 514 depends on X86 515 help 516 This driver adds explicit support for ATI IXP chipset. 517 This allows the kernel to change PIO, DMA and UDMA speeds 518 and to configure the chip to optimum performance. 519 520 Say Y here if you have an ATI IXP chipset IDE controller. 521 522config BLK_DEV_CMD64X 523 tristate "CMD64{3|6|8|9} chipset support" 524 help 525 Say Y here if you have an IDE controller which uses any of these 526 chipsets: CMD643, CMD646, or CMD648. 527 528config BLK_DEV_TRIFLEX 529 tristate "Compaq Triflex IDE support" 530 help 531 Say Y here if you have a Compaq Triflex IDE controller, such 532 as those commonly found on Compaq Pentium-Pro systems 533 534config BLK_DEV_CY82C693 535 tristate "CY82C693 chipset support" 536 help 537 This driver adds detection and support for the CY82C693 chipset 538 used on Digital's PC-Alpha 164SX boards. 539 540 If you say Y here, you need to say Y to "Use DMA by default 541 when available" as well. 542 543config BLK_DEV_CS5520 544 tristate "Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)" 545 depends on EXPERIMENTAL 546 help 547 Include support for PIO tuning and virtual DMA on the Cyrix MediaGX 548 5510/5520 chipset. This will automatically be detected and 549 configured if found. 550 551 It is safe to say Y to this question. 552 553config BLK_DEV_CS5530 554 tristate "Cyrix/National Semiconductor CS5530 MediaGX chipset support" 555 help 556 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This 557 will automatically be detected and configured if found. 558 559 It is safe to say Y to this question. 560 561config BLK_DEV_CS5535 562 tristate "AMD CS5535 chipset support" 563 depends on X86 && !X86_64 564 help 565 Include support for UDMA on the NSC/AMD CS5535 companion chipset. 566 This will automatically be detected and configured if found. 567 568 It is safe to say Y to this question. 569 570config BLK_DEV_HPT34X 571 tristate "HPT34X chipset support" 572 help 573 This driver adds up to 4 more EIDE devices sharing a single 574 interrupt. The HPT343 chipset in its current form is a non-bootable 575 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX) 576 PCI UDMA controllers. This driver requires dynamic tuning of the 577 chipset during the ide-probe at boot time. It is reported to support 578 DVD II drives, by the manufacturer. 579 580config HPT34X_AUTODMA 581 bool "HPT34X AUTODMA support (EXPERIMENTAL)" 582 depends on BLK_DEV_HPT34X && EXPERIMENTAL 583 help 584 This is a dangerous thing to attempt currently! Please read the 585 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y 586 here, then say Y to "Use DMA by default when available" as well. 587 588 If unsure, say N. 589 590config BLK_DEV_HPT366 591 tristate "HPT36X/37X chipset support" 592 ---help--- 593 HPT366 is an Ultra DMA chipset for ATA-66. 594 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based. 595 HPT370 is an Ultra DMA chipset for ATA-100. 596 HPT372 is an Ultra DMA chipset for ATA-100. 597 HPT374 is an Ultra DMA chipset for ATA-100. 598 599 This driver adds up to 4 more EIDE devices sharing a single 600 interrupt. 601 602 The HPT366 chipset in its current form is bootable. One solution 603 for this problem are special LILO commands for redirecting the 604 reference to device 0x80. The other solution is to say Y to "Boot 605 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless 606 your mother board has the chipset natively mounted. Regardless one 607 should use the fore mentioned option and call at LILO or include 608 "ide=reverse" in LILO's append-line. 609 610 This driver requires dynamic tuning of the chipset during the 611 ide-probe at boot. It is reported to support DVD II drives, by the 612 manufacturer. 613 614config BLK_DEV_JMICRON 615 tristate "JMicron JMB36x support" 616 help 617 Basic support for the JMicron ATA controllers. For full support 618 use the libata drivers. 619 620config BLK_DEV_SC1200 621 tristate "National SCx200 chipset support" 622 help 623 This driver adds support for the built in IDE on the National 624 SCx200 series of embedded x86 "Geode" systems 625 626config BLK_DEV_PIIX 627 tristate "Intel PIIXn chipsets support" 628 help 629 This driver adds explicit support for Intel PIIX and ICH chips 630 and also for the Efar Victory66 (slc90e66) chip. This allows 631 the kernel to change PIO, DMA and UDMA speeds and to configure 632 the chip to optimum performance. 633 634config BLK_DEV_IT8213 635 tristate "IT8213 IDE support" 636 help 637 This driver adds support for the ITE 8213 IDE controller. 638 639config BLK_DEV_IT821X 640 tristate "IT821X IDE support" 641 help 642 This driver adds support for the ITE 8211 IDE controller and the 643 IT 8212 IDE RAID controller in both RAID and pass-through mode. 644 645config BLK_DEV_NS87415 646 tristate "NS87415 chipset support" 647 help 648 This driver adds detection and support for the NS87415 chip 649 (used mainly on SPARC64 and PA-RISC machines). 650 651 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>. 652 653config BLK_DEV_PDC202XX_OLD 654 tristate "PROMISE PDC202{46|62|65|67} support" 655 help 656 Promise Ultra33 or PDC20246 657 Promise Ultra66 or PDC20262 658 Promise Ultra100 or PDC20265/PDC20267/PDC20268 659 660 This driver adds up to 4 more EIDE devices sharing a single 661 interrupt. This add-on card is a bootable PCI UDMA controller. Since 662 multiple cards can be installed and there are BIOS ROM problems that 663 happen if the BIOS revisions of all installed cards (three-max) do 664 not match, the driver attempts to do dynamic tuning of the chipset 665 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required 666 for more than one card. This card may require that you say Y to 667 "Special UDMA Feature". 668 669 If you say Y here, you need to say Y to "Use DMA by default when 670 available" as well. 671 672 Please read the comments at the top of 673 <file:drivers/ide/pci/pdc202xx_old.c>. 674 675 If unsure, say N. 676 677config PDC202XX_BURST 678 bool "Special UDMA Feature" 679 depends on BLK_DEV_PDC202XX_OLD 680 help 681 This option causes the pdc202xx driver to enable UDMA modes on the 682 PDC202xx even when the PDC202xx BIOS has not done so. 683 684 It was originally designed for the PDC20246/Ultra33, whose BIOS will 685 only setup UDMA on the first two PDC20246 cards. It has also been 686 used successfully on a PDC20265/Ultra100, allowing use of UDMA modes 687 when the PDC20265 BIOS has been disabled (for faster boot up). 688 689 Please read the comments at the top of 690 <file:drivers/ide/pci/pdc202xx_old.c>. 691 692 If unsure, say N. 693 694config BLK_DEV_PDC202XX_NEW 695 tristate "PROMISE PDC202{68|69|70|71|75|76|77} support" 696 697config BLK_DEV_SVWKS 698 tristate "ServerWorks OSB4/CSB5/CSB6 chipsets support" 699 help 700 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5 701 chipsets. 702 703config BLK_DEV_SGIIOC4 704 tristate "Silicon Graphics IOC4 chipset ATA/ATAPI support" 705 depends on (IA64_SGI_SN2 || IA64_GENERIC) && SGI_IOC4 706 select IDEPCI_SHARE_IRQ 707 help 708 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4 709 chipset, which has one channel and can support two devices. 710 Please say Y here if you have an Altix System from SGI. 711 712config BLK_DEV_SIIMAGE 713 tristate "Silicon Image chipset support" 714 help 715 This driver adds PIO/(U)DMA support for the SI CMD680 and SII 716 3112 (Serial ATA) chips. 717 718config BLK_DEV_SIS5513 719 tristate "SiS5513 chipset support" 720 depends on X86 721 ---help--- 722 This driver ensures (U)DMA support for SIS5513 chipset family based 723 mainboards. 724 725 The following chipsets are supported: 726 ATA16: SiS5511, SiS5513 727 ATA33: SiS5591, SiS5597, SiS5598, SiS5600 728 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640 729 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740, 730 SiS745, SiS750 731 732 If you say Y here, you need to say Y to "Use DMA by default when 733 available" as well. 734 735 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>. 736 737config BLK_DEV_SL82C105 738 tristate "Winbond SL82c105 support" 739 depends on (PPC || ARM) 740 help 741 If you have a Winbond SL82c105 IDE controller, say Y here to enable 742 special configuration for this chip. This is common on various CHRP 743 motherboards, but could be used elsewhere. If in doubt, say Y. 744 745config BLK_DEV_SLC90E66 746 tristate "SLC90E66 chipset support" 747 help 748 This driver ensures (U)DMA support for Victory66 SouthBridges for 749 SMsC with Intel NorthBridges. This is an Ultra66 based chipset. 750 The nice thing about it is that you can mix Ultra/DMA/PIO devices 751 and it will handle timing cycles. Since this is an improved 752 look-a-like to the PIIX4 it should be a nice addition. 753 754 If you say Y here, you need to say Y to "Use DMA by default when 755 available" as well. 756 757 Please read the comments at the top of 758 <file:drivers/ide/pci/slc90e66.c>. 759 760config BLK_DEV_TRM290 761 tristate "Tekram TRM290 chipset support" 762 help 763 This driver adds support for bus master DMA transfers 764 using the Tekram TRM290 PCI IDE chip. Volunteers are 765 needed for further tweaking and development. 766 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>. 767 768config BLK_DEV_VIA82CXXX 769 tristate "VIA82CXXX chipset support" 770 help 771 This driver adds explicit support for VIA BusMastering IDE chips. 772 This allows the kernel to change PIO, DMA and UDMA speeds and to 773 configure the chip to optimum performance. 774 775config BLK_DEV_TC86C001 776 tristate "Toshiba TC86C001 support" 777 help 778 This driver adds support for Toshiba TC86C001 GOKU-S chip. 779 780config BLK_DEV_CELLEB 781 tristate "Toshiba's Cell Reference Set IDE support" 782 depends on PPC_CELLEB 783 help 784 This driver provides support for the built-in IDE controller on 785 Toshiba Cell Reference Board. 786 If unsure, say Y. 787 788endif 789 790config BLK_DEV_IDE_PMAC 791 bool "Builtin PowerMac IDE support" 792 depends on PPC_PMAC && IDE=y && BLK_DEV_IDE=y 793 help 794 This driver provides support for the built-in IDE controller on 795 most of the recent Apple Power Macintoshes and PowerBooks. 796 If unsure, say Y. 797 798config BLK_DEV_IDE_PMAC_ATA100FIRST 799 bool "Probe internal ATA/100 (Kauai) first" 800 depends on BLK_DEV_IDE_PMAC 801 help 802 This option will cause the ATA/100 controller found in UniNorth2 803 based machines (Windtunnel PowerMac, Aluminium PowerBooks, ...) 804 to be probed before the ATA/66 and ATA/33 controllers. Without 805 these, those machine used to have the hard disk on hdc and the 806 CD-ROM on hda. This option changes this to more natural hda for 807 hard disk and hdc for CD-ROM. 808 809config BLK_DEV_IDEDMA_PMAC 810 bool "PowerMac IDE DMA support" 811 depends on BLK_DEV_IDE_PMAC 812 select BLK_DEV_IDEDMA_PCI 813 help 814 This option allows the driver for the built-in IDE controller on 815 Power Macintoshes and PowerBooks to use DMA (direct memory access) 816 to transfer data to and from memory. Saying Y is safe and improves 817 performance. 818 819config BLK_DEV_IDE_SWARM 820 tristate "IDE for Sibyte evaluation boards" 821 depends on SIBYTE_SB1xxx_SOC 822 823config BLK_DEV_IDE_AU1XXX 824 bool "IDE for AMD Alchemy Au1200" 825 depends on SOC_AU1200 826choice 827 prompt "IDE Mode for AMD Alchemy Au1200" 828 default CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA 829 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX 830 831config BLK_DEV_IDE_AU1XXX_PIO_DBDMA 832 bool "PIO+DbDMA IDE for AMD Alchemy Au1200" 833 834config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA 835 bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200" 836 depends on SOC_AU1200 && BLK_DEV_IDE_AU1XXX 837endchoice 838 839config BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ 840 int "Maximum transfer size (KB) per request (up to 128)" 841 default "128" 842 depends on BLK_DEV_IDE_AU1XXX 843 844config IDE_ARM 845 def_bool ARM && (ARCH_CLPS7500 || ARCH_RPC || ARCH_SHARK) 846 select IDE_GENERIC 847 848config BLK_DEV_IDE_ICSIDE 849 tristate "ICS IDE interface support" 850 depends on ARM && ARCH_ACORN 851 help 852 On Acorn systems, say Y here if you wish to use the ICS IDE 853 interface card. This is not required for ICS partition support. 854 If you are unsure, say N to this. 855 856config BLK_DEV_IDEDMA_ICS 857 bool "ICS DMA support" 858 depends on BLK_DEV_IDE_ICSIDE 859 help 860 Say Y here if you want to add DMA (Direct Memory Access) support to 861 the ICS IDE driver. 862 863config BLK_DEV_IDE_RAPIDE 864 tristate "RapIDE interface support" 865 depends on ARM && ARCH_ACORN 866 help 867 Say Y here if you want to support the Yellowstone RapIDE controller 868 manufactured for use with Acorn computers. 869 870config BLK_DEV_IDE_BAST 871 tristate "Simtec BAST / Thorcom VR1000 IDE support" 872 depends on ARM && (ARCH_BAST || MACH_VR1000) 873 help 874 Say Y here if you want to support the onboard IDE channels on the 875 Simtec BAST or the Thorcom VR1000 876 877config BLK_DEV_GAYLE 878 bool "Amiga Gayle IDE interface support" 879 depends on AMIGA 880 select IDE_GENERIC 881 help 882 This is the IDE driver for the Amiga Gayle IDE interface. It supports 883 both the `A1200 style' and `A4000 style' of the Gayle IDE interface, 884 This includes builtin IDE interfaces on some Amiga models (A600, 885 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion 886 bus (M-Tech E-Matrix 530 expansion card). 887 Say Y if you have an Amiga with a Gayle IDE interface and want to use 888 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to 889 it. 890 Note that you also have to enable Zorro bus support if you want to 891 use Gayle IDE interfaces on the Zorro expansion bus. 892 893config BLK_DEV_IDEDOUBLER 894 bool "Amiga IDE Doubler support (EXPERIMENTAL)" 895 depends on BLK_DEV_GAYLE && EXPERIMENTAL 896 ---help--- 897 This driver provides support for the so-called `IDE doublers' (made 898 by various manufacturers, e.g. Eyetech) that can be connected to the 899 builtin IDE interface of some Amiga models. Using such an IDE 900 doubler, you can connect up to four instead of two IDE devices on 901 the Amiga's builtin IDE interface. 902 903 Note that the normal Amiga Gayle IDE driver may not work correctly 904 if you have an IDE doubler and don't enable this driver! 905 906 Say Y if you have an IDE doubler. The driver is enabled at kernel 907 runtime using the "ide=doubler" kernel boot parameter. 908 909config BLK_DEV_BUDDHA 910 bool "Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)" 911 depends on ZORRO && EXPERIMENTAL 912 select IDE_GENERIC 913 help 914 This is the IDE driver for the IDE interfaces on the Buddha, 915 Catweasel and X-Surf expansion boards. It supports up to two interfaces 916 on the Buddha, three on the Catweasel and two on the X-Surf. 917 918 Say Y if you have a Buddha or Catweasel expansion board and want to 919 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected 920 to one of its IDE interfaces. 921 922config BLK_DEV_FALCON_IDE 923 bool "Falcon IDE interface support" 924 depends on ATARI 925 select IDE_GENERIC 926 help 927 This is the IDE driver for the builtin IDE interface on the Atari 928 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard 929 disks, CD-ROM drives, etc.) that are connected to the builtin IDE 930 interface. 931 932config BLK_DEV_MAC_IDE 933 bool "Macintosh Quadra/Powerbook IDE interface support" 934 depends on MAC 935 select IDE_GENERIC 936 help 937 This is the IDE driver for the builtin IDE interface on some m68k 938 Macintosh models. It supports both the `Quadra style' (used in 939 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style' 940 (used in the Powerbook 150 and 190 models) IDE interface. 941 942 Say Y if you have such an Macintosh model and want to use IDE 943 devices (hard disks, CD-ROM drives, etc.) that are connected to the 944 builtin IDE interface. 945 946config BLK_DEV_Q40IDE 947 bool "Q40/Q60 IDE interface support" 948 depends on Q40 949 select IDE_GENERIC 950 help 951 Enable the on-board IDE controller in the Q40/Q60. This should 952 normally be on; disable it only if you are running a custom hard 953 drive subsystem through an expansion card. 954 955config BLK_DEV_MPC8xx_IDE 956 bool "MPC8xx IDE support" 957 depends on 8xx && IDE=y && BLK_DEV_IDE=y && !PPC_MERGE 958 select IDE_GENERIC 959 help 960 This option provides support for IDE on Motorola MPC8xx Systems. 961 Please see 'Type of MPC8xx IDE interface' for details. 962 963 If unsure, say N. 964 965choice 966 prompt "Type of MPC8xx IDE interface" 967 depends on BLK_DEV_MPC8xx_IDE 968 default IDE_8xx_PCCARD 969 970config IDE_8xx_PCCARD 971 bool "8xx_PCCARD" 972 ---help--- 973 Select how the IDE devices are connected to the MPC8xx system: 974 975 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination 976 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter), 977 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL 978 systems) 979 980 8xx_DIRECT is used for directly connected IDE devices using the 8xx 981 internal PCMCIA interface (example: IVMS8 systems) 982 983 EXT_DIRECT is used for IDE devices directly connected to the 8xx 984 bus using some glue logic, but _not_ the 8xx internal 985 PCMCIA interface (example: IDIF860 systems) 986 987config IDE_8xx_DIRECT 988 bool "8xx_DIRECT" 989 990config IDE_EXT_DIRECT 991 bool "EXT_DIRECT" 992 993endchoice 994 995# no isa -> no vlb 996config IDE_CHIPSETS 997 bool "Other IDE chipset support" 998 depends on ISA 999 ---help--- 1000 Say Y here if you want to include enhanced support for various IDE 1001 interface chipsets used on motherboards and add-on cards. You can 1002 then pick your particular IDE chip from among the following options. 1003 This enhanced support may be necessary for Linux to be able to 1004 access the 3rd/4th drives in some systems. It may also enable 1005 setting of higher speed I/O rates to improve system performance with 1006 these chipsets. Most of these also require special kernel boot 1007 parameters to actually turn on the support at runtime; you can find 1008 a list of these in the file <file:Documentation/ide.txt>. 1009 1010 People with SCSI-only systems can say N here. 1011 1012if IDE_CHIPSETS 1013 1014comment "Note: most of these also require special kernel boot parameters" 1015 1016config BLK_DEV_4DRIVES 1017 bool "Generic 4 drives/port support" 1018 help 1019 Certain older chipsets, including the Tekram 690CD, use a single set 1020 of I/O ports at 0x1f0 to control up to four drives, instead of the 1021 customary two drives per port. Support for this can be enabled at 1022 runtime using the "ide0=four" kernel boot parameter if you say Y 1023 here. 1024 1025config BLK_DEV_ALI14XX 1026 tristate "ALI M14xx support" 1027 help 1028 This driver is enabled at runtime using the "ali14xx.probe" kernel 1029 boot parameter. It enables support for the secondary IDE interface 1030 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster 1031 I/O speeds to be set as well. See the files 1032 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for 1033 more info. 1034 1035config BLK_DEV_DTC2278 1036 tristate "DTC-2278 support" 1037 help 1038 This driver is enabled at runtime using the "dtc2278.probe" kernel 1039 boot parameter. It enables support for the secondary IDE interface 1040 of the DTC-2278 card, and permits faster I/O speeds to be set as 1041 well. See the <file:Documentation/ide.txt> and 1042 <file:drivers/ide/legacy/dtc2278.c> files for more info. 1043 1044config BLK_DEV_HT6560B 1045 tristate "Holtek HT6560B support" 1046 help 1047 This driver is enabled at runtime using the "ht6560b.probe" kernel 1048 boot parameter. It enables support for the secondary IDE interface 1049 of the Holtek card, and permits faster I/O speeds to be set as well. 1050 See the <file:Documentation/ide.txt> and 1051 <file:drivers/ide/legacy/ht6560b.c> files for more info. 1052 1053config BLK_DEV_QD65XX 1054 tristate "QDI QD65xx support" 1055 help 1056 This driver is enabled at runtime using the "qd65xx.probe" kernel 1057 boot parameter. It permits faster I/O speeds to be set. See the 1058 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for 1059 more info. 1060 1061config BLK_DEV_UMC8672 1062 tristate "UMC-8672 support" 1063 help 1064 This driver is enabled at runtime using the "umc8672.probe" kernel 1065 boot parameter. It enables support for the secondary IDE interface 1066 of the UMC-8672, and permits faster I/O speeds to be set as well. 1067 See the files <file:Documentation/ide.txt> and 1068 <file:drivers/ide/legacy/umc8672.c> for more info. 1069 1070endif 1071 1072config BLK_DEV_IDEDMA 1073 def_bool BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS || BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA 1074 1075config IDEDMA_IVB 1076 bool "IGNORE word93 Validation BITS" 1077 depends on BLK_DEV_IDEDMA_PCI || BLK_DEV_IDEDMA_PMAC || BLK_DEV_IDEDMA_ICS 1078 ---help--- 1079 There are unclear terms in ATA-4 and ATA-5 standards how certain 1080 hardware (an 80c ribbon) should be detected. Different interpretations 1081 of the standards have been released in hardware. This causes problems: 1082 for example, a host with Ultra Mode 4 (or higher) will not run 1083 in that mode with an 80c ribbon. 1084 1085 If you are experiencing compatibility or performance problems, you 1086 MAY try to answer Y here. However, it does not necessarily solve 1087 any of your problems, it could even cause more of them. 1088 1089 It is normally safe to answer Y; however, the default is N. 1090 1091endif 1092 1093config BLK_DEV_HD_ONLY 1094 bool "Old hard disk (MFM/RLL/IDE) driver" 1095 depends on BLK_DEV_IDE=n 1096 help 1097 There are two drivers for MFM/RLL/IDE hard disks. Most people use 1098 the newer enhanced driver, but this old one is still around for two 1099 reasons. Some older systems have strange timing problems and seem to 1100 work only with the old driver (which itself does not work with some 1101 newer systems). The other reason is that the old driver is smaller, 1102 since it lacks the enhanced functionality of the new one. This makes 1103 it a good choice for systems with very tight memory restrictions, or 1104 for systems with only older MFM/RLL/ESDI drives. Choosing the old 1105 driver can save 13 KB or so of kernel memory. 1106 1107 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver 1108 instead of this one. For more detailed information, read the 1109 Disk-HOWTO, available from 1110 <http://www.tldp.org/docs.html#howto>. 1111 1112config BLK_DEV_HD 1113 def_bool BLK_DEV_HD_IDE || BLK_DEV_HD_ONLY 1114 1115endif # IDE 1116