Behavior Of Pci/Pci-X Initiated Cycles To Hub Interface - Intel 6300ESB Datasheet

I/o controller hub
Hide thumbs Also See for 6300ESB:
Table of Contents

Advertisement

18.9.4
Behavior of PCI/PCI-X Initiated Cycles to Hub
Interface
Table 629. Terminations of Completion Required Cycles to Hub Interface
Hub Interface Termination
Successful
Master Abort (PCI)
Master Abort (PCI-X)
Target Abort
Master and Target Abort
NOTES:
1. The Intel
Hub Interface before the initial connect by PCI or when the PCI master reconnects after a
previous disconnect. When the Intel
the middle of a read completion stream it does not interrupt the stream to signal Target
Abort.
2. The Intel
Target Abort for the remaining completion sequence when an abort is detected on the Hub
Interface. When several bytes of data returned successfully from the Hub Interface and have
not yet been sent back on PCI-X, when the abort is detected on the Hub Interface the Intel
6300ESB ICH stops the current sequence for that data (if it was running) and generates the
Split Completion Error Message.
18.10 Delayed/Split Transactions
18.10.1 Number Supported
When in PCI mode, transactions follow the delayed transaction model of PCI 2.2. When
in PCI-X mode, transactions follow the split transaction model of PCI-X. For each
bridge, the Intel
and one delayed/split transaction outbound.
The Hub Interface may take four outbound delayed/split transactions, but only
launches one at a time to each PCI-X interface. Each PCI interface may take eight
delayed/split transactions, but only launches four of those transactions onto the Hub
Interface.
The outbound delayed/split transactions does not prefetch from PCI devices, regardless
of whether the transaction falls in the prefetchable window or the non-prefetchable
window. When in PCI mode, the inbound delayed/split transactions prefetch for all
command types. The "memory read" command may optionally have its prefetch turned
off as specified in the PCI bridge specification. When in PCI-X mode, the inbound
delayed/split transactions do not prefetch – they acquire only the byte count from the
request.
®
Intel
6300ESB I/O Controller Hub
DS
698
Successful
Target Abort
Split Master Abort
Target Abort (PCI)
Split Target Abort (PCI-X)
Target Abort (PCI)
Split Target Abort (PCI-X)
®
6300ESB ICH only signals Target Abort when the error has been logged from the
®
6300ESB ICH issues a Split Completion Error Message with either Master Abort or
®
6300ESB ICH supports eight delayed / split transactions inbound,
PCI Completion
None
Received Master Abort (Pri)
1
Signaled Target Abort (Sec)
2
Received Master Abort (Pri)
1
Received Target Abort (Pri)
2
Signaled Target Abort (Sec)
Received Master Abort (Pri)
1
Received Target Abort (Pri)
2
Signaled Target Abort (Sec)
®
6300ESB ICH receives an abort on the Hub Interface in
®
Intel
6300ESB ICH—18
Status Register Bits Set
November 2007
Order Number: 300641-004US
®

Advertisement

Table of Contents
loading

Table of Contents