Prev: Create a webcam driver and draw into it ?
Next: names of debug registers
From: Maxim S. Shatskih on 9 May 2008 13:16
> Based on my knows, the different IDE Controller, they have own ATA Timing
> Control Registers.
> On Booting, the BIOS IDE Controller Driver will drive the hard disk to
> bootload.
> before this, the BIOS use those registers to config the hard disk to match
> their transfer mode - PIO, UDMA...etc.

Non-PC/AT-compatible controllers use their own extension BIOS, just like SCSI
controllers. int13h is OK for them, but the ports 0x1f0 and interrupt 14 can be
absent.

For such controllers, Windows require their particular driver.

So, just like SCSI, but the attached disks are ATA.

> Does also Windows XP config the hard disk by those registers?

For PC/AT compatible controllers, Windows uses the information from ACPI table,
which appears in the ACPI table as a result of BIOS setup.

For non-PC/AT compatibles, the transfer mode setting is proprietary for the
driver.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Kai Lidda on 13 May 2008 22:51

> Non-PC/AT-compatible controllers use their own extension BIOS, just like SCSI
> controllers. int13h is OK for them, but the ports 0x1f0 and interrupt 14 can be
> absent.
>
> For such controllers, Windows require their particular driver.
>
> So, just like SCSI, but the attached disks are ATA.

If this card is a PCI IDE Card and its class code is IDE controller that
follows Intel specification, does Windows still need a Vendor-specific
driver to drive it?



>
> > Does also Windows XP config the hard disk by those registers?
>
> For PC/AT compatible controllers, Windows uses the information from ACPI table,
> which appears in the ACPI table as a result of BIOS setup.
>
> For non-PC/AT compatibles, the transfer mode setting is proprietary for the
> driver.
>

First  |  Prev  | 
Pages: 1 2
Prev: Create a webcam driver and draw into it ?
Next: names of debug registers