pciide(4) [netbsd man page]
PCIIDE(4) BSD Kernel Interfaces Manual PCIIDE(4) NAME
pciide -- PCI IDE disk controllers driver SYNOPSIS
pciide* at pci? dev ? function ? flags 0x0000 pciide* at pnpbios? index ? DESCRIPTION
The pciide driver supports the PCI IDE controllers as specified in the "PCI IDE controller specification, revision 1.0" draft, and provides the interface with the hardware for the ata driver. Please use the chip-specific drivers for the following controllers for enhanced and DMA support: - Acard ATP850 (Ultra/33) and ATP860 (Ultra/66) IDE Controllers: acardide(4) - Acer labs M5229 IDE Controller: aceride(4) - Advanced Micro Devices AMD-756, 766, and 768 IDE Controllers: viaide(4) - Advanced Micro Devices Geode IDE Controllers: geodeide(4) - CMD Tech PCI0643, PCI0646, PCI0648, and PCI0649 IDE Controllers: cmdide(4) - Contaq Microsystems/Cypress CY82C693 IDE Controller: cypide(4) - HighPoint HPT366 Ultra/66, HPT370 Ultra/100, HPT372, and HPT374 Ultra/133 IDE controller: hptide(4) - Intel PIIX, PIIX3, and PIIX4 IDE Controllers: piixide(4) - Intel i31244 Serial ATA controller: artsata(4) - Intel 82801 (ICH/ICH0/ICH2/ICH3/ICH4/ICH5/ICH6) IDE Controllers: piixide(4) - Intel SCH IDE Controllers: schide(4) - NVIDIA nForce/nForce2 IDE Controllers: viaide(4) - OPTi 82c621 (plus a few of its derivatives) IDE Controllers: optiide(4) - Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66), PDC20265/PDC20267 (Ultra100), PDC20268 (Ultra/100TX2 and Ultra/100TX2v2), Ultra/133, Ultra/133TX2 and Ultra/133TX2v2 PCI IDE controllers: pdcide(4) - Serverworks K2 SATA controllers: svwsata(4) - Silicon Image 0680 IDE controller: cmdide(4) - Silicon Image SATALink 3112 Serial ATA controller: satalink(4) - Silicon Image SteelVine 3124/3132/3531 Serial ATA II controller: siisata(4) - Silicon Integrated System 5597/5598 IDE controller: siside(4) - Symphony Labs 82C105 and Winbond W83C553F IDE controller: slide(4) - VIA Technologies VT82C586, VT82C586A, VT82C596A, VT82C686A, VT8233A, and VT8235 IDE Controllers: viaide(4) The 0x0001 flag forces the pciide driver to use DMA when there is no explicit DMA mode setting support for the controller but DMA is present. If the BIOS didn't set up the controller properly, this can cause a machine hang. The 0x0002 flag forces the pciide driver to disable DMA on chipsets for which DMA would normally be enabled. This can be used as a debugging aid, or to work around problems where the IDE controller is wired up to the system incorrectly. SEE ALSO
acardide(4), aceride(4), artsata(4), ata(4), atapi(4), cmdide(4), cypide(4), geodeide(4), hptide(4), intro(4), optiide(4), pci(4), pdcide(4), piixide(4), pnpbios(4), satalink(4), schide(4), siisata(4), siside(4), slide(4), viaide(4), wd(4), wdc(4) BSD
November 7, 2010 BSD
Check Out this Related Man Page
atapi_ide(7) Miscellaneous Information Manual atapi_ide(7) NAME
atapi_ide - Interface for ATAPI or IDE (PC) devices SYNOPSIS
PCI bus CMD/Acer ATAPI/IDE adapter: bus pci0 at * bus ata0 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata0 slot 1 PCI bus Cypress ATAPI/IDE adapter: bus pci0 at * bus ata0 at * bus ata1 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata1 slot 0 PCMCIA bus ATA/IDE disk card: bus pcmcia0 at * bus ata0 at pcmcia? controller scsi0 at ata0 DESCRIPTION
Devices commonly known for their use on PC devices as ATA or IDE devices are supported using the SCSI CAM device driver. The ATA standard has also been expanded to include what are known as ATAPI devices. The SCSI CAM device driver is also used for those disks and CD-ROM devices. These devices may also be known under the names EIDE, ATA-2, Fast-ATA, or Ultra-ATA. Beacuse the ATA/IDE standard was not developed until after many of the devices that used this standard were produced, there are many devices which do not strictly comply with the standard. While it is possible some industry standard devices may appear to work, it is also possible they will cause hang or data corruption cases when used under more stressful situations. For this reason, it is recommended that only the supported devices be used. These devices have been tested and are certified for correct operation. ATAPI/IDE controllers allow the connection of two devices. These two devices are known as the master device and the slave device. If only one device is connected, that device must be the master (slave-only configurations are not supported). When used by the SCSI CAM device driver, the IDE master device is assigned SCSI id 0 for that controller. The slave device is assigned SCSI id 1 for that controller. No other SCSI ids are assigned on that controller. Most ATAPI/IDE adapters contain two channels (known as the primary and secondary). Each of these channels may contain their own master and slave devices. Therefore, a dual channel ATAPI/IDE controller may contain up to 4 devices (a master and slave pair on each channel). These 4 devices are then accessed as SCSI id 0 and 1 on each channel. Many SCSI operations translate perfectly for use on IDE. For example, read and write operations are the same. However, many SCSI disk mode pages are emulated by the IDE device driver. For example, you can display the SCSI inquiry mode pages using the following command: % scu show inq pages pages are created by the device driver to contain the long (full IDE) form of the device name, serial number, revision, and the operational modes of the device. Only a shortened version of this information is available with the standard SCSI inquiry command. Note also that the following command: % scu show pages Shows that the SCSI mode pages contain only partial information. Only that informa- tion (such as geometry) that the drive reports to the system is able to be reformatted into these emulated SCSI mode pages. Much of the information (such as RPM) is simply not available from the drive, and therefore not accurately reported. ATAPI devices are much more closely related to SCSI devices, and as such contain their own mode pages. Therefore, for these devices, the mode page values reported are those from the device, and no emulation is involved. ATAPI tape devices are not supported at this time. FILES
/dev/disk/dsk??? /dev/disk/dsk??? RELATED INFORMATION
SCSI(7), rz(7), and disklabel(8) delim off atapi_ide(7)