Plug and Play for IDE Controllers and Peripherals

This section summarizes the Plug and Play requirements for IDE controllers and peripherals.

11. Plug and Play device identifier

• For a system board device, there must be a Plug and Play device-specific ID.
• Each IDE device must provide device identifiers in the manner required for the bus it uses, as defined in Part 3 of this guide.

  For example, an add-on PCI IDE device must comply with PCI 2.1 requirements and also provide a Subsystem ID and Subsystem Vendor ID, as defined in the "PCI" chapter in Part 3 of this guide. PCI IDE controllers integrated into core logic on the system board do not have to provide Subsystem IDs and Vendor Subsystem IDs, but must meet the other requirements in the PCI 2.1 specification.

12. Dynamic resource configuration for all devices

Changing or adding a controller to the system must not require changing jumpers or switches on either the controller or the system board.

13. Resource configuration per bus requirements

Plug and Play resource configuration requirements are defined by the bus used by the IDE device, as defined in the related chapters in Part 3 of this guide. For non-PCI devices, the following is required:

• Support for two ranges: 1F0h – 1F7h, 3F6h and 170h – 177h, 376h.

  Using the standard addresses ensures the proper functioning of software written for legacy systems. Support for alternate I/O addresses 170h – 177h ensures support for enhanced IDE.

• Support for IRQ 14 and IRQ 15.

14. 3F7h and 377h not claimed by IDE devices

Although IDE device might use these addresses, 3F7h and 377h also contain registers used by the floppy disk controller. To prevent resource conflicts, these addresses must not be claimed as resources in device registers.