IDE / ATA
IDE (Integrated Drive Electronics) is the ATA-defined storage interface associated with drives that integrate their controller electronics.
Naming: IDE denotes an interface defined by ATA. [5] PATA is parallel ATA, not a successor to a distinct IDE interface. Firmware terminology can be broader: the UEFI initialization specification describes both PATA and SATA IDE controllers. A SATA controller can emulate PATA registers or expose AHCI; an IDE-mode setting does not identify the cable. [4]
Early ATA: The ATA-1 revision 4c draft describes an integrated host-to-drive interface, a 40-pin connector and two devices per channel. Its PIO modes 0-2 have minimum cycle times of 600, 383 and 240 ns. At two bytes per cycle these imply about 3.3, 5.2 and 8.3 decimal MB/s, not the ceiling of all later PATA modes. [2]
Addressing: A 28-bit LBA space with 512-byte sectors spans 128 GiB, or about 137 GB. This is an addressing calculation, not the capacity limit of every ATA revision. [2]
Software: Removal of the legacy Linux IDE driver in 2021 concerns that driver implementation, not the disappearance of ATA devices or the libata subsystem. [3]
Relations
- related
- PATA, Serial ATA (SATA), Hard disk drive (HDD), AHCI, ST-412, Ultra DMA
Advantages
- A defined register set, commands and LBA addressing carried over into later ATA generations and into the kernel libata layer. [2, 3]
Citations
- Information technology - AT Attachment Interface for Disk Drives, ATA-1 draft revision 4c (X3T9.2 draft of ANSI X3.221)
- ide: remove the legacy ide driver. Linux kernel commit b7fb14d3ac63, 2021
- UEFI PI 1.8: IDE controller terminology, sections 7.2.1.1 and 7.2.3.1
- SNIA Dictionary: Integrated Drive Electronics, ATA interface naming
Further reading
Sources & caveats
- The ATA-1 source is working draft revision 4c, accessed through a university-hosted copy, not the published ANSI standard.
- UEFI PI 1.8 establishes controller terminology, not the first historical use of IDE or PATA.
- Arithmetic uses two bytes per minimum PIO cycle and 2^28 sectors of 512 bytes; neither calculation is a device benchmark.
- Historical interface documentation does not establish a single current end-of-life status for all implementations.