From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guennadi Liakhovetski Subject: Re: ATMEL camera interface Date: Mon, 3 May 2010 16:26:18 +0200 (CEST) Message-ID: References: <4BD9AA8A.7030306@atmel.com> <4BDED3A8.4090606@atmel.com> <4BDEDB06.9090909@atmel.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from mail.gmx.net ([213.165.64.20]:46029 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932433Ab0ECO0K (ORCPT ); Mon, 3 May 2010 10:26:10 -0400 In-Reply-To: <4BDEDB06.9090909@atmel.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Sedji Gaouaou Cc: Linux Media Mailing List , linux-input@vger.kernel.org On Mon, 3 May 2010, Sedji Gaouaou wrote: > Well I need contiguous memory, so I guess I will have a look at mx1_camera.c? > Is there another example? > > What do you mean by videobuf implementation? As I said I just need a > contiguous memory. I mean, whether you're gping to use videobuf-dma-contig.c or videobuf-dma-sg.c, respectively, whether you'll be calling videobuf_queue_dma_contig_init() or videobuf_queue_sg_init() in your driver. Regards Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/