hello,
we are using tornado2.2 with an mvme2400 board together with an
dpio-card from vmetro. our systems was running but after some updates
from 2.0-->2.2 and NT-->XP the dpio-card is not configured and not
accessible.
in addition i found some news about the changed header-files from
pciConfigLib.h instead of pciIomapLib.h for T2.2. and what about these
INCLUDE_PCI_AUTOCONF in this business...?

iam somehow a rookie with with this pci-dpio stuff, so please give me
any hint that comes to your mind...even if iam posting trivial things
and simply doing bad/stupid things.

booting and use of pciConfigTopoShow before our dpioInit routine is
running gives:
[0,0,0] type=HOST BRIDGE
status=0x02a0 ( 66MHZ FBTB DEVSEL=1 )
command=0x0006 ( MEM_ENABLE MASTER_ENABLE )
bar0 in I/O space @ 0x00000000
bar1 in 32-bit mem space @ 0xfc000000
[0,11,0] type=ISA BRIDGE
status=0x0200 ( DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
[0,11,1] type=MASS STORAGE
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0000 ( )
bar0 in I/O space @ 0x000001f0
bar1 in I/O space @ 0x000003f4
bar2 in I/O space @ 0x00000170
bar3 in I/O space @ 0x00000374
bar4 in I/O space @ 0x00000000
bar5 in I/O space @ 0x00000000
[0,13,0] type=UNKNOWN (0x80) BRIDGE
status=0x0200 ( DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
bar0 in 32-bit mem space @ 0xfd000000
bar1 in I/O space @ 0x00010000
[0,14,0] type=NET_CNTLR
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
bar0 in I/O space @ 0x00011000
bar1 in 32-bit mem space @ 0xfd001000
[0,16,0] type=DATA ACQUISITION DEV
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
bar0 in 32-bit mem space @ 0xfd001400
bar1 in I/O space @ 0x00011100
bar2 in 32-bit mem space @ 0xff000000

where [0,16,0] is the dpio-card, as i pressume. i understand that ppc
have no i/o mapped pci but memory mapped pci. so after running our
dpioInit routine it looks like the following:

[0,0,0] type=HOST BRIDGE
status=0x02a0 ( 66MHZ FBTB DEVSEL=1 )
command=0x0006 ( MEM_ENABLE MASTER_ENABLE )
bar0 in I/O space @ 0x00000000
bar1 in 32-bit mem space @ 0xfc000000
[0,11,0] type=ISA BRIDGE
status=0x0200 ( DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
[0,11,1] type=MASS STORAGE
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0000 ( )
bar0 in I/O space @ 0x000001f0
bar1 in I/O space @ 0x000003f4
bar2 in I/O space @ 0x00000170
bar3 in I/O space @ 0x00000374
bar4 in I/O space @ 0x00000000
bar5 in I/O space @ 0x00000000
[0,13,0] type=UNKNOWN (0x80) BRIDGE
status=0x0200 ( DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
bar0 in 32-bit mem space @ 0xfd000000
bar1 in I/O space @ 0x00010000
[0,14,0] type=NET_CNTLR
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0007 ( IO_ENABLE MEM_ENABLE MASTER_ENABLE )
bar0 in I/O space @ 0x00011000
bar1 in 32-bit mem space @ 0xfd001000
[0,16,0] type=DATA ACQUISITION DEV
status=0x0280 ( FBTB DEVSEL=1 )
command=0x0002 ( MEM_ENABLE )
bar0 in 32-bit mem space @ 0xf7000000
bar1 in I/O space @ 0x00000000
bar2 in 32-bit mem space @ 0xf8000000

the ppc the prints out the following:
DPIO Device Driver - Release:
Copyright (C) 1996-1999 - VMETRO, Inc. All rights reserved.
Creation date: Aug 17 2005, 16:42:07


Exception number 768: Task: 0x1eff760 (t1)

data access
program counter: 0x100184
access address: 0xf8e00020
machine status: 0xb030
1f6ff8 vxTaskEntry +68 : 1aeea0 ([])
1aef48 wdbFuncCallLibInit+158: fttL3SlaveInit ([])
1d7a84 fttL3SlaveInit +138: fttL3DpioInit ([])
1da28c fttL3DpioInit +78 : dpioDevScan (f7000000)
210f74 dpioDevScan +208: 210c54 (0)
210d0c pciLocalToPciMemAdrs+e4 : dpioDevCreate (&devName)
2089d0 dpioDevCreate +144: 209bcc (1efa510)
209d08 dpioDisplayRelease+1280: 208df8 (1efa510)
208e24 dpioDisplayRelease+39c: pciMemRdByte (f8e00020)
21086c pciMemRdByte +24 : sysPciInByte ([])

data access
Exception current instruction address: 0x00100184
Machine Status Register: 0x0000b030
Data Access Register: 0xf8e00020
Condition Register: 0x20000085
Data storage interrupt Register: 0x40000000
Task: 0x1eff760 "t1"
value = 0 = 0x0

i tryed to initialise manually with dpioDevScan,etc. with the address
0xfd001400 for dpio-card [0,16,0] given directly after start. but this
results to the same error as written above with the 0xfd001400 adrdress
instead of 0x7f000000.

as far as i understand the Data storage interrupt Register: 0x40000000
tells me that iam writing nowwhere but i dont understand how this could
happen.

any help/hint is welcome...