Intel
®
81341 and 81342—Address Translation Unit (PCI Express)
Intel
®
81341 and 81342 I/O Processors
Developer’s Manual
December 2007
292
Order Number: 315037-002US
Example 8. ATUE as a Root Complex and ATUX as a Central Resource
The user wants to setup the ATUE as root complex and ATUX as a central resource by
using the Inbound Address Translation Window 2 and Outbound Address Translation
Window 2 of the ATUs. Each ATU would support a 4-GByte Inbound window and a 4-
GByte Outbound window. ATUE outbound window is placed in section 6 and the ATUX
outbound window is placed in section 9 of the 64-GByte internal address space.
— External Straps: INTERFACE_SEL_PCIX# = ‘0’, PCIE_RC# = ‘0’, and PCIX_EP#
= ‘1’. Note that setting up INTERFACE_SEL_PCIX# to ‘0’ causes the ATUX to be
function number 0H and the ATUE to be function number 5H. In this scenario
since none of the ATUs is an endpoint, INTERFACE_SEL_PCIX# can be setup to
either ‘0’ or ‘1’. However, the function number must be consistent with the
function number field programmed in the OUMBAR2[30:28] as this function
number is used to report and log error conditions.
— Inbound Address Translation Window for ATUE:
IALR2 = 00000000H, IATVR2 =
00000000H, IAUTVR2 = 00000009H.
— Outbound Address Translation Window for ATUX:
OUMBAR2 = 80000009H,
OUMWTVR2 = 00000000H
— Inbound Address Translation Window for ATUX:
IALR2 = 00000000H, IATVR2 =
00000000H, IAUTVR2 = 00000006H.
— Outbound Address Translation Window for ATUE:
OUMBAR2 = D0000006H,
OUMWTVR2 = 00000000H.
Warning:
The following restrictions on the embedded bridge transactions from the ATUX to ATUE
need to be noted.
• When the ATUX is operating in PCI-X mode, Inbound Write transactions with non-
contiguous byte enables are not supported. Note that byte enables may be disabled
in the first and/or last DWORD of an Inbound Write transaction.
• When the ATUX is operating in conventional PCI mode, all of the byte enables must
be asserted on Inbound Write transactions.