Intel
82815EM GMCH
R
122
Datasheet
The GMCH2-M accepts accesses from the hub interface to the following address ranges:
All memory Read/Write accesses to Main DRAM including PAM region (except SMM space)
All memory Read/Write accesses to the Graphics Aperture 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 1’s with Master Abort completion. Writes will have BE’s 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.
4.7.2.
The Hub Interface Accesses to GMCH2-M 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 visa versa). The GMCH2-M does not support transactions
that cross device boundaries. For reads and for writes requiring completion, the GMCH2-M will provide
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 1’s with Master Abort completion. Writes will
have BE’s deasserted and will terminate with Master Abort if completion is required.
If the starting address of a transaction hits a 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 1’s with
Master Abort completion. Writes will have BE’s deasserted and will terminate with Master Abort if
completion is required.
4.7.3.
AGP Interface Decode Rules
4.7.3.1.
Cycles Initiated Using PCI Protocol
The GMCH2-M does not support any AGP/PCI access targeting the hub interface. The GMCH2-M will
claim AGP/PCI initiated memory read and write transactions decoded to the main DRAM range or the
Graphics Aperture range. All other memory read and write requests will be master-aborted by the
AGP/PCI initiator as a consequence of GMCH2-M not responding to a transaction.
Under certain conditions, the GMCH2-M restricts access to the DOS Compatibility ranges governed by
the PAM registers by distinguishing access type and destination bus. The GMCH2-M accepts AGP/PCI
write transactions to the compatibility ranges if the PAM designates DRAM as write-able. If accesses to
a range are not write enabled by the PAM, the GMCH2-M does not respond and the cycle will result in a
master-abort. AGP/PCI read transactions to the compatibility ranges are accepted if the PAM designates