[This is
preliminary documentation and subject to change.]
This is the Universal
AGPv3.5 chipset driver. This driver works on any (v3.5) chipset that is
compatible with the AGP3 Specification from Intel®. Currently there is no
corresponding hardware for any 64-bit platform.
·
The AGP target capability version must not change,
i.e., when an AGP2 master device is present, the target capability must remain
v3.5.
·
The AGPv3.5 capability block, and Aperture Base
register must reside in a single PCI device/function, i.e., for PCI_CAPABILITY_ID_AGP
systems this is typically PCI bus 0, device 0, function 0, whereas with the new
PCI_CAPABILITY_ID_AGP_TRAGET, these registers simply reside in the PCI-to-PCI
bridge device/function on which the driver is loaded.
The sample is built with
the standard DDK BUILD utility in the standard checked or free DDK build
environment. Simply type build from the
\\Ntddk\Src\Kernel\Agp\Ugp35 directory. A successful build produces Ugp35.sys.
An installation file,
Uagp35.inf, is provided. Install Uagp35.sys by creating an installation
directory containing the Uagp35.sys binary and Uagp35.inf.
In the .inf file, change the names and PCI IDs as necessary for
your setup. Then, go into Device Manager and right-click on the PCI-PCI
bridge that represents your AGPv3.5 bridge. Select Properties.
Then select the Driver tab and click the Update Driver button.
Follow the prompts in the Update Driver wizard. On the Locate Driver Files
page, select Specify a Location, and enter the location of your .inf and driver.
Although the Uagp35.sys
driver, when built in the XP build environment (in conjunction with AGPLIB),
will also run on Win2K, and Microsoft®
Windows® Server 2003, this has not been extensively
tested. Conversely, when the Uagp35.sys driver (and AGPLIB) are built in the Windows Server 2003 build environment, it will not
use the obsolete HAL APIs HalGet/SetBusDataByOffset,
but this type of driver is only compatible on OS versions that support the new
AGP_TARGET_BUS_INTERFACE_STANDARD, i.e., XPSP2, Windows
Server 2003, and higher.
Therefore, if your goal is building a driver for test and inclusion in a
future OS release, you should build in the Windows
Server 2003 build environment, whereas if your goal is to produce a
binary that is compatible across the broadest range of OS releases, you should
build in the XP build environment.
(See Agplib.htm for additional compatibility details.)
See http://developer.intel.com/technology/agp/agp_3_spec.htm
for more information on AGP3 HW design.
File Description