Specifications

Futurebus+ Bus Support
15.12 Futurebus+ on DEC 10000/7000
Figure 15–11 Futurebus+ A64 Space
ZK−6736A−GE
Futurebus+ A64 Space DEC 10000/7000 System Memory
00 0000 0000
FF FFFF FFFF
0000 0000 0000 0000
0000 00FF FFFF FFFF
0000 0000 F000 0000
FFFF FFFF FFFF FFFF
0000 00FF EFFF FFFF
Use A32
equivalent
address
A64
available
memory
space
The Flag responds as a Futurebus slave to A64 transactions from 0000 0000
F000 0000 to 0000 00FF FFFF FFFF and passes the transfer to DEC 10000/7000
system memory. The Flag does not respond to A64 transactions directed to 64 bit
address space from 0 to 0000 0000 EFFF FFFF. Adapters should not generate
A64 accesses in this region anyway, as this region overlaps A32 address space.
The equivalent A32 address should be used in the address range below EFFF
FFFF. See the Flag specification and the IEEE Futurebus+ specifications for more
information. If a Futurebus+ adapter requires A64 space, the driver must call
IOC$RESERVE_FBUS_A64 to reserve a region of A64 space. The A64 address
region at 100 0000 0000 through FFFF FFFF FFFF FFFF (which is the address
range beyond the space consumed by the Flag module) is available to adapters.
15.12.3 DEC 10000/7000 ADP List
During booting, INI$IOMAP creates an ADP list describing the DEC 10000/7000
I/O subsystem. The exact format of the DEC 10000/7000 ADP list depends on
which I/O bridges and backplanes are installed in the system. An example of a
DEC 10000/7000 ADP list with an XMI and a Futurebus+ backplane is shown in
Figure 15–12.
15–16