
82815 GMCH
R
130
Datasheet
4.3.2.
Address Decode Rules
The GMCH accepts all memory read and write accesses from the hub interface to both system memory
and graphics memory. The hub interface accesses that fall elsewhere within the PCI memory range will
not be accepted. The GMCH never responds to hub interface initiated I/O read or write cycles.
The GMCH accepts accesses from the hub interface to the following address ranges:
All memory read and write accesses to main DRAM including PAM region (except SMM space)
All memory read/write accesses to the graphics aperture (DRAM) defined by APBASE and
APSIZE.
All hub interface memory write accesses to AGP memory range defined by MBASE, MLIMIT,
PMBASE, and PMLIMIT.
Memory writes to VGA range on AGP, if enabled.
The hub interface memory accesses that fall elsewhere within the memory range are considered invalid
and will be remapped to a translated memory address, snooped on the host bus, and dispatched to
DRAM. Reads will return all 1s with Master Abort completion. Writes will have byte enables deasserted
and will terminate with Master Abort, if completion is required. I/O cycles will not be accepted. They are
terminated with Master Abort completion packets.
The Hub Interface Accesses to GMCH that Cross Device Boundaries
The hub interface accesses are limited to 256 bytes but have no restrictions on crossing address
boundaries. A single hub interface request may, therefore, span device boundaries (AGP, DRAM) or
cross from valid addresses to invalid addresses (or vica versa). The GMCH does not support transactions
that cross device boundaries. For reads and for writes requiring completion, the GMCH provides
separate completion status for each naturally-aligned 32 or 64 byte block. If the starting address of a
transaction hits a valid address, the portion of a request that hits that target device (AGP or DRAM) will
complete normally.
The remaining portion of the access that crosses a device boundary (targets a different device than that of
the starting address) or hits an invalid address will be remapped to memory address 0h, snooped on the
host bus, and dispatched to DRAM. Reads will return all 1s with Master Abort completion. Writes will
have byte enables deasserted and will terminate with Master Abort if completion is required.
If the starting address of a transaction hits an invalid address, the entire transaction will be remapped to
memory address 0h, snooped on the host bus, and dispatched to DRAM. Reads will return all 1s with
Master Abort completion. Writes will have byte enables deasserted and will terminate with Master Abort
if completion is required.