To: linux-kernel@vger.kernel.org
From: Robert Hancock <hancockr@shaw.ca>
Subject: Re: DMA from memory to local bus
Date: Fri, 28 Nov 2008 21:24:40 -0600
Message-ID: <4930B5F8.6020601@shaw.ca>
References: <62DDBB9E5E23CC4A929EE46F9427CEAF0162468D@BUDMLVEM04.e2k.ad.ge.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: maciej.sosnowski@intel.com, dan.j.williams@intel.com
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
In-Reply-To: <62DDBB9E5E23CC4A929EE46F9427CEAF0162468D@BUDMLVEM04.e2k.ad.ge.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1053
Lines: 18

Hommel, Thomas (GE EntSol, Intelligent Platforms) wrote:
> Hi all,
> I'm currently developing a driver and want to make use of the DMA
> offload engine. Data has to be transferred from memory to a device on
> the local bus and vice versa.
> At a first look, the function dma_async_memcpy_buf_to_buf() seemed to be
> suitable, but it does not translate addresses correctly. Both addresses
> are treated as if they were in memory.

That would be the normal use of these things, I believe.. normally when 
copying to/from a device the device does it itself with bus master DMA.

> In my configuration, the buffer is located in memory, but the device's
> I/O space is mapped into vmalloc space via ioremap(). How can I access
> the I/O space corectly from the DMA controller?
> 
> Thanks for your help
> Thomas

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/