405gp PCI?

[Denton Gentry]

> Hmmm...I know it works with PCI slave devices, but I don't know
> if it will for masters.  I know the Linux support functions for
> virt_to_bus and friends will provide the proper addresses.  Sounds
> like there is some missing 405 register initialization.  Are you
> doing this on a custom board, or in the Walnut eval board?  I
> suspect on the Walnut we rely on the boot rom for some of this
> 405 PCI initialization.

  The addresses returned by virt_to_bus look reasonable. The virtual
address of the buffer in question is 0xc0261940, and the DMA address
returned by virt_to_bus is 0x00261940. I assume that the lower few megs
of physical RAM are pinned memory for the kernel, and that a 1:1 mapping
of physical pages in this pinned memory is done starting at a kernel
offset in the virtual address space, so these addresses look reasonable
to me.

  This is the Walnut eval board. I am using IBM's firmware to tftpboot
a kernel, which the NFS mounts its root filesystem.

  I'll keep digging into it. Since no-one has piped up to confirm that
PCI DMA works in PPC 405gp systems, I'll start looking at the PCI
controller initialization code as well.

> >   Also, though I'm certain that this problem is not caused by
> > stale data, one of the next things I'll need to tackle is cache
> > coherency.
>
> I have just recently finished the pci_consistent_* functions and
> software cache mangement functions so they will do the right thing
> on the IBM4xx and MPC8xx processors.

  Ok, thanks.

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