|
hello !
I have a few questions on split completions: 1. If due to internal completer error or unpopulated address range (say a 128 byte block with only 8 bytes populated), the backend application stops providing split read completion data in the middle of an ADQ, is the PCI-X logic supposed to insert dummy data and negate Byte Enables till the next ADB and then disconnect? 2. The SCM generated will have the remaining lower-address and remaining byte-count fields indicating the data not sent starting from the dummy data in the previous split completion? 3. Does this also hold for target aborts during split completions? 4. Why is there no definition of Completer-Class/Target-Abort-Index in the SCM's in the spec. ? Thanks. |