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