Intel® 460GX Chipset Software Developer’s Manual
7-11
AGP Subsystem
When a DRC is valid in the GXB, a 2
15
PCI clock timer is started as described in the PCI 2.2
Specification. When the timer expires the DRC is discarded and the associated delayed read
matching registers are cleared. This condition is optionally treated as an error. See the “Error”
Chapter for details.
7.2.7.5
Inbound I/O Reads
I/O reads on the PCI bus are not claimed by the GXB.
7.2.7.6
Inbound Writes
Memory write requests may be directed to the memory only. All write requests are posted. A series
of buffers in both the GXB and SAC allow posted writes to be accumulated and serviced as
convenient. The actual data is forwarded to buffers in the SAC, where it is held until the request
can be snooped on the system bus.
Writes to Memory
The snoops on the system bus for PCI Stream AGP-DRAM writes will be initiated by using the
Memory Read and Invalidate of Length=0 system bus transaction. Any implicit write back due to
snoop hit to a modified line will be snarfed by the SDC. The write back data will be merged with
the AGP write data within the SDC.
Writes to memory use the linear burst ordering provided on the AGP bus.
The Write and Write & Invalidate commands have small differences, as follows:
Write
Accumulates posted data until (a) a cache line boundary is reached, or (b) the
master disconnects, before forwarding the request to the SAC. The SAC
therefore deals with a single packet that represents up to a cache line of data.
The SAC places a cache-line snoop on the bus, and the SDC handles the writing/
merging of the partial data into memory. The Expander bus command is a write.
Write & Invalidate By definition this must be an aligned cache line worth of data. It is forwarded
to the SAC as a cache line of data. The SAC places a cache-line snoop on the
bus for each line of data, and the SDC writes the full cache line into memory.
In the event the snoop results in a HITM#, the write back data from the
processor is discarded by the SDC.
Note that the actual writing of the data into memory may be delayed. However, in effect, the data
can be counted as being written in the memory, since no other write to that location may pass this
write.
7.2.7.7
Inbound I/O Writes
I/O writes on the PCI bus are not claimed by the GXB.
Table 7-2. Delayed Read Matching Criteria
Command
Address
BEs
Any Memory Read
Match
Match
Summary of Contents for 460GX
Page 1: ...Intel 460GX Chipset System Software Developer s Manual June 2001 Document Number 248704 001 ...
Page 20: ...Introduction 1 8 Intel 460GX Chipset Software Developer s Manual ...
Page 80: ...System Architecture 3 8 Intel 460GX Chipset Software Developer s Manual ...
Page 90: ...System Address Map 4 10 Intel 460GX Chipset Software Developer s Manual ...
Page 98: ...Memory Subsystem 5 8 Intel 460GX Chipset Software Developer s Manual ...
Page 146: ...AGP Subsystem 7 16 Intel 460GX Chipset Software Developer s Manual ...
Page 170: ...IFB Register Mapping 9 6 Intel 460GX Chipset Software Developer s Manual ...
Page 190: ...IFB Usage Considerations 10 20 Intel 460GX Chipset Software Developer s Manual ...
Page 232: ...LPC FWH Interface Configuration 11 42 Intel 460GX Chipset Software Developer s Manual ...
Page 244: ...IDE Configuration 12 12 Intel 460GX Chipset Software Developer s Manual ...
Page 258: ...Universal Serial Bus USB Configuration 13 14 Intel 460GX Chipset Software Developer s Manual ...
Page 270: ...SM Bus Controller Configuration 14 12 Intel 460GX Chipset Software Developer s Manual ...
Page 288: ...PCI LPC Bridge Description 15 18 Intel 460GX Chipset Software Developer s Manual ...
Page 294: ...IFB Power Management 16 6 Intel 460GX Chipset Software Developer s Manual ...