Em Tue, 12 May 2009 22:30:37 +0900
Magnus Damm escreveu:
> >> What does it do, how does it do it and why does it do it?
> >
> > A good documentation is a really good idea here. There videobuf internals
> > are
> > very complex. A good documentation for it is very important to keep it
> > updat
On Mon, May 11, 2009 at 10:36 PM, Mauro Carvalho Chehab
wrote:
> Em Fri, 8 May 2009 13:06:58 -0700
> Andrew Morton escreveu:
>
>> On Fri, 08 May 2009 17:53:10 +0900
>> Magnus Damm wrote:
>>
>> > From: Magnus Damm
>> >
>> > This is V3 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
>> >
Em Fri, 08 May 2009 17:53:10 +0900
Magnus Damm escreveu:
> From: Magnus Damm
>
> This is V3 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
>
> Since videobuf-dma-contig is designed to handle physically contiguous
> memory, this patch modifies the videobuf-dma-contig code to only acce
Em Fri, 8 May 2009 13:06:58 -0700
Andrew Morton escreveu:
> On Fri, 08 May 2009 17:53:10 +0900
> Magnus Damm wrote:
>
> > From: Magnus Damm
> >
> > This is V3 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
> >
> > Since videobuf-dma-contig is designed to handle physically contiguou
On Fri, 08 May 2009 17:53:10 +0900
Magnus Damm wrote:
> From: Magnus Damm
>
> This is V3 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
>
> Since videobuf-dma-contig is designed to handle physically contiguous
> memory, this patch modifies the videobuf-dma-contig code to only accept
From: Magnus Damm
This is V3 of the V4L2 videobuf-dma-contig USERPTR zero copy patch.
Since videobuf-dma-contig is designed to handle physically contiguous
memory, this patch modifies the videobuf-dma-contig code to only accept
a user space pointer to physically contiguous memory. For now only
V
