pi7c8150b Pericom Semiconductor Corporation, pi7c8150b Datasheet - Page 28

no-image

pi7c8150b

Manufacturer Part Number
pi7c8150b
Description
Asynchronous 2-port Pci Bridge
Manufacturer
Pericom Semiconductor Corporation
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
pi7c8150bMA-33
Quantity:
80
Part Number:
pi7c8150bMAE
Manufacturer:
Pericom
Quantity:
10 000
Part Number:
pi7c8150bMAE
Manufacturer:
PERICOM
Quantity:
20 000
Part Number:
pi7c8150bMAIE
Quantity:
375
Part Number:
pi7c8150bMAIE
Manufacturer:
Pericom
Quantity:
10 000
Part Number:
pi7c8150bMAZ
Quantity:
17
Part Number:
pi7c8150bND
Quantity:
800
Part Number:
pi7c8150bNDE
Manufacturer:
CYPRESS
Quantity:
101
Part Number:
pi7c8150bNDE
Manufacturer:
Pericom
Quantity:
10 000
Part Number:
pi7c8150bNDE
Manufacturer:
ALTERA
0
Part Number:
pi7c8150bNDE
Manufacturer:
PERICOM
Quantity:
20 000
Part Number:
pi7c8150bNDIE
Manufacturer:
Pericom
Quantity:
10 000
Part Number:
pi7c8150bNDIE
Manufacturer:
PERICOM
Quantity:
20 000
06-0044
3.6.3
3.6.4
Table 3-4. Read Prefetch Address Boundaries
Table 3-5. Read Transaction Prefetching
READ PREFETCH ADDRESS BOUNDARIES
PI7C8150B imposes internal read address boundaries on read pre-fetched data. When a
read transaction reaches one of these aligned address boundaries, the PI7C8150B stops pre-
fetched data, unless the target signals a target disconnect before the read pre-fetched
boundary is reached. When PI7C8150B finishes transferring this read data to the initiator,
it returns a target disconnect with the last data transfer, unless the initiator completes the
transaction before all pre-fetched read data is delivered. Any leftover pre-fetched data is
discarded.
Prefetchable read transactions in flow-through mode pre-fetch to the nearest aligned 4KB
address boundary, or until the initiator de-asserts FRAME_L. Section 3.6.6 describes flow-
through mode during read operations.
Table 3-4 shows the read pre-fetch address boundaries for read transactions during non-
flow-through mode.
DELAYED READ REQUESTS
PI7C8150B treats all read transactions as delayed read transactions, which means
that the read request from the initiator is posted into a delayed transaction queue.
Read data from the target is placed in the read data queue directed toward the initiator bus
interface and is transferred to the initiator when the initiator repeats
the read transaction.
- does not matter if it is prefetchable or non-prefetchable
* don’t care
See Section 4.3 for detailed information about prefetchable and non-prefetchable address spaces.
Type of Transaction
Configuration Read
I/O Read
Memory Read
Memory Read
Memory Read
Memory Read Line
Memory Read Line
Memory Read Multiple
Memory Read Multiple
Type of Transaction
I/O Read
Configuration Read
Memory Read
Memory Read Line
Memory Read Multiple
Address Space
-
-
Non-Prefetchable
Prefetchable
Prefetchable
-
-
-
-
Page 28 of 108
Read Behavior
Prefetching never allowed
Prefetching never allowed
Downstream: Prefetching used if address is prefetchable space
Upstream: Prefetching used or programmable
Prefetching always used
Prefetching always used
ASYNCHRONOUS 2-PORT PCI-TO-PCI BRIDGE
Cache
(CLS)
*
CLS = 1, 2, 4, 8, 16
*
*
CLS = 0 or 16
CLS = 1, 2, 4, 8, 16
CLS = 0 or 16
CLS = 1, 2, 4, 8, 16
CLS = 0 or 16
Line
Size
APRIL 2006 – Revision 2.02
Prefetch
Boundary
One DWORD (no prefetch)
One DWORD (no prefetch)
One DWORD (no prefetch)
16-DWORD aligned address
boundary
Cache line address boundary
16-DWORD aligned address
boundary
Cache line boundary
32-DWORD aligned address
boundary
2X of cache line boundary
Aligned
PI7C8150B
Address

Related parts for pi7c8150b