On Mon, Nov 28, 2011 at 08:47:31AM +0100, Marek Szyprowski wrote:
> On Tuesday, November 08, 2011 7:43 PM Daniel Vetter wrote:
> > Thanks for the clarification. I think this is another reason why
> > get_scatterlist should return the sg_list already mapped into the device
> > address space - it's
Hello,
I'm sorry for the late reply, I must have missed this mail...
On Tuesday, November 08, 2011 7:43 PM Daniel Vetter wrote:
> On Tue, Nov 08, 2011 at 05:55:17PM +, Russell King - ARM Linux wrote:
> > On Tue, Nov 08, 2011 at 06:42:27PM +0100, Daniel Vetter wrote:
> > > Actually I think
On Tue, Nov 08, 2011 at 05:55:17PM +, Russell King - ARM Linux wrote:
> On Tue, Nov 08, 2011 at 06:42:27PM +0100, Daniel Vetter wrote:
> > Actually I think the importer should get a _mapped_ scatterlist when it
> > calls get_scatterlist. The simple reason is that for strange stuff like
> >
On Tue, Nov 08, 2011 at 10:59:56AM -0600, Clark, Rob wrote:
> On Thu, Nov 3, 2011 at 3:04 AM, Marek Szyprowski
> > 2. dma-mapping api is very limited in the area of the dynamic buffer
> > management,
> > this API has been designed definitely for static buffer allocation and
> > mapping.
> >
> >
On Tue, Nov 08, 2011 at 06:42:27PM +0100, Daniel Vetter wrote:
> Actually I think the importer should get a _mapped_ scatterlist when it
> calls get_scatterlist. The simple reason is that for strange stuff like
> memory remapped into e.g. omaps TILER doesn't have any sensible notion of
> an
On Tue, Nov 08, 2011 at 10:59:56AM -0600, Clark, Rob wrote:
On Thu, Nov 3, 2011 at 3:04 AM, Marek Szyprowski
2. dma-mapping api is very limited in the area of the dynamic buffer
management,
this API has been designed definitely for static buffer allocation and
mapping.
It looks that
On Tue, Nov 08, 2011 at 06:42:27PM +0100, Daniel Vetter wrote:
Actually I think the importer should get a _mapped_ scatterlist when it
calls get_scatterlist. The simple reason is that for strange stuff like
memory remapped into e.g. omaps TILER doesn't have any sensible notion of
an address in
