Date: Thu, 10 May 2007 04:32:33 -0700 (PDT)
Message-Id: <20070510.043233.08323827.davem@davemloft.net>
To: maheshk@cdac.in
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: [HOWTO] accessing the DMA mapped data
From: David Miller <davem@davemloft.net>
In-Reply-To: <4642FFA7.4040303@cdac.in>
References: <4642D095.6070305@cdac.in>
	<20070510.014751.74749340.davem@davemloft.net>
	<4642FFA7.4040303@cdac.in>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1007
Lines: 24

From: Mahesh <maheshk@cdac.in>
Date: Thu, 10 May 2007 16:49:03 +0530

> I think you have not understood my question properly. My problem is, the 
> layer above the driver will do
> dma_map_single on a kmalloc'ed buffer and passes the result  (bus 
> address) to the device driver. Now
> the driver has to modify the contents of the the original buffer.
> Is it possible to do that ??

You haven't given an example of where this might actually happen.

The driver is where the DMA mappings almost always occur because
that is the layer that knows the bus technology and therefore
the correct DMA interfaces to call.

What kind of driver do you have and what is this upper layer
doing the mappings for you but not giving you a pointer to
the kernel buffer as well?
-
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/