Re: driver for the mvme5100

That's what you should expect to see.  In Linux a PCI mem resource
is defined as an ioremapable token.  It may or may not be a PCI or
processor bus address.  In the case of a PReP memory map, PCI bus
addresses are translated in a non-1:1 fashion.  So an offset of
0xc0000000 is correct for the difference between the actual BAR
value and the corresponding Linux resource value.  In the case
of a CHRP memory map, PCI bus addresses are 1:1 with processor
bus addresses (like most developers like to assume..x86).  In
this case the mem resource start will be the same as the actual
memory BAR value.

Hi,

With your informations I have found the problem and also a solution.

I had programmed the tundra chip SLSI image to map at 0x0 in pci address.
In the prep model, there isn't any problem with the dram memory. In the
CHRP
there is a ressource allocation conflict with the dram memory. Since my
mvme5100 board
have 64MB of memory I have changed the SLSI offset to 128MB and there is no
more conflict.

Thanks one more time, xavier

--
33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/