Problems with dma_alloc_coherent()
jwhitney-linuxppc at sands-edge.com
Fri Apr 2 04:48:56 EST 2004
> They do the same thing _now_, because it's a _new_ API. This _may_
> change in
> DMA API is needed, because generic code uses it, most archs have
> default generic
> implementation which use PCI DMA API and I don't see _any_ problems
> with that.
> Some archs may have _different_ implementations which DON'T use PCI
> DMA API.
>> This means that the address produced by pci_alloc_... and
>> are incorrect for a device like a direct memory-mapped encryption
>> or in my case a northbridge DMA controller.
> It depends, on all systems I use PCI view == phys address, so it'll
And in actuality, it will work in my case as well. However, it won't
work for some single-board computers I've worked on, so I'd like to
have an API that works for everything.
It would be nice if there was a dma_bus_offset field in the device
structure that got set by the device creator. PCI devices would get
PCI_DRAM_OFFSET, PLB devices would get 0, OCP devices would get
whatever they need.
Then the API could add the appropriate offset for the device passed in,
rather than relying on the static virt_to_bus() mapping, which is PCI
specific. As a default, with a NULL device given, I think it should
return a PLB physical address.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev