linux-kernel - DMA from memory to local bus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <62DDBB9E5E23CC4A929EE46F9427CEAF0162468D@BUDMLVEM04.e2k.ad.ge.com>
Date:	Fri, 28 Nov 2008 07:35:28 +0100
From:	"Hommel, Thomas (GE EntSol, Intelligent Platforms)" 
	<Thomas.Hommel@...anuc.com>
To:	<linux-kernel@...r.kernel.org>
Cc:	<maciej.sosnowski@...el.com>, <dan.j.williams@...el.com>
Subject: DMA from memory to local bus

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.
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/